FIELD GUIDE

Red-Teaming AI Responsibly: Permission, Scope and Safe Reporting

Safety testing becomes a liability when testers use genuine personal data, access systems without authorization or mistake a public interface for permission to attack a vendor.

Safety testing becomes a liability when testers use genuine personal data, access systems without authorization or mistake a public interface for permission to attack a vendor.

Agree to rules before testing

Document written authorization, assets in scope, testing window, rate limits, prohibited actions, data-handling restrictions and emergency contact. Include model, retrieval, browser and integrated tool boundaries where relevant. A vulnerability disclosure program may permit some testing and prohibit other methods; read its actual terms.

Design realistic but controlled cases

Challenge instruction hierarchy, unsafe output, sensitive data exposure, identity and tool permissions with synthetic or consented fixtures. For safety evaluation, avoid creating unnecessary harmful materials or sharing detailed exploitation traces publicly. Include ordinary benign prompts so testers can assess false positives as well as attack success.

Record evidence precisely

Preserve model configuration, exact prompt class, test input version, boundary conditions and observed result. Redact secrets and affected user information in reports. A single dramatic jailbreak screenshot is not a prevalence estimate. Use reproducibility and severity criteria rather than chasing sensational outputs.

Coordinate disclosure and fixes

Provide the vendor a secure reporting channel, reasonable response window and clear reproduction steps. CISA’s federal vulnerability disclosure directive provides one governance example; it is not a global authorization to probe any platform. Track retest outcomes and regressions.

Example

A university evaluates its own campus knowledge assistant with authorized mock records. Testers find that an injected page can redirect answers to an external URL. The team disables the vulnerable retrieval path and retests, without sending real student records to a third-party domain.

Sources & Further Reading

CONTINUE EXPLORINGExplore related files ↗