EvidenceSheet
BSI C5 (121-criteria catalogue) · C5: Procurement, Development and Modification of Information Systems

DEV-04 Safety training and awareness programme regarding continuous software delivery and associated systems…

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 as policies, roles and tooling change.

Source: BSI C5 (121-criteria catalogue), DEV-04. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open BSI C5 (121-criteria catalogue) in the compliance library.

The edition of the catalogue is not stamped here; check the edition your attestation is issued against.

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. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

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 · HR system / LMS

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

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

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

DEV-03 Policies for changes to information systems · DEV-05 Risk assessment, categorisation and prioritisation of changes