SA-11 Developer Testing and Evaluation
Requires developers and suppliers to test what they deliver and to make the results available.
4
artefacts
0
held by a system
1
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Evidence of flaw remediation by the developer · Document repository
governing documentDocuments that govern the control
- Testing requirements in contract · Vendor register / contract repository
- Developer test plans and results received · Policy repository / GRC workspace
- Independent verification where warranted · Document repository
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- test results asserted in a summary letter with no detail
- flaws found by the developer never disclosed
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetSA-10 Developer Configuration Management · SA-15 Development Process, Standards, and Tools