Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 CCM-IVS-04: OS Hardening and Base Controls

What else in your programme already covers this

This control maps to 66 controls across 25 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 · 8 controls

1.2.1 1.2.1 Ruleset configuration standards for NSCs
1.2.5 1.2.5 Allowed services, protocols and ports justified
1.2.6 1.2.6 Security features for insecure services in use
2.2.1 2.2.1 System configuration standards maintained
2.2.2 2.2.2 Vendor default accounts managed
2.2.4 2.2.4 Only necessary functionality enabled
2.2.5 2.2.5 Insecure services, protocols or daemons secured
2.2.6 2.2.6 System security parameters configured against misuse

CIS Controls v8 · 5 controls

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

ASD Strategies to Mitigate Cyber Security Incidents · 4 controls

ASD37-04 User application hardening (Essential)
ASD37-09 OS generic exploit mitigation (Excellent)
ASD37-10 Server application hardening (Very Good)
ASD37-11 Operating system hardening (Very Good)

CMMC 2.0 · 4 controls

CM.L2-3.4.1 System Baselining
CM.L2-3.4.2 Security Configuration Enforcement
CM.L2-3.4.6 Least Functionality
CM.L2-3.4.7 Nonessential Functionality

CNCF Security Technical Advisory Group (TAG) · 4 controls

CNCF-4C-CONTAINER Container Layer Security
CNCF-DIST-IMGHARDEN Image Hardening
CNCF-DIST-MANIFESTHARDEN Container Application Manifest Hardening
CNCF-RT-COMPUTE Runtime Compute Security (Orchestration, Hosts, Containers)

FedRAMP High · 4 controls

CM-2 Baseline Configuration
CM-6 Configuration Settings
CM-7 Least Functionality
CM-7(1) Periodic Review

FedRAMP Moderate · 4 controls

CM-2 Baseline Configuration
CM-6 Configuration Settings
CM-7 Least Functionality
CM-7(1) Periodic Review

NIST SP 800-53 Rev 5 · 4 controls

NIST800-CM-2 CM-2 Baseline Configuration
NIST800-CM-6 CM-6 Configuration Settings
NIST800-CM-7 CM-7 Least Functionality
NIST800-SC-41 SC-41 Port and I/O Device Access

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

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 3 controls

ANSSI-HYG-12 Change Default Authentication Elements on Equipment and Services
ANSSI-HYG-14 Apply a Minimum Security Level Across the Whole Estate
ANSSI-HYG-16 Use a Centralised Management Tool to Standardise Security Policies

Azure Security Benchmark · 3 controls

ASBv3-PV-1 Define and establish secure configurations
ASBv3-PV-3 Define and establish secure configurations for compute resources
ASBv3-PV-4 Audit and enforce secure configurations for compute resources

NIST SP 800-218 · 3 controls

SP800-218-PO.5.1 Secure Development Environment Implementation
SP800-218-PO.5.2 Harden Development Endpoints
SP800-218-PW.6.1 Configure Compilation and Build Processes Securely

AWS Well-Architected Security Pillar · 2 controls

SEC06-BP02 Provision compute from hardened images
SEC06-BP05 Automate compute protection

DORA · 2 controls

DORA-Art.7 ICT systems, protocols and tools
DORA-Art.9 Protection and prevention

NIST SP 800-171 Rev 3 · 2 controls

03.04.02 Configuration Settings
03.04.06 Least Functionality

ACSC Essential Eight · 1 control

E8-UAH-ML2 User Application Hardening - Maturity Level 2

Australia Consumer Data Right - Banking (CDR) · 1 control

AUCDR-IS-2 Secure the network and systems within the data environment

C5 (Germany) · 1 control

C5-OPS-23 Managing Vulnerabilities, Malfunctions and Errors - System Hardening

NIS2 Directive · 1 control

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

NIST Cybersecurity Framework 2.0 · 1 control

NIST-CSF-PR.PS-01 Configuration management practices are established and applied

NIST SP 800-161 Rev 1 · 1 control

161R1-CM-6 Configuration Settings

NIST SP 800-172 · 1 control

3.4.2e Automated Detection and Remediation of Unauthorized Software

SOC 2 · 1 control

SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)

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.

You are reading one control. How much of Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 have you already done?

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 CCM-IVS-04 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 140 of 197 Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 controls already carry evidence.

If you hold NIST SP 800-53 Rev 571.1% covered · 57 gaps If you hold FedRAMP Moderate60.4% covered · 78 gaps If you hold PCI DSS 4.060.4% covered · 78 gaps If you hold C5 (Germany)58.4% covered · 82 gaps If you hold ISO 27001:202256.3% covered · 86 gaps If you hold ISO 27002:202256.3% covered · 86 gaps

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. 12 were rejected on the NIST SP 800-53 Rev 5 pair alone.

See the released pairs, $299 each Browse the graph free