Manage public release of technical details

Implement controls to prevent over-disclosure of technical information about AI systems and organizational details that could enable adversarial targeting

Keywords

Public Disclosure

Open-Source

External Threats

Application

Optional

Frequency

Every 12 months

Type

Preventative

Crosswalks

AML-M0000: Limit Public Release of Information

AML-M0001: Limit Model Artifact Release

LLM02:25 - Sensitive Information Disclosure

LLM07:25 - System Prompt Leakage

AIS-09: Output Validation

AIS-15: Prompt Differentiation

Control activities

Typical evidence

Documenting limitations on technical information release. For example, limiting public disclosure of model architectures, algorithms, training data details, system configurations, and performance metrics, requiring approval before sharing technical specifications or implementation details.

Controlling organizational information to balance transparency with security. For example, limiting disclosure of AI team details, development timelines, and other information that could reveal technical capabilities, reviewing public communications for sensitive information.

B003.1 Documentation: Technical information disclosure guidelines

Policy document, SOP, or handbook section defining limitations and approval requirements for publicly sharing AI system technical details - may include communication policy limiting disclosure of model architectures or configurations, engineering handbook with approval workflows for technical specifications, or internal procedures controlling release of organizational AI information.

AIUC-1 is built with industry leaders

"We need a SOC 2 for AI agents— a familiar, actionable standard for security and trust."

Phil Venables

Former CISO of Google Cloud

"Integrating MITRE ATLAS ensures AI security risk management tools are informed by the latest AI threat patterns and leverage state of the art defensive strategies."