EvidenceSheet

SEC11-BP01 Train for application security

Provide developers with secure coding training covering OWASP Top 10, AWS specific risks, IAM least privilege and use of managed security services.

4
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

  • Completion records by role · Identity provider / directory
  • Annual refresher schedule · HR system / LMS

governing documentDocuments that govern the control

  • Training curriculum · HR system / LMS
  • AWS specific modules · 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

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 sheet

SEC10-BP08 Establish a framework for learning from incidents · SEC11-BP02 Automate testing throughout the development and release lifecycle