The framework in full

Six domains, twenty-six security functions, and the written descriptor for every function at every level of maturity. Search it, or open a function to read what each level actually requires.

🔒
Domain 1 · 5 functions

Secure Design

Incorporating security principles and requirements into the design phase of product development, including threat modeling, architectural risk analysis, and security requirements.

Third-Party Components 5 levels

Third-party components are defined as components over which the organization does not have design or development control, but that are promoted, sold, developed, or integrated within the organization's products. The organization retains the same cybersecurity and privacy accountability for third-party products as it does for internally created components.

1Ad Hoc

Documentation is incomplete or inconsistent. Security and privacy evaluations are informal and reactive. No formal update or replacement plans exist.

2Basic

Basic documentation is available but not comprehensive. Initial security and privacy evaluations are conducted, but processes are not standardized. Basic update plans are in place.

3Defined

Comprehensive documentation is reviewed and maintained. Formal security and privacy evaluations are conducted and documented. Defined processes for updating and replacing third-party components are established.

4Managed

Documentation is regularly reviewed and updated. Metrics are used to monitor the effectiveness of security and privacy evaluations. Quantitative techniques are used to predict and address potential issues.

5Optimized

Documentation and evaluation processes are continuously improved. Automation tools enforce security and privacy standards. Statistical techniques optimize the update and replacement processes.

Software Bill of Materials (SBOM) 5 levels

A robust SBOM includes both organizational-developed components and third-party components, encompassing purchased/licensed software, open-source software, and the upstream software dependencies required or depended upon by proprietary, purchased/licensed, and open-source software.

1Ad Hoc

SBOM practices are inconsistent and informal. The SBOM is incomplete and lacks critical information. Updates and reviews are conducted on an as-needed basis.

2Basic

A basic SBOM is established, including key components and dependencies. The SBOM includes some NTIA minimum elements. The SBOM is updated periodically, but not consistently.

3Defined

The SBOM is comprehensive and includes all components. All NTIA minimum elements are included. The SBOM is machine-readable and follows a consistent format. Regular updates and formal reviews are conducted.

4Managed

Metrics are established to monitor the effectiveness of SBOM practices. Automation tools are used to generate, update, and maintain the SBOM. Regular audits ensure adherence to standards.

5Optimized

SBOM practices are continuously improved. Advanced automation tools enforce SBOM standards and detect issues early. Continuous integration ensures real-time updates and monitoring.

Security Architecture 5 levels

The cybersecurity architecture represents the team's plan for actualizing the cybersecurity objectives determined in the product cybersecurity strategy. It provides for the definition of cybersecurity requirements, and the design and engineering of tools, technologies, processes, and controls.

1Ad Hoc

Security architecture practices are inconsistent and informal. The architecture lacks comprehensive views and documentation. Security measures are addressed reactively.

2Basic

Basic security architecture is established, including key views and considerations. Security measures are repeatable but not yet standardized. Progress towards objectives is monitored at a basic level.

3Defined

The security architecture is comprehensive and includes detailed views (Interoperability, Global System, Multi-Patient Harm, Update and Patchability, Security Use Case). Formally defined and communicated to all stakeholders.

4Managed

Metrics are established to monitor the effectiveness of the security architecture. Automation tools enforce standards and detect issues early. Regular audits ensure adherence.

5Optimized

Security architecture practices are continuously improved. Advanced automation tools optimize the architecture and address emerging threats. Statistical techniques enhance performance.

Threat Modeling 5 levels

Threat modeling involves capturing cybersecurity risks introduced through various stages of the product lifecycle, including supply chain, manufacturing, deployment, interoperation with other devices, maintenance/update activities, and decommission activities. The threat model provides a detailed analysis including processes, data stores, data flows, trust boundaries, and interfaces with external entities.

1Ad Hoc

Threat modeling practices are inconsistent and informal. The threat model is incomplete and lacks detailed analysis. Risks and mitigations are addressed reactively.

2Basic

Basic threat modeling processes are established. Threat models include key processes, data stores, data flows, and trust boundaries. Risks and mitigations are identified but not standardized.

3Defined

Threat modeling processes are comprehensive and include detailed analysis of all relevant elements. Formally defined, documented, and communicated. Risks, mitigations, and assumptions are thoroughly documented.

4Managed

Metrics are established to monitor the effectiveness of threat modeling. Automation tools support the process and maintain traceability. Regular reviews and audits ensure adherence.

5Optimized

Threat modeling practices are continuously improved. Advanced automation tools optimize the process and address emerging threats. Statistical techniques enhance performance.

Cybersecurity Requirements 5 levels

Cybersecurity requirements are described through system and software level detailed requirements and expressed to the development team for implementation. A similar approach to functional requirements should be adopted, including unit testing, boundary analysis, and considering legal, regulatory, and customer requirements, as well as industry standards.

1Ad Hoc

Cybersecurity requirement practices are inconsistent and informal. Requirements are incomplete. Evidence of implementation is sporadic. Compliance with legal and regulatory requirements is not consistently ensured.

2Basic

Basic cybersecurity requirements are established and documented. Requirements are communicated to the development team but not standardized. Evidence of implementation is collected but not comprehensively.

3Defined

Cybersecurity requirements are detailed at both system and software levels and formally documented. Systematically communicated and integrated into the development process. Comprehensive evidence of implementation provided.

4Managed

Metrics are established to monitor the effectiveness of cybersecurity requirement practices. Quantitative techniques predict performance variations. Continuous feedback from customers is integrated.

5Optimized

Cybersecurity requirement practices are continuously improved. Advanced automation tools optimize the definition and implementation of requirements. Statistical techniques enhance performance.

💻
Domain 2 · 4 functions

Secure Development

Implementing secure coding practices during the software development phase, including code reviews, secure coding standards, and integration of security tools.

Secure Build 5 levels

Secure build practices involve ensuring that the build processes for software and systems are conducted in a secure manner to prevent the introduction of vulnerabilities. This includes using secure build environments, implementing security checks during the build process, and ensuring the integrity and authenticity of build artifacts.

1Ad Hoc

Secure build practices are inconsistent and informal. The build environment is not securely configured or isolated. Security checks during the build process are sporadic.

2Basic

Basic secure build practices are established and documented. Initial efforts to secure the build environment and implement security checks are made. The CI/CD pipeline includes basic security checks.

3Defined

Secure build practices are comprehensively defined, documented, and communicated. The build environment is securely configured and isolated. Automated security checks are integrated into the build process.

4Managed

Metrics are established to monitor the effectiveness of secure build practices. Quantitative techniques predict performance variations. Continuous monitoring and validation processes are integrated.

5Optimized

Secure build practices are continuously improved. Advanced automation tools optimize the build process, security checks, and monitoring. Statistical techniques enhance performance.

Secure Coding & Code Quality 5 levels

Secure coding and code quality practices involve ensuring that software development processes follow secure coding standards and maintain high code quality to prevent the introduction of vulnerabilities. This includes implementing secure coding guidelines, conducting code reviews, using automated tools for static and dynamic analysis, and maintaining comprehensive documentation.

1Ad Hoc

Secure coding and code quality practices are inconsistent and informal. Secure coding guidelines are not comprehensively developed or communicated. Code reviews are sporadic.

2Basic

Basic secure coding and code quality practices are established and documented. Secure coding guidelines are communicated to developers but not standardized. Code reviews are conducted periodically.

3Defined

Secure coding and code quality practices are comprehensively defined, documented, and communicated. Formal code review processes are implemented. Automated static and dynamic analysis tools are integrated.

4Managed

Metrics are established to monitor the effectiveness of secure coding and code quality practices. Quantitative techniques predict performance variations in code quality. Regular audits ensure adherence.

5Optimized

Secure coding and code quality practices are continuously improved. Advanced automation tools optimize code analysis and reviews. Statistical techniques enhance performance.

Supply Chain Security & Manufacturing Integrity 5 levels

Supply chain security and manufacturing integrity involve ensuring that all components, processes, and partners involved in the supply chain and manufacturing process adhere to stringent security standards. This includes assessing and managing risks associated with third-party suppliers, verifying the integrity of components, and implementing robust security measures throughout the manufacturing process.

1Ad Hoc

Supply chain security and manufacturing integrity practices are inconsistent and informal. Supplier evaluations are not comprehensively conducted. Component verification processes are limited.

2Basic

Basic supply chain security and manufacturing integrity practices are established and documented. Initial efforts to evaluate and manage suppliers are made. Component verification processes are implemented but not fully standardized.

3Defined

Supply chain security and manufacturing integrity practices are comprehensively defined, documented, and communicated. Thorough supplier evaluation processes are established. Component verification processes are systematically implemented.

4Managed

Metrics are established to monitor the effectiveness of supply chain security practices. Quantitative techniques predict performance variations. Regular audits ensure adherence.

5Optimized

Supply chain security and manufacturing integrity practices are continuously improved. Advanced automation tools optimize supplier evaluation and component verification. Statistical techniques enhance performance.

Security Training, Awareness & Culture 5 levels

Security training, awareness, and culture involve educating and engaging employees at all levels of the engineering organization to ensure they understand and adhere to security best practices. This includes providing regular training sessions, promoting awareness of security threats and policies, and fostering a security-conscious culture throughout the organization.

1Ad Hoc

Security training, awareness, and culture practices are inconsistent and informal. Training programs are limited and not regularly updated. Awareness initiatives are sporadic. Leadership support for security culture is minimal.

2Basic

Basic security training programs are established and documented. Initial efforts to promote security awareness and engage employees are made. Basic monitoring and assessment of training effectiveness are conducted.

3Defined

Comprehensive security training programs are defined, documented, and communicated. Ongoing security awareness initiatives and engagement activities are implemented. Leadership actively supports a security-conscious culture.

4Managed

Metrics are established to monitor the effectiveness of security training, awareness, and culture practices. Quantitative techniques predict performance variations. Regular audits ensure adherence.

5Optimized

Security training, awareness, and culture practices are continuously improved. Advanced automation tools optimize training delivery, monitoring, and engagement. Statistical techniques enhance performance.

🧪
Domain 3 · 4 functions

Security Testing

Rigorous testing of products to identify and address security weaknesses through static and dynamic analysis, vulnerability assessment, and penetration testing.

Configuration Security & Validation 5 levels

Configuration security and validation involve ensuring that components are configured securely to prevent unintentional vulnerabilities that can be easily exploited. This includes addressing issues such as exposing interfaces to untrusted networks, retaining unused or development functionality, and using improper authentication/authorization of accessible resources.

1Ad Hoc

Configuration security practices are inconsistent and informal. Configuration requirements are not comprehensively identified or documented. Validation processes are sporadic and not systematically conducted.

2Basic

Basic configuration security practices are established and documented. Initial efforts to identify and document configuration requirements are made. Validation processes are conducted periodically but lack consistency.

3Defined

Configuration security requirements are comprehensively identified, documented, and communicated. Secure configuration settings are consistently implemented. Regular validation processes, including automated and manual checks, are conducted.

4Managed

Metrics are established to monitor the effectiveness of configuration security practices. Quantitative techniques predict performance variations. Validation processes are integrated into the overall security management framework.

5Optimized

Configuration security practices are continuously improved. Advanced automation tools optimize configuration implementation, monitoring, and validation. Statistical techniques enhance performance.

Cybersecurity Controls 5 levels

Cybersecurity controls are measures implemented to protect systems, networks, and data from security threats and vulnerabilities. These controls can be preventive, detective, and corrective, and they include policies, procedures, technologies, and practices designed to mitigate risks and ensure the integrity, confidentiality, and availability of information.

1Ad Hoc

Cybersecurity control practices are inconsistent and informal. Controls are not comprehensively identified, documented, or implemented. Testing, validation, and monitoring of controls are sporadic.

2Basic

Basic cybersecurity control practices are established and documented. Initial efforts to implement and configure controls are made. Basic testing and validation are conducted but not standardized.

3Defined

Cybersecurity control practices are comprehensively defined, documented, and communicated. Controls are systematically implemented to meet security requirements. Regular testing, validation, and monitoring are conducted.

4Managed

Metrics are established to monitor the effectiveness of cybersecurity control practices. Quantitative techniques predict performance variations. Continuous monitoring and validation are integrated.

5Optimized

Cybersecurity control practices are continuously improved. Advanced automation tools optimize control implementation, monitoring, and incident response. Statistical techniques enhance performance.

Vulnerability Assessment & Management 5 levels

Vulnerability assessment and management involve identifying, evaluating, and mitigating security vulnerabilities within product design. This process includes regular vulnerability scans, risk assessment, prioritization of remediation efforts, and continuous monitoring to ensure vulnerabilities are addressed promptly and effectively.

1Ad Hoc

Vulnerability assessment and management practices are inconsistent and informal. Vulnerability scanning and testing are sporadic. Risk assessment and prioritization are limited or lacking.

2Basic

Basic vulnerability assessment and management practices are established and documented. Initial efforts to conduct regular vulnerability scans and manual testing are made. Basic risk assessment and prioritization processes are implemented.

3Defined

Vulnerability assessment and management practices are comprehensively defined, documented, and communicated. Regular vulnerability scans and manual testing are systematically conducted. Formal risk assessment and prioritization processes are established.

4Managed

Metrics are established to monitor the effectiveness of vulnerability assessment and management practices. Quantitative techniques predict performance variations. Regular audits ensure adherence.

5Optimized

Vulnerability assessment and management practices are continuously improved. Advanced automation tools optimize vulnerability scanning, risk assessment, and remediation processes. Statistical techniques enhance performance.

Red Team & Penetration Testing 5 levels

Red team and penetration testing involve conducting simulated attacks on a product to identify security weaknesses that could be exploited to cause the device to function outside its intended use or to cause patient harm.

1Ad Hoc

Penetration testing practices are inconsistent and informal. Testing scope and objectives are not clearly defined. Testing methodologies are limited or lacking.

2Basic

Basic penetration testing practices are established and documented. Initial efforts to define testing scope and objectives are made. Basic testing at different levels is conducted but not standardized.

3Defined

Penetration testing practices are comprehensively defined, documented, and communicated. Testing scope and objectives are clearly defined and aligned with security requirements. Systematic testing at different levels is conducted.

4Managed

Metrics are established to monitor the effectiveness of penetration testing practices. Quantitative techniques predict performance variations. Regular audits ensure adherence.

5Optimized

Penetration testing practices are continuously improved. Advanced automation tools optimize testing methodologies, risk assessment, and mitigation processes. Statistical techniques enhance performance.

⚠
Domain 4 · 4 functions

Risk Management

Systematic identification, assessment, and mitigation of security risks throughout the product lifecycle.

Measures & Metrics 5 levels

Measures and metrics involve the systematic collection, analysis, and reporting of data to evaluate and improve the effectiveness of security programs and processes. This includes defining key performance indicators (KPIs), establishing benchmarks, tracking progress, and using data-driven insights to inform decision-making and drive continuous improvement.

1Ad Hoc

Measures and metrics practices are inconsistent and informal. Data collection is sporadic and not systematically conducted. KPIs are limited or lacking. Decision-making is not consistently informed by data.

2Basic

Basic measures and metrics practices are established and documented. Initial efforts to collect data regularly are made. Basic KPIs are defined and tracked. Initial analysis and reporting practices are implemented.

3Defined

Measures and metrics practices are comprehensively defined, documented, and communicated. Regular data collection is systematically conducted. Formal processes for defining and tracking KPIs are established. Decision-making is consistently informed by data-driven insights.

4Managed

Metrics are established to monitor the effectiveness of measures and metrics practices. Quantitative techniques predict performance variations. Data is used to proactively identify areas for improvement.

5Optimized

Measures and metrics practices are continuously improved. Advanced analytics and automation tools optimize data collection, analysis, and reporting processes. Metrics are aligned with strategic goals.

Risk Assessment & Mitigation 5 levels

Risk assessment and mitigation involve identifying, evaluating, and addressing cybersecurity risks within an engineering organization and the products they develop. This includes conducting thorough risk assessments to determine the potential impact and likelihood of risks, prioritizing risks based on their severity, and implementing mitigation strategies to reduce or eliminate risks.

1Ad Hoc

Risk assessment and mitigation practices are inconsistent and informal. Asset, threat, and vulnerability identification are not comprehensively conducted or documented. Risk assessment and scoring processes are limited.

2Basic

Basic risk assessment and mitigation practices are established and documented. Initial efforts to identify assets, threats, and vulnerabilities are made. Basic risk assessment and scoring processes are implemented.

3Defined

Risk assessment and mitigation practices are comprehensively defined, documented, and communicated. Systematic identification of threats and vulnerabilities is conducted. Formal risk assessment and scoring processes are consistently applied.

4Managed

Metrics are established to monitor the effectiveness of risk assessment and mitigation practices. Quantitative techniques predict performance variations. Regular audits ensure adherence.

5Optimized

Risk assessment and mitigation practices are continuously improved. Advanced automation tools optimize risk identification, assessment, and mitigation processes. Statistical techniques enhance performance.

Cybersecurity Governance & Program Management 5 levels

Cybersecurity governance and program management involve establishing a structured framework to oversee and manage the engineering organization's cybersecurity efforts. This includes defining roles and responsibilities, creating policies and procedures, ensuring compliance with regulatory requirements, and continuously improving the cybersecurity posture through strategic planning and resource allocation.

1Ad Hoc

Cybersecurity governance and program management practices are inconsistent and informal. Roles and responsibilities are not clearly defined or documented. Policies and procedures are limited or lacking.

2Basic

Basic cybersecurity governance and program management practices are established and documented. Initial efforts to define roles and responsibilities are made. Basic policies and procedures are developed and communicated.

3Defined

Cybersecurity governance and program management practices are comprehensively defined, documented, and communicated. Clear roles and responsibilities are established. Comprehensive policies and procedures are aligned with regulatory requirements.

4Managed

Metrics are established to monitor the effectiveness of cybersecurity governance and program management practices. Quantitative techniques predict performance variations. Regular audits ensure adherence.

5Optimized

Cybersecurity governance and program management practices are continuously improved. Advanced automation tools optimize policy development, compliance monitoring, and project management. Statistical techniques enhance performance.

Labeling, Documentation & Compliance 5 levels

Labeling, documentation, and compliance involve the creation, maintenance, and management of comprehensive documentation related to cybersecurity activities and measures. This includes ensuring that all relevant documentation is accurate, accessible, and compliant with regulatory and industry standards.

1Ad Hoc

Labeling, documentation, and compliance practices are inconsistent and informal. Documentation is incomplete. Compliance efforts are sporadic. Accessibility and security of documentation are limited.

2Basic

Basic labeling, documentation, and compliance practices are established and documented. Initial efforts to create and maintain comprehensive documentation are made. Basic compliance audits are conducted.

3Defined

Labeling, documentation, and compliance practices are comprehensively defined, documented, and communicated. Comprehensive documentation covering all cybersecurity activities is maintained. Regular compliance audits are conducted.

4Managed

Metrics are established to monitor the effectiveness of labeling, documentation, and compliance practices. Quantitative techniques predict performance variations. Regular audits ensure adherence.

5Optimized

Labeling, documentation, and compliance practices are continuously improved. Advanced automation tools optimize documentation management, compliance monitoring, and reporting. Statistical techniques enhance performance.

🔐
Domain 5 · 4 functions

Privacy & Data Protection

Protection of personal and sensitive data through encryption, access controls, data anonymization, and compliance with privacy regulations.

Data Architecture & Design 5 levels

Data architecture and design involve the structured organization, storage, and management of data within an engineering organization, and within a product design to ensure its privacy and protection. This includes defining data models, establishing data governance, implementing data protection measures, and ensuring compliance with regulatory requirements.

1Ad Hoc

Data architecture and design practices are inconsistent and informal. Data modeling and classification are not comprehensively conducted or documented. Data protection measures are sporadic.

2Basic

Basic product data architecture and design practices are established and documented. Initial efforts to create and maintain product data models and classification are made. Initial data protection measures are implemented.

3Defined

Data architecture and design practices are comprehensively defined, documented, and communicated. Comprehensive product data models and data classification are maintained. Comprehensive data protection measures are systematically implemented.

4Managed

Metrics are established to monitor the effectiveness of product data architecture and design practices. Quantitative techniques predict performance variations. Regular audits ensure adherence.

5Optimized

Data architecture and design practices are continuously improved. Advanced automation tools optimize data modeling, governance, protection, and compliance processes. Statistical techniques enhance performance.

Data Inventory & Classification 5 levels

Data inventory and classification activities involve identifying, cataloging, and categorizing of all data assets within an engineering organization and within a product design. This process helps in understanding the types, locations, and sensitivity of data, enabling the implementation of appropriate data protection measures and compliance with regulatory requirements.

1Ad Hoc

Data inventory and classification practices are inconsistent and informal. Data inventory is incomplete. Data classification criteria and processes are limited. Access control and data protection measures are sporadic.

2Basic

Basic data inventory and classification practices are established and documented. Initial efforts to create and maintain a data inventory are made. Basic data classification criteria and processes are developed.

3Defined

Data inventory and classification practices are comprehensively defined, documented, and communicated. Comprehensive data inventory covering all data assets is maintained. Formal data classification criteria and processes are consistently applied.

4Managed

Metrics are established to monitor the effectiveness of data inventory and classification practices. Quantitative techniques predict performance variations. Regular audits ensure adherence.

5Optimized

Data inventory and classification practices are continuously improved. Advanced automation tools optimize data discovery, classification, tagging, and protection processes. Statistical techniques enhance performance.

Privacy & Data Security Governance 5 levels

Privacy and data security governance involve establishing a structured framework to oversee and manage the engineering organization's privacy and data protection efforts as well as those designed into our products. This includes defining roles and responsibilities, creating policies and procedures, ensuring compliance with regulatory requirements, and continuously improving the privacy and data security posture.

1Ad Hoc

Privacy and data security governance practices are inconsistent and informal. Roles and responsibilities are not clearly defined or documented. Policies and procedures are limited or lacking.

2Basic

Basic privacy and data security governance practices are established and documented. Initial efforts to define roles and responsibilities are made. Basic policies and procedures are developed and communicated.

3Defined

Privacy and data security governance practices are comprehensively defined, documented, and communicated. Clear roles and responsibilities are established. Comprehensive policies and procedures are aligned with regulatory requirements.

4Managed

Metrics are established to monitor the effectiveness of privacy and data security governance practices. Quantitative techniques predict performance variations. Regular audits ensure adherence.

5Optimized

Privacy and data security governance practices are continuously improved. Advanced automation tools optimize policy development, compliance monitoring, and project management. Statistical techniques enhance performance.

Secure Data Processing & Handling 5 levels

Secure data processing and handling involve implementing and maintaining practices that ensure data integrity, confidentiality, and availability throughout the data lifecycle. This includes data collection, storage, processing, transmission, and deletion, as well as implementing appropriate security measures to protect data from unauthorized access, alteration, and loss.

1Ad Hoc

Data processing and handling practices are inconsistent and informal. Data collection, storage, processing, transmission, and deletion practices are not comprehensively conducted or documented.

2Basic

Basic data processing and handling practices are established and documented. Initial efforts to implement secure data collection, storage, processing, transmission, and deletion practices are made.

3Defined

Data processing and handling practices are comprehensively defined, documented, and communicated. Comprehensive data collection, storage, processing, transmission, and deletion practices are maintained.

4Managed

Metrics are established to monitor the effectiveness of data processing and handling practices. Quantitative techniques predict performance variations. Regular audits ensure adherence.

5Optimized

Data processing and handling practices are continuously improved. Advanced automation tools optimize data collection, storage, processing, transmission, and deletion processes. Statistical techniques enhance performance.

🔄
Domain 6 · 5 functions

Lifecycle Management

Maintaining and enhancing product security throughout its entire lifecycle, from development to decommissioning, including patch management and vulnerability disclosure.

Threat Monitoring & Intelligence 5 levels

Threat monitoring and intelligence involves the continuous collection, analysis, and dissemination of information related to potential cybersecurity threats. This process helps engineering organizations detect, respond to, and mitigate threats in a timely manner, ensuring the ongoing protection of systems, data, and networks throughout their lifecycle.

1Ad Hoc

Threat monitoring and intelligence practices are inconsistent and informal. Sources of threat intelligence are limited. Continuous monitoring and alerting are limited or lacking. Threat intelligence sharing is minimal.

2Basic

Basic threat monitoring and intelligence practices are established and documented. Initial efforts to identify and document sources of threat intelligence are made. Basic analytical techniques and correlation processes are implemented.

3Defined

Threat monitoring and intelligence practices are comprehensively defined, documented, and communicated. Reliable sources of threat intelligence are identified, documented, and regularly reviewed. Advanced analytical techniques are established.

4Managed

Metrics are established to monitor the effectiveness of threat monitoring and intelligence practices. Quantitative techniques predict performance variations. Regular audits ensure adherence.

5Optimized

Threat monitoring and intelligence practices are continuously improved. Advanced automation tools optimize threat intelligence collection, analysis, detection, and response processes. Statistical techniques enhance performance.

Incident Detection & Response 5 levels

Incident detection and response involves identifying, analyzing, and mitigating cybersecurity incidents to minimize their impact on the engineering organization and products. This includes implementing tools and processes for detection of security events, establishing incident response plans, and ensuring effective communication and remediation efforts.

1Ad Hoc

Incident detection and response practices are inconsistent and informal. Monitoring and alerting are limited. Incident response plans are incomplete or not regularly updated. Communication and coordination efforts are limited.

2Basic

Basic incident detection and response practices are established and documented. Initial efforts to implement monitoring and alerting are made. Basic incident analysis and root cause investigation processes are developed.

3Defined

Incident detection and response practices are comprehensively defined, documented, and communicated. Comprehensive monitoring and alerting processes are in place. A comprehensive incident response plan is developed, maintained, and regularly updated.

4Managed

Metrics are established to monitor the effectiveness of incident detection and response practices. Quantitative techniques predict performance variations. Regular audits ensure adherence.

5Optimized

Incident detection and response practices are continuously improved. Advanced automation tools optimize detection, analysis, response, and recovery processes. Statistical techniques enhance performance.

Product Lifecycle Transition Management 5 levels

Product lifecycle transition management involves overseeing the secure and efficient transition of products through their various lifecycle stages, including development, deployment, maintenance, end-of-service (EOS), and end-of-life (EOL). This ensures that security and privacy are maintained throughout the product's lifecycle and that risks associated with transitions are effectively managed.

1Ad Hoc

Product lifecycle transition management practices are inconsistent and informal. Lifecycle stages and transition plans are not comprehensively documented. EOS and EOL transition processes are limited or lacking.

2Basic

Basic product lifecycle transition management practices are established and documented. Initial efforts to define lifecycle stages and develop transition plans are made. Initial EOS and EOL transition processes are developed.

3Defined

Product lifecycle transition management practices are comprehensively defined, documented, and communicated. Clear lifecycle stages and detailed transition plans are established and consistently applied. Formal EOS and EOL transition processes are developed.

4Managed

Metrics are established to monitor the effectiveness of product lifecycle transition management practices. Quantitative techniques predict performance variations. Regular audits ensure adherence.

5Optimized

Product lifecycle transition management practices are continuously improved. Advanced automation tools optimize transition planning, risk management, and communication processes. Statistical techniques enhance performance.

Coordinated Vulnerability Disclosure & Collaboration 5 levels

Coordinated vulnerability disclosure, information sharing, and collaboration involve the structured process of identifying, reporting, and addressing security vulnerabilities in a cooperative manner with stakeholders, including security researchers, industry partners, and regulatory bodies. This ensures that vulnerabilities are disclosed responsibly, mitigated effectively, and that information is shared to enhance overall cybersecurity.

1Ad Hoc

Vulnerability disclosure, information sharing, and collaboration practices are inconsistent and informal. Vulnerability disclosure policies are limited or lacking. Reporting mechanisms and triage processes are sporadic.

2Basic

Basic vulnerability disclosure, information sharing, and collaboration practices are established and documented. Initial efforts to develop and publish vulnerability disclosure policies are made. Basic reporting mechanisms and triage processes are implemented.

3Defined

Vulnerability disclosure, information sharing, and collaboration practices are comprehensively defined, documented, and communicated. Clear and accessible vulnerability disclosure policies are established and published. Active participation in information-sharing initiatives is conducted.

4Managed

Metrics are established to monitor the effectiveness of vulnerability disclosure, information sharing, and collaboration practices. Quantitative techniques predict performance variations. Regular audits ensure adherence.

5Optimized

Vulnerability disclosure, information sharing, and collaboration practices are continuously improved. Advanced automation tools optimize reporting, triage, analysis, and mitigation processes. Statistical techniques enhance performance.

Patch Management 5 levels

Patch management involves the systematic process of identifying, acquiring, testing, deploying, and monitoring software and firmware updates (patches) to mitigate security vulnerabilities and enhance system performance. Effective patch management ensures that systems remain secure, compliant, and functional throughout their lifecycle.

1Ad Hoc

Patch management practices are inconsistent and informal. Patch identification and acquisition processes are limited. Patch deployment efforts are reactive. Post-deployment validation and continuous monitoring are limited.

2Basic

Basic patch management practices are established and documented. Initial efforts to identify and acquire patches are made. Basic patch testing and evaluation processes are implemented.

3Defined

Patch management practices are comprehensively defined, documented, and communicated. Reliable sources for patch identification and acquisition are established. Comprehensive patch testing and evaluation processes are systematically conducted.

4Managed

Metrics are established to monitor the effectiveness of patch management practices. Quantitative techniques predict performance variations. Regular audits ensure adherence.

5Optimized

Patch management practices are continuously improved. Advanced automation tools optimize patch identification, testing, deployment, and monitoring processes. Statistical techniques enhance performance.