Concepts / Hardening and auditing

Hardening and auditing

Secure baseline and hardening

Also called baseline, hardening, secure configuration, configuration enforcement, benchmark compliance, drift

The known-good configuration a host should hold, and the work of bringing it there and keeping it there.

A secure baseline is the agreed known-good state of a host: the services it runs, the options they are set to, the permissions on sensitive files. Hardening is bringing a host to that baseline — disabling what is not needed, tightening what is (no direct root SSH login, tight file modes) — and configuration enforcement is keeping it there as changes and updates push it off, called drift. A baseline makes "secure" concrete and checkable: a SCAP benchmark is a baseline written as rules, and a scan measures how far a host has drifted from it. The baseline is also the reference a file-integrity monitor and an incident responder compare the live host against.

See it on real machines

Learn it on real machines.

Every lab is a small network of real Linux machines in your browser. Start with a free account: Google or email, no card.

Open this lab