FedRAMP Moderate CM-2: Baseline Configuration

What else in your programme already covers this

This control maps to 33 controls across 19 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 · 5 controls

1.2.1 NSC configuration standards defined
12.5.1 Inventory of system components in scope
2.1.1 All security policies and operational procedures that are identified in Requirement 2 are: • Documented. • Kept up to date. • In use. • Known to all affected parties
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.6 System security parameters configured

C5 (Germany) · 4 controls

C5-AM-03 Commissioning of Hardware
C5-COS-07 Documentation of the network topology
C5-OPS-23 Managing Vulnerabilities, Malfunctions and Errors - System Hardening
C5-PSS-11 Images for Virtual Machines and Containers

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

ANSSI-HYG-14 Apply a Minimum Security Level Across the Whole Estate
ANSSI-HYG-16 Use a Centralised Management Tool to Standardise Security Policies

ASD Strategies to Mitigate Cyber Security Incidents · 2 controls

ASD37-11 Operating system hardening (Very Good)
ASD37-36 System recovery capabilities (Very Good)

AWS Well-Architected Security Pillar · 2 controls

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

Azure Security Benchmark · 2 controls

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

CIS Controls v8 · 2 controls

CIS-4.1 Establish and Maintain a Secure Configuration Process
CIS-4.2 Establish and Maintain a Secure Configuration Process for Network Infrastructure

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

CCM-CCC-06 Change Management Baseline
CCM-IVS-04 OS Hardening and Base Controls

SOC 2 · 2 controls

SOC2-CC7.1 Detection and monitoring procedures for security events are in place
SOC2-CC8.1 Change management processes are in place

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

CFTC-SS-4 Systems Operations Category

CMMC 2.0 · 1 control

CM.L2-3.4.1 System Baselining

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-2 Baseline Configuration

NIST SP 800-171 Rev 3 · 1 control

03.04.01 Baseline Configuration

NIST SP 800-172 · 1 control

3.14.4e Refresh Systems and Components from a Trusted Baseline

NIST SP 800-53 Rev 5 · 1 control

NIST800-CM-2 Baseline configuration

UK Cyber Essentials · 1 control

CE-SC.1 Remove or Disable Unused Software

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-2 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