GS-5 Define and implement security posture management strategy
Define and implement a security posture management strategy establishing policy, procedure and standards for security configuration management and vulnerability management.
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
- Posture management strategy and the policies under it · Policy repository / GRC workspace
- Defined baselines and the tooling that measures against them · Document repository
- Vulnerability management standard with remediation timeframes · Policy repository / GRC workspace
- Posture reporting to accountable owners · 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
- posture scores watched but no policy defines acceptable levels
- configuration and vulnerability management owned by different teams with no joint standard
- no remediation timeframes so findings age indefinitely
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-4 Define and implement network security strategy · GS-6 Define and implement identity and privileged access strategy