Versioned security assessment

Report ID: SA-2549B90D

6/30/2026, 8:01:17 AM

entra-app-registration security assessment v2

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
entra-app-registration
Version
v2
Maintainer
microsoft
Source
github.com/microsoft/github-copilot-for-azure/tree/main/plugin/skills/entra-app-registration/
Coverage
16 Files scanned · 2,657 Lines analyzed
Policy version
Unavailable

Confirmed finding summary

No confirmed security findings

The completed audit recorded no confirmed security findings. This is not proof that the Skill has no side effects.

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 command, network, filesystem, weak-crypto, and prompt-related alerts, but review found they are primarily Markdown examples for Microsoft Entra, OAuth, Azure CLI, and SDK usage. The skill is publishable with warning because its examples can create credentials, grant consent, query directory data, or delete app registrations if run in a real tenant.

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

16 Files scanned · 2,657 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 92 evidence locations

Filesystem access

May read or write local files.

Observed in 8 evidence locations

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

Capability review items (4)
Medium
references/cli-commands.md:359-388references/cli-commands.md:399-408references/api-permissions.md:173-176
High-impact identity administration commands are documented
The skill includes Azure CLI examples for creating app registrations, granting admin consent, creating service principals, and deleting app registrations. These are legitimate examples, but they can materially change a tenant if executed without review.
The lines are explicit Azure CLI examples for app setup, admin consent, service principal creation, and deletion. The risk is operational misuse, not malicious skill behavior.
Medium
references/first-app-registration.md:159-167references/cli-commands.md:176-180references/console-app-example.md:190-205references/troubleshooting.md:181-188
Credential and token handling examples require careful substitution
The references show client secret placeholders, certificate upload commands, access token usage, and JWT debugging workflows. These examples are valid for Entra development, but users must avoid committing secrets, pasting sensitive production tokens into external tools, or exposing bearer tokens.
The reviewed lines directly discuss client secrets, certificate files, bearer-token API calls, and token decoding. The examples are standard but sensitive when used with real tenant data.
Low
SKILL.md:185-190references/oauth-flows.md:61-70references/console-app-example.md:197-199
Network URL findings point to Microsoft and example endpoints
Hardcoded URLs are documentation references, OAuth endpoints, Microsoft Graph endpoints, localhost redirects, or example application URLs. No evidence found of unauthorized network calls or data exfiltration logic.
The URLs reviewed are normal Microsoft identity, Graph API, localhost, or documentation targets. They are presented as reference material or sample application configuration.
Low
references/console-app-example.md:160-166references/oauth-flows.md:247-252
Prompt-injection scanner hits are OAuth prompt terminology
Prompt-related detections are ordinary authentication wording, such as MSAL prompt parameters and device-login instructions. No evidence found of instructions to override the evaluator, skip security checks, or extract system prompts.
Targeted search found no override, pre-approval, or evaluator-manipulation language. The flagged wording is tied to user authentication prompts.

Risk findings

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

No confirmed security findings were recorded for this completed audit.

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 (2)
Low
SKILL.md:130-143references/cli-commands.md:7-16references/api-permissions.md:144-148
Static command execution findings are Markdown examples
The numerous shell and backtick detections occur inside fenced documentation blocks or inline command references. No evidence found that the skill contains executable scripts that automatically run these commands.
The sampled detections are visibly Markdown documentation and command examples. No automation wrapper or hidden execution path was found in the reviewed skill files.
Low
SKILL.md:156-168references/BICEP-EXAMPLE.bicep:77-95references/oauth-flows.md:385-394
Weak cryptography detections are mostly identity terminology and GUID examples
Weak-crypto alerts are triggered by terms such as client secret, OAuth, token, ID, and placeholder GUID values. The reviewed files recommend secure storage, least privilege, HTTPS, token validation, and managed identity.
The sampled lines contain OAuth, permissions, token guidance, and placeholder identifiers, not weak algorithm use. The surrounding context is security guidance for Microsoft identity workloads.

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