Limitation of Production Data Use
Specification
Obtain authorization from data owners, and manage associated risk before replicating or using production data in non-production environments.
Threat coverage
Architectural relevance
Lifecycle
Team and expertise
Design, Guardrails
Evaluation, Validation/Red Teaming
Orchestration, AI Services supply chain
Operations, Maintenance, Continuous monitoring
Data deletion, Archiving
Ownership / SSRM
PI
Owned by the Customer (AIC)
The Customer (AIC) is responsible and accountable for the design, development, implementation, and enforcement of the control to mitigate security, privacy, or compliance risks associated with Large Language Model (LLM)/GenAI technologies services or products they consume.
Model
Owned by the Customer (AIC)
The Customer (AIC) is responsible and accountable for the design, development, implementation, and enforcement of the control to mitigate security, privacy, or compliance risks associated with Large Language Model (LLM)/GenAI technologies services or products they consume.
Orchestrated
Owned by the Customer (AIC)
The Customer (AIC) is responsible and accountable for the design, development, implementation, and enforcement of the control to mitigate security, privacy, or compliance risks associated with Large Language Model (LLM)/GenAI technologies services or products they consume.
Application
Owned by the Customer (AIC)
The Customer (AIC) is responsible and accountable for the design, development, implementation, and enforcement of the control to mitigate security, privacy, or compliance risks associated with Large Language Model (LLM)/GenAI technologies services or products they consume.
Implementation guidelines
Auditing guidelines
1. Verify that infrastructure-level policies and technical safeguards are in place to control the use of production tenant data in test, dev, or benchmarking environments. 2. Verify if infrastructure users (e.g., internal teams or client teams) obtain approval before replicating production workloads or datasets in non-production environments. 3. Verify if mechanisms (e.g., data masking, encryption) are in place to anonymize and secure data during infrastructure provisioning or testing. 4. Verify if any deviations from the infrastructure provider’s standard for handling production data are documented and approved. 5. Verify if infrastructure governance procedures are periodically updated to reflect regulatory, contractual, or service-level agreement changes. 6. Verify if internal teams are trained on policies and practices for securing client or production data when testing or provisioning infrastructure services.
Standards mappings
42001: A.6.1.2 Objectives for responsible development of AI system 42001: A.6.1.3 Processes for responsible design and development of AI systems 42001: 6.3.2 – AI control planning must consider environment sensitivity. 42001: A.7.2 Data for development and enhancement of AI system. 42001: A.7.4 Quality of data for AI systems 42001: A.2.3 Alignment with other organizational policies 27001: A.8.31 - Separation of development test and production environments 27001: A.8.33 - Test information 27001: A.8.27 – Segregation of environments. 27001: A.5.11 – Protection against misuse of systems. 27002: 8.31 Separation of development test and production environments 27002: 8.33 Test Information 27002: 8.28 – Environment segregation implementation. 27002: 5.9 – Protection against misuse or unintentional data disclosure.
Addendum
N/A
Article 10 Article 16 Article 17 Article 28 Article 29
Addendum
The EU AI Act covers data governance and risk management broadly but doesn't specifically address environment-specific risk management and non-production environment data usage is not specifically addressed.
No Mapping
Addendum
NIST AI 600-1 does not cover these DSP-15 topics.
BC-06
Addendum
For such topics, there is the GDPR in the EU. The GDPR is translated to local regulations for every country in the EU. This is an explicit target of GDPR.
AI-CAIQ questions (1)
Are authorizations obtained from data owners and associated risks managed before replicating or using production data in non-production environments?