# OPS-05 Protection Against Malware - Implementation

- Domain: OPS – Operations
- Since C5:2020: changed
- Web page: https://c5.patrickscheid.de/en/ops-05/

## Basic criterion

### OPS-05.01B

System components under the cloud service provider's responsibility that are used to operate the cloud service in the production environment are configured with malware protection according to the policies and procedures.

**Supplementary information (on 01B, 02B, 02AS):**

Protection against malicious programmes can be implemented by operating system-specific protection mechanisms or explicit protection programmes (e.g. for signature- and behaviour-based detection and removal of malicious programmes).

If the cloud service provider operates malware protected containers or virtual machines to provide the cloud service, the malware protection should include container-specific measures. This can include, for example, monitoring the container images and the container runtime, and due to the frequent start and stop of the containers, real-time scans and -monitoring processes.

**Supplementary information:**

For end-devices used by the personnel of the cloud service provider, the applicability of this subcriterion is determined based on the risk assessment performed according to AM-08.

### OPS-05.02B

If protection programmes are set up with signature or behaviour-based malware detection and removal, these protection programmes are regularly updated with the latest malware definitions when they are available, at least on a daily basis.

### OPS-05.03B

The cloud service provider creates regular reports on the checks performed by the operated protection programmes, which are reviewed and analysed by authorised individuals, bodies or committees.

## Additional criterion

### OPS-05.02AS (additional, sharpens 02B)

If protection programmes are set up with signature and behaviour-based malware detection and removal, these protection programmes are regularly updated with the latest malware definitions when they are available, at the highest frequency that the vendor(s) offer(s) where applicable.

### OPS-05.01AC (additional, complementing)

Policies and procedures describe the technical measures taken to securely configure and monitor the management console (both the customer's self-service and the service provider's cloud administration) to protect it from malware.

### OPS-05.02AC (additional, complementing)

The configuration of the protection mechanisms is monitored automatically.

### OPS-05.03AC (additional, complementing)

Deviations from the specifications are automatically reported to the cloud service provider's subject matter experts so that they can be immediately assessed and the necessary measures taken.

## Complementary customer criteria

Cloud service customers ensure with suitable controls that the layers of the cloud service which they are responsible for have security products in place to detect and remove malware.

## Changes since C5:2020

From BSI's C5:2026 changelog.

**Basic criterion:**

Modified requirement regarding the frequency of signature updates to whenever such updates are available, but at least daily.

Moved requirement regarding the creation of regular reports from the former OPS-04 additional criterion to this basic criterion.

**Additional criterion:**

Removed original additional criterion of former OPS-05.

Added requirements from the former OPS-04 additional criterion regarding technical measures for configuring and monitoring the management console, and for updates being applied at the highest frequency offered by the vendor.

---

Source: BSI C5:2026, machine-readable edition v1.0.1, © Federal Office for Information Security (BSI) 2026, reproduced unchanged under CC BY-ND 4.0 (https://creativecommons.org/licenses/by-nd/4.0/). Change notes: BSI C5:2026 Changelog, © BSI 2026, CC BY-ND 4.0. Unofficial presentation, not affiliated with BSI.