Auditing Security
Overview
Comprehensive security analysis to identify vulnerabilities, assess risk, and provide remediation guidance aligned with industry standards (OWASP Top 10, CVSS scoring).
Inputs:
- Codebase to audit
docs/system-design.md - Architecture context
docs/api-contracts.yaml - API specifications
docs/feature-spec/F-##-*.md - Feature implementations
Outputs:
- Security findings organized by severity (CRITICAL, HIGH, MEDIUM, LOW)
- CVSS scores and OWASP Top 10 mapping
- Exploit scenarios and remediation code
- Risk-prioritized remediation plan
Quick Start
Ask for security audit with context:
- What to audit? Feature, component, or full application
- Concerns? Injection, auth bypass, data leaks, access control, API security
- Sensitive data? PII, credentials, financial data, health info, business secrets
- Existing security? JWT/sessions, RBAC/ABAC, TLS, input validation, headers, rate limiting
Scope Discovery
Q1: Audit Scope
- Specific feature or component
- Entire application (full security audit)
- Known vulnerability investigation
- Compliance check (OWASP Top 10, PCI-DSS, GDPR)
- Code review for security issues
- Infrastructure and configuration
Q2: Threat Model
- Data breaches and leaks
- Authentication bypass
- Injection attacks (SQL, XSS, command)
- Access control failures
- API security
- Infrastructure vulnerabilities
- Dependency vulnerabilities
Q3: Sensitivity Level
- Personal identifiable information (PII)
- Authentication credentials
- Financial data (payment info, transactions)
- Health information (HIPAA)
- Business secrets or proprietary data
- User-generated content
Q4: Existing Security (optional)
- Authentication method (JWT, sessions, OAuth)
- Authorization model (RBAC, ABAC)
- Encryption (TLS, at-rest encryption)
- Input validation and sanitization
- Security headers (CSP, HSTS, etc.)
- Rate limiting and throttling
- Logging and monitoring
Security Review Strategy
Sequential Review (Targeted audits)
When to use: Small codebase, single vulnerability investigation, specific attack vector, <5 files
Review vulnerabilities one area at a time using direct tools:
Injection Vulnerabilities:
- SQL injection: String concatenation in queries (
db.query("SELECT * FROM users WHERE id = '" + id + "'"))
- XSS:
dangerouslySetInnerHTML, unsanitized HTML (.innerHTML = userInput)
- Command injection: Shell command construction (
exec('rm ' + filename))
- NoSQL injection, LDAP injection
- Search for:
db.query(, eval(, exec(, .innerHTML
Authentication/Authorization:
- Endpoints without auth checks
- Weak password requirements
- Missing rate limiting on auth endpoints
- Session management issues
- Broken access control, privilege escalation
- Search for: route handlers, auth middleware, permission checks
Sensitive Data Exposure:
- Hardcoded secrets: API keys, passwords, tokens
- Excessive data in API responses
- Logging sensitive information
- Unencrypted transmission
- Insecure storage
- Search for:
apiKey, password, secret, token assignments
Security Misconfiguration:
- Missing security headers (CSP, HSTS, X-Frame-Options)
- CORS misconfiguration
- Verbose error messages exposing internals
- Default credentials
- Debug mode in production
- Search for: server config, error handlers, CORS setup
Dependency Vulnerabilities:
- Run
npm audit or equivalent
- Check for outdated packages with CVEs
- Unnecessary dependencies, supply chain risks
Parallel Scanning (Comprehensive audits)
When to use: Entire application, multiple OWASP categories, >1000 lines, multiple attack surfaces
Agent 1: Injection (OWASP A03)
SQL, XSS, command, NoSQL, LDAP injection vulnerabilities
Agent 2: Authentication/Authorization (OWASP A01, A07)
Missing auth, weak passwords, broken sessions, access control failures, privilege escalation
Agent 3: Data Exposure (OWASP A02)
Hardcoded secrets, excessive API responses, logging sensitive data, unencrypted transmission, insecure storage
Agent 4: Configuration (OWASP A05)
Missing security headers, CORS misconfiguration, verbose errors, default credentials, unnecessary services
Agent 5: Dependencies (OWASP A06)
Vulnerable packages, outdated versions, supply chain risks
Finding Documentation Format
For each vulnerability:
### [SEVERITY] Issue Name
**CVSS Score:** X.X | **Category:** OWASP A##:YEAR | **Location:** `src/path/file.js:123`
**Vulnerable Code:**
[Code snippet]
**Exploit Scenario:**
[Concrete example of how to abuse this]
**Impact:**
[What attacker can achieve: data access, auth bypass, system compromise, etc.]
**Fix:**
[Secure replacement code]
**References:**
- OWASP: [link]
- CWE-##: [link]
Severity Mapping:
- 🔴 CRITICAL (CVSS 9.0-10.0): Fix immediately, authentication bypass, full database access, RCE
- 🔴 HIGH (CVSS 7.0-8.9): Fix within days, data exfiltration, significant privilege escalation
- 🟡 MEDIUM (CVSS 4.0-6.9): Fix within weeks, partial data access, limited auth bypass
- 🟢 LOW (CVSS 0.1-3.9): Fix within months, information disclosure, minor config issues
Security Audit Report
Generate comprehensive report with:
# Security Audit Report: [System Name]
## Executive Summary
**Overall Security Posture:** [CRITICAL / POOR / FAIR / GOOD / EXCELLENT]
**Vulnerability Summary:**
- CRITICAL: [X] (CVSS 9.0-10.0)
- HIGH: [Y] (CVSS 7.0-8.9)
- MEDIUM: [Z] (CVSS 4.0-6.9)
- LOW: [N] (CVSS 0.1-3.9)
**Immediate Actions Required:**
1. [Most critical issue]
2. [Second priority]
## OWASP Top 10 Assessment
| Category | Status | Findings | Priority |
|----------|--------|----------|----------|
| A01: Broken Access Control | ✅/⚠️/❌ | [count] | - |
| A02: Cryptographic Failures | ✅/⚠️/❌ | [count] | - |
| A03: Injection | ✅/⚠️/❌ | [count] | - |
| [Continue for all 10] | | | |
## Findings by Severity
[CRITICAL vulnerabilities]
[HIGH vulnerabilities]
[MEDIUM vulnerabilities]
[LOW vulnerabilities]
## Remediation Plan
### Immediate (24 hours)
[Critical and high-severity fixes]
### Short-term (1 week)
[Medium-severity fixes]
### Medium-term (1 month)
[Low-severity fixes, hardening]
## Verification Checklist
- [ ] Re-run security scans on fixed code
- [ ] Verify each vulnerability is closed
- [ ] Run `npm audit` on dependencies
- [ ] Test fixes don't break functionality
- [ ] Add security regression tests
Security Check Reference
Injection:
- SQL queries use parameterization (prepared statements, ORM)
- HTML output is sanitized (DOMPurify, escaped)
- No dynamic command execution (
exec, spawn with user input)
- No
eval() or similar code execution
Authentication:
- Password requirements adequate (12+ chars, complexity)
- All sensitive endpoints have auth checks
- Session management secure (httpOnly, secure cookies)
- Rate limiting on auth endpoints (5 attempts/min max)
- Credentials hashed with bcrypt/argon2, not plaintext
Data Exposure:
- No hardcoded secrets (use environment variables)
- API responses don't leak unnecessary data
- Sensitive data not in logs
- HTTPS/TLS enforced everywhere
- Sensitive data encrypted at rest (AES-256)
Configuration:
- Security headers present (CSP, HSTS, X-Frame-Options, X-Content-Type-Options)
- CORS properly configured (not
*, validate origins)
- Error messages don't expose internals
- No default credentials
- Debug mode disabled in production
Dependencies:
- No known vulnerabilities (run
npm audit)
- Packages up to date
- No unnecessary dependencies
Remediation Workflow
- Fix each vulnerability following documented code examples
- Verify immediately - re-run security scans, test functionality
- Document resolution - mark findings as fixed with verification method
- Run dependency audit -
npm audit, update packages
- Test regression - ensure fixes don't break features
- Update docs - document security measures implemented
Examples
Example 1: SQL Injection Finding
### [CRITICAL] SQL Injection in User Login
**CVSS Score:** 9.8 | **Category:** OWASP A03:2021 | **Location:** `src/auth/login.js:45`
**Vulnerable Code:**
const query = `SELECT * FROM users WHERE email = '${email}'`;
const user = await db.query(query);
**Exploit Scenario:**
Attacker sends: email = "admin' OR '1'='1"
→ Returns all users, bypasses authentication, gains admin access
**Impact:**
- Complete authentication bypass
- Full database access
- Data exfiltration and manipulation
**Fix:**
const query = 'SELECT * FROM users WHERE email = ?';
const user = await db.query(query, [email]);
Example 2: Hardcoded Secrets Finding
### [CRITICAL] Hardcoded API Key
**CVSS Score:** 9.6 | **Category:** OWASP A02:2021 | **Location:** `src/config.js:12`
**Vulnerable Code:**
const apiKey = "sk-1234567890abcdef";
**Impact:**
- Unauthorized API access
- Billing liability
- Data access under victim's account
**Fix:**
const apiKey = process.env.API_KEY;
// Store in .env: API_KEY=sk-1234567890abcdef
1---2name: auditing-security3description: Identify and remediate vulnerabilities through systematic code analysis. Use when performing security assessments, pre-deployment reviews, compliance validation (OWASP, PCI-DSS, GDPR), investigating known vulnerabilities, or post-incident analysis.4metadata:5 source: https://skillmd.com/skills/captaincrouton89/auditing-security6---78# Auditing Security910## Overview1112Comprehensive security analysis to identify vulnerabilities, assess risk, and provide remediation guidance aligned with industry standards (OWASP Top 10, CVSS scoring).1314**Inputs:**15- Codebase to audit16- `docs/system-design.md` - Architecture context17- `docs/api-contracts.yaml` - API specifications18- `docs/feature-spec/F-##-*.md` - Feature implementations1920**Outputs:**21- Security findings organized by severity (CRITICAL, HIGH, MEDIUM, LOW)22- CVSS scores and OWASP Top 10 mapping23- Exploit scenarios and remediation code24- Risk-prioritized remediation plan2526## Quick Start2728Ask for security audit with context:29- **What to audit?** Feature, component, or full application30- **Concerns?** Injection, auth bypass, data leaks, access control, API security31- **Sensitive data?** PII, credentials, financial data, health info, business secrets32- **Existing security?** JWT/sessions, RBAC/ABAC, TLS, input validation, headers, rate limiting3334## Scope Discovery3536**Q1: Audit Scope**37- Specific feature or component38- Entire application (full security audit)39- Known vulnerability investigation40- Compliance check (OWASP Top 10, PCI-DSS, GDPR)41- Code review for security issues42- Infrastructure and configuration4344**Q2: Threat Model**45- Data breaches and leaks46- Authentication bypass47- Injection attacks (SQL, XSS, command)48- Access control failures49- API security50- Infrastructure vulnerabilities51- Dependency vulnerabilities5253**Q3: Sensitivity Level**54- Personal identifiable information (PII)55- Authentication credentials56- Financial data (payment info, transactions)57- Health information (HIPAA)58- Business secrets or proprietary data59- User-generated content6061**Q4: Existing Security** (optional)62- Authentication method (JWT, sessions, OAuth)63- Authorization model (RBAC, ABAC)64- Encryption (TLS, at-rest encryption)65- Input validation and sanitization66- Security headers (CSP, HSTS, etc.)67- Rate limiting and throttling68- Logging and monitoring6970## Security Review Strategy7172### Sequential Review (Targeted audits)73**When to use:** Small codebase, single vulnerability investigation, specific attack vector, <5 files7475Review vulnerabilities one area at a time using direct tools:7677**Injection Vulnerabilities:**78- SQL injection: String concatenation in queries (`db.query("SELECT * FROM users WHERE id = '" + id + "'")`)79- XSS: `dangerouslySetInnerHTML`, unsanitized HTML (`.innerHTML = userInput`)80- Command injection: Shell command construction (`exec('rm ' + filename)`)81- NoSQL injection, LDAP injection82- Search for: `db.query(`, `eval(`, `exec(`, `.innerHTML`8384**Authentication/Authorization:**85- Endpoints without auth checks86- Weak password requirements87- Missing rate limiting on auth endpoints88- Session management issues89- Broken access control, privilege escalation90- Search for: route handlers, auth middleware, permission checks9192**Sensitive Data Exposure:**93- Hardcoded secrets: API keys, passwords, tokens94- Excessive data in API responses95- Logging sensitive information96- Unencrypted transmission97- Insecure storage98- Search for: `apiKey`, `password`, `secret`, `token` assignments99100**Security Misconfiguration:**101- Missing security headers (CSP, HSTS, X-Frame-Options)102- CORS misconfiguration103- Verbose error messages exposing internals104- Default credentials105- Debug mode in production106- Search for: server config, error handlers, CORS setup107108**Dependency Vulnerabilities:**109- Run `npm audit` or equivalent110- Check for outdated packages with CVEs111- Unnecessary dependencies, supply chain risks112113### Parallel Scanning (Comprehensive audits)114**When to use:** Entire application, multiple OWASP categories, >1000 lines, multiple attack surfaces115116**Agent 1: Injection (OWASP A03)**117SQL, XSS, command, NoSQL, LDAP injection vulnerabilities118119**Agent 2: Authentication/Authorization (OWASP A01, A07)**120Missing auth, weak passwords, broken sessions, access control failures, privilege escalation121122**Agent 3: Data Exposure (OWASP A02)**123Hardcoded secrets, excessive API responses, logging sensitive data, unencrypted transmission, insecure storage124125**Agent 4: Configuration (OWASP A05)**126Missing security headers, CORS misconfiguration, verbose errors, default credentials, unnecessary services127128**Agent 5: Dependencies (OWASP A06)**129Vulnerable packages, outdated versions, supply chain risks130131## Finding Documentation Format132133**For each vulnerability:**134135```markdown136### [SEVERITY] Issue Name137**CVSS Score:** X.X | **Category:** OWASP A##:YEAR | **Location:** `src/path/file.js:123`138139**Vulnerable Code:**140[Code snippet]141142**Exploit Scenario:**143[Concrete example of how to abuse this]144145**Impact:**146[What attacker can achieve: data access, auth bypass, system compromise, etc.]147148**Fix:**149[Secure replacement code]150151**References:**152- OWASP: [link]153- CWE-##: [link]154```155156**Severity Mapping:**157- 🔴 CRITICAL (CVSS 9.0-10.0): Fix immediately, authentication bypass, full database access, RCE158- 🔴 HIGH (CVSS 7.0-8.9): Fix within days, data exfiltration, significant privilege escalation159- 🟡 MEDIUM (CVSS 4.0-6.9): Fix within weeks, partial data access, limited auth bypass160- 🟢 LOW (CVSS 0.1-3.9): Fix within months, information disclosure, minor config issues161162## Security Audit Report163164Generate comprehensive report with:165166```markdown167# Security Audit Report: [System Name]168169## Executive Summary170**Overall Security Posture:** [CRITICAL / POOR / FAIR / GOOD / EXCELLENT]171172**Vulnerability Summary:**173- CRITICAL: [X] (CVSS 9.0-10.0)174- HIGH: [Y] (CVSS 7.0-8.9)175- MEDIUM: [Z] (CVSS 4.0-6.9)176- LOW: [N] (CVSS 0.1-3.9)177178**Immediate Actions Required:**1791. [Most critical issue]1802. [Second priority]181182## OWASP Top 10 Assessment183| Category | Status | Findings | Priority |184|----------|--------|----------|----------|185| A01: Broken Access Control | ✅/⚠️/❌ | [count] | - |186| A02: Cryptographic Failures | ✅/⚠️/❌ | [count] | - |187| A03: Injection | ✅/⚠️/❌ | [count] | - |188| [Continue for all 10] | | | |189190## Findings by Severity191[CRITICAL vulnerabilities]192[HIGH vulnerabilities]193[MEDIUM vulnerabilities]194[LOW vulnerabilities]195196## Remediation Plan197### Immediate (24 hours)198[Critical and high-severity fixes]199200### Short-term (1 week)201[Medium-severity fixes]202203### Medium-term (1 month)204[Low-severity fixes, hardening]205206## Verification Checklist207- [ ] Re-run security scans on fixed code208- [ ] Verify each vulnerability is closed209- [ ] Run `npm audit` on dependencies210- [ ] Test fixes don't break functionality211- [ ] Add security regression tests212```213214## Security Check Reference215216**Injection:**217- SQL queries use parameterization (prepared statements, ORM)218- HTML output is sanitized (DOMPurify, escaped)219- No dynamic command execution (`exec`, `spawn` with user input)220- No `eval()` or similar code execution221222**Authentication:**223- Password requirements adequate (12+ chars, complexity)224- All sensitive endpoints have auth checks225- Session management secure (httpOnly, secure cookies)226- Rate limiting on auth endpoints (5 attempts/min max)227- Credentials hashed with bcrypt/argon2, not plaintext228229**Data Exposure:**230- No hardcoded secrets (use environment variables)231- API responses don't leak unnecessary data232- Sensitive data not in logs233- HTTPS/TLS enforced everywhere234- Sensitive data encrypted at rest (AES-256)235236**Configuration:**237- Security headers present (CSP, HSTS, X-Frame-Options, X-Content-Type-Options)238- CORS properly configured (not `*`, validate origins)239- Error messages don't expose internals240- No default credentials241- Debug mode disabled in production242243**Dependencies:**244- No known vulnerabilities (run `npm audit`)245- Packages up to date246- No unnecessary dependencies247248## Remediation Workflow2492501. **Fix each vulnerability** following documented code examples2512. **Verify immediately** - re-run security scans, test functionality2523. **Document resolution** - mark findings as fixed with verification method2534. **Run dependency audit** - `npm audit`, update packages2545. **Test regression** - ensure fixes don't break features2556. **Update docs** - document security measures implemented256257## Examples258259**Example 1: SQL Injection Finding**260```markdown261### [CRITICAL] SQL Injection in User Login262**CVSS Score:** 9.8 | **Category:** OWASP A03:2021 | **Location:** `src/auth/login.js:45`263264**Vulnerable Code:**265const query = `SELECT * FROM users WHERE email = '${email}'`;266const user = await db.query(query);267268**Exploit Scenario:**269Attacker sends: email = "admin' OR '1'='1"270→ Returns all users, bypasses authentication, gains admin access271272**Impact:**273- Complete authentication bypass274- Full database access275- Data exfiltration and manipulation276277**Fix:**278const query = 'SELECT * FROM users WHERE email = ?';279const user = await db.query(query, [email]);280```281282**Example 2: Hardcoded Secrets Finding**283```markdown284### [CRITICAL] Hardcoded API Key285**CVSS Score:** 9.6 | **Category:** OWASP A02:2021 | **Location:** `src/config.js:12`286287**Vulnerable Code:**288const apiKey = "sk-1234567890abcdef";289290**Impact:**291- Unauthorized API access292- Billing liability293- Data access under victim's account294295**Fix:**296const apiKey = process.env.API_KEY;297// Store in .env: API_KEY=sk-1234567890abcdef298```