SC-6 Resource Availability. Protect the availability of resources by allocating [organization-defined] by [organization-defined]
Resource Availability. Protect the availability of resources by allocating [organization-defined] by [organization-defined].
5
artefacts
2
held by a system
2
at each review
moderate
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- The defined allocation method, such as priority, quota or partition, and its configuration · Cloud console / configuration management
- Monitoring showing resource consumption against the allocations · SIEM / log platform
periodic reviewEvidence produced at each review
- Evidence the allocation protects availability of the priority workload when the resource is contended · Document repository
- Test or incident evidence showing the allocation held under load · Document repository
governing documentDocuments that govern the control
- The defined resources allocated for protection, such as processing, bandwidth, storage or connection capacity · Policy repository / GRC workspace
First move
Start with the 2 of 5 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Quotas configured but set above the resource actually available, so they never bind
- Priority defined for production workloads while shared infrastructure such as storage or the control plane has none
- Allocation never tested under contention, so its behaviour under real exhaustion is unknown
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 sheetSC-5 Denial-of-service protection · SC-7 Boundary protection