Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is System Hardening?

System hardening is the process of securing servers, endpoints, network devices, and applications by removing unnecessary functions and applying secure configuration settings.

Illustration for the cybersecurity term System Hardening
Home / Blog / Cybersecurity Terms / What Is System Hardening?
17 November 2026

What Is System Hardening?

What Is System Hardening?

System hardening is the practice of reducing a system’s attack surface by removing what it does not need and configuring what remains as securely as possible. Operating systems, applications, databases, and network devices usually ship with settings chosen for convenience and compatibility, not security. Hardening changes those defaults so that attackers have fewer ways in and less room to move once inside.

Think of it as closing every window and door you do not use, then putting good locks on the ones you do. A hardened system is not invulnerable, but it forces attackers to work harder and makes their activity easier to spot.

What Hardening Involves

Hardening covers several layers:

Examples by System Type

Windows endpoints and servers: disable SMBv1, LLMNR, and NetBIOS name resolution, which attackers abuse for credential theft; enforce SMB signing; enable Credential Guard and attack surface reduction rules; restrict PowerShell to Constrained Language Mode for standard users; deploy Windows LAPS; and remove local administrator rights.

Linux servers: disable root login over SSH and require key-based authentication; remove unused packages and services; configure a host firewall; apply SELinux or AppArmor policies; and restrict sudo rules carefully to avoid privilege escalation.

Network devices: disable Telnet, HTTP management, and unused interfaces; use SSH and SNMPv3; restrict management access to a dedicated network; and back up configurations securely.

Web servers and applications: remove version banners and default pages, disable directory listing, enforce secure headers and modern TLS, and run services under dedicated low-privilege accounts.

Cloud services: block public access to storage by default, enforce MFA on all accounts, enable logging across every region, and apply organisation-wide guardrail policies.

Hardening Standards and Benchmarks

You do not have to start from scratch. Several respected sources publish detailed configuration guides:

SourceWhat it offers
CIS BenchmarksConsensus-based settings for operating systems, cloud platforms, databases, and applications, with Level 1 and Level 2 profiles
Microsoft security baselinesRecommended Group Policy and Intune settings for Windows and Microsoft 365
DISA STIGsDetailed configuration guides from the US military, often used in high-security environments
NCSC device security guidanceUK guidance on configuring laptops, mobiles, and other devices securely

The UK Cyber Essentials scheme includes secure configuration as one of its five technical controls, covering the removal of unnecessary software and accounts and the changing of default passwords.

Doing Hardening Well

  1. Build a secure baseline for each system type, based on a recognised benchmark adapted to your environment.
  2. Test before deploying, since some settings can break legacy applications.
  3. Automate through Group Policy, Intune, configuration management tools such as Ansible, or golden images and infrastructure as code.
  4. Monitor for drift, because systems gradually move away from their baseline as changes are made.
  5. Document exceptions, with an owner and a review date for any setting you cannot apply.
  6. Verify regularly with configuration scanners and penetration testing.

Why Hardening Matters

Many intrusions rely not on sophisticated exploits but on weak configuration: default passwords on management interfaces, legacy protocols that leak credentials, open file shares, or overly permissive services. Hardening removes these easy wins. It also limits the damage of unknown vulnerabilities, since a feature that has been disabled cannot be exploited.

At Privia Security, our Infrastructure and Architecture Review Services assess your systems against recognised hardening benchmarks and give you prioritised, practical configuration changes.

FAQ – Frequently Asked Questions

What Is the Difference Between Hardening and Patching?

Patching fixes known vulnerabilities in software by installing vendor updates. Hardening reduces the attack surface by removing unnecessary features and applying secure settings, which also protects against weaknesses that have not been discovered yet. Both are essential and complement each other, and most security frameworks require them together as part of basic hygiene.

Which Hardening Standard Should I Use?

CIS Benchmarks are a popular starting point because they cover a wide range of products and offer graded profiles. Microsoft security baselines suit Windows-heavy environments, and DISA STIGs suit very high-security settings. Whichever you choose, adapt it to your environment, test changes carefully, and document any settings you deliberately do not apply.

Can Hardening Break Applications?

Yes, particularly with older or poorly written software that depends on legacy protocols, broad permissions, or insecure defaults. That is why changes should be tested on representative systems first and rolled out in stages. Where a setting cannot be applied, document the exception and compensate with other controls such as segmentation and monitoring.

Related Terms

You May Be Interested In These

What Are Testing Limits in OT Environments?

Cybersecurity Terms

17 November 2026

What Are Testing Limits in OT Environments?

Read More
What Is the Internet of Medical Things?

Cybersecurity Terms

17 November 2026

What Is the Internet of Medical Things?

Read More