Versioned security assessment

Report ID: SA-EBDFE608

7/23/2026, 7:43:24 PM

azure-validate security assessment v5

Skill Security Certification Report

Audit History
Scanner version 3.0.0 Audit model: codex Latest published report
Skill name
azure-validate
Version
v0.0.0-placeholder
Maintainer
microsoft
Coverage
18 Files scanned Β· 1,301 Lines analyzed
Policy version
skillstore-security-audit-policy-v1

Highest confirmed finding severity

Critical

3 confirmed security findings require attention.

Installation context

Check the current Skill page

This page summarizes report evidence only. The Skill page provides the canonical install advisory.

Open current Skill page

This report does not block or authorize the manifest or ZIP.

All 56 static findings are false positives caused by Markdown formatting, relative documentation links, expected Azure checks, or project-local plan paths. Semantic review found a critical authority injection, high-risk execution of repository-defined builds, and a medium-risk wildcard CORS workaround.

Report position

Latest published report

Latest refers to the report sequence, not to artifact currentness.

Audit attestation

Active attestation

A public attestation is available for this exact report.

Human verification

Not verified

No human verification is recorded for this report.

Coverage

18 Files scanned Β· 1,301 Lines analyzed

3 items shown for review

Limitations

This report does not claim runtime or sandbox execution and does not prove the absence of side effects.

Evidence chain

Follow the evidence from source binding to the install contract. Available evidence supports verification; it is not a safety guarantee.

  1. Source

    Commit and path bound

  2. Artifact

    Content and tree hashes bound

  3. Audit

    Complete

  4. Install contract

    Open manifest to verify

    Open manifest

Capabilities observed

Observed means this report recorded supporting evidence. Not recorded does not prove that a capability is absent.

Contains scripts

May execute code included with the Skill.

Not recorded by this audit

Network access

May connect to external services.

Observed in 2 evidence locations

Filesystem access

May read or write local files.

Observed in 8 evidence locations

Env variables

May read values from the process environment.

Not recorded by this audit

External commands

May invoke commands or programs outside the Skill.

Observed in 24 evidence locations

Risk findings

Confirmed security concerns are separated from items that still need review.

Confirmed security concerns (3)

RISK-001 Critical
Prompt Injection Attempt Detected
The skill states "AUTHORITATIVE GUIDANCE" and claims it is "the officially verified way" before requiring an azure-deploy invocation. These authority claims pressure the agent to accept unverified instructions and trigger deployment beyond a validation request.
The source contains explicit authority language and a mandatory downstream deployment action. Both behaviors match the stated prompt-injection indicators.
RISK-002 High
Untrusted Project Build Execution
The workflow directs the agent to build Dockerfiles and run AZD packaging for repository-controlled projects. Build definitions and package hooks can execute untrusted commands with the agent's local credentials and network access.
The cited instructions explicitly execute repository-defined Docker and packaging workflows. Such workflows commonly execute project-controlled build commands.
RISK-003 Medium
Temporary Wildcard CORS Exposure
A Terraform workaround permits a wildcard CORS origin during an initial deployment. Failures before the required follow-up can leave the API accessible from arbitrary web origins.
The example explicitly sets the allowed origin to a wildcard before a later correction. The warning reduces intent risk but does not prevent an interrupted deployment.

Remediation

Suggested fixes recorded by this audit. Applying them is the maintainer’s responsibility.

  1. FIX-001
    Critical
    The skill claims authoritative verification status and mandates deployment after validation.
    Remove authority claims and automatic deployment instructions. End with a validation report, then require explicit user approval before any deployment handoff.
  2. FIX-002
    High
    Validation can execute build, package, and Docker instructions controlled by the reviewed repository.
    Require confirmation, inspect build definitions first, isolate execution, restrict credentials and network access, and report commands before running them.
  3. FIX-003
    Medium
    The Terraform cycle workaround temporarily permits wildcard CORS.
    Use a known restricted origin or staged hostname. Do not deploy an API with wildcard CORS, even as a temporary bootstrap.

Expert evidence

Immutable subject identity, scanner metadata, dismissed matches, and source-level evidence.

Artifact subject

Marketplace commit
ebdfe608f5de2b66ff37ab4af12af8ac4f5e8006
Content hash
b02b76f66372ee519802a1a92e147cd85019f1027ac04e98441286844e41e15a
Tree hash
b571f2d585f480ebe8b3e090b57741fcee30b98b1d9fdb4e6d419656b2c799b9
Skill path
skills/microsoft/azure-validate
Audit payload hash
d7ccb0e6d3323c6e63ef12bb608b4633

Analysis metadata

Audit model: codex

Analysis state: Complete

Scope is limited to the recorded files, lines, methods, and evidence. No runtime or sandbox execution is claimed.

Verify and export

The manifest and lockfile bind install artifacts to cryptographic hashes. This integrity claim is separate from the security assessment.

Audit attestation: active