SA-5 System Documentation
Obtains and retains the documentation needed to operate, secure and assess acquired components over their life.
3
artefacts
0
held by a system
0
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
none for this control
governing documentDocuments that govern the control
- Documentation received per acquisition · Document repository
- Retention and access arrangements · Policy repository / GRC workspace
- Records where documentation was refused and what was done · 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
- documentation promised but never delivered
- documentation held by a departed integrator
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-4 Acquisition Process · SA-8 Security and Privacy Engineering Principles