Versioned security assessment

Report ID: SA-E89B4AEE

6/30/2026, 8:16:33 AM

azure-deploy security assessment v2

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
azure-deploy
Version
v2
Maintainer
microsoft
Coverage
31 Files scanned · 1,416 Lines analyzed
Policy version
Unavailable

Highest confirmed finding severity

Medium

1 confirmed security finding requires attention.

Installation context

Historical evidence

This report may not describe the currently installable artifact. Open the current Skill page for install guidance.

Open current Skill page

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

Static analysis found many command, credential, filesystem, and network patterns, but most are Markdown deployment examples rather than hidden executable code. The confirmed risk is legitimate but high-impact Azure deployment guidance, including no-prompt provisioning, destructive cleanup examples, CI secrets references, and one curl-to-shell installer pattern. No evidence found of credential exfiltration, obfuscation, or prompt injection that would justify blocking publication.

Report position

Historical report

Open audit history before using this report to install.

Audit attestation

Not attestable

The required immutable binding is incomplete.

Human verification

Not verified

No human verification is recorded for this report.

Coverage

31 Files scanned · 1,416 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

    Binding unavailable

  2. Artifact

    Identity incomplete

  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 3 evidence locations

Filesystem access

May read or write local files.

Observed in 4 evidence locations

Env variables

May read values from the process environment.

Observed in 4 evidence locations

External commands

May invoke commands or programs outside the Skill.

Observed in 5 evidence locations

Capability review items (2)
Medium
High-Impact Azure Deployment Commands
TRUE POSITIVE: The skill explicitly guides agents to run Azure deployment and provisioning commands. This is expected for the skill, but it can create, modify, or redeploy cloud resources and may incur cost if used without user confirmation.
The cited files directly instruct deployment commands such as azd up, azd deploy, az deployment, and terraform apply. The commands match the skill purpose, so the risk is operational impact rather than malicious intent.
Medium
Pipe to Shell Installer Pattern
TRUE POSITIVE: The reference guidance installs azd by piping a remote script directly to bash. This creates supply-chain risk because the downloaded script executes immediately without inspection or checksum verification.
The pipe-to-shell pattern is explicit on the cited line. It is a common installer shortcut, but it remains a real security risk in automated agent guidance.

Risk findings

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

Confirmed security concerns (1)

RISK-001 Medium
Destructive Cleanup Commands Require Confirmation
TRUE POSITIVE WITH MITIGATION: The references include destructive cleanup examples such as deleting a resource group. The skill also includes rules requiring user confirmation before destructive actions, which reduces but does not remove the risk.
The destructive command examples and data-loss warning are explicit. Confidence is slightly lower because the skill provides clear confirmation rules that mitigate accidental execution.

Expert evidence

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

Artifact subject

Marketplace commit
Unavailable
Content hash
Unavailable
Tree hash
Unavailable
Skill path
Unavailable
Audit payload hash
Unavailable

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.

Static false positives ignored (3)
Low
Credential References Are CI Configuration Guidance
FALSE POSITIVE FOR EXFILTRATION: The detected Azure credential variables are used in GitHub Actions and Azure identity documentation. No evidence found that the skill sends secrets to an unauthorized endpoint.
The references use standard Azure authentication names and GitHub secrets syntax. The files do not contain a network exfiltration path, but handling cloud credentials still requires care.
Low
Path Traversal and Weak Crypto Alerts Are Documentation False Positives
FALSE POSITIVE: The path traversal alerts correspond to relative Markdown links such as checklist references, not file reads or writes. The weak cryptography alerts appear to be keyword matches in prose or Markdown context, with no cryptographic implementation found.
The cited path references are Markdown navigation, and the reviewed files are documentation rather than source code. No evidence found of filesystem traversal logic or weak cryptographic code.
Low
Prompt Injection Review Found No Malicious Override
FALSE POSITIVE CHECK: The skill uses strong mandatory wording for deployment prerequisites and validation, but no evidence found of instructions to ignore higher-priority rules, skip security review, or claim pre-approval.
The reviewed wording is directive but tied to workflow safety and validation. It does not contain the prompt-injection patterns specified for critical findings.

Verify and export

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

Audit attestation: not_attestable