PR.PS-01 Configuration management practices are established and applied
Configuration management practices are established and applied. Control from NIST Cybersecurity Framework 2.0 framework, domain: PR - Protect.
5
artefacts
2
held by a system
1
at each review
moderate
to go live
SIEM / log platform
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Configuration drift monitoring telemetry · SIEM / log platform
- Configuration audit findings and remediation · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Approved change management records · Ticketing / ITSM
governing documentDocuments that govern the control
- Configuration management standards by platform · Policy repository / GRC workspace
- Hardening baselines and compliance reports · Policy repository / GRC workspace
First move
Start with the 2 of 5 artefacts that already live in a system (SIEM / log platform); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Baselines absent for cloud native services
- Drift monitoring noisy and ignored
- Hardening exceptions accumulate
- Audit findings linger past SLA
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 sheetPR.IR-04 Adequate resource capacity to ensure availability is maintained · PR.PS-02 Software is maintained, replaced, and removed commensurate with risk