AID-M-007: AI Use Case & Safety Boundary Modeling

Version 1.20261015 · Family — navigation only

Define a signed, machine-readable safety boundary for an AI use case, determine which technically testable safety and conformance dimensions apply to its real architecture and impact paths, and evaluate the exact release candidate before promotion.

Scope boundary

Owns intended-use and forbidden-action safety-boundary modeling, applicability classification, deterministic release conformance, and conditional statistical fairness evaluation. Adaptive adversarial security benchmarking and model-card publication remain separate controls.

AID-M-004: AID-M-007 defines acceptable use, forbidden outcomes, applicable safety dimensions, and release criteria; AID-M-004 identifies adversarial threats and prioritizes technical security risk across the architecture. A safety policy states what must hold, while a threat model explains how assets and trust boundaries may be attacked or fail.

AID-M-008: AID-M-007 owns the signed safety boundary and its deterministic or fairness-specific release checks; AID-M-008 owns repeatable adversarial agent security benchmarking. Passing declared conformance cases does not establish adaptive bypass resistance, and an adversarial benchmark does not define the authoritative use-case boundary.

Sub-techniques

Threat mappings

MITRE ATLAS

MAESTRO

OWASP LLM Top 10 2026

OWASP ML Top 10 2023

OWASP Top 10 for Agentic Applications 2026

NIST Adversarial Machine Learning 2025

Cisco Integrated AI Security and Safety Framework

Google Secure AI Framework 2.0 - Risks

Databricks AI Security Framework 3.0

AID-M-007: AI Use Case & Safety Boundary Modeling | AIDEFEND

Loading interactive view…

A Practical Knowledge Base for AI Security Defenses

Version