northdakota103a
Board Regular
- Joined
- Apr 1, 2008
- Messages
- 65
Worksheet (WS 1) is my main list that I'm trying to map other data back to based on Section ID.
Worksheet 2 (WS 2) has the Section IDs in Worksheet 1 but they are all delimited in a list by semicolon by row. It' s annoying and I'm not sure how to join it back to WS 1, but here is what I want ~~
If WS Section ID is in a delimited list on a row in WS 2, I want the specific row data from WS 2 copied to WS 1 section that is a match. Note: The Section ID on WS 1 can exist in WS 2 delimited lists more than once, so there may be multiple rows on WS 2 applicable to WS 1 Section ID. Example: Section ID 5.4.1.1 only showed up once on WS 2, so I only had to copy the data over to row for Section 5.4.1.1 on WS 1 once. Section ID 5.4.1.2 showed up in 3 delimited list rows on WS 2, so I had to insert two blank rows on WS 1 under 5.4.1.2 (yellow highlights) and then copy over the WS 2 data into its applicable 3 in a 1:1 relationship.
If this is confusing, sorry - I am hopeful one of you all can help me. You guys and girls are so smart and I need a lightbulb to go off on this becuase I'm not sure how to describe it. I would like to programmatically be able to do this, but it does go beyond WS 2. I have about 10 other worksheets set up same in terms of the column headers, but amount of rows vary. Delimited lists are the same too, but some delimited lists are longer than what is in the WS 2 sheet below. I would also like to be able to pop in a new WS and be able to run the code and this continue to work.
Worksheet 2 (WS 2) has the Section IDs in Worksheet 1 but they are all delimited in a list by semicolon by row. It' s annoying and I'm not sure how to join it back to WS 1, but here is what I want ~~
If WS Section ID is in a delimited list on a row in WS 2, I want the specific row data from WS 2 copied to WS 1 section that is a match. Note: The Section ID on WS 1 can exist in WS 2 delimited lists more than once, so there may be multiple rows on WS 2 applicable to WS 1 Section ID. Example: Section ID 5.4.1.1 only showed up once on WS 2, so I only had to copy the data over to row for Section 5.4.1.1 on WS 1 once. Section ID 5.4.1.2 showed up in 3 delimited list rows on WS 2, so I had to insert two blank rows on WS 1 under 5.4.1.2 (yellow highlights) and then copy over the WS 2 data into its applicable 3 in a 1:1 relationship.
If this is confusing, sorry - I am hopeful one of you all can help me. You guys and girls are so smart and I need a lightbulb to go off on this becuase I'm not sure how to describe it. I would like to programmatically be able to do this, but it does go beyond WS 2. I have about 10 other worksheets set up same in terms of the column headers, but amount of rows vary. Delimited lists are the same too, but some delimited lists are longer than what is in the WS 2 sheet below. I would also like to be able to pop in a new WS and be able to run the code and this continue to work.
| database (5).xlsx | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| A | B | C | D | E | F | G | |||
| 2 | id | section | body | NIST ID | NIST SECTION | NIST BODY | ISOLINKS | ||
| 3 | 5 | 5 | Requirements related to ISO/IEC 27001 | ||||||
| 4 | 5.2 | 5.2 | Context of the organization | ||||||
| 5 | 5.2.1 | 5.2.1 - Understanding the organization and its context | The organization shall determine its role as a PII controller (including as a joint PII controller) and/or a PII processor. | ID.BE-2 | ID.BE-2 | The organization’s place in critical infrastructure and its industry sector is identified and communicated | 5.2.1 | ||
| 6 | 5.2.2 | 5.2.2 - Understanding the needs and expectations of interested parties | The organization shall include among its interested parties (see ISO/IEC 27001:2013, 4.2), those parties having interests or responsibilities associated with the processing of PII… | ||||||
| 7 | 5.2.3 | 5.2.3 - Determining the scope of the information security management system | A requirement additional to ISO/IEC 27001:2013, 4.3 is: When determining the scope of the PIMS, the organization shall include the processing of PII. NOTE The determination... | ||||||
| 8 | 5.2.4 | 5.2.4 - Information security management system | A requirement additional to ISO/IEC 27001:2013, 4.4 is: The organization shall establish, implement, maintain and continually improve a PIMS in accordance with the requirements of ISO/IEC... | ||||||
| 9 | 5.3 | 5.3 | Leadership | ||||||
| 10 | 5.3.1 | Leadership and commitment | The requirements stated in ISO/IEC 27001:2013, 5.1 along with the interpretation specified in 5.1, apply. | ||||||
| 11 | 5.3.2 | Policy | The requirements stated in ISO/IEC 27001:2013, 5.2 along with the interpretation specified in 5.1, apply. | ||||||
| 12 | 5.3.3 | Organizational roles, responsibilities and authorities | The requirements stated in ISO/IEC 27001:2013, 5.3 along with the interpretation specified in 5.1, apply. | ||||||
| 13 | 5.4 | 5.4 | Planning | ||||||
| 14 | 5.4.1 | 5.4.1 | Actions to address risks and opportunities | ||||||
| 15 | 5.4.1.1 | 5.4.1.1 - General | The requirements stated in ISO/IEC 27001:2013, 6.1.1 along with the interpretation specified in 5.1, apply. | ID.GV-4 | ID.GV-4 | Governance and risk management processes address cybersecurity risks | 5.4.1.1;5.4.1.2;5.4.1.3;5.4.2 | ||
| 16 | 5.4.1.2 | 5.4.1.2 - Information security risk assessment | ISO/IEC 27001:2013, 6.1.2 c) 1) is refined as follows: The organization shall apply the information security risk assessment process(s) to identify risks associated with the loss of... | ID.GV-4 | ID.GV-4 | Governance and risk management processes address cybersecurity risks | 5.4.1.1;5.4.1.2;5.4.1.3;5.4.2 | ||
| 17 | 5.4.1.2 | 5.4.1.2 - Information security risk assessment | ISO/IEC 27001:2013, 6.1.2 c) 1) is refined as follows: The organization shall apply the information security risk assessment process(s) to identify risks associated with the loss of... | ID.RA-3 | ID.RA-3 | Threats, both internal and external, are identified and documented | 5.4.1.2 | ||
| 18 | 5.4.1.2 | 5.4.1.2 - Information security risk assessment | ISO/IEC 27001:2013, 6.1.2 c) 1) is refined as follows: The organization shall apply the information security risk assessment process(s) to identify risks associated with the loss of... | ID.RA-4 | ID.RA-4 | Potential business impacts and likelihoods are identified | 5.4.1.2;6.13.1.6 | ||
ISO | |||||||||
| database (5).xlsx | ||||||
|---|---|---|---|---|---|---|
| A | B | C | D | |||
| 1 | NIST ID | NIST SECTION | NIST BODY | ISOLINKS | ||
| 2 | ID.AM | ID.AM Asset Management | The data, personnel, devices, systems, and facilities that enable the organization to achieve business purposes are identified and managed consistent with their relative importance to organizational objectives and the organization’s risk strategy. | |||
| 3 | ID.AM-1 | ID.AM-1 | Physical devices and systems within the organization are inventoried | 6.5.1.1;6.5.1.2 | ||
| 4 | ID.AM-2 | ID.AM-2 | Software platforms and applications within the organization are inventoried | 6.5.1.1;6.5.1.2;6.9.5.1 | ||
| 5 | ID.AM-3 | ID.AM-3 | Organizational communication and data flows are mapped | 6.10.2.1;6.10.2.2 | ||
| 6 | ID.AM-4 | ID.AM-4 | External information systems are catalogued | 6.8.2.6 | ||
| 7 | ID.AM-5 | ID.AM-5 | Resources (e.g., hardware, devices, data, time, personnel, and software) are prioritized based on their classification, criticality, and business value | 6.5.2.1 | ||
| 8 | 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 | 6.3.1.1 | ||
| 9 | ID.BE | ID.BE Business Environment | The organization’s mission, objectives, stakeholders, and activities are understood and prioritized; this information is used to inform cybersecurity roles, responsibilities, and risk management decisions. | |||
| 10 | ID.BE-1 | ID.BE-1 | The organization’s role in the supply chain is identified and communicated | 6.12.1.1;6.12.1.2;6.12.1.3;6.12.2.1;6.12.2.2 | ||
| 11 | ID.BE-2 | ID.BE-2 | The organization’s place in critical infrastructure and its industry sector is identified and communicated | 5.2.1 | ||
| 12 | ID.BE-3 | ID.BE-3 | Priorities for organizational mission, objectives, and activities are established and communicated | |||
| 13 | ID.BE-4 | ID.BE-4 | Dependencies and critical functions for delivery of critical services are established | 6.8.2.2;6.8.2.3;6.9.1.3 | ||
| 14 | ID.BE-5 | 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) | 6.8.1.4;6.14.1.1;6.14.1.2;6.14.2.1 | ||
| 15 | ID.GV | ID.GV Governance | The policies, procedures, and processes to manage and monitor the organization’s regulatory, legal, risk, environmental, and operational requirements are understood and inform the management of cybersecurity risk. | |||
| 16 | ID.GV-1 | ID.GV-1 | Organizational cybersecurity policy is established and communicated | 6.2.1.1 | ||
| 17 | ID.GV-2 | ID.GV-2 | Cybersecurity roles and responsibilities are coordinated and aligned with internal roles and external partners | 6.3.1.1;6.4.2.1;6.12.1.1 | ||
| 18 | ID.GV-3 | ID.GV-3 | Legal and regulatory requirements regarding cybersecurity, including privacy and civil liberties obligations, are understood and managed | 6.15.1.1;6.15.1.2;6.15.1.3;6.15.1.4;6.15.1.5 | ||
| 19 | ID.GV-4 | ID.GV-4 | Governance and risk management processes address cybersecurity risks | 5.4.1.1;5.4.1.2;5.4.1.3;5.4.2 | ||
| 20 | ID.RA | ID.RA Risk Assessment | The organization understands the cybersecurity risk to organizational operations (including mission, functions, image, or reputation), organizational assets, and individuals. | |||
| 21 | ID.RA-1 | ID.RA-1 | Asset vulnerabilities are identified and documented | 6.9.6.1;6.15.2.3 | ||
| 22 | ID.RA-2 | ID.RA-2 | Cyber threat intelligence is received from information sharing forums and sources | 6.3.1.4 | ||
| 23 | ID.RA-3 | ID.RA-3 | Threats, both internal and external, are identified and documented | 5.4.1.2 | ||
| 24 | ID.RA-4 | ID.RA-4 | Potential business impacts and likelihoods are identified | 5.4.1.2;6.13.1.6 | ||
| 25 | ID.RA-5 | ID.RA-5 | Threats, vulnerabilities, likelihoods, and impacts are used to determine risk | 6.9.6.1 | ||
| 26 | ID.RA-6 | ID.RA-6 | Risk responses are identified and prioritized | 5.4.1.3 | ||
| 27 | ID.RM | ID.RM Risk Management Strategy | The organization’s priorities, constraints, risk tolerances, and assumptions are established and used to support operational risk decisions. | |||
| 28 | ID.RM-1 | ID.RM-1 | Risk management processes are established, managed, and agreed to by organizational stakeholders | 5.4.1.3;5.6.3;5.7.3 | ||
| 29 | ID.RM-2 | ID.RM-2 | Organizational risk tolerance is determined and clearly expressed | 5.4.1.3;5.6.3 | ||
| 30 | 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 | 5.4.1.3;5.6.3 | ||
| 31 | ID.SC | ID.SC Supply Chain Risk Management | The organization’s priorities, constraints, risk tolerances, and assumptions are established and used to support risk decisions associated with managing supply chain risk. The organization has established and implemented the processes to identify, assess and manage supply chain risks. | |||
| 32 | ID.SC-1 | ID.SC-1 | Cyber supply chain risk management processes are identified, established, assessed, managed, and agreed to by organizational stakeholders | 6.12.1.1;6.12.1.2;6.12.1.3;6.12.2.1;6.12.2.2 | ||
| 33 | ID.SC-2 | ID.SC-2 | Suppliers and third party partners of information systems, components, and services are identified, prioritized, and assessed using a cyber supply chain risk assessment process | 6.12.2.1;6.12.2.2 | ||
| 34 | ID.SC-3 | ID.SC-3 | Contracts with suppliers and third-party partners are used to implement appropriate measures designed to meet the objectives of an organization’s cybersecurity program and Cyber Supply Chain Risk Management Plan. | 6.12.1.1;6.12.1.2;6.12.1.3 | ||
| 35 | ID.SC-4 | ID.SC-4 | Suppliers and third-party partners are routinely assessed using audits, test results, or other forms of evaluations to confirm they are meeting their contractual obligations. | 6.12.2.1;6.12.2.2 | ||
| 36 | ID.SC-5 | ID.SC-5 | Response and recovery planning and testing are conducted with suppliers and third-party providers | 6.14.1.3 | ||
| 37 | PR.AC | PR.AC Identity Management, Authentication and Access Control | Access to physical and logical assets and associated facilities is limited to authorized users, processes, and devices, and is managed consistent with the assessed risk of unauthorized access to authorized activities and transactions. | |||
| 38 | PR.AC-1 | PR.AC-1 | Identities and credentials are issued, managed, verified, revoked, and audited for authorized devices, users and processes | 6.6.2.1;6.6.2.2;6.6.2.3;6.6.2.4;6.6.2.6;6.6.3.1;6.6.4.2;6.6.4.3 | ||
| 39 | PR.AC-2 | PR.AC-2 | Physical access to assets is managed and protected | 6.8.1.1;6.8.1.2;6.8.1.3;6.8.1.4;6.8.1.5;6.8.1.6;6.8.2.1;6.8.2.3;6.8.2.5;6.8.2.6;6.8.2.7;6.8.2.8 | ||
| 40 | PR.AC-3 | PR.AC-3 | Remote access is managed | 6.3.2.1;6.3.2.2;6.8.2.6;6.10.1.1;6.10.2.1 | ||
| 41 | PR.AC-4 | PR.AC-4 | Access permissions and authorizations are managed, incorporating the principles of least privilege and separation of duties | 6.3.1.2;6.6.1.2;6.6.2.3;6.6.4.1;6.6.4.4;6.6.4.5 | ||
| 42 | PR.AC-5 | PR.AC-5 | Network integrity is protected (e.g., network segregation, network segmentation) | 6.10.1.1;6.10.1.3;6.10.2.1;6.11.1.2;6.11.1.3 | ||
| 43 | PR.AC-6 | PR.AC-6 | Identities are proofed and bound to credentials and asserted in interactions | 6.4.1.1;6.6.2.1 | ||
| 44 | PR.AC-7 | PR.AC-7 | Users, devices, and other assets are authenticated (e.g., single-factor, multi-factor) commensurate with the risk of the transaction (e.g., individuals’ security and privacy risks and other organizational risks) | 6.6.2.1;6.6.2.4;6.6.3.1;6.6.4.2;6.6.4.3;6.15.1.4 | ||
| 45 | PR.AT | PR.AT Awareness and Training | The organization’s personnel and partners are provided cybersecurity awareness education and are trained to perform their cybersecurity-related duties and responsibilities consistent with related policies, procedures, and agreements. | |||
| 46 | PR.AT-1 | PR.AT-1 | All users are informed and trained | 6.4.2.2;6.9.2.1 | ||
| 47 | PR.AT-2 | PR.AT-2 | Privileged users understand their roles and responsibilities | 6.3.1.1;6.4.2.2 | ||
| 48 | PR.AT-3 | PR.AT-3 | Third-party stakeholders (e.g., suppliers, customers, partners) understand their roles and responsibilities | 6.3.1.1;6.4.2.1;6.4.2.2 | ||
| 49 | PR.AT-4 | PR.AT-4 | Senior executives understand their roles and responsibilities | 6.3.1.1;6.4.2.2 | ||
| 50 | PR.AT-5 | PR.AT-5 | Physical and cybersecurity personnel understand their roles and responsibilities | 6.3.1.1;6.4.2.2 | ||
| 51 | PR.DS | PR.DS Data Security | Information and records (data) are managed consistent with the organization’s risk strategy to protect the confidentiality, integrity, and availability of information. | |||
| 52 | PR.DS-1 | PR.DS-1 | Data-at-rest is protected | 6.5.2.3 | ||
| 53 | PR.DS-2 | PR.DS-2 | Data-in-transit is protected | 6.5.2.3;6.10.1.1;6.10.2.1;6.10.2.3;6.11.1.2;6.11.1.3 | ||
| 54 | PR.DS-3 | PR.DS-3 | Assets are formally managed throughout removal, transfers, and disposition | 6.5.2.3;6.5.3.1;6.5.3.2;6.5.3.3;6.8.2.5;6.8.2.7 | ||
| 55 | PR.DS-4 | PR.DS-4 | Adequate capacity to ensure availability is maintained | 6.9.1.3;6.14.2.1 | ||
| 56 | PR.DS-5 | PR.DS-5 | Protections against data leaks are implemented | 6.3.1.2;6.4.1.1;6.4.1.2;6.4.3.1;6.5.2.2;6.5.2.3;6.6.1.1;6.6.1.2;6.6.2.3;6.6.4.1;6.6.4.4;6.6.4.5;6.7.1.1;6.8.1.4;6.8.1.5;6.8.2.1;6.10.1.1;6.10.1.3;6.10.2.1;6.10.2.3;6.10.2.4;6.11.1.2;6.11.1.3 | ||
| 57 | PR.DS-6 | PR.DS-6 | Integrity checking mechanisms are used to verify software, firmware, and information integrity | 6.9.2.1;6.9.5.1;6.11.1.2;6.11.1.3;6.11.2.4 | ||
| 58 | PR.DS-7 | PR.DS-7 | The development and testing environment(s) are separate from the production environment | 6.9.1.4 | ||
| 59 | PR.DS-8 | PR.DS-8 | Integrity checking mechanisms are used to verify hardware integrity | 6.8.2.4 | ||
| 60 | PR.IP | PR.IP Information Protection Processes and Procedures | Security policies (that address purpose, scope, roles, responsibilities, management commitment, and coordination among organizational entities), processes, and procedures are maintained and used to manage protection of information systems and assets. | |||
| 61 | PR.IP-1 | PR.IP-1 | A baseline configuration of information technology/industrial control systems is created and maintained incorporating security principles (e.g. concept of least functionality) | 6.9.1.2;6.9.5.1;6.9.6.2;6.11.2.2;6.11.2.3;6.11.2.4 | ||
| 62 | PR.IP-2 | PR.IP-2 | A System Development Life Cycle to manage systems is implemented | 6.3.1.5;6.11.1.1;6.11.2.1;6.11.2.5 | ||
| 63 | PR.IP-3 | PR.IP-3 | Configuration change control processes are in place | 6.9.1.2;6.9.5.1;6.9.6.2;6.11.2.2;6.11.2.3;6.11.2.4 | ||
| 64 | PR.IP-4 | PR.IP-4 | Backups of information are conducted, maintained, and tested | 6.9.3.1;6.14.1.2;6.14.1.3;6.15.1.3 | ||
| 65 | PR.IP-5 | PR.IP-5 | Policy and regulations regarding the physical operating environment for organizational assets are met | 6.8.1.4;6.8.2.1;6.8.2.2;6.8.2.3 | ||
| 66 | PR.IP-6 | PR.IP-6 | Data is destroyed according to policy | 6.5.2.3;6.5.3.1;6.5.3.2;6.8.2.7 | ||
| 67 | PR.IP-7 | PR.IP-7 | Protection processes are improved | 5.7.1;5.7.2;5.7.3;5.8.1;5.8.2;6.13.1.6 | ||
| 68 | PR.IP-8 | PR.IP-8 | Effectiveness of protection technologies is shared | 6.13.1.6 | ||
| 69 | 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 | 6.13.1.1;6.14.1.1;6.14.1.2;6.14.1.3 | ||
| 70 | PR.IP-10 | PR.IP-10 | Response and recovery plans are tested | 6.14.1.3 | ||
| 71 | PR.IP-11 | PR.IP-11 | Cybersecurity is included in human resources practices (e.g., deprovisioning, personnel screening) | 6.4.1.1;6.4.1.2;6.4.2.1;6.4.2.2;6.4.2.3;6.4.3.1;6.5.1.4 | ||
| 72 | PR.IP-12 | PR.IP-12 | A vulnerability management plan is developed and implemented | 6.9.6.1;6.11.2.3;6.13.1.3;6.15.2.2;6.15.2.3 | ||
| 73 | PR.MA | PR.MA Maintenance | Maintenance and repairs of industrial control and information system components are performed consistent with policies and procedures. | |||
| 74 | PR.MA-1 | PR.MA-1 | Maintenance and repair of organizational assets are performed and logged, with approved and controlled tools | 6.8.1.2;6.8.2.4;6.8.2.5;6.8.2.6 | ||
| 75 | PR.MA-2 | PR.MA-2 | Remote maintenance of organizational assets is approved, logged, and performed in a manner that prevents unauthorized access | 6.8.2.4;6.12.1.1;6.12.2.1 | ||
| 76 | PR.PT | PR.PT Protective Technology | ||||
| 77 | PR.PT-1 | PR.PT-1 | Audit/log records are determined, documented, implemented, and reviewed in accordance with policy | 6.9.4.1;6.9.4.2;6.9.4.3;6.9.4.4;6.9.7.1 | ||
| 78 | PR.PT-2 | PR.PT-2 | Removable media is protected and its use restricted according to policy | 6.5.2.1;6.5.2.2;6.5.2.3;6.5.3.1;6.5.3.3;6.8.2.9 | ||
| 79 | PR.PT-3 | PR.PT-3 | The principle of least functionality is incorporated by configuring systems to provide only essential capabilities | 6.6.1.2 | ||
| 80 | PR.PT-4 | PR.PT-4 | Communications and control networks are protected | 6.10.1.1;6.10.2.1;6.11.1.3 | ||
| 81 | PR.PT-5 | PR.PT-5 | Mechanisms (e.g., failsafe, load balancing, hot swap) are implemented to achieve resilience requirements in normal and adverse situations | 6.14.1.2;6.14.2.1 | ||
| 82 | DE.AE | DE.AE Anomalies and Events | Anomalous activity is detected and the potential impact of events is understood. | |||
| 83 | DE.AE-1 | DE.AE-1 | A baseline of network operations and expected data flows for users and systems is established and managed | 6.9.1.1;6.9.1.2;6.10.1.1;6.10.1.2 | ||
| 84 | DE.AE-2 | DE.AE-2 | Detected events are analyzed to understand attack targets and methods | 6.9.4.1;6.13.1.1;6.13.1.4 | ||
| 85 | DE.AE-3 | DE.AE-3 | Event data are collected and correlated from multiple sources and sensors | 6.9.4.1;6.13.1.7 | ||
| 86 | DE.AE-4 | DE.AE-4 | Impact of events is determined | 6.13.1.4 | ||
| 87 | DE.AE-5 | DE.AE-5 | Incident alert thresholds are established | 6.13.1.4 | ||
| 88 | DE.CM | DE.CM Security Continuous Monitoring | The information system and assets are monitored to identify cybersecurity events and verify the effectiveness of protective measures. | |||
| 89 | DE.CM-1 | DE.CM-1 | The network is monitored to detect potential cybersecurity events | |||
| 90 | DE.CM-2 | DE.CM-2 | The physical environment is monitored to detect potential cybersecurity events | 6.8.1.1 | ||
| 91 | DE.CM-3 | DE.CM-3 | Personnel activity is monitored to detect potential cybersecurity events | 6.8.1.2 | ||
| 92 | DE.CM-4 | DE.CM-4 | Malicious code is detected | 6.9.2.1 | ||
| 93 | DE.CM-5 | DE.CM-5 | Unauthorized mobile code is detected | 6.9.5.1;6.9.6.2 | ||
| 94 | DE.CM-6 | DE.CM-6 | External service provider activity is monitored to detect potential cybersecurity events | 6.9.5.1;6.9.6.2 | ||
| 95 | DE.CM-7 | DE.CM-7 | Monitoring for unauthorized personnel, connections, devices, and software is performed | 6.9.4.1;6.11.2.7;6.12.2.1 | ||
| 96 | DE.CM-8 | DE.CM-8 | Vulnerability scans are performed | 6.9.6.1 | ||
| 97 | DE.DP | DE.DP Detection Processes | Detection processes and procedures are maintained and tested to ensure awareness of anomalous events. | |||
| 98 | DE.DP-1 | DE.DP-1 | Roles and responsibilities for detection are well defined to ensure accountability | 6.3.1.1;6.4.2.2 | ||
| 99 | DE.DP-2 | DE.DP-2 | Detection activities comply with all applicable requirements | 6.15.1.4;6.15.2.2;6.15.2.3 | ||
| 100 | DE.DP-3 | DE.DP-3 | Detection processes are tested | 6.11.2.8 | ||
| 101 | DE.DP-4 | DE.DP-4 | Event detection information is communicated | 6.13.1.2;6.13.1.3 | ||
| 102 | DE.DP-5 | DE.DP-5 | Detection processes are continuously improved | 6.13.1.6 | ||
| 103 | RS.RP | RS.RP Response Planning | Response processes and procedures are executed and maintained, to ensure response to detected cybersecurity incidents. | |||
| 104 | RS.RP-1 | RS.RP-1 | Response plan is executed during or after an incident | 6.13.1.5 | ||
| 105 | RS.CO | RS.CO Communications | Response activities are coordinated with internal and external stakeholders (e.g. external support from law enforcement agencies). | |||
| 106 | RS.CO-1 | RS.CO-1 | Personnel know their roles and order of operations when a response is needed | 6.3.1.1;6.4.2.2;6.13.1.1 | ||
| 107 | RS.CO-2 | RS.CO-2 | Incidents are reported consistent with established criteria | 6.3.1.3;6.13.1.2 | ||
| 108 | RS.CO-3 | RS.CO-3 | Information is shared consistent with response plans | 6.13.1.2;5.5.4 | ||
| 109 | RS.CO-4 | RS.CO-4 | Coordination with stakeholders occurs consistent with response plans | 5.5.4 | ||
| 110 | RS.CO-5 | RS.CO-5 | Voluntary information sharing occurs with external stakeholders to achieve broader cybersecurity situational awareness | 6.3.1.4 | ||
| 111 | RS.AN | RS.AN Analysis | Analysis is conducted to ensure effective response and support recovery activities. | |||
| 112 | RS.AN-1 | RS.AN-1 | Notifications from detection systems are investigated | 6.9.4.1;6.9.4.3;6.13.1.5 | ||
| 113 | RS.AN-2 | RS.AN-2 | The impact of the incident is understood | 6.13.1.4;6.13.1.6 | ||
| 114 | RS.AN-3 | RS.AN-3 | Forensics are performed | 6.13.1.7 | ||
| 115 | RS.AN-4 | RS.AN-4 | Incidents are categorized consistent with response plans | 6.13.1.4 | ||
| 116 | RS.AN-5 | RS.AN-5 | Processes are established to receive, analyze and respond to vulnerabilities disclosed to the organization from internal and external sources (e.g. internal testing, security bulletins, or security researchers) | |||
| 117 | RS.MI | RS.MI Mitigation | Activities are performed to prevent expansion of an event, mitigate its effects, and resolve the incident. | |||
| 118 | RS.MI-1 | RS.MI-1 | Incidents are contained | 6.9.2.1;6.13.1.5 | ||
| 119 | RS.MI-2 | RS.MI-2 | Incidents are mitigated | 6.9.2.1;6.13.1.5 | ||
| 120 | RS.MI-3 | RS.MI-3 | Newly identified vulnerabilities are mitigated or documented as accepted risks | 6.9.6.1 | ||
| 121 | RS.IM | RS.IM Improvements | Organizational response activities are improved by incorporating lessons learned from current and previous detection/response activities. | |||
| 122 | RS.IM-1 | RS.IM-1 | Response plans incorporate lessons learned | 6.13.1.6;5.8.1;5.8.2 | ||
| 123 | RS.IM-2 | RS.IM-2 | Response strategies are updated | 6.13.1.6;5.8.1;5.8.2 | ||
| 124 | RC.RP | RC.RP Recovery Planning | Recovery processes and procedures are executed and maintained to ensure restoration of systems or assets affected by cybersecurity incidents. | |||
| 125 | RC.RP-1 | RC.RP-1 | Recovery plan is executed during or after a cybersecurity incident | 6.13.1.5 | ||
| 126 | RC.IM | RC.IM Improvements | Recovery planning and processes are improved by incorporating lessons learned into future activities. | |||
| 127 | RC.IM-1 | RC.IM-1 | Recovery plans incorporate lessons learned | 6.13.1.6;5.8.1;5.8.2 | ||
| 128 | RC.IM-2 | RC.IM-2 | Recovery strategies are updated | 6.13.1.6;5.8.1;5.8.2 | ||
| 129 | RC.CO | RC.CO Communications | Restoration activities are coordinated with internal and external parties (e.g. coordinating centers, Internet Service Providers, owners of attacking systems, victims, other CSIRTs, and vendors). | |||
| 130 | RC.CO-1 | RC.CO-1 | Public relations are managed | 6.3.1.4;5.5.4 | ||
| 131 | RC.CO-2 | RC.CO-2 | Reputation is repaired after an incident | 5.5.4 | ||
| 132 | RC.CO-3 | RC.CO-3 | Recovery activities are communicated to internal and external stakeholders as well as executive and management teams | 5.5.4 | ||
NIST CF | ||||||
