Security Audit

Priority: P0 (CRITICAL)

1. Scan for Hardcoded Secrets

See implementation examples for secrets scanning commands.

2. Detect Data Leakage in Logs

Identify sensitive info printed to logs or stdout.

• Node/TS: grep -rE "console\.(log|error|warn)" . --include="*.ts" --include="*.js" | grep -iE "password|token|secret"
• Go: grep -rE "log\.(Print|Printf|Println|Fatal)" . --include="*.go" | grep -iE "password|token|secret"
• Dart/Flutter: grep -rE "print\(|debugPrint\(" . --include="*.dart" | grep -iE "password|token|secret"
• Java/Spring: grep -rE "log(ger)?\.(info|debug|warn|error)" . --include="*.java" | grep -iE "password|token|secret"

3. Map Injection Surfaces

Detect raw string concatenation in queries or system commands.

See implementation examples for injection surface detection.

4. Measure Auth Coverage vs Exposure

Compare total routes against protected endpoints.

• NestJS: total=$(grep -r "@(Get|Post|Put|Delete|Patch)" . | wc -l); guarded=$(grep -r "@(UseGuards|Auth)" . | wc -l)
• Spring: total=$(grep -r "@(GetMapping|PostMapping|PutMapping)" . | wc -l); guarded=$(grep -r "@(PreAuthorize|Secured)" . | wc -l)
• Go: total=$(grep -rE "(GET|POST|PUT|DELETE)" . | wc -l); guarded=$(grep -rE "(middleware|auth|jwt|guard)" . | wc -l)

5. Run Dependency CVE Scans

• Node: npm audit --audit-level=high
• Dart/Flutter: dart pub outdated --json
• Go: go list -m -u all | grep "\["
• Java: mvn dependency:list or ./gradlew dependencies
• Python: pip-audit
• Rust: cargo audit

6. Audit Infrastructure Hardening

See implementation examples for infrastructure hardening checks.

7. Detect Adversarial Entry Points (RCE/SSRF/Path Traversal)

Identify where user input reaches dangerous sinks without sanitization.

• Path Traversal: grep -rE "path\.join\(|os\.path\.join\(" . | grep -vE "path\.resolve|path\.normalize"
• SSRF: grep -rE "axios\.get\(|http\.Get\(|fetch\(" . | grep -vE "['\"]https?://"
• BOLA/IDOR: grep -rE "findById\(|findOne\(" . | grep -viE "tenant|owner|user_id"

Scoring Impact

CAUTION: P0 finding immediately caps Security score at 40/100.

Anti-Patterns

• No applying generic patterns over project-specific rules: Respect existing security constraints.
• No ignoring error handling or edge cases: Audit must cover boundary conditions.

References

• Vulnerability Remediation Protocols