What evidence do auditors commonly ask for on PR.IR-04 Adequate resource capacity to ensure availability is maintained?

Capacity forecasts with growth assumptions; Performance monitoring telemetry; Scaling automation configuration evidence; Reserved capacity and burst contract records; Availability SLO and error budget reports.

What is the most common gap auditors find on PR.IR-04?

Forecasts not refreshed with demand spikes

NIST CSF 2.0 · PR - Protect

`PR.IR-04` Adequate resource capacity to ensure availability is maintained

Adequate resource capacity to ensure availability is maintained. Control from NIST Cybersecurity Framework 2.0 framework, domain: PR - Protect.

Source: NIST CSF 2.0, PR.IR-04. 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.

artefacts

held by a system

at each review

easy

to go live

SIEM / log platform

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

Performance monitoring telemetry · SIEM / log platform
Scaling automation configuration evidence · Cloud console / configuration management
Reserved capacity and burst contract records · Vendor register / contract repository

periodic reviewEvidence produced at each review

Availability SLO and error budget reports · Document repository

governing documentDocuments that govern the control

Capacity forecasts with growth assumptions · Policy repository / GRC workspace

First move

Automate the pull from your SIEM / log platform. Retention and alert rules exported from the SIEM; review evidence is the closed-alert record with reviewer and time.

Common gaps auditors find

Forecasts not refreshed with demand spikes
Scaling automation untested under load
Reserved capacity contracts expired
SLOs lack error budget enforcement

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

PR.IR-03 Mechanisms are implemented to achieve resilience requirements in normal and adverse situations · PR.PS-01 Configuration management practices are established and applied