Skill official security
Risk level
low
20/100

Azure Compliance ↗

Azure Compliance is an officially published skill from Microsoft. Anomity scores its risk at 20 out of 100 (low).

network:outbound credentials:access

Analysis summary

Azure Compliance is an officially published skill from Microsoft. Anomity scores its risk at 20 out of 100 (low).

Audits Azure compliance posture and monitors Key Vault expiry — surfacing misconfigured resources and secrets approaching their rotation date before they fail in production.

Declared capabilities are outbound network and credential access. Note the subtlety worth catching: monitoring Key Vault means the skill enumerates secret metadata — names, expiry, versions — not secret values. That distinction is the whole security argument for allowing it, and it is worth verifying in the skill's own implementation rather than assuming, because the two API calls sit next to each other.

Why this entry scored 20 out of 100

This profile starts at the catalog's neutral base of 50. Because the entry is officially published, trust adjusts the score by -40. Declared high-risk capabilities add +10 (capped at +30). It matches no dangerous capability combinations. The clamped result is 20, placing it in the low band.

See the full scoring formula →

Findings

  • Published by the vendor Trust offset
    Contribution to score: -40
  • 1 high-risk capability: credentials:access High
    Contribution to score: +10

Capabilities

Every capability the entry declares, with the security implication of each.

  • network:outbound Outbound network
    Can make outbound network requests. Required for hosted model providers and remote APIs; also the path for data exfiltration if combined with read access.
  • credentials:access Credentials access
    Reads provider API keys, OAuth tokens, or other secrets from the host keychain or environment.