Udemy
Turn what you know into an opportunity and reach millions around the world.
Learn More
Your cart is empty.
Keep shopping
NIST 800-53 High Baseline Implementation Bootcamp 2026
New
43 students

NIST 800-53 High Baseline Implementation Bootcamp 2026

Implement and prove the SP 800-53 Rev. 5 High baseline on a real system: OSCAL, OpenSCAP, auditd, Wazuh, evidence
Created byNEXUS ACADEMY
Last updated 10/2026
English
English [Auto],

What you'll learn

  • Explain where the High baseline comes from (FISMA, FIPS 199, FIPS 200) and what SP 800-53 Release 5.2.0 did and did not change
  • Load the official NIST OSCAL catalog and High profile, count the baseline yourself and tailor it with organization-defined parameters
  • Read a control the way an assessor does: statement, discussion, SP 800-53A assessment objectives and the evidence each one needs
  • Implement the Access Control and Identification and Authentication families on Linux: account lifecycle, least privilege, faillock, TOTP, SSH key lifecycle
  • Generate, protect and analyse audit records with auditd, chrony, off-host TLS log shipping, signed archives and Wazuh dashboards
  • Capture configuration baselines as code, apply STIG remediation with Ansible, rescan with OpenSCAP and pivot results back to 800-53 controls
  • Enforce boundaries, isolation, fail-secure behaviour and cryptography (TLS, keys, encryption at rest) and understand the FIPS 140-3 transition
  • Automate integrity, vulnerability and incident-response controls: AIDE, ClamAV, Trivy, SBOMs with Syft, Cosign signatures and an incident timeline
  • Run continuous monitoring, produce assessment results and POA&M entries, and generate a System Security Plan in OSCAL with compliance-trestle
  • Assemble a complete authorization package for a reference High system end to end in the capstone

Course content

25 sections • 285 lectures • 26h 31m total length
  • Course Documents and How to Use Them7:34
  • Section 1 Intro: Why a High System Is a Different Job2:47
  • FISMA, FIPS 199 and FIPS 200: Where the Obligation Comes From5:42
  • No Waivers: What FIPS 200 Says About High-Impact Systems4:31
  • The 800-53 Family of Documents: Catalog, Baselines, Assessment4:48
  • Release 5.2.0: What Changed in August 2025 and What Did Not4:44
  • The 20 Control Families on One Page5:45
  • Low, Moderate, High: 149, 287 and 370 Items, Measured4:37
  • The 83 Items Only High Adds6:30
  • National Security Systems, FedRAMP and Contractors: Who Else Uses This4:56
  • The Bootcamp Artefact: A Small High System and Its Evidence Locker4:43
  • Section 1 Wrap: The Rules You Now Work Under2:47

Requirements

  • Comfort with the Linux shell, SSH, containers and basic networking; no prior RMF or 800-53 experience is assumed
  • A machine that can run Docker containers and, for the kernel-level labs, a QEMU/KVM virtual machine (about 16 GB RAM recommended). All tools used are open source

Description

“This course contains the use of artificial intelligence.”

A High-impact system is a different job. Under FISMA and FIPS 200 there are no waivers: if a system is categorized High under FIPS 199, every applicable control in the SP 800-53 Rev. 5 High baseline has to be implemented, and an assessor will ask you to prove it. This bootcamp is about doing exactly that on a real system, control family by control family, and leaving behind the evidence an assessor can parse.

You start by measuring the baseline yourself. You load NIST's official OSCAL catalog and the Low, Moderate and High profiles (version 5.2.0), count the items — 149, 287 and 370 — identify the 83 items that only High adds, and tailor the profile with organization-defined parameters into a machine-readable control list. Then you build the lab: a three-tier reference system (web, app, database) in containers plus an Ubuntu 24.04 VM for the kernel-level controls, OpenSCAP with the SCAP Security Guide, Wazuh and OpenSearch for monitoring, and a Git evidence locker organised by control family.

From there the course walks the technical families and implements them for real. Access Control: account lifecycle, automated disablement, separation of duties, sudo least privilege, concurrent session limits, nftables tier-to-tier flows and hardened SSH. Identification and Authentication: unique IDs, TOTP multifactor, password quality and SSH key rotation. Audit and Accountability: auditd rules, time-correlated trails with chrony, off-host shipping over TLS, signed archives, non-repudiation and retention. Configuration Management: baselines as code, STIG remediation with Ansible, scheduled compliance scans committed to Git, change gates, least functionality, allow-listing and live inventory.

The System and Communications Protection family covers boundaries, isolation, fail-secure behaviour, TLS 1.2 and 1.3 only, key management, encryption at rest and the FIPS 140-3 transition, including what FIPS mode does and does not prove. System and Information Integrity, Risk Assessment, Contingency Planning and Incident Response are built the same way: AIDE with automated response, ClamAV reporting into Wazuh, Trivy image scans, a ranked risk register, encrypted backups with a timed restore drill, and an incident timeline generated from audit and Wazuh data.

Two sections take the controls onto modern substrates: a container platform (dropped capabilities, segmented networks, a deployment gate that refuses unsigned images, Cosign signatures and SBOMs with Syft) and infrastructure as code (Terraform plans, policy-as-code checks, drift detection). The families you cannot script — PE, PS, MA, MP, AT, PL, PM and PT — get an owner and an evidence type each, so nothing is left as an unowned paragraph.

The last sections are about proving it: continuous monitoring jobs that scan, compare and report; assessment results files; POA&M entries generated from failed checks; and a System Security Plan authored in OSCAL with compliance-trestle, validated against the schema and linked to the evidence locker. A capstone rebuilds the reference system from zero, applies the hardened baseline, and assembles the whole authorization package the way an assessor would walk it.

This is a defensive, implementation-first course. Every control ID and baseline count comes from the NIST OSCAL content, not from memory; STIG results are pivoted to 800-53 through each rule's NIST reference, and the course says plainly where a clean scan stops covering the baseline. There are no attack labs, no licensed consoles and no statistics. The course produces implementations and evidence; authorization remains a risk decision made by an authorizing official, and nothing here is legal advice. Eleven downloadable documents come with the course, including the lab bundle handbook, the High baseline quick reference, the FIPS 199 categorization worksheet, the tailoring and parameter decision record, the evidence locker standard, the technical controls checklist, the recovery and IR exercise workbook, the supply-chain and IaC checklist, the non-technical families owner matrix and the continuous monitoring, POA&M and OSCAL SSP build guide.

Who this course is for:

  • System owners, ISSOs and ISSMs responsible for a federal system categorized High under FIPS 199
  • Engineers at federal contractors and cloud providers who must build and operate systems to the High baseline
  • GRC analysts and assessors who want to see what each High control looks like when it is actually implemented and evidenced