|
+Quantum Security Policy |
Quantum Security PolicyDescriptionMechanisms exist to establish a formal, documented quantum security policy that:(1) Conveys executive management's intent; (2) Provides organizational direction and expected behaviors; (3) Is reviewed at least annually; and (4) Is updated, as necessary, to adapt to evolving risks, threats and other changes that affect the organization. Possible Solutions & ConsiderationsMicro-Small Business (<10 staff) / BLS Firm Size Classes 1-2∙ Reference NIST PQC standards in cryptography policy∙ Note: Standalone quantum security policy may not be required at this size Small Business (10-49 staff) / BLS Firm Size Classes 3-4∙ Addendum to existing cryptography policy covering quantum risks∙ NIST PQC reference (https://csrc.nist.gov/pqc) Medium Business (50-249 staff) / BLS Firm Size Classes 5-6∙ Formal quantum security policy∙ Annual review cycle aligned to NIST PQC updates ∙ Integration with cryptography standard Large Business (250-999 staff) / BLS Firm Size Classes 7-8∙ Standalone quantum security policy with executive approval∙ Annual review and update cycle ∙ Alignment to NIST PQC, NSA CNSA 2.0 and CISA PQC guidance Enterprise (> 1,000 staff) / BLS Firm Size Class 9∙ Enterprise quantum security policy with board endorsement∙ Alignment to NIST, NSA, CISA, and applicable regulatory guidance ∙ Integration with security policy framework 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 TrackedQuantum Security (QTS) 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 QTS domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with QTS domain capabilities are documented and maintained by process owners. ▪ Quantum security risk management-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). Level 3 Well DefinedQuantum Security (QTS) 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 QTS 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 QTS domain capabilities are well-documented and kept current by process owners. ▪ A risk management team, or similar function, is appropriately staffed and supported to implement and maintain QTS domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of risk management operations (e.g., risk management solution, GRC platform and TPRM tool). ▪ 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 QTS 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 establish a formal, documented quantum security policy that: (1) Conveys executive management's intent; (2) Provides organizational direction and expected behaviors; (3) Is reviewed at least annually; and (4) Is updated, as necessary, to adapt to evolving risks, threats and other changes that affect the organization. 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. Visão geral
1.1 Referências1.2 Requisitos identificados1.3 Regulamentos relacionados2. Requisitos identificados
3. Regulamentos relacionados
Pedidos ligados
|