Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
System hardening is the process of securing servers, endpoints, network devices, and applications by removing unnecessary functions and applying secure configuration settings.

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.
Hardening covers several layers:
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.
You do not have to start from scratch. Several respected sources publish detailed configuration guides:
| Source | What it offers |
|---|---|
| CIS Benchmarks | Consensus-based settings for operating systems, cloud platforms, databases, and applications, with Level 1 and Level 2 profiles |
| Microsoft security baselines | Recommended Group Policy and Intune settings for Windows and Microsoft 365 |
| DISA STIGs | Detailed configuration guides from the US military, often used in high-security environments |
| NCSC device security guidance | UK 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.
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.
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.
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.
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.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.