OPS-01 Capacity Management - Planning
Follow an established procedure for planning personnel and IT capacity that forecasts future demand, identifies usage trends and prevents overload, with measures that keep agreed customer commitments intact when resource
4
artefacts
0
held by a system
1
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
- Minutes of the capacity review board approving hardware order lead times · Cloud console / configuration management
governing documentDocuments that govern the control
- Capacity forecast model with historical growth curves per resource pool · Policy repository / GRC workspace
- Planning procedure naming the forecast horizon and its review cycle · Policy repository / GRC workspace
- Staffing plan for operations and on call roles against projected workload · 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
- Forecasting covers compute only while storage, network and licences are ignored
- Planning addresses IT resources and never personnel availability
- Procurement lead times excluded, so a forecast cannot prevent an actual shortfall
- Dedicated single tenant components left outside the planning scope
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 sheetOIS-07 Application of the Risk Management Policy · OPS-02 Capacity Management - Monitoring