AICM AtlasCSA AI Controls Matrix
IPY · Interoperability & Portability
IPY-02Cloud & AI Related

Application Interface Availability

Specification

Provide application interface(s) to AICs so that they programmatically retrieve their data to enable interoperability and portability.

Threat coverage

Model manipulation
Data poisoning
Sensitive data disclosure
Model theft
Model/Service Failure
Insecure supply chain
Insecure apps/plugins
Denial of Service
Loss of governance

Architectural relevance

Physical infrastructure
Network
Compute
Storage
Application
Data

Lifecycle

Preparation

Data storage

Development

Not applicable

Evaluation

Not applicable

Deployment

Orchestration, AI Services supply chain, AI applications

Delivery

Operations, Maintenance, Continuous monitoring

Retirement

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 Model Provider-Orchestrated Service Provider (Shared MP-OSP)

The MP and OSP 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

[All Actors]
1. API Design & Provision: a) Develop/maintain robust, documented APIs for AIC data retrieval. b) Ensure APIs cover relevant AIC data scopes. c) Follow API design best practices. d) Follow applicable industry standards for interoperability. 

2. Security & Access Control: a) Implement secure authentication/authorization for AIC-specific data access. b) Ensure data segregation. 

3. Performance & Reliability: a) Design for performance/scalability. b) Monitor availability/latency/errors. c) Implement rate limiting. 

4. Documentation & Support: a) Provide comprehensive, current API documentation. b) Offer support channels. c) Communicate API changes/versioning proactively.

Auditing guidelines

1. Verify that the CSP provides complete, up-to-date API documentation covering integration, data handling, and usage. Confirm that the CSP ensures reliable API operation through uptime monitoring, incident response procedures, and customer notifications during disruptions.

2. Ensure that the APIs cover all necessary functionalities required by AI Customers to retrieve their data fully.

3. Verify that there are adequate security controls in place for accessing and using the APIs, including but not limited to authentication, authorization, and encryption. 

4. Verify that the policy governing API availability and usage is reviewed and updated on a periodic basis by the respective owner.

Standards mappings

ISO 42001Partial Gap
42001: B.8.2
Addendum

AICM ensures that interfaces remain available for data interactions. ISO 42001 focuses on transparency, ensuring users receive relevant system information.

EU AI ActFull Gap
No Mapping
Addendum

The EU AI Act does not cover the IPY-02 topic, "Provide application interface(s) to AICs so that they programmatically retrieve their data to enable interoperability and portability."

NIST AI 600-1Full Gap
No Mapping
Addendum

The NIST AI 600-1 framework does not establish the requirement of providing application interface(s) to enable interoperability and portability.

BSI AIC4Partial Gap
C4 PC-02
C5 PI-01
Addendum

No C4 control speaks to IPY0-02 topic of providing an interface for this access.

AI-CAIQ questions (1)

IPY-02.1

Are application interface(s) to AICs provided so that they programmatically retrieve their data to enable interoperability and portability?