Versioned security assessment

Report ID: SA-7F84FB0C

6/30/2026, 7:28:24 AM

azure-postgres security assessment v2

Skill Security Certification Report

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

Highest confirmed finding severity

Medium

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 analysis reported many command, filesystem, credential, and heuristic matches. Most matches in Markdown references are false positives from documentation links, inline command names, and PostgreSQL SECURITY LABEL syntax. The real risk is moderate: included shell scripts execute Azure CLI and psql administration commands, export database access tokens, and build SQL from caller-provided identifiers.

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,983 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.

Observed in 5 evidence locations

Network access

May connect to external services.

Observed in 3 evidence locations

Filesystem access

May read or write local files.

Observed in 3 evidence locations

Env variables

May read values from the process environment.

Observed in 5 evidence locations

External commands

May invoke commands or programs outside the Skill.

Observed in 5 evidence locations

Capability review items (1)
Medium
scripts/setup-user.sh:25-85scripts/setup-managed-identity.sh:26-102scripts/setup-group.sh:28-129scripts/migrate-to-entra.sh:21-72
Administrative scripts execute Azure and PostgreSQL commands
The skill includes Bash scripts that call Azure CLI and psql to inspect servers, create Entra-mapped roles, change server parameters, and grant database permissions. This is expected for the skill purpose, but it can change cloud and database authorization state when run by an operator with privileges. Static external command findings are true positives for the scripts and false positives for most Markdown examples.
The scripts directly invoke az and psql and perform role or permission administration. The behavior is legitimate for this skill, but the operational impact is clear.

Risk findings

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

Confirmed security concerns (2)

RISK-001 Medium
scripts/setup-user.sh:78-118scripts/setup-managed-identity.sh:92-138scripts/setup-group.sh:112-164
SQL constructed from caller-provided identifiers
Several scripts insert resource names, database names, user names, group names, or identity names into SQL statements. Shell arguments are generally quoted for command invocation, but SQL identifiers and string values are not consistently validated or escaped before execution as an Entra admin.
The affected lines show variables embedded in SQL passed to psql. Legitimate inputs are expected, but malicious or malformed identifiers could alter SQL behavior.
RISK-002 Medium
scripts/setup-user.sh:65scripts/setup-managed-identity.sh:79scripts/setup-group.sh:83scripts/migrate-to-entra.sh:49scripts/az-commands.sh:48
Database access tokens are stored in environment variables
The scripts acquire an Azure Database for PostgreSQL access token and place it in PGPASSWORD for psql. This is a standard psql pattern, but environment-based token handling can expose credentials to child processes or local diagnostics if the operator environment is compromised.
The token assignment is explicit and repeated. It is a common operational pattern, so the concern is exposure risk rather than malicious handling.

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
references/entra-rbac-overview.md:55-67references/sql-functions.md:47-59references/group-sync.md:25-57references/troubleshooting.md:26-60
Documentation patterns triggered false positives
Many static findings come from Markdown code spans, relative documentation links, command examples, and PostgreSQL SECURITY LABEL syntax. No evidence found that these reference files execute code, access local files, or target the Windows SAM database.
The cited content is Markdown documentation or SQL reference text. It explains Azure PostgreSQL operations and does not create an execution path by itself.

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