HITRUST CSF requirement statement [?] (12.09abAISecSystem.3)
The design of the AI application allows its human operators the ability to
(1) evaluate AI model outputs before relying on them and
(2) intervene in AI model-initiated actions (e.g., sending emails, modifying records) if
deemed necessary.
- Evaluative elements in this requirement statement [?]
-
1. The design of the AI system allows its human operators the ability to evaluate AI model outputs before relying on.
2. The design of the AI system allows its human operators the ability to intervene in AI model-initiated actions (e.g., sending emails, modifying records) if deemed necessary.
- Illustrative procedures for use during assessments [?]
- Policy: Examine policies related to each evaluative element within the requirement statement. Validate the existence of a written or undocumented policy as defined in the HITRUST scoring rubric.
- Procedure: Examine evidence that written or undocumented procedures exist as defined in the HITRUST scoring rubric. Determine if the procedures and address the operational aspects of how to perform each evaluative element within the requirement statement.
- Implemented: Examine evidence that all evaluative elements within the requirement statement have been implemented as defined in the HITRUST scoring rubric, using a sample based test where possible for each evaluative element. Example test(s):
- For example, review the AI application to confirm it allows a human operator to evaluate AI model outputs. Further, confirm the ability for human operators to intervene in AI model-initiated actions when necessary.
- For example, review the AI application to confirm it allows a human operator to evaluate AI model outputs. Further, confirm the ability for human operators to intervene in AI model-initiated actions when necessary.
- Measured: Examine measurements that formally evaluate and communicate the operation and/or performance of each evaluative element within the requirement statement. Determine the percentage of evaluative elements addressed by the organization’s operational and/or independent measure(s) or metric(s) as defined in the HITRUST scoring rubric. Determine if the measurements include independent and/or operational measure(s) or metric(s) as defined in the HITRUST scoring rubric. Example test(s):
- For example, measures indicate if the AI application allows human operators to evaluate AI model outputs and intervene in AI model-initiated actions when necessary. Reviews, tests, or audits are completed by the organization to measure the effectiveness of the implemented controls.
- For example, measures indicate if the AI application allows human operators to evaluate AI model outputs and intervene in AI model-initiated actions when necessary. Reviews, tests, or audits are completed by the organization to measure the effectiveness of the implemented controls.
- Managed: Examine evidence that a written or undocumented risk treatment process exists, as defined in the HITRUST scoring rubric. Determine the frequency that the risk treatment process was applied to issues identified for each evaluative element within the requirement statement.
- Policy: Examine policies related to each evaluative element within the requirement statement. Validate the existence of a written or undocumented policy as defined in the HITRUST scoring rubric.
- Placement of this requirement in the HITRUST CSF [?]
- Assessment domain: 12 Audit Logging & Monitoring
- Control category: 09.0 – Communications and Operations Management
- Control reference: 09.ab – Monitoring System Use
- Specific to which parts of the overall AI system? [?]
-
- AI application layer:
- Application AI safety and security systems
- Application AI safety and security systems
- AI application layer:
- Discussed in which authoritative AI security sources? [?]
-
- ISO/IEC 22989:2022: Information technology — Artificial intelligence — Artificial intelligence concepts and terminology
2022, © International Standards Organization (ISO)/International Electrotechnical Commission (IEC)- Where:
- 5. AI Concepts > 5.15 Trustworthiness > 5.15.5. AI controllability
- 5. AI Concepts > 5.15 Trustworthiness > 5.15.5. AI controllability
- Where:
- ISO/IEC 38507:2022- Governance implications of the use of artificial intelligence by organizations
2022, © International Standards Organization (ISO)/International Electrotechnical Commission (IEC)- Where:
- 5. Overview of AI and AI systems > 5.1. General
- 6. Policies to address the use of AI > 6.2. Governance oversight of AI
- Where:
- OWASP 2023 Top 10 for LLM Applications
Oct. 2023, © The OWASP Foundation- Where:
- LLM01: Prompt injection > Prevention and mitigation strategies > Bullet #2
- LLM03: Training data poisoning > Prevention and mitigation strategies > Bullet #7
- LLM07: Insecure plugin design > Prevention and mitigation strategies > Bullet #6
- LLM08: Excessive agency > Prevention and mitigation strategies > Bullet #6
- LLM09: Overreliance > Prevention and mitigation strategies > Bullet #1
- Where:
- OWASP 2025 Top 10 for LLM Applications
2025, © The OWASP Foundation- Where:
- LLM01: Prompt Injection > Prevention and Mitigation Strategies > Bullet #5
- LLM06: Excessive Agency > Prevention and Mitigation Strategies > Bullet #6
- LLM09: Misinformation > Prevention and Mitigation Strategies > Bullet #3
- Where:
- OWASP AI Exchange
2024, © The OWASP Foundation- Where:
- Deploying AI Systems Securely: Best Practices for Deploying Secure and Resilient AI Systems
Apr 2024, National Security Agency (NSA)- Where:
- Continuously protect the AI system > Validate the AI system before and during use > Bullet 5
- Continuously protect the AI system > Validate the AI system before and during use > Bullet 8 > Sub-bullet 1
- Where:
- Generative AI framework for HM Government
2023, Central Digital and Data Office, UK Government- Where:
- Building generative AI solutions > Building the solution > Getting reliable results > Bullet 9
- Building generative AI solutions > Building the solution > Getting reliable results > Bullet 10
- Using generative AI safely and responsibly > Ethics > Accountability and responsibility > Practical recommendations > Bullet 6
- Using generative AI safely and responsibly > Ethics > Accountability and responsibility > Practical recommendations > Bullet 5
- Using generative AI safely and responsibly > Ethics > Maintaining appropriate human involvement in automated processes > Bullet 3
- Using generative AI safely and responsibly > Ethics > Maintaining appropriate human involvement in automated processes > Bullet 5
- Building generative AI solutions > Building the solution > Data management > Practical recommendations > Bullet 2
- Where:
- ISO/IEC TR 24028:2020: Information technology — Artificial intelligence — Overview of trustworthiness in artificial intelligence
2020, © International Standards Organization (ISO)/International Electrotechnical Commission (IEC)- Where:
- 9. Mitigation measures > 9.4. Controllability > 9.4.2. Human-in-the-loop control points
- 9. Mitigation measures > 9.4. Controllability > 9.4.2. Human-in-the-loop control points
- Where:
- ISO/IEC 22989:2022: Information technology — Artificial intelligence — Artificial intelligence concepts and terminology
- Discussed in which commercial AI security sources? [?]
- Databricks AI Security Framework
Sept. 2024, © Databricks- Where:
- DASF 29: Build MLOps workflows with human-in-the-loop (HILP) with permissions, versions and approvals to promote models to production
- DASF 29: Build MLOps workflows with human-in-the-loop (HILP) with permissions, versions and approvals to promote models to production
- Where:
- Snowflake AI Security Framework
2024, © Snowflake Inc.- Where:
- Prompt injection > Mitigations > Human-in-the-loop systems
- Indirect prompt injection > Mitigations > Human-in-the-loop systems
- Where:
- Databricks AI Security Framework
- Control functions against which AI security threats? [?]
-
- Control function: Corrective
- Control function: Preventative
- Additional information
-
- Q: When will this requirement included in an assessment? [?]
- This requirement will always be added to HITRUST assessments which include the
Security for AI systems
regulatory factor. - No other assessment tailoring factors affect this requirement.
- This requirement will always be added to HITRUST assessments which include the
- Q: When will this requirement included in an assessment? [?]