SA-21 Developer Screening
Requires screening of the developer personnel who will have access to what matters, and verifies it.
3
artefacts
0
held by a system
2
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
- Verification evidence · Document repository
- Records of personnel covered · Document repository
governing documentDocuments that govern the control
- Screening requirements in contract by access level · HR system / LMS
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
- screening asserted by the developer and never verified
- subcontracted developers outside the requirement
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-20 Customized Development of Critical Components · SA-22 Unsupported System Components