FedRAMP Moderate CM-6: Configuration Settings

What else in your programme already covers this

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

UK Cyber Essentials · 7 controls

CE-FW.2 Change Default Firewall Passwords
CE-FW.7 Restrict Firewall Administrative Interface from the Internet
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
CE-SC.4 Authenticate Users Before Access
CE-SU.5 Firmware Updates

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 6 controls

CCM-AIS-02 Application Security Baseline Requirements
CCM-CCC-06 Change Management Baseline
CCM-IVS-04 OS Hardening and Base Controls
CCM-UEM-03 Compatibility
CCM-UEM-05 Endpoint Management
CCM-UEM-07 Operating Systems

PCI DSS 4.0 · 6 controls

1.2.1 NSC configuration standards defined
1.2.8 Configuration files secured and synchronised
2.2.1 Configuration standards are developed, implemented, and maintained to: • Cover all system components. • Address all known security vulnerabilities. • Be consistent with industry-accepted system hardening standards or vendor hardening recommendations. • Be updated
2.2.2 Vendor default accounts are managed as follows: • If the vendor default account(s) will be used, the default password is changed per Requirement 8.3.6. • If the vendor default account(s) will not be used,
2.2.4 Only necessary services enabled
2.2.6 System security parameters configured

C5 (Germany) · 5 controls

C5-AM-02 Acceptable Use and Safe Handling of Assets Policy
C5-OPS-16 Logging and Monitoring - Configuration
C5-OPS-23 Managing Vulnerabilities, Malfunctions and Errors - System Hardening
C5-PSS-11 Images for Virtual Machines and Containers
C5-SP-03 Exceptions from Existing Policies and Instructions

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.7 Manage Default Accounts on 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-03 Configure Microsoft Office macro settings (Essential)
ASD37-04 User application hardening (Essential)
ASD37-10 Server application hardening (Very Good)
ASD37-11 Operating system hardening (Very Good)

Azure Security Benchmark · 4 controls

ASBv3-NS-7 Simplify network security configuration
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-218 · 4 controls

SP800-218-PO.5.2 Harden Development Endpoints
SP800-218-PW.6.2 Configure Build Tool Security Features
SP800-218-PW.9.1 Configure Software to Have Secure Settings by Default
SP800-218-PW.9.2 Implement and Document Secure Defaults

ACSC Essential Eight · 3 controls

E8-MACRO-ML1 Configure Microsoft Office Macro Settings (ML1)
E8-UAH-ML1 User Application Hardening - Maturity Level 1
E8-UAH-ML2 User Application Hardening - Maturity Level 2

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

AWS Well-Architected Security Pillar · 2 controls

SEC01-BP06 Automate deployment of standard security controls
SEC06-BP02 Provision compute from hardened images

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 2 controls

CFTC-SS-4 Systems Operations Category
CFTC-SS-7 Generally Accepted Standards and Best Practices

SOC 2 · 2 controls

SOC2-CC5.2 COSO principle 11: Selects and develops general controls over technology
SOC2-CC7.1 Detection and monitoring procedures for security events are in place

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

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

CMMC 2.0 · 1 control

CM.L2-3.4.2 Security Configuration Enforcement

DORA · 1 control

DORA-Art.9 Protection and prevention

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-171 Rev 3 · 1 control

03.04.02 Configuration Settings

NIST SP 800-53 Rev 5 · 1 control

NIST800-CM-6 Configuration settings

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 FedRAMP Moderate have you already done?

FedRAMP Moderate CM-6 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of FedRAMP Moderate your existing evidence covers. Hold ISO 27002:2022 and 182 of 323 FedRAMP Moderate controls already carry evidence.

If you hold ISO 27002:202256.3% covered · 141 gaps If you hold PCI DSS 4.051.1% covered · 158 gaps If you hold ISO 27001:202249.8% covered · 162 gaps If you hold NIST SP 800-171 Rev 345.5% covered · 176 gaps If you hold C5 (Germany)37.2% covered · 203 gaps If you hold CMMC 2.035% covered · 210 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. 348 were rejected on the ISO 27002:2022 pair alone.

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