DE.AE | Anomalies and Events (DE.AE) | 0 |
DE.AE-1 | DE.AE-1: A baseline of network operations and expected data flows for users and systems is established and managed | 1 |
DE.AE-2 | DE.AE-2: Detected events are analyzed to understand attack targets and methods | 1 |
DE.AE-3 | DE.AE-3: Event data are aggregated and correlated from multiple sources and sensors | 1 |
DE.AE-4 | DE.AE-4: Impact of events is determined | 1 |
DE.AE-5 | DE.AE-5: Incident alert thresholds are established | 1 |
DE.CM | Security Continuous Monitoring (DE.CM) | 0 |
DE.CM-1 | DE.CM-1: The network is monitored to detect potential cybersecurity events | 1 |
DE.CM-2 | DE.CM-2: The physical environment is monitored to detect potential cybersecurity events | 1 |
DE.CM-3 | DE.CM-3: Personnel activity is monitored to detect potential cybersecurity events | 1 |
DE.CM-4 | DE.CM-4: Malicious code is detected | 1 |
DE.CM-5 | DE.CM-5: Unauthorized mobile code is detected | 1 |
DE.CM-6 | DE.CM-6: External service provider activity is monitored to detect potential cybersecurity events | 1 |
DE.CM-7 | DE.CM-7: Monitoring for unauthorized personnel, connections, devices, and software is performed | 1 |
DE.CM-8 | DE.CM-8: Vulnerability scans are performed | 1 |
DE.DP | Detection Processes (DE.DP) | 0 |
DE.DP-1 | DE.DP-1: Roles and responsibilities for detection are well defined to ensure accountability | 1 |
DE.DP-2 | DE.DP-2: Detection activities comply with all applicable requirements | 1 |
DE.DP-3 | DE.DP-3: Detection processes are tested | 1 |
DE.DP-4 | DE.DP-4: Event detection information is communicated to appropriate parties | 1 |
DE.DP-5 | DE.DP-5: Detection processes are continuously improved | 1 |
ID.AM | Asset Management (ID.AM) | 0 |
ID.AM-1 | ID.AM-1: Physical devices and systems within the organization are inventoried | 1 |
ID.AM-2 | ID.AM-2: Software platforms and applications within the organization are inventoried | 1 |
ID.AM-3 | ID.AM-3: Organizational communication and data flows are mapped | 1 |
ID.AM-4 | ID.AM-4: External information systems are catalogued | 1 |
ID.AM-5 | ID.AM-5: Resources (e.g., hardware, devices, data, and software) are prioritized based on their classification, criticality, and business value | 1 |
ID.AM-6 | ID.AM-6: Cybersecurity roles and responsibilities for the entire workforce and third-party stakeholders (e.g., suppliers, customers, partners) are established | 1 |
ID.BE | Business Environment (ID.BE) | 0 |
ID.BE-1 | ID.BE-1: The organization's role in the supply chain is identified and communicated | 1 |
ID.BE-2 | ID.BE-2: The organization's place in critical infrastructure and its industry sector is identified and communicated | 1 |
ID.BE-3 | ID.BE-3: Priorities for organizational mission, objectives, and activities are established and communicated | 1 |
ID.BE-4 | ID.BE-4: Dependencies and critical functions for delivery of critical services are established | 1 |
ID.BE-5 | ID.BE-5: Resilience requirements to support delivery of critical services are established | 1 |
ID.GV | Governance (ID.GV) | 0 |
ID.GV-1 | ID.GV-1: Organizational information security policy is established | 1 |
ID.GV-2 | ID.GV-2: Information security roles & responsibilities are coordinated and aligned with internal roles and external partners | 1 |
ID.GV-3 | ID.GV-3: Legal and regulatory requirements regarding cybersecurity, including privacy and civil liberties obligations, are understood and managed | 1 |
ID.GV-4 | ID.GV-4: Governance and risk management processes address cybersecurity risks | 1 |
ID.RA | Risk Assessment (ID.RA) | 0 |
ID.RA-1 | ID.RA-1: Asset vulnerabilities are identified and documented | 1 |
ID.RA-2 | ID.RA-2: Threat and vulnerability information is received from information sharing forums and sources | 1 |
ID.RA-3 | ID.RA-3: Threats, both internal and external, are identified and documented | 1 |
ID.RA-4 | ID.RA-4: Potential business impacts and likelihoods are identified | 1 |
ID.RA-5 | ID.RA-5: Threats, vulnerabilities, likelihoods, and impacts are used to determine risk | 1 |
ID.RA-6 | ID.RA-6: Risk responses are identified and prioritized | 1 |
ID.RM | Risk Management Strategy (ID.RM) | 0 |
ID.RM-1 | ID.RM-1: Risk management processes are established, managed, and agreed to by organizational stakeholders | 1 |
ID.RM-2 | ID.RM-2: Organizational risk tolerance is determined and clearly expressed | 1 |
ID.RM-3 | ID.RM-3: The organization's determination of risk tolerance is informed by its role in critical infrastructure and sector specific risk analysis | 1 |
PR.AC | Access Control (PR.AC) | 0 |
PR.AC-1 | PR.AC-1: Identities and credentials are managed for authorized devices and users | 1 |
PR.AC-2 | PR.AC-2: Physical access to assets is managed and protected | 1 |
PR.AC-3 | PR.AC-3: Remote access is managed | 1 |
PR.AC-4 | PR.AC-4: Access permissions are managed, incorporating the principles of least privilege and separation of duties | 1 |
PR.AC-5 | PR.AC-5: Network integrity is protected, incorporating network segregation where appropriate | 1 |
PR.AT | Awareness and Training (PR.AT) | 0 |
PR.AT-1 | PR.AT-1: All users are informed and trained | 1 |
PR.AT-2 | PR.AT-2: Privileged users understand roles & responsibilities | 1 |
PR.AT-3 | PR.AT-3: Third-party stakeholders (e.g., suppliers, customers, partners) understand roles & responsibilities | 1 |
PR.AT-4 | PR.AT-4: Senior executives understand roles & responsibilities | 1 |
PR.AT-5 | PR.AT-5: Physical and information security personnel understand roles & responsibilities | 1 |
PR.DS | Data Security (PR.DS) | 0 |
PR.DS-1 | PR.DS-1: Data-at-rest is protected | 1 |
PR.DS-2 | PR.DS-2: Data-in-transit is protected | 1 |
PR.DS-3 | PR.DS-3: Assets are formally managed throughout removal, transfers, and disposition | 1 |
PR.DS-4 | PR.DS-4: Adequate capacity to ensure availability is maintained | 1 |
PR.DS-5 | PR.DS-5: Protections against data leaks are implemented | 1 |
PR.DS-6 | PR.DS-6: Integrity checking mechanisms are used to verify software, firmware, and information integrity | 1 |
PR.DS-7 | PR.DS-7: The development and testing environment(s) are separate from the production environment | 1 |
PR.IP | Information Protection Processes and Procedures (PR.IP) | 0 |
PR.IP-1 | PR.IP-1: A baseline configuration of information technology/industrial control systems is created and maintained | 1 |
PR.IP-10 | PR.IP-10: Response and recovery plans are tested | 1 |
PR.IP-11 | PR.IP-11: Cybersecurity is included in human resources practices (e.g., deprovisioning, personnel screening) | 1 |
PR.IP-12 | PR.IP-12: A vulnerability management plan is developed and implemented | 1 |
PR.IP-2 | PR.IP-2: A System Development Life Cycle to manage systems is implemented | 1 |
PR.IP-3 | PR.IP-3: Configuration change control processes are in place | 1 |
PR.IP-4 | PR.IP-4: Backups of information are conducted, maintained, and tested periodically | 1 |
PR.IP-5 | PR.IP-5: Policy and regulations regarding the physical operating environment for organizational assets are met | 1 |
PR.IP-6 | PR.IP-6: Data is destroyed according to policy | 1 |
PR.IP-7 | PR.IP-7: Protection processes are continuously improved | 1 |
PR.IP-8 | PR.IP-8: Effectiveness of protection technologies is shared with appropriate parties | 1 |
PR.IP-9 | PR.IP-9: Response plans (Incident Response and Business Continuity) and recovery plans (Incident Recovery and Disaster Recovery) are in place and managed | 1 |
PR.MA | Maintenance (PR.MA) | 0 |
PR.MA-1 | PR.MA-1: Maintenance and repair of organizational assets is performed and logged in a timely manner, with approved and controlled tools | 1 |
PR.MA-2 | PR.MA-2: Remote maintenance of organizational assets is approved, logged, and performed in a manner that prevents unauthorized access | 1 |
PR.PT | Protective Technology (PR.PT) | 0 |
PR.PT-1 | PR.PT-1: Audit/log records are determined, documented, implemented, and reviewed in accordance with policy | 1 |
PR.PT-2 | PR.PT-2: Removable media is protected and its use restricted according to policy | 1 |
PR.PT-3 | PR.PT-3: Access to systems and assets is controlled, incorporating the principle of least functionality | 1 |
PR.PT-4 | PR.PT-4: Communications and control networks are protected | 1 |
RC.CO | Communications (RC.CO) | 0 |
RC.CO-1 | RC.CO-1: Public relations are managed | 1 |
RC.CO-2 | RC.CO-2: Reputation after an event is repaired | 1 |
RC.CO-3 | RC.CO-3: Recovery activities are communicated to internal stakeholders and executive and management teams | 1 |
RC.IM | Improvements (RC.IM) | 0 |
RC.IM-1 | RC.IM-1: Recovery plans incorporate lessons learned | 1 |
RC.IM-2 | RC.IM-2: Recovery strategies are updated | 1 |
RC.RP | Recovery Planning (RC.RP) | 0 |
RC.RP-1 | RC.RP-1: Recovery plan is executed during or after an event | 1 |
RS.AN | Analysis (RS.AN) | 0 |
RS.AN-1 | RS.AN-1: Notifications from detection systems are investigated | 1 |
RS.AN-2 | RS.AN-2: The impact of the incident is understood | 1 |
RS.AN-3 | RS.AN-3: Forensics are performed | 1 |
RS.AN-4 | RS.AN-4: Incidents are categorized consistent with response plans | 1 |
RS.CO | Communications (RS.CO) | 0 |
RS.CO-1 | RS.CO-1: Personnel know their roles and order of operations when a response is needed | 1 |
RS.CO-2 | RS.CO-2: Events are reported consistent with established criteria | 1 |
RS.CO-3 | RS.CO-3: Information is shared consistent with response plans | 1 |
RS.CO-4 | RS.CO-4: Coordination with stakeholders occurs consistent with response plans | 1 |
RS.CO-5 | RS.CO-5: Voluntary information sharing occurs with external stakeholders to achieve broader cybersecurity situational awareness | 1 |
RS.IM | Improvements (RS.IM) | 0 |
RS.IM-1 | RS.IM-1: Response plans incorporate lessons learned | 1 |
RS.IM-2 | RS.IM-2: Response strategies are updated | 1 |
RS.MI | Mitigation (RS.MI) | 0 |
RS.MI-1 | RS.MI-1: Incidents are contained | 1 |
RS.MI-2 | RS.MI-2: Incidents are mitigated | 1 |
RS.MI-3 | RS.MI-3: Newly identified vulnerabilities are mitigated or documented as accepted risks | 1 |
RS.RP | Response Planning (RS.RP) | 0 |
RS.RP-1 | RS.RP-1: Response plan is executed during or after an event | 1 |
X.1 | The Framework and its three parts | 0 |
X.2 | Implementation Tiers | 0 |
X.3 | Profiles, the seven steps and the privacy methodology | 0 |
X.4 | Supersession | 0 |