Versioned security assessment

Report ID: SA-461913B7

6/30/2026, 8:05:53 AM

azure-compliance security assessment v2

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
azure-compliance
Version
v2
Maintainer
microsoft
Source
github.com/microsoft/github-copilot-for-azure/tree/main/plugin/skills/azure-compliance/
Coverage
15 Files scanned · 1,306 Lines analyzed
Policy version
Unavailable

Highest confirmed finding severity

Medium

3 confirmed security findings require 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 produced many high-volume alerts, but most are false positives from Markdown examples, Azure resource identifiers, placeholders, and documentation links. The skill has a legitimate compliance-audit purpose, but it can enumerate Azure resources and includes Key Vault secret inspection and state-changing remediation examples, so publication should include a warning.

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

15 Files scanned · 1,306 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 5 evidence locations

Filesystem access

May read or write local files.

Not recorded by this audit

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

Risk findings

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

Confirmed security concerns (3)

RISK-001 Medium
references/azure-keyvault-expiration-audit.md:91-104
Key Vault Secret Value Exposure Risk
The fallback guidance uses broad Key Vault secret show commands while the stated goal is expiration metadata. That command can expose secret values in tool output if a user runs it without a narrowed query.
The command guidance is directly present and relates to Key Vault secrets. The intent is legitimate auditing, but the unscoped command can disclose more than expiration metadata.
RISK-002 Medium
references/azqr-remediation-patterns.md:23-27references/azqr-remediation-patterns.md:94-98references/azqr-remediation-patterns.md:348-359
State-Changing Azure Remediation Examples
The remediation reference includes Azure CLI and PowerShell examples that update storage accounts, Key Vaults, web apps, SQL servers, and other resources. These are documentation examples, but an assistant could propose or run them without enough confirmation.
The examples are explicitly state-changing Azure commands. They are normal remediation guidance, so the risk depends on whether a tool executes them without user approval.
RISK-003 Low
references/azure-resource-graph.md:71-89references/azure-keyvault-expiration-audit.md:42-49references/azure-quick-review.md:33-47
Cloud Inventory Queries Are Intended Behavior
The reconnaissance-style findings are Azure inventory and Resource Graph queries used for compliance assessment. This is expected for the skill, but results may contain resource names, roles, and configuration metadata.
The skill is explicitly designed to enumerate Azure compliance metadata. This is legitimate, but it still creates privacy and least-privilege considerations.

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 (4)
Low
references/azqr-remediation-patterns.md:12-28references/azure-quick-review.md:27-31references/azure-resource-graph.md:17-19SKILL.md:46
Documentation Command Alerts Are False Positives
Most external command detections are Markdown command blocks, MCP tool names, or Azure CLI examples. I did not find evidence that the skill hides executable scripts or automatically runs shell commands.
The flagged content is visible Markdown reference material. There are no scripts, install hooks, or hidden command execution files in the reviewed evidence.
Low
references/azqr-recommendations.md:3-9references/azqr-recommendations.md:79-83SKILL.md:105-110
Weak Cryptography Alerts Are Terminology Matches
The weak cryptography findings point to headings, tables, and Key Vault terminology rather than implementation of weak algorithms. I did not find evidence of MD5, SHA-1, DES, or similar cryptographic use in the cited context.
The cited lines contain descriptive compliance text or links to Key Vault SDK references. The semantic context does not show weak cryptographic algorithm use.
Low
references/azqr-recommendations.md:171-174references/azure-quick-review.md:156-157references/sdk/azure-keyvault-py.md:14
Hardcoded URL Alerts Are Benign References
The URL detections are official documentation links or placeholder Azure Key Vault endpoint patterns. They do not send data to an external collection service.
The URLs are documentation targets or placeholder service endpoints. No evidence shows network exfiltration or calls to unknown infrastructure.
Low
references/sdk/azure-keyvault-py.md:13-14references/sdk/azure-security-keyvault-keys-java.md:21-22references/sdk/azure-security-keyvault-secrets-java.md:21-22
Certificate And Key File Alerts Are False Positives
The sensitive-file findings match SDK import lines and Key Vault class names, not embedded private keys, certificates, or filesystem paths to secret material.
The reviewed lines show package imports and client builders only. I did not find hardcoded private keys, certificate blobs, or local key files.

Verify and export

JSON report CITATION.cff SARIF 2.1.0 Signed installation manifest

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

Audit attestation: not_attestable