instruction stringlengths 44 167 | input stringclasses 1
value | output stringlengths 39 11.2k | source stringclasses 6
values | id stringlengths 5 19 |
|---|---|---|---|---|
What are the requirements for Establish and Maintain a Secure Network Architecture according to CIS Controls v8.1.2? | Design and maintain a secure network architecture. A secure network architecture must address segmentation, least privilege, and availability, at a minimum. Example implementations may include documentation, policy, and design components.
Additional Context: Parent Control: Network Infrastructure Management
Security ... | CIS Controls v8.1.2 | CIS-12.2 | |
Explain the CIS Controls v8.1.2 requirement: Securely Manage Network Infrastructure | Securely manage network infrastructure. Example implementations include version-controlled Infrastructure-as-Code (IaC), and the use of secure network protocols, such as SSH and HTTPS.
Additional Context: Parent Control: Network Infrastructure Management
Security Function: Protect | Asset Class: Network | Implementat... | CIS Controls v8.1.2 | CIS-12.3 | |
Explain the CIS Controls v8.1.2 requirement: Establish and Maintain Architecture Diagram(s) | Establish and maintain architecture diagram(s) and/or other network system documentation. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.
Additional Context: Parent Control: Network Infrastructure Management
Security Function: Govern | Asset Cla... | CIS Controls v8.1.2 | CIS-12.4 | |
Describe the security control 'Centralize Network Authentication, Authorization, and Auditing (AAA)' from CIS Controls v8.1.2. | Centralize network AAA.
Additional Context: Parent Control: Network Infrastructure Management
Security Function: Protect | Asset Class: Network | Implementation Groups: IG2, IG3 | CIS Controls v8.1.2 | CIS-12.5 | |
What is CIS-12.6 in the CIS Controls v8.1.2 framework? | Adopt secure network management protocols (e.g., 802.1X) and secure communication protocols (e.g., Wi-Fi Protected Access 2 (WPA2) Enterprise or more secure alternatives).
Additional Context: Parent Control: Network Infrastructure Management
Security Function: Protect | Asset Class: Network | Implementation Groups: I... | CIS Controls v8.1.2 | CIS-12.6 | |
Describe the security control 'Ensure Remote Devices Utilize a VPN and are Connecting to an Enterprise’s AAA Infrastructure' from CIS Controls v8.1.2. | Require users to authenticate to enterprise-managed VPN and authentication services prior to accessing enterprise resources on end-user devices.
Additional Context: Parent Control: Network Infrastructure Management
Security Function: Protect | Asset Class: Devices | Implementation Groups: IG2, IG3 | CIS Controls v8.1.2 | CIS-12.7 | |
Explain the CIS Controls v8.1.2 requirement: Establish and Maintain Dedicated Computing Resources for All Administrative Work | Establish and maintain dedicated computing resources, either physically or logically separated, for all administrative tasks or tasks requiring administrative access. The computing resources should be segmented from the enterprise's primary network and not be allowed internet access.
Additional Context: Parent Control... | CIS Controls v8.1.2 | CIS-12.8 | |
What are the requirements for Network Monitoring and Defense according to CIS Controls v8.1.2? | Operate processes and tooling to establish and maintain comprehensive network monitoring and defense against security threats across the enterprise’s network infrastructure and user base. | CIS Controls v8.1.2 | CIS-13 | |
What are the requirements for Centralize Security Event Alerting according to CIS Controls v8.1.2? | Centralize security event alerting across enterprise assets for log correlation and analysis. Best practice implementation requires the use of a SIEM, which includes vendor-defined event correlation alerts. A log analytics platform configured with security-relevant correlation alerts also satisfies this Safeguard.
Add... | CIS Controls v8.1.2 | CIS-13.1 | |
What are the requirements for Deploy a Host-Based Intrusion Detection Solution according to CIS Controls v8.1.2? | Deploy a host-based intrusion detection solution on enterprise assets, where appropriate and/or supported.
Additional Context: Parent Control: Network Monitoring and Defense
Security Function: Detect | Asset Class: Devices | Implementation Groups: IG2, IG3 | CIS Controls v8.1.2 | CIS-13.2 | |
Explain the CIS Controls v8.1.2 requirement: Deploy a Network Intrusion Detection Solution | Deploy a network intrusion detection solution on enterprise assets, where appropriate. Example implementations include the use of a Network Intrusion Detection System (NIDS) or equivalent cloud service provider (CSP) service.
Additional Context: Parent Control: Network Monitoring and Defense
Security Function: Detect... | CIS Controls v8.1.2 | CIS-13.3 | |
Explain the CIS Controls v8.1.2 requirement: Perform Traffic Filtering Between Network Segments | Perform traffic filtering between network segments, where appropriate.
Additional Context: Parent Control: Network Monitoring and Defense
Security Function: Protect | Asset Class: Network | Implementation Groups: IG2, IG3 | CIS Controls v8.1.2 | CIS-13.4 | |
What is CIS-13.5 in the CIS Controls v8.1.2 framework? | Manage access control for assets remotely connecting to enterprise resources. Determine amount of access to enterprise resources based on: up-to-date anti-malware software installed, configuration compliance with the enterprise’s secure configuration process, and ensuring the operating system and applications are up-to... | CIS Controls v8.1.2 | CIS-13.5 | |
Describe the security control 'Collect Network Traffic Flow Logs' from CIS Controls v8.1.2. | Collect network traffic flow logs and/or network traffic to review and alert upon from network devices.
Additional Context: Parent Control: Network Monitoring and Defense
Security Function: Detect | Asset Class: Network | Implementation Groups: IG2, IG3 | CIS Controls v8.1.2 | CIS-13.6 | |
Explain the CIS Controls v8.1.2 requirement: Deploy a Host-Based Intrusion Prevention Solution | Deploy a host-based intrusion prevention solution on enterprise assets, where appropriate and/or supported. Example implementations include use of an Endpoint Detection and Response (EDR) client or host-based IPS agent.
Additional Context: Parent Control: Network Monitoring and Defense
Security Function: Protect | As... | CIS Controls v8.1.2 | CIS-13.7 | |
Describe the security control 'Deploy a Network Intrusion Prevention Solution' from CIS Controls v8.1.2. | Deploy a network intrusion prevention solution, where appropriate. Example implementations include the use of a Network Intrusion Prevention System (NIPS) or equivalent CSP service.
Additional Context: Parent Control: Network Monitoring and Defense
Security Function: Protect | Asset Class: Network | Implementation Gr... | CIS Controls v8.1.2 | CIS-13.8 | |
What is CIS-13.9 in the CIS Controls v8.1.2 framework? | Deploy port-level access control. Port-level access control utilizes 802.1x, or similar network access control protocols, such as certificates, and may incorporate user and/or device authentication.
Additional Context: Parent Control: Network Monitoring and Defense
Security Function: Protect | Asset Class: Network | ... | CIS Controls v8.1.2 | CIS-13.9 | |
Describe the security control 'Tune Security Event Alerting Thresholds' from CIS Controls v8.1.2. | Tune security event alerting thresholds monthly, or more frequently.
Additional Context: Parent Control: Network Monitoring and Defense
Security Function: Detect | Asset Class: Network | Implementation Groups: IG3 | CIS Controls v8.1.2 | CIS-13.11 | |
Describe the security control 'Security Awareness and Skills Training' from CIS Controls v8.1.2. | Establish and maintain a security awareness program to influence behavior among the workforce to be security conscious and properly skilled to reduce cybersecurity risks to the enterprise. | CIS Controls v8.1.2 | CIS-14 | |
What is CIS-14.1 in the CIS Controls v8.1.2 framework? | Establish and maintain a security awareness program. The purpose of a security awareness program is to educate the enterprise’s workforce on how to interact with enterprise assets and data in a secure manner. Conduct training at hire and, at a minimum, annually. Review and update content annually, or when significant e... | CIS Controls v8.1.2 | CIS-14.1 | |
What is CIS-14.2 in the CIS Controls v8.1.2 framework? | Train workforce members to recognize social engineering attacks, such as phishing, business email compromise (BEC), pretexting, and tailgating.
Additional Context: Parent Control: Security Awareness and Skills Training
Security Function: Protect | Asset Class: Users | Implementation Groups: IG1, IG2, IG3 | CIS Controls v8.1.2 | CIS-14.2 | |
Describe the security control 'Train Workforce Members on Authentication Best Practices' from CIS Controls v8.1.2. | Train workforce members on authentication best practices. Example topics include MFA, password composition, and credential management.
Additional Context: Parent Control: Security Awareness and Skills Training
Security Function: Protect | Asset Class: Users | Implementation Groups: IG1, IG2, IG3 | CIS Controls v8.1.2 | CIS-14.3 | |
Describe the security control 'Train Workforce on Data Handling Best Practices' from CIS Controls v8.1.2. | Train workforce members on how to identify and properly store, transfer, archive, and destroy sensitive data. This also includes training workforce members on clear screen and desk best practices, such as locking their screen when they step away from their enterprise asset, erasing physical and virtual whiteboards at t... | CIS Controls v8.1.2 | CIS-14.4 | |
Describe the security control 'Train Workforce Members on Causes of Unintentional Data Exposure' from CIS Controls v8.1.2. | Train workforce members to be aware of causes for unintentional data exposure. Example topics include mis-delivery of sensitive data, losing a portable end-user device, or publishing data to unintended audiences.
Additional Context: Parent Control: Security Awareness and Skills Training
Security Function: Protect | A... | CIS Controls v8.1.2 | CIS-14.5 | |
Explain the CIS Controls v8.1.2 requirement: Train Workforce Members on Recognizing and Reporting Security Incidents | Train workforce members to be able to recognize a potential incident and be able to report such an incident.
Additional Context: Parent Control: Security Awareness and Skills Training
Security Function: Protect | Asset Class: Users | Implementation Groups: IG1, IG2, IG3 | CIS Controls v8.1.2 | CIS-14.6 | |
What is CIS-14.7 in the CIS Controls v8.1.2 framework? | Train workforce to understand how to verify and report out-of-date software patches or any failures in automated processes and tools. Part of this training should include notifying IT personnel of any failures in automated processes and tools.
Additional Context: Parent Control: Security Awareness and Skills Training
... | CIS Controls v8.1.2 | CIS-14.7 | |
What are the requirements for Train Workforce on the Dangers of Connecting to and Transmitting Enterprise Data Over Insecure Networks according to CIS Controls v8.1.2? | Train workforce members on the dangers of connecting to, and transmitting data over, insecure networks for enterprise activities. If the enterprise has remote workers, training must include guidance to ensure that all users securely configure their home network infrastructure.
Additional Context: Parent Control: Secur... | CIS Controls v8.1.2 | CIS-14.8 | |
Describe the security control 'Conduct Role-Specific Security Awareness and Skills Training' from CIS Controls v8.1.2. | Conduct role-specific security awareness and skills training. Example implementations include secure system administration courses for IT professionals, OWASP® Top 10 vulnerability awareness and prevention training for web application developers, and advanced social engineering awareness training for high-profile roles... | CIS Controls v8.1.2 | CIS-14.9 | |
Describe the security control 'Service Provider Management' from CIS Controls v8.1.2. | Develop a process to evaluate service providers who hold sensitive data, or are responsible for an enterprise’s critical IT platforms or processes, to ensure these providers are protecting those platforms and data appropriately. | CIS Controls v8.1.2 | CIS-15 | |
Explain the CIS Controls v8.1.2 requirement: Establish and Maintain an Inventory of Service Providers | Establish and maintain an inventory of service providers. The inventory is to list all known service providers, include classification(s), and designate an enterprise contact for each service provider. Review and update the inventory annually, or when significant enterprise changes occur that could impact this Safeguar... | CIS Controls v8.1.2 | CIS-15.1 | |
Explain the CIS Controls v8.1.2 requirement: Establish and Maintain a Service Provider Management Policy | Establish and maintain a service provider management policy. Ensure the policy addresses the classification, inventory, assessment, monitoring, and decommissioning of service providers. Review and update the policy annually, or when significant enterprise changes occur that could impact this Safeguard.
Additional Cont... | CIS Controls v8.1.2 | CIS-15.2 | |
Explain the CIS Controls v8.1.2 requirement: Classify Service Providers | Classify service providers. Classification consideration may include one or more characteristics, such as data sensitivity, data volume, availability requirements, applicable regulations, inherent risk, and mitigated risk. Update and review classifications annually, or when significant enterprise changes occur that cou... | CIS Controls v8.1.2 | CIS-15.3 | |
What are the requirements for Ensure Service Provider Contracts Include Security Requirements according to CIS Controls v8.1.2? | Ensure service provider contracts include security requirements. Example requirements may include minimum security program requirements, security incident and/or data breach notification and response, data encryption requirements, and data disposal commitments. These security requirements must be consistent with the en... | CIS Controls v8.1.2 | CIS-15.4 | |
What is CIS-15.5 in the CIS Controls v8.1.2 framework? | Assess service providers consistent with the enterprise’s service provider management policy. Assessment scope may vary based on classification(s), and may include review of standardized assessment reports, such as Service Organization Control 2 (SOC 2) and Payment Card Industry (PCI) Attestation of Compliance (AoC), c... | CIS Controls v8.1.2 | CIS-15.5 | |
What are the requirements for Monitor Service Providers according to CIS Controls v8.1.2? | Monitor service providers consistent with the enterprise’s service provider management policy. Monitoring may include periodic reassessment of service provider compliance, monitoring service provider release notes, and dark web monitoring.
Additional Context: Parent Control: Service Provider Management
Security Funct... | CIS Controls v8.1.2 | CIS-15.6 | |
Describe the security control 'Securely Decommission Service Providers' from CIS Controls v8.1.2. | Securely decommission service providers. Example considerations include user and service account deactivation, termination of data flows, and secure disposal of enterprise data within service provider systems.
Additional Context: Parent Control: Service Provider Management
Security Function: Protect | Asset Class: Da... | CIS Controls v8.1.2 | CIS-15.7 | |
Describe the security control 'Application Software Security' from CIS Controls v8.1.2. | Manage the security life cycle of in-house developed, hosted, or acquired software to prevent, detect, and remediate security weaknesses before they can impact the enterprise. | CIS Controls v8.1.2 | CIS-16 | |
Explain the CIS Controls v8.1.2 requirement: Establish and Maintain a Secure Application Development Process | Establish and maintain a secure application development process. In the process, address such items as: secure application design standards, secure coding practices, developer training, vulnerability management, security of third-party code, and application security testing procedures. Review and update documentation a... | CIS Controls v8.1.2 | CIS-16.1 | |
Describe the security control 'Establish and Maintain a Process to Accept and Address Software Vulnerabilities' from CIS Controls v8.1.2. | Establish and maintain a process to accept and address reports of software vulnerabilities, including providing a means for external entities to report. The process is to include such items as: a vulnerability handling policy that identifies reporting process, responsible party for handling vulnerability reports, and a... | CIS Controls v8.1.2 | CIS-16.2 | |
What are the requirements for Perform Root Cause Analysis on Security Vulnerabilities according to CIS Controls v8.1.2? | Perform root cause analysis on security vulnerabilities. When reviewing vulnerabilities, root cause analysis is the task of evaluating underlying issues that create vulnerabilities in code, and allows development teams to move beyond just fixing individual vulnerabilities as they arise.
Additional Context: Parent Cont... | CIS Controls v8.1.2 | CIS-16.3 | |
Explain the CIS Controls v8.1.2 requirement: Establish and Manage an Inventory of Third-Party Software Components | Establish and manage an updated inventory of third-party components used in development, often referred to as a “bill of materials,” as well as components slated for future use. This inventory is to include any risks that each third-party component could pose. Evaluate the list at least monthly to identify any changes ... | CIS Controls v8.1.2 | CIS-16.4 | |
Describe the security control 'Use Up-to-Date and Trusted Third-Party Software Components' from CIS Controls v8.1.2. | Use up-to-date and trusted third-party software components. When possible, choose established and proven frameworks and libraries that provide adequate security. Acquire these components from trusted sources or evaluate the software for vulnerabilities before use.
Additional Context: Parent Control: Application Softwa... | CIS Controls v8.1.2 | CIS-16.5 | |
Explain the CIS Controls v8.1.2 requirement: Establish and Maintain a Severity Rating System and Process for Application Vulnerabilities | Establish and maintain a severity rating system and process for application vulnerabilities that facilitates prioritizing the order in which discovered vulnerabilities are fixed. This process includes setting a minimum level of security acceptability for releasing code or applications. Severity ratings bring a systemat... | CIS Controls v8.1.2 | CIS-16.6 | |
What is CIS-16.7 in the CIS Controls v8.1.2 framework? | Use standard, industry-recommended hardening configuration templates for application infrastructure components. This includes underlying servers, databases, and web servers, and applies to cloud containers, Platform as a Service (PaaS) components, and SaaS components. Do not allow in-house developed software to weaken ... | CIS Controls v8.1.2 | CIS-16.7 | |
What is CIS-16.8 in the CIS Controls v8.1.2 framework? | Maintain separate environments for production and non-production systems.
Additional Context: Parent Control: Application Software Security
Security Function: Protect | Asset Class: Network | Implementation Groups: IG2, IG3 | CIS Controls v8.1.2 | CIS-16.8 | |
What are the requirements for Train Developers in Application Security Concepts and Secure Coding according to CIS Controls v8.1.2? | Ensure that all software development personnel receive training in writing secure code for their specific development environment and responsibilities. Training can include general security principles and application security standard practices. Conduct training at least annually and design in a way to promote security... | CIS Controls v8.1.2 | CIS-16.9 | |
Describe the security control 'Leverage Vetted Modules or Services for Application Security Components' from CIS Controls v8.1.2. | Leverage vetted modules or services for application security components, such as identity management, encryption, auditing, and logging. Using platform features in critical security functions will reduce developers’ workload and minimize the likelihood of design or implementation errors. Modern operating systems provid... | CIS Controls v8.1.2 | CIS-16.11 | |
Describe the security control 'Implement Code-Level Security Checks' from CIS Controls v8.1.2. | Apply static and dynamic analysis tools within the application life cycle to verify that secure coding practices are being followed.
Additional Context: Parent Control: Application Software Security
Security Function: Protect | Asset Class: Software | Implementation Groups: IG3 | CIS Controls v8.1.2 | CIS-16.12 | |
What are the requirements for Conduct Application Penetration Testing according to CIS Controls v8.1.2? | Conduct application penetration testing. For critical applications, authenticated penetration testing is better suited to finding business logic vulnerabilities than code scanning and automated security testing. Penetration testing relies on the skill of the tester to manually manipulate an application as an authentica... | CIS Controls v8.1.2 | CIS-16.13 | |
What are the requirements for Conduct Threat Modeling according to CIS Controls v8.1.2? | Conduct threat modeling. Threat modeling is the process of identifying and addressing application security design flaws within a design, before code is created. It is conducted through specially trained individuals who evaluate the application design and gauge security risks for each entry point and access level. The g... | CIS Controls v8.1.2 | CIS-16.14 | |
Explain the CIS Controls v8.1.2 requirement: Incident Response Management | Establish a program to develop and maintain an incident response capability (e.g., policies, plans, procedures, defined roles, training, and communications) to prepare, detect, and quickly respond to an attack. | CIS Controls v8.1.2 | CIS-17 | |
What are the requirements for Designate Personnel to Manage Incident Handling according to CIS Controls v8.1.2? | Designate one key person, and at least one backup, who will manage the enterprise’s incident handling process. Management personnel are responsible for the coordination and documentation of incident response and recovery efforts and can consist of employees internal to the enterprise, service providers, or a hybrid app... | CIS Controls v8.1.2 | CIS-17.1 | |
What are the requirements for Establish and Maintain Contact Information for Reporting Security Incidents according to CIS Controls v8.1.2? | Establish and maintain contact information for parties that need to be informed of security incidents. Contacts may include internal staff, service providers, law enforcement, cyber insurance providers, relevant government agencies, Information Sharing and Analysis Center (ISAC) partners, or other stakeholders. Verify ... | CIS Controls v8.1.2 | CIS-17.2 | |
Describe the security control 'Establish and Maintain an Enterprise Process for Reporting Incidents' from CIS Controls v8.1.2. | Establish and maintain a documented enterprise process for the workforce to report security incidents. The process includes reporting timeframe, personnel to report to, mechanism for reporting, and the minimum information to be reported. Ensure the process is publicly available to all of the workforce. Review annually,... | CIS Controls v8.1.2 | CIS-17.3 | |
What is CIS-17.4 in the CIS Controls v8.1.2 framework? | Establish and maintain a documented incident response process that addresses roles and responsibilities, compliance requirements, and a communication plan. Review annually, or when significant enterprise changes occur that could impact this Safeguard.
Additional Context: Parent Control: Incident Response Management
S... | CIS Controls v8.1.2 | CIS-17.4 | |
Describe the security control 'Assign Key Roles and Responsibilities' from CIS Controls v8.1.2. | Assign key roles and responsibilities for incident response, including staff from legal, IT, information security, facilities, public relations, human resources, incident responders, analysts, and relevant third parties. Review annually, or when significant enterprise changes occur that could impact this Safeguard.
Ad... | CIS Controls v8.1.2 | CIS-17.5 | |
What are the requirements for Define Mechanisms for Communicating During Incident Response according to CIS Controls v8.1.2? | Determine which primary and secondary mechanisms will be used to communicate and report during a security incident. Mechanisms can include phone calls, emails, secure chat, or notification letters. Keep in mind that certain mechanisms, such as emails, can be affected during a security incident. Review annually, or when... | CIS Controls v8.1.2 | CIS-17.6 | |
What are the requirements for Conduct Routine Incident Response Exercises according to CIS Controls v8.1.2? | Plan and conduct routine incident response exercises and scenarios for key personnel involved in the incident response process to prepare for responding to real-world incidents. Exercises need to test communication channels, decision making, and workflows. Conduct testing on an annual basis, at a minimum.
Additional C... | CIS Controls v8.1.2 | CIS-17.7 | |
What are the requirements for Conduct Post-Incident Reviews according to CIS Controls v8.1.2? | Conduct post-incident reviews. Post-incident reviews help prevent incident recurrence through identifying lessons learned and follow-up action.
Additional Context: Parent Control: Incident Response Management
Security Function: Recover | Asset Class: Users | Implementation Groups: IG2, IG3 | CIS Controls v8.1.2 | CIS-17.8 | |
What are the requirements for Establish and Maintain Security Incident Thresholds according to CIS Controls v8.1.2? | Establish and maintain security incident thresholds, including, at a minimum, differentiating between an incident and an event. Examples can include: abnormal activity, security vulnerability, security weakness, data breach, privacy incident, etc. Review annually, or when significant enterprise changes occur that could... | CIS Controls v8.1.2 | CIS-17.9 | |
Explain the CIS Controls v8.1.2 requirement: Penetration Testing | Test the effectiveness and resiliency of enterprise assets through identifying and exploiting weaknesses in controls (people, processes, and technology), and simulating the objectives and actions of an attacker. | CIS Controls v8.1.2 | CIS-18 | |
Describe the security control 'Establish and Maintain a Penetration Testing Program' from CIS Controls v8.1.2. | Establish and maintain a penetration testing program appropriate to the size, complexity, industry, and maturity of the enterprise. Penetration testing program characteristics include scope, such as network, web application, Application Programming Interface (API), hosted services, and physical premise controls; freque... | CIS Controls v8.1.2 | CIS-18.1 | |
What are the requirements for Perform Periodic External Penetration Tests according to CIS Controls v8.1.2? | Perform periodic external penetration tests based on program requirements, no less than annually. External penetration testing must include enterprise and environmental reconnaissance to detect exploitable information. Penetration testing requires specialized skills and experience and must be conducted through a qualif... | CIS Controls v8.1.2 | CIS-18.2 | |
Describe the security control 'Remediate Penetration Test Findings' from CIS Controls v8.1.2. | Remediate penetration test findings based on the enterprise’s documented vulnerability remediation process. This should include determining a timeline and level of effort based on the impact and prioritization of each identified finding.
Additional Context: Parent Control: Penetration Testing
Security Function: Prote... | CIS Controls v8.1.2 | CIS-18.3 | |
Explain the CIS Controls v8.1.2 requirement: Validate Security Measures | Validate security measures after each penetration test. If deemed necessary, modify rulesets and capabilities to detect the techniques used during testing.
Additional Context: Parent Control: Penetration Testing
Security Function: Protect | Asset Class: Network | Implementation Groups: IG3 | CIS Controls v8.1.2 | CIS-18.4 | |
Describe the security control 'Perform Periodic Internal Penetration Tests' from CIS Controls v8.1.2. | Perform periodic internal penetration tests based on program requirements, no less than annually. The testing may be clear box or opaque box.
Additional Context: Parent Control: Penetration Testing
Security Function: Detect | Asset Class: Network | Implementation Groups: IG3 | CIS Controls v8.1.2 | CIS-18.5 | |
What is AI-RMF-GOVERN-1.1 in the NIST AI RMF Playbook framework? | Legal and regulatory requirements involving AI are understood, managed, and documented. About: AI systems may be subject to specific applicable legal and regulatory requirements. Some legal requirements can mandate (e.g., nondiscrimination, data privacy and security controls) documentation, disclosure, and increased AI... | NIST AI RMF Playbook | AI-RMF-GOVERN-1.1 | |
What is AI-RMF-GOVERN-1.2 in the NIST AI RMF Playbook framework? | The characteristics of trustworthy AI are integrated into organizational policies, processes, and procedures. About: Policies, processes, and procedures are central components of effective AI risk management and fundamental to individual and organizational accountability. All stakeholders benefit from policies, process... | NIST AI RMF Playbook | AI-RMF-GOVERN-1.2 | |
Describe the security control 'GOVERN 1.3' from NIST AI RMF Playbook. | Processes and procedures are in place to determine the needed level of risk management activities based on the organization's risk tolerance. About: Risk management resources are finite in any organization. Adequate AI governance policies delineate the mapping, measurement, and prioritization of risks to allocate resou... | NIST AI RMF Playbook | AI-RMF-GOVERN-1.3 | |
What are the requirements for GOVERN 1.4 according to NIST AI RMF Playbook? | The risk management process and its outcomes are established through transparent policies, procedures, and other controls based on organizational risk priorities. About: Clear policies and procedures relating to documentation and transparency facilitate and enhance efforts to communicate roles and responsibilities for ... | NIST AI RMF Playbook | AI-RMF-GOVERN-1.4 | |
Describe the security control 'GOVERN 1.5' from NIST AI RMF Playbook. | Ongoing monitoring and periodic review of the risk management process and its outcomes are planned, organizational roles and responsibilities are clearly defined, including determining the frequency of periodic review. About: AI systems are dynamic and may perform in unexpected ways once deployed or after deployment. C... | NIST AI RMF Playbook | AI-RMF-GOVERN-1.5 | |
Describe the security control 'GOVERN 1.6' from NIST AI RMF Playbook. | Mechanisms are in place to inventory AI systems and are resourced according to organizational risk priorities. About: An AI system inventory is an organized database of artifacts relating to an AI system or model. It may include system documentation, incident response plans, data dictionaries, links to implementation s... | NIST AI RMF Playbook | AI-RMF-GOVERN-1.6 | |
Explain the NIST AI RMF Playbook requirement: GOVERN 1.7 | Processes and procedures are in place for decommissioning and phasing out of AI systems safely and in a manner that does not increase risks or decrease the organization’s trustworthiness. About: Irregular or indiscriminate termination or deletion of models or AI systems may be inappropriate and increase organizational ... | NIST AI RMF Playbook | AI-RMF-GOVERN-1.7 | |
What are the requirements for GOVERN 2.1 according to NIST AI RMF Playbook? | Roles and responsibilities and lines of communication related to mapping, measuring, and managing AI risks are documented and are clear to individuals and teams throughout the organization. About: The development of a risk-aware organizational culture starts with defining responsibilities. For example, under some risk ... | NIST AI RMF Playbook | AI-RMF-GOVERN-2.1 | |
Describe the security control 'GOVERN 2.2' from NIST AI RMF Playbook. | The organization’s personnel and partners receive AI risk management training to enable them to perform their duties and responsibilities consistent with related policies, procedures, and agreements. About: To enhance AI risk management adoption and effectiveness, organizations are encouraged to identify and integrate ... | NIST AI RMF Playbook | AI-RMF-GOVERN-2.2 | |
What are the requirements for GOVERN 2.3 according to NIST AI RMF Playbook? | Executive leadership of the organization takes responsibility for decisions about risks associated with AI system development and deployment. About: Senior leadership and members of the C-Suite in organizations that maintain an AI portfolio, should maintain awareness of AI risks, affirm the organizational appetite for ... | NIST AI RMF Playbook | AI-RMF-GOVERN-2.3 | |
Describe the security control 'GOVERN 3.1' from NIST AI RMF Playbook. | Decision-makings related to mapping, measuring, and managing AI risks throughout the lifecycle is informed by a diverse team (e.g., diversity of demographics, disciplines, experience, expertise, and backgrounds). About: A diverse team that includes AI actors with diversity of experience, disciplines, and backgrounds to... | NIST AI RMF Playbook | AI-RMF-GOVERN-3.1 | |
What are the requirements for GOVERN 3.2 according to NIST AI RMF Playbook? | Policies and procedures are in place to define and differentiate roles and responsibilities for human-AI configurations and oversight of AI systems. About: Identifying and managing AI risks and impacts are enhanced when a broad set of perspectives and actors across the AI lifecycle, including technical, legal, complian... | NIST AI RMF Playbook | AI-RMF-GOVERN-3.2 | |
What is AI-RMF-GOVERN-4.1 in the NIST AI RMF Playbook framework? | Organizational policies, and practices are in place to foster a critical thinking and safety-first mindset in the design, development, deployment, and uses of AI systems to minimize negative impacts. About: A risk culture and accompanying practices can help organizations effectively triage the most critical risks. Orga... | NIST AI RMF Playbook | AI-RMF-GOVERN-4.1 | |
Describe the security control 'GOVERN 4.2' from NIST AI RMF Playbook. | Organizational teams document the risks and potential impacts of the AI technology they design, develop, deploy, evaluate and use, and communicate about the impacts more broadly. About: Impact assessments are one approach for driving responsible technology development practices. And, within a specific use case, these a... | NIST AI RMF Playbook | AI-RMF-GOVERN-4.2 | |
What are the requirements for GOVERN 4.3 according to NIST AI RMF Playbook? | Organizational practices are in place to enable AI testing, identification of incidents, and information sharing. About: Identifying AI system limitations, detecting and tracking negative impacts and incidents, and sharing information about these issues with appropriate AI actors will improve risk management. Issues su... | NIST AI RMF Playbook | AI-RMF-GOVERN-4.3 | |
What are the requirements for GOVERN 5.1 according to NIST AI RMF Playbook? | Organizational policies and practices are in place to collect, consider, prioritize, and integrate feedback from those external to the team that developed or deployed the AI system regarding the potential individual and societal impacts related to AI risks. About: Beyond internal and laboratory-based system testing, or... | NIST AI RMF Playbook | AI-RMF-GOVERN-5.1 | |
What are the requirements for GOVERN 5.2 according to NIST AI RMF Playbook? | Mechanisms are established to enable AI actors to regularly incorporate adjudicated feedback from relevant AI actors into system design and implementation. About: Organizational policies and procedures that equip AI actors with the processes, knowledge, and expertise needed to inform collaborative decisions about syste... | NIST AI RMF Playbook | AI-RMF-GOVERN-5.2 | |
What are the requirements for GOVERN 6.1 according to NIST AI RMF Playbook? | Policies and procedures are in place that address AI risks associated with third-party entities, including risks of infringement of a third party’s intellectual property or other rights. About: Risk measurement and management can be complicated by how customers use or integrate third-party data or systems into AI produ... | NIST AI RMF Playbook | AI-RMF-GOVERN-6.1 | |
Explain the NIST AI RMF Playbook requirement: GOVERN 6.2 | Contingency processes are in place to handle failures or incidents in third-party data or AI systems deemed to be high-risk. About: To mitigate the potential harms of third-party system failures, organizations may implement policies and procedures that include redundancies for covering third-party functions.
Additiona... | NIST AI RMF Playbook | AI-RMF-GOVERN-6.2 | |
What are the requirements for MANAGE 1.1 according to NIST AI RMF Playbook? | A determination is made as to whether the AI system achieves its intended purpose and stated objectives and whether its development or deployment should proceed. About: AI systems may not necessarily be the right solution for a given business task or problem. A standard risk management practice is to formally weigh an ... | NIST AI RMF Playbook | AI-RMF-MANAGE-1.1 | |
Explain the NIST AI RMF Playbook requirement: MANAGE 1.2 | Treatment of documented AI risks is prioritized based on impact, likelihood, or available resources or methods. About: Risk refers to the composite measure of an event’s probability of occurring and the magnitude (or degree) of the consequences of the corresponding events. The impacts, or consequences, of AI systems ca... | NIST AI RMF Playbook | AI-RMF-MANAGE-1.2 | |
What is AI-RMF-MANAGE-1.3 in the NIST AI RMF Playbook framework? | Responses to the AI risks deemed high priority as identified by the Map function, are developed, planned, and documented. Risk response options can include mitigating, transferring, avoiding, or accepting. About: Outcomes from GOVERN-1, MAP-5 and MEASURE-2, can be used to address and document identified risks based on ... | NIST AI RMF Playbook | AI-RMF-MANAGE-1.3 | |
What is AI-RMF-MANAGE-1.4 in the NIST AI RMF Playbook framework? | Negative residual risks (defined as the sum of all unmitigated risks) to both downstream acquirers of AI systems and end users are documented. About: Organizations may choose to accept or transfer some of the documented risks from MAP and MANAGE 1.3 and 2.1. Such risks, known as residual risk, may affect downstream AI ... | NIST AI RMF Playbook | AI-RMF-MANAGE-1.4 | |
Describe the security control 'MANAGE 2.1' from NIST AI RMF Playbook. | Resources required to manage AI risks are taken into account, along with viable non-AI alternative systems, approaches, or methods – to reduce the magnitude or likelihood of potential impacts. About: Organizational risk response may entail identifying and analyzing alternative approaches, methods, processes or systems,... | NIST AI RMF Playbook | AI-RMF-MANAGE-2.1 | |
What are the requirements for MANAGE 2.2 according to NIST AI RMF Playbook? | Mechanisms are in place and applied to sustain the value of deployed AI systems. About: System performance and trustworthiness may evolve and shift over time, once an AI system is deployed and put into operation. This phenomenon, generally known as drift, can degrade the value of the AI system to the organization and i... | NIST AI RMF Playbook | AI-RMF-MANAGE-2.2 | |
What is AI-RMF-MANAGE-2.3 in the NIST AI RMF Playbook framework? | Procedures are followed to respond to and recover from a previously unknown risk when it is identified. About: AI systems – like any technology – can demonstrate non-functionality or failure or unexpected and unusual behavior. They also can be subject to attacks, incidents, or other misuse or abuse – which their source... | NIST AI RMF Playbook | AI-RMF-MANAGE-2.3 | |
What is AI-RMF-MANAGE-2.4 in the NIST AI RMF Playbook framework? | Mechanisms are in place and applied, responsibilities are assigned and understood to supersede, disengage, or deactivate AI systems that demonstrate performance or outcomes inconsistent with intended use. About: Performance inconsistent with intended use does not always increase risk or lead to negative impacts. Rigoro... | NIST AI RMF Playbook | AI-RMF-MANAGE-2.4 | |
What are the requirements for MANAGE 3.1 according to NIST AI RMF Playbook? | AI risks and benefits from third-party resources are regularly monitored, and risk controls are applied and documented. About: AI systems may depend on external resources and associated processes, including third-party data, software or hardware systems. Third parties’ supplying organizations with components and servic... | NIST AI RMF Playbook | AI-RMF-MANAGE-3.1 | |
Describe the security control 'MANAGE 3.2' from NIST AI RMF Playbook. | Pre-trained models which are used for development are monitored as part of AI system regular monitoring and maintenance. About: A common approach in AI development is transfer learning, whereby an existing pre-trained model is adapted for use in a different, but related application. AI actors in development tasks often... | NIST AI RMF Playbook | AI-RMF-MANAGE-3.2 | |
Describe the security control 'MANAGE 4.1' from NIST AI RMF Playbook. | Post-deployment AI system monitoring plans are implemented, including mechanisms for capturing and evaluating input from users and other relevant AI actors, appeal and override, decommissioning, incident response, recovery, and change management. About: AI system performance and trustworthiness can change due to a vari... | NIST AI RMF Playbook | AI-RMF-MANAGE-4.1 | |
Describe the security control 'MANAGE 4.2' from NIST AI RMF Playbook. | Measurable activities for continual improvements are integrated into AI system updates and include regular engagement with interested parties, including relevant AI actors. About: Regular monitoring processes enable system updates to enhance performance and functionality in accordance with regulatory and legal framewor... | NIST AI RMF Playbook | AI-RMF-MANAGE-4.2 | |
What is AI-RMF-MANAGE-4.3 in the NIST AI RMF Playbook framework? | Incidents and errors are communicated to relevant AI actors including affected communities. Processes for tracking, responding to, and recovering from incidents and errors are followed and documented. About: Regularly documenting an accurate and transparent account of identified and reported errors can enhance AI risk ... | NIST AI RMF Playbook | AI-RMF-MANAGE-4.3 | |
What are the requirements for MAP 1.1 according to NIST AI RMF Playbook? | Intended purpose, potentially beneficial uses, context-specific laws, norms and expectations, and prospective settings in which the AI system will be deployed are understood and documented. Considerations include: specific set or types of users along with their expectations; potential positive and negative impacts of s... | NIST AI RMF Playbook | AI-RMF-MAP-1.1 | |
What is AI-RMF-MAP-1.2 in the NIST AI RMF Playbook framework? | Inter-disciplinary AI actors, competencies, skills and capacities for establishing context reflect demographic diversity and broad domain and user experience expertise, and their participation is documented. Opportunities for interdisciplinary collaboration are prioritized. About: Successfully mapping context requires ... | NIST AI RMF Playbook | AI-RMF-MAP-1.2 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.