Runs a whole-application security audit – threat-model-lite scoping, dependencies and supply chain, secrets, authentication and authorization, input handling, transport and headers, logging, and infrastructure config – and delivers a severity-ranked findings report with reproduction steps and concrete fixes.
Runs a whole-application security audit - threat-model-lite scoping, dependencies and supply chain, secrets, authentication and authorization, input handling, transport and headers, logging, and infrastructure config - and delivers a severity-ranked findings report with reproduction steps and concrete fixes. Use when someone asks "audit our app's security", "are we ready for a pentest or SOC 2", "what are our biggest security holes", or is preparing for launch, an enterprise security questionnaire, or taking over an inherited codebase. Do NOT use for hunting flaw classes in a single diff or PR - use secure-code-review instead; for prioritizing an existing scanner or pentest report, use vulnerability-triage; for design-stage analysis before code exists, use threat-model-stride.This is the skill's description: the text your AI reads to decide when the skill applies.
security-audit/SKILL.md
---
name: Security Audit
description: Runs a whole-application security audit - threat-model-lite scoping, dependencies and supply chain, secrets, authentication and authorization, input handling, transport and headers, logging, and infrastructure config - and delivers a severity-ranked findings report with reproduction steps and concrete fixes. Use when someone asks "audit our app's security", "are we ready for a pentest or SOC 2", "what are our biggest security holes", or is preparing for launch, an enterprise security questionnaire, or taking over an inherited codebase. Do NOT use for hunting flaw classes in a single diff or PR - use secure-code-review instead; for prioritizing an existing scanner or pentest report, use vulnerability-triage; for design-stage analysis before code exists, use threat-model-stride.
---
# Security Audit
A security audit asks, for a whole system: where would a motivated attacker get in first, and what would it cost? It is broader than code review - many real breaches start from a leaked key in git history, an admin panel without MFA, an unpatched edge dependency, or a public bucket, none of which appear in a diff. The costly mistake this skill prevents is auditing only the code you were shown, producing a long list of medium-severity lint, and missing the one system-level hole that is trivially exploitable from the internet.
## Operating procedure
Scope before scanning. A scan with no map of assets and entry points produces noise ranked by tool output instead of by attacker value.
### Step 1: Confirm authorization and rules of engagement
- Get written confirmation of what you may touch: repositories, environments, cloud accounts, live endpoints.
- Default to read-only analysis and non-destructive testing in non-production. No exploitation, fuzzing, or load against production without a named owner's approval.
- Record exclusions so the report does not imply coverage it lacks.
### Step 2: Threat-model-lite scoping (time-box to about 10% of the audit)
One page, not a full STRIDE exercise:
- Assets: what an attacker wants - customer PII, payment data, credentials, tenant data, admin capability, compute.
- Actors: anonymous internet user, authenticated user, user of another tenant, insider or contractor, compromised dependency.… load the full skill through Skill MeClick to play with sound.