liveBook · Manning

Security hardening

Also called system hardening

Security hardening is the practice of reducing a system’s vulnerabilities and attack surface through secure configuration, protective controls, and removal of unnecessary functionality.

How 3 Manning books explain it

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.

How it is used
Reduces exploitable entry points by turning organizational security requirements into secure system configurations.
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 you can do after
Practice/perform secure configuration by removing unnecessary functionality, limiting access, applying patches, and reviewing systems as they change.

Read how Fundamentals of Cybersecurity explains security hardening →

Secure APIs

Server hardening is the practice of reducing a server's attack surface by disabling unnecessary services, restricting access, and applying restrictive security configurations.

How it is used
Protects managed API servers against unauthorized access and infrastructure-level malicious traffic.
How deep it goes
Details a hardening checklist but stops short of provider-specific configuration procedures.
Examples
Uses an exposed Jenkins server on port 8080 to demonstrate how port scanning supports service hijacking.
What you can do after
Operate/configure managed servers by reducing exposed services, restricting privileged access, and securing remote endpoints.

Read how Secure APIs explains security hardening →

Learn Docker in a Month of Lunches, Second Edition

Security hardening is the practice of reducing exploitable weaknesses by applying restrictive configuration and removing unnecessary capabilities.

How it is used
Applies restrictive container and deployment configuration while checking whether applications continue to run.
How deep it goes
Works through image and configuration scans, then stops short of automatic fixes by requiring pragmatic review and end-to-end testing.
Examples
Uses Trivy image scans, repository misconfiguration scans, non-root users, and read-only container filesystems.
What you can do after
Diagnose vulnerabilities and deployment misconfigurations, apply compatible hardening changes, and verify them with end-to-end tests.

Read how Learn Docker in a Month of Lunches, Second Edition explains security hardening →

Also covered in

What to know first

Related concepts

Questions about security hardening

What is security hardening?

Security hardening is the practice of reducing a system’s vulnerabilities and attack surface through secure configuration, protective controls, and removal of unnecessary functionality.

Which Manning books explain security hardening?

Fundamentals of Cybersecurity, Secure APIs and Learn Docker in a Month of Lunches, Second Edition.

What should I know before learning security hardening?

Manning books that teach security hardening usually introduce vulnerability and Common Vulnerabilities and Exposures first.

What is security hardening also called?

Security hardening is also called system hardening.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.