Versioned security assessment

Report ID: SA-93DD6360

6/30/2026, 7:47:37 AM

azure-storage security assessment v2

Skill Security Certification Report

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

Highest confirmed finding severity

Low

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 reported many command execution, network, dynamic import, and weak cryptography patterns. Review found these are markdown tables, fenced SDK examples, placeholder Azure service URLs, Microsoft Learn links, and substring false positives, with no evidence of prompt injection, malware, secret harvesting, or unauthorized exfiltration. The remaining risk is low because the skill includes user-mediated Azure CLI and SDK examples that can read or write Azure Storage resources when intentionally run.

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

13 Files scanned · 527 Lines analyzed

2 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 6 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 (1)

RISK-001 Low
SKILL.md:32-47
Azure CLI Examples Can Modify Storage Resources
The CLI fallback includes az storage commands for listing, downloading, and uploading blobs. This is legitimate Azure Storage guidance, but users should review account, container, blob, and file parameters before running commands because upload and download operations affect cloud data.
The cited lines contain real Azure CLI commands, including upload and download. They are documented examples with placeholders and no hidden execution path, so the risk is operational rather than malicious.
Needs review findings (1)
REVIEW-001 Low
references/sdk/azure-storage-file-share-py.md:17-20references/sdk/azure-storage-file-share-ts.md:17-20
Connection String Guidance Needs Care
The file share references mention connection strings for simple setup. The same sections also recommend Entra ID or DefaultAzureCredential for production, so this is a minor documentation caution rather than a publication blocker.
Connection strings can contain secrets, but the guidance is framed as simple setup and balanced by production identity guidance. No secret values are embedded in the skill.

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
SKILL.md:12-28references/sdk-usage.md:20-25references/sdk/azure-storage-blob-java.md:8-18
Static Shell Execution Alerts Are Markdown Examples
Most external command alerts are backticked package names, CLI snippets, Maven dependency blocks, or SDK code fences. I did not find evidence that the skill executes shell commands by itself or interpolates untrusted input into a command runner.
The suspicious tokens appear inside markdown tables and fenced documentation samples. No script file, command execution API, or automation wrapper was found in the reviewed files.
Low
references/sdk-usage.md:36references/sdk-usage.md:47SKILL.md:78-80
Static Network Alerts Are Azure Placeholders and Documentation Links
The hardcoded URL findings point to Azure service endpoint templates and Microsoft Learn links. They do not send local files, credentials, environment variables, or user data to an unauthorized endpoint.
The URLs are Azure Storage placeholder endpoints or official Microsoft documentation links. A search found no suspicious external domains or webhook-style exfiltration destinations.
Low
SKILL.md:3SKILL.md:84-96references/sdk/azure-data-tables-java.md:30-35references/sdk/azure-data-tables-py.md:17-24
Weak Cryptography Alerts Are Substring False Positives
The weak cryptography detections cite lines about Azure Blob Storage descriptions, SDK reference text, and table partition key design. I did not find evidence of MD5, SHA-1, DES, RC4, or another weak algorithm being recommended or implemented.
The reviewed lines discuss storage services, SDK links, and partitioning guidance, not cryptographic algorithms. Targeted search for weak crypto terms returned no supporting evidence.
Low
references/sdk-usage.md:83-88
Dynamic Import Alert Is a Go Import Block
The dynamic import finding maps to a Go example import block in a fenced code sample. It is not a JavaScript dynamic import expression and does not load attacker-controlled code.
The code is inside a documented Go quick start and uses a normal import block. There is no dynamic module path or runtime code loading behavior.

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