C5 (Germany)
C5: Operations

C5 (Germany) C5-OPS-23: Managing Vulnerabilities, Malfunctions and Errors - System Hardening

Harden production system components to generally accepted industry standards, document the hardening requirements for each component, verify immutable images against those requirements when the images are created, and retain configuration and log files evidencing their continuous availability.

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

What else in your programme already covers this

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

PCI DSS 4.0 · 7 controls

  • 1.2.1 1.2.1 Ruleset configuration standards for NSCs
  • 1.2.5 1.2.5 Allowed services, protocols and ports justified
  • 11.5.2 11.5.2 Change detection on critical files
  • 2.1.1 2.1.1 Requirement 2 policies and procedures governed
  • 2.2.1 2.2.1 System configuration standards maintained
  • 2.2.4 2.2.4 Only necessary functionality enabled
  • 2.2.6 2.2.6 System security parameters configured against misuse

FedRAMP High · 6 controls

  • CM-2 Baseline Configuration
  • CM-6 Configuration Settings
  • CM-6(1) Automated Management, Application, and Verification
  • CM-7 Least Functionality
  • CM-7(1) Periodic Review
  • PL-10 Baseline Selection. Select a control baseline for the system

FedRAMP Moderate · 6 controls

  • CM-2 Baseline Configuration
  • CM-6 Configuration Settings
  • CM-6(1) Automated Management, Application, and Verification
  • CM-7 Least Functionality
  • CM-7(1) Periodic Review
  • PL-10 Baseline Selection. Select a control baseline for the system
  • ASBv3-GS-5 Define and implement security posture management strategy
  • ASBv3-NS-8 Detect and disable insecure services and protocols
  • ASBv3-PV-1 Define and establish secure configurations
  • ASBv3-PV-3 Define and establish secure configurations for compute resources
  • PV-2 Audit and enforce secure configurations

NIST SP 800-161 Rev 1 · 5 controls

ACSC Essential Eight · 4 controls

  • E8-MACRO-ML1 Configure Microsoft Office Macro Settings (ML1)
  • E8-PATCHOS-ML3 Patch Operating Systems (ML3)
  • E8-UAH-ML1 User Application Hardening - Maturity Level 1
  • E8-UAH-ML2 User Application Hardening - Maturity Level 2
  • ASD37-01 Application control (Essential)
  • ASD37-04 User application hardening (Essential)
  • ASD37-10 Server application hardening (Very Good)
  • ASD37-11 Operating system hardening (Very Good)

CIS Controls v8 · 4 controls

  • CIS-16.7 Use Standard Hardening Configuration Templates for Application Infrastructure
  • CIS-4.1 Establish and Maintain a Secure Configuration Process
  • CIS-4.6 Securely Manage Enterprise Assets and Software
  • CIS-4.8 Uninstall or Disable Unnecessary Services on Enterprise Assets and Software

CMMC 2.0 · 4 controls

NIST SP 800-53 Rev 5 · 4 controls

UK Cyber Essentials · 4 controls

  • CE-FW.2 Change Default Firewall Passwords
  • CE-SC.1 Remove or Disable Unused Software
  • CE-SC.2 Change Default Passwords on Devices and Software
  • CE-SC.3 Disable Auto-Run Features

NIST SP 800-171 Rev 3 · 3 controls

NIST SP 800-172 · 3 controls

  • 3.14.1e Verify Integrity of Security Critical Software and Firmware
  • 3.14.4e Refresh Systems and Components from a Trusted Baseline
  • 3.4.2e Automated Detection and Remediation of Unauthorized Software
  • ANSSI-HYG-14 Apply a Minimum Security Level Across the Whole Estate
  • ANSSI-HYG-16 Use a Centralised Management Tool to Standardise Security Policies
  • SEC01-BP06 Automate deployment of standard security controls
  • SEC06-BP02 Provision compute from hardened images

NIST SP 800-218 · 2 controls

  • CBPR-PR-30 Specific proportional safeguards in place
  • AUCDR-IS-2 Secure the network and systems within the data environment

DORA · 1 control

ISO 27001:2022 · 1 control

  • 8.9 Configuration management

ISO 27002:2022 · 1 control

  • 8.9 Configuration management

NIS2 Directive · 1 control

  • Art.21.2.g Basic cyber hygiene practices and cybersecurity training

SOC 2 · 1 control

  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities

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: Operations

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

C5 (Germany) C5-OPS-23 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 78 it maps to, and the evidence behind each claim, over MCP and REST.