CIS Controls v8 CIS-16.7: Use Standard Hardening Configuration Templates for Application Infrastructure

What else in your programme already covers this

This control maps to 43 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.

NIST SP 800-53 Rev 5 · 5 controls

NIST800-CM-2 CM-2 Baseline Configuration
NIST800-CM-6 CM-6 Configuration Settings
NIST800-CM-7 CM-7 Least Functionality
NIST800-SA-10 SA-10 Developer Configuration Management
NIST800-SA-17 SA-17 Developer Security and Privacy Architecture and Design

ISO 27001:2022 · 4 controls

5.36 Compliance with policies, rules and standards for information security
8.25 Secure development life cycle
8.27 Secure system architecture and engineering principles
8.9 Configuration management

ISO 27002:2022 · 4 controls

5.36 Compliance with policies, rules and standards for information security
8.20 Networks security
8.27 Secure system architecture and engineering principles
8.9 Configuration management

NIST SP 800-218 · 4 controls

SP800-218-PO.3.2 Toolchain Configuration and Integration
SP800-218-PO.5.1 Secure Development Environment Implementation
SP800-218-PO.5.2 Harden Development Endpoints
SP800-218-PW.9.1 Configure Software to Have Secure Settings by Default

AWS Well-Architected Security Pillar · 3 controls

SEC01-BP06 Automate deployment of standard security controls
SEC06-BP02 Provision compute from hardened images
SEC11-BP07 Regularly assess security properties of the pipelines

Australian Information Security Manual · 3 controls

ISM-1246 Hardening server applications
ISM-1409 Hardening operating systems
ISM-1916 Approved server application configurations

Azure Security Benchmark · 3 controls

ASBv3-DS-3 Secure DevOps infrastructure
ASBv3-PV-1 Define and establish secure configurations
ASBv3-PV-3 Define and establish secure configurations for compute resources

SOC 2 · 3 controls

SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)
SOC2-CC6.8 CC6.8 Preventing and detecting unauthorised or malicious software
SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

C5 (Germany) · 2 controls

C5-OPS-23 Managing Vulnerabilities, Malfunctions and Errors - System Hardening
C5-PSS-11 Images for Virtual Machines and Containers

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

CCM-AIS-02 Application Security Baseline Requirements
CCM-IVS-04 OS Hardening and Base Controls

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

ASD37-10 Server application hardening (Very Good)

CMMC 2.0 · 1 control

CM.L2-3.4.2 Security Configuration Enforcement

FedRAMP High · 1 control

CM-6 Configuration Settings

ISO 27701:2019 · 1 control

6.9.6 Technical vulnerability management

ISO/IEC 42001:2023 · 1 control

A.6.2.5 AI system deployment

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

PCI DSS 4.0 · 1 control

2.2.1 2.2.1 System configuration standards maintained

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 CIS Controls v8 have you already done?

CIS Controls v8 CIS-16.7 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CIS Controls v8 your existing evidence covers. Hold ISO 27001:2022 and 102 of 153 CIS Controls v8 controls already carry evidence.

If you hold ISO 27001:202266.7% covered · 51 gaps If you hold FedRAMP Moderate62.7% covered · 57 gaps If you hold NIST SP 800-53 Rev 557.5% covered · 65 gaps If you hold NIST Cybersecurity Framework 2.050.3% covered · 76 gaps If you hold ISO 27002:202249.7% covered · 77 gaps If you hold Azure Security Benchmark49% covered · 78 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. 240 were rejected on the ISO 27001:2022 pair alone.

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