Anchore STIG Profiles Release Notes - 2026-11-03
Anchore STIG Profiles - 2026-11-03
The profile-inputs.yaml files for the RHEL 8 and RHEL 9 profiles are corrected. The profiles themselves are unchanged. The update was published through the Anchore Data Service on 2026-11-03. Anchore Enterprise deployments receive it at their next feed sync. Air-gapped deployments receive it when they next download and import the datasets.
The files had outdated values that gave some wrong results. This affected evaluations that used rhel8/profile-inputs.yaml or rhel9/profile-inputs.yaml as an inputs file, for example with --stig-input-file. Evaluations run without an inputs file used the profiles’ built-in defaults, which already have the corrected values, and were not affected.
Corrected Inputs
| Input | Profiles | Old value | New value |
|---|---|---|---|
lockout_time | rhel8, rhel9 | 604800 | 0 |
days_of_inactivity | rhel8, rhel9 | 0 | 35 |
exempt_home_users | rhel8, rhel9 | [] | ["root"] |
non_removable_media_fs | rhel8, rhel9 | File system types (xfs, ext4, swap, tmpfs) | Mount points (/, /tmp, none, /home, /tmpfs) |
system_activity_timeout | rhel8 | 600 | 900 |
mail_package | rhel8 | postfix | mailx |
remove_xorg_x11_server_packages | rhel8 | 1 package | 4 packages |
rpm_gpg_file | rhel8 | CentOS key file | Red Hat key file |
The corrected non_removable_media_fs and system_activity_timeout values do not change results for container images: no rhel8 control reads system_activity_timeout, and the controls that read non_removable_media_fs are Not Applicable to containers.
rhel8 SV-230337 and SV-256974 and rhel9 SV-258057 appear under both Fixed: Wrong Failures and Fixed: Wrong Passes: with the old values, these checks failed images that met the STIG and passed images that did not.
Fixed: Wrong Failures
rhel8SV-256973 looked for a CentOS key file, which RHEL 8 images do not have, so it failed on every RHEL 8 image evaluated with the oldrhel8/profile-inputs.yaml. It now checks the Red Hat key file.rhel8SV-230373 andrhel9SV-258049 failed on images that disable accounts after 35 days of inactivity, as the STIG requires. They now accept up to 35 days.rhel8SV-230337 andrhel9SV-258057 failed on images that keep accounts locked until an administrator unlocks them (unlock_time = 0), as the STIG requires. They now require that setting.rhel8SV-256974 checked forpostfix, so it failed on images withoutpostfix, including images that have themailxpackage that the STIG names. It now checks formailx.rhel8SV-230317 andrhel9SV-258050 also checkedroot’s initialization files, which the STIG check does not cover, so they could fail onroot’sPATHsettings. They now skiproot.
Fixed: Wrong Passes
rhel8SV-244531 and SV-244532 skipped every user, so they passed without checking anything. They now check the files in users’ home directories.rhel8SV-230553 checked 1 of the 4 X server packages that must not be installed. It now checks all 4.rhel8SV-230337 andrhel9SV-258057 passed on images that unlock accounts automatically after 7 days (unlock_time = 604800). They now fail there.rhel8SV-256974 passed on images withpostfixinstead ofmailx. It now fails there.
Update and Rescan
- If you pass the shipped
profile-inputs.yamlwith--stig-input-file, runanchorectl stig write-profilesagain after your deployment has synced the update, then rescan RHEL 8 and RHEL 9 images. - If you keep your own inputs file, check it against the table above.
- To see which commands replace an image’s existing evaluation, see Managing STIG Evaluations.