Cookies on this site. Help us understand what works and improve your experience. Essential cookies keep the site working. With your permission, our visit insights and Google Analytics measure usage, and Google Ads measures advertising. Optional cookies are not required to use the free kit. Change your choice anytime in Cookie settings. Privacy policyCookie policy
Monitor and adjust capacity (compute, storage, network, people) so services stay available.
Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.
Why this control matters
Capacity management fails when teams react only after outages, slowdowns, or storage exhaustion instead of tracking trends and trigger points. Guidance should connect service demand, business growth, and technical bottlenecks to accountable owners who can adjust compute, storage, network, and staffing before availability drops. It should also show what records prove planning, review, and remediation decisions were made.
Common auditor findings to check for
Potential gaps to test in your own environment, not a claim about observed audit frequency.
Monitoring exists for servers or cloud usage, but thresholds are not linked to service owners, so alerts are seen without clear decisions or follow-up actions.
Forecasts ignore business events such as product launches, onboarding waves, or seasonal peaks, leading to undersized resources for known demand increases.
Capacity issues recur because post-incident actions stop at immediate scaling and do not capture trend analysis, budget approval, or long-term architectural changes.
How you can implement it
Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.
Name a capacity owner for each critical service, usually the service manager or operations lead, and require periodic review of compute, storage, network, and queue depth indicators. Use dashboards with threshold alerts, growth trend lines, and forecast assumptions so the review is decision-oriented rather than purely observational.
Link capacity planning to business inputs such as customer growth, new releases, supplier dependencies, and people capacity for support and engineering. Capture the assumptions behind each forecast, the planned headroom target, and the trigger points that require scaling, redistribution, or deferral of work.
Define escalation actions for pressure points: increase limits, rebalance workloads, archive unused data, upgrade bandwidth, or add support shifts where service response is staff-limited. Record who approved the action, what was changed, and the expected review date after implementation.
Retain evidence of recurring review meetings, cloud billing trends, utilization reports, and capacity exceptions. Where tools automate scaling, keep the rule set, test results, and any manual override decisions so the organization can explain why a service remained stable during demand spikes.
What an auditor will ask to see
Monthly capacity report with utilization trends, forecast assumptions, and named action owners for each critical service.
Alert tickets or change records showing threshold breaches, scaling decisions, and confirmation that service levels returned to target.
Meeting minutes or review notes with business demand inputs, approved headroom targets, and follow-up dates for unresolved constraints.
Baseline documents in the kit
These free kit documents help you document or evidence A.8.6. Each one is tailored to your organization when you build your kit.
Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.
For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.
Get these documents tailored to your organization
109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.