A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Function | Category | Subcategory | Frequency | Person Responsible | |||||||||||||||||||||
2 | IDENTIFY | Asset Management (ID.AM): The data, personnel, tools, systems, and resources that enable an organization to achieve business objectives are identified and managed in accordance with their importance to the business objectives and organizational risk strategies. | ID.AM-1: Physical devices and systems within the organization are inventoried | |||||||||||||||||||||||
3 | ID.AM-2: Software platforms and applications within the organization are inventoried | |||||||||||||||||||||||||
4 | ID.AM-3: Organizational communication and data flows are mapped | |||||||||||||||||||||||||
5 | ID.AM-4: External information systems are catalogued | |||||||||||||||||||||||||
6 | ID.AM-5: Resources (e.g., hardware, devices, data, time, and software) are prioritized based on their classification, criticality, and business value | |||||||||||||||||||||||||
7 | ID.AM-6: Cybersecurity roles and responsibilities for the entire workforce and third-party stakeholders (e.g., suppliers, customers, partners) are established | |||||||||||||||||||||||||
8 | Business Environment (ID.BE): Organizational goals, objectives, stakeholders, and activities are understood and prioritized; this information is used to inform cybersecurity roles, obligations, and risk management decisions. | ID.BE-1: The organization’s role in the supply chain is identified and communicated | ||||||||||||||||||||||||
9 | ID.BE-2: The organization’s place in critical infrastructure and its industry sector is identified and communicated | |||||||||||||||||||||||||
10 | ID.BE-3: Priorities for organizational mission, objectives, and activities are established and communicated | |||||||||||||||||||||||||
11 | ID.BE-4: Dependencies and critical functions for delivery of critical services are established | |||||||||||||||||||||||||
12 | ID.BE-5: Resilience requirements to support delivery of critical services are established for all operating states (e.g. under duress/attack, during recovery, normal operations) | |||||||||||||||||||||||||
13 | Governance (ID.GV): Policies, procedures, and procedures for managing and monitoring organizational, legal, risk, environmental, and operational requirements are understood and informed by cybersecurity risk management. | ID.GV-1: Organizational information security policy is established | ||||||||||||||||||||||||
14 | ID.GV-2: Information security roles & responsibilities are coordinated and aligned with internal roles and external partners | |||||||||||||||||||||||||
15 | ID.GV-3: Legal and regulatory requirements regarding cybersecurity, including privacy and civil liberties obligations, are understood and managed | |||||||||||||||||||||||||
16 | ID.GV-4: Governance and risk management processes address cybersecurity risks | |||||||||||||||||||||||||
17 | Risk Assessment (ID.RA): The organization recognizes the risk of cybersecurity in the organization's activities (including purpose, functions, image, or reputation), organizational assets, and individuals. | ID.RA-1: Asset vulnerabilities are identified and documented | ||||||||||||||||||||||||
18 | ID.RA-2: Cyber threat intelligence and vulnerability information is received from information sharing forums and sources | |||||||||||||||||||||||||
19 | ID.RA-3: Threats, both internal and external, are identified and documented | |||||||||||||||||||||||||
20 | ID.RA-4: Potential business impacts and likelihoods are identified | |||||||||||||||||||||||||
21 | ID.RA-5: Threats, vulnerabilities, likelihoods, and impacts are used to determine risk | |||||||||||||||||||||||||
22 | ID.RA-6: Risk responses are identified and prioritized | |||||||||||||||||||||||||
23 | Risk Management Strategy (ID.RM): Organizational values, barriers, risk tolerance, and speculation are established and used to support operational risk decisions. | ID.RM-1: Risk management processes are established, managed, and agreed to by organizational stakeholders | ||||||||||||||||||||||||
24 | ID.RM-2: Organizational risk tolerance is determined and clearly expressed | |||||||||||||||||||||||||
25 | ID.RM-3: The organization’s determination of risk tolerance is informed by its role in critical infrastructure and sector specific risk analysis | |||||||||||||||||||||||||
26 | Supply Chain Risk Management (ID.SC): Organizational priorities, barriers, risk tolerance, and assumptions are established and used to support risk decisions related to risk management of the supply chain. The organization has procedures for diagnosing, evaluating and managing the supply chain risk. | ID.SC-1: Cyber supply chain risk management processes are identified, established, assessed, managed, and agreed to by organizational stakeholders | ||||||||||||||||||||||||
27 | ID.SC-2: Identify, prioritize and assess suppliers and partners of critical information systems, components and services using a cyber supply chain risk assessment process | |||||||||||||||||||||||||
28 | ID.SC-3: Suppliers and partners are required by contract to implement appropriate measures designed to meet the objectives of the Information Security program or Cyber Supply Chain Risk Management Plan. | |||||||||||||||||||||||||
29 | ID.SC-4: Suppliers and partners are monitored to confirm that they have satisfied their obligations as required. Reviews of audits, summaries of test results, or other equivalent evaluations of suppliers/providers are conducted | |||||||||||||||||||||||||
30 | ID.SC-5: Response and recovery planning and testing are conducted with critical suppliers/providers | |||||||||||||||||||||||||
31 | PROTECT (PR) | Identity Management and Access Control (PR.AC): Access to tangible and intangible assets and associated facilities is limited to authorized users, processes, and devices, and is controlled in accordance with the tested risk of unauthorized access. | PR.AC-1: Identities and credentials are issued, managed, revoked, and audited for authorized devices, users, and processes | |||||||||||||||||||||||
32 | PR.AC-2: Physical access to assets is managed and protected | |||||||||||||||||||||||||
33 | PR.AC-3: Remote access is managed | |||||||||||||||||||||||||
34 | PR.AC-4: Access permissions and authorizations are managed, incorporating the principles of least privilege and separation of duties | |||||||||||||||||||||||||
35 | PR.AC-5: Network integrity is protected, incorporating network segregation where appropriate | |||||||||||||||||||||||||
36 | PR.AC-6: Identities are proofed and bound to credentials, and asserted in interactions when appropriate | |||||||||||||||||||||||||
37 | Awareness and Training (PR.AT): Organizational staff and partners are provided with cybersecurity awareness education and are adequately trained to perform their duties related to information security and obligations in line with related policies, procedures, and agreements. | PR.AT-1: All users are informed and trained | ||||||||||||||||||||||||
38 | PR.AT-2: Privileged users understand roles & responsibilities | |||||||||||||||||||||||||
39 | PR.AT-3: Third-party stakeholders (e.g., suppliers, customers, partners) understand roles & responsibilities | |||||||||||||||||||||||||
40 | PR.AT-4: Senior executives understand roles & responsibilities | |||||||||||||||||||||||||
41 | PR.AT-5: Physical and information security personnel understand roles & responsibilities | |||||||||||||||||||||||||
42 | Data Security (PR.DS): Information and records (data) are managed in accordance with the organization's risk strategy to protect privacy, integrity, and access to information. | PR.DS-1: Data-at-rest is protected | ||||||||||||||||||||||||
43 | PR.DS-2: Data-in-transit is protected | |||||||||||||||||||||||||
44 | PR.DS-3: Assets are formally managed throughout removal, transfers, and disposition | |||||||||||||||||||||||||
45 | PR.DS-4: Adequate capacity to ensure availability is maintained | |||||||||||||||||||||||||
46 | PR.DS-5: Protections against data leaks are implemented | |||||||||||||||||||||||||
47 | PR.DS-6: Integrity checking mechanisms are used to verify software, firmware, and information integrity | |||||||||||||||||||||||||
48 | PR.DS-7: The development and testing environment(s) are separate from the production environment | |||||||||||||||||||||||||
49 | PR.DS-8: Integrity checking mechanisms are used to verify hardware integrity | |||||||||||||||||||||||||
50 | Information Protection Processes and Procedures (PR.IP): Security policies (dealing with purpose, scope, roles, responsibilities, administrative responsibility, and communication between organizational organizations), procedures, and procedures are maintained and used to manage the protection of information systems and assets. | PR.IP-1: A baseline configuration of information technology/industrial control systems is created and maintained incorporating appropriate security principles (e.g. concept of least functionality) | ||||||||||||||||||||||||
51 | PR.IP-2: A System Development Life Cycle to manage systems is implemented | |||||||||||||||||||||||||
52 | PR.IP-3: Configuration change control processes are in place | |||||||||||||||||||||||||
53 | PR.IP-4: Backups of information are conducted, maintained, and tested periodically | |||||||||||||||||||||||||
54 | PR.IP-5: Policy and regulations regarding the physical operating environment for organizational assets are met | |||||||||||||||||||||||||
55 | PR.IP-6: Data is destroyed according to policy | |||||||||||||||||||||||||
56 | PR.IP-7: Protection processes are continuously improved | |||||||||||||||||||||||||
57 | PR.IP-8: Effectiveness of protection technologies is shared with appropriate parties | |||||||||||||||||||||||||
58 | PR.IP-9: Response plans (Incident Response and Business Continuity) and recovery plans (Incident Recovery and Disaster Recovery) are in place and managed | |||||||||||||||||||||||||
59 | PR.IP-10: Response and recovery plans are tested | |||||||||||||||||||||||||
60 | PR.IP-11: Cybersecurity is included in human resources practices (e.g., deprovisioning, personnel screening) | |||||||||||||||||||||||||
61 | PR.IP-12: A vulnerability management plan is developed and implemented | |||||||||||||||||||||||||
62 | Maintenance (PR.MA): Maintenance and adjustment of industrial controls and components of the information system is done in accordance with policies and procedures. | PR.MA-1: Maintenance and repair of organizational assets is performed and logged in a timely manner, with approved and controlled tools | ||||||||||||||||||||||||
63 | PR.MA-2: Remote maintenance of organizational assets is approved, logged, and performed in a manner that prevents unauthorized access | |||||||||||||||||||||||||
64 | Protective Technology (PR.PT): Technical security solutions are managed to ensure the security and durability of systems and assets, in accordance with related policies, procedures, and agreements. | PR.PT-1: Audit/log records are determined, documented, implemented, and reviewed in accordance with policy | ||||||||||||||||||||||||
65 | PR.PT-2: Removable media is protected and its use restricted according to policy | |||||||||||||||||||||||||
66 | PR.PT-3: The principle of least functionality is incorporated by configuring systems to provide only essential capabilities | |||||||||||||||||||||||||
67 | PR.PT-4: Communications and control networks are protected | |||||||||||||||||||||||||
68 | PR.PT-5: Systems operate in pre-defined functional states to achieve availability (e.g. under duress, under attack, during recovery, normal operations). | |||||||||||||||||||||||||
69 | DETECT (DE) | Anomalies and Events (DE.AE): Amazing work is timely and the potential impact of events is understandable. | DE.AE-1: A baseline of network operations and expected data flows for users and systems is established and managed | |||||||||||||||||||||||
70 | DE.AE-2: Detected events are analyzed to understand attack targets and methods | |||||||||||||||||||||||||
71 | DE.AE-3: Event data are aggregated and correlated from multiple sources and sensors | |||||||||||||||||||||||||
72 | DE.AE-4: Impact of events is determined | |||||||||||||||||||||||||
73 | DE.AE-5: Incident alert thresholds are established | |||||||||||||||||||||||||
74 | Security Continuous Monitoring (DE.CM): The information system and assets are periodically monitored to identify cybersecurity incidents and to ensure the effectiveness of security measures. | DE.CM-1: The network is monitored to detect potential cybersecurity events | ||||||||||||||||||||||||
75 | DE.CM-2: The physical environment is monitored to detect potential cybersecurity events | |||||||||||||||||||||||||
76 | DE.CM-3: Personnel activity is monitored to detect potential cybersecurity events | |||||||||||||||||||||||||
77 | DE.CM-4: Malicious code is detected | |||||||||||||||||||||||||
78 | DE.CM-5: Unauthorized mobile code is detected | |||||||||||||||||||||||||
79 | DE.CM-6: External service provider activity is monitored to detect potential cybersecurity events | |||||||||||||||||||||||||
80 | DE.CM-7: Monitoring for unauthorized personnel, connections, devices, and software is performed | |||||||||||||||||||||||||
81 | DE.CM-8: Vulnerability scans are performed | |||||||||||||||||||||||||
82 | Detection Processes (DE.DP): Procedures and procedures for detection are maintained and monitored to ensure timely and adequate awareness of emergencies. | DE.DP-1: Roles and responsibilities for detection are well defined to ensure accountability | ||||||||||||||||||||||||
83 | DE.DP-2: Detection activities comply with all applicable requirements | |||||||||||||||||||||||||
84 | DE.DP-3: Detection processes are tested | |||||||||||||||||||||||||
85 | DE.DP-4: Event detection information is communicated to appropriate parties | |||||||||||||||||||||||||
86 | DE.DP-5: Detection processes are continuously improved | |||||||||||||||||||||||||
87 | RESPOND (RS) | Response Planning (RS.RP): Response and procedures are developed and maintained, to ensure timely responses to online security events. | RS.RP-1: Response plan is executed during or after an event | |||||||||||||||||||||||
88 | Communications (RS.CO): Response activities are coordinated with internal and external stakeholders, as appropriate, to include external support from legal entities. | RS.CO-1: Personnel know their roles and order of operations when a response is needed | ||||||||||||||||||||||||
89 | RS.CO-2: Events are reported consistent with established criteria | |||||||||||||||||||||||||
90 | RS.CO-3: Information is shared consistent with response plans | |||||||||||||||||||||||||
91 | RS.CO-4: Coordination with stakeholders occurs consistent with response plans | |||||||||||||||||||||||||
92 | RS.CO-5: Voluntary information sharing occurs with external stakeholders to achieve broader cybersecurity situational awareness | |||||||||||||||||||||||||
93 | Analysis (RS.AN): Analysis was performed to ensure adequate response and support for recovery activities. | RS.AN-1: Notifications from detection systems are investigated | ||||||||||||||||||||||||
94 | RS.AN-2: The impact of the incident is understood | |||||||||||||||||||||||||
95 | RS.AN-3: Forensics are performed | |||||||||||||||||||||||||
96 | RS.AN-4: Incidents are categorized consistent with response plans | |||||||||||||||||||||||||
97 | Mitigation (RS.MI): Tasks were taken to prevent the expansion of the event, to reduce its effects, and to eliminate the incident. | RS.MI-1: Incidents are contained | ||||||||||||||||||||||||
98 | RS.MI-2: Incidents are mitigated | |||||||||||||||||||||||||
99 | RS.MI-3: Newly identified vulnerabilities are mitigated or documented as accepted risks | |||||||||||||||||||||||||
100 | Improvements (RS.IM): The organisation's response functions are enhanced by integrating lessons learned from current acquisition / response activities. | RS.IM-1: Response plans incorporate lessons learned |