Secure Interoperability and Portability Management
Specification
Implement cryptographically secure and standardized network protocols for the management, import and export of data, according to industry standards.
Threat coverage
Architectural relevance
Lifecycle
Data collection, Data curation, Data storage
Training
Evaluation, Validation/Red Teaming, Re-evaluation
Orchestration, AI Services supply chain, AI applications
Operations, Maintenance, Continuous monitoring, Continuous improvement
Data deletion
Ownership / SSRM
PI
Shared Cloud Service Provider-Model Provider (Shared CSP-MP)
The CSP and MP are jointly 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 in the context of the services or products they develop and offer.
Model
Owned by the Model Provider (MP)
The model provider (MP) designs, develops, and implements the control as part of their services or products to mitigate security, privacy, or compliance risks associated with the Large Language Model (LLM). Model Providers are entities that develop, train, and distribute foundational and fine-tuned AI models for various applications. They create the underlying AI capabilities that other actors build upon. Model Providers are responsible for model architecture, training methodologies, performance characteristics, and documentation of capabilities and limitations. They operate at the foundation layer of the AI stack and may provide direct API access to their models. Examples: OpenAI (GPT, DALL-E, Whisper), Anthropic(Claude), Google(Gemini), Meta(Llama), as well as any customized model.
Orchestrated
Shared Orchestrated Service Provider-Application Provider (Shared OSP-AP)
The OSP and AP are jointly 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 in the context of the services or products they develop and offer.
Application
Owned by the Application Provider (AP)
The Application Provider (AP) is responsible 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 in the context of the services or products they develop and offer. The AP is responsible and accountable for the implementation of the control within its own infrastructure/environment. If the control has downstream implications on the users/customers, the AP is responsible for enabling the customer and/or upstream partner in the implementation/configuration of the control within their risk management approach. The AP is accountable for carrying out the due diligence on its upstream providers (e.g MPs, Orchestrated Services) to verify that they implement the control as it relates to the service/product develop and offered by the AP. These providers build and offer end-user applications that leverage generative AI models for specific tasks such as content creation, chatbots, code generation, and enterprise automation. These applications are often delivered as software-as-a-service (SaaS) solutions. These providers focus on user interfaces, application logic, domain-specific functionality, and overall user experience rather than underlying model development. Example: OpenAI (GPTs,Assistants), Zapier, CustomGPT, Microsoft Copilot (integrated into Office products), Jasper (AI-driven content generation), Notion AI (AI-enhanced productivity tools), Adobe Firefly (AI-generated media), and AI-powered customer service solutions like Amazon Rufus, as well as any organization that develops its AI-based application internally.
Implementation guidelines
Auditing guidelines
1. Examine the adequacy of the policy to ensure to if they contain comprehensive details regarding the implementation of cryptographically secure and standardized network protocols within the CSP environment. 2. Review that the Interoperability and Portability Policy has been updated regularly to adapt to evolving industry standards and emerging threats. 3. Review that the communication channels are adequate to communicate about the policy to all relevant parties involved. 4. Examine the mechanisms used for the monitoring and enforcement of the policy. Ensure that there are clear procedures for detecting and addressing non-compliance.
Standards mappings
42001: Annex A 42001: A.7 42001: B.7.3
Addendum
ISO/IEC 42001 highlights the need for standardized AI management practices but lacks specific guidance on implementing network protocols for data management. AI CM V0.9 bridges this gap by recommending standardized cryptographic protocols to ensure consistency and interoperability in data handling.
No Mapping
Addendum
The EU AI Act does not cover the IPY-03 topic, "Implement cryptographically secure and standardized network protocols for the management, import, and export of data."
No Mapping
Addendum
The NIST AI 600-1 framework explicitly requires to consider, among others, data security factors (e.g., containment, protocols, data leakage) when tackling the mere question of AI systems' decommissioning and phasing out (see GV-1.7-002) (out of scope).
C4 SR-06 C5 PI-01 C5 CRY-02
Addendum
N/A
AI-CAIQ questions (1)
Are cryptographically secure and standardized network protocols implemented for the management, import, and export of data, according to industry standards?