SA-16 Developer-Provided Training
Obtains the training needed to operate and secure delivered components correctly.
3
artefacts
0
held by a system
2
at each review
hard
to go live
HR system / LMS
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
- Delivery records · HR system / LMS
- Evidence knowledge transferred to the operating team · HR system / LMS
governing documentDocuments that govern the control
- Training requirements in contract · 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
- training delivered to a project team that then disbands
- no training obtained for security-relevant features
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-15 Development Process, Standards, and Tools · SA-17 Developer Security and Privacy Architecture and Design