AICM AtlasCSA AI Controls Matrix
AIS · Application & Interface Security
AIS-02Cloud & AI Related

Application Security Baseline Requirements

Specification

Establish, document and maintain baseline requirements for securing applications."

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, Data curation, Data collection

Development

Design, Guardrails, Supply Chain, Training

Evaluation

Validation/Red Teaming, Evaluation, Re-evaluation

Deployment

AI Services supply chain, AI applications

Delivery

Continuous monitoring, Continuous improvement, Maintenance, Operations

Retirement

Archiving

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

[All Actors]
All actors in the AI supply chain must establish and adhere to security baselines that address the unique risks and vulnerabilities of AI systems. 
1. Define AI-Specific Security Baselines: Establish baseline security requirements that address the unique challenges and risks associated with AI systems. 

2. Document and Maintain Baselines: Document security baselines in a centralized repository with version control to ensure consistency, clarity, and ease of updating.

3. Align with Best Practices and Standards: Ensure that security baselines align with recognized industry best practices and relevant security standards, including those specific to AI.

4. Regularly Review and Update: Establish a process for regularly reviewing and updating security baselines to adapt to the evolving threat landscape and emerging technologies.

5. Communicate Baselines: Effectively communicate security baselines to relevant stakeholders to ensure alignment and understanding.

Auditing guidelines

1. Examine policy and procedures for adequacy and effectiveness.

2. Determine if security baseline requirements of respective applications are clearly defined.

3. Examine the process to determine the baseline security for AI-enabling services.

(The above are from CCM and apply here as well.)

Standards mappings

ISO 42001Partial Gap
42001: 6.1.2
42001: B.6.2.2
42001: B.7.2
27001:6.1.2
27001:6.1.3
27001: A.8.26
Addendum

Explicitly require the definition, documentation, and periodic maintenance of baseline application security requirements.

EU AI ActNo Gap
Article 11
Article 15 (1)
Article 53 and Annex XI
Article 55
Addendum

N/A

NIST AI 600-1Partial Gap
GV-6.1-004
GV-6.1-005
Addendum

Define application-specific security baseline frameworks, including authentication, encryption, and access control requirements. Establish a baseline validation and compliance tracking mechanism. Enhance policy enforcement mechanisms to explicitly define application security requirements for AI-related technologies.

BSI AIC4No Gap
DEV-01
DEV-03
OPS-04
OPS-06
OPS-10
OPS-11
OPS-18
OPS-23
PS-01
Addendum

N/A

AI-CAIQ questions (1)

AIS-02.1

Are baseline requirements for securing applications established, documented, and maintained?