OPS-03 Capacity Management - Controlling of Resources
Give the cloud customer, so far as the service model permits, the means to monitor and steer the system resources allocated to it, so the customer can prevent resource contention and sustain adequate performance.
4
artefacts
0
held by a system
2
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
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Customer console screenshots of quota, scaling and resource limit settings · Cloud console / configuration management
- Change record for a resource adjustment initiated by a customer · Ticketing / ITSM
governing documentDocuments that govern the control
- Product documentation stating which resource controls exist for each service model · Policy repository / GRC workspace
- Sample tenant metric feed or API response exposing allocated resource usage · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Customer facing metrics show consumption but offer no lever to act on it
- Controls documented for the flagship service while older services expose nothing
- Quota changes possible only through a support ticket with no stated turnaround
- Contention effects hidden from the customer because only aggregate figures are shown
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 sheetOPS-02 Capacity Management - Monitoring · OPS-04 Protection Against Malware - Concept