TVM-02Cloud & AI Related

Malware and Malicious Instructions Protection Policy and Procedures

Specification

Establish, document, approve, communicate, apply, evaluate and maintain policies and procedures to protect against malware and malicious instructions. Review and update the policies and procedures at least annually or upon significant changes.

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, Resource provisioning

Development

Training

Evaluation

Re-evaluation

Deployment

Orchestration, AI Services supply chain, AI applications

Delivery

Operations, Maintenance, Continuous monitoring, Continuous improvement

Retirement

Archiving, Data deletion, Model disposal

Ownership / SSRM

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

Shared Application Provider-AI Customer (Shared AP-AIC)

The AP and AIC both share responsibility and accountability 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 offer and consume.

Implementation guidelines

[All Actors]
1. Establish and maintain an anti-malware policy that covers prevention, detection, response and annual review.

2. Implement continuous threat identification through automated scanning and threat-intelligence feeds.

3. Integrate real-time malware detection tools in development and production environments (source, container images, model artefacts, APIs).

4. Classify detected malware or malicious instructions by severity, exploitability and potential business impact; prioritise remediation accordingly.

5. Keep threat-intelligence sources and detection signatures up to date, and align classification criteria with the organisation’s risk-management framework.

Auditing guidelines

1. Verify that the Cloud Service Provider (CSP) has established and documented policies and procedures in the domain of Malware Protection that—by defining organizational and technical measures to prevent, detect, examine and remove malicious codes from systems—aim at leading efforts to protect the latter against malware attacks. Ensure that the policies are documented in detail, covering scope, objectives, roles and responsibilities.

2. Inspect whether the above-mentioned policies and procedures are compliant with relevant regulatory requirements, industry best practices and the specific threat scenarios to which the organization is potentially exposed.

3. Verify that the above-mentioned policies and procedures have been formally approved by authorized parties (e.g., management sign-off).

4. Verify that the above-mentioned policies and procedures (in both their original and subsequent versions) have been adequately communicated by authorized parties to all relevant stakeholders and that their content has been thoroughly comprehended by them.

5. Confirm that the policy is concretely and appropriately applied by involved parties in their day-to-day operations.

6. Verify that metrics and Key Performance Indicators (KPIs) have been established and are continuously monitored to evaluate the effectiveness of the above-mentioned policies and procedures and identify possible improvement areas.

7. Inspect whether the above-mentioned policies and procedures are periodically reviewed and updated (at least annually) by responsible parties.

8. Verify the CSP has a multi-layered malware protection strategy for its infrastructure, including scanning of internal systems, network intrusion detection, and protection for managed services.

9. Review the CSP’s documentation on the security measures they take to protect the cloud environment from malware.

Standards mappings

ISO 42001No Gap

5.2 AI Policy (42001)
A.5.2.1 Policies for information security (27001)
6.1.2 AI risk Assessment (42001)
A.8.7 Protection against Malware (27001)
7.5 Documented information (42001)
8.1 Operational planning and control (42001)
9.1 Monitoring
measurement .... (42001)
10.1 Continual improvement ... (42001)

Addendum

N/A

EU AI ActPartial Gap

Article 15 (4)
Article 15 (5)

Addendum

Explicitly mention the concept of malware protection. Establish a specific frequency for the review or evaluation and monitoring of the efficacy of technical measures.

NIST AI 600-1Full Gap

No Mapping

Addendum

NIST AI 600-1 should reference the TVM-02 guidance, "Establish, document, approve, communicate, apply, evaluate, and maintain policies and procedures to protect against malware on managed assets. Review and update the policies and procedures at least annually or upon significant changes."

BSI AIC4No Gap

C4 PC-02
C5 OPS-04

Addendum

N/A

AI-CAIQ questions (2)

TVM-02.1

Are policies and procedures to protect against malware and malicious instructions, established, documented, approved, communicated, applied, evaluated, and maintained?

TVM-02.2

Are malware and malicious instructions protection policies and procedures, reviewed and updated at least annually or upon significant changes?