+Deprecated Cryptographic Algorithms

Deprecated Cryptographic Algorithms

Description

Mechanisms exist to identify and disallow quantum-vulnerable and otherwise deprecated cryptographic algorithms.

Possible Solutions & Considerations

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

∙ Disable RC4, DES, 3DES and MD5 in systems and services
∙ Enforce TLS 1.2 minimum (disable TLS 1.0/1.1)
∙ Reference NIST SP 800-131A for deprecated algorithm guidance

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

∙ Deprecated algorithm disablement per NIST SP 800-131A
∙ TLS 1.2 minimum enforcement
∙ Retire RSA-1024 and similar weak key sizes

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

∙ Deprecated algorithm disablement across all systems
∙ NIST SP 800-131A and SP 800-57 compliance
∙ Vulnerability scanning for deprecated algorithm detection

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

∙ Formal deprecated algorithm disablement program
∙ Automated scanning for deprecated cryptographic use
∙ NIST SP 800-131A compliance tracking

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

∙ Enterprise deprecated algorithm removal program
∙ Automated detection and alerting for deprecated algorithm use
∙ NIST SP 800-131A and CNSA 2.0 compliance enforcement
∙ Continuous monitoring for deprecated algorithm introduction

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

Quantum Security (QTS) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include:

Level 2 Planned Tracked

Quantum 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 Defined

Quantum 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 identify and disallow quantum-vulnerable and otherwise deprecated cryptographic algorithms.

Level 4 Quantitatively Controlled

Utilize 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 Improving

Utilize 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łania

1.2 Zidentyfikowane wymagania

1.3 Powiązane regulacje

2. Zidentyfikowane wymagania

Wymagania

3. Powiązane regulacje

Regulacje
EULAW Artykuł 6 Mechanizmy kontroli szyfrowania i kryptograficznej
-

Powiązane zgłoszenia

Powiązania
is related to Annual
is related to relative Control Weighting = 07
is related to Process
is related to Protect
is related to SCRM Focus Tier 2 OPERATIONAL
blocks Identity Compromise / Impersonation
blocks Exposure from Unaddressed Vulnerabilities
blocks Unaddressed Security / Compliance Exposure
blocks Long-Term Confidentiality Loss from Cryptographic Obsolescence
blocks Loss of Confidentiality
blocks Loss of Data Integrity
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 Malicious Cyber Activity
blocks Dysfunctional Management Practices
blocks Human Error
blocks Statutory / Regulatory / Contractual Change
blocks Data Quality Degradation / Data Poisoning
blocks Harvest Now / Decrypt Later (HNDL)
blocks Cryptographic Compromise / Cryptanalytic Capability Advancement
is blocked by QTS-09.5 Deprecated Cryptographic Algorithms – Assessment Procedure
  • 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.