Skip to main content

CAP-02: Resource Priority

CAP 8 — High Protect

Mechanisms exist to control resource utilization of Technology Assets, Applications and/or Services (TAAS) that are susceptible to Denial of Service (DoS) attacks to limit and prioritize the use of resources.

Control Question: Does the organization control resource utilization of Technology Assets, Applications and/or Services (TAAS) that are susceptible to Denial of Service (DoS) attacks to limit and prioritize the use of resources?

General (25)
Framework Mapping Values
AICPA TSC 2017:2022 (used for SOC 2) (source) A1.1
GovRAMP Low SC-05
GovRAMP Low+ SC-05
GovRAMP Moderate SC-05 SC-06
GovRAMP High SC-05 SC-06
MITRE ATT&CK 10 T1564.009
NIST 800-53 R4 SC-5 SC-5(1) SC-5(2) SC-6
NIST 800-53 R4 (low) SC-5
NIST 800-53 R4 (moderate) SC-5
NIST 800-53 R4 (high) SC-5
NIST 800-53 R5 (source) SC-5 SC-5(1) SC-5(2) SC-6
NIST 800-53B R5 (low) (source) SC-5
NIST 800-53B R5 (moderate) (source) SC-5
NIST 800-53B R5 (high) (source) SC-5
NIST 800-53 R5 (NOC) (source) SC-5(1) SC-5(2) SC-6
NIST 800-82 R3 LOW OT Overlay SC-5
NIST 800-82 R3 MODERATE OT Overlay SC-5
NIST 800-82 R3 HIGH OT Overlay SC-5
NIST 800-161 R1 SC-5 SC-5(2)
NIST 800-161 R1 Level 2 SC-5(2)
NIST CSF 2.0 (source) PR.IR-04
Shared Assessments SIG 2025 N.2
SCF CORE ESP Level 1 Foundational CAP-02
SCF CORE ESP Level 2 Critical Infrastructure CAP-02
SCF CORE ESP Level 3 Advanced Threats CAP-02
US (14)
APAC (1)
Framework Mapping Values
APAC Australia ISM June 2024 ISM-1579 ISM-1580 ISM-1581

Capability Maturity Model

Level 0 — Not Performed

There is no evidence of a capability to control resource utilization of Technology Assets, Applications and/or Services (TAAS) that are susceptible to Denial of Service (DoS) attacks to limit and prioritize the use of resources.

Level 1 — Performed Informally

C|P-CMM1 is N/A, since a structured process is required to control resource utilization of Technology Assets, Applications and/or Services (TAAS) that are susceptible to Denial of Service (DoS) attacks to limit and prioritize the use of resources.

Level 2 — Planned & Tracked

Capability & Performance Planning (CAP) are requirements-driven and governed at a local/regional level, but are not consistent across the organization. CMM Level 2 control maturity would reasonably expect all, or at least most, the following criteria to exist: o Business stakeholders to identify business-critical Technology Assets, Applications and/or Services (TAAS) and services. o Business stakeholders to identify single points of failure from a system/applications/services perspective. o Create and maintain infrastructure performance metrics to understand current resource needs. o Deploy preventative technologies to minimize the effect of Denial of Service (DoS) attacks against business-critical services.

  • Capacity management is decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
  • IT/cybersecurity personnel identify cybersecurity and data protection controls that are appropriate to address applicable statutory, regulatory and contractual requirements for capability management.
  • IT personnel work with:
  • IT infrastructure personnel:
Level 3 — Well Defined

Capability & Performance Planning (CAP) efforts are standardized across the organization and centrally managed, where technically feasible, to ensure consistency. CMM Level 3 control maturity would reasonably expect all, or at least most, the following criteria to exist: o Create an annual infrastructure growth plan with input from both technology and business stakeholders. o Create and maintain infrastructure performance metrics to understand current resource needs. o Produce a capacity plan that covers current use, forecasted needs and support costs for new Technology Assets, Applications and/or Services (TAAS), applications and services.

  • The Chief Information Security Officer (CISO), or similar function with technical competence to address cybersecurity concerns, analyzes the organization's business strategy to provide guidance for capacity and performance planning practices.
  • The CISO, or similar function, develops a security-focused Concept of Operations (CONOPS) that documents management, operational and technical measures to apply defense-in-depth techniques across the organization. This CONOPS for capacity and performance planning may be incorporated as part of a broader operational plan for the cybersecurity and data privacy program.
  • A Governance, Risk & Compliance (GRC) team, or similar function, provides governance oversight for the implementation of applicable statutory, regulatory and contractual cybersecurity and data protection controls to protect the confidentiality, integrity, availability and safety of the organization's applications, Technology Assets, Applications and/or Services (TAAS), services and data.
  • A steering committee is formally established to provide executive oversight of the cybersecurity and data privacy program and establishes a clear and authoritative accountability structure for capacity and performance planning operations.
  • IT personnel work with business stakeholders to identify business-critical Technology Assets, Applications and/or Services (TAAS) and services, as part of the organization's IT Asset Management (ITAM) program.
  • Automated tools continuously monitor the operating state and health status of Technology Assets, Applications and/or Services (TAAS)/applications/services.
  • Business stakeholders conduct a Business Impact Analysis (BIA) to determine acceptable downtime constraints and any dependencies between applications or Technology Assets, Applications and/or Services (TAAS), to objectively determine the criticality of Technology Assets, Applications and/or Services (TAAS), applications or services, as well as the order is which Technology Assets, Applications and/or Services (TAAS) need to be restored.
  • Demand is managed for computing resources based on BIA-defined prioritization.
  • Based on BIA results, IT infrastructure personnel deploy preventative technologies to minimize the effect of Denial of Service (DoS) attacks.
  • IT architects identify appropriate solutions to make sure service levels can be met.
  • IT infrastructure personnel:
  • Automated tools continuously monitor the operating state and health status of Technology Assets, Applications and/or Services (TAAS), applications and services to expand the availability of resources, as demand conditions change.
  • IT personnel work with business stakeholders to identify single points of failure from a system/applications/services perspective.
Level 4 — Quantitatively Controlled

See C|P-CMM3. There are no defined C|P-CMM4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to control resource utilization of Technology Assets, Applications and/or Services (TAAS) that are susceptible to Denial of Service (DoS) attacks to limit and prioritize the use of resources.

Level 5 — Continuously Improving

See C|P-CMM4. There are no defined C|P-CMM5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to control resource utilization of Technology Assets, Applications and/or Services (TAAS) that are susceptible to Denial of Service (DoS) attacks to limit and prioritize the use of resources.

Assessment Objectives

  1. CAP-02_A01 types of denial-of-service events to be protected against or limited are defined.
  2. CAP-02_A02 controls by type of denial-of-service event are employed to achieve the denial-of-service protection objective.
  3. CAP-02_A03 resource prioritization is designed to limit negative effects of denial-of-service events.
  4. CAP-02_A04 controls to achieve the denial-of-service objective by type of denial-of-service event are defined.
  5. CAP-02_A05 the effects of types of denial-of-service events are organizationally-defined.

Evidence Requirements

E-CAP-02 Resource Prioritization

Documented evidence of resource prioritization to maintain business performance requirements for critical systems, applications and/or services.

Capacity Management

Technology Recommendations

The Secure Controls Framework (SCF) is maintained by SCF Council. Use of SCF content is subject to the SCF Terms & Conditions.

Manage this control in SCF Connect

Track implementation status, collect evidence, and map controls to your compliance frameworks automatically.