What evidence do auditors commonly ask for on I&S-02 Capacity and Resource Planning?

Documented business performance requirements or SLOs; Capacity plans and forecasts with review dates; Monitoring dashboards and alerts for utilisation, latency and saturation; Records of capacity actions taken when thresholds were reached.

What is the most common gap auditors find on I&S-02?

Capacity monitored but never compared with documented business requirements

CSA CCM v4.1 · I&S - Infrastructure Security

`I&S-02` Capacity and Resource Planning

Plan and track the availability, quality and capacity of resources so the system performs as the business requires.

Source: CSA CCM v4.1, I&S-02. 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 CSA CCM v4.1 in the compliance library.

Version 4.1 adds 11 controls (among them API security, log sanitisation and a service bill of materials) and renumbers several domains. CSA accepts v4.0.x during its transition; if your STAR assessment is still on v4.0.1, check the numbering against it.

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

Monitoring dashboards and alerts for utilisation, latency and saturation · SIEM / log platform
Records of capacity actions taken when thresholds were reached · Cloud console / configuration management

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

Documented business performance requirements or SLOs · Policy repository / GRC workspace
Capacity plans and forecasts with review dates · 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

Capacity monitored but never compared with documented business requirements
No forecast, so scaling is only reactive
Capacity alerts with no assigned responder

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

I&S-01 Infrastructure and Virtualization Security Policy and Procedures · I&S-03 Network Security