6.2.2 Software development personnel working on bespoke and custom software are trained at least once every 12 months as follows: • On software security relevant to their job function and development languages. • Including secure
Software development personnel working on bespoke and custom software are trained at least once every 12 months as follows: • On software security relevant to their job function and development languages. • Including sec.
5
artefacts
0
held by a system
2
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
- Training records and attendance evidence for each developer working on bespoke and custom software, with dates · Source control / CI pipeline
- Evidence the training is refreshed within 12 months for each individual · Source control / CI pipeline
governing documentDocuments that govern the control
- Software development procedures defining the training required, its content and its at least annual frequency · Policy repository / GRC workspace
- Training content showing coverage of software security relevant to job function and development languages, secure design and secure coding techniques · Policy repository / GRC workspace
- Training content covering the use of tools for detecting vulnerabilities in software where such tools are used · 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 recorded as developer training, missing the language and job function specificity required
- Training completed at induction only, so the annual cycle lapses for existing staff
- Contract developers excluded from the training records despite working on bespoke software
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 sheet6.2.1 Bespoke and custom software are developed securely, as follows: • Based on industry standards and/or best practices for secure development. • In accordance with PCI DSS (for example, secure authentication and logging). • Incorporating · 6.2.3 Custom software reviewed prior to production