What this policy is
Defines how the organization forecasts resource demand (compute, storage, bandwidth, licence seats) and ensures capacity stays ahead of it.
Why every organization needs one
Capacity is a security control as much as an operations one: a saturated system fails open, drops audit logs, or rejects MFA prompts.
What a competent Capacity Management Policy typically contains
- Purpose and scope
- Roles and responsibilities
- Definitions
- Capacity-forecasting cadence
- Performance baselining
- Scale-up triggers
- Procurement lead-time assumptions
- Review cadence (typically annual) and version control
- Approval, sign-off and effective date
How iCompaas tracks this policy
The icompaas policy-doc producer manages this document through an 8-state lifecycle: draft → generated → internal_qa → customer_review → in_review → approved → signed (with rejected as a terminal side-state). The producer publishes a policy_doc_capacity_management_policy_signed compliance finding once at least one document of this kind reaches the signed state for the account being assessed; the finding then rolls up into every compliance framework that references this policy (see the table below).
Compliance frameworks that reference this policy
The icompaas compliance controls library links every policy document to the controls in each framework that require, evidence, or otherwise rely on it. Below: every control across every framework in the iCompaas catalogue that names this policy as part of its evidence base. Each control links to its own dedicated page with auditor-view content + implementation guidance.
| Framework | Control | Title | Component |
|---|---|---|---|
| ISO/IEC 27001:2022 | A.8.6 | Capacity management | Technological controls |
1 control across 1 framework reference this policy.
About this page
This article is part of the iCompaas Policy Documents library — one page per signed-document type the icompaas policy-doc producer tracks for customer accounts. The article is intentionally framework-agnostic: a customer signing a policy of this kind gets the same regulatory benefit across every framework that references it.