GS-10 Define and implement DevOps security strategy
Mandate security controls as part of the organisation's DevOps engineering and operating standard, defining security objectives, control requirements and tooling specifications.
4
artefacts
0
held by a system
0
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
none for this control
governing documentDocuments that govern the control
- DevOps engineering standard containing the mandated security controls · Policy repository / GRC workspace
- Defined security objectives and control requirements for pipelines · Policy repository / GRC workspace
- Approved tooling specification · Document repository
- Conformance reporting across delivery teams · Document repository
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
- security expectations communicated informally rather than in the standard
- standard published with no conformance measurement
- each team selecting its own security tooling with no baseline
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 sheetGS-9 Define and implement endpoint security strategy · IM-1 Use centralized identity and authentication system