Deviations from the Security Technical Implementation Guide (STIG)¶
The ansible-hardening role deviates from some of the STIG’s requirements when a security control could cause significant issues with production systems. The role classifies each control into an implementation status and provides notes on why a certain control is skipped or altered.
The following provides a brief overview of each implementation status:
If a control requires manual intervention outside the host, or if it could cause significant harm to a host, it will be skipped and listed as an exception. All controls in this category are not implemented in Ansible.
- Configuration Required
These controls require some type of initial configuration before they can be applied. Review the notes for each control to determine how to configure each of them.
These controls are fully implemented and they may have configurations which can be adjusted. The notes for each control will identify which configuration options are available.
The controls in the opt-in list are implemented in Ansible, but are disabled by default. They are often disabled because they could cause harm to a subset of systems. Each control has notes that explains the caveats of the control and how to enable it if needed.
Deployers should review the full list of controls sorted by implementation status.
All of the default configurations are found within