|
+Technology Assets, Applications, Services and/or Data (TAASD) Criticality Ratings |
Technology Assets, Applications, Services and/or Data (TAASD) Criticality RatingsDescriptionMechanisms exist to assign Business Continuity & Disaster Recovery (BC/DR)-relevant criticality ratings for Technology Assets, Applications, Services and/or Data (TAASD).Possible Solutions & ConsiderationsMicro-Small Business (<10 staff) / BLS Firm Size Classes 1-2∙ Business Impact Analysis (BIA)∙ Criticality rating column in the asset inventory spreadsheet Small Business (10-49 staff) / BLS Firm Size Classes 3-4∙ Business Impact Analysis (BIA)∙ Criticality assessments ∙ Criticality rating field in the asset inventory Medium Business (50-249 staff) / BLS Firm Size Classes 5-6∙ Business Impact Analysis (BIA)∙ Criticality assessments ∙ Configuration Management Database (CMDB) criticality attribute Large Business (250-999 staff) / BLS Firm Size Classes 7-8∙ Business Impact Analysis (BIA)∙ Criticality assessments ∙ CMDB criticality attribute linked to BC/DR plans (e.g., ServiceNow, Fusion Risk Management) Enterprise (> 1,000 staff) / BLS Firm Size Class 9∙ Enterprise BIA program with automated dependency mapping∙ CMDB criticality attribute linked to BC/DR plans (e.g., ServiceNow, Fusion Risk Management) ∙ Annual criticality recertification SCR-CMMLevel 0 Not PerformedPractices 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 InformallyAsset Management (AST) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include:▪ Policies, standards & procedures associated with AST domain capabilities provide limited coverage due to the depth and breadth of the existing documentation. ▪ Asset management-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices. ▪ Asset management is informally assigned as an additional duty to existing IT/cybersecurity personnel. ▪ IT and/or cybersecurity personnel work with business stakeholders to identify business-critical Technology Assets, Applications, Services and/or Data (TAASD). ▪ No structured process exists to review or share the results of the inventories. Level 2 Planned TrackedAsset Management (AST) 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 AST domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with AST 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 AST domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Asset management-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Asset management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel. ▪ Data/process owners for business-critical assets are documented and are reviewed as part of the annual asset inventories. Level 3 Well DefinedAsset Management (AST) 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 AST 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 AST domain capabilities are well-documented and kept current by process owners. ▪ An IT Asset Management (ITAM) team, or similar function, is appropriately staffed and supported to implement and maintain AST domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of ITAM operations (e.g., ITAM platform, (e.g., Configuration Management Database (CMBD) Asset Management solution). ▪ 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 AST 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). Level 4 Quantitatively ControlledUtilize SCR-CMM Level 3 criteria definitions:▪ There are no defined Level 4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to operationalize this control. ▪ While it may be possible to develop “metrics-driven” capabilities for this control, the criteria would be organization-specific to define. Level 5 Continuously ImprovingUtilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions:▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define. 1. Przegląd
1.1 Odwołania1.2 Zidentyfikowane wymagania1.3 Powiązane regulacje2. Zidentyfikowane wymagania
3. Powiązane regulacje
Powiązane zgłoszenia
|