CMMC Linux Compliance: FIPS-Validated Distros, sudo, Logging and Hardening for Level 2
By The Defense Compliance Report Editorial Team · Last verified: November 19, 2026
General information for the defense industrial base, not legal, contractual or compliance advice. Not affiliated with DoD, the Department of War, NIST, The Cyber AB, Red Hat, Canonical, SUSE, Oracle, Amazon Web Services, CIQ, TuxCare, Microsoft, Google or any government agency. Your contract and your own scoping decisions control what applies to you.
Short answer: You can run Linux for CUI under CMMC Level 2, but not every distribution can do it. The deciding test is cryptography: when encryption protects CUI, NIST SP 800-171 requires FIPS-validated cryptography, which means the module itself must hold a NIST certificate. On November 19, 2026, active FIPS 140-3 certificates covered OpenSSL modules for Red Hat Enterprise Linux 9, Ubuntu 22.04 and 24.04, SUSE Linux Enterprise, Oracle Linux 9, Rocky Linux 8 and 9, AlmaLinux 9 (through TuxCare) and Amazon Linux 2023. We found no active certificate with Debian or CentOS in the module name, and the RHEL 8 OpenSSL certificate is a FIPS 140-2 certificate now on NIST's Historical list. After the distro choice, Linux needs the same 110 requirements as any other system: unique logins instead of shared root, MFA for privileged access, audit logs tied to people, a documented hardening baseline and patching on a supported release. CMMC Phase II is still suspended, but Level 2 (Self) assessments and DFARS 252.204-7012 still apply.
Who this page is for
- IT managers and MSPs with Linux file servers, build servers, databases or jump hosts inside a Level 2 boundary.
- Engineering and manufacturing shops running Linux workstations for CAD, simulation or CNC programming that touch controlled drawings.
- Software and hardware teams whose CI/CD runners, Git servers or containers handle CUI source code or technical data.
- Anyone building a CUI enclave who wants to know why some distributions are acceptable and others aren't.
If your Linux systems never store, process or transmit CUI and can't reach systems that do, most of this page won't apply. The scoping section below explains how to tell.
Is your Linux system in scope for CMMC?
CMMC assesses your company's systems, not an operating system. A Linux host is in scope based on what it does, using the asset categories in 32 CFR 170.19.
| Linux system | Typical asset category | What applies |
|---|---|---|
| File server, NAS or database holding drawings or CUI records | CUI Asset | All 110 Level 2 requirements |
| Engineering workstation that opens controlled CAD files | CUI Asset | All 110 requirements, including FIPS crypto if CUI leaves the boundary |
| Build server or Git host with CUI source code | CUI Asset | All 110 requirements |
| SIEM, log collector, bastion host, patch server, vulnerability scanner | Security Protection Asset | Requirements relevant to the security functions it provides |
| Linux server on the same network that is configured to keep CUI off it | Contractor Risk Managed Asset | Documented in inventory, SSP and diagram; policies and controls must keep CUI off it |
| Test equipment, CNC controllers, lab or OT boxes running embedded Linux | Specialized Asset | Inventory, SSP, network diagram and how you manage them |
| Linux host physically or logically separated from CUI systems | Out of scope | Must be unable to process, store or transmit CUI |
Specialized Assets matter for Linux shops because embedded Linux sits inside machine controllers, test rigs and lab instruments that you often can't patch or harden. 170.19 lets you document those as Specialized Assets rather than force them through every requirement. The CMMC asset inventory guide shows how to record each one, and CMMC scope reduction covers ways to shrink the Linux footprint inside the boundary.
There is no "CMMC certified Linux"
No distribution is "CMMC certified" or "CMMC compliant" out of the box. What vendors can earn is a FIPS 140-3 certificate for specific cryptographic modules, a published security baseline such as a DISA STIG or CIS benchmark, and a support lifecycle that keeps patches coming. Those three things make a distribution usable for CUI. Your configuration, documentation and evidence make it compliant.
When a vendor's page says its distribution "supports CMMC," read that as "has the parts you need." Then check each part yourself.
Which Linux distributions can protect CUI: the FIPS test
NIST SP 800-171 requirement 3.13.11 says to "Employ FIPS-validated cryptography when used to protect the confidentiality of CUI." The CMMC Assessment Guide explains that FIPS-validated means the cryptographic module is validated by NIST's Cryptographic Module Validation Program (CMVP). An approved algorithm such as AES running in an unvalidated library isn't enough.
The guide also limits where this applies. FIPS validation is required when cryptography protects CUI that is transmitted or stored outside the protected environment, including wireless and remote access. Encryption used for other purposes inside the protected environment doesn't have to be FIPS-validated. For a Linux host that means SSH from remote admins, TLS for web apps and file transfers, VPN tunnels and encrypted backups leaving the boundary all need a validated module.
That is why some distributions can't be used for a CUI enclave: if no validated module exists for that release, you can't meet 3.13.11 with it.
Active FIPS 140-3 OpenSSL modules on November 19, 2026
We opened each certificate on NIST's CMVP site on November 19, 2026. All were Active, all were FIPS 140-3, and each carries a caveat that it is validated when operated in approved mode, which on Linux means FIPS mode.
| Distribution | Module | CMVP certificate | Sunset date | Notes |
|---|---|---|---|---|
| Red Hat Enterprise Linux 9 | RHEL 9 OpenSSL FIPS Provider | #5573 | October 28, 2029 | Replaced #4857; RHEL 9 kernel crypto API is #5445 |
| Ubuntu 24.04 LTS | Ubuntu 24.04 OpenSSL Cryptographic Module | #5115 | January 5, 2031 | Requires Ubuntu Pro |
| Ubuntu 22.04 LTS | Ubuntu 22.04 OpenSSL Cryptographic Module | #4794 | September 10, 2029 | Requires Ubuntu Pro |
| SUSE Linux Enterprise | SUSE Linux Enterprise OpenSSL 3 Cryptographic Module | #5096 | November 25, 2030 | Tested configurations include SLES 15 SP6; SUSE OpenSSL module #5436 is also active |
| Oracle Linux 9 | Oracle Linux 9 OpenSSL FIPS Provider | #5294 | August 24, 2029 | |
| Rocky Linux 9 | Rocky Linux 9 OpenSSL FIPS Provider (Ctrl IQ) | #5116 | January 5, 2031 | Certificate holder is CIQ, not the community project |
| Rocky Linux 8 | Rocky Linux 8 OpenSSL module (Ctrl IQ) | #5200 | March 17, 2031 | Certificate holder is CIQ |
| AlmaLinux 9 | OpenSSL FIPS Provider for AlmaLinux 9 (TuxCare) | #5482 | October 6, 2029 | Certificate holder is TuxCare, a division of CloudLinux |
| Amazon Linux 2023 | Amazon Linux 2023 OpenSSL FIPS Provider | #5438 | July 26, 2031 |
OpenSSL is the module most Linux services use for SSH and TLS, so it is the first one to check. Distributions also have separate certificates for the kernel crypto API, GnuTLS, NSS and libgcrypt. If an application uses one of those libraries, look up that module too.
Note who holds the certificate. For Rocky Linux and AlmaLinux, the validated modules come from commercial vendors (CIQ and TuxCare), so you need their supported packages rather than the free community install.
Distributions without an active OpenSSL module today
| Distribution | Status on November 19, 2026 | What it means |
|---|---|---|
| Red Hat Enterprise Linux 8 | OpenSSL certificate #4642 is FIPS 140-2 and Historical ("Moved to historical list due to sunsetting"). Active RHEL 8 certificates cover the kernel crypto API and NSS (#5513), not OpenSSL | Existing RHEL 8 systems may keep using the Historical module, since CMVP supports Historical modules for existing systems; new CUI systems should go on RHEL 9 or another release with an active OpenSSL module |
| Red Hat Enterprise Linux 10 | No active certificate named for RHEL 10. RHEL 10 kernel and GnuTLS modules are on NIST's Implementation Under Test list; Red Hat lists RHEL 10.0's OpenSSL module as "Pending Operational Environment update" | Validation is in progress, not done; check Red Hat's FIPS page before building on RHEL 10 |
| Ubuntu 20.04 LTS | Canonical lists "FIPS 140-2: Expired" | Plan a move to 22.04 or 24.04 |
| Ubuntu 26.04 LTS, Oracle Linux 10, Rocky Linux from CIQ 10 | Modules on NIST's Implementation Under Test list | Not validated yet |
| Debian | 0 active certificates with Debian in the module name | Can't meet 3.13.11 with stock packages |
| CentOS Linux 7 and 8, CentOS Stream | 0 active certificates with CentOS in the module name; CentOS Linux 7 reached end of life June 30, 2024 | Replace; it fails both the crypto and the patching tests |
Distributions not listed in either table, such as Fedora, Arch or Linux Mint, didn't turn up in our checks for validated modules. If you rely on one, search the CMVP database for the exact module before you put CUI on it.
FIPS 140-2 vs FIPS 140-3 after September 2026
NIST's CMVP placed all FIPS 140-2 certificates on the Historical list on September 22, 2026. Its main page says FIPS 140-2 modules could be used for new systems until September 21, 2026, and its transition page says that even on the Historical list, CMVP supports the purchase and use of these modules for existing systems. For a new Linux system, that leaves FIPS 140-3.
| Situation | What to do |
|---|---|
| New Linux server or enclave being built now | Use a release with an active FIPS 140-3 module from the table above |
| Existing RHEL 8 or Ubuntu 20.04 host using a 140-2 module | It may stay as an existing system; record it in the SSP and plan a migration |
| Vendor document cites a certificate number | Open the certificate on the CMVP site; numbers get replaced (RHEL 9 #4857 was replaced by #5573) |
| Certificate shows "Interim validation" | It is still an active validation; read the caveat and the security policy |
FIPS mode: how to turn it on and prove it
A validated module only counts when the system runs it in FIPS mode. Each distribution does this differently.
| Distribution | How to enable | How to verify |
|---|---|---|
| RHEL 9 | Add fips=1 to the kernel command line during installation | fips-mode-setup --check or cat /proc/sys/crypto/fips_enabled returns 1 |
| Ubuntu 22.04 and 24.04 | Attach Ubuntu Pro, run sudo pro enable fips-updates, reboot | cat /proc/sys/crypto/fips_enabled returns 1; pro status shows the FIPS service enabled |
| Oracle Linux, Rocky Linux, AlmaLinux, SUSE | Follow the vendor's FIPS guide for the certified packages | Kernel flag plus the vendor's provider or package check |
| Any OpenSSL 3 system | Applies once FIPS mode is on | openssl list -providers shows the FIPS provider active |
Red Hat: enable FIPS at install, not afterward
Red Hat's RHEL 9 FIPS documentation says to install the system in FIPS mode. Switching an existing system with fips-mode-setup doesn't guarantee compliance with FIPS 140. Red Hat explains that only enabling FIPS mode during installation ensures the system generates all keys with FIPS-approved algorithms and continuous monitoring tests in place. If you must switch after installation, Red Hat says to do it as the first step, before any other configuration or workloads. Once FIPS mode is set up, Red Hat warns you can't switch it off without leaving the system in an inconsistent state. Red Hat also notes that FIPS compliance is tied to the specific binary version that was validated, and its FIPS compliance page maps each RHEL minor release to its module, package version and certificate.
Ubuntu: fips vs fips-updates
Canonical's Pro Client FIPS guide says, "we don't recommend enabling fips anymore - please use fips-updates instead," pointing to FedRAMP's newer policy on cryptographic modules. Its FIPS overview explains the trade-off. The fips service installs the exact certified binaries, which get no security updates. The fips-updates service adds security fixes, so the packages are no longer the exact binaries NIST tested.
The CMMC Assessment Guide addresses this case directly. It says FIPS-validated cryptography that needs a patch, where the patched version is no longer the validated version, may be a temporary deficiency. Write that decision down: which service you use, why, and the certificate the packages trace back to.
Applications that break in FIPS mode
Red Hat lists RHEL 9 applications that use cryptography that isn't FIPS-compliant, plus behavior that changes once FIPS mode is on. Test these before you flip the switch on a production server.
| Component | What changes in FIPS mode |
|---|---|
| MySQL and MariaDB | The mysql_native_password authentication plugin relies on SHA-1 |
| PostgreSQL | Some functions use Blowfish, DES and MD5 |
| Samba | Uses RC4 and DES for some functions |
| PKCS#12 files | Red Hat treats them as plain text for FIPS purposes, so protect them another way |
| zip | Encrypted zip files use PKWARE encryption, which isn't FIPS-approved |
| TLS 1.2 clients and servers | From RHEL 9.2, TLS 1.2 connections require Extended Master Secret (EMS), so old peers may fail to connect |
| Containers | A container uses the host kernel, so the host must run in FIPS mode |
If an application can't run with FIPS mode on, either move it off the CUI path or document the gap. Encryption that isn't FIPS-validated is the one 3-point requirement that can go on a POA&M, as the scoring section shows.
Privileged access: root and sudo
Linux makes least privilege easy to break: one shared root password, everyone in the wheel group, or sudo ALL for every admin. Level 2 requirements push the other way.
| Requirement | What it means on Linux | Points |
|---|---|---|
| AC.L2-3.1.1 Authorized access control | Every person has their own account; disable direct root login over SSH | 5 |
| AC.L2-3.1.5 Least privilege | Grant sudo only for the commands each admin needs | 3 |
| AC.L2-3.1.6 Non-privileged accounts for nonsecurity functions | Admins do daily work as a normal user and use sudo only for admin tasks | 1 |
| AC.L2-3.1.7 Privileged functions | Non-admins can't run privileged commands; sudo use is logged | 1 |
| AC.L2-3.1.8 Unsuccessful logon attempts | Lock accounts after repeated failures, for example with pam_faillock | 1 |
| IA.L2-3.5.3 Multifactor authentication | MFA for local and network access to privileged accounts and network access to all accounts | 3 or 5 |
Disabling direct root login and using named accounts with sudo gives you two things at once: least privilege and an audit trail. The Linux audit system records each user's original login ID (the auid), which Red Hat says is inherited by every process even when the user's identity changes, for example with su, so actions trace back to a person.
For vaulting root credentials, session recording and tools that cover Windows and network devices too, see our CMMC privileged access management guide.
MFA on Linux
IA.L2-3.5.3 requires MFA for local and network access to privileged accounts and for network access to non-privileged accounts. The Assessment Guide splits this into four objectives, and objective [b], local access to privileged accounts, is easy to miss on Linux. Someone at the console who logs in as an admin, or who switches to root locally, needs a second factor too.
| Access path | Needs MFA? | Common Linux approaches |
|---|---|---|
| SSH by an admin | Yes (network, privileged) | SSH keys on a hardware token plus a PAM-based second factor, or a bastion host that enforces MFA |
| SSH by a normal user | Yes (network, non-privileged) | Same as above |
| Console login by an admin | Yes (local, privileged) | PAM module for a hardware token or one-time code at the console |
| Console login by a normal user | Not required by 3.5.3 | Password plus lockout and session controls |
| Service accounts and automation | Treat separately | Keys restricted to specific commands and hosts; document in the SSP |
A missing MFA control costs 3 points if MFA covers remote and privileged users only, and 5 if no MFA is in place. Neither can go on a POA&M. The CMMC MFA requirements page covers the four objectives across all systems.
Audit logging with auditd
Linux ships with the audit framework (auditd) that most assessors expect to see. Red Hat's RHEL 9 auditing guide includes sample rule files for STIG-based rules (30-stig), privileged command use (31-privileged) and a finalize file (99-finalize) that makes the rules immutable.
| Requirement | auditd setting or practice | Points |
|---|---|---|
| AU.L2-3.3.1 Create and retain logs | auditd enabled at boot; rules for logins, sudo, account changes, file access to CUI paths; logs shipped to a central collector | 5 |
| AU.L2-3.3.2 Trace actions to users | Named accounts; auid recorded on every event | 3 |
| AU.L2-3.3.4 Alert on logging failure | space_left_action set to email or a script; collector alerts when a host stops sending | 1 |
| AU.L2-3.3.5 Review and correlate | Central SIEM or log tool that correlates Linux with other systems | 5 |
| AU.L2-3.3.7 Time stamps | Chrony or NTP synced to an authoritative source | 1 |
| AU.L2-3.3.8 Protect logs | Root-only log files, immutable rules, forwarding off the host | 1 |
| AU.L2-3.3.9 Limit log management | Only a small named group can change audit configuration | 1 |
Set max_log_file_action to keep_logs or rotate to the collector so logs aren't overwritten before they leave the host. DFARS 252.204-7012 also expects you to preserve images of affected systems for 90 days after you report an incident, so keep enough log history to support that. The SIEM for CMMC page compares central log tools, and DFARS 7012 incident reporting covers the 72-hour report.
Hardening baselines: STIG, CIS and the NIST 800-171 profile
CM.L2-3.4.1 and 3.4.2 require a documented baseline configuration and enforced security settings, each worth 5 points. On Linux, nobody writes that baseline from scratch. NIST SP 800-171 itself names security technical implementation guides and benchmarks as common secure configurations.
| Baseline | Where it comes from | Notes |
|---|---|---|
| DISA STIG | DoD's Defense Information Systems Agency | Strict; well known to DoD assessors; Canonical lists DISA-STIG as achieved for Ubuntu 18.04 through 24.04 |
| CIS Benchmark | Center for Internet Security | Level 1 and Level 2 profiles; easier to apply than a STIG |
| SCAP Security Guide "NIST 800-171" profile | Shipped with RHEL 9 as xccdf_org.ssgproject.content_profile_cui | Red Hat labels it [DRAFT]; maps rules to 800-171 |
| Vendor hardening tools | Ubuntu Security Guide (Ubuntu Pro), vendor SCAP content | Automates STIG or CIS for that distribution |
On RHEL, the oscap utility and the scap-security-guide package let you scan a host against a profile and produce an HTML report, as described in Red Hat's configuration compliance scanning guide. Save that report as evidence for 3.4.1 and 3.4.2, and record any rules you deliberately skip and why.
Pick one baseline per distribution and stick with it. Mixing STIG rules on some hosts and CIS on others makes your SSP harder to defend. Our configuration management requirements page covers the rest of the CM family.
Patching and end-of-life releases
SI.L2-3.14.1 requires you to identify, report and correct flaws in a timely manner, and it is worth 5 points that can't go on a POA&M. A Linux release that no longer receives security updates fails it by definition.
| Release | Support status | CMMC impact |
|---|---|---|
| CentOS Linux 7 | End of life June 30, 2024 | No patches; replace |
| CentOS Linux 8 | End of life December 31, 2021 | No patches; replace |
| CentOS Stream 8 | End of life May 31, 2024 | No patches; replace |
| Ubuntu 20.04 LTS | Standard security maintenance ended May 2025; Ubuntu Pro extends to May 2030 | Needs Ubuntu Pro for patches; FIPS 140-2 expired |
| Ubuntu 22.04 LTS | Standard security maintenance to May 2027 | Supported; plan the next upgrade |
| Ubuntu 24.04 LTS | Standard security maintenance to May 2029 | Supported |
| RHEL 8, RHEL 9 | Supported under Red Hat's life cycle policy | Supported; check your minor release's support phase |
Dates for CentOS come from the CentOS project, and Ubuntu dates come from Canonical's release cycle page.
Vulnerability scanning (RA.L2-3.11.2, 5 points) should include authenticated scans of Linux hosts in addition to network scans. See vulnerability scanning for CMMC and CMMC patch management requirements.
Malware protection on Linux
SI.L2-3.14.2 (5 points) requires protection from malicious code at designated locations, 3.14.4 (5 points) requires updating it, and 3.14.5 (3 points) requires periodic and real-time scans. "Linux doesn't get viruses" isn't an answer an assessor will accept for a CUI file server.
Most endpoint detection and response products ship Linux agents. Check that the agent supports your exact distribution and kernel, and that it still runs with FIPS mode on. The EDR for CMMC page compares options. If you decide a specific host doesn't need an agent, record the reasoning and the compensating controls in your SSP.
Session controls and remote access
| Requirement | Linux setting | Points |
|---|---|---|
| AC.L2-3.1.10 Session lock | Screen lock on workstations; shell timeout (for example TMOUT) on servers | 1 |
| AC.L2-3.1.11 Session termination | SSH ClientAliveInterval and ClientAliveCountMax to end idle sessions | 1 |
| AC.L2-3.1.12 Monitor remote access | SSH logins logged and reviewed | 5 |
| AC.L2-3.1.13 Cryptographic remote sessions | SSH and VPN using the FIPS-validated module | 5 |
| AC.L2-3.1.9 Privacy and security notices | SSH and console login banner | 1 |
| SC.L2-3.13.15 Session authenticity | TLS and SSH host key verification | 5 |
Our CMMC remote work requirements page covers remote access for staff who aren't admins.
Encryption at rest on Linux
SC.L2-3.13.16 requires protecting the confidentiality of CUI at rest, and it is worth 1 point. On Linux this is usually disk encryption with LUKS, which uses the kernel crypto API. If that storage, or a backup made from it, leaves your protected environment (a laptop, removable media, an offsite backup), the encryption must use a validated module, so check the kernel crypto certificate for your release. The CMMC encryption requirements and FIPS 140-2 requirements pages explain the rules across all systems.
Linux in the cloud
A Linux VM in a cloud that holds CUI brings in the cloud rule: under 32 CFR 170.16(c)(2) and DFARS 252.204-7012, a cloud service provider that stores, processes or transmits CUI must be FedRAMP Authorized at Moderate or higher, or meet DoD's FedRAMP Moderate equivalency standard.
| Cloud offering | FedRAMP Marketplace status (data last changed November 16, 2026) |
|---|---|
| Amazon Web Services US East/West | Authorized, Moderate |
| AWS GovCloud (US) | Authorized, High |
| Microsoft Azure (commercial) | Authorized, High |
| Microsoft Azure Government | Authorized, High |
| Google Services | Authorized, High |
| Oracle Cloud Infrastructure Government Cloud | Authorized, High |
| Red Hat OpenShift Service on AWS (ROSA) | Authorized, High |
A FedRAMP authorization covers the provider's infrastructure. Everything inside your VM, including the distribution, FIPS mode, accounts, auditd, hardening and patching, is still yours under the shared responsibility model. Ask the provider for its customer responsibility matrix and reference it in your SSP. Note that 7012 can also bring ITAR or export-control considerations that push some contractors toward GovCloud or Azure Government; see AWS GovCloud for CMMC, Azure Government for CMMC and FedRAMP Moderate cloud services.
Containers and Kubernetes
Containers don't have their own kernel, so their FIPS status depends on the host. Red Hat's documentation says the host kernel must be in FIPS mode, that fips-mode-setup doesn't work inside containers, and that installing or updating cryptographic libraries outside the package manager breaks FIPS compliance. In practice:
- Run container hosts in FIPS mode from installation.
- Use base images from the same distribution and release as the validated module.
- Treat registries, CI runners and cluster nodes that handle CUI images or data as CUI Assets.
- Log container admin actions (
kubectl,podman,docker) like any other privileged command.
How Linux gaps affect your SPRS score
A Level 2 self-assessment starts at 110 points and subtracts each NOT MET requirement's value from 32 CFR 170.24. Under 32 CFR 170.21, Conditional Level 2 (Self) status with open items requires a score of at least 88 (0.8 of 110), only 1-point items on the POA&M (plus 3.13.11 when encryption is used but isn't FIPS-validated), none from the excluded list, and closeout within 180 days.
| Linux gap | Requirement | Points lost | Can it go on a POA&M for Conditional status? |
|---|---|---|---|
| Shared root password, no named accounts | AC.L2-3.1.1 and AU.L2-3.3.2 | 5 + 3 | No |
Everyone has sudo ALL | AC.L2-3.1.5 | 3 | No |
| No MFA for SSH or admin access | IA.L2-3.5.3 | 3 or 5 | No |
| auditd off or logs stay on the host | AU.L2-3.3.1 | 5 | No |
| No documented baseline or STIG/CIS scan | CM.L2-3.4.1 and 3.4.2 | 5 + 5 | No |
| End-of-life distribution with no patches | SI.L2-3.14.1 | 5 | No |
| No malware protection on a CUI file server | SI.L2-3.14.2 | 5 | No |
| SSH or TLS working, but not FIPS-validated | SC.L2-3.13.11 | 3 | Yes, this is the one 3-point exception |
| No encryption for CUI leaving the boundary | SC.L2-3.13.11 | 5 | No |
| No idle session timeout | AC.L2-3.1.11 | 1 | Yes |
| Logs not protected from admins | AU.L2-3.3.8 | 1 | Yes |
| LUKS not used on CUI storage | SC.L2-3.13.16 | 1 | Yes |
The SPRS score guide explains how the score is posted, and how to improve your SPRS score shows which fixes move it most.
Evidence to keep for Linux systems
Your Affirming Official signs off on the score, and DoD can still run government-led assessments during the suspension. Keep evidence you could hand over.
| Evidence | What it proves |
|---|---|
| Asset inventory with distribution, release and asset category for each Linux host | You know what's in scope |
CMVP certificate numbers for the modules in use, plus fips_enabled output | Cryptography is validated and in approved mode |
/etc/sudoers and sudoers.d files, plus the admin account list | Least privilege is enforced |
| SSH and PAM configuration showing MFA | Privileged and network access use MFA |
audit rules, auditd.conf and sample events showing auid | Logs exist and trace to people |
| SCAP or CIS scan report and the list of deliberate exceptions | Baseline is defined and applied |
| Patch history and vulnerability scan results | Flaws are fixed on time |
| Malware agent status for each host | Malicious code protection is in place |
| Cloud provider's FedRAMP listing and responsibility matrix | The cloud rule is met |
| SSP section describing Linux hosts and their roles | Scope decisions are documented |
The CMMC Level 2 documentation checklist shows where these fit in your SSP.
Step by step: making Linux CMMC ready
- Inventory every Linux host. Include servers, workstations, VMs, container hosts and embedded Linux in test or shop equipment. Record the distribution and exact release.
- Assign asset categories. Decide which hosts are CUI Assets, Security Protection Assets, Contractor Risk Managed Assets or Specialized Assets.
- Check the crypto. For each CUI host, find the active CMVP certificate for its OpenSSL module and any other module it uses. If there isn't one, plan a migration.
- Turn on FIPS mode. For new systems, install in FIPS mode. Test databases, Samba and older clients first.
- Fix accounts. Disable direct root login, give every admin a named account and narrow sudo rules.
- Add MFA. Cover SSH for everyone and local admin access.
- Configure auditd and forward logs. Use STIG-based rules, make them immutable and send logs to a central tool.
- Apply a baseline. Scan against a STIG, CIS or NIST 800-171 profile and record exceptions.
- Patch and scan. Move off end-of-life releases, set a patch schedule and run authenticated vulnerability scans.
- Document it. Update the SSP, network diagram and POA&M, then re-score.
What the CMMC suspension changes for Linux
The suspension changed the assessment type. The Linux requirements stayed the same. On July 13, 2026 the Department of War suspended the move to CMMC Phase II. The implementing memo says requiring activities may include only CMMC Level 1 (Self) or Level 2 (Self) and may not designate Level 2 (C3PAO) or Level 3 (DIBCAC) (suspension memo, PDF). The DoD CIO CMMC page still says that "All Phase I self-assessment requirements remain firmly in place" and that the suspension "does not eliminate the requirement for companies to protect information in accordance with DFARS clause 252.204-7012." Class Deviation 2026-O0025, Revision 3, dated September 3, 2026, tells contracting officers to remove or revise CMMC requirements to match, and newer contracts may show 7012 dated (JUN 2026)(DEVIATION 2026-O0025). As of November 19, 2026, no restart date has been announced. CMMC phases tracks the status.
| Item | Status on November 19, 2026 | Source |
|---|---|---|
| Level 2 (Self) in new contracts | Allowed | Suspension memo; Class Deviation 2026-O0025, Revision 3 |
| Level 2 (C3PAO) designations | Not allowed during the suspension | Suspension memo |
| All 110 requirements for Linux hosts that handle CUI | Still part of Level 2 | 32 CFR 170; NIST SP 800-171 Rev 2 |
| FIPS-validated cryptography for CUI | Still required | NIST SP 800-171 Rev 2, 3.13.11 |
| FedRAMP Moderate rule for cloud-hosted Linux with CUI | Still in force | DFARS 252.204-7012; 32 CFR 170.16 |
| Government-led assessments | May still happen | DoD CIO CMMC page |
NIST SP 800-171 Revision 3 was published in May 2024, but 32 CFR 170 is built on Revision 2 and DoD says it is enforcing Revision 2 during the suspension. Score your Linux systems against Revision 2 unless your contract says otherwise. See NIST 800-171 Rev 2 vs Rev 3.
What it costs
Linux subscription, migration and tooling costs vary too much by host count, distribution and support tier for us to publish a reliable range, and we don't quote prices we can't source. These are the drivers that move the number.
| Cost driver | Why it matters |
|---|---|
| Moving off CentOS, Debian or another release without validated modules | Rebuilding servers and retesting applications takes the most time |
| Commercial subscriptions for validated packages | Ubuntu Pro, RHEL, SUSE, CIQ and TuxCare FIPS packages are paid offerings |
| Reinstalling hosts in FIPS mode | Red Hat recommends enabling FIPS at installation, so some hosts need a rebuild |
| MFA for SSH and console | Hardware tokens or an identity service |
| Central logging | SIEM or log service fees often scale with volume |
| EDR agents for Linux | Per-host licensing |
| SSP, baseline scans and evidence | Internal hours or consultant time |
For the assessment itself, DoD's final rule estimates $34,277 for a small entity's Level 2 self-assessment and affirmation and $37,196 over three years (CMMC final rule, 89 FR 83092). Those figures assume the requirements are already in place, so Linux remediation costs extra.
Common Linux mistakes with CMMC
- Assuming any Linux with AES is fine. The module has to hold an active CMVP certificate and run in FIPS mode.
- Copying a certificate number from an old vendor page. Certificates get replaced and sunset; open the CMVP page.
- Running community Rocky or AlmaLinux and citing the commercial certificate. The certificate covers the vendor's supported packages.
- Flipping FIPS mode on a running RHEL server and calling it done. Red Hat says that doesn't guarantee compliance.
- Building a new enclave on RHEL 8 or Ubuntu 20.04. Their OpenSSL modules are FIPS 140-2, and NIST's cutoff for using 140-2 modules in new systems was September 21, 2026.
- Sharing the root password. It breaks unique identification, least privilege and audit traceability at once.
- Forgetting local admin MFA. 3.5.3 covers local access to privileged accounts as well as SSH.
- Leaving logs on the host. An attacker with root can erase them.
- Ignoring embedded Linux in shop equipment. Document it as a Specialized Asset instead of leaving it off the inventory.
Which provider category fits
| If you need | Provider category | Start here |
|---|---|---|
| A scope decision and SSP language for Linux hosts | Readiness consultant or RPO | CMMC consultant |
| Ongoing patching, logging, MFA and hardening for Linux servers | Managed service provider | CMMC for IT MSPs |
| A ready-made CUI environment instead of rebuilding servers | CUI enclave provider | CUI enclave providers |
| Linux servers in a government cloud | Cloud or MSP partner with GovCloud or Azure Government experience | AWS GovCloud for CMMC |
| Help closing open items after a self-assessment | Remediation provider | CMMC remediation services |
The CMMC provider categories page explains how these differ. Find My CMMC Path is free; we may receive a referral fee from providers, and providers can't pay for placement in a recommendation.
CMMC Linux compliance: FAQ
Can I use Linux for CUI under CMMC?
Yes. Linux can meet all 110 Level 2 requirements if you use a release with an active FIPS 140-3 module, run it in FIPS mode, and configure accounts, MFA, logging, hardening and patching like any other CUI system.
Why can't some Linux distros be used for a CUI enclave?
Because NIST SP 800-171 requirement 3.13.11 requires FIPS-validated cryptography when encryption protects CUI, and the module itself must hold a NIST certificate. On November 19, 2026 we found no active certificate with Debian or CentOS in the module name, and CentOS Linux 7 also stopped getting patches on June 30, 2024.
Which Linux distributions are FIPS 140-3 validated?
On November 19, 2026, active FIPS 140-3 OpenSSL certificates covered RHEL 9, Ubuntu 22.04 and 24.04, SUSE Linux Enterprise, Oracle Linux 9, Rocky Linux 8 and 9 (from CIQ), AlmaLinux 9 (from TuxCare) and Amazon Linux 2023. Check the CMVP site for your exact release before relying on it.
Is RHEL 8 still OK for CMMC?
Existing RHEL 8 systems can stay, but plan to move. Its OpenSSL certificate (#4642) is FIPS 140-2 and on the Historical list. NIST's CMVP supports Historical modules for existing systems, but its cutoff for using 140-2 modules in new systems was September 21, 2026. For new CUI systems, use RHEL 9 or another release with an active FIPS 140-3 OpenSSL module.
Is RHEL 10 FIPS validated?
Not yet, as of November 19, 2026. RHEL 10 kernel and GnuTLS modules were on NIST's Implementation Under Test list, and Red Hat listed the RHEL 10.0 OpenSSL module as pending an operational environment update.
Does Ubuntu need Ubuntu Pro for CMMC?
For FIPS, yes. Canonical's FIPS packages come through Ubuntu Pro, enabled with sudo pro enable fips-updates. Ubuntu 20.04 also needs Ubuntu Pro for security updates after May 2025.
Do I need MFA for sudo?
IA.L2-3.5.3 requires MFA for local and network access to privileged accounts. If admins reach the host over SSH with MFA and then use sudo, the network access is covered. Local console access to an admin account needs MFA too.
Is auditd enough for CMMC logging?
auditd creates the records, but Level 2 also requires reviewing and correlating logs (3.3.5), alerting on logging failures (3.3.4) and protecting logs (3.3.8). Most companies forward auditd output to a central log tool to meet those.
Do I have to apply the DISA STIG to every Linux server?
No. CMMC requires a documented baseline and enforced security settings, not a specific benchmark. A STIG, a CIS benchmark or the SCAP Security Guide NIST 800-171 profile can all serve as the baseline if you apply it and document exceptions.
Does the CMMC suspension mean I can wait on Linux changes?
No. The suspension stopped Level 2 (C3PAO) and Level 3 designations, but Level 2 (Self) assessments, annual affirmations and DFARS 252.204-7012 still apply, and DoD says it is enforcing NIST SP 800-171 Rev 2 through self-assessments and select government-led assessments.
What we verified
On November 19, 2026 we opened each source linked on this page: the DoD CIO CMMC page, the July 13, 2026 suspension memo, Class Deviation 2026-O0025 Revision 3, 32 CFR 170.16, 170.19, 170.21 and 170.24 on eCFR (current through November 17, 2026), DFARS 252.204-7012, NIST SP 800-171 Revision 2, NIST SP 800-171A, the CMMC Assessment Guide for Level 2, every CMVP certificate in the tables, NIST's Implementation Under Test and Modules In Process lists (both last updated November 19, 2026), NIST's CMVP main page and FIPS 140-3 transition page, Red Hat's FIPS compliance page and RHEL 9 documentation on FIPS mode, configuration scanning and auditing, Canonical's FIPS and release cycle documentation, the CentOS project's end-of-life notices, the FedRAMP Marketplace listings in the cloud table (Marketplace data last changed November 16, 2026) and the CMMC final rule cost estimates. The Debian and CentOS checks searched CMVP module names for active certificates. We did not test any distribution, and certificate status, support dates and Marketplace listings can change.
Sources
- DoD CIO, About CMMC
- Implementing the DoW CIO's Suspension of CMMC Phase 2 Requirements, memo 26-P-1023 (July 13, 2026)
- Class Deviation 2026-O0025, Revision 3 (September 3, 2026)
- 32 CFR 170.16, CMMC Level 2 self-assessment
- 32 CFR 170.19, CMMC scoping
- 32 CFR 170.21, Plan of Action and Milestones requirements
- 32 CFR 170.24, CMMC Scoring Methodology
- DFARS 252.204-7012
- NIST SP 800-171 Rev 2 (PDF)
- NIST SP 800-171A, Assessing Security Requirements for CUI
- NIST SP 800-171 Rev 3 (May 2024)
- CMMC Assessment Guide, Level 2 (PDF)
- NIST Cryptographic Module Validation Program
- NIST CMVP, FIPS 140-3 transition
- NIST CMVP, Implementation Under Test list
- NIST CMVP, Modules In Process list
- Red Hat, FIPS 140-2 and FIPS 140-3 compliance
- Red Hat, RHEL 9: Switching RHEL to FIPS mode
- Red Hat, RHEL 9: Scanning the system for configuration compliance
- Red Hat, RHEL 9: Auditing the system
- Red Hat, Enterprise Linux life cycle
- Canonical, How to manage FIPS (Ubuntu Pro Client)
- Canonical, Overview of FIPS-certified modules
- Canonical, Ubuntu release cycle
- CentOS project, End dates for CentOS Stream 8 and CentOS Linux 7
- CentOS project, CentOS Linux end of life
- FedRAMP Marketplace
- CMMC Program final rule, 89 FR 83092 (October 15, 2024)