SA-11 Developer testing and evaluation
What the standard requires
a. Develop and implement a plan for ongoing security and privacy control assessments; b. Perform [unit | integration | system | regression] testing/evaluation [frequency to conduct] at [depth and coverage]; c. Produce evidence of the execution of the assessment plan and the results of the testing and evaluation; d. Implement a verifiable flaw remediation process; and e. Correct flaws identified during testing and evaluation.
Quoted verbatim from NIST SP 800-53 Rev 5 (OSCAL catalog), which is in the public domain.
Maps to 1 control in 1 other framework
| Framework | Control |
|---|---|
| HITRUST CSF v11 | 10.e.06 System security testing (SAST/DAST) is performed during development and release |
Mappings are CMDash’s own, seeded with the product and shown on both frameworks they connect. In the product they mean evidence you attach here also counts against the controls listed above.
In CMDash this control is a row with an owner, a status, uploaded evidence kept with its full history, and an export an assessor can read.