C5 (Germany)
C5: Product Safety and Security

C5 (Germany) C5-PSS-11: Images for Virtual Machines and Containers

Where customers run virtual machines or containers, let the customer restrict which images its users may launch, inform the customer of what changed between versions of any images the provider supplies, and harden those provider supplied images to generally accepted industry standards.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 48 controls across 20 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

FedRAMP High · 6 controls

  • CM-11 User-Installed Software
  • CM-2 Baseline Configuration
  • CM-6 Configuration Settings
  • CM-7(5) Authorized Software Allow-by-Exception
  • SI-7 Software, Firmware, and Information Integrity
  • SR-11(2) Component Authenticity | Configuration Control for Component Service and Repair (SR-11(2))

FedRAMP Moderate · 6 controls

  • CM-11 User-Installed Software
  • CM-2 Baseline Configuration
  • CM-6 Configuration Settings
  • CM-7(5) Authorized Software Allow-by-Exception
  • SI-7 Software, Firmware, and Information Integrity
  • SR-11(2) Component Authenticity | Configuration Control for Component Service and Repair (SR-11(2))
  • AM-2 Use only approved services
  • ASBv3-AM-5 Use only approved applications in virtual machine
  • ASBv3-PV-3 Define and establish secure configurations for compute resources
  • ASBv3-PV-4 Audit and enforce secure configurations for compute resources

CMMC 2.0 · 4 controls

  • ASD37-10 Server application hardening (Very Good)
  • ASD37-11 Operating system hardening (Very Good)
  • ASD37-36 System recovery capabilities (Very Good)

CIS Controls v8 · 3 controls

  • CIS-16.7 Use Standard Hardening Configuration Templates for Application Infrastructure
  • CIS-2.3 Address Unauthorized Software
  • CIS-4.1 Establish and Maintain a Secure Configuration Process

NIST SP 800-218 · 3 controls

ISO 27001:2022 · 2 controls

  • 8.19 Installation of software on operational systems
  • 8.9 Configuration management

ISO 27002:2022 · 2 controls

  • 8.19 Installation of software on operational systems
  • 8.9 Configuration management

NIST SP 800-53 Rev 5 · 2 controls

SOC 2 · 2 controls

  • SOC2-CC6.8 CC6.8 Preventing and detecting unauthorised or malicious software
  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
  • E8-APP-ML1 Application Control (ML1)
  • ANSSI-HYG-14 Apply a Minimum Security Level Across the Whole Estate

ISO 27017:2015 · 1 control

  • 03.04.08 Authorized Software - Allow by Exception

PCI DSS 4.0 · 1 control

  • 2.2.1 2.2.1 System configuration standards maintained

UK Cyber Essentials · 1 control

  • CE-MP.4 Application Allowlisting (Alternative)

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in C5: Product Safety and Security

You are reading one control. How much of C5 (Germany) have you already done?

C5 (Germany) C5-PSS-11 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of C5 (Germany) your existing evidence covers. Hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 and 95 of 121 C5 (Germany) controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 pair alone.

Query this from an agent

The graph holds this control, the 48 it maps to, and the evidence behind each claim, over MCP and REST.