What evidence do auditors commonly ask for on CM-4 Impact Analyses?

Configuration management policy; Procedures addressing security impact analyses for changes to the system; Procedures addressing privacy impact analyses for changes to the system; Configuration management plan; Security impact analysis documentation; Privacy impact analysis documentation.

What is the most common gap auditors find on CM-4?

Changes are implemented without a documented analysis of security and privacy impact beforehand

NIST SP 800-53 Rev 5 · CM - Configuration Management

`CM-4` Impact Analyses

Analyze changes to the system to determine potential security and privacy impacts prior to change implementation.

Source: NIST SP 800-53 Rev 5, CM-4. 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 SP 800-53 Rev 5 in the compliance library.

Base controls and their enhancements. Which apply follows the baseline you are assessed against (for example FedRAMP Moderate or High, or the low, moderate and high baselines of SP 800-53B). Text in square brackets is a parameter your organisation sets.

artefacts

held by a system

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

Analysis tools and associated outputs · Cloud console / configuration management

periodic reviewEvidence produced at each review

Procedures addressing security impact analyses for changes to the system · Cloud console / configuration management
Procedures addressing privacy impact analyses for changes to the system · Cloud console / configuration management
Privacy impact assessment · Cloud console / configuration management
Test of Organizational processes for security impact analyses; organizational processes for privacy impact analyses · Cloud console / configuration management

governing documentDocuments that govern the control

Configuration management policy · Policy repository / GRC workspace
Configuration management plan · Policy repository / GRC workspace
Security impact analysis documentation · Policy repository / GRC workspace
Privacy impact analysis documentation · Policy repository / GRC workspace
Privacy risk assessment documentation, system design documentation · Policy repository / GRC workspace

First move

Mostly documents and reviews. Pull the 1 system-held artefact from your Cloud console / configuration management on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.

Common gaps auditors find

Changes are implemented without a documented analysis of security and privacy impact beforehand
Impact analyses are performed but done by staff without security or privacy expertise, and conclusions are unsupported

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

CM-3(8) Configuration Change Control | Prevent or Restrict Configuration Changes · CM-4(1) Impact Analyses | Separate Test Environments