System Hardening
What is System Hardening?
The process of securing a system by reducing its attack surface through removing unnecessary software, closing unused ports, and applying security configurations.
Terms that appear alongside system hardening
Each of these is named in at least one of the same controls as system hardening. The number is how many controls name both.
- hardening 15 shared controls
- patch management 6 shared controls
- secure configuration 4 shared controls
- malware 4 shared controls
- baseline 4 shared controls
- cis benchmarks 3 shared controls
- disa stig 3 shared controls
- secure boot 3 shared controls
Frameworks that govern system hardening
What the standards actually require on system hardening
Requirements naming system hardening across 6 standards, quoted from the control text.
Harden operating systems based on vendor guidance and ASD guidance. Remove unneeded software, services and ports.
ASD37-11 · Operating system hardening (Very Good) →Reduce the cyber attack surface of SWIFT-related components by performing system hardening on all in-scope systems.
2.3 · 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 evidenc...
C5-OPS-23 · Managing Vulnerabilities, Malfunctions and Errors - System Hardening →Disclose and operate malware detection + system hardening + cybersecurity upgrade features per MDS2 MLDP + SAHD + CSUP sections. Malware Detection and Protection (MLDP) including anti-malware software support + signature update mechanism + behavioural detectio...
MDS2-Malware-Detection-MLDP-System-Hardening-SAHD-Cybersecurity-Upgrades-CSUP-Patch-Management · MDS2 Malware Detection + MLDP + System Hardening + SAHD + Cybersecurity Upgrades + CSUP + Patch Management →Apply NZISM Chapters 10 (Network Security) + 11 (System Hardening) + 12 (Software Security and Application Development) covering: network segmentation with cross-domain solutions where applicable + perimeter defence + intrusion detection/prevention + system ha...
NZISM-5 · Network Security, System Hardening, and Application Security →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.
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 →Questions people ask about system hardening
What is System Hardening?
Why is System Hardening important for compliance?
Which compliance frameworks address System Hardening?
Where can I learn more about System Hardening?
See how System Hardening applies across compliance frameworks
Our platform maps 686 frameworks with 311K cross-framework control mappings. Explore how this concept is addressed across standards.