+Capacity Planning

Capacity Planning

Description

Mechanisms exist to conduct capacity planning so that necessary capacity for information processing, telecommunications and environmental support will exist during contingency operations.

Possible Solutions & Considerations

Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2

∙ Monitor system resource usage periodically

Small Business (10-49 staff) / BLS Firm Size Classes 3-4

∙ Capacity monitoring for critical systems
∙ Resource usage baseline

Medium Business (50-249 staff) / BLS Firm Size Classes 5-6

∙ Capacity planning process
∙ Performance monitoring tools

Large Business (250-999 staff) / BLS Firm Size Classes 7-8

∙ Enterprise capacity management program
∙ Performance monitoring platform (e.g., Dynatrace, New Relic)

Enterprise (> 1,000 staff) / BLS Firm Size Class 9

∙ Enterprise capacity management platform
∙ APM tools (e.g., Dynatrace, Datadog)
∙ Automated scaling

SCR-CMM

Level 0 Not Performed

Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.

Level 1 Performed Informally

SCR-CMM Level 1 criteria definitions are not available for this control:
▪ A reasonable person would conclude this control requires a structured process.
▪ At this level of maturity, the "ad hoc" nature of performing a capability informally would indicate the intent of the control is not met due to a lack of consistency and formality.

Level 2 Planned Tracked

Capability & Performance Planning (CAP) capabilities are requirements-driven, but are not standardized across the entity (e.g., local/regional level consistency). Capability criteria associated with this control reasonably expect the following criteria to exist:
▪ Policies and standards associated with CAP domain capabilities are formally documented and centrally-managed by the entity.
▪ Standardized Operating Procedures (SOP) associated with CAP domain capabilities are documented and maintained by process owners.
▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with CAP domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Capability management-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines).
▪ Capability management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel.
▪ IT personnel work with business stakeholders and process owners to create and maintain infrastructure performance metrics to understand current resource needs.

Level 3 Well Defined

Capability & Performance Planning (CAP) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist:
▪ Policies and standards associated with CAP domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function.
▪ Standardized Operating Procedures (SOP) associated with CAP domain capabilities are well-documented and kept current by process owners.
▪ A Business Continuity & Disaster Recovery (BC/DR) team, or similar function, is appropriately staffed and supported to implement and maintain BCD domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of BC/DR operations (e.g., BC/DR planning software, Disaster Recovery as a Service (DRaaS), Orchestration and Automation Tools).
▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with CAP domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls).
▪ An implemented and operational capability exists to conduct capacity planning so that necessary capacity for information processing, telecommunications and environmental support will exist during contingency operations.

Level 4 Quantitatively Controlled

Capability & Performance Planning (CAP) capabilities, in addition to being standardized across the entity and centrally managed to ensure consistency across Technology Assets, Applications, Services and/or Data (TAASD), efforts are metrics driven to provide sufficient insight for decision makers to predict optimal performance, ensure continued operations and/or identify areas for improvement. Capability criteria associated with this control reasonably expect the following criteria to exist:
▪ Applicable SCR-CMM Level 3 (Well Defined) capabilities are implemented and operational.
▪ Metrics reporting includes quantitative analysis of Key Performance Indicators (KPIs).
▪ Metrics reporting includes quantitative analysis of Key Risk Indicators (KRIs).
▪ Scope of metrics, KPIs and KRIs covers organization-wide cybersecurity and data protection controls, including functions performed by third-parties.
▪ Organizational leadership maintains a formal process to objectively review and respond to metrics, KPIs and KRIs (e.g., monthly or quarterly review).
▪ Based on metrics analysis, process improvement recommendations are submitted for review and are handled in accordance with change control processes.
▪ Business and technical stakeholders are involved in reviewing and approving proposed changes to evolve capabilities.

Level 5 Continuously Improving

Capability & Performance Planning (CAP) capabilities, in addition to being standardized across the entity and centrally managed to ensure consistency across Technology Assets, Applications, Services and/or Data (TAASD), efforts are metrics driven to provide sufficient insight for decision makers to predict optimal performance, ensure continued operations and/or identify areas for improvement. Capability criteria associated with this control reasonably expect the following criteria to exist:
▪ Applicable SCR-CMM Level 3 (Well Defined) capabilities are implemented and operational.
▪ Based on predictive analysis, process improvements are implemented according to “continuous improvement” practices that affect process changes.
▪ Stakeholders make time-sensitive decisions to support operational efficiency, which may include automated remediation actions via Artificial Intelligence (AI) or Machine Learning (ML) technologies.

1. Prezentare generală

Titlu Standard

1.1 Referințe

1.2 Cerințe identificate

1.3 Reglementări asociate

2. Cerințe identificate

Cerințe
Sursă Cerință

3. Reglementări asociate

Reglementări
Sursă Reglementare
EULAW Articolul 9 Gestionarea capacității și a performanței
EULAW Articolul 34 Securitatea operațiunilor TIC

Articolul 34

Securitatea operațiunilor TIC

Ca parte a sistemelor, protocoalelor și instrumentelor lor și pentru toate activele TIC, entitățile financiare menționate la articolul 16 alineatul (1) din Regulamentul (UE) 2022/2554:

(a) 

monitorizează și gestionează ciclul de viață al tuturor activelor TIC;

(b) 

monitorizează dacă activele TIC sunt sprijinite de furnizori terți de servicii TIC ai entităților financiare, după caz;

(c) 

identifică cerințele în materie de capacitate ale activelor TIC și măsurile de menținere și îmbunătățire a disponibilității și eficienței sistemelor TIC și de prevenire a deficitelor de capacitate TIC înainte ca acestea să se concretizeze;

(d) 

efectuează scanarea automată a vulnerabilităților și evaluări ale activelor TIC, proporționale cu clasificarea acestora, astfel cum se menționează la articolul 30 alineatul (1), și cu profilul general de risc al activului TIC, și implementează corecții pentru a aborda vulnerabilitățile identificate;

(e) 

gestionează riscurile legate de activele TIC care sunt învechite sau moștenite sau care nu mai beneficiază de asistență;

(f) 

înregistrează în jurnale evenimentele legate de controlul accesului logic și fizic, operațiunile TIC, inclusiv activitățile de trafic de sistem și de rețea, precum și gestionarea modificărilor TIC;

(g) 

identifică și pun în aplicare măsuri de monitorizare și analiză a informațiilor privind activitățile și comportamentele anormale pentru operațiunile TIC critice sau importante;

(h) 

pun în aplicare măsuri de monitorizare a informațiilor relevante și actualizate cu privire la amenințările cibernetice;

(i) 

pun în aplicare măsuri de identificare a posibilelor scurgeri de informații, a codurilor dăunătoare și a altor amenințări la adresa securității, precum și a vulnerabilităților cunoscute public ale software-ului și hardware-ului și verifică dacă există noi actualizări de securitate corespunzătoare.

În sensul literei (f), entitățile financiare aliniază nivelul de detaliu al jurnalelor la scopul acestora și la utilizarea activelor TIC care produc înregistrările în jurnalele respective.

Tichete legate

Legături
Tip de legătură Tichet
is related to Annual
is related to relative Control Weighting = 08
is related to Process
is related to Protect
is related to SCRM Focus Tier 2 OPERATIONAL
is related to SCRM Focus Tier 3 TACTICAL
blocks Unauthorized Retention / Inability to Dispose of Data
blocks Business / Service Interruption
blocks Reduced Operational Productivity
blocks System / Data Compromise (Technical Vector)
blocks System / Data Compromise (Non-Technical Vector)
blocks Revenue Loss
blocks Contractual Default / Termination
blocks Loss of Competitive Advantage
blocks Reputational Harm / Loss of Stakeholder Trust
blocks Regulatory / Legal / Contractual Financial Liability
blocks Failure to Support Business / Mission Objectives
blocks Unaddressed Security / Compliance Exposure
blocks Uncontrolled Internal Security / Privacy Exposure
blocks Uncontrolled Third-Party Security / Privacy Exposure
blocks Undetected / Delayed Detection of Adverse Activity
blocks Failure to Achieve Strategic / Mission Objectives
blocks Recovery Failure / Unacceptable Recovery Delay
blocks Concentration / Single-Point Dependency Failure
blocks Third-Party Dependency Failure
blocks Loss of Data / Service Availability
blocks Physical / Environmental Damage
blocks Drought & Water Shortage
blocks Earthquakes
blocks Fire & Wildfires
blocks Floods
blocks Hurricanes & Tropical Storms
blocks Landslides & Debris Flow
blocks Pandemic (Disease) Outbreaks
blocks Severe Weather
blocks Space Weather
blocks Thunderstorms & Lightning
blocks Tornadoes
blocks Tsunamis
blocks Volcanoes
blocks Winter Storms & Extreme Cold
blocks Civil or Political Unrest
blocks Malicious Cyber Activity
blocks Hazardous Materials Emergencies
blocks Nuclear, Biological and Chemical (NBC) Weapons
blocks Terrorism & Armed Attacks
blocks Utility Service Disruption
blocks Dysfunctional Management Practices
blocks Human Error
blocks Technical / Mechanical Failure
blocks Data Quality Degradation / Data Poisoning
blocks Economic Shock / Market Disruption
blocks Hazardous / Degraded Operational Environment
blocks Manufacturing Capacity / Supply Disruption
blocks Product Defect / Design Failure
blocks Supplier Financial Distress / Insolvency
blocks Workforce Shortage / Loss of Critical Skills / Labor Disruption
blocks Transportation / Logistics Disruption
blocks Infrastructure Failure / Degradation
blocks OPS-01.01B
blocks OPS-01.02B
blocks OPS-01.01AC
is blocked by CAP-03 Capacity Planning – Assessment Procedure
blocks CP-02(02) Capacity Planning
blocks SC-05 Denial-of-service Protection
blocks SC-05(02) Capacity, Bandwidth, and Redundancy
blocks SC-05 [L] Denial-of-service Protection
blocks SC-05 [M] Denial-of-service Protection
blocks CP-02(02) [H] Capacity Planning
blocks SC-05 [H] Denial-of-service Protection
blocks 03.13.12E Denial-of-Service Protection
blocks PR.IR-04 Adequate resource capacity to ensure availability is maintained
  • Secure Controls Framework -

    The Secure Controls Framework® (SCF)

    "The SCF is the Common Controls Framework™ (CCF), the world's most comprehensive cybersecurity and data privacy metaframework - it is also free to use. The entire concept is building secure, compliant and resilient capabilities in the most efficient and cost-effective manner possible.

    The SCF is more than just a unified control catalog, since its included content creates a playbook for Governance, Risk & Compliance (GRC) capabilities. Used globally by organizations of every size, the SCF is a robust and scalable solution for security, compliance and resilience controls. As a comprehensive security framework, the SCF maps 1,400+ controls across 200+ laws, regulations, and industry frameworks so you can implement once and comply everywhere.

    Like it or not, cybersecurity is a protracted war on an asymmetric battlefield, where the threats are everywhere and as defenders we have to make the effort to work together to help improve cybersecurity and data privacy practices, since we all suffer when massive data breaches occur or when cyber attacks have physical impacts. Hackers share information on attack methods with other hackers, so why shouldn’t the good guys share information on how to best protect an organization? We decided to take action and make a difference, since we feel it is too important to wait for someone else to fix the problems that exist.

    The SCF is made up of volunteers, mainly specialists within the cybersecurity profession, who focus on GRC and the cybersecurity side of data privacy. These are auditors, engineers, architects, incident responders, consultants and other specialists who live and breathe these topics on a daily basis. The end product is "expert-derived content" that makes up the SCF." https://securecontrolsframework.com/ 

    Terms & Conditions

    The SCF End User License Agreement (EULA) governs the use of the Secure Controls Framework® (SCF) under the Creative Commons Attribution-No Derivatives 4.0 International Public License.