SA-20 Customized Development of Critical Components
Considers building or customizing critical components where the market cannot supply them at the assurance level required.
3
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
- Decision records on custom development · Document repository
governing documentDocuments that govern the control
- Identification of components where market supply is inadequate · Document repository
- Assurance arrangements for custom components · 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
- critical dependency on a component nobody has assessed and no alternative considered
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-17 Developer Security and Privacy Architecture and Design · SA-21 Developer Screening