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.
Source: NIST CSF 2.0, PR.PS-01. 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 NIST CSF 2.0 in the compliance library.
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
- Hardening baselines and compliance reports · Cloud console / configuration management
- Configuration drift monitoring telemetry · SIEM / log platform
- Approved change management records · Ticketing / ITSM
- Configuration audit findings and remediation · Cloud console / configuration management
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Configuration management standards by platform · Policy repository / GRC workspace
First move
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