liveBook · Manning

Security hardening

As explained in Fundamentals of Cybersecurity

System hardening is the process of reducing a system's vulnerabilities and attack opportunities through secure configuration, removal of unnecessary functionality, and protective controls.

Security hardening means configuring a system to reduce vulnerabilities and its attack surface—the possible entry points an attacker could use. Default settings may leave unnecessary services running, network ports open, or permissions too broad. A poorly secured system can become a foothold for attacks on the wider organization. section 15.0 section 15.1

Common hardening actions include:

  • Remove unused software, disable unnecessary services, and close unused network ports. section 15.9
  • Replace default credentials and limit access using permissions and the principle of least privilege. section 15.0 section 15.2.1
  • Apply patches and updates to address known flaws, prioritizing risks to critical systems. section 15.4

Turn a rule into a setting

A password policy states what a strong password requires. Hardening turns that rule into settings such as password complexity and account lockout. Similarly, an access control policy becomes permissions and role-based access controls, rather than remaining only a written requirement. section 15.2.1

Start with an up-to-date asset inventory: unknown systems cannot be reliably secured or patched. A security baseline then defines the minimum approved settings for those systems. CIS Benchmarks, DISA STIGs, and NIST checklist guidance can help organizations establish or tailor those requirements. section 15.2 section 15.1 section 15.3

Hardening is not finished at deployment. New vulnerabilities, updates, and configuration changes can weaken a secure setup. Continue patching and reviewing systems, and use change management to evaluate and test modifications before they reach production. section 15.0 section 15.8

How Fundamentals of Cybersecurity covers it

How deep it goes
Explains hardening measures, baselines, patching, and change management at an operational level, without device-specific commands.
Examples
Uses unused services and ports, default credentials, password complexity, account lockout, and role-based access controls as concrete cases.
What it assumes
Requires an accurate asset inventory and governing policies before technical measures can reliably cover an organization's systems.
What you can do after
Practice/perform secure configuration by removing unnecessary functionality, limiting access, applying patches, and reviewing systems as they change.
How it connects
Connects attack surface reduction with security policies, asset inventory, security baselines, patch management, least privilege, and change management.

Also explained in

Compare how 3 books explain security hardening →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Fundamentals of Cybersecurity. The section links point to the parts of the book it draws on.