DEV-04 Safety training and awareness programme regarding continuous software delivery and associated systems, components or tools
Run a recurring, audience-specific security training and awareness programme for internal and external staff on standards and methods of secure software development and delivery and on the tools involved, and refresh it
4
artefacts
0
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
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
- Attendance and completion records for the current training period · Source control / CI pipeline
governing documentDocuments that govern the control
- Curriculum differentiated for developer, tester and operations audiences · Policy repository / GRC workspace
- Proof the material was revised after a tooling or policy change · Policy repository / GRC workspace
- Coverage list confirming external development staff were included · Policy repository / GRC workspace
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
- Generic security awareness counted as secure software development training
- Contracted developers left out of the programme entirely
- Course content unchanged after the delivery toolchain was replaced
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 sheetDEV-03 Policies for changes to information systems · DEV-05 Risk assessment, categorisation and prioritisation of changes