CAIN-42 CAIN StudioCART · Module 5 of 5 · 12 min
From finding to fix to permanent regression
A red-team finding is done only when the fix is proven and the attack becomes a permanent test. The KEYSTONE red-team loop does exactly that: reproduce, propose a patch, prove the attack now fails and ordinary behaviour still works, sign the record.
Write findings with severity, reproduction, affected boundary, the evidence that it executed, and the expected safe outcome.
Never hide a miss. A suite that only shows passes trains everyone to stop looking.
Key points
- Reproduce → patch → prove → sign.
- Attack becomes a permanent regression test.
- Severity, repro, boundary, evidence, expected outcome.
- Never hide a miss.
In the CAIN-42 codebase
keystone/— KEYSTONE red-team loop (REDTEAM KEYSTONE)
Practice check
Practice 1 · choose one
A finding is closed when…
Practice 2 · true or false