Udemy
Turn what you know into an opportunity and reach millions around the world.
Learn More
Your cart is empty.
Keep shopping
Linux Server Hardening: CIS Benchmarks in Practice
Rating: 2.5 out of 5(4 ratings)
87 students

Linux Server Hardening: CIS Benchmarks in Practice

Harden Ubuntu 24.04 to the CIS Benchmark hands-on: OpenSCAP scans, tailoring, SSH, auditd, AIDE, Ansible and evidence
Created byNEXUS ACADEMY
Last updated 9/2026
English

What you'll learn

  • Build a disposable Ubuntu 24.04 LTS lab server with snapshots, then scan it against the CIS Benchmark with OpenSCAP and the SCAP Security Guide
  • Read a CIS recommendation like an engineer, trace it to an oscap rule and write a tailoring file for the deviations you need
  • Harden partitions, mount options, kernel modules, GRUB and kernel parameters, and verify them after a real reboot
  • Reduce the attack surface: package sources, automatic updates, unneeded services, time sync and a default-deny host firewall
  • Harden SSH and verify the effective configuration with sshd -T and ssh -Q, without locking yourself out
  • Lock down accounts, PAM, password quality, account lockout and sudo so there is one logged way to become root
  • Configure journald, rsyslog and auditd, then use AIDE, SUID/SGID baselines and AppArmor to detect and contain change
  • Diagnose and roll back hardening that breaks production, and write exceptions an auditor will accept
  • Automate the baseline with SSG remediation and an Ansible CIS role, bake a hardened image and gate drift in CI
  • Produce audit evidence: before-and-after reports, a Lynis second opinion, scheduled drift scans and an evidence pack

Course content

15 sections • 131 lectures • 13h 13m total length
  • Course Documents and How to Use Them7:15
  • Section 1 Intro: What You Are Actually Building2:59
  • What "Hardening" Means and What It Does Not5:22
  • The CIS Benchmark: A Consensus Document, Not a Law6:21
  • Level 1, Level 2 and the STIG Profile6:27
  • Server or Workstation: Choosing the Right Profile5:16
  • Why an Auditor Asks You for a Configuration Standard6:25
  • [LAB] Getting the Benchmark and Finding Your Platform's Version6:31
  • The Baseline: The Artefact You Build in This Course5:07
  • Section 1 Wrap: The Document and the Machine3:06

Requirements

  • Comfort in a Linux shell: editing files, using sudo and reading command output. No compliance or audit background is required
  • A computer that can run a virtual machine for the lab server; all tools used in the labs are free and open source

Description

“This course contains the use of artificial intelligence.”

This is the rebuilt, hands-on edition of Linux Server Hardening: CIS Benchmarks in Practice. Instead of describing controls from slides, you harden a real Ubuntu 24.04 LTS server in a virtual machine, one control at a time, and prove each change with a scan. More than half of the content lectures are screen-recorded labs marked [LAB]: every command is run on camera, and the output you see is the output it really printed.

The course has one running artefact, the baseline: a hardened Ubuntu 24.04 LTS host plus its evidence pack, made of a tailoring file, an exception register, an Ansible role and before-and-after scan reports. You build the lab host with snapshots so you can break things safely, install OpenSCAP and the SCAP Security Guide, run your first CIS scan and learn to read the report without chasing the score.

You then learn to read the benchmark like an engineer: the description, rationale and impact of a recommendation, its audit and remediation blocks, automated versus manual controls, how one recommendation maps to an oscap rule ID, and how to write a tailoring file for the deviations you genuinely need. CIS profiles are treated as what they are: recommendations, not law.

The hardening sections follow the benchmark in order: partitions and mount options, filesystem module blacklists, GRUB passwords and kernel parameters verified after a real reboot, package sources and automatic updates, service reduction and time synchronisation, a default-deny host firewall with nftables, ufw or firewalld, SSH verified with sshd -T and ssh -Q, accounts, PAM, pam_pwquality, pam_faillock and sudo, journald, rsyslog and auditd with immutable rules, file permissions, SUID/SGID baselines, AIDE, and AppArmor. RHEL 9 differences such as dnf, firewalld and SELinux are called out where they matter.

Then comes the part most courses skip: what to do when hardening breaks production. You diagnose a host that stopped accepting connections, roll back a single control and prove the rollback, and write exceptions an auditor will accept. After that you turn the baseline into code with SSG-generated remediation and an Ansible CIS role, bake a hardened image, and add a compliance gate to CI that fails the build on drift.

The final section covers audit evidence and operations: before-and-after reports, a second opinion with Lynis, scheduled drift scanning, the evidence pack you hand an auditor, and how to move to a new benchmark version. Licensed consoles such as CIS-CAT Pro and Ubuntu Pro's Security Guide are explained conceptually and never used in the labs; everything you run is free and open source.

Ten downloadable working documents accompany the course, from the hardening baseline template and the tailoring file starter kit to the SSH hardening guide, the exception register and the audit evidence and drift monitoring kit, plus the lab scripts as a download, so the artefacts you build are ones you can take to work.

Who this course is for:

  • Linux system administrators and DevOps or platform engineers who have been handed a CIS Benchmark and told to comply
  • SOC, infrastructure and security engineers who need to audit Linux hosts and produce evidence an auditor will accept
  • Security engineers writing a Linux configuration standard for the first time who want it grounded in real controls