Skip to main content

Bound Workload Resource Consumption

CCC.K8S.CN13 · Resource

Bound resource requests, namespace consumption, and autoscaling so workloads cannot exhaust cluster or cloud capacity.

Related Capabilities

IDTitleDescription
CCC.Core.CP04Transaction Rate LimitsThe service can throttle, delay, or reject excess requests when transactions exceed a user-specified rate limit, and always provides industry-standard throughput up to that limit.
CCC.Core.CP16BudgetingThe service may be configured to take a user-specified action when a spending threshold is met or exceeded on a child or networked resource.
CCC.Core.CP19Child Resource ScalingThe service may be configured to scale child resources automatically or on-demand.

Related Threats

IDTitleDescription
CCC.Core.TH12Resource Constraints are ExhaustedExceeding the resource constraints through excessive consumption, resource-intensive operations, or lowering of rate-limit thresholds can impact the availability of elements such as memory, CPU, or storage. This may disrupt availability of the service or child resources by denying the associated functionality to users. If the impacted system is not designed to expect such a failure, the effect could also cascade to other services and resources.

Assessment Requirements

IDTextApplicability
CCC.K8S.CN13.AR01When a workload is admitted, every container MUST define approved CPU and memory requests and limits.tlp-clear, tlp-green, tlp-amber, tlp-red
CCC.K8S.CN13.AR02When a user workload namespace is active, ResourceQuota objects MUST bound its aggregate CPU, memory, storage, workload count, and externally exposed services.tlp-clear, tlp-green, tlp-amber, tlp-red
CCC.K8S.CN13.AR03When workload or node autoscaling is enabled, every autoscaler MUST define an approved maximum replica or capacity boundary.tlp-clear, tlp-green, tlp-amber, tlp-red

Guideline Mappings

FrameworkIDRemarks
NIST_800_53SC-5Denial-of-service Protection