|
+Materiality Determination |
Materiality DeterminationDescriptionMechanisms exist to define materiality threshold criteria capable of designating an incident as material.Possible Solutions & ConsiderationsMicro-Small Business (<10 staff) / BLS Firm Size Classes 1-2∙ SCF Secure, Compliant & Resilient (SCR) Risk Management Model (SCR-RMM) (https://securecontrolsframework.com/risk-management-model)∙ Simple materiality threshold definition (document what constitutes a material incident) Small Business (10-49 staff) / BLS Firm Size Classes 3-4∙ SCF Secure, Compliant & Resilient (SCR) Risk Management Model (SCR-RMM) (https://securecontrolsframework.com/risk-management-model)∙ Documented materiality criteria aligned to business impact and applicable regulations Medium Business (50-249 staff) / BLS Firm Size Classes 5-6∙ SCF Secure, Compliant & Resilient (SCR) Risk Management Model (SCR-RMM) (https://securecontrolsframework.com/risk-management-model)∙ Documented materiality thresholds (financial, reputational, operational, regulatory) ∙ SEC cybersecurity disclosure rules considered (if applicable) Large Business (250-999 staff) / BLS Firm Size Classes 7-8∙ SCF Secure, Compliant & Resilient (SCR) Risk Management Model (SCR-RMM) (https://securecontrolsframework.com/risk-management-model)∙ Formal materiality determination process aligned to SEC cybersecurity disclosure rules (if public) ∙ Cross-functional materiality review team (Legal, Finance, CISO, Operations) Enterprise (> 1,000 staff) / BLS Firm Size Class 9∙ SCF Secure, Compliant & Resilient (SCR) Risk Management Model (SCR-RMM) (https://securecontrolsframework.com/risk-management-model)∙ Enterprise materiality determination framework (SEC Item 1.05, PCAOB, SOX alignment) ∙ Board-approved materiality thresholds with regular review cycle ∙ Automated materiality scoring integrated with incident response workflows 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 InformallySCR-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 TrackedSCR-CMM Level 2 criteria definitions are not available for this control:▪ A reasonable person would conclude a well-defined and standardized process is required. ▪ At this level of maturity, the “requirements-driven” nature of performing the control is focused on a localized and/or regionalized implementation, not uniform and consistent across the organization. ▪ Requirements are narrowly scoped for applicability and are primarily derived from compliance obligations (e.g., laws, regulations and contracts). Level 3 Well DefinedCybersecurity & Data Protection Governance (GOV) 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 GOV 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 GOV domain capabilities are well-documented and kept current by process owners. ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, is appropriately staffed and supported to implement and maintain GOV 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). ▪ Technology is leveraged to enhance the efficiency and accuracy of governance, risk management and compliance operations (e.g., GRC platform). ▪ An implemented and operational capability exists to define materiality threshold criteria capable of designating an incident as material. 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. Prehľad
1.1 Odkazy1.2 Identifikované požiadavky1.3 Súvisiace predpisy2. Identifikované požiadavky
3. Súvisiace predpisy
Prepojené úlohy
|