instruction stringlengths 44 167 | input stringclasses 1
value | output stringlengths 39 11.2k | source stringclasses 6
values | id stringlengths 5 19 |
|---|---|---|---|---|
Explain the NIST AI RMF Playbook requirement: MAP 1.3 | The organization’s mission and relevant goals for the AI technology are understood and documented. About: Defining and documenting the specific business purpose of an AI system in a broader context of societal values helps teams to evaluate risks and increases the clarity of “go/no-go” decisions about whether to deploy... | NIST AI RMF Playbook | AI-RMF-MAP-1.3 | |
What are the requirements for MAP 1.4 according to NIST AI RMF Playbook? | The business value or context of business use has been clearly defined or – in the case of assessing existing AI systems – re-evaluated. About: Socio-technical AI risks emerge from the interplay between technical development decisions and how a system is used, who operates it, and the social context into which it is de... | NIST AI RMF Playbook | AI-RMF-MAP-1.4 | |
What is AI-RMF-MAP-1.5 in the NIST AI RMF Playbook framework? | Organizational risk tolerances are determined and documented. About: Risk tolerance reflects the level and type of risk the organization is willing to accept while conducting its mission and carrying out its strategy. Organizations can follow existing regulations and guidelines for risk criteria, tolerance and response... | NIST AI RMF Playbook | AI-RMF-MAP-1.5 | |
What is AI-RMF-MAP-1.6 in the NIST AI RMF Playbook framework? | System requirements (e.g., “the system shall respect the privacy of its users”) are elicited from and understood by relevant AI actors. Design decisions take socio-technical implications into account to address AI risks. About: AI system development requirements may outpace documentation processes for traditional softw... | NIST AI RMF Playbook | AI-RMF-MAP-1.6 | |
Explain the NIST AI RMF Playbook requirement: MAP 2.1 | The specific task, and methods used to implement the task, that the AI system will support is defined (e.g., classifiers, generative models, recommenders). About: AI actors define the technical learning or decision-making task(s) an AI system is designed to accomplish, or the benefits that the system will provide. The ... | NIST AI RMF Playbook | AI-RMF-MAP-2.1 | |
What is AI-RMF-MAP-2.2 in the NIST AI RMF Playbook framework? | Information about the AI system’s knowledge limits and how system output may be utilized and overseen by humans is documented. Documentation provides sufficient information to assist relevant AI actors when making informed decisions and taking subsequent actions. About: An AI lifecycle consists of many interdependent a... | NIST AI RMF Playbook | AI-RMF-MAP-2.2 | |
What are the requirements for MAP 2.3 according to NIST AI RMF Playbook? | Scientific integrity and TEVV considerations are identified and documented, including those related to experimental design, data collection and selection (e.g., availability, representativeness, suitability), system trustworthiness, and construct validation. About: Standard testing and evaluation protocols provide a ba... | NIST AI RMF Playbook | AI-RMF-MAP-2.3 | |
What is AI-RMF-MAP-3.1 in the NIST AI RMF Playbook framework? | Potential benefits of intended AI system functionality and performance are examined and documented. About: AI systems have enormous potential to improve quality of life, enhance economic prosperity and security costs. Organizations are encouraged to define and document system purpose and utility, and its potential posi... | NIST AI RMF Playbook | AI-RMF-MAP-3.1 | |
Explain the NIST AI RMF Playbook requirement: MAP 3.2 | Potential costs, including non-monetary costs, which result from expected or realized AI errors or system functionality and trustworthiness - as connected to organizational risk tolerance - are examined and documented. About: Anticipating negative impacts of AI systems is a difficult task. Negative impacts can be due t... | NIST AI RMF Playbook | AI-RMF-MAP-3.2 | |
What are the requirements for MAP 3.3 according to NIST AI RMF Playbook? | Targeted application scope is specified and documented based on the system’s capability, established context, and AI system categorization. About: Systems that function in a narrow scope tend to enable better mapping, measurement, and management of risks in the learning or decision-making tasks and the system context. ... | NIST AI RMF Playbook | AI-RMF-MAP-3.3 | |
Describe the security control 'MAP 3.4' from NIST AI RMF Playbook. | Processes for operator and practitioner proficiency with AI system performance and trustworthiness – and relevant technical standards and certifications – are defined, assessed and documented. About: Human-AI configurations can span from fully autonomous to fully manual. AI systems can autonomously make decisions, defe... | NIST AI RMF Playbook | AI-RMF-MAP-3.4 | |
Describe the security control 'MAP 3.5' from NIST AI RMF Playbook. | Processes for human oversight are defined, assessed, and documented in accordance with organizational policies from GOVERN function. About: As AI systems have evolved in accuracy and precision, computational systems have moved from being used purely for decision support—or for explicit use by and under the control of a... | NIST AI RMF Playbook | AI-RMF-MAP-3.5 | |
What is AI-RMF-MAP-4.1 in the NIST AI RMF Playbook framework? | Approaches for mapping AI technology and legal risks of its components – including the use of third-party data or software – are in place, followed, and documented, as are risks of infringement of a third-party’s intellectual property or other rights. About: Technologies and personnel from third-parties are another pot... | NIST AI RMF Playbook | AI-RMF-MAP-4.1 | |
What are the requirements for MAP 4.2 according to NIST AI RMF Playbook? | Internal risk controls for components of the AI system including third-party AI technologies are identified and documented. About: In the course of their work, AI actors often utilize open-source, or otherwise freely available, third-party technologies – some of which may have privacy, bias, and security risks. Organiz... | NIST AI RMF Playbook | AI-RMF-MAP-4.2 | |
What are the requirements for MAP 5.1 according to NIST AI RMF Playbook? | Likelihood and magnitude of each identified impact (both potentially beneficial and harmful) based on expected use, past uses of AI systems in similar contexts, public incident reports, feedback from those external to the team that developed or deployed the AI system, or other data are identified and documented. About:... | NIST AI RMF Playbook | AI-RMF-MAP-5.1 | |
Explain the NIST AI RMF Playbook requirement: MAP 5.2 | Practices and personnel for supporting regular engagement with relevant AI actors and integrating feedback about positive, negative, and unanticipated impacts are in place and documented. About: AI systems are socio-technical in nature and can have positive, neutral, or negative implications that extend beyond their st... | NIST AI RMF Playbook | AI-RMF-MAP-5.2 | |
What is AI-RMF-MEASURE-1.1 in the NIST AI RMF Playbook framework? | Approaches and metrics for measurement of AI risks enumerated during the Map function are selected for implementation starting with the most significant AI risks. The risks or trustworthiness characteristics that will not – or cannot – be measured are properly documented. About: The development and utility of trustwort... | NIST AI RMF Playbook | AI-RMF-MEASURE-1.1 | |
What is AI-RMF-MEASURE-1.2 in the NIST AI RMF Playbook framework? | Appropriateness of AI metrics and effectiveness of existing controls is regularly assessed and updated including reports of errors and impacts on affected communities. About: Different AI tasks, such as neural networks or natural language processing, benefit from different evaluation techniques. Use-case and particular... | NIST AI RMF Playbook | AI-RMF-MEASURE-1.2 | |
Describe the security control 'MEASURE 1.3' from NIST AI RMF Playbook. | Internal experts who did not serve as front-line developers for the system and/or independent assessors are involved in regular assessments and updates. Domain experts, users, AI actors external to the team that developed or deployed the AI system, and affected communities are consulted in support of assessments as nec... | NIST AI RMF Playbook | AI-RMF-MEASURE-1.3 | |
What is AI-RMF-MEASURE-2.1 in the NIST AI RMF Playbook framework? | Test sets, metrics, and details about the tools used during test, evaluation, validation, and verification (TEVV) are documented. About: Documenting measurement approaches, test sets, metrics, processes and materials used, and associated details builds foundation upon which to build a valid, reliable measurement proces... | NIST AI RMF Playbook | AI-RMF-MEASURE-2.1 | |
Explain the NIST AI RMF Playbook requirement: MEASURE 2.2 | Evaluations involving human subjects meet applicable requirements (including human subject protection) and are representative of the relevant population. About: Measurement and evaluation of AI systems often involves testing with human subjects or using data captured from human subjects. Protection of human subjects is... | NIST AI RMF Playbook | AI-RMF-MEASURE-2.2 | |
Explain the NIST AI RMF Playbook requirement: MEASURE 2.3 | AI system performance or assurance criteria are measured qualitatively or quantitatively and demonstrated for conditions similar to deployment setting(s). Measures are documented. About: The current risk and impact environment suggests AI system performance estimates are insufficient and require a deeper understanding ... | NIST AI RMF Playbook | AI-RMF-MEASURE-2.3 | |
What is AI-RMF-MEASURE-2.4 in the NIST AI RMF Playbook framework? | The functionality and behavior of the AI system and its components – as identified in the MAP function – are monitored when in production. About: AI systems may encounter new issues and risks while in production as the environment evolves over time. This effect, often referred to as “drift”, means AI systems no longer ... | NIST AI RMF Playbook | AI-RMF-MEASURE-2.4 | |
What are the requirements for MEASURE 2.5 according to NIST AI RMF Playbook? | The AI system to be deployed is demonstrated to be valid and reliable. Limitations of the generalizability beyond the conditions under which the technology was developed are documented. About: An AI system that is not validated or that fails validation may be inaccurate or unreliable or may generalize poorly to data an... | NIST AI RMF Playbook | AI-RMF-MEASURE-2.5 | |
What is AI-RMF-MEASURE-2.6 in the NIST AI RMF Playbook framework? | AI system is evaluated regularly for safety risks – as identified in the MAP function. The AI system to be deployed is demonstrated to be safe, its residual negative risk does not exceed the risk tolerance, and can fail safely, particularly if made to operate beyond its knowledge limits. Safety metrics implicate system... | NIST AI RMF Playbook | AI-RMF-MEASURE-2.6 | |
Describe the security control 'MEASURE 2.7' from NIST AI RMF Playbook. | AI system security and resilience – as identified in the MAP function – are evaluated and documented. About: AI systems, as well as the ecosystems in which they are deployed, may be said to be resilient if they can withstand unexpected adverse events or unexpected changes in their environment or use – or if they can ma... | NIST AI RMF Playbook | AI-RMF-MEASURE-2.7 | |
What are the requirements for MEASURE 2.8 according to NIST AI RMF Playbook? | Risks associated with transparency and accountability – as identified in the MAP function – are examined and documented. About: Transparency enables meaningful visibility into entire AI pipelines, workflows, processes or organizations and decreases information asymmetry between AI developers and operators and other AI ... | NIST AI RMF Playbook | AI-RMF-MEASURE-2.8 | |
What is AI-RMF-MEASURE-2.9 in the NIST AI RMF Playbook framework? | The AI model is explained, validated, and documented, and AI system output is interpreted within its context – as identified in the MAP function – and to inform responsible use and governance. About: Explainability and interpretability assist those operating or overseeing an AI system, as well as users of an AI system,... | NIST AI RMF Playbook | AI-RMF-MEASURE-2.9 | |
Describe the security control 'MEASURE 2.10' from NIST AI RMF Playbook. | Privacy risk of the AI system – as identified in the MAP function – is examined and documented. About: Privacy refers generally to the norms and practices that help to safeguard human autonomy, identity, and dignity. These norms and practices typically address freedom from intrusion, limiting observation, or individual... | NIST AI RMF Playbook | AI-RMF-MEASURE-2.10 | |
What are the requirements for MEASURE 2.11 according to NIST AI RMF Playbook? | Fairness and bias – as identified in the MAP function – are evaluated and results are documented. About: Fairness in AI includes concerns for equality and equity by addressing issues such as harmful bias and discrimination. Standards of fairness can be complex and difficult to define because perceptions of fairness dif... | NIST AI RMF Playbook | AI-RMF-MEASURE-2.11 | |
Explain the NIST AI RMF Playbook requirement: MEASURE 2.12 | Environmental impact and sustainability of AI model training and management activities – as identified in the MAP function – are assessed and documented. About: Large-scale, high-performance computational resources used by AI systems for training and operation can contribute to environmental impacts. Direct negative im... | NIST AI RMF Playbook | AI-RMF-MEASURE-2.12 | |
What is AI-RMF-MEASURE-2.13 in the NIST AI RMF Playbook framework? | Effectiveness of the employed TEVV metrics and processes in the MEASURE function are evaluated and documented. About: The development of metrics is a process often considered to be objective but, as a human and organization driven endeavor, can reflect implicit and systemic biases, and may inadvertently reflect factors... | NIST AI RMF Playbook | AI-RMF-MEASURE-2.13 | |
Explain the NIST AI RMF Playbook requirement: MEASURE 3.1 | Approaches, personnel, and documentation are in place to regularly identify and track existing, unanticipated, and emergent AI risks based on factors such as intended and actual performance in deployed contexts. About: For trustworthy AI systems, regular system monitoring is carried out in accordance with organizationa... | NIST AI RMF Playbook | AI-RMF-MEASURE-3.1 | |
What are the requirements for MEASURE 3.2 according to NIST AI RMF Playbook? | Risk tracking approaches are considered for settings where AI risks are difficult to assess using currently available measurement techniques or where metrics are not yet available. About: Risks identified in the Map function may be complex, emerge over time, or difficult to measure. Systematic methods for risk tracking... | NIST AI RMF Playbook | AI-RMF-MEASURE-3.2 | |
Explain the NIST AI RMF Playbook requirement: MEASURE 3.3 | Feedback processes for end users and impacted communities to report problems and appeal system outcomes are established and integrated into AI system evaluation metrics. About: Assessing impact is a two-way effort. Many AI system outcomes and impacts may not be visible or recognizable to AI actors across the developmen... | NIST AI RMF Playbook | AI-RMF-MEASURE-3.3 | |
Describe the security control 'MEASURE 4.1' from NIST AI RMF Playbook. | Measurement approaches for identifying AI risks are connected to deployment context(s) and informed through consultation with domain experts and other end users. Approaches are documented. About: AI Actors carrying out TEVV tasks may have difficulty evaluating impacts within the system context of use. AI system risks a... | NIST AI RMF Playbook | AI-RMF-MEASURE-4.1 | |
What are the requirements for MEASURE 4.2 according to NIST AI RMF Playbook? | Measurement results regarding AI system trustworthiness in deployment context(s) and across AI lifecycle are informed by input from domain experts and other relevant AI actors to validate whether the system is performing consistently as intended. Results are documented. About: Feedback captured from relevant AI Actors ... | NIST AI RMF Playbook | AI-RMF-MEASURE-4.2 | |
Explain the NIST AI RMF Playbook requirement: MEASURE 4.3 | Measurable performance improvements or declines based on consultations with relevant AI actors including affected communities, and field data about context-relevant risks and trustworthiness characteristics, are identified and documented. About: TEVV activities conducted throughout the AI system lifecycle can provide b... | NIST AI RMF Playbook | AI-RMF-MEASURE-4.3 | |
What is CSF-GV in the NIST CSF 2.0 framework? | The organization's cybersecurity risk management strategy, expectations, and policy are established, communicated, and monitored | NIST CSF 2.0 | CSF-GV | |
What are the requirements for Organizational Context according to NIST CSF 2.0? | The circumstances - mission, stakeholder expectations, dependencies, and legal, regulatory, and contractual requirements - surrounding the organization's cybersecurity risk management decisions are understood
Additional Context: Function: GOVERN | NIST CSF 2.0 | CSF-GV.OC | |
Describe the security control 'GV.OC-01' from NIST CSF 2.0. | The organizational mission is understood and informs cybersecurity risk management 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
Additional Context: Parent: Organizational Context | NIST CSF 2.0 | CSF-GV.OC-01 | |
What is CSF-GV.OC-02 in the NIST CSF 2.0 framework? | Internal and external stakeholders are understood, and their needs and expectations regarding cybersecurity risk management are understood and considered Identify relevant internal stakeholders and their cybersecurity-related expectations (e.g., performance and risk expectations of officers, directors, and advisors; cu... | NIST CSF 2.0 | CSF-GV.OC-02 | |
Describe the security control 'GV.OC-03' from NIST CSF 2.0. | Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed Determine a process to track and manage legal and regulatory requirements regarding protection of individuals' information (e.g., Health Insurance Portability and Acco... | NIST CSF 2.0 | CSF-GV.OC-03 | |
What is CSF-GV.OC-04 in the NIST CSF 2.0 framework? | Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organization are understood and communicated Establish criteria for determining the criticality of capabilities and services as viewed by internal and external stakeholders Determine (e.g., from a business impact ana... | NIST CSF 2.0 | CSF-GV.OC-04 | |
What is CSF-GV.OC-05 in the NIST CSF 2.0 framework? | Outcomes, capabilities, and services that the organization depends on are understood and communicated 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 Identify and docume... | NIST CSF 2.0 | CSF-GV.OC-05 | |
What is CSF-GV.OV in the NIST CSF 2.0 framework? | Results of organization-wide cybersecurity risk management activities and performance are used to inform, improve, and adjust the risk management strategy
Additional Context: Function: GOVERN | NIST CSF 2.0 | CSF-GV.OV | |
What is CSF-GV.OV-01 in the NIST CSF 2.0 framework? | Cybersecurity risk management strategy outcomes are reviewed to inform and adjust strategy and direction Measure how well the risk management strategy and risk results have helped leaders make decisions and achieve organizational objectives Examine whether cybersecurity risk strategies that impede operations or innovat... | NIST CSF 2.0 | CSF-GV.OV-01 | |
Describe the security control 'GV.OV-02' from NIST CSF 2.0. | The cybersecurity risk management strategy is reviewed and adjusted to ensure coverage of organizational requirements and risks Review audit findings to confirm whether the existing cybersecurity strategy has ensured compliance with internal and external requirements Review the performance oversight of those in cyberse... | NIST CSF 2.0 | CSF-GV.OV-02 | |
Describe the security control 'GV.OV-03' from NIST CSF 2.0. | Organizational cybersecurity risk management performance is evaluated and reviewed for adjustments needed Review key performance indicators (KPIs) to ensure that organization-wide policies and procedures achieve objectives Review key risk indicators (KRIs) to identify risks the organization faces, including likelihood ... | NIST CSF 2.0 | CSF-GV.OV-03 | |
Explain the NIST CSF 2.0 requirement: Policy | Organizational cybersecurity policy is established, communicated, and enforced
Additional Context: Function: GOVERN | NIST CSF 2.0 | CSF-GV.PO | |
What is CSF-GV.PO-01 in the NIST CSF 2.0 framework? | Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced Create, disseminate, and maintain an understandable, usable risk management policy with statements of management intent, expectations, and direction Periodicall... | NIST CSF 2.0 | CSF-GV.PO-01 | |
Explain the NIST CSF 2.0 requirement: GV.PO-02 | Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission Update policy based on periodic reviews of cybersecurity risk management results to ensure that policy and supporting processes and procedures adeq... | NIST CSF 2.0 | CSF-GV.PO-02 | |
Explain the NIST CSF 2.0 requirement: Risk Management Strategy | The organization's priorities, constraints, risk tolerance and appetite statements, and assumptions are established, communicated, and used to support operational risk decisions
Additional Context: Function: GOVERN | NIST CSF 2.0 | CSF-GV.RM | |
What is CSF-GV.RM-01 in the NIST CSF 2.0 framework? | Risk management objectives are established and agreed to by organizational stakeholders Update near-term and long-term cybersecurity risk management objectives as part of annual strategic planning and when major changes occur Establish measurable objectives for cybersecurity risk management (e.g., manage the quality of... | NIST CSF 2.0 | CSF-GV.RM-01 | |
What is CSF-GV.RM-02 in the NIST CSF 2.0 framework? | Risk appetite and risk tolerance statements are established, communicated, and maintained Determine and communicate risk appetite statements that convey expectations about the appropriate level of risk for the organization Translate risk appetite statements into specific, measurable, and broadly understandable risk tol... | NIST CSF 2.0 | CSF-GV.RM-02 | |
What are the requirements for GV.RM-03 according to NIST CSF 2.0? | Cybersecurity risk management activities and outcomes are included in enterprise risk management processes Aggregate and manage cybersecurity risks alongside other enterprise risks (e.g., compliance, financial, operational, regulatory, reputational, safety) Include cybersecurity risk managers in enterprise risk managem... | NIST CSF 2.0 | CSF-GV.RM-03 | |
Explain the NIST CSF 2.0 requirement: GV.RM-04 | Strategic direction that describes appropriate risk response options is established and communicated Specify criteria for accepting and avoiding cybersecurity risk for various classifications of data Determine whether to purchase cybersecurity insurance Document conditions under which shared responsibility models are a... | NIST CSF 2.0 | CSF-GV.RM-04 | |
Explain the NIST CSF 2.0 requirement: GV.RM-05 | Lines of communication across the organization are established for cybersecurity risks, including risks from suppliers and other third parties Determine how to update senior executives, directors, and management on the organization's cybersecurity posture at agreed-upon intervals Identify how all departments across the... | NIST CSF 2.0 | CSF-GV.RM-05 | |
What are the requirements for GV.RM-06 according to NIST CSF 2.0? | A standardized method for calculating, documenting, categorizing, and prioritizing cybersecurity risks is established and communicated Establish criteria for using a quantitative approach to cybersecurity risk analysis, and specify probability and exposure formulas Create and use templates (e.g., a risk register) to do... | NIST CSF 2.0 | CSF-GV.RM-06 | |
What is CSF-GV.RM-07 in the NIST CSF 2.0 framework? | Strategic opportunities (i.e., positive risks) are characterized and are included in organizational cybersecurity risk discussions Define and communicate guidance and methods for identifying opportunities and including them in risk discussions (e.g., strengths, weaknesses, opportunities, and threats (SWOT) analysis) Id... | NIST CSF 2.0 | CSF-GV.RM-07 | |
Explain the NIST CSF 2.0 requirement: Roles, Responsibilities, and Authorities | Cybersecurity roles, responsibilities, and authorities to foster accountability, performance assessment, and continuous improvement are established and communicated
Additional Context: Function: GOVERN | NIST CSF 2.0 | CSF-GV.RR | |
What is CSF-GV.RR-01 in the NIST CSF 2.0 framework? | Organizational leadership is responsible and accountable for cybersecurity risk and fosters a culture that is risk-aware, ethical, and continually improving Leaders (e.g., directors) agree on their roles and responsibilities in developing, implementing, and assessing the organization's cybersecurity strategy Share lead... | NIST CSF 2.0 | CSF-GV.RR-01 | |
Describe the security control 'GV.RR-02' from NIST CSF 2.0. | Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced Document risk management roles and responsibilities in policy Document who is responsible and accountable for cybersecurity risk management activities and how those teams and individ... | NIST CSF 2.0 | CSF-GV.RR-02 | |
What is CSF-GV.RR-03 in the NIST CSF 2.0 framework? | Adequate resources are allocated commensurate with the cybersecurity risk strategy, roles, responsibilities, and policies Conduct periodic management reviews to ensure that those given cybersecurity risk management responsibilities have the necessary authority Identify resource allocation and investment in line with ri... | NIST CSF 2.0 | CSF-GV.RR-03 | |
Describe the security control 'GV.RR-04' from NIST CSF 2.0. | Cybersecurity is included in human resources practices Integrate cybersecurity risk management considerations into human resources processes (e.g., personnel screening, onboarding, change notification, offboarding) Consider cybersecurity knowledge to be a positive factor in hiring, training, and retention decisions Con... | NIST CSF 2.0 | CSF-GV.RR-04 | |
What are the requirements for Cybersecurity Supply Chain Risk Management according to NIST CSF 2.0? | Cyber supply chain risk management processes are identified, established, managed, monitored, and improved by organizational stakeholders
Additional Context: Function: GOVERN | NIST CSF 2.0 | CSF-GV.SC | |
What are the requirements for GV.SC-01 according to NIST CSF 2.0? | A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organizational stakeholders Establish a strategy that expresses the objectives of the cybersecurity supply chain risk management program Develop the cybersecurity supply chain risk manage... | NIST CSF 2.0 | CSF-GV.SC-01 | |
Describe the security control 'GV.SC-02' from NIST CSF 2.0. | Cybersecurity roles and responsibilities for suppliers, customers, and partners are established, communicated, and coordinated internally and externally Identify one or more specific roles or positions that will be responsible and accountable for planning, resourcing, and executing cybersecurity supply chain risk manag... | NIST CSF 2.0 | CSF-GV.SC-02 | |
What are the requirements for GV.SC-03 according to NIST CSF 2.0? | Cybersecurity supply chain risk management is integrated into cybersecurity and enterprise risk management, risk assessment, and improvement processes Identify areas of alignment and overlap with cybersecurity and enterprise risk management Establish integrated control sets for cybersecurity risk management and cyberse... | NIST CSF 2.0 | CSF-GV.SC-03 | |
Describe the security control 'GV.SC-04' from NIST CSF 2.0. | Suppliers are known and prioritized by criticality 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 Keep a record ... | NIST CSF 2.0 | CSF-GV.SC-04 | |
Explain the NIST CSF 2.0 requirement: GV.SC-05 | 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 Establish security requirements for suppliers, products, and services commensurate with their criticality level and poten... | NIST CSF 2.0 | CSF-GV.SC-05 | |
What are the requirements for GV.SC-06 according to NIST CSF 2.0? | Planning and due diligence are performed to reduce risks before entering into formal supplier or other third-party relationships 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 rela... | NIST CSF 2.0 | CSF-GV.SC-06 | |
Explain the NIST CSF 2.0 requirement: GV.SC-07 | 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 Adjust assessment formats and frequencies based on the third party's reputation and the criticality of the products or serv... | NIST CSF 2.0 | CSF-GV.SC-07 | |
What is CSF-GV.SC-08 in the NIST CSF 2.0 framework? | Relevant suppliers and other third parties are included in incident planning, response, and recovery activities Define and use rules and protocols for reporting incident response and recovery activities and the status between the organization and its suppliers Identify and document the roles and responsibilities of the... | NIST CSF 2.0 | CSF-GV.SC-08 | |
What is CSF-GV.SC-09 in the NIST CSF 2.0 framework? | 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 Policies and procedures require provenance records for all acquired technology products and services Periodically provide... | NIST CSF 2.0 | CSF-GV.SC-09 | |
Explain the NIST CSF 2.0 requirement: GV.SC-10 | Cybersecurity supply chain risk management plans include provisions for activities that occur after the conclusion of a partnership or service agreement Establish processes for terminating critical relationships under both normal and adverse circumstances Define and implement plans for component end-of-life maintenance... | NIST CSF 2.0 | CSF-GV.SC-10 | |
What is CSF-ID in the NIST CSF 2.0 framework? | The organization's current cybersecurity risks are understood | NIST CSF 2.0 | CSF-ID | |
What is CSF-ID.AM in the NIST CSF 2.0 framework? | 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
Additional Context: Function: IDENTIFY | NIST CSF 2.0 | CSF-ID.AM | |
What is CSF-ID.AM-01 in the NIST CSF 2.0 framework? | Inventories of hardware managed by the organization are maintained Maintain inventories for all types of hardware, including IT, IoT, OT, and mobile devices Constantly monitor networks to detect new hardware and automatically update inventories
Additional Context: Parent: Asset Management | NIST CSF 2.0 | CSF-ID.AM-01 | |
Describe the security control 'ID.AM-02' from NIST CSF 2.0. | Inventories of software, services, and systems managed by the organization are maintained 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 Constantly monitor all platforms, including... | NIST CSF 2.0 | CSF-ID.AM-02 | |
Explain the NIST CSF 2.0 requirement: ID.AM-03 | Representations of the organization's authorized network communication and internal and external network data flows are maintained Maintain baselines of communication and data flows within the organization's wired and wireless networks Maintain baselines of communication and data flows between the organization and thir... | NIST CSF 2.0 | CSF-ID.AM-03 | |
Explain the NIST CSF 2.0 requirement: ID.AM-04 | Inventories of services provided by suppliers are maintained 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 Update the inv... | NIST CSF 2.0 | CSF-ID.AM-04 | |
What are the requirements for ID.AM-05 according to NIST CSF 2.0? | Assets are prioritized based on classification, criticality, resources, and impact on the mission Define criteria for prioritizing each class of assets Apply the prioritization criteria to assets Track the asset priorities and update them periodically or when significant changes to the organization occur
Additional Co... | NIST CSF 2.0 | CSF-ID.AM-05 | |
Describe the security control 'ID.AM-06' from NIST CSF 2.0. | Cybersecurity roles and responsibilities for the entire workforce and third-party stakeholders (e.g., suppliers, customers, partners) are established
Additional Context: Parent: Asset Management | NIST CSF 2.0 | CSF-ID.AM-06 | |
Describe the security control 'ID.AM-07' from NIST CSF 2.0. | Inventories of data and corresponding metadata for designated data types are maintained 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) Continuou... | NIST CSF 2.0 | CSF-ID.AM-07 | |
What are the requirements for ID.AM-08 according to NIST CSF 2.0? | Systems, hardware, software, services, and data are managed throughout their life cycles Integrate cybersecurity considerations throughout the life cycles of systems, hardware, software, and services Integrate cybersecurity considerations into product life cycles Identify unofficial uses of technology to meet mission o... | NIST CSF 2.0 | CSF-ID.AM-08 | |
Describe the security control 'Business Environment' from NIST CSF 2.0. | Business Environment
Additional Context: Function: IDENTIFY | NIST CSF 2.0 | CSF-ID.BE | |
What are the requirements for ID.BE-01 according to NIST CSF 2.0? | The organization’s role in the supply chain is identified and communicated
Additional Context: Parent: Business Environment | NIST CSF 2.0 | CSF-ID.BE-01 | |
Describe the security control 'ID.BE-02' from NIST CSF 2.0. | The organization’s place in critical infrastructure and its industry sector is identified and communicated
Additional Context: Parent: Business Environment | NIST CSF 2.0 | CSF-ID.BE-02 | |
Explain the NIST CSF 2.0 requirement: ID.BE-03 | Priorities for organizational mission, objectives, and activities are established and communicated
Additional Context: Parent: Business Environment | NIST CSF 2.0 | CSF-ID.BE-03 | |
What is CSF-ID.BE-04 in the NIST CSF 2.0 framework? | Dependencies and critical functions for delivery of critical services are established
Additional Context: Parent: Business Environment | NIST CSF 2.0 | CSF-ID.BE-04 | |
Explain the NIST CSF 2.0 requirement: ID.BE-05 | Resilience requirements to support delivery of critical services are established for all operating states (e.g. under duress/attack, during recovery, normal operations)
Additional Context: Parent: Business Environment | NIST CSF 2.0 | CSF-ID.BE-05 | |
Explain the NIST CSF 2.0 requirement: Governance | Governance
Additional Context: Function: IDENTIFY | NIST CSF 2.0 | CSF-ID.GV | |
Describe the security control 'ID.GV-01' from NIST CSF 2.0. | Organizational cybersecurity policy is established and communicated
Additional Context: Parent: Governance | NIST CSF 2.0 | CSF-ID.GV-01 | |
Explain the NIST CSF 2.0 requirement: ID.GV-02 | Cybersecurity roles and responsibilities are coordinated and aligned with internal roles and external partners
Additional Context: Parent: Governance | NIST CSF 2.0 | CSF-ID.GV-02 | |
Describe the security control 'ID.GV-03' from NIST CSF 2.0. | Legal and regulatory requirements regarding cybersecurity, including privacy and civil liberties obligations, are understood and managed
Additional Context: Parent: Governance | NIST CSF 2.0 | CSF-ID.GV-03 | |
Explain the NIST CSF 2.0 requirement: ID.GV-04 | Governance and risk management processes address cybersecurity risks
Additional Context: Parent: Governance | NIST CSF 2.0 | CSF-ID.GV-04 | |
What are the requirements for Improvement according to NIST CSF 2.0? | Improvements to organizational cybersecurity risk management processes, procedures and activities are identified across all CSF Functions
Additional Context: Function: IDENTIFY | NIST CSF 2.0 | CSF-ID.IM | |
What is CSF-ID.IM-01 in the NIST CSF 2.0 framework? | Improvements are identified from evaluations Perform self-assessments of critical services that take current threats and TTPs into consideration Invest in third-party assessments or independent audits of the effectiveness of the organization's cybersecurity program to identify areas that need improvement Constantly eva... | NIST CSF 2.0 | CSF-ID.IM-01 | |
What is CSF-ID.IM-02 in the NIST CSF 2.0 framework? | Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties Identify improvements for future incident response activities based on findings from incident response assessments (e.g., tabletop exercises and simulations, tests, internal revi... | NIST CSF 2.0 | CSF-ID.IM-02 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.