How to meet it
OWASP AISVS v1.01
AI-Assisted Secure Coding (Appendix C) · Adversarial AI Detection in Inbound Contributions
Map detections to MITRE ATT&CK and ATLAS
Verify that detection rules are tagged to MITRE ATT&CK (T1195 Supply Chain Compromise and CI/CD-relevant sub-techniques) and to MITRE ATLAS techniques, maintained for the inbound contribution analysis use case, and reviewed against current threat intelligence.
OWASP AISVS v1.01, requirement AC.13.4
In plain English
Tag your detection rules with the matching MITRE ATT&CK and MITRE ATLAS techniques, keep them current for inbound contribution analysis, and review them against threat intelligence.
What good looks like
- Rules are mapped to ATT&CK (including T1195) and ATLAS techniques.
- They are maintained for this use case.
- Reviews against threat intelligence are recorded.
How teams usually do it
- Technique tags in your rule repository.
Evidence an auditor would accept
- Tagged rules and review records.
Common mistakes
- Tagging once and never revisiting.
Not sure which requirements apply to your system? Take the assessment.
Requirement text from the OWASP AI Security Verification Standard, licensed under CC BY-SA 4.0. This guidance is shared under the same licence.