{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV", "element_type": "function", "text": "The organization's cybersecurity risk management strategy, expectations, and policy are established, communicated, and monitored", "title": "GOVERN"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.OC", "element_type": "category", "text": "The circumstances - mission, stakeholder expectations, dependencies, and legal, regulatory, and contractual requirements - surrounding the organization's cybersecurity risk management decisions are understood", "title": "Organizational Context"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.OC-01", "element_type": "subcategory", "text": "The organizational mission is understood and informs cybersecurity risk management", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.OC-01.001", "element_type": "implementation_example", "text": "Share the organization's mission (e.g., through vision and mission statements, marketing, and service strategies) to provide a basis for identifying risks that may impede that mission", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.OC-02", "element_type": "subcategory", "text": "Internal and external stakeholders are understood, and their needs and expectations regarding cybersecurity risk management are understood and considered", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.OC-02.002", "element_type": "implementation_example", "text": "Identify relevant internal stakeholders and their cybersecurity-related expectations (e.g., performance and risk expectations of officers, directors, and advisors; cultural expectations of employees)", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.OC-02.003", "element_type": "implementation_example", "text": "Identify relevant external stakeholders and their cybersecurity-related expectations (e.g., privacy expectations of customers, business expectations of partnerships, compliance expectations of regulators, ethics expectations of society)", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.OC-03", "element_type": "subcategory", "text": "Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.OC-03.004", "element_type": "implementation_example", "text": "Determine a process to track and manage legal and regulatory requirements regarding protection of individuals' information (e.g., Health Insurance Portability and Accountability Act, California Consumer Privacy Act, General Data Protection Regulation)", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.OC-03.005", "element_type": "implementation_example", "text": "Determine a process to track and manage contractual requirements for cybersecurity management of supplier, customer, and partner information", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.OC-03.006", "element_type": "implementation_example", "text": "Align the organization's cybersecurity strategy with legal, regulatory, and contractual requirements", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.OC-04", "element_type": "subcategory", "text": "Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organization are understood and communicated", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.OC-04.007", "element_type": "implementation_example", "text": "Establish criteria for determining the criticality of capabilities and services as viewed by internal and external stakeholders", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.OC-04.008", "element_type": "implementation_example", "text": "Determine (e.g., from a business impact analysis) assets and business operations that are vital to achieving mission objectives and the potential impact of a loss (or partial loss) of such operations", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.OC-04.009", "element_type": "implementation_example", "text": "Establish and communicate resilience objectives (e.g., recovery time objectives) for delivering critical capabilities and services in various operating states (e.g., under attack, during recovery, normal operation)", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.OC-05", "element_type": "subcategory", "text": "Outcomes, capabilities, and services that the organization depends on are understood and communicated", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.OC-05.010", "element_type": "implementation_example", "text": "Create an inventory of the organization's dependencies on external resources (e.g., facilities, cloud-based hosting providers) and their relationships to organizational assets and business functions", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.OC-05.011", "element_type": "implementation_example", "text": "Identify and document external dependencies that are potential points of failure for the organization's critical capabilities and services, and share that information with appropriate personnel", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RM", "element_type": "category", "text": "The organization's priorities, constraints, risk tolerance and appetite statements, and assumptions are established, communicated, and used to support operational risk decisions", "title": "Risk Management Strategy"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RM-01", "element_type": "subcategory", "text": "Risk management objectives are established and agreed to by organizational stakeholders", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RM-01.012", "element_type": "implementation_example", "text": "Update near-term and long-term cybersecurity risk management objectives as part of annual strategic planning and when major changes occur", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RM-01.013", "element_type": "implementation_example", "text": "Establish measurable objectives for cybersecurity risk management (e.g., manage the quality of user training, ensure adequate risk protection for industrial control systems)", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RM-01.014", "element_type": "implementation_example", "text": "Senior leaders agree about cybersecurity objectives and use them for measuring and managing risk and performance", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RM-02", "element_type": "subcategory", "text": "Risk appetite and risk tolerance statements are established, communicated, and maintained", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RM-02.015", "element_type": "implementation_example", "text": "Determine and communicate risk appetite statements that convey expectations about the appropriate level of risk for the organization", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RM-02.016", "element_type": "implementation_example", "text": "Translate risk appetite statements into specific, measurable, and broadly understandable risk tolerance statements", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RM-02.017", "element_type": "implementation_example", "text": "Refine organizational objectives and risk appetite periodically based on known risk exposure and residual risk", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RM-03", "element_type": "subcategory", "text": "Cybersecurity risk management activities and outcomes are included in enterprise risk management processes", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RM-03.018", "element_type": "implementation_example", "text": "Aggregate and manage cybersecurity risks alongside other enterprise risks (e.g., compliance, financial, operational, regulatory, reputational, safety)", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RM-03.019", "element_type": "implementation_example", "text": "Include cybersecurity risk managers in enterprise risk management planning", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RM-03.020", "element_type": "implementation_example", "text": "Establish criteria for escalating cybersecurity risks within enterprise risk management", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RM-04", "element_type": "subcategory", "text": "Strategic direction that describes appropriate risk response options is established and communicated", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RM-04.021", "element_type": "implementation_example", "text": "Specify criteria for accepting and avoiding cybersecurity risk for various classifications of data", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RM-04.022", "element_type": "implementation_example", "text": "Determine whether to purchase cybersecurity insurance", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RM-04.023", "element_type": "implementation_example", "text": "Document conditions under which shared responsibility models are acceptable (e.g., outsourcing certain cybersecurity functions, having a third party perform financial transactions on behalf of the organization, using public cloud-based services)", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RM-05", "element_type": "subcategory", "text": "Lines of communication across the organization are established for cybersecurity risks, including risks from suppliers and other third parties", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RM-05.024", "element_type": "implementation_example", "text": "Determine how to update senior executives, directors, and management on the organization's cybersecurity posture at agreed-upon intervals", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RM-05.025", "element_type": "implementation_example", "text": "Identify how all departments across the organization - such as management, operations, internal auditors, legal, acquisition, physical security, and HR - will communicate with each other about cybersecurity risks", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RM-06", "element_type": "subcategory", "text": "A standardized method for calculating, documenting, categorizing, and prioritizing cybersecurity risks is established and communicated", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RM-06.026", "element_type": "implementation_example", "text": "Establish criteria for using a quantitative approach to cybersecurity risk analysis, and specify probability and exposure formulas", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RM-06.027", "element_type": "implementation_example", "text": "Create and use templates (e.g., a risk register) to document cybersecurity risk information (e.g., risk description, exposure, treatment, and ownership)", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RM-06.028", "element_type": "implementation_example", "text": "Establish criteria for risk prioritization at the appropriate levels within the enterprise", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RM-06.029", "element_type": "implementation_example", "text": "Use a consistent list of risk categories to support integrating, aggregating, and comparing cybersecurity risks", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RM-07", "element_type": "subcategory", "text": "Strategic opportunities (i.e., positive risks) are characterized and are included in organizational cybersecurity risk discussions", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RM-07.030", "element_type": "implementation_example", "text": "Define and communicate guidance and methods for identifying opportunities and including them in risk discussions (e.g., strengths, weaknesses, opportunities, and threats [SWOT] analysis)", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RM-07.031", "element_type": "implementation_example", "text": "Identify stretch goals and document them", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RM-07.032", "element_type": "implementation_example", "text": "Calculate, document, and prioritize positive risks alongside negative risks", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RR", "element_type": "category", "text": "Cybersecurity roles, responsibilities, and authorities to foster accountability, performance assessment, and continuous improvement are established and communicated", "title": "Roles, Responsibilities, and Authorities"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RR-01", "element_type": "subcategory", "text": "Organizational leadership is responsible and accountable for cybersecurity risk and fosters a culture that is risk-aware, ethical, and continually improving", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RR-01.033", "element_type": "implementation_example", "text": "Leaders (e.g., directors) agree on their roles and responsibilities in developing, implementing, and assessing the organization's cybersecurity strategy", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RR-01.034", "element_type": "implementation_example", "text": "Share leaders' expectations regarding a secure and ethical culture, especially when current events present the opportunity to highlight positive or negative examples of cybersecurity risk management", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RR-01.035", "element_type": "implementation_example", "text": "Leaders direct the CISO to maintain a comprehensive cybersecurity risk strategy and review and update it at least annually and after major events", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RR-01.036", "element_type": "implementation_example", "text": "Conduct reviews to ensure adequate authority and coordination among those responsible for managing cybersecurity risk", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RR-02", "element_type": "subcategory", "text": "Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RR-02.037", "element_type": "implementation_example", "text": "Document risk management roles and responsibilities in policy", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RR-02.038", "element_type": "implementation_example", "text": "Document who is responsible and accountable for cybersecurity risk management activities and how those teams and individuals are to be consulted and informed", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RR-02.039", "element_type": "implementation_example", "text": "Include cybersecurity responsibilities and performance requirements in personnel descriptions", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RR-02.040", "element_type": "implementation_example", "text": "Document performance goals for personnel with cybersecurity risk management responsibilities, and periodically measure performance to identify areas for improvement", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RR-02.041", "element_type": "implementation_example", "text": "Clearly articulate cybersecurity responsibilities within operations, risk functions, and internal audit functions", "title": "Ex5"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RR-03", "element_type": "subcategory", "text": "Adequate resources are allocated commensurate with the cybersecurity risk strategy, roles, responsibilities, and policies", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RR-03.042", "element_type": "implementation_example", "text": "Conduct periodic management reviews to ensure that those given cybersecurity risk management responsibilities have the necessary authority", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RR-03.043", "element_type": "implementation_example", "text": "Identify resource allocation and investment in line with risk tolerance and response", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RR-03.044", "element_type": "implementation_example", "text": "Provide adequate and sufficient people, process, and technical resources to support the cybersecurity strategy", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RR-04", "element_type": "subcategory", "text": "Cybersecurity is included in human resources practices", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RR-04.045", "element_type": "implementation_example", "text": "Integrate cybersecurity risk management considerations into human resources processes (e.g., personnel screening, onboarding, change notification, offboarding)", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RR-04.046", "element_type": "implementation_example", "text": "Consider cybersecurity knowledge to be a positive factor in hiring, training, and retention decisions", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RR-04.047", "element_type": "implementation_example", "text": "Conduct background checks prior to onboarding new personnel for sensitive roles, and periodically repeat background checks for personnel with such roles", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.RR-04.048", "element_type": "implementation_example", "text": "Define and enforce obligations for personnel to be aware of, adhere to, and uphold security policies as they relate to their roles", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.PO", "element_type": "category", "text": "Organizational cybersecurity policy is established, communicated, and enforced", "title": "Policy"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.PO-01", "element_type": "subcategory", "text": "Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.PO-01.049", "element_type": "implementation_example", "text": "Create, disseminate, and maintain an understandable, usable risk management policy with statements of management intent, expectations, and direction", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.PO-01.050", "element_type": "implementation_example", "text": "Periodically review policy and supporting processes and procedures to ensure that they align with risk management strategy objectives and priorities, as well as the high-level direction of the cybersecurity policy", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.PO-01.051", "element_type": "implementation_example", "text": "Require approval from senior management on policy", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.PO-01.052", "element_type": "implementation_example", "text": "Communicate cybersecurity risk management policy and supporting processes and procedures across the organization", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.PO-01.053", "element_type": "implementation_example", "text": "Require personnel to acknowledge receipt of policy when first hired, annually, and whenever policy is updated", "title": "Ex5"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.PO-02", "element_type": "subcategory", "text": "Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.PO-02.054", "element_type": "implementation_example", "text": "Update policy based on periodic reviews of cybersecurity risk management results to ensure that policy and supporting processes and procedures adequately maintain risk at an acceptable level", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.PO-02.055", "element_type": "implementation_example", "text": "Provide a timeline for reviewing changes to the organization's risk environment (e.g., changes in risk or in the organization's mission objectives), and communicate recommended policy updates", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.PO-02.056", "element_type": "implementation_example", "text": "Update policy to reflect changes in legal and regulatory requirements", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.PO-02.057", "element_type": "implementation_example", "text": "Update policy to reflect changes in technology (e.g., adoption of artificial intelligence) and changes to the business (e.g., acquisition of a new business, new contract requirements)", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.OV", "element_type": "category", "text": "Results of organization-wide cybersecurity risk management activities and performance are used to inform, improve, and adjust the risk management strategy", "title": "Oversight"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.OV-01", "element_type": "subcategory", "text": "Cybersecurity risk management strategy outcomes are reviewed to inform and adjust strategy and direction", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.OV-01.058", "element_type": "implementation_example", "text": "Measure how well the risk management strategy and risk results have helped leaders make decisions and achieve organizational objectives", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.OV-01.059", "element_type": "implementation_example", "text": "Examine whether cybersecurity risk strategies that impede operations or innovation should be adjusted", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.OV-02", "element_type": "subcategory", "text": "The cybersecurity risk management strategy is reviewed and adjusted to ensure coverage of organizational requirements and risks", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.OV-02.060", "element_type": "implementation_example", "text": "Review audit findings to confirm whether the existing cybersecurity strategy has ensured compliance with internal and external requirements", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.OV-02.061", "element_type": "implementation_example", "text": "Review the performance oversight of those in cybersecurity-related roles to determine whether policy changes are necessary", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.OV-02.062", "element_type": "implementation_example", "text": "Review strategy in light of cybersecurity incidents", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.OV-03", "element_type": "subcategory", "text": "Organizational cybersecurity risk management performance is evaluated and reviewed for adjustments needed", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.OV-03.063", "element_type": "implementation_example", "text": "Review key performance indicators (KPIs) to ensure that organization-wide policies and procedures achieve objectives", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.OV-03.064", "element_type": "implementation_example", "text": "Review key risk indicators (KRIs) to identify risks the organization faces, including likelihood and potential impact", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.OV-03.065", "element_type": "implementation_example", "text": "Collect and communicate metrics on cybersecurity risk management with senior leadership", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC", "element_type": "category", "text": "Cyber supply chain risk management processes are identified, established, managed, monitored, and improved by organizational stakeholders", "title": "Cybersecurity Supply Chain Risk Management"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-01", "element_type": "subcategory", "text": "A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organizational stakeholders", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-01.066", "element_type": "implementation_example", "text": "Establish a strategy that expresses the objectives of the cybersecurity supply chain risk management program", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-01.067", "element_type": "implementation_example", "text": "Develop the cybersecurity supply chain risk management program, including a plan (with milestones), policies, and procedures that guide implementation and improvement of the program, and share the policies and procedures with the organizational stakeholders", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-01.068", "element_type": "implementation_example", "text": "Develop and implement program processes based on the strategy, objectives, policies, and procedures that are agreed upon and performed by the organizational stakeholders", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-01.069", "element_type": "implementation_example", "text": "Establish a cross-organizational mechanism that ensures alignment between functions that contribute to cybersecurity supply chain risk management, such as cybersecurity, IT, operations, legal, human resources, and engineering", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-02", "element_type": "subcategory", "text": "Cybersecurity roles and responsibilities for suppliers, customers, and partners are established, communicated, and coordinated internally and externally", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-02.070", "element_type": "implementation_example", "text": "Identify one or more specific roles or positions that will be responsible and accountable for planning, resourcing, and executing cybersecurity supply chain risk management activities", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-02.071", "element_type": "implementation_example", "text": "Document cybersecurity supply chain risk management roles and responsibilities in policy", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-02.072", "element_type": "implementation_example", "text": "Create responsibility matrixes to document who will be responsible and accountable for cybersecurity supply chain risk management activities and how those teams and individuals will be consulted and informed", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-02.073", "element_type": "implementation_example", "text": "Include cybersecurity supply chain risk management responsibilities and performance requirements in personnel descriptions to ensure clarity and improve accountability", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-02.074", "element_type": "implementation_example", "text": "Document performance goals for personnel with cybersecurity risk management-specific responsibilities, and periodically measure them to demonstrate and improve performance", "title": "Ex5"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-02.075", "element_type": "implementation_example", "text": "Develop roles and responsibilities for suppliers, customers, and business partners to address shared responsibilities for applicable cybersecurity risks, and integrate them into organizational policies and applicable third-party agreements", "title": "Ex6"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-02.076", "element_type": "implementation_example", "text": "Internally communicate cybersecurity supply chain risk management roles and responsibilities for third parties", "title": "Ex7"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-02.077", "element_type": "implementation_example", "text": "Establish rules and protocols for information sharing and reporting processes between the organization and its suppliers", "title": "Ex8"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-03", "element_type": "subcategory", "text": "Cybersecurity supply chain risk management is integrated into cybersecurity and enterprise risk management, risk assessment, and improvement processes", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-03.078", "element_type": "implementation_example", "text": "Identify areas of alignment and overlap with cybersecurity and enterprise risk management", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-03.079", "element_type": "implementation_example", "text": "Establish integrated control sets for cybersecurity risk management and cybersecurity supply chain risk management", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-03.080", "element_type": "implementation_example", "text": "Integrate cybersecurity supply chain risk management into improvement processes", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-03.081", "element_type": "implementation_example", "text": "Escalate material cybersecurity risks in supply chains to senior management, and address them at the enterprise risk management level", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-04", "element_type": "subcategory", "text": "Suppliers are known and prioritized by criticality", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-04.082", "element_type": "implementation_example", "text": "Develop criteria for supplier criticality based on, for example, the sensitivity of data processed or possessed by suppliers, the degree of access to the organization's systems, and the importance of the products or services to the organization's mission", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-04.083", "element_type": "implementation_example", "text": "Keep a record of all suppliers, and prioritize suppliers based on the criticality criteria", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-05", "element_type": "subcategory", "text": "Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third parties", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-05.084", "element_type": "implementation_example", "text": "Establish security requirements for suppliers, products, and services commensurate with their criticality level and potential impact if compromised", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-05.085", "element_type": "implementation_example", "text": "Include all cybersecurity and supply chain requirements that third parties must follow and how compliance with the requirements may be verified in default contractual language", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-05.086", "element_type": "implementation_example", "text": "Define the rules and protocols for information sharing between the organization and its suppliers and sub-tier suppliers in agreements", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-05.087", "element_type": "implementation_example", "text": "Manage risk by including security requirements in agreements based on their criticality and potential impact if compromised", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-05.088", "element_type": "implementation_example", "text": "Define security requirements in service-level agreements (SLAs) for monitoring suppliers for acceptable security performance throughout the supplier relationship lifecycle", "title": "Ex5"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-05.089", "element_type": "implementation_example", "text": "Contractually require suppliers to disclose cybersecurity features, functions, and vulnerabilities of their products and services for the life of the product or the term of service", "title": "Ex6"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-05.090", "element_type": "implementation_example", "text": "Contractually require suppliers to provide and maintain a current component inventory (e.g., software or hardware bill of materials) for critical products", "title": "Ex7"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-05.091", "element_type": "implementation_example", "text": "Contractually require suppliers to vet their employees and guard against insider threats", "title": "Ex8"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-05.092", "element_type": "implementation_example", "text": "Contractually require suppliers to provide evidence of performing acceptable security practices through, for example, self-attestation, conformance to known standards, certifications, or inspections", "title": "Ex9"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-05.093", "element_type": "implementation_example", "text": "Specify in contracts and other agreements the rights and responsibilities of the organization, its suppliers, and their supply chains, with respect to potential cybersecurity risks", "title": "Ex10"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-06", "element_type": "subcategory", "text": "Planning and due diligence are performed to reduce risks before entering into formal supplier or other third-party relationships", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-06.094", "element_type": "implementation_example", "text": "Perform thorough due diligence on prospective suppliers that is consistent with procurement planning and commensurate with the level of risk, criticality, and complexity of each supplier relationship", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-06.095", "element_type": "implementation_example", "text": "Assess the suitability of the technology and cybersecurity capabilities and the risk management practices of prospective suppliers", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-06.096", "element_type": "implementation_example", "text": "Conduct supplier risk assessments against business and applicable cybersecurity requirements", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-06.097", "element_type": "implementation_example", "text": "Assess the authenticity, integrity, and security of critical products prior to acquisition and use", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-07", "element_type": "subcategory", "text": "The risks posed by a supplier, their products and services, and other third parties are understood, recorded, prioritized, assessed, responded to, and monitored over the course of the relationship", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-07.098", "element_type": "implementation_example", "text": "Adjust assessment formats and frequencies based on the third party's reputation and the criticality of the products or services they provide", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-07.099", "element_type": "implementation_example", "text": "Evaluate third parties' evidence of compliance with contractual cybersecurity requirements, such as self-attestations, warranties, certifications, and other artifacts", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-07.100", "element_type": "implementation_example", "text": "Monitor critical suppliers to ensure that they are fulfilling their security obligations throughout the supplier relationship lifecycle using a variety of methods and techniques, such as inspections, audits, tests, or other forms of evaluation", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-07.101", "element_type": "implementation_example", "text": "Monitor critical suppliers, services, and products for changes to their risk profiles, and reevaluate supplier criticality and risk impact accordingly", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-07.102", "element_type": "implementation_example", "text": "Plan for unexpected supplier and supply chain-related interruptions to ensure business continuity", "title": "Ex5"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-08", "element_type": "subcategory", "text": "Relevant suppliers and other third parties are included in incident planning, response, and recovery activities", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-08.103", "element_type": "implementation_example", "text": "Define and use rules and protocols for reporting incident response and recovery activities and the status between the organization and its suppliers", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-08.104", "element_type": "implementation_example", "text": "Identify and document the roles and responsibilities of the organization and its suppliers for incident response", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-08.105", "element_type": "implementation_example", "text": "Include critical suppliers in incident response exercises and simulations", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-08.106", "element_type": "implementation_example", "text": "Define and coordinate crisis communication methods and protocols between the organization and its critical suppliers", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-08.107", "element_type": "implementation_example", "text": "Conduct collaborative lessons learned sessions with critical suppliers", "title": "Ex5"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-09", "element_type": "subcategory", "text": "Supply chain security practices are integrated into cybersecurity and enterprise risk management programs, and their performance is monitored throughout the technology product and service life cycle", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-09.108", "element_type": "implementation_example", "text": "Policies and procedures require provenance records for all acquired technology products and services", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-09.109", "element_type": "implementation_example", "text": "Periodically provide risk reporting to leaders about how acquired components are proven to be untampered and authentic", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-09.110", "element_type": "implementation_example", "text": "Communicate regularly among cybersecurity risk managers and operations personnel about the need to acquire software patches, updates, and upgrades only from authenticated and trustworthy software providers", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-09.111", "element_type": "implementation_example", "text": "Review policies to ensure that they require approved supplier personnel to perform maintenance on supplier products", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-09.112", "element_type": "implementation_example", "text": "Policies and procedure require checking upgrades to critical hardware for unauthorized changes", "title": "Ex5"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-10", "element_type": "subcategory", "text": "Cybersecurity supply chain risk management plans include provisions for activities that occur after the conclusion of a partnership or service agreement", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-10.113", "element_type": "implementation_example", "text": "Establish processes for terminating critical relationships under both normal and adverse circumstances", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-10.114", "element_type": "implementation_example", "text": "Define and implement plans for component end-of-life maintenance support and obsolescence", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-10.115", "element_type": "implementation_example", "text": "Verify that supplier access to organization resources is deactivated promptly when it is no longer needed", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-10.116", "element_type": "implementation_example", "text": "Verify that assets containing the organization's data are returned or properly disposed of in a timely, controlled, and safe manner", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-10.117", "element_type": "implementation_example", "text": "Develop and execute a plan for terminating or transitioning supplier relationships that takes supply chain security risk and resiliency into account", "title": "Ex5"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-10.118", "element_type": "implementation_example", "text": "Mitigate risks to data and systems created by supplier termination", "title": "Ex6"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "GV.SC-10.119", "element_type": "implementation_example", "text": "Manage data leakage risks associated with supplier termination", "title": "Ex7"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID", "element_type": "function", "text": "The organization's current cybersecurity risks are understood", "title": "IDENTIFY"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM", "element_type": "category", "text": "Assets (e.g., data, hardware, software, systems, facilities, services, people) 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", "title": "Asset Management"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-01", "element_type": "subcategory", "text": "Inventories of hardware managed by the organization are maintained", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-01.120", "element_type": "implementation_example", "text": "Maintain inventories for all types of hardware, including IT, IoT, OT, and mobile devices", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-01.121", "element_type": "implementation_example", "text": "Constantly monitor networks to detect new hardware and automatically update inventories", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-02", "element_type": "subcategory", "text": "Inventories of software, services, and systems managed by the organization are maintained", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-02.122", "element_type": "implementation_example", "text": "Maintain inventories for all types of software and services, including commercial-off-the-shelf, open-source, custom applications, API services, and cloud-based applications and services", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-02.123", "element_type": "implementation_example", "text": "Constantly monitor all platforms, including containers and virtual machines, for software and service inventory changes", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-02.124", "element_type": "implementation_example", "text": "Maintain an inventory of the organization's systems", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-03", "element_type": "subcategory", "text": "Representations of the organization's authorized network communication and internal and external network data flows are maintained", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-03.125", "element_type": "implementation_example", "text": "Maintain baselines of communication and data flows within the organization's wired and wireless networks", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-03.126", "element_type": "implementation_example", "text": "Maintain baselines of communication and data flows between the organization and third parties", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-03.127", "element_type": "implementation_example", "text": "Maintain baselines of communication and data flows for the organization's infrastructure-as-a-service (IaaS) usage", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-03.128", "element_type": "implementation_example", "text": "Maintain documentation of expected network ports, protocols, and services that are typically used among authorized systems", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-04", "element_type": "subcategory", "text": "Inventories of services provided by suppliers are maintained", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-04.129", "element_type": "implementation_example", "text": "Inventory all external services used by the organization, including third-party infrastructure-as-a-service (IaaS), platform-as-a-service (PaaS), and software-as-a-service (SaaS) offerings; APIs; and other externally hosted application services", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-04.130", "element_type": "implementation_example", "text": "Update the inventory when a new external service is going to be utilized to ensure adequate cybersecurity risk management monitoring of the organization's use of that service", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-05", "element_type": "subcategory", "text": "Assets are prioritized based on classification, criticality, resources, and impact on the mission", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-05.131", "element_type": "implementation_example", "text": "Define criteria for prioritizing each class of assets", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-05.132", "element_type": "implementation_example", "text": "Apply the prioritization criteria to assets", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-05.133", "element_type": "implementation_example", "text": "Track the asset priorities and update them periodically or when significant changes to the organization occur", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-06", "element_type": "subcategory", "text": "Cybersecurity roles and responsibilities for the entire workforce and third-party stakeholders (e.g., suppliers, customers, partners) are established", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-ID.AM-06", "element_type": "withdraw_reason", "text": "Incorporated into GV.RR-02, GV.SC-02", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-07", "element_type": "subcategory", "text": "Inventories of data and corresponding metadata for designated data types are maintained", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-07.134", "element_type": "implementation_example", "text": "Maintain a list of the designated data types of interest (e.g., personally identifiable information, protected health information, financial account numbers, organization intellectual property, operational technology data)", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-07.135", "element_type": "implementation_example", "text": "Continuously discover and analyze ad hoc data to identify new instances of designated data types", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-07.136", "element_type": "implementation_example", "text": "Assign data classifications to designated data types through tags or labels", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-07.137", "element_type": "implementation_example", "text": "Track the provenance, data owner, and geolocation of each instance of designated data types", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-08", "element_type": "subcategory", "text": "Systems, hardware, software, services, and data are managed throughout their life cycles", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-08.138", "element_type": "implementation_example", "text": "Integrate cybersecurity considerations throughout the life cycles of systems, hardware, software, and services", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-08.139", "element_type": "implementation_example", "text": "Integrate cybersecurity considerations into product life cycles", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-08.140", "element_type": "implementation_example", "text": "Identify unofficial uses of technology to meet mission objectives (i.e., shadow IT)", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-08.141", "element_type": "implementation_example", "text": "Periodically identify redundant systems, hardware, software, and services that unnecessarily increase the organization's attack surface", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-08.142", "element_type": "implementation_example", "text": "Properly configure and secure systems, hardware, software, and services prior to their deployment in production", "title": "Ex5"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-08.143", "element_type": "implementation_example", "text": "Update inventories when systems, hardware, software, and services are moved or transferred within the organization", "title": "Ex6"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-08.144", "element_type": "implementation_example", "text": "Securely destroy stored data based on the organization's data retention policy using the prescribed destruction method, and keep and manage a record of the destructions", "title": "Ex7"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-08.145", "element_type": "implementation_example", "text": "Securely sanitize data storage when hardware is being retired, decommissioned, reassigned, or sent for repairs or replacement", "title": "Ex8"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.AM-08.146", "element_type": "implementation_example", "text": "Offer methods for destroying paper, storage media, and other physical forms of data storage", "title": "Ex9"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA", "element_type": "category", "text": "The cybersecurity risk to the organization, assets, and individuals is understood by the organization", "title": "Risk Assessment"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-01", "element_type": "subcategory", "text": "Vulnerabilities in assets are identified, validated, and recorded", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-01.147", "element_type": "implementation_example", "text": "Use vulnerability management technologies to identify unpatched and misconfigured software", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-01.148", "element_type": "implementation_example", "text": "Assess network and system architectures for design and implementation weaknesses that affect cybersecurity", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-01.149", "element_type": "implementation_example", "text": "Review, analyze, or test organization-developed software to identify design, coding, and default configuration vulnerabilities", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-01.150", "element_type": "implementation_example", "text": "Assess facilities that house critical computing assets for physical vulnerabilities and resilience issues", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-01.151", "element_type": "implementation_example", "text": "Monitor sources of cyber threat intelligence for information on new vulnerabilities in products and services", "title": "Ex5"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-01.152", "element_type": "implementation_example", "text": "Review processes and procedures for weaknesses that could be exploited to affect cybersecurity", "title": "Ex6"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-02", "element_type": "subcategory", "text": "Cyber threat intelligence is received from information sharing forums and sources", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-02.153", "element_type": "implementation_example", "text": "Configure cybersecurity tools and technologies with detection or response capabilities to securely ingest cyber threat intelligence feeds", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-02.154", "element_type": "implementation_example", "text": "Receive and review advisories from reputable third parties on current threat actors and their tactics, techniques, and procedures (TTPs)", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-02.155", "element_type": "implementation_example", "text": "Monitor sources of cyber threat intelligence for information on the types of vulnerabilities that emerging technologies may have", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-03", "element_type": "subcategory", "text": "Internal and external threats to the organization are identified and recorded", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-03.156", "element_type": "implementation_example", "text": "Use cyber threat intelligence to maintain awareness of the types of threat actors likely to target the organization and the TTPs they are likely to use", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-03.157", "element_type": "implementation_example", "text": "Perform threat hunting to look for signs of threat actors within the environment", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-03.158", "element_type": "implementation_example", "text": "Implement processes for identifying internal threat actors", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-04", "element_type": "subcategory", "text": "Potential impacts and likelihoods of threats exploiting vulnerabilities are identified and recorded", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-04.159", "element_type": "implementation_example", "text": "Business leaders and cybersecurity risk management practitioners work together to estimate the likelihood and impact of risk scenarios and record them in risk registers", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-04.160", "element_type": "implementation_example", "text": "Enumerate the potential business impacts of unauthorized access to the organization's communications, systems, and data processed in or by those systems", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-04.161", "element_type": "implementation_example", "text": "Account for the potential impacts of cascading failures for systems of systems", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-05", "element_type": "subcategory", "text": "Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritization", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-05.162", "element_type": "implementation_example", "text": "Develop threat models to better understand risks to the data and identify appropriate risk responses", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-05.163", "element_type": "implementation_example", "text": "Prioritize cybersecurity resource allocations and investments based on estimated likelihoods and impacts", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-06", "element_type": "subcategory", "text": "Risk responses are chosen, prioritized, planned, tracked, and communicated", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-06.164", "element_type": "implementation_example", "text": "Apply the vulnerability management plan's criteria for deciding whether to accept, transfer, mitigate, or avoid risk", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-06.165", "element_type": "implementation_example", "text": "Apply the vulnerability management plan's criteria for selecting compensating controls to mitigate risk", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-06.166", "element_type": "implementation_example", "text": "Track the progress of risk response implementation (e.g., plan of action and milestones [POA&M], risk register, risk detail report)", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-06.167", "element_type": "implementation_example", "text": "Use risk assessment findings to inform risk response decisions and actions", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-06.168", "element_type": "implementation_example", "text": "Communicate planned risk responses to affected stakeholders in priority order", "title": "Ex5"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-07", "element_type": "subcategory", "text": "Changes and exceptions are managed, assessed for risk impact, recorded, and tracked", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-07.169", "element_type": "implementation_example", "text": "Implement and follow procedures for the formal documentation, review, testing, and approval of proposed changes and requested exceptions", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-07.170", "element_type": "implementation_example", "text": "Document the possible risks of making or not making each proposed change, and provide guidance on rolling back changes", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-07.171", "element_type": "implementation_example", "text": "Document the risks related to each requested exception and the plan for responding to those risks", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-07.172", "element_type": "implementation_example", "text": "Periodically review risks that were accepted based upon planned future actions or milestones", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-08", "element_type": "subcategory", "text": "Processes for receiving, analyzing, and responding to vulnerability disclosures are established", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-08.173", "element_type": "implementation_example", "text": "Conduct vulnerability information sharing between the organization and its suppliers following the rules and protocols defined in contracts", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-08.174", "element_type": "implementation_example", "text": "Assign responsibilities and verify the execution of procedures for processing, analyzing the impact of, and responding to cybersecurity threat, vulnerability, or incident disclosures by suppliers, customers, partners, and government cybersecurity organizations", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-09", "element_type": "subcategory", "text": "The authenticity and integrity of hardware and software are assessed prior to acquisition and use", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-09.175", "element_type": "implementation_example", "text": "Assess the authenticity and cybersecurity of critical technology products and services prior to acquisition and use", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-10", "element_type": "subcategory", "text": "Critical suppliers are assessed prior to acquisition", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RA-10.176", "element_type": "implementation_example", "text": "Conduct supplier risk assessments against business and applicable cybersecurity requirements, including the supply chain", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.IM", "element_type": "category", "text": "Improvements to organizational cybersecurity risk management processes, procedures and activities are identified across all CSF Functions", "title": "Improvement"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.IM-01", "element_type": "subcategory", "text": "Improvements are identified from evaluations", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.IM-01.177", "element_type": "implementation_example", "text": "Perform self-assessments of critical services that take current threats and TTPs into consideration", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.IM-01.178", "element_type": "implementation_example", "text": "Invest in third-party assessments or independent audits of the effectiveness of the organization's cybersecurity program to identify areas that need improvement", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.IM-01.179", "element_type": "implementation_example", "text": "Constantly evaluate compliance with selected cybersecurity requirements through automated means", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.IM-02", "element_type": "subcategory", "text": "Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.IM-02.180", "element_type": "implementation_example", "text": "Identify improvements for future incident response activities based on findings from incident response assessments (e.g., tabletop exercises and simulations, tests, internal reviews, independent audits)", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.IM-02.181", "element_type": "implementation_example", "text": "Identify improvements for future business continuity, disaster recovery, and incident response activities based on exercises performed in coordination with critical service providers and product suppliers", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.IM-02.182", "element_type": "implementation_example", "text": "Involve internal stakeholders (e.g., senior executives, legal department, HR) in security tests and exercises as appropriate", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.IM-02.183", "element_type": "implementation_example", "text": "Perform penetration testing to identify opportunities to improve the security posture of selected high-risk systems as approved by leadership", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.IM-02.184", "element_type": "implementation_example", "text": "Exercise contingency plans for responding to and recovering from the discovery that products or services did not originate with the contracted supplier or partner or were altered before receipt", "title": "Ex5"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.IM-02.185", "element_type": "implementation_example", "text": "Collect and analyze performance metrics using security tools and services to inform improvements to the cybersecurity program", "title": "Ex6"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.IM-03", "element_type": "subcategory", "text": "Improvements are identified from execution of operational processes, procedures, and activities", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.IM-03.186", "element_type": "implementation_example", "text": "Conduct collaborative lessons learned sessions with suppliers", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.IM-03.187", "element_type": "implementation_example", "text": "Annually review cybersecurity policies, processes, and procedures to take lessons learned into account", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.IM-03.188", "element_type": "implementation_example", "text": "Use metrics to assess operational cybersecurity performance over time", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.IM-04", "element_type": "subcategory", "text": "Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.IM-04.189", "element_type": "implementation_example", "text": "Establish contingency plans (e.g., incident response, business continuity, disaster recovery) for responding to and recovering from adverse events that can interfere with operations, expose confidential information, or otherwise endanger the organization's mission and viability", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.IM-04.190", "element_type": "implementation_example", "text": "Include contact and communication information, processes for handling common scenarios, and criteria for prioritization, escalation, and elevation in all contingency plans", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.IM-04.191", "element_type": "implementation_example", "text": "Create a vulnerability management plan to identify and assess all types of vulnerabilities and to prioritize, test, and implement risk responses", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.IM-04.192", "element_type": "implementation_example", "text": "Communicate cybersecurity plans (including updates) to those responsible for carrying them out and to affected parties", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.IM-04.193", "element_type": "implementation_example", "text": "Review and update all cybersecurity plans annually or when a need for significant improvements is identified", "title": "Ex5"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.BE-01", "element_type": "subcategory", "text": "The organization’s role in the supply chain is identified and communicated", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-ID.BE-01", "element_type": "withdraw_reason", "text": "Incorporated into GV.OC-05", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.BE-02", "element_type": "subcategory", "text": "The organization’s place in critical infrastructure and its industry sector is identified and communicated", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-ID.BE-02", "element_type": "withdraw_reason", "text": "Incorporated into GV.OC-01", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.BE-03", "element_type": "subcategory", "text": "Priorities for organizational mission, objectives, and activities are established and communicated", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-ID.BE-03", "element_type": "withdraw_reason", "text": "Incorporated into GV.OC-01", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.BE-04", "element_type": "subcategory", "text": "Dependencies and critical functions for delivery of critical services are established", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-ID.BE-04", "element_type": "withdraw_reason", "text": "Incorporated into GV.OC-04, GV.OC-05", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.BE-05", "element_type": "subcategory", "text": "Resilience requirements to support delivery of critical services are established for all operating states (e.g. under duress/attack, during recovery, normal operations)", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-ID.BE-05", "element_type": "withdraw_reason", "text": "Incorporated into GV.OC-04", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-ID.BE", "element_type": "withdraw_reason", "text": "Incorporated into GV.OC", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.GV-01", "element_type": "subcategory", "text": "Organizational cybersecurity policy is established and communicated", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-ID.GV-01", "element_type": "withdraw_reason", "text": "Incorporated into GV.PO, GV.PO-01, GV.PO-02", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.GV-02", "element_type": "subcategory", "text": "Cybersecurity roles and responsibilities are coordinated and aligned with internal roles and external partners", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-ID.GV-02", "element_type": "withdraw_reason", "text": "Incorporated into GV.OC-02, GV.RR, GV.RR-02", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.GV-03", "element_type": "subcategory", "text": "Legal and regulatory requirements regarding cybersecurity, including privacy and civil liberties obligations, are understood and managed", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-ID.GV-03", "element_type": "withdraw_reason", "text": "Moved to GV.OC-03", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.GV-04", "element_type": "subcategory", "text": "Governance and risk management processes address cybersecurity risks", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-ID.GV-04", "element_type": "withdraw_reason", "text": "Moved to GV.RM-04", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-ID.GV", "element_type": "withdraw_reason", "text": "Incorporated into GV", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RM-01", "element_type": "subcategory", "text": "Risk management processes are established, managed, and agreed to by organizational stakeholders", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-ID.RM-01", "element_type": "withdraw_reason", "text": "Incorporated into GV.RM-01, GV.RM-06, GV.RR-03", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RM-02", "element_type": "subcategory", "text": "Organizational risk tolerance is determined and clearly expressed", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-ID.RM-02", "element_type": "withdraw_reason", "text": "Incorporated into GV.RM-02, GV.RM-04", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.RM-03", "element_type": "subcategory", "text": "The organization’s determination of risk tolerance is informed by its role in critical infrastructure and sector specific risk analysis", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-ID.RM-03", "element_type": "withdraw_reason", "text": "Moved into GV.RM-02", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-ID.RM", "element_type": "withdraw_reason", "text": "Incorporated into GV.RM", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.SC-01", "element_type": "subcategory", "text": "Cyber supply chain risk management processes are identified, established, assessed, managed, and agreed to by organizational stakeholders", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-ID.SC-01", "element_type": "withdraw_reason", "text": "Incorporated into GV.RM-05, GV.SC-01, GV.SC-06, GV.SC-09, GV.SC-10", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.SC-02", "element_type": "subcategory", "text": "Suppliers and third party partners of information systems, components, and services are identified, prioritized, and assessed using a cyber supply chain risk assessment process", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-ID.SC-02", "element_type": "withdraw_reason", "text": "Incorporated into GV.OC-02, GV.SC-03, GV.SC-04, GV.SC-07, ID.RA-10", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.SC-03", "element_type": "subcategory", "text": "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.", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-ID.SC-03", "element_type": "withdraw_reason", "text": "Moved to GV.SC-05", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.SC-04", "element_type": "subcategory", "text": "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.", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-ID.SC-04", "element_type": "withdraw_reason", "text": "Incorporated into GV.SC-07, ID.RA-10", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "ID.SC-05", "element_type": "subcategory", "text": "Response and recovery planning and testing are conducted with suppliers and third-party providers", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-ID.SC-05", "element_type": "withdraw_reason", "text": "Incorporated into GV.SC-08, ID.IM-02", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-ID.SC", "element_type": "withdraw_reason", "text": "Incorporated into GV.SC", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR", "element_type": "function", "text": "Safeguards to manage the organization's cybersecurity risks are used", "title": "PROTECT"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AA", "element_type": "category", "text": "Access to physical and logical assets is limited to authorized users, services, and hardware and  managed commensurate with the assessed risk of unauthorized access", "title": "Identity Management, Authentication, and Access Control"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AA-01", "element_type": "subcategory", "text": "Identities and credentials for authorized users, services, and hardware are managed by the organization", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AA-01.194", "element_type": "implementation_example", "text": "Initiate requests for new access or additional access for employees, contractors, and others, and track, review, and fulfill the requests, with permission from system or data owners when needed", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AA-01.195", "element_type": "implementation_example", "text": "Issue, manage, and revoke cryptographic certificates and identity tokens, cryptographic keys (i.e., key management), and other credentials", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AA-01.196", "element_type": "implementation_example", "text": "Select a unique identifier for each device from immutable hardware characteristics or an identifier securely provisioned to the device", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AA-01.197", "element_type": "implementation_example", "text": "Physically label authorized hardware with an identifier for inventory and servicing purposes", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AA-02", "element_type": "subcategory", "text": "Identities are proofed and bound to credentials based on the context of interactions", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AA-02.198", "element_type": "implementation_example", "text": "Verify a person's claimed identity at enrollment time using government-issued identity credentials (e.g., passport, visa, driver's license)", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AA-02.199", "element_type": "implementation_example", "text": "Issue a different credential for each person (i.e., no credential sharing)", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AA-03", "element_type": "subcategory", "text": "Users, services, and hardware are authenticated", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AA-03.200", "element_type": "implementation_example", "text": "Require multifactor authentication", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AA-03.201", "element_type": "implementation_example", "text": "Enforce policies for the minimum strength of passwords, PINs, and similar authenticators", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AA-03.202", "element_type": "implementation_example", "text": "Periodically reauthenticate users, services, and hardware based on risk (e.g., in zero trust architectures)", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AA-03.203", "element_type": "implementation_example", "text": "Ensure that authorized personnel can access accounts essential for protecting safety under emergency conditions", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AA-04", "element_type": "subcategory", "text": "Identity assertions are protected, conveyed, and verified", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AA-04.204", "element_type": "implementation_example", "text": "Protect identity assertions that are used to convey authentication and user information through single sign-on systems", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AA-04.205", "element_type": "implementation_example", "text": "Protect identity assertions that are used to convey authentication and user information between federated systems", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AA-04.206", "element_type": "implementation_example", "text": "Implement standards-based approaches for identity assertions in all contexts, and follow all guidance for the generation (e.g., data models, metadata), protection (e.g., digital signing, encryption), and verification (e.g., signature validation) of identity assertions", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AA-05", "element_type": "subcategory", "text": "Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AA-05.207", "element_type": "implementation_example", "text": "Review logical and physical access privileges periodically and whenever someone changes roles or leaves the organization, and promptly rescind privileges that are no longer needed", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AA-05.208", "element_type": "implementation_example", "text": "Take attributes of the requester and the requested resource into account for authorization decisions (e.g., geolocation, day/time, requester endpoint's cyber health)", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AA-05.209", "element_type": "implementation_example", "text": "Restrict access and privileges to the minimum necessary (e.g., zero trust architecture)", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AA-05.210", "element_type": "implementation_example", "text": "Periodically review the privileges associated with critical business functions to confirm proper separation of duties", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AA-06", "element_type": "subcategory", "text": "Physical access to assets is managed, monitored, and enforced commensurate with risk", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AA-06.211", "element_type": "implementation_example", "text": "Use security guards, security cameras, locked entrances, alarm systems, and other physical controls to monitor facilities and restrict access", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AA-06.212", "element_type": "implementation_example", "text": "Employ additional physical security controls for areas that contain high-risk assets", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AA-06.213", "element_type": "implementation_example", "text": "Escort guests, vendors, and other third parties within areas that contain business-critical assets", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AT", "element_type": "category", "text": "The organization's personnel are provided with cybersecurity awareness and training so that they can perform their cybersecurity-related tasks", "title": "Awareness and Training"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AT-01", "element_type": "subcategory", "text": "Personnel are provided with awareness and training so that they possess the knowledge and skills to perform general tasks with cybersecurity risks in mind", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AT-01.214", "element_type": "implementation_example", "text": "Provide basic cybersecurity awareness and training to employees, contractors, partners, suppliers, and all other users of the organization's non-public resources", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AT-01.215", "element_type": "implementation_example", "text": "Train personnel to recognize social engineering attempts and other common attacks, report attacks and suspicious activity, comply with acceptable use policies, and perform basic cyber hygiene tasks (e.g., patching software, choosing passwords, protecting credentials)", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AT-01.216", "element_type": "implementation_example", "text": "Explain the consequences of cybersecurity policy violations, both to individual users and the organization as a whole", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AT-01.217", "element_type": "implementation_example", "text": "Periodically assess or test users on their understanding of basic cybersecurity practices", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AT-01.218", "element_type": "implementation_example", "text": "Require annual refreshers to reinforce existing practices and introduce new practices", "title": "Ex5"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AT-02", "element_type": "subcategory", "text": "Individuals in specialized roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AT-02.219", "element_type": "implementation_example", "text": "Identify the specialized roles within the organization that require additional cybersecurity training, such as physical and cybersecurity personnel, finance personnel, senior leadership, and anyone with access to business-critical data", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AT-02.220", "element_type": "implementation_example", "text": "Provide role-based cybersecurity awareness and training to all those in specialized roles, including contractors, partners, suppliers, and other third parties", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AT-02.221", "element_type": "implementation_example", "text": "Periodically assess or test users on their understanding of cybersecurity practices for their specialized roles", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AT-02.222", "element_type": "implementation_example", "text": "Require annual refreshers to reinforce existing practices and introduce new practices", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AT-03", "element_type": "subcategory", "text": "Third-party stakeholders (e.g., suppliers, customers, partners) understand their roles and responsibilities", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.AT-03", "element_type": "withdraw_reason", "text": "Incorporated into PR.AT-01, PR.AT-02", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AT-04", "element_type": "subcategory", "text": "Senior executives understand their roles and responsibilities", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.AT-04", "element_type": "withdraw_reason", "text": "Incorporated into PR.AT-02", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AT-05", "element_type": "subcategory", "text": "Physical and cybersecurity personnel understand their roles and responsibilities", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.AT-05", "element_type": "withdraw_reason", "text": "Incorporated into PR.AT-02", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.DS", "element_type": "category", "text": "Data are managed consistent with the organization's risk strategy to protect the confidentiality, integrity, and availability of information", "title": "Data Security"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.DS-01", "element_type": "subcategory", "text": "The confidentiality, integrity, and availability of data-at-rest are protected", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.DS-01.223", "element_type": "implementation_example", "text": "Use encryption, digital signatures, and cryptographic hashes to protect the confidentiality and integrity of stored data in files, databases, virtual machine disk images, container images, and other resources", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.DS-01.224", "element_type": "implementation_example", "text": "Use full disk encryption to protect data stored on user endpoints", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.DS-01.225", "element_type": "implementation_example", "text": "Confirm the integrity of software by validating signatures", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.DS-01.226", "element_type": "implementation_example", "text": "Restrict the use of removable media to prevent data exfiltration", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.DS-01.227", "element_type": "implementation_example", "text": "Physically secure removable media containing unencrypted sensitive information, such as within locked offices or file cabinets", "title": "Ex5"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.DS-02", "element_type": "subcategory", "text": "The confidentiality, integrity, and availability of data-in-transit are protected", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.DS-02.228", "element_type": "implementation_example", "text": "Use encryption, digital signatures, and cryptographic hashes to protect the confidentiality and integrity of network communications", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.DS-02.229", "element_type": "implementation_example", "text": "Automatically encrypt or block outbound emails and other communications that contain sensitive data, depending on the data classification", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.DS-02.230", "element_type": "implementation_example", "text": "Block access to personal email, file sharing, file storage services, and other personal communications applications and services from organizational systems and networks", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.DS-02.231", "element_type": "implementation_example", "text": "Prevent reuse of sensitive data from production environments (e.g., customer records) in development, testing, and other non-production environments", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.DS-03", "element_type": "subcategory", "text": "Assets are formally managed throughout removal, transfers, and disposition", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.DS-03", "element_type": "withdraw_reason", "text": "Incorporated into ID.AM-08, PR.PS-03", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.DS-04", "element_type": "subcategory", "text": "Adequate capacity to ensure availability is maintained", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.DS-04", "element_type": "withdraw_reason", "text": "Moved to PR.IR-04", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.DS-05", "element_type": "subcategory", "text": "Protections against data leaks are implemented", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.DS-05", "element_type": "withdraw_reason", "text": "Incorporated into PR.DS-01, PR.DS-02, PR.DS-10", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.DS-06", "element_type": "subcategory", "text": "Integrity checking mechanisms are used to verify software, firmware, and information integrity", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.DS-06", "element_type": "withdraw_reason", "text": "Incorporated into PR.DS-01, DE.CM-09", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.DS-07", "element_type": "subcategory", "text": "The development and testing environment(s) are separate from the production environment", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.DS-07", "element_type": "withdraw_reason", "text": "Incorporated into PR.IR-01", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.DS-08", "element_type": "subcategory", "text": "Integrity checking mechanisms are used to verify hardware integrity", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.DS-08", "element_type": "withdraw_reason", "text": "Incorporated into ID.RA-09, DE.CM-09", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.DS-10", "element_type": "subcategory", "text": "The confidentiality, integrity, and availability of data-in-use are protected", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.DS-10.232", "element_type": "implementation_example", "text": "Remove data that must remain confidential (e.g., from processors and memory) as soon as it is no longer needed", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.DS-10.233", "element_type": "implementation_example", "text": "Protect data in use from access by other users and processes of the same platform", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.DS-11", "element_type": "subcategory", "text": "Backups of data are created, protected, maintained, and tested", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.DS-11.234", "element_type": "implementation_example", "text": "Continuously back up critical data in near-real-time, and back up other data frequently at agreed-upon schedules", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.DS-11.235", "element_type": "implementation_example", "text": "Test backups and restores for all types of data sources at least annually", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.DS-11.236", "element_type": "implementation_example", "text": "Securely store some backups offline and offsite so that an incident or disaster will not damage them", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.DS-11.237", "element_type": "implementation_example", "text": "Enforce geographic separation and geolocation restrictions for data backup storage", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PS", "element_type": "category", "text": "The hardware, software (e.g., firmware, operating systems, applications), and services of physical and virtual platforms are managed consistent with the organization's risk strategy to protect their confidentiality, integrity, and availability", "title": "Platform Security"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PS-01", "element_type": "subcategory", "text": "Configuration management practices are established and applied", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PS-01.238", "element_type": "implementation_example", "text": "Establish, test, deploy, and maintain hardened baselines that enforce the organization's cybersecurity policies and provide only essential capabilities (i.e., principle of least functionality)", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PS-01.239", "element_type": "implementation_example", "text": "Review all default configuration settings that may potentially impact cybersecurity when installing or upgrading software", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PS-01.240", "element_type": "implementation_example", "text": "Monitor implemented software for deviations from approved baselines", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PS-02", "element_type": "subcategory", "text": "Software is maintained, replaced, and removed commensurate with risk", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PS-02.241", "element_type": "implementation_example", "text": "Perform routine and emergency patching within the timeframes specified in the vulnerability management plan", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PS-02.242", "element_type": "implementation_example", "text": "Update container images, and deploy new container instances to replace rather than update existing instances", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PS-02.243", "element_type": "implementation_example", "text": "Replace end-of-life software and service versions with supported, maintained versions", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PS-02.244", "element_type": "implementation_example", "text": "Uninstall and remove unauthorized software and services that pose undue risks", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PS-02.245", "element_type": "implementation_example", "text": "Uninstall and remove any unnecessary software components (e.g., operating system utilities) that attackers might misuse", "title": "Ex5"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PS-02.246", "element_type": "implementation_example", "text": "Define and implement plans for software and service end-of-life maintenance support and obsolescence", "title": "Ex6"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PS-03", "element_type": "subcategory", "text": "Hardware is maintained, replaced, and removed commensurate with risk", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PS-03.247", "element_type": "implementation_example", "text": "Replace hardware when it lacks needed security capabilities or when it cannot support software with needed security capabilities", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PS-03.248", "element_type": "implementation_example", "text": "Define and implement plans for hardware end-of-life maintenance support and obsolescence", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PS-03.249", "element_type": "implementation_example", "text": "Perform hardware disposal in a secure, responsible, and auditable manner", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PS-04", "element_type": "subcategory", "text": "Log records are generated and made available for continuous monitoring", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PS-04.250", "element_type": "implementation_example", "text": "Configure all operating systems, applications, and services (including cloud-based services) to generate log records", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PS-04.251", "element_type": "implementation_example", "text": "Configure log generators to securely share their logs with the organization's logging infrastructure systems and services", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PS-04.252", "element_type": "implementation_example", "text": "Configure log generators to record the data needed by zero-trust architectures", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PS-05", "element_type": "subcategory", "text": "Installation and execution of unauthorized software are prevented", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PS-05.253", "element_type": "implementation_example", "text": "When risk warrants it, restrict software execution to permitted products only or deny the execution of prohibited and unauthorized software", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PS-05.254", "element_type": "implementation_example", "text": "Verify the source of new software and the software's integrity before installing it", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PS-05.255", "element_type": "implementation_example", "text": "Configure platforms to use only approved DNS services that block access to known malicious domains", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PS-05.256", "element_type": "implementation_example", "text": "Configure platforms to allow the installation of organization-approved software only", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PS-06", "element_type": "subcategory", "text": "Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PS-06.257", "element_type": "implementation_example", "text": "Protect all components of organization-developed software from tampering and unauthorized access", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PS-06.258", "element_type": "implementation_example", "text": "Secure all software produced by the organization, with minimal vulnerabilities in their releases", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PS-06.259", "element_type": "implementation_example", "text": "Maintain the software used in production environments, and securely dispose of software once it is no longer needed", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.IR", "element_type": "category", "text": "Security architectures are managed with the organization's risk strategy to protect asset confidentiality, integrity, and availability, and organizational resilience", "title": "Technology Infrastructure Resilience"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.IR-01", "element_type": "subcategory", "text": "Networks and environments are protected from unauthorized logical access and usage", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.IR-01.260", "element_type": "implementation_example", "text": "Logically segment organization networks and cloud-based platforms according to trust boundaries and platform types (e.g., IT, IoT, OT, mobile, guests), and permit required communications only between segments", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.IR-01.261", "element_type": "implementation_example", "text": "Logically segment organization networks from external networks, and permit only necessary communications to enter the organization's networks from the external networks", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.IR-01.262", "element_type": "implementation_example", "text": "Implement zero trust architectures to restrict network access to each resource to the minimum necessary", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.IR-01.263", "element_type": "implementation_example", "text": "Check the cyber health of endpoints before allowing them to access and use production resources", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.IR-02", "element_type": "subcategory", "text": "The organization's technology assets are protected from environmental threats", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.IR-02.264", "element_type": "implementation_example", "text": "Protect organizational equipment from known environmental threats, such as flooding, fire, wind, and excessive heat and humidity", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.IR-02.265", "element_type": "implementation_example", "text": "Include protection from environmental threats and provisions for adequate operating infrastructure in requirements for service providers that operate systems on the organization's behalf", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.IR-03", "element_type": "subcategory", "text": "Mechanisms are implemented to achieve resilience requirements in normal and adverse situations", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.IR-03.266", "element_type": "implementation_example", "text": "Avoid single points of failure in systems and infrastructure", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.IR-03.267", "element_type": "implementation_example", "text": "Use load balancing to increase capacity and improve reliability", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.IR-03.268", "element_type": "implementation_example", "text": "Use high-availability components like redundant storage and power supplies to improve system reliability", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.IR-04", "element_type": "subcategory", "text": "Adequate resource capacity to ensure availability is maintained", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.IR-04.269", "element_type": "implementation_example", "text": "Monitor usage of storage, power, compute, network bandwidth, and other resources", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.IR-04.270", "element_type": "implementation_example", "text": "Forecast future needs, and scale resources accordingly", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AC-01", "element_type": "subcategory", "text": "Identities and credentials are issued, managed, verified, revoked, and audited for authorized devices, users and processes", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.AC-01", "element_type": "withdraw_reason", "text": "Incorporated into PR.AA-01, PR.AA-05", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AC-02", "element_type": "subcategory", "text": "Physical access to assets is managed and protected", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.AC-02", "element_type": "withdraw_reason", "text": "Moved to PR.AA-06", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AC-03", "element_type": "subcategory", "text": "Remote access is managed", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.AC-03", "element_type": "withdraw_reason", "text": "Incorporated into PR.AA-03, PR.AA-05, PR.IR-01", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AC-04", "element_type": "subcategory", "text": "Access permissions and authorizations are managed, incorporating the principles of least privilege and separation of duties", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.AC-04", "element_type": "withdraw_reason", "text": "Moved to PR.AA-05", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AC-05", "element_type": "subcategory", "text": "Network integrity is protected (e.g., network segregation, network segmentation)", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.AC-05", "element_type": "withdraw_reason", "text": "Incorporated into PR.IR-01", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AC-06", "element_type": "subcategory", "text": "Identities are proofed and bound to credentials and asserted in interactions", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.AC-06", "element_type": "withdraw_reason", "text": "Moved to PR.AA-02", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.AC-07", "element_type": "subcategory", "text": "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)", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.AC-07", "element_type": "withdraw_reason", "text": "Moved to PR.AA-03", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.AC", "element_type": "withdraw_reason", "text": "Moved to PR.AA", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.IP-01", "element_type": "subcategory", "text": "A baseline configuration of information technology/industrial control systems is created and maintained incorporating security principles (e.g. concept of least functionality)", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.IP-01", "element_type": "withdraw_reason", "text": "Incorporated into PR.PS-01", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.IP-02", "element_type": "subcategory", "text": "A System Development Life Cycle to manage systems is implemented", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.IP-02", "element_type": "withdraw_reason", "text": "Incorporated into ID.AM-08, PR.PS-06", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.IP-03", "element_type": "subcategory", "text": "Configuration change control processes are in place", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.IP-03", "element_type": "withdraw_reason", "text": "Incorporated into PR.PS-01, ID.RA-07", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.IP-04", "element_type": "subcategory", "text": "Backups of information are conducted, maintained, and tested", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.IP-04", "element_type": "withdraw_reason", "text": "Moved to PR.DS-11", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.IP-05", "element_type": "subcategory", "text": "Policy and regulations regarding the physical operating environment for organizational assets are met", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.IP-05", "element_type": "withdraw_reason", "text": "Moved to PR.IR-02", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.IP-06", "element_type": "subcategory", "text": "Data is destroyed according to policy", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.IP-06", "element_type": "withdraw_reason", "text": "Incorporated into ID.AM-08", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.IP-07", "element_type": "subcategory", "text": "Protection processes are improved", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.IP-07", "element_type": "withdraw_reason", "text": "Incorporated into ID.IM, ID.IM-03", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.IP-08", "element_type": "subcategory", "text": "Effectiveness of protection technologies is shared", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.IP-08", "element_type": "withdraw_reason", "text": "Moved to ID.IM-03", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.IP-09", "element_type": "subcategory", "text": "Response plans (Incident Response and Business Continuity) and recovery plans (Incident Recovery and Disaster Recovery) are in place and managed", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.IP-09", "element_type": "withdraw_reason", "text": "Moved to ID.IM-04", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.IP-10", "element_type": "subcategory", "text": "Response and recovery plans are tested", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.IP-10", "element_type": "withdraw_reason", "text": "Incorporated into ID.IM-02, ID.IM-04", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.IP-11", "element_type": "subcategory", "text": "Cybersecurity is included in human resources practices (e.g., deprovisioning, personnel screening)", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.IP-11", "element_type": "withdraw_reason", "text": "Moved to GV.RR-04", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.IP-12", "element_type": "subcategory", "text": "A vulnerability management plan is developed and implemented", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.IP-12", "element_type": "withdraw_reason", "text": "Incorporated into ID.RA-01, PR.PS-02", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.IP", "element_type": "withdraw_reason", "text": "Incorporated into other Categories and Functions", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.MA-01", "element_type": "subcategory", "text": "Maintenance and repair of organizational assets are performed and logged, with approved and controlled tools", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.MA-01", "element_type": "withdraw_reason", "text": "Incorporated into ID.AM-08, PR.PS-03", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.MA-02", "element_type": "subcategory", "text": "Remote maintenance of organizational assets is approved, logged, and performed in a manner that prevents unauthorized access", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.MA-02", "element_type": "withdraw_reason", "text": "Incorporated into ID.AM-08, PR.PS-02", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.MA", "element_type": "withdraw_reason", "text": "Incorporated into ID.AM-08", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PT-01", "element_type": "subcategory", "text": "Audit/log records are determined, documented, implemented, and reviewed in accordance with policy", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.PT-01", "element_type": "withdraw_reason", "text": "Incorporated into PR.PS-04", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PT-02", "element_type": "subcategory", "text": "Removable media is protected and its use restricted according to policy", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.PT-02", "element_type": "withdraw_reason", "text": "Incorporated into PR.DS-01, PR.PS-01", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PT-03", "element_type": "subcategory", "text": "The principle of least functionality is incorporated by configuring systems to provide only essential capabilities", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.PT-03", "element_type": "withdraw_reason", "text": "Incorporated into PR.PS-01", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PT-04", "element_type": "subcategory", "text": "Communications and control networks are protected", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.PT-04", "element_type": "withdraw_reason", "text": "Incorporated into PR.AA-06, PR.IR-01", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "PR.PT-05", "element_type": "subcategory", "text": "Mechanisms (e.g., failsafe, load balancing, hot swap) are implemented to achieve resilience requirements in normal and adverse situations", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.PT-05", "element_type": "withdraw_reason", "text": "Moved to PR.IR-03", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-PR.PT", "element_type": "withdraw_reason", "text": "Incorporated into other Protect Categories", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE", "element_type": "function", "text": "Possible cybersecurity attacks and compromises are found and analyzed", "title": "DETECT"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.CM", "element_type": "category", "text": "Assets are monitored to find anomalies, indicators of compromise, and other potentially adverse events", "title": "Continuous Monitoring"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.CM-01", "element_type": "subcategory", "text": "Networks and network services are monitored to find potentially adverse events", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.CM-01.271", "element_type": "implementation_example", "text": "Monitor DNS, BGP, and other network services for adverse events", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.CM-01.272", "element_type": "implementation_example", "text": "Monitor wired and wireless networks for connections from unauthorized endpoints", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.CM-01.273", "element_type": "implementation_example", "text": "Monitor facilities for unauthorized or rogue wireless networks", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.CM-01.274", "element_type": "implementation_example", "text": "Compare actual network flows against baselines to detect deviations", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.CM-01.275", "element_type": "implementation_example", "text": "Monitor network communications to identify changes in security postures for zero trust purposes", "title": "Ex5"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.CM-02", "element_type": "subcategory", "text": "The physical environment is monitored to find potentially adverse events", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.CM-02.276", "element_type": "implementation_example", "text": "Monitor logs from physical access control systems (e.g., badge readers) to find unusual access patterns (e.g., deviations from the norm) and failed access attempts", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.CM-02.277", "element_type": "implementation_example", "text": "Review and monitor physical access records (e.g., from visitor registration, sign-in sheets)", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.CM-02.278", "element_type": "implementation_example", "text": "Monitor physical access controls (e.g., locks, latches, hinge pins, alarms) for signs of tampering", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.CM-02.279", "element_type": "implementation_example", "text": "Monitor the physical environment using alarm systems, cameras, and security guards", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.CM-03", "element_type": "subcategory", "text": "Personnel activity and technology usage are monitored to find potentially adverse events", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.CM-03.280", "element_type": "implementation_example", "text": "Use behavior analytics software to detect anomalous user activity to mitigate insider threats", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.CM-03.281", "element_type": "implementation_example", "text": "Monitor logs from logical access control systems to find unusual access patterns and failed access attempts", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.CM-03.282", "element_type": "implementation_example", "text": "Continuously monitor deception technology, including user accounts, for any usage", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.CM-04", "element_type": "subcategory", "text": "Malicious code is detected", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-DE.CM-04", "element_type": "withdraw_reason", "text": "Incorporated into DE.CM-01, DE.CM-09", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.CM-05", "element_type": "subcategory", "text": "Unauthorized mobile code is detected", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-DE.CM-05", "element_type": "withdraw_reason", "text": "Incorporated into DE.CM-01, DE.CM-09", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.CM-06", "element_type": "subcategory", "text": "External service provider activities and services are monitored to find potentially adverse events", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.CM-06.283", "element_type": "implementation_example", "text": "Monitor remote and onsite administration and maintenance activities that external providers perform on organizational systems", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.CM-06.284", "element_type": "implementation_example", "text": "Monitor activity from cloud-based services, internet service providers, and other service providers for deviations from expected behavior", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.CM-07", "element_type": "subcategory", "text": "Monitoring for unauthorized personnel, connections, devices, and software is performed", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-DE.CM-07", "element_type": "withdraw_reason", "text": "Incorporated into DE.CM-01, DE.CM-03, DE.CM-06, DE.CM-09", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.CM-08", "element_type": "subcategory", "text": "Vulnerability scans are performed", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-DE.CM-08", "element_type": "withdraw_reason", "text": "Incorporated into ID.RA-01", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.CM-09", "element_type": "subcategory", "text": "Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.CM-09.285", "element_type": "implementation_example", "text": "Monitor email, web, file sharing, collaboration services, and other common attack vectors to detect malware, phishing, data leaks and exfiltration, and other adverse events", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.CM-09.286", "element_type": "implementation_example", "text": "Monitor authentication attempts to identify attacks against credentials and unauthorized credential reuse", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.CM-09.287", "element_type": "implementation_example", "text": "Monitor software configurations for deviations from security baselines", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.CM-09.288", "element_type": "implementation_example", "text": "Monitor hardware and software for signs of tampering", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.CM-09.289", "element_type": "implementation_example", "text": "Use technologies with a presence on endpoints to detect cyber health issues (e.g., missing patches, malware infections, unauthorized software), and redirect the endpoints to a remediation environment before access is authorized", "title": "Ex5"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.AE", "element_type": "category", "text": "Anomalies, indicators of compromise, and other potentially adverse events are analyzed to characterize the events and detect cybersecurity incidents", "title": "Adverse Event Analysis"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.AE-01", "element_type": "subcategory", "text": "A baseline of network operations and expected data flows for users and systems is established and managed", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-DE.AE-01", "element_type": "withdraw_reason", "text": "Incorporated into ID.AM-03", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.AE-02", "element_type": "subcategory", "text": "Potentially adverse events are analyzed to better understand associated activities", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.AE-02.290", "element_type": "implementation_example", "text": "Use security information and event management (SIEM) or other tools to continuously monitor log events for known malicious and suspicious activity", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.AE-02.291", "element_type": "implementation_example", "text": "Utilize up-to-date cyber threat intelligence in log analysis tools to improve detection accuracy and characterize threat actors, their methods, and indicators of compromise", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.AE-02.292", "element_type": "implementation_example", "text": "Regularly conduct manual reviews of log events for technologies that cannot be sufficiently monitored through automation", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.AE-02.293", "element_type": "implementation_example", "text": "Use log analysis tools to generate reports on their findings", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.AE-03", "element_type": "subcategory", "text": "Information is correlated from multiple sources", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.AE-03.294", "element_type": "implementation_example", "text": "Constantly transfer log data generated by other sources to a relatively small number of log servers", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.AE-03.295", "element_type": "implementation_example", "text": "Use event correlation technology (e.g., SIEM) to collect information captured by multiple sources", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.AE-03.296", "element_type": "implementation_example", "text": "Utilize cyber threat intelligence to help correlate events among log sources", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.AE-04", "element_type": "subcategory", "text": "The estimated impact and scope of adverse events are understood", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.AE-04.297", "element_type": "implementation_example", "text": "Use SIEMs or other tools to estimate impact and scope, and review and refine the estimates", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.AE-04.298", "element_type": "implementation_example", "text": "A person creates their own estimates of impact and scope", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.AE-05", "element_type": "subcategory", "text": "Incident alert thresholds are established", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-DE.AE-05", "element_type": "withdraw_reason", "text": "Moved to DE.AE-08", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.AE-06", "element_type": "subcategory", "text": "Information on adverse events is provided to authorized staff and tools", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.AE-06.299", "element_type": "implementation_example", "text": "Use cybersecurity software to generate alerts and provide them to the security operations center (SOC), incident responders, and incident response tools", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.AE-06.300", "element_type": "implementation_example", "text": "Incident responders and other authorized personnel can access log analysis findings at all times", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.AE-06.301", "element_type": "implementation_example", "text": "Automatically create and assign tickets in the organization's ticketing system when certain types of alerts occur", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.AE-06.302", "element_type": "implementation_example", "text": "Manually create and assign tickets in the organization's ticketing system when technical staff discover indicators of compromise", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.AE-07", "element_type": "subcategory", "text": "Cyber threat intelligence and other contextual information are integrated into the analysis", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.AE-07.303", "element_type": "implementation_example", "text": "Securely provide cyber threat intelligence feeds to detection technologies, processes, and personnel", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.AE-07.304", "element_type": "implementation_example", "text": "Securely provide information from asset inventories to detection technologies, processes, and personnel", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.AE-07.305", "element_type": "implementation_example", "text": "Rapidly acquire and analyze vulnerability disclosures for the organization's technologies from suppliers, vendors, and third-party security advisories", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.AE-08", "element_type": "subcategory", "text": "Incidents are declared when adverse events meet the defined incident criteria", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.AE-08.306", "element_type": "implementation_example", "text": "Apply incident criteria to known and assumed characteristics of activity in order to determine whether an incident should be declared", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.AE-08.307", "element_type": "implementation_example", "text": "Take known false positives into account when applying incident criteria", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.DP-01", "element_type": "subcategory", "text": "Roles and responsibilities for detection are well defined to ensure accountability", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-DE.DP-01", "element_type": "withdraw_reason", "text": "Incorporated into GV.RR-02", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.DP-02", "element_type": "subcategory", "text": "Detection activities comply with all applicable requirements", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-DE.DP-02", "element_type": "withdraw_reason", "text": "Incorporated into DE.AE", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.DP-03", "element_type": "subcategory", "text": "Detection processes are tested", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-DE.DP-03", "element_type": "withdraw_reason", "text": "Incorporated into ID.IM-02", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.DP-04", "element_type": "subcategory", "text": "Event detection information is communicated", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-DE.DP-04", "element_type": "withdraw_reason", "text": "Incorporated into DE.AE-06", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "DE.DP-05", "element_type": "subcategory", "text": "Detection processes are continuously improved", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-DE.DP-05", "element_type": "withdraw_reason", "text": "Incorporated into ID.IM, ID.IM-03", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-DE.DP", "element_type": "withdraw_reason", "text": "Incorporated into other Categories and Functions", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS", "element_type": "function", "text": "Actions regarding a detected cybersecurity incident are taken", "title": "RESPOND"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.MA", "element_type": "category", "text": "Responses to detected cybersecurity incidents are managed", "title": "Incident Management"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.MA-01", "element_type": "subcategory", "text": "The incident response plan is executed in coordination with relevant third parties once an incident is declared", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.MA-01.308", "element_type": "implementation_example", "text": "Detection technologies automatically report confirmed incidents", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.MA-01.309", "element_type": "implementation_example", "text": "Request incident response assistance from the organization's incident response outsourcer", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.MA-01.310", "element_type": "implementation_example", "text": "Designate an incident lead for each incident", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.MA-01.311", "element_type": "implementation_example", "text": "Initiate execution of additional cybersecurity plans as needed to support incident response (for example, business continuity and disaster recovery)", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.MA-02", "element_type": "subcategory", "text": "Incident reports are triaged and validated", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.MA-02.312", "element_type": "implementation_example", "text": "Preliminarily review incident reports to confirm that they are cybersecurity-related and necessitate incident response activities", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.MA-02.313", "element_type": "implementation_example", "text": "Apply criteria to estimate the severity of an incident", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.MA-03", "element_type": "subcategory", "text": "Incidents are categorized and prioritized", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.MA-03.314", "element_type": "implementation_example", "text": "Further review and categorize incidents based on the type of incident (e.g., data breach, ransomware, DDoS, account compromise)", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.MA-03.315", "element_type": "implementation_example", "text": "Prioritize incidents based on their scope, likely impact, and time-critical nature", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.MA-03.316", "element_type": "implementation_example", "text": "Select incident response strategies for active incidents by balancing the need to quickly recover from an incident with the need to observe the attacker or conduct a more thorough investigation", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.MA-04", "element_type": "subcategory", "text": "Incidents are escalated or elevated as needed", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.MA-04.317", "element_type": "implementation_example", "text": "Track and validate the status of all ongoing incidents", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.MA-04.318", "element_type": "implementation_example", "text": "Coordinate incident escalation or elevation with designated internal and external stakeholders", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.MA-05", "element_type": "subcategory", "text": "The criteria for initiating incident recovery are applied", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.MA-05.319", "element_type": "implementation_example", "text": "Apply incident recovery criteria to known and assumed characteristics of the incident to determine whether incident recovery processes should be initiated", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.MA-05.320", "element_type": "implementation_example", "text": "Take the possible operational disruption of incident recovery activities into account", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.AN", "element_type": "category", "text": "Investigations are conducted to ensure effective response and support forensics and recovery activities", "title": "Incident Analysis"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.AN-01", "element_type": "subcategory", "text": "Notifications from detection systems are investigated", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-RS.AN-01", "element_type": "withdraw_reason", "text": "Incorporated into RS.MA-02", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.AN-02", "element_type": "subcategory", "text": "The impact of the incident is understood", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-RS.AN-02", "element_type": "withdraw_reason", "text": "Incorporated into RS.MA-02, RS.MA-03, RS.MA-04", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.AN-03", "element_type": "subcategory", "text": "Analysis is performed to establish what has taken place during an incident and the root cause of the incident", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.AN-03.321", "element_type": "implementation_example", "text": "Determine the sequence of events that occurred during the incident and which assets and resources were involved in each event", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.AN-03.322", "element_type": "implementation_example", "text": "Attempt to determine what vulnerabilities, threats, and threat actors were directly or indirectly involved in the incident", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.AN-03.323", "element_type": "implementation_example", "text": "Analyze the incident to find the underlying, systemic root causes", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.AN-03.324", "element_type": "implementation_example", "text": "Check any cyber deception technology for additional information on attacker behavior", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.AN-04", "element_type": "subcategory", "text": "Incidents are categorized consistent with response plans", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-RS.AN-04", "element_type": "withdraw_reason", "text": "Moved to RS.MA-03", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.AN-05", "element_type": "subcategory", "text": "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)", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-RS.AN-05", "element_type": "withdraw_reason", "text": "Moved to ID.RA-08", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.AN-06", "element_type": "subcategory", "text": "Actions performed during an investigation are recorded, and the records' integrity and provenance are preserved", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.AN-06.325", "element_type": "implementation_example", "text": "Require each incident responder and others (e.g., system administrators, cybersecurity engineers) who perform incident response tasks to record their actions and make the record immutable", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.AN-06.326", "element_type": "implementation_example", "text": "Require the incident lead to document the incident in detail and be responsible for preserving the integrity of the documentation and the sources of all information being reported", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.AN-07", "element_type": "subcategory", "text": "Incident data and metadata are collected, and their integrity and provenance are preserved", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.AN-07.327", "element_type": "implementation_example", "text": "Collect, preserve, and safeguard the integrity of all pertinent incident data and metadata (e.g., data source, date/time of collection) based on evidence preservation and chain-of-custody procedures", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.AN-08", "element_type": "subcategory", "text": "An incident's magnitude is estimated and validated", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.AN-08.328", "element_type": "implementation_example", "text": "Review other potential targets of the incident to search for indicators of compromise and evidence of persistence", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.AN-08.329", "element_type": "implementation_example", "text": "Automatically run tools on targets to look for indicators of compromise and evidence of persistence", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.CO", "element_type": "category", "text": "Response activities are coordinated with internal and external stakeholders as required by laws, regulations, or policies", "title": "Incident Response Reporting and Communication"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.CO-01", "element_type": "subcategory", "text": "Personnel know their roles and order of operations when a response is needed", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-RS.CO-01", "element_type": "withdraw_reason", "text": "Incorporated into PR.AT-01", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.CO-02", "element_type": "subcategory", "text": "Internal and external stakeholders are notified of incidents", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.CO-02.330", "element_type": "implementation_example", "text": "Follow the organization's breach notification procedures after discovering a data breach incident, including notifying affected customers", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.CO-02.331", "element_type": "implementation_example", "text": "Notify business partners and customers of incidents in accordance with contractual requirements", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.CO-02.332", "element_type": "implementation_example", "text": "Notify law enforcement agencies and regulatory bodies of incidents based on criteria in the incident response plan and management approval", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.CO-03", "element_type": "subcategory", "text": "Information is shared with designated internal and external stakeholders", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.CO-03.333", "element_type": "implementation_example", "text": "Securely share information consistent with response plans and information sharing agreements", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.CO-03.334", "element_type": "implementation_example", "text": "Voluntarily share information about an attacker's observed TTPs, with all sensitive data removed, with an Information Sharing and Analysis Center (ISAC)", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.CO-03.335", "element_type": "implementation_example", "text": "Notify HR when malicious insider activity occurs", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.CO-03.336", "element_type": "implementation_example", "text": "Regularly update senior leadership on the status of major incidents", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.CO-03.337", "element_type": "implementation_example", "text": "Follow the rules and protocols defined in contracts for incident information sharing between the organization and its suppliers", "title": "Ex5"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.CO-03.338", "element_type": "implementation_example", "text": "Coordinate crisis communication methods between the organization and its critical suppliers", "title": "Ex6"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.CO-04", "element_type": "subcategory", "text": "Coordination with stakeholders occurs consistent with response plans", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-RS.CO-04", "element_type": "withdraw_reason", "text": "Incorporated into RS.MA-01, RS.MA-04", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.CO-05", "element_type": "subcategory", "text": "Voluntary information sharing occurs with external stakeholders to achieve broader cybersecurity situational awareness", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-RS.CO-05", "element_type": "withdraw_reason", "text": "Incorporated into RS.CO-03", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.MI", "element_type": "category", "text": "Activities are performed to prevent expansion of an event and mitigate its effects", "title": "Incident Mitigation"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.MI-01", "element_type": "subcategory", "text": "Incidents are contained", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.MI-01.339", "element_type": "implementation_example", "text": "Cybersecurity technologies (e.g., antivirus software) and cybersecurity features of other technologies (e.g., operating systems, network infrastructure devices) automatically perform containment actions", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.MI-01.340", "element_type": "implementation_example", "text": "Allow incident responders to manually select and perform containment actions", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.MI-01.341", "element_type": "implementation_example", "text": "Allow a third party (e.g., internet service provider, managed security service provider) to perform containment actions on behalf of the organization", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.MI-01.342", "element_type": "implementation_example", "text": "Automatically transfer compromised endpoints to a remediation virtual local area network (VLAN)", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.MI-02", "element_type": "subcategory", "text": "Incidents are eradicated", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.MI-02.343", "element_type": "implementation_example", "text": "Cybersecurity technologies and cybersecurity features of other technologies (e.g., operating systems, network infrastructure devices) automatically perform eradication actions", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.MI-02.344", "element_type": "implementation_example", "text": "Allow incident responders to manually select and perform eradication actions", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.MI-02.345", "element_type": "implementation_example", "text": "Allow a third party (e.g., managed security service provider) to perform eradication actions on behalf of the organization", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.MI-03", "element_type": "subcategory", "text": "Newly identified vulnerabilities are mitigated or documented as accepted risks", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-RS.MI-03", "element_type": "withdraw_reason", "text": "Incorporated into ID.RA-06", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.RP-01", "element_type": "subcategory", "text": "Response plan is executed during or after an incident", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-RS.RP-01", "element_type": "withdraw_reason", "text": "Incorporated into RS.MA-01", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-RS.RP", "element_type": "withdraw_reason", "text": "Incorporated into RS.MA", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.IM-01", "element_type": "subcategory", "text": "Response plans incorporate lessons learned", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-RS.IM-01", "element_type": "withdraw_reason", "text": "Incorporated into ID.IM-03, ID.IM-04", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RS.IM-02", "element_type": "subcategory", "text": "Response strategies are updated", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-RS.IM-02", "element_type": "withdraw_reason", "text": "Incorporated into ID.IM-03", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-RS.IM", "element_type": "withdraw_reason", "text": "Incorporated into ID.IM", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RC", "element_type": "function", "text": "Assets and operations affected by a cybersecurity incident are restored", "title": "RECOVER"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RC.RP", "element_type": "category", "text": "Restoration activities are performed to ensure operational availability of systems and services affected by cybersecurity incidents", "title": "Incident Recovery Plan Execution"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RC.RP-01", "element_type": "subcategory", "text": "The recovery portion of the incident response plan is executed once initiated from the incident response process", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RC.RP-01.346", "element_type": "implementation_example", "text": "Begin recovery procedures during or after incident response processes", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RC.RP-01.347", "element_type": "implementation_example", "text": "Make all individuals with recovery responsibilities aware of the plans for recovery and the authorizations required to implement each aspect of the plans", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RC.RP-02", "element_type": "subcategory", "text": "Recovery actions are selected, scoped, prioritized, and performed", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RC.RP-02.348", "element_type": "implementation_example", "text": "Select recovery actions based on the criteria defined in the incident response plan and available resources", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RC.RP-02.349", "element_type": "implementation_example", "text": "Change planned recovery actions based on a reassessment of organizational needs and resources", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RC.RP-03", "element_type": "subcategory", "text": "The integrity of backups and other restoration assets is verified before using them for restoration", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RC.RP-03.350", "element_type": "implementation_example", "text": "Check restoration assets for indicators of compromise, file corruption, and other integrity issues before use", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RC.RP-04", "element_type": "subcategory", "text": "Critical mission functions and cybersecurity risk management are considered to establish post-incident operational norms", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RC.RP-04.351", "element_type": "implementation_example", "text": "Use business impact and system categorization records (including service delivery objectives) to validate that essential services are restored in the appropriate order", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RC.RP-04.352", "element_type": "implementation_example", "text": "Work with system owners to confirm the successful restoration of systems and the return to normal operations", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RC.RP-04.353", "element_type": "implementation_example", "text": "Monitor the performance of restored systems to verify the adequacy of the restoration", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RC.RP-05", "element_type": "subcategory", "text": "The integrity of restored assets is verified, systems and services are restored, and normal operating status is confirmed", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RC.RP-05.354", "element_type": "implementation_example", "text": "Check restored assets for indicators of compromise and remediation of root causes of the incident before production use", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RC.RP-05.355", "element_type": "implementation_example", "text": "Verify the correctness and adequacy of the restoration actions taken before putting a restored system online", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RC.RP-06", "element_type": "subcategory", "text": "The end of incident recovery is declared based on criteria, and incident-related documentation is completed", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RC.RP-06.356", "element_type": "implementation_example", "text": "Prepare an after-action report that documents the incident itself, the response and recovery actions taken, and lessons learned", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RC.RP-06.357", "element_type": "implementation_example", "text": "Declare the end of incident recovery once the criteria are met", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RC.CO", "element_type": "category", "text": "Restoration activities are coordinated with internal and external parties", "title": "Incident Recovery Communication"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RC.CO-01", "element_type": "subcategory", "text": "Public relations are managed", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-RC.CO-01", "element_type": "withdraw_reason", "text": "Incorporated into RC.CO-04", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RC.CO-02", "element_type": "subcategory", "text": "Reputation is repaired after an incident", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-RC.CO-02", "element_type": "withdraw_reason", "text": "Incorporated into RC.CO-04", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RC.CO-03", "element_type": "subcategory", "text": "Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "third", "element_type": "party", "text": "3rd Party Risk", "title": "3rd"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RC.CO-03.358", "element_type": "implementation_example", "text": "Securely share recovery information, including restoration progress, consistent with response plans and information sharing agreements", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RC.CO-03.359", "element_type": "implementation_example", "text": "Regularly update senior leadership on recovery status and restoration progress for major incidents", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RC.CO-03.360", "element_type": "implementation_example", "text": "Follow the rules and protocols defined in contracts for incident information sharing between the organization and its suppliers", "title": "Ex3"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RC.CO-03.361", "element_type": "implementation_example", "text": "Coordinate crisis communication between the organization and its critical suppliers", "title": "Ex4"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RC.CO-04", "element_type": "subcategory", "text": "Public updates on incident recovery are shared using approved methods and messaging", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "first", "element_type": "party", "text": "1st Party Risk", "title": "1st"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RC.CO-04.362", "element_type": "implementation_example", "text": "Follow the organization's breach notification procedures for recovering from a data breach incident", "title": "Ex1"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RC.CO-04.363", "element_type": "implementation_example", "text": "Explain the steps being taken to recover from the incident and to prevent a recurrence", "title": "Ex2"}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RC.IM-01", "element_type": "subcategory", "text": "Recovery plans incorporate lessons learned", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-RC.IM-01", "element_type": "withdraw_reason", "text": "Incorporated into ID.IM-03, ID.IM-04", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "RC.IM-02", "element_type": "subcategory", "text": "Recovery strategies are updated", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-RC.IM-02", "element_type": "withdraw_reason", "text": "Incorporated into ID.IM-03", "title": ""}
{"doc_identifier": "CSF_2_0_0", "element_identifier": "WR-RC.IM", "element_type": "withdraw_reason", "text": "Incorporated into ID.IM", "title": ""}
{"element_type": "category", "element_identifier": "GV.OC", "title": "Organizational Context", "text": "The circumstances - mission, stakeholder expectations, dependencies, and legal, regulatory, and contractual requirements - surrounding the organization's cybersecurity risk management decisions are understood", "doc_identifier": "CSF_2_0_0"}
{"element_type": "category", "element_identifier": "GV.RM", "title": "Risk Management Strategy", "text": "The organization's priorities, constraints, risk tolerance and appetite statements, and assumptions are established, communicated, and used to support operational risk decisions", "doc_identifier": "CSF_2_0_0"}
{"element_type": "category", "element_identifier": "GV.RR", "title": "Roles, Responsibilities, and Authorities", "text": "Cybersecurity roles, responsibilities, and authorities to foster accountability, performance assessment, and continuous improvement are established and communicated", "doc_identifier": "CSF_2_0_0"}
{"element_type": "category", "element_identifier": "GV.PO", "title": "Policy", "text": "Organizational cybersecurity policy is established, communicated, and enforced", "doc_identifier": "CSF_2_0_0"}
{"element_type": "category", "element_identifier": "GV.OV", "title": "Oversight", "text": "Results of organization-wide cybersecurity risk management activities and performance are used to inform, improve, and adjust the risk management strategy", "doc_identifier": "CSF_2_0_0"}
{"element_type": "category", "element_identifier": "GV.SC", "title": "Cybersecurity Supply Chain Risk Management", "text": "Cyber supply chain risk management processes are identified, established, managed, monitored, and improved by organizational stakeholders", "doc_identifier": "CSF_2_0_0"}
{"element_type": "category", "element_identifier": "ID.AM", "title": "Asset Management", "text": "Assets (e.g., data, hardware, software, systems, facilities, services, people) 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", "doc_identifier": "CSF_2_0_0"}
{"element_type": "category", "element_identifier": "ID.RA", "title": "Risk Assessment", "text": "The cybersecurity risk to the organization, assets, and individuals is understood by the organization", "doc_identifier": "CSF_2_0_0"}
{"element_type": "category", "element_identifier": "ID.IM", "title": "Improvement", "text": "Improvements to organizational cybersecurity risk management processes, procedures and activities are identified across all CSF Functions", "doc_identifier": "CSF_2_0_0"}
{"element_type": "category", "element_identifier": "PR.AA", "title": "Identity Management, Authentication, and Access Control", "text": "Access to physical and logical assets is limited to authorized users, services, and hardware and  managed commensurate with the assessed risk of unauthorized access", "doc_identifier": "CSF_2_0_0"}
{"element_type": "category", "element_identifier": "PR.AT", "title": "Awareness and Training", "text": "The organization's personnel are provided with cybersecurity awareness and training so that they can perform their cybersecurity-related tasks", "doc_identifier": "CSF_2_0_0"}
{"element_type": "category", "element_identifier": "PR.DS", "title": "Data Security", "text": "Data are managed consistent with the organization's risk strategy to protect the confidentiality, integrity, and availability of information", "doc_identifier": "CSF_2_0_0"}
{"element_type": "category", "element_identifier": "PR.PS", "title": "Platform Security", "text": "The hardware, software (e.g., firmware, operating systems, applications), and services of physical and virtual platforms are managed consistent with the organization's risk strategy to protect their confidentiality, integrity, and availability", "doc_identifier": "CSF_2_0_0"}
{"element_type": "category", "element_identifier": "PR.IR", "title": "Technology Infrastructure Resilience", "text": "Security architectures are managed with the organization's risk strategy to protect asset confidentiality, integrity, and availability, and organizational resilience", "doc_identifier": "CSF_2_0_0"}
{"element_type": "category", "element_identifier": "DE.CM", "title": "Continuous Monitoring", "text": "Assets are monitored to find anomalies, indicators of compromise, and other potentially adverse events", "doc_identifier": "CSF_2_0_0"}
{"element_type": "category", "element_identifier": "DE.AE", "title": "Adverse Event Analysis", "text": "Anomalies, indicators of compromise, and other potentially adverse events are analyzed to characterize the events and detect cybersecurity incidents", "doc_identifier": "CSF_2_0_0"}
{"element_type": "category", "element_identifier": "RS.MA", "title": "Incident Management", "text": "Responses to detected cybersecurity incidents are managed", "doc_identifier": "CSF_2_0_0"}
{"element_type": "category", "element_identifier": "RS.AN", "title": "Incident Analysis", "text": "Investigations are conducted to ensure effective response and support forensics and recovery activities", "doc_identifier": "CSF_2_0_0"}
{"element_type": "category", "element_identifier": "RS.CO", "title": "Incident Response Reporting and Communication", "text": "Response activities are coordinated with internal and external stakeholders as required by laws, regulations, or policies", "doc_identifier": "CSF_2_0_0"}
{"element_type": "category", "element_identifier": "RS.MI", "title": "Incident Mitigation", "text": "Activities are performed to prevent expansion of an event and mitigate its effects", "doc_identifier": "CSF_2_0_0"}
{"element_type": "category", "element_identifier": "RC.RP", "title": "Incident Recovery Plan Execution", "text": "Restoration activities are performed to ensure operational availability of systems and services affected by cybersecurity incidents", "doc_identifier": "CSF_2_0_0"}
{"element_type": "category", "element_identifier": "RC.CO", "title": "Incident Recovery Communication", "text": "Restoration activities are coordinated with internal and external parties", "doc_identifier": "CSF_2_0_0"}
{"element_type": "function", "element_identifier": "GV", "title": "GOVERN", "text": "The organization's cybersecurity risk management strategy, expectations, and policy are established, communicated, and monitored", "doc_identifier": "CSF_2_0_0"}
{"element_type": "function", "element_identifier": "ID", "title": "IDENTIFY", "text": "The organization's current cybersecurity risks are understood", "doc_identifier": "CSF_2_0_0"}
{"element_type": "function", "element_identifier": "PR", "title": "PROTECT", "text": "Safeguards to manage the organization's cybersecurity risks are used", "doc_identifier": "CSF_2_0_0"}
{"element_type": "function", "element_identifier": "DE", "title": "DETECT", "text": "Possible cybersecurity attacks and compromises are found and analyzed", "doc_identifier": "CSF_2_0_0"}
{"element_type": "function", "element_identifier": "RS", "title": "RESPOND", "text": "Actions regarding a detected cybersecurity incident are taken", "doc_identifier": "CSF_2_0_0"}
{"element_type": "function", "element_identifier": "RC", "title": "RECOVER", "text": "Assets and operations affected by a cybersecurity incident are restored", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.OC-01.001", "title": "Ex1", "text": "Share the organization's mission (e.g., through vision and mission statements, marketing, and service strategies) to provide a basis for identifying risks that may impede that mission", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.OC-02.002", "title": "Ex1", "text": "Identify relevant internal stakeholders and their cybersecurity-related expectations (e.g., performance and risk expectations of officers, directors, and advisors; cultural expectations of employees)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.OC-02.003", "title": "Ex2", "text": "Identify relevant external stakeholders and their cybersecurity-related expectations (e.g., privacy expectations of customers, business expectations of partnerships, compliance expectations of regulators, ethics expectations of society)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.OC-03.004", "title": "Ex1", "text": "Determine a process to track and manage legal and regulatory requirements regarding protection of individuals' information (e.g., Health Insurance Portability and Accountability Act, California Consumer Privacy Act, General Data Protection Regulation)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.OC-03.005", "title": "Ex2", "text": "Determine a process to track and manage contractual requirements for cybersecurity management of supplier, customer, and partner information", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.OC-03.006", "title": "Ex3", "text": "Align the organization's cybersecurity strategy with legal, regulatory, and contractual requirements", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.OC-04.007", "title": "Ex1", "text": "Establish criteria for determining the criticality of capabilities and services as viewed by internal and external stakeholders", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.OC-04.008", "title": "Ex2", "text": "Determine (e.g., from a business impact analysis) assets and business operations that are vital to achieving mission objectives and the potential impact of a loss (or partial loss) of such operations", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.OC-04.009", "title": "Ex3", "text": "Establish and communicate resilience objectives (e.g., recovery time objectives) for delivering critical capabilities and services in various operating states (e.g., under attack, during recovery, normal operation)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.OC-05.010", "title": "Ex1", "text": "Create an inventory of the organization's dependencies on external resources (e.g., facilities, cloud-based hosting providers) and their relationships to organizational assets and business functions", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.OC-05.011", "title": "Ex2", "text": "Identify and document external dependencies that are potential points of failure for the organization's critical capabilities and services, and share that information with appropriate personnel", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RM-01.012", "title": "Ex1", "text": "Update near-term and long-term cybersecurity risk management objectives as part of annual strategic planning and when major changes occur", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RM-01.013", "title": "Ex2", "text": "Establish measurable objectives for cybersecurity risk management (e.g., manage the quality of user training, ensure adequate risk protection for industrial control systems)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RM-01.014", "title": "Ex3", "text": "Senior leaders agree about cybersecurity objectives and use them for measuring and managing risk and performance", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RM-02.015", "title": "Ex1", "text": "Determine and communicate risk appetite statements that convey expectations about the appropriate level of risk for the organization", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RM-02.016", "title": "Ex2", "text": "Translate risk appetite statements into specific, measurable, and broadly understandable risk tolerance statements", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RM-02.017", "title": "Ex3", "text": "Refine organizational objectives and risk appetite periodically based on known risk exposure and residual risk", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RM-03.018", "title": "Ex1", "text": "Aggregate and manage cybersecurity risks alongside other enterprise risks (e.g., compliance, financial, operational, regulatory, reputational, safety)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RM-03.019", "title": "Ex2", "text": "Include cybersecurity risk managers in enterprise risk management planning", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RM-03.020", "title": "Ex3", "text": "Establish criteria for escalating cybersecurity risks within enterprise risk management", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RM-04.021", "title": "Ex1", "text": "Specify criteria for accepting and avoiding cybersecurity risk for various classifications of data", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RM-04.022", "title": "Ex2", "text": "Determine whether to purchase cybersecurity insurance", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RM-04.023", "title": "Ex3", "text": "Document conditions under which shared responsibility models are acceptable (e.g., outsourcing certain cybersecurity functions, having a third party perform financial transactions on behalf of the organization, using public cloud-based services)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RM-05.024", "title": "Ex1", "text": "Determine how to update senior executives, directors, and management on the organization's cybersecurity posture at agreed-upon intervals", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RM-05.025", "title": "Ex2", "text": "Identify how all departments across the organization - such as management, operations, internal auditors, legal, acquisition, physical security, and HR - will communicate with each other about cybersecurity risks", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RM-06.026", "title": "Ex1", "text": "Establish criteria for using a quantitative approach to cybersecurity risk analysis, and specify probability and exposure formulas", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RM-06.027", "title": "Ex2", "text": "Create and use templates (e.g., a risk register) to document cybersecurity risk information (e.g., risk description, exposure, treatment, and ownership)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RM-06.028", "title": "Ex3", "text": "Establish criteria for risk prioritization at the appropriate levels within the enterprise", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RM-06.029", "title": "Ex4", "text": "Use a consistent list of risk categories to support integrating, aggregating, and comparing cybersecurity risks", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RM-07.030", "title": "Ex1", "text": "Define and communicate guidance and methods for identifying opportunities and including them in risk discussions (e.g., strengths, weaknesses, opportunities, and threats [SWOT] analysis)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RM-07.031", "title": "Ex2", "text": "Identify stretch goals and document them", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RM-07.032", "title": "Ex3", "text": "Calculate, document, and prioritize positive risks alongside negative risks", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RR-01.033", "title": "Ex1", "text": "Leaders (e.g., directors) agree on their roles and responsibilities in developing, implementing, and assessing the organization's cybersecurity strategy", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RR-01.034", "title": "Ex2", "text": "Share leaders' expectations regarding a secure and ethical culture, especially when current events present the opportunity to highlight positive or negative examples of cybersecurity risk management", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RR-01.035", "title": "Ex3", "text": "Leaders direct the CISO to maintain a comprehensive cybersecurity risk strategy and review and update it at least annually and after major events", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RR-01.036", "title": "Ex4", "text": "Conduct reviews to ensure adequate authority and coordination among those responsible for managing cybersecurity risk", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RR-02.037", "title": "Ex1", "text": "Document risk management roles and responsibilities in policy", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RR-02.038", "title": "Ex2", "text": "Document who is responsible and accountable for cybersecurity risk management activities and how those teams and individuals are to be consulted and informed", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RR-02.039", "title": "Ex3", "text": "Include cybersecurity responsibilities and performance requirements in personnel descriptions", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RR-02.040", "title": "Ex4", "text": "Document performance goals for personnel with cybersecurity risk management responsibilities, and periodically measure performance to identify areas for improvement", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RR-02.041", "title": "Ex5", "text": "Clearly articulate cybersecurity responsibilities within operations, risk functions, and internal audit functions", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RR-03.042", "title": "Ex1", "text": "Conduct periodic management reviews to ensure that those given cybersecurity risk management responsibilities have the necessary authority", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RR-03.043", "title": "Ex2", "text": "Identify resource allocation and investment in line with risk tolerance and response", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RR-03.044", "title": "Ex3", "text": "Provide adequate and sufficient people, process, and technical resources to support the cybersecurity strategy", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RR-04.045", "title": "Ex1", "text": "Integrate cybersecurity risk management considerations into human resources processes (e.g., personnel screening, onboarding, change notification, offboarding)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RR-04.046", "title": "Ex2", "text": "Consider cybersecurity knowledge to be a positive factor in hiring, training, and retention decisions", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RR-04.047", "title": "Ex3", "text": "Conduct background checks prior to onboarding new personnel for sensitive roles, and periodically repeat background checks for personnel with such roles", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.RR-04.048", "title": "Ex4", "text": "Define and enforce obligations for personnel to be aware of, adhere to, and uphold security policies as they relate to their roles", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.PO-01.049", "title": "Ex1", "text": "Create, disseminate, and maintain an understandable, usable risk management policy with statements of management intent, expectations, and direction", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.PO-01.050", "title": "Ex2", "text": "Periodically review policy and supporting processes and procedures to ensure that they align with risk management strategy objectives and priorities, as well as the high-level direction of the cybersecurity policy", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.PO-01.051", "title": "Ex3", "text": "Require approval from senior management on policy", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.PO-01.052", "title": "Ex4", "text": "Communicate cybersecurity risk management policy and supporting processes and procedures across the organization", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.PO-01.053", "title": "Ex5", "text": "Require personnel to acknowledge receipt of policy when first hired, annually, and whenever policy is updated", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.PO-02.054", "title": "Ex1", "text": "Update policy based on periodic reviews of cybersecurity risk management results to ensure that policy and supporting processes and procedures adequately maintain risk at an acceptable level", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.PO-02.055", "title": "Ex2", "text": "Provide a timeline for reviewing changes to the organization's risk environment (e.g., changes in risk or in the organization's mission objectives), and communicate recommended policy updates", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.PO-02.056", "title": "Ex3", "text": "Update policy to reflect changes in legal and regulatory requirements", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.PO-02.057", "title": "Ex4", "text": "Update policy to reflect changes in technology (e.g., adoption of artificial intelligence) and changes to the business (e.g., acquisition of a new business, new contract requirements)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.OV-01.058", "title": "Ex1", "text": "Measure how well the risk management strategy and risk results have helped leaders make decisions and achieve organizational objectives", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.OV-01.059", "title": "Ex2", "text": "Examine whether cybersecurity risk strategies that impede operations or innovation should be adjusted", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.OV-02.060", "title": "Ex1", "text": "Review audit findings to confirm whether the existing cybersecurity strategy has ensured compliance with internal and external requirements", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.OV-02.061", "title": "Ex2", "text": "Review the performance oversight of those in cybersecurity-related roles to determine whether policy changes are necessary", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.OV-02.062", "title": "Ex3", "text": "Review strategy in light of cybersecurity incidents", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.OV-03.063", "title": "Ex1", "text": "Review key performance indicators (KPIs) to ensure that organization-wide policies and procedures achieve objectives", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.OV-03.064", "title": "Ex2", "text": "Review key risk indicators (KRIs) to identify risks the organization faces, including likelihood and potential impact", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.OV-03.065", "title": "Ex3", "text": "Collect and communicate metrics on cybersecurity risk management with senior leadership", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-01.066", "title": "Ex1", "text": "Establish a strategy that expresses the objectives of the cybersecurity supply chain risk management program", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-01.067", "title": "Ex2", "text": "Develop the cybersecurity supply chain risk management program, including a plan (with milestones), policies, and procedures that guide implementation and improvement of the program, and share the policies and procedures with the organizational stakeholders", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-01.068", "title": "Ex3", "text": "Develop and implement program processes based on the strategy, objectives, policies, and procedures that are agreed upon and performed by the organizational stakeholders", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-01.069", "title": "Ex4", "text": "Establish a cross-organizational mechanism that ensures alignment between functions that contribute to cybersecurity supply chain risk management, such as cybersecurity, IT, operations, legal, human resources, and engineering", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-02.070", "title": "Ex1", "text": "Identify one or more specific roles or positions that will be responsible and accountable for planning, resourcing, and executing cybersecurity supply chain risk management activities", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-02.071", "title": "Ex2", "text": "Document cybersecurity supply chain risk management roles and responsibilities in policy", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-02.072", "title": "Ex3", "text": "Create responsibility matrixes to document who will be responsible and accountable for cybersecurity supply chain risk management activities and how those teams and individuals will be consulted and informed", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-02.073", "title": "Ex4", "text": "Include cybersecurity supply chain risk management responsibilities and performance requirements in personnel descriptions to ensure clarity and improve accountability", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-02.074", "title": "Ex5", "text": "Document performance goals for personnel with cybersecurity risk management-specific responsibilities, and periodically measure them to demonstrate and improve performance", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-02.075", "title": "Ex6", "text": "Develop roles and responsibilities for suppliers, customers, and business partners to address shared responsibilities for applicable cybersecurity risks, and integrate them into organizational policies and applicable third-party agreements", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-02.076", "title": "Ex7", "text": "Internally communicate cybersecurity supply chain risk management roles and responsibilities for third parties", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-02.077", "title": "Ex8", "text": "Establish rules and protocols for information sharing and reporting processes between the organization and its suppliers", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-03.078", "title": "Ex1", "text": "Identify areas of alignment and overlap with cybersecurity and enterprise risk management", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-03.079", "title": "Ex2", "text": "Establish integrated control sets for cybersecurity risk management and cybersecurity supply chain risk management", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-03.080", "title": "Ex3", "text": "Integrate cybersecurity supply chain risk management into improvement processes", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-03.081", "title": "Ex4", "text": "Escalate material cybersecurity risks in supply chains to senior management, and address them at the enterprise risk management level", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-04.082", "title": "Ex1", "text": "Develop criteria for supplier criticality based on, for example, the sensitivity of data processed or possessed by suppliers, the degree of access to the organization's systems, and the importance of the products or services to the organization's mission", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-04.083", "title": "Ex2", "text": "Keep a record of all suppliers, and prioritize suppliers based on the criticality criteria", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-05.084", "title": "Ex1", "text": "Establish security requirements for suppliers, products, and services commensurate with their criticality level and potential impact if compromised", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-05.085", "title": "Ex2", "text": "Include all cybersecurity and supply chain requirements that third parties must follow and how compliance with the requirements may be verified in default contractual language", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-05.086", "title": "Ex3", "text": "Define the rules and protocols for information sharing between the organization and its suppliers and sub-tier suppliers in agreements", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-05.087", "title": "Ex4", "text": "Manage risk by including security requirements in agreements based on their criticality and potential impact if compromised", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-05.088", "title": "Ex5", "text": "Define security requirements in service-level agreements (SLAs) for monitoring suppliers for acceptable security performance throughout the supplier relationship lifecycle", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-05.089", "title": "Ex6", "text": "Contractually require suppliers to disclose cybersecurity features, functions, and vulnerabilities of their products and services for the life of the product or the term of service", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-05.090", "title": "Ex7", "text": "Contractually require suppliers to provide and maintain a current component inventory (e.g., software or hardware bill of materials) for critical products", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-05.091", "title": "Ex8", "text": "Contractually require suppliers to vet their employees and guard against insider threats", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-05.092", "title": "Ex9", "text": "Contractually require suppliers to provide evidence of performing acceptable security practices through, for example, self-attestation, conformance to known standards, certifications, or inspections", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-05.093", "title": "Ex10", "text": "Specify in contracts and other agreements the rights and responsibilities of the organization, its suppliers, and their supply chains, with respect to potential cybersecurity risks", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-06.094", "title": "Ex1", "text": "Perform thorough due diligence on prospective suppliers that is consistent with procurement planning and commensurate with the level of risk, criticality, and complexity of each supplier relationship", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-06.095", "title": "Ex2", "text": "Assess the suitability of the technology and cybersecurity capabilities and the risk management practices of prospective suppliers", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-06.096", "title": "Ex3", "text": "Conduct supplier risk assessments against business and applicable cybersecurity requirements", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-06.097", "title": "Ex4", "text": "Assess the authenticity, integrity, and security of critical products prior to acquisition and use", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-07.098", "title": "Ex1", "text": "Adjust assessment formats and frequencies based on the third party's reputation and the criticality of the products or services they provide", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-07.099", "title": "Ex2", "text": "Evaluate third parties' evidence of compliance with contractual cybersecurity requirements, such as self-attestations, warranties, certifications, and other artifacts", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-07.100", "title": "Ex3", "text": "Monitor critical suppliers to ensure that they are fulfilling their security obligations throughout the supplier relationship lifecycle using a variety of methods and techniques, such as inspections, audits, tests, or other forms of evaluation", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-07.101", "title": "Ex4", "text": "Monitor critical suppliers, services, and products for changes to their risk profiles, and reevaluate supplier criticality and risk impact accordingly", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-07.102", "title": "Ex5", "text": "Plan for unexpected supplier and supply chain-related interruptions to ensure business continuity", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-08.103", "title": "Ex1", "text": "Define and use rules and protocols for reporting incident response and recovery activities and the status between the organization and its suppliers", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-08.104", "title": "Ex2", "text": "Identify and document the roles and responsibilities of the organization and its suppliers for incident response", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-08.105", "title": "Ex3", "text": "Include critical suppliers in incident response exercises and simulations", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-08.106", "title": "Ex4", "text": "Define and coordinate crisis communication methods and protocols between the organization and its critical suppliers", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-08.107", "title": "Ex5", "text": "Conduct collaborative lessons learned sessions with critical suppliers", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-09.108", "title": "Ex1", "text": "Policies and procedures require provenance records for all acquired technology products and services", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-09.109", "title": "Ex2", "text": "Periodically provide risk reporting to leaders about how acquired components are proven to be untampered and authentic", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-09.110", "title": "Ex3", "text": "Communicate regularly among cybersecurity risk managers and operations personnel about the need to acquire software patches, updates, and upgrades only from authenticated and trustworthy software providers", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-09.111", "title": "Ex4", "text": "Review policies to ensure that they require approved supplier personnel to perform maintenance on supplier products", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-09.112", "title": "Ex5", "text": "Policies and procedure require checking upgrades to critical hardware for unauthorized changes", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-10.113", "title": "Ex1", "text": "Establish processes for terminating critical relationships under both normal and adverse circumstances", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-10.114", "title": "Ex2", "text": "Define and implement plans for component end-of-life maintenance support and obsolescence", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-10.115", "title": "Ex3", "text": "Verify that supplier access to organization resources is deactivated promptly when it is no longer needed", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-10.116", "title": "Ex4", "text": "Verify that assets containing the organization's data are returned or properly disposed of in a timely, controlled, and safe manner", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-10.117", "title": "Ex5", "text": "Develop and execute a plan for terminating or transitioning supplier relationships that takes supply chain security risk and resiliency into account", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-10.118", "title": "Ex6", "text": "Mitigate risks to data and systems created by supplier termination", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "GV.SC-10.119", "title": "Ex7", "text": "Manage data leakage risks associated with supplier termination", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.AM-01.120", "title": "Ex1", "text": "Maintain inventories for all types of hardware, including IT, IoT, OT, and mobile devices", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.AM-01.121", "title": "Ex2", "text": "Constantly monitor networks to detect new hardware and automatically update inventories", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.AM-02.122", "title": "Ex1", "text": "Maintain inventories for all types of software and services, including commercial-off-the-shelf, open-source, custom applications, API services, and cloud-based applications and services", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.AM-02.123", "title": "Ex2", "text": "Constantly monitor all platforms, including containers and virtual machines, for software and service inventory changes", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.AM-02.124", "title": "Ex3", "text": "Maintain an inventory of the organization's systems", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.AM-03.125", "title": "Ex1", "text": "Maintain baselines of communication and data flows within the organization's wired and wireless networks", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.AM-03.126", "title": "Ex2", "text": "Maintain baselines of communication and data flows between the organization and third parties", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.AM-03.127", "title": "Ex3", "text": "Maintain baselines of communication and data flows for the organization's infrastructure-as-a-service (IaaS) usage", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.AM-03.128", "title": "Ex4", "text": "Maintain documentation of expected network ports, protocols, and services that are typically used among authorized systems", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.AM-04.129", "title": "Ex1", "text": "Inventory all external services used by the organization, including third-party infrastructure-as-a-service (IaaS), platform-as-a-service (PaaS), and software-as-a-service (SaaS) offerings; APIs; and other externally hosted application services", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.AM-04.130", "title": "Ex2", "text": "Update the inventory when a new external service is going to be utilized to ensure adequate cybersecurity risk management monitoring of the organization's use of that service", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.AM-05.131", "title": "Ex1", "text": "Define criteria for prioritizing each class of assets", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.AM-05.132", "title": "Ex2", "text": "Apply the prioritization criteria to assets", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.AM-05.133", "title": "Ex3", "text": "Track the asset priorities and update them periodically or when significant changes to the organization occur", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.AM-07.134", "title": "Ex1", "text": "Maintain a list of the designated data types of interest (e.g., personally identifiable information, protected health information, financial account numbers, organization intellectual property, operational technology data)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.AM-07.135", "title": "Ex2", "text": "Continuously discover and analyze ad hoc data to identify new instances of designated data types", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.AM-07.136", "title": "Ex3", "text": "Assign data classifications to designated data types through tags or labels", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.AM-07.137", "title": "Ex4", "text": "Track the provenance, data owner, and geolocation of each instance of designated data types", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.AM-08.138", "title": "Ex1", "text": "Integrate cybersecurity considerations throughout the life cycles of systems, hardware, software, and services", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.AM-08.139", "title": "Ex2", "text": "Integrate cybersecurity considerations into product life cycles", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.AM-08.140", "title": "Ex3", "text": "Identify unofficial uses of technology to meet mission objectives (i.e., shadow IT)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.AM-08.141", "title": "Ex4", "text": "Periodically identify redundant systems, hardware, software, and services that unnecessarily increase the organization's attack surface", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.AM-08.142", "title": "Ex5", "text": "Properly configure and secure systems, hardware, software, and services prior to their deployment in production", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.AM-08.143", "title": "Ex6", "text": "Update inventories when systems, hardware, software, and services are moved or transferred within the organization", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.AM-08.144", "title": "Ex7", "text": "Securely destroy stored data based on the organization's data retention policy using the prescribed destruction method, and keep and manage a record of the destructions", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.AM-08.145", "title": "Ex8", "text": "Securely sanitize data storage when hardware is being retired, decommissioned, reassigned, or sent for repairs or replacement", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.AM-08.146", "title": "Ex9", "text": "Offer methods for destroying paper, storage media, and other physical forms of data storage", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.RA-01.147", "title": "Ex1", "text": "Use vulnerability management technologies to identify unpatched and misconfigured software", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.RA-01.148", "title": "Ex2", "text": "Assess network and system architectures for design and implementation weaknesses that affect cybersecurity", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.RA-01.149", "title": "Ex3", "text": "Review, analyze, or test organization-developed software to identify design, coding, and default configuration vulnerabilities", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.RA-01.150", "title": "Ex4", "text": "Assess facilities that house critical computing assets for physical vulnerabilities and resilience issues", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.RA-01.151", "title": "Ex5", "text": "Monitor sources of cyber threat intelligence for information on new vulnerabilities in products and services", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.RA-01.152", "title": "Ex6", "text": "Review processes and procedures for weaknesses that could be exploited to affect cybersecurity", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.RA-02.153", "title": "Ex1", "text": "Configure cybersecurity tools and technologies with detection or response capabilities to securely ingest cyber threat intelligence feeds", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.RA-02.154", "title": "Ex2", "text": "Receive and review advisories from reputable third parties on current threat actors and their tactics, techniques, and procedures (TTPs)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.RA-02.155", "title": "Ex3", "text": "Monitor sources of cyber threat intelligence for information on the types of vulnerabilities that emerging technologies may have", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.RA-03.156", "title": "Ex1", "text": "Use cyber threat intelligence to maintain awareness of the types of threat actors likely to target the organization and the TTPs they are likely to use", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.RA-03.157", "title": "Ex2", "text": "Perform threat hunting to look for signs of threat actors within the environment", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.RA-03.158", "title": "Ex3", "text": "Implement processes for identifying internal threat actors", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.RA-04.159", "title": "Ex1", "text": "Business leaders and cybersecurity risk management practitioners work together to estimate the likelihood and impact of risk scenarios and record them in risk registers", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.RA-04.160", "title": "Ex2", "text": "Enumerate the potential business impacts of unauthorized access to the organization's communications, systems, and data processed in or by those systems", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.RA-04.161", "title": "Ex3", "text": "Account for the potential impacts of cascading failures for systems of systems", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.RA-05.162", "title": "Ex1", "text": "Develop threat models to better understand risks to the data and identify appropriate risk responses", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.RA-05.163", "title": "Ex2", "text": "Prioritize cybersecurity resource allocations and investments based on estimated likelihoods and impacts", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.RA-06.164", "title": "Ex1", "text": "Apply the vulnerability management plan's criteria for deciding whether to accept, transfer, mitigate, or avoid risk", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.RA-06.165", "title": "Ex2", "text": "Apply the vulnerability management plan's criteria for selecting compensating controls to mitigate risk", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.RA-06.166", "title": "Ex3", "text": "Track the progress of risk response implementation (e.g., plan of action and milestones [POA&M], risk register, risk detail report)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.RA-06.167", "title": "Ex4", "text": "Use risk assessment findings to inform risk response decisions and actions", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.RA-06.168", "title": "Ex5", "text": "Communicate planned risk responses to affected stakeholders in priority order", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.RA-07.169", "title": "Ex1", "text": "Implement and follow procedures for the formal documentation, review, testing, and approval of proposed changes and requested exceptions", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.RA-07.170", "title": "Ex2", "text": "Document the possible risks of making or not making each proposed change, and provide guidance on rolling back changes", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.RA-07.171", "title": "Ex3", "text": "Document the risks related to each requested exception and the plan for responding to those risks", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.RA-07.172", "title": "Ex4", "text": "Periodically review risks that were accepted based upon planned future actions or milestones", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.RA-08.173", "title": "Ex1", "text": "Conduct vulnerability information sharing between the organization and its suppliers following the rules and protocols defined in contracts", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.RA-08.174", "title": "Ex2", "text": "Assign responsibilities and verify the execution of procedures for processing, analyzing the impact of, and responding to cybersecurity threat, vulnerability, or incident disclosures by suppliers, customers, partners, and government cybersecurity organizations", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.RA-09.175", "title": "Ex1", "text": "Assess the authenticity and cybersecurity of critical technology products and services prior to acquisition and use", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.RA-10.176", "title": "Ex1", "text": "Conduct supplier risk assessments against business and applicable cybersecurity requirements, including the supply chain", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.IM-01.177", "title": "Ex1", "text": "Perform self-assessments of critical services that take current threats and TTPs into consideration", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.IM-01.178", "title": "Ex2", "text": "Invest in third-party assessments or independent audits of the effectiveness of the organization's cybersecurity program to identify areas that need improvement", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.IM-01.179", "title": "Ex3", "text": "Constantly evaluate compliance with selected cybersecurity requirements through automated means", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.IM-02.180", "title": "Ex1", "text": "Identify improvements for future incident response activities based on findings from incident response assessments (e.g., tabletop exercises and simulations, tests, internal reviews, independent audits)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.IM-02.181", "title": "Ex2", "text": "Identify improvements for future business continuity, disaster recovery, and incident response activities based on exercises performed in coordination with critical service providers and product suppliers", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.IM-02.182", "title": "Ex3", "text": "Involve internal stakeholders (e.g., senior executives, legal department, HR) in security tests and exercises as appropriate", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.IM-02.183", "title": "Ex4", "text": "Perform penetration testing to identify opportunities to improve the security posture of selected high-risk systems as approved by leadership", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.IM-02.184", "title": "Ex5", "text": "Exercise contingency plans for responding to and recovering from the discovery that products or services did not originate with the contracted supplier or partner or were altered before receipt", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.IM-02.185", "title": "Ex6", "text": "Collect and analyze performance metrics using security tools and services to inform improvements to the cybersecurity program", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.IM-03.186", "title": "Ex1", "text": "Conduct collaborative lessons learned sessions with suppliers", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.IM-03.187", "title": "Ex2", "text": "Annually review cybersecurity policies, processes, and procedures to take lessons learned into account", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.IM-03.188", "title": "Ex3", "text": "Use metrics to assess operational cybersecurity performance over time", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.IM-04.189", "title": "Ex1", "text": "Establish contingency plans (e.g., incident response, business continuity, disaster recovery) for responding to and recovering from adverse events that can interfere with operations, expose confidential information, or otherwise endanger the organization's mission and viability", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.IM-04.190", "title": "Ex2", "text": "Include contact and communication information, processes for handling common scenarios, and criteria for prioritization, escalation, and elevation in all contingency plans", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.IM-04.191", "title": "Ex3", "text": "Create a vulnerability management plan to identify and assess all types of vulnerabilities and to prioritize, test, and implement risk responses", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.IM-04.192", "title": "Ex4", "text": "Communicate cybersecurity plans (including updates) to those responsible for carrying them out and to affected parties", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "ID.IM-04.193", "title": "Ex5", "text": "Review and update all cybersecurity plans annually or when a need for significant improvements is identified", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.AA-01.194", "title": "Ex1", "text": "Initiate requests for new access or additional access for employees, contractors, and others, and track, review, and fulfill the requests, with permission from system or data owners when needed", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.AA-01.195", "title": "Ex2", "text": "Issue, manage, and revoke cryptographic certificates and identity tokens, cryptographic keys (i.e., key management), and other credentials", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.AA-01.196", "title": "Ex3", "text": "Select a unique identifier for each device from immutable hardware characteristics or an identifier securely provisioned to the device", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.AA-01.197", "title": "Ex4", "text": "Physically label authorized hardware with an identifier for inventory and servicing purposes", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.AA-02.198", "title": "Ex1", "text": "Verify a person's claimed identity at enrollment time using government-issued identity credentials (e.g., passport, visa, driver's license)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.AA-02.199", "title": "Ex2", "text": "Issue a different credential for each person (i.e., no credential sharing)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.AA-03.200", "title": "Ex1", "text": "Require multifactor authentication", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.AA-03.201", "title": "Ex2", "text": "Enforce policies for the minimum strength of passwords, PINs, and similar authenticators", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.AA-03.202", "title": "Ex3", "text": "Periodically reauthenticate users, services, and hardware based on risk (e.g., in zero trust architectures)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.AA-03.203", "title": "Ex4", "text": "Ensure that authorized personnel can access accounts essential for protecting safety under emergency conditions", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.AA-04.204", "title": "Ex1", "text": "Protect identity assertions that are used to convey authentication and user information through single sign-on systems", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.AA-04.205", "title": "Ex2", "text": "Protect identity assertions that are used to convey authentication and user information between federated systems", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.AA-04.206", "title": "Ex3", "text": "Implement standards-based approaches for identity assertions in all contexts, and follow all guidance for the generation (e.g., data models, metadata), protection (e.g., digital signing, encryption), and verification (e.g., signature validation) of identity assertions", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.AA-05.207", "title": "Ex1", "text": "Review logical and physical access privileges periodically and whenever someone changes roles or leaves the organization, and promptly rescind privileges that are no longer needed", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.AA-05.208", "title": "Ex2", "text": "Take attributes of the requester and the requested resource into account for authorization decisions (e.g., geolocation, day/time, requester endpoint's cyber health)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.AA-05.209", "title": "Ex3", "text": "Restrict access and privileges to the minimum necessary (e.g., zero trust architecture)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.AA-05.210", "title": "Ex4", "text": "Periodically review the privileges associated with critical business functions to confirm proper separation of duties", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.AA-06.211", "title": "Ex1", "text": "Use security guards, security cameras, locked entrances, alarm systems, and other physical controls to monitor facilities and restrict access", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.AA-06.212", "title": "Ex2", "text": "Employ additional physical security controls for areas that contain high-risk assets", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.AA-06.213", "title": "Ex3", "text": "Escort guests, vendors, and other third parties within areas that contain business-critical assets", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.AT-01.214", "title": "Ex1", "text": "Provide basic cybersecurity awareness and training to employees, contractors, partners, suppliers, and all other users of the organization's non-public resources", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.AT-01.215", "title": "Ex2", "text": "Train personnel to recognize social engineering attempts and other common attacks, report attacks and suspicious activity, comply with acceptable use policies, and perform basic cyber hygiene tasks (e.g., patching software, choosing passwords, protecting credentials)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.AT-01.216", "title": "Ex3", "text": "Explain the consequences of cybersecurity policy violations, both to individual users and the organization as a whole", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.AT-01.217", "title": "Ex4", "text": "Periodically assess or test users on their understanding of basic cybersecurity practices", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.AT-01.218", "title": "Ex5", "text": "Require annual refreshers to reinforce existing practices and introduce new practices", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.AT-02.219", "title": "Ex1", "text": "Identify the specialized roles within the organization that require additional cybersecurity training, such as physical and cybersecurity personnel, finance personnel, senior leadership, and anyone with access to business-critical data", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.AT-02.220", "title": "Ex2", "text": "Provide role-based cybersecurity awareness and training to all those in specialized roles, including contractors, partners, suppliers, and other third parties", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.AT-02.221", "title": "Ex3", "text": "Periodically assess or test users on their understanding of cybersecurity practices for their specialized roles", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.AT-02.222", "title": "Ex4", "text": "Require annual refreshers to reinforce existing practices and introduce new practices", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.DS-01.223", "title": "Ex1", "text": "Use encryption, digital signatures, and cryptographic hashes to protect the confidentiality and integrity of stored data in files, databases, virtual machine disk images, container images, and other resources", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.DS-01.224", "title": "Ex2", "text": "Use full disk encryption to protect data stored on user endpoints", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.DS-01.225", "title": "Ex3", "text": "Confirm the integrity of software by validating signatures", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.DS-01.226", "title": "Ex4", "text": "Restrict the use of removable media to prevent data exfiltration", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.DS-01.227", "title": "Ex5", "text": "Physically secure removable media containing unencrypted sensitive information, such as within locked offices or file cabinets", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.DS-02.228", "title": "Ex1", "text": "Use encryption, digital signatures, and cryptographic hashes to protect the confidentiality and integrity of network communications", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.DS-02.229", "title": "Ex2", "text": "Automatically encrypt or block outbound emails and other communications that contain sensitive data, depending on the data classification", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.DS-02.230", "title": "Ex3", "text": "Block access to personal email, file sharing, file storage services, and other personal communications applications and services from organizational systems and networks", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.DS-02.231", "title": "Ex4", "text": "Prevent reuse of sensitive data from production environments (e.g., customer records) in development, testing, and other non-production environments", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.DS-10.232", "title": "Ex1", "text": "Remove data that must remain confidential (e.g., from processors and memory) as soon as it is no longer needed", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.DS-10.233", "title": "Ex2", "text": "Protect data in use from access by other users and processes of the same platform", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.DS-11.234", "title": "Ex1", "text": "Continuously back up critical data in near-real-time, and back up other data frequently at agreed-upon schedules", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.DS-11.235", "title": "Ex2", "text": "Test backups and restores for all types of data sources at least annually", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.DS-11.236", "title": "Ex3", "text": "Securely store some backups offline and offsite so that an incident or disaster will not damage them", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.DS-11.237", "title": "Ex4", "text": "Enforce geographic separation and geolocation restrictions for data backup storage", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.PS-01.238", "title": "Ex1", "text": "Establish, test, deploy, and maintain hardened baselines that enforce the organization's cybersecurity policies and provide only essential capabilities (i.e., principle of least functionality)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.PS-01.239", "title": "Ex2", "text": "Review all default configuration settings that may potentially impact cybersecurity when installing or upgrading software", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.PS-01.240", "title": "Ex3", "text": "Monitor implemented software for deviations from approved baselines", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.PS-02.241", "title": "Ex1", "text": "Perform routine and emergency patching within the timeframes specified in the vulnerability management plan", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.PS-02.242", "title": "Ex2", "text": "Update container images, and deploy new container instances to replace rather than update existing instances", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.PS-02.243", "title": "Ex3", "text": "Replace end-of-life software and service versions with supported, maintained versions", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.PS-02.244", "title": "Ex4", "text": "Uninstall and remove unauthorized software and services that pose undue risks", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.PS-02.245", "title": "Ex5", "text": "Uninstall and remove any unnecessary software components (e.g., operating system utilities) that attackers might misuse", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.PS-02.246", "title": "Ex6", "text": "Define and implement plans for software and service end-of-life maintenance support and obsolescence", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.PS-03.247", "title": "Ex1", "text": "Replace hardware when it lacks needed security capabilities or when it cannot support software with needed security capabilities", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.PS-03.248", "title": "Ex2", "text": "Define and implement plans for hardware end-of-life maintenance support and obsolescence", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.PS-03.249", "title": "Ex3", "text": "Perform hardware disposal in a secure, responsible, and auditable manner", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.PS-04.250", "title": "Ex1", "text": "Configure all operating systems, applications, and services (including cloud-based services) to generate log records", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.PS-04.251", "title": "Ex2", "text": "Configure log generators to securely share their logs with the organization's logging infrastructure systems and services", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.PS-04.252", "title": "Ex3", "text": "Configure log generators to record the data needed by zero-trust architectures", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.PS-05.253", "title": "Ex1", "text": "When risk warrants it, restrict software execution to permitted products only or deny the execution of prohibited and unauthorized software", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.PS-05.254", "title": "Ex2", "text": "Verify the source of new software and the software's integrity before installing it", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.PS-05.255", "title": "Ex3", "text": "Configure platforms to use only approved DNS services that block access to known malicious domains", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.PS-05.256", "title": "Ex4", "text": "Configure platforms to allow the installation of organization-approved software only", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.PS-06.257", "title": "Ex1", "text": "Protect all components of organization-developed software from tampering and unauthorized access", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.PS-06.258", "title": "Ex2", "text": "Secure all software produced by the organization, with minimal vulnerabilities in their releases", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.PS-06.259", "title": "Ex3", "text": "Maintain the software used in production environments, and securely dispose of software once it is no longer needed", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.IR-01.260", "title": "Ex1", "text": "Logically segment organization networks and cloud-based platforms according to trust boundaries and platform types (e.g., IT, IoT, OT, mobile, guests), and permit required communications only between segments", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.IR-01.261", "title": "Ex2", "text": "Logically segment organization networks from external networks, and permit only necessary communications to enter the organization's networks from the external networks", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.IR-01.262", "title": "Ex3", "text": "Implement zero trust architectures to restrict network access to each resource to the minimum necessary", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.IR-01.263", "title": "Ex4", "text": "Check the cyber health of endpoints before allowing them to access and use production resources", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.IR-02.264", "title": "Ex1", "text": "Protect organizational equipment from known environmental threats, such as flooding, fire, wind, and excessive heat and humidity", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.IR-02.265", "title": "Ex2", "text": "Include protection from environmental threats and provisions for adequate operating infrastructure in requirements for service providers that operate systems on the organization's behalf", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.IR-03.266", "title": "Ex1", "text": "Avoid single points of failure in systems and infrastructure", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.IR-03.267", "title": "Ex2", "text": "Use load balancing to increase capacity and improve reliability", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.IR-03.268", "title": "Ex3", "text": "Use high-availability components like redundant storage and power supplies to improve system reliability", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.IR-04.269", "title": "Ex1", "text": "Monitor usage of storage, power, compute, network bandwidth, and other resources", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "PR.IR-04.270", "title": "Ex2", "text": "Forecast future needs, and scale resources accordingly", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.CM-01.271", "title": "Ex1", "text": "Monitor DNS, BGP, and other network services for adverse events", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.CM-01.272", "title": "Ex2", "text": "Monitor wired and wireless networks for connections from unauthorized endpoints", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.CM-01.273", "title": "Ex3", "text": "Monitor facilities for unauthorized or rogue wireless networks", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.CM-01.274", "title": "Ex4", "text": "Compare actual network flows against baselines to detect deviations", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.CM-01.275", "title": "Ex5", "text": "Monitor network communications to identify changes in security postures for zero trust purposes", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.CM-02.276", "title": "Ex1", "text": "Monitor logs from physical access control systems (e.g., badge readers) to find unusual access patterns (e.g., deviations from the norm) and failed access attempts", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.CM-02.277", "title": "Ex2", "text": "Review and monitor physical access records (e.g., from visitor registration, sign-in sheets)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.CM-02.278", "title": "Ex3", "text": "Monitor physical access controls (e.g., locks, latches, hinge pins, alarms) for signs of tampering", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.CM-02.279", "title": "Ex4", "text": "Monitor the physical environment using alarm systems, cameras, and security guards", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.CM-03.280", "title": "Ex1", "text": "Use behavior analytics software to detect anomalous user activity to mitigate insider threats", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.CM-03.281", "title": "Ex2", "text": "Monitor logs from logical access control systems to find unusual access patterns and failed access attempts", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.CM-03.282", "title": "Ex3", "text": "Continuously monitor deception technology, including user accounts, for any usage", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.CM-06.283", "title": "Ex1", "text": "Monitor remote and onsite administration and maintenance activities that external providers perform on organizational systems", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.CM-06.284", "title": "Ex2", "text": "Monitor activity from cloud-based services, internet service providers, and other service providers for deviations from expected behavior", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.CM-09.285", "title": "Ex1", "text": "Monitor email, web, file sharing, collaboration services, and other common attack vectors to detect malware, phishing, data leaks and exfiltration, and other adverse events", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.CM-09.286", "title": "Ex2", "text": "Monitor authentication attempts to identify attacks against credentials and unauthorized credential reuse", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.CM-09.287", "title": "Ex3", "text": "Monitor software configurations for deviations from security baselines", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.CM-09.288", "title": "Ex4", "text": "Monitor hardware and software for signs of tampering", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.CM-09.289", "title": "Ex5", "text": "Use technologies with a presence on endpoints to detect cyber health issues (e.g., missing patches, malware infections, unauthorized software), and redirect the endpoints to a remediation environment before access is authorized", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.AE-02.290", "title": "Ex1", "text": "Use security information and event management (SIEM) or other tools to continuously monitor log events for known malicious and suspicious activity", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.AE-02.291", "title": "Ex2", "text": "Utilize up-to-date cyber threat intelligence in log analysis tools to improve detection accuracy and characterize threat actors, their methods, and indicators of compromise", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.AE-02.292", "title": "Ex3", "text": "Regularly conduct manual reviews of log events for technologies that cannot be sufficiently monitored through automation", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.AE-02.293", "title": "Ex4", "text": "Use log analysis tools to generate reports on their findings", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.AE-03.294", "title": "Ex1", "text": "Constantly transfer log data generated by other sources to a relatively small number of log servers", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.AE-03.295", "title": "Ex2", "text": "Use event correlation technology (e.g., SIEM) to collect information captured by multiple sources", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.AE-03.296", "title": "Ex3", "text": "Utilize cyber threat intelligence to help correlate events among log sources", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.AE-04.297", "title": "Ex1", "text": "Use SIEMs or other tools to estimate impact and scope, and review and refine the estimates", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.AE-04.298", "title": "Ex2", "text": "A person creates their own estimates of impact and scope", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.AE-06.299", "title": "Ex1", "text": "Use cybersecurity software to generate alerts and provide them to the security operations center (SOC), incident responders, and incident response tools", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.AE-06.300", "title": "Ex2", "text": "Incident responders and other authorized personnel can access log analysis findings at all times", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.AE-06.301", "title": "Ex3", "text": "Automatically create and assign tickets in the organization's ticketing system when certain types of alerts occur", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.AE-06.302", "title": "Ex4", "text": "Manually create and assign tickets in the organization's ticketing system when technical staff discover indicators of compromise", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.AE-07.303", "title": "Ex1", "text": "Securely provide cyber threat intelligence feeds to detection technologies, processes, and personnel", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.AE-07.304", "title": "Ex2", "text": "Securely provide information from asset inventories to detection technologies, processes, and personnel", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.AE-07.305", "title": "Ex3", "text": "Rapidly acquire and analyze vulnerability disclosures for the organization's technologies from suppliers, vendors, and third-party security advisories", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.AE-08.306", "title": "Ex1", "text": "Apply incident criteria to known and assumed characteristics of activity in order to determine whether an incident should be declared", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "DE.AE-08.307", "title": "Ex2", "text": "Take known false positives into account when applying incident criteria", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.MA-01.308", "title": "Ex1", "text": "Detection technologies automatically report confirmed incidents", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.MA-01.309", "title": "Ex2", "text": "Request incident response assistance from the organization's incident response outsourcer", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.MA-01.310", "title": "Ex3", "text": "Designate an incident lead for each incident", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.MA-01.311", "title": "Ex4", "text": "Initiate execution of additional cybersecurity plans as needed to support incident response (for example, business continuity and disaster recovery)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.MA-02.312", "title": "Ex1", "text": "Preliminarily review incident reports to confirm that they are cybersecurity-related and necessitate incident response activities", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.MA-02.313", "title": "Ex2", "text": "Apply criteria to estimate the severity of an incident", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.MA-03.314", "title": "Ex1", "text": "Further review and categorize incidents based on the type of incident (e.g., data breach, ransomware, DDoS, account compromise)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.MA-03.315", "title": "Ex2", "text": "Prioritize incidents based on their scope, likely impact, and time-critical nature", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.MA-03.316", "title": "Ex3", "text": "Select incident response strategies for active incidents by balancing the need to quickly recover from an incident with the need to observe the attacker or conduct a more thorough investigation", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.MA-04.317", "title": "Ex1", "text": "Track and validate the status of all ongoing incidents", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.MA-04.318", "title": "Ex2", "text": "Coordinate incident escalation or elevation with designated internal and external stakeholders", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.MA-05.319", "title": "Ex1", "text": "Apply incident recovery criteria to known and assumed characteristics of the incident to determine whether incident recovery processes should be initiated", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.MA-05.320", "title": "Ex2", "text": "Take the possible operational disruption of incident recovery activities into account", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.AN-03.321", "title": "Ex1", "text": "Determine the sequence of events that occurred during the incident and which assets and resources were involved in each event", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.AN-03.322", "title": "Ex2", "text": "Attempt to determine what vulnerabilities, threats, and threat actors were directly or indirectly involved in the incident", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.AN-03.323", "title": "Ex3", "text": "Analyze the incident to find the underlying, systemic root causes", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.AN-03.324", "title": "Ex4", "text": "Check any cyber deception technology for additional information on attacker behavior", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.AN-06.325", "title": "Ex1", "text": "Require each incident responder and others (e.g., system administrators, cybersecurity engineers) who perform incident response tasks to record their actions and make the record immutable", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.AN-06.326", "title": "Ex2", "text": "Require the incident lead to document the incident in detail and be responsible for preserving the integrity of the documentation and the sources of all information being reported", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.AN-07.327", "title": "Ex1", "text": "Collect, preserve, and safeguard the integrity of all pertinent incident data and metadata (e.g., data source, date/time of collection) based on evidence preservation and chain-of-custody procedures", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.AN-08.328", "title": "Ex1", "text": "Review other potential targets of the incident to search for indicators of compromise and evidence of persistence", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.AN-08.329", "title": "Ex2", "text": "Automatically run tools on targets to look for indicators of compromise and evidence of persistence", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.CO-02.330", "title": "Ex1", "text": "Follow the organization's breach notification procedures after discovering a data breach incident, including notifying affected customers", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.CO-02.331", "title": "Ex2", "text": "Notify business partners and customers of incidents in accordance with contractual requirements", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.CO-02.332", "title": "Ex3", "text": "Notify law enforcement agencies and regulatory bodies of incidents based on criteria in the incident response plan and management approval", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.CO-03.333", "title": "Ex1", "text": "Securely share information consistent with response plans and information sharing agreements", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.CO-03.334", "title": "Ex2", "text": "Voluntarily share information about an attacker's observed TTPs, with all sensitive data removed, with an Information Sharing and Analysis Center (ISAC)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.CO-03.335", "title": "Ex3", "text": "Notify HR when malicious insider activity occurs", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.CO-03.336", "title": "Ex4", "text": "Regularly update senior leadership on the status of major incidents", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.CO-03.337", "title": "Ex5", "text": "Follow the rules and protocols defined in contracts for incident information sharing between the organization and its suppliers", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.CO-03.338", "title": "Ex6", "text": "Coordinate crisis communication methods between the organization and its critical suppliers", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.MI-01.339", "title": "Ex1", "text": "Cybersecurity technologies (e.g., antivirus software) and cybersecurity features of other technologies (e.g., operating systems, network infrastructure devices) automatically perform containment actions", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.MI-01.340", "title": "Ex2", "text": "Allow incident responders to manually select and perform containment actions", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.MI-01.341", "title": "Ex3", "text": "Allow a third party (e.g., internet service provider, managed security service provider) to perform containment actions on behalf of the organization", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.MI-01.342", "title": "Ex4", "text": "Automatically transfer compromised endpoints to a remediation virtual local area network (VLAN)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.MI-02.343", "title": "Ex1", "text": "Cybersecurity technologies and cybersecurity features of other technologies (e.g., operating systems, network infrastructure devices) automatically perform eradication actions", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.MI-02.344", "title": "Ex2", "text": "Allow incident responders to manually select and perform eradication actions", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RS.MI-02.345", "title": "Ex3", "text": "Allow a third party (e.g., managed security service provider) to perform eradication actions on behalf of the organization", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RC.RP-01.346", "title": "Ex1", "text": "Begin recovery procedures during or after incident response processes", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RC.RP-01.347", "title": "Ex2", "text": "Make all individuals with recovery responsibilities aware of the plans for recovery and the authorizations required to implement each aspect of the plans", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RC.RP-02.348", "title": "Ex1", "text": "Select recovery actions based on the criteria defined in the incident response plan and available resources", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RC.RP-02.349", "title": "Ex2", "text": "Change planned recovery actions based on a reassessment of organizational needs and resources", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RC.RP-03.350", "title": "Ex1", "text": "Check restoration assets for indicators of compromise, file corruption, and other integrity issues before use", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RC.RP-04.351", "title": "Ex1", "text": "Use business impact and system categorization records (including service delivery objectives) to validate that essential services are restored in the appropriate order", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RC.RP-04.352", "title": "Ex2", "text": "Work with system owners to confirm the successful restoration of systems and the return to normal operations", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RC.RP-04.353", "title": "Ex3", "text": "Monitor the performance of restored systems to verify the adequacy of the restoration", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RC.RP-05.354", "title": "Ex1", "text": "Check restored assets for indicators of compromise and remediation of root causes of the incident before production use", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RC.RP-05.355", "title": "Ex2", "text": "Verify the correctness and adequacy of the restoration actions taken before putting a restored system online", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RC.RP-06.356", "title": "Ex1", "text": "Prepare an after-action report that documents the incident itself, the response and recovery actions taken, and lessons learned", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RC.RP-06.357", "title": "Ex2", "text": "Declare the end of incident recovery once the criteria are met", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RC.CO-03.358", "title": "Ex1", "text": "Securely share recovery information, including restoration progress, consistent with response plans and information sharing agreements", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RC.CO-03.359", "title": "Ex2", "text": "Regularly update senior leadership on recovery status and restoration progress for major incidents", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RC.CO-03.360", "title": "Ex3", "text": "Follow the rules and protocols defined in contracts for incident information sharing between the organization and its suppliers", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RC.CO-03.361", "title": "Ex4", "text": "Coordinate crisis communication between the organization and its critical suppliers", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RC.CO-04.362", "title": "Ex1", "text": "Follow the organization's breach notification procedures for recovering from a data breach incident", "doc_identifier": "CSF_2_0_0"}
{"element_type": "implementation_example", "element_identifier": "RC.CO-04.363", "title": "Ex2", "text": "Explain the steps being taken to recover from the incident and to prevent a recurrence", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "GV.OC-01", "title": "", "text": "The organizational mission is understood and informs cybersecurity risk management", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "GV.OC-02", "title": "", "text": "Internal and external stakeholders are understood, and their needs and expectations regarding cybersecurity risk management are understood and considered", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "GV.OC-03", "title": "", "text": "Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "GV.OC-04", "title": "", "text": "Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organization are understood and communicated", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "GV.OC-05", "title": "", "text": "Outcomes, capabilities, and services that the organization depends on are understood and communicated", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "GV.RM-01", "title": "", "text": "Risk management objectives are established and agreed to by organizational stakeholders", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "GV.RM-02", "title": "", "text": "Risk appetite and risk tolerance statements are established, communicated, and maintained", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "GV.RM-03", "title": "", "text": "Cybersecurity risk management activities and outcomes are included in enterprise risk management processes", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "GV.RM-04", "title": "", "text": "Strategic direction that describes appropriate risk response options is established and communicated", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "GV.RM-05", "title": "", "text": "Lines of communication across the organization are established for cybersecurity risks, including risks from suppliers and other third parties", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "GV.RM-06", "title": "", "text": "A standardized method for calculating, documenting, categorizing, and prioritizing cybersecurity risks is established and communicated", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "GV.RM-07", "title": "", "text": "Strategic opportunities (i.e., positive risks) are characterized and are included in organizational cybersecurity risk discussions", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "GV.RR-01", "title": "", "text": "Organizational leadership is responsible and accountable for cybersecurity risk and fosters a culture that is risk-aware, ethical, and continually improving", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "GV.RR-02", "title": "", "text": "Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "GV.RR-03", "title": "", "text": "Adequate resources are allocated commensurate with the cybersecurity risk strategy, roles, responsibilities, and policies", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "GV.RR-04", "title": "", "text": "Cybersecurity is included in human resources practices", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "GV.PO-01", "title": "", "text": "Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "GV.PO-02", "title": "", "text": "Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "GV.OV-01", "title": "", "text": "Cybersecurity risk management strategy outcomes are reviewed to inform and adjust strategy and direction", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "GV.OV-02", "title": "", "text": "The cybersecurity risk management strategy is reviewed and adjusted to ensure coverage of organizational requirements and risks", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "GV.OV-03", "title": "", "text": "Organizational cybersecurity risk management performance is evaluated and reviewed for adjustments needed", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "GV.SC-01", "title": "", "text": "A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organizational stakeholders", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "GV.SC-02", "title": "", "text": "Cybersecurity roles and responsibilities for suppliers, customers, and partners are established, communicated, and coordinated internally and externally", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "GV.SC-03", "title": "", "text": "Cybersecurity supply chain risk management is integrated into cybersecurity and enterprise risk management, risk assessment, and improvement processes", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "GV.SC-04", "title": "", "text": "Suppliers are known and prioritized by criticality", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "GV.SC-05", "title": "", "text": "Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third parties", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "GV.SC-06", "title": "", "text": "Planning and due diligence are performed to reduce risks before entering into formal supplier or other third-party relationships", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "GV.SC-07", "title": "", "text": "The risks posed by a supplier, their products and services, and other third parties are understood, recorded, prioritized, assessed, responded to, and monitored over the course of the relationship", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "GV.SC-08", "title": "", "text": "Relevant suppliers and other third parties are included in incident planning, response, and recovery activities", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "GV.SC-09", "title": "", "text": "Supply chain security practices are integrated into cybersecurity and enterprise risk management programs, and their performance is monitored throughout the technology product and service life cycle", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "GV.SC-10", "title": "", "text": "Cybersecurity supply chain risk management plans include provisions for activities that occur after the conclusion of a partnership or service agreement", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.AM-01", "title": "", "text": "Inventories of hardware managed by the organization are maintained", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.AM-02", "title": "", "text": "Inventories of software, services, and systems managed by the organization are maintained", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.AM-03", "title": "", "text": "Representations of the organization's authorized network communication and internal and external network data flows are maintained", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.AM-04", "title": "", "text": "Inventories of services provided by suppliers are maintained", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.AM-05", "title": "", "text": "Assets are prioritized based on classification, criticality, resources, and impact on the mission", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.AM-07", "title": "", "text": "Inventories of data and corresponding metadata for designated data types are maintained", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.AM-08", "title": "", "text": "Systems, hardware, software, services, and data are managed throughout their life cycles", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.RA-01", "title": "", "text": "Vulnerabilities in assets are identified, validated, and recorded", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.RA-02", "title": "", "text": "Cyber threat intelligence is received from information sharing forums and sources", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.RA-03", "title": "", "text": "Internal and external threats to the organization are identified and recorded", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.RA-04", "title": "", "text": "Potential impacts and likelihoods of threats exploiting vulnerabilities are identified and recorded", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.RA-05", "title": "", "text": "Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritization", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.RA-06", "title": "", "text": "Risk responses are chosen, prioritized, planned, tracked, and communicated", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.RA-07", "title": "", "text": "Changes and exceptions are managed, assessed for risk impact, recorded, and tracked", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.RA-08", "title": "", "text": "Processes for receiving, analyzing, and responding to vulnerability disclosures are established", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.RA-09", "title": "", "text": "The authenticity and integrity of hardware and software are assessed prior to acquisition and use", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.RA-10", "title": "", "text": "Critical suppliers are assessed prior to acquisition", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.IM-01", "title": "", "text": "Improvements are identified from evaluations", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.IM-02", "title": "", "text": "Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.IM-03", "title": "", "text": "Improvements are identified from execution of operational processes, procedures, and activities", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.IM-04", "title": "", "text": "Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.AA-01", "title": "", "text": "Identities and credentials for authorized users, services, and hardware are managed by the organization", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.AA-02", "title": "", "text": "Identities are proofed and bound to credentials based on the context of interactions", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.AA-03", "title": "", "text": "Users, services, and hardware are authenticated", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.AA-04", "title": "", "text": "Identity assertions are protected, conveyed, and verified", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.AA-05", "title": "", "text": "Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.AA-06", "title": "", "text": "Physical access to assets is managed, monitored, and enforced commensurate with risk", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.AT-01", "title": "", "text": "Personnel are provided with awareness and training so that they possess the knowledge and skills to perform general tasks with cybersecurity risks in mind", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.AT-02", "title": "", "text": "Individuals in specialized roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.DS-01", "title": "", "text": "The confidentiality, integrity, and availability of data-at-rest are protected", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.DS-02", "title": "", "text": "The confidentiality, integrity, and availability of data-in-transit are protected", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.DS-10", "title": "", "text": "The confidentiality, integrity, and availability of data-in-use are protected", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.DS-11", "title": "", "text": "Backups of data are created, protected, maintained, and tested", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.PS-01", "title": "", "text": "Configuration management practices are established and applied", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.PS-02", "title": "", "text": "Software is maintained, replaced, and removed commensurate with risk", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.PS-03", "title": "", "text": "Hardware is maintained, replaced, and removed commensurate with risk", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.PS-04", "title": "", "text": "Log records are generated and made available for continuous monitoring", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.PS-05", "title": "", "text": "Installation and execution of unauthorized software are prevented", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.PS-06", "title": "", "text": "Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.IR-01", "title": "", "text": "Networks and environments are protected from unauthorized logical access and usage", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.IR-02", "title": "", "text": "The organization's technology assets are protected from environmental threats", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.IR-03", "title": "", "text": "Mechanisms are implemented to achieve resilience requirements in normal and adverse situations", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.IR-04", "title": "", "text": "Adequate resource capacity to ensure availability is maintained", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "DE.CM-01", "title": "", "text": "Networks and network services are monitored to find potentially adverse events", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "DE.CM-02", "title": "", "text": "The physical environment is monitored to find potentially adverse events", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "DE.CM-03", "title": "", "text": "Personnel activity and technology usage are monitored to find potentially adverse events", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "DE.CM-06", "title": "", "text": "External service provider activities and services are monitored to find potentially adverse events", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "DE.CM-09", "title": "", "text": "Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "DE.AE-02", "title": "", "text": "Potentially adverse events are analyzed to better understand associated activities", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "DE.AE-03", "title": "", "text": "Information is correlated from multiple sources", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "DE.AE-04", "title": "", "text": "The estimated impact and scope of adverse events are understood", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "DE.AE-06", "title": "", "text": "Information on adverse events is provided to authorized staff and tools", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "DE.AE-07", "title": "", "text": "Cyber threat intelligence and other contextual information are integrated into the analysis", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "DE.AE-08", "title": "", "text": "Incidents are declared when adverse events meet the defined incident criteria", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RS.MA-01", "title": "", "text": "The incident response plan is executed in coordination with relevant third parties once an incident is declared", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RS.MA-02", "title": "", "text": "Incident reports are triaged and validated", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RS.MA-03", "title": "", "text": "Incidents are categorized and prioritized", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RS.MA-04", "title": "", "text": "Incidents are escalated or elevated as needed", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RS.MA-05", "title": "", "text": "The criteria for initiating incident recovery are applied", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RS.AN-03", "title": "", "text": "Analysis is performed to establish what has taken place during an incident and the root cause of the incident", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RS.AN-06", "title": "", "text": "Actions performed during an investigation are recorded, and the records' integrity and provenance are preserved", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RS.AN-07", "title": "", "text": "Incident data and metadata are collected, and their integrity and provenance are preserved", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RS.AN-08", "title": "", "text": "An incident's magnitude is estimated and validated", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RS.CO-02", "title": "", "text": "Internal and external stakeholders are notified of incidents", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RS.CO-03", "title": "", "text": "Information is shared with designated internal and external stakeholders", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RS.MI-01", "title": "", "text": "Incidents are contained", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RS.MI-02", "title": "", "text": "Incidents are eradicated", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RC.RP-01", "title": "", "text": "The recovery portion of the incident response plan is executed once initiated from the incident response process", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RC.RP-02", "title": "", "text": "Recovery actions are selected, scoped, prioritized, and performed", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RC.RP-03", "title": "", "text": "The integrity of backups and other restoration assets is verified before using them for restoration", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RC.RP-04", "title": "", "text": "Critical mission functions and cybersecurity risk management are considered to establish post-incident operational norms", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RC.RP-05", "title": "", "text": "The integrity of restored assets is verified, systems and services are restored, and normal operating status is confirmed", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RC.RP-06", "title": "", "text": "The end of incident recovery is declared based on criteria, and incident-related documentation is completed", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RC.CO-03", "title": "", "text": "Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RC.CO-04", "title": "", "text": "Public updates on incident recovery are shared using approved methods and messaging", "doc_identifier": "CSF_2_0_0"}
{"element_type": "party", "element_identifier": "third", "title": "3rd", "text": "3rd Party Risk", "doc_identifier": "CSF_2_0_0"}
{"element_type": "party", "element_identifier": "first", "title": "1st", "text": "1st Party Risk", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.AM-06", "title": "", "text": "Cybersecurity roles and responsibilities for the entire workforce and third-party stakeholders (e.g., suppliers, customers, partners) are established", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-ID.AM-06", "title": "", "text": "Incorporated into GV.RR-02, GV.SC-02", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-ID.BE", "title": "", "text": "Incorporated into GV.OC", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.BE-01", "title": "", "text": "The organization’s role in the supply chain is identified and communicated", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-ID.BE-01", "title": "", "text": "Incorporated into GV.OC-05", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.BE-02", "title": "", "text": "The organization’s place in critical infrastructure and its industry sector is identified and communicated", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-ID.BE-02", "title": "", "text": "Incorporated into GV.OC-01", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.BE-03", "title": "", "text": "Priorities for organizational mission, objectives, and activities are established and communicated", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-ID.BE-03", "title": "", "text": "Incorporated into GV.OC-01", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.BE-04", "title": "", "text": "Dependencies and critical functions for delivery of critical services are established", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-ID.BE-04", "title": "", "text": "Incorporated into GV.OC-04, GV.OC-05", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.BE-05", "title": "", "text": "Resilience requirements to support delivery of critical services are established for all operating states (e.g. under duress/attack, during recovery, normal operations)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-ID.BE-05", "title": "", "text": "Incorporated into GV.OC-04", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-ID.GV", "title": "", "text": "Incorporated into GV", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.GV-01", "title": "", "text": "Organizational cybersecurity policy is established and communicated", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-ID.GV-01", "title": "", "text": "Incorporated into GV.PO, GV.PO-01, GV.PO-02", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.GV-02", "title": "", "text": "Cybersecurity roles and responsibilities are coordinated and aligned with internal roles and external partners", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-ID.GV-02", "title": "", "text": "Incorporated into GV.OC-02, GV.RR, GV.RR-02", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.GV-03", "title": "", "text": "Legal and regulatory requirements regarding cybersecurity, including privacy and civil liberties obligations, are understood and managed", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-ID.GV-03", "title": "", "text": "Moved to GV.OC-03", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.GV-04", "title": "", "text": "Governance and risk management processes address cybersecurity risks", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-ID.GV-04", "title": "", "text": "Moved to GV.RM-04", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-ID.RM", "title": "", "text": "Incorporated into GV.RM", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.RM-01", "title": "", "text": "Risk management processes are established, managed, and agreed to by organizational stakeholders", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-ID.RM-01", "title": "", "text": "Incorporated into GV.RM-01, GV.RM-06, GV.RR-03", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.RM-02", "title": "", "text": "Organizational risk tolerance is determined and clearly expressed", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-ID.RM-02", "title": "", "text": "Incorporated into GV.RM-02, GV.RM-04", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.RM-03", "title": "", "text": "The organization’s determination of risk tolerance is informed by its role in critical infrastructure and sector specific risk analysis", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-ID.RM-03", "title": "", "text": "Moved into GV.RM-02", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-ID.SC", "title": "", "text": "Incorporated into GV.SC", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.SC-01", "title": "", "text": "Cyber supply chain risk management processes are identified, established, assessed, managed, and agreed to by organizational stakeholders", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-ID.SC-01", "title": "", "text": "Incorporated into GV.RM-05, GV.SC-01, GV.SC-06, GV.SC-09, GV.SC-10", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.SC-02", "title": "", "text": "Suppliers and third party partners of information systems, components, and services are identified, prioritized, and assessed using a cyber supply chain risk assessment process", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-ID.SC-02", "title": "", "text": "Incorporated into GV.OC-02, GV.SC-03, GV.SC-04, GV.SC-07, ID.RA-10", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.SC-03", "title": "", "text": "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.", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-ID.SC-03", "title": "", "text": "Moved to GV.SC-05", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.SC-04", "title": "", "text": "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.", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-ID.SC-04", "title": "", "text": "Incorporated into GV.SC-07, ID.RA-10", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "ID.SC-05", "title": "", "text": "Response and recovery planning and testing are conducted with suppliers and third-party providers", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-ID.SC-05", "title": "", "text": "Incorporated into GV.SC-08, ID.IM-02", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.AC", "title": "", "text": "Moved to PR.AA", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.AC-01", "title": "", "text": "Identities and credentials are issued, managed, verified, revoked, and audited for authorized devices, users and processes", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.AC-01", "title": "", "text": "Incorporated into PR.AA-01, PR.AA-05", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.AC-02", "title": "", "text": "Physical access to assets is managed and protected", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.AC-02", "title": "", "text": "Moved to PR.AA-06", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.AC-03", "title": "", "text": "Remote access is managed", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.AC-03", "title": "", "text": "Incorporated into PR.AA-03, PR.AA-05, PR.IR-01", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.AC-04", "title": "", "text": "Access permissions and authorizations are managed, incorporating the principles of least privilege and separation of duties", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.AC-04", "title": "", "text": "Moved to PR.AA-05", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.AC-05", "title": "", "text": "Network integrity is protected (e.g., network segregation, network segmentation)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.AC-05", "title": "", "text": "Incorporated into PR.IR-01", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.AC-06", "title": "", "text": "Identities are proofed and bound to credentials and asserted in interactions", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.AC-06", "title": "", "text": "Moved to PR.AA-02", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.AC-07", "title": "", "text": "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)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.AC-07", "title": "", "text": "Moved to PR.AA-03", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.AT-03", "title": "", "text": "Third-party stakeholders (e.g., suppliers, customers, partners) understand their roles and responsibilities", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.AT-03", "title": "", "text": "Incorporated into PR.AT-01, PR.AT-02", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.AT-04", "title": "", "text": "Senior executives understand their roles and responsibilities", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.AT-04", "title": "", "text": "Incorporated into PR.AT-02", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.AT-05", "title": "", "text": "Physical and cybersecurity personnel understand their roles and responsibilities", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.AT-05", "title": "", "text": "Incorporated into PR.AT-02", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.DS-03", "title": "", "text": "Assets are formally managed throughout removal, transfers, and disposition", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.DS-03", "title": "", "text": "Incorporated into ID.AM-08, PR.PS-03", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.DS-04", "title": "", "text": "Adequate capacity to ensure availability is maintained", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.DS-04", "title": "", "text": "Moved to PR.IR-04", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.DS-05", "title": "", "text": "Protections against data leaks are implemented", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.DS-05", "title": "", "text": "Incorporated into PR.DS-01, PR.DS-02, PR.DS-10", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.DS-06", "title": "", "text": "Integrity checking mechanisms are used to verify software, firmware, and information integrity", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.DS-06", "title": "", "text": "Incorporated into PR.DS-01, DE.CM-09", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.DS-07", "title": "", "text": "The development and testing environment(s) are separate from the production environment", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.DS-07", "title": "", "text": "Incorporated into PR.IR-01", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.DS-08", "title": "", "text": "Integrity checking mechanisms are used to verify hardware integrity", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.DS-08", "title": "", "text": "Incorporated into ID.RA-09, DE.CM-09", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.IP", "title": "", "text": "Incorporated into other Categories and Functions", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.IP-01", "title": "", "text": "A baseline configuration of information technology/industrial control systems is created and maintained incorporating security principles (e.g. concept of least functionality)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.IP-01", "title": "", "text": "Incorporated into PR.PS-01", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.IP-02", "title": "", "text": "A System Development Life Cycle to manage systems is implemented", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.IP-02", "title": "", "text": "Incorporated into ID.AM-08, PR.PS-06", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.IP-03", "title": "", "text": "Configuration change control processes are in place", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.IP-03", "title": "", "text": "Incorporated into PR.PS-01, ID.RA-07", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.IP-04", "title": "", "text": "Backups of information are conducted, maintained, and tested", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.IP-04", "title": "", "text": "Moved to PR.DS-11", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.IP-05", "title": "", "text": "Policy and regulations regarding the physical operating environment for organizational assets are met", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.IP-05", "title": "", "text": "Moved to PR.IR-02", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.IP-06", "title": "", "text": "Data is destroyed according to policy", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.IP-06", "title": "", "text": "Incorporated into ID.AM-08", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.IP-07", "title": "", "text": "Protection processes are improved", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.IP-07", "title": "", "text": "Incorporated into ID.IM, ID.IM-03", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.IP-08", "title": "", "text": "Effectiveness of protection technologies is shared", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.IP-08", "title": "", "text": "Moved to ID.IM-03", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.IP-09", "title": "", "text": "Response plans (Incident Response and Business Continuity) and recovery plans (Incident Recovery and Disaster Recovery) are in place and managed", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.IP-09", "title": "", "text": "Moved to ID.IM-04", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.IP-10", "title": "", "text": "Response and recovery plans are tested", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.IP-10", "title": "", "text": "Incorporated into ID.IM-02, ID.IM-04", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.IP-11", "title": "", "text": "Cybersecurity is included in human resources practices (e.g., deprovisioning, personnel screening)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.IP-11", "title": "", "text": "Moved to GV.RR-04", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.IP-12", "title": "", "text": "A vulnerability management plan is developed and implemented", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.IP-12", "title": "", "text": "Incorporated into ID.RA-01, PR.PS-02", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.MA", "title": "", "text": "Incorporated into ID.AM-08", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.MA-01", "title": "", "text": "Maintenance and repair of organizational assets are performed and logged, with approved and controlled tools", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.MA-01", "title": "", "text": "Incorporated into ID.AM-08, PR.PS-03", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.MA-02", "title": "", "text": "Remote maintenance of organizational assets is approved, logged, and performed in a manner that prevents unauthorized access", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.MA-02", "title": "", "text": "Incorporated into ID.AM-08, PR.PS-02", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.PT", "title": "", "text": "Incorporated into other Protect Categories", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.PT-01", "title": "", "text": "Audit/log records are determined, documented, implemented, and reviewed in accordance with policy", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.PT-01", "title": "", "text": "Incorporated into PR.PS-04", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.PT-02", "title": "", "text": "Removable media is protected and its use restricted according to policy", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.PT-02", "title": "", "text": "Incorporated into PR.DS-01, PR.PS-01", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.PT-03", "title": "", "text": "The principle of least functionality is incorporated by configuring systems to provide only essential capabilities", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.PT-03", "title": "", "text": "Incorporated into PR.PS-01", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.PT-04", "title": "", "text": "Communications and control networks are protected", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.PT-04", "title": "", "text": "Incorporated into PR.AA-06, PR.IR-01", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "PR.PT-05", "title": "", "text": "Mechanisms (e.g., failsafe, load balancing, hot swap) are implemented to achieve resilience requirements in normal and adverse situations", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-PR.PT-05", "title": "", "text": "Moved to PR.IR-03", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "DE.CM-04", "title": "", "text": "Malicious code is detected", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-DE.CM-04", "title": "", "text": "Incorporated into DE.CM-01, DE.CM-09", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "DE.CM-05", "title": "", "text": "Unauthorized mobile code is detected", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-DE.CM-05", "title": "", "text": "Incorporated into DE.CM-01, DE.CM-09", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "DE.CM-07", "title": "", "text": "Monitoring for unauthorized personnel, connections, devices, and software is performed", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-DE.CM-07", "title": "", "text": "Incorporated into DE.CM-01, DE.CM-03, DE.CM-06, DE.CM-09", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "DE.CM-08", "title": "", "text": "Vulnerability scans are performed", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-DE.CM-08", "title": "", "text": "Incorporated into ID.RA-01", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "DE.AE-01", "title": "", "text": "A baseline of network operations and expected data flows for users and systems is established and managed", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-DE.AE-01", "title": "", "text": "Incorporated into ID.AM-03", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "DE.AE-05", "title": "", "text": "Incident alert thresholds are established", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-DE.AE-05", "title": "", "text": "Moved to DE.AE-08", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-DE.DP", "title": "", "text": "Incorporated into other Categories and Functions", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "DE.DP-01", "title": "", "text": "Roles and responsibilities for detection are well defined to ensure accountability", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-DE.DP-01", "title": "", "text": "Incorporated into GV.RR-02", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "DE.DP-02", "title": "", "text": "Detection activities comply with all applicable requirements", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-DE.DP-02", "title": "", "text": "Incorporated into DE.AE", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "DE.DP-03", "title": "", "text": "Detection processes are tested", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-DE.DP-03", "title": "", "text": "Incorporated into ID.IM-02", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "DE.DP-04", "title": "", "text": "Event detection information is communicated", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-DE.DP-04", "title": "", "text": "Incorporated into DE.AE-06", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "DE.DP-05", "title": "", "text": "Detection processes are continuously improved", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-DE.DP-05", "title": "", "text": "Incorporated into ID.IM, ID.IM-03", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-RS.RP", "title": "", "text": "Incorporated into RS.MA", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RS.RP-01", "title": "", "text": "Response plan is executed during or after an incident", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-RS.RP-01", "title": "", "text": "Incorporated into RS.MA-01", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RS.AN-01", "title": "", "text": "Notifications from detection systems are investigated", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-RS.AN-01", "title": "", "text": "Incorporated into RS.MA-02", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RS.AN-02", "title": "", "text": "The impact of the incident is understood", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-RS.AN-02", "title": "", "text": "Incorporated into RS.MA-02, RS.MA-03, RS.MA-04", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RS.AN-04", "title": "", "text": "Incidents are categorized consistent with response plans", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-RS.AN-04", "title": "", "text": "Moved to RS.MA-03", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RS.AN-05", "title": "", "text": "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)", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-RS.AN-05", "title": "", "text": "Moved to ID.RA-08", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RS.CO-01", "title": "", "text": "Personnel know their roles and order of operations when a response is needed", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-RS.CO-01", "title": "", "text": "Incorporated into PR.AT-01", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RS.CO-04", "title": "", "text": "Coordination with stakeholders occurs consistent with response plans", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-RS.CO-04", "title": "", "text": "Incorporated into RS.MA-01, RS.MA-04", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RS.CO-05", "title": "", "text": "Voluntary information sharing occurs with external stakeholders to achieve broader cybersecurity situational awareness", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-RS.CO-05", "title": "", "text": "Incorporated into RS.CO-03", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RS.MI-03", "title": "", "text": "Newly identified vulnerabilities are mitigated or documented as accepted risks", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-RS.MI-03", "title": "", "text": "Incorporated into ID.RA-06", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-RS.IM", "title": "", "text": "Incorporated into ID.IM", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RS.IM-01", "title": "", "text": "Response plans incorporate lessons learned", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-RS.IM-01", "title": "", "text": "Incorporated into ID.IM-03, ID.IM-04", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RS.IM-02", "title": "", "text": "Response strategies are updated", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-RS.IM-02", "title": "", "text": "Incorporated into ID.IM-03", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RC.CO-01", "title": "", "text": "Public relations are managed", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-RC.CO-01", "title": "", "text": "Incorporated into RC.CO-04", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RC.CO-02", "title": "", "text": "Reputation is repaired after an incident", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-RC.CO-02", "title": "", "text": "Incorporated into RC.CO-04", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-RC.IM", "title": "", "text": "Incorporated into ID.IM", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RC.IM-01", "title": "", "text": "Recovery plans incorporate lessons learned", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-RC.IM-01", "title": "", "text": "Incorporated into ID.IM-03, ID.IM-04", "doc_identifier": "CSF_2_0_0"}
{"element_type": "subcategory", "element_identifier": "RC.IM-02", "title": "", "text": "Recovery strategies are updated", "doc_identifier": "CSF_2_0_0"}
{"element_type": "withdraw_reason", "element_identifier": "WR-RC.IM-02", "title": "", "text": "Incorporated into ID.IM-03", "doc_identifier": "CSF_2_0_0"}