|
+Entropy Source & Random Bit Generation |
Entropy Source & Random Bit GenerationDescriptionMechanisms exist to use validated entropy sources and random bit generators that comply with NIST SP 800-90B to support Post-Quantum Cryptography (PQC):(1) Key generation; (2) Nonce generation; (3) Probabilistic algorithm inputs; and (4) Key validation. Possible Solutions & ConsiderationsMicro-Small Business (<10 staff) / BLS Firm Size Classes 1-2∙ Use OS and cloud provider cryptographically secure random number generators∙ Avoid custom entropy implementations Small Business (10-49 staff) / BLS Firm Size Classes 3-4∙ Cryptographically secure PRNG from OS or validated cryptographic libraries∙ NIST SP 800-90B guidance (https://csrc.nist.gov) Medium Business (50-249 staff) / BLS Firm Size Classes 5-6∙ FIPS 140-3 validated entropy sources∙ Hardware Security Module (HSM) with validated RNG ∙ NIST SP 800-90B compliance Large Business (250-999 staff) / BLS Firm Size Classes 7-8∙ FIPS 140-3 validated HSMs for key generation∙ Validated entropy sources aligned to NIST SP 800-90B ∙ Enterprise key management platform Enterprise (> 1,000 staff) / BLS Firm Size Class 9∙ Enterprise HSM infrastructure with FIPS 140-3 validated entropy∙ Quantum random number generators (QRNG) for enhanced entropy ∙ Centralized key management platform ∙ Continuous entropy source validation 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 InformallyQuantum Security (QTS) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include: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. 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 use validated entropy sources and random bit generators that comply with NIST SP 800-90B to support Post-Quantum Cryptography (PQC): (1) Key generation; (2) Nonce generation; (3) Probabilistic algorithm inputs; and (4) Key validation. 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. Ħarsa ġenerali
1.1 Referenzi1.2 Rekwiżiti identifikati1.3 Regolamenti relatati2. Rekwiżiti identifikati
3. Regolamenti relatati
Kwistjonijiet marbuta
|