hardening
Reducing a system's attack surface by removing or locking down anything it does not need, such as unused services and direct root login.
In more detail
Typical steps include removing unused software, closing unused ports, disabling direct root login over SSH and applying secure defaults. Hardening is best applied by automation, so every machine gets it and none drifts back.
Example
Because direct root login is usually disabled, Ansible connects as an ordinary user and escalates with become.Related terms
- root user — The all-powerful administrator account on Linux, with user ID 0, which can read or change anything.
- SSH — A protocol for logging in to and running commands on another computer securely over a network.
- least privilege — Giving every program and person only the access they need, and nothing more.
- minimal base image — A base image with as little inside as possible, such as Alpine, a slim variant or a distroless image, to shrink size and attack surface.
- non-root user — An ordinary user account with limited rights, which a container should run its service as.
Taught in
- Connections And Privilege Escalation — Ansible Configuration Management at Scale
- Security Governance vs Security Management — Cybersecurity Fundamentals, GRC & Cryptography
- Security Baselines, Policies & Hardening Standards — Cybersecurity Fundamentals, GRC & Cryptography
- Security Frameworks: NIST CSF 2.0, ISO 27001 & CIS — Cybersecurity Fundamentals, GRC & Cryptography
- Production Hardening: Graceful Shutdown & Docker — Node.js Internals & Backend Services