This role is based on RHEL 9 DISA STIG: Version 1, Rel 3 released on Apr 24, 2024.
On our Discord Server to ask questions, discuss features, or just chat with other Ansible-Lockdown users
Configure a RHEL/Rocky/Alma 9 system to be DISA STIG compliant.
Non-disruptive CAT I, CAT II, and CAT III findings will be corrected by default.
Disruptive finding remediation can be enabled by setting rhel9stig_disruption_high to true.
Coming from a previous release.
As with all releases and updates, It is suggested to test and align controls. This contains rewrites and ID reference changes as per STIG documentation.
This can be turned on or off within the defaults/main.yml file with the variable rhel7stig_run_audit. The value is false by default, please refer to the wiki for more details. The defaults file also populates the goss checks to check only the controls that have been enabled in the ansible role.
This is a much quicker, very lightweight, checking (where possible) config compliance and live/running settings.
A new form of auditing has been developed, by using a small (12MB) go binary called goss along with the relevant configurations to check. Without the need for infrastructure or other tooling. This audit will not only check the config has the correct setting but aims to capture if it is running with that configuration also trying to remove false positives in the process.
- Read The Docs
- Getting Started
- Customizing Roles
- Per-Host Configuration
- Getting the Most Out of the Role
- RHEL/Rocky/AlmaLinux/OL 9 - Other versions are not supported.
- Other OSs can be checked by changing the skip_os_check to true for testing purposes.
- Access to download or add the goss binary and content to the system if using auditing. options are available on how to get the content to the system.
The following packages must be installed on the controlling host/host where ansible is executed:
- python-lxml
- python-xmltodict
Package 'python-xmltodict' is required if you enable the OpenSCAP tool installation and run a report. These are all required on the controller host that executes Ansible.
This role is designed that the end user should not have to edit the tasks themselves. All customizing should be done via the defaults/main.yml file or with extra vars within the project, job, workflow, etc.
There are many tags available for added control precision. Each control has it's own set of tags noting the control number as well as what parts of the system that control addresses.
Below is an example of the tag section from a control within this role. Using this example if you set your run to skip all controls with the tag ssh, this task will be skipped. The opposite can also happen where you run only controls tagged with ssh.
tags:
- RHEL-9-010050
- ssh
- dod_logon_bannerThis is based on a vagrant image with selections enabled. e.g. No Gui or firewall. Note: More tests are run during audit as we check config and running state.
ok: [rocky9_efi] =>
msg:
- 'The pre remediation results are: Count: 804, Failed: 416, Duration: 6.488s.'
- 'The post remediation results are: Count: 804, Failed: 28, Duration: 68.687s.'
- Full breakdown can be found in /opt
PLAY RECAP ****************************************************************************************************************
rocky9_efi : ok=482 changed=269 unreachable=0 failed=0 skipped=207 rescued=0 ignored=0- devel - This is the default branch and the working development branch. Community pull requests will pull into this branch
- main - This is the release branch
- reports - This is a protected branch for our scoring reports, no code should ever go here
- gh_pages - github pages
- all other branches - Individual community member branches
- system_is_container
This is set to false by defaults/main.yml If discovered it is a container type or ansible_connection == docker it will convert to run to with with true. Some controls will skip is this is true as they are not applicable at all. Others runs a subset of controls found in vars/is_container.yml based on a vendor supplied un altered image.
NON altered vendor image.
- container_vars_file: is_container.yml
This vars file runs controls are grouped into tags so if the container does later have ssh it could be re-enabled by loading an alternative vars file.
We encourage you (the community) to contribute to this role. Please read the rules below.
- Your work is done in your own individual branch. Make sure to Signed-off and GPG sign all commits you intend to merge.
- All community Pull Requests are pulled into the devel branch
- Pull Requests into devel will confirm your commits have a GPG signature, Signed-off, and a functional test before being approved
- Once your changes are merged and a more detailed review is complete, an authorized member will merge your changes into the main branch for a new release.
uses:
- ansible-core 2.12
- ansible collections - pulls in the latest version based on requirements file
- runs the audit using the devel branch
- This is an automated test that occurs on pull requests into devel
STIG Control
- RHEL-09-211035 rngd service - this is replaced if running FIPS see https://bugzilla.redhat.com/show_bug.cgi?id=2208049
This is a community project at its core and will be managed as such.
If you would are interested in dedicated support to assist or provide bespoke setups
This repo originated from work done by Sam Doran
- makefile - this is there purely for testing and initial setup purposes.
- pre-commit can be tested and can be run from within the directory
pre-commit run