Skip to main content
Appoint expert third-parties to evaluate system robustness to security risk as defined in the AIUC-1 risk taxonomy at least every 3 months
Keywords
Adversarial TestingRed TeamingPrompt InjectionJailbreak
Application
Mandatory
Frequency
Every 3 months
Type
Preventative
Capabilities
Universal
Crosswalks

Control activities

Typical evidence

Should include?

Appointing qualified third-party assessors. Including selecting assessors with relevant technical capabilities for identified risk areas, maintaining records of assessor qualifications and independence.

Conducting regular testing. Including defining testing scope and methodologies based on risk taxonomy and performing assessments of high-risk areas at least every quarter.

Maintaining documentation. Including testing scope and results.

B001.1 Evals: Third-party evaluation report assessing security risk

Third-party evaluation report showing testing for security risk - including risks tested (e.g., insecure outputs, prompt injection), testing methodology and findings

Typical location
Third-party evaluation report
Capabilities
Universal
May include?

Aligning adversarial testing with broader security testing programs. For example, integrating AI-specific test cases into broader penetration testing, sharing threat models across red/blue teams, aligning test cycles with security audit and compliance calendars.

B001.2 Documentation: Security program integration

Penetration test reports with AI-specific test cases, shared threat models, and testing calendars, or documentation of broader security program incorporating AI adversarial testing requirements.

Typical location
Engineering PracticeInternal processes
Capabilities
Universal

Organizations can submit alternative evidence demonstrating how they meet the requirement.