Versioned security assessment

Report ID: SA-99CE2266

6/30/2026, 8:20:34 AM

azure-diagnostics security assessment v2

Skill Security Certification Report

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

Highest confirmed finding severity

High

2 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 command-execution, network, environment-access, and weak-cryptography detections were reviewed in context. Most static hits are Markdown examples for Azure CLI, KQL, MCP tool calls, URLs, or app port configuration, so they are false positives for executable malware; however, the skill contains authority-style instruction text and operationally mutating Azure commands that create marketplace risk.

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

4 Files scanned · 393 Lines analyzed

4 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 2 evidence locations

Filesystem access

May read or write local files.

Not recorded by this audit

Env variables

May read values from the process environment.

Observed in 1 evidence location

External commands

May invoke commands or programs outside the Skill.

Observed in 7 evidence locations

Capability review items (2)
Medium
references/container-apps/README.md:26-29references/container-apps/README.md:49references/container-apps/README.md:98-104SKILL.md:114-119
Operational Cloud Commands Can Change Live Azure Resources
The command examples are documentation, not embedded executable code, but several remediation commands can change Container Apps settings, registry configuration, image tags, or running diagnostics if copied or executed by an agent. This is legitimate for an Azure diagnostics skill, yet it requires user confirmation and careful subscription scoping.
The affected lines are visible Azure CLI or Docker examples with real operational impact. Confidence is medium-high because the commands are examples, not code that runs automatically.
Low
references/container-apps/README.md:62references/container-apps/README.md:80-81references/kql-queries.md:64-65
Static Network And Environment Findings Are Documentation Context
The hardcoded URLs point to Microsoft Learn references and an example Container Apps health endpoint. The environment-access hit is a note to check whether the application reads process.env.PORT, not code that reads or exfiltrates environment variables.
The cited lines are Markdown examples or documentation links, with no executable source file and no outbound exfiltration logic. The evidence strongly supports a false positive for malware behavior.

Risk findings

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

Confirmed security concerns (2)

RISK-001 High
SKILL.md:11-13
Prompt Injection Attempt Detected
SKILL.md uses authority-style language: "AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE" and says the document is the official source. This can pressure an AI agent to treat marketplace content as higher priority than user or system instructions, even though the text is scoped to Azure troubleshooting and does not directly request bypassing security review.
The wording matches the prompt-injection warning for special authority and mandatory compliance. Confidence is not higher because the text stays within diagnostic guidance and does not tell the model to ignore prior instructions.
RISK-002 Medium
references/kql-queries.md:14-20references/kql-queries.md:24-31references/kql-queries.md:46-52SKILL.md:87-94
Diagnostic Queries May Surface Sensitive Operational Data
The KQL and log-query examples are appropriate for troubleshooting, but they can reveal exception messages, stack traces, request names, dependency targets, and recent logs. This is a moderate data-handling risk when used in production tenants.
The files explicitly query errors, stack traces, failed requests, dependency targets, and monitor logs. This is expected diagnostic behavior, but production log data can contain sensitive details.

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 (1)
Low
SKILL.md:3-5SKILL.md:45-50SKILL.md:78-81references/kql-queries.md:19references/kql-queries.md:30references/kql-queries.md:41
Weak Cryptography Detections Are False Positives
The weak-cryptography static findings occur on lines that contain front matter, normal diagnostic wording, or KQL query text. No evidence found of MD5, SHA-1, custom cryptography, password hashing, or encryption code in the reviewed files.
The reviewed context contains Azure diagnostic prose and KQL ordering clauses, not cryptographic implementation. Confidence is high because no matching crypto behavior is present at the reported lines.

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