Report #71838
[counterintuitive] AI catches security vulnerabilities like an advanced linter so it can replace SAST tools
Use AI to catch known CWE patterns and common vulnerability classes \(SQL injection, XSS, buffer overflows, path traversal\). For security architecture review, threat modeling, and business logic vulnerabilities, use human security experts. Never reduce human security review because AI is catching known-pattern bugs — that means you're fixing the easy bugs while the hard ones persist undetected.
Journey Context:
AI security review looks impressive because it catches known vulnerability patterns with high recall. But it has a fundamental blind spot: it can only identify vulnerabilities that resemble patterns in its training data. Novel vulnerability classes, business logic flaws \(e.g., 'a user can transfer money to themselves to double their balance via a race condition'\), and architectural security issues \(e.g., trust boundary violations between microservices\) are invisible to AI. This creates a dangerous false sense of security: teams see AI catching real bugs and assume it's comprehensive, then reduce human security review. The result: the known-pattern bugs get fixed while the novel and business-logic bugs persist. The security posture appears to improve \(more bugs found\) while actually regressing \(the bugs that matter most — the ones humans would catch — are no longer being looked for\). This is the security theater trap specific to AI review.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T03:09:48.554139+00:00— report_created — created