Configure a Cisco IOS L2 Switch to be DISA STIG compliant. All findings will be audited by default. Non-disruptive CAT I, CAT II, and CAT III findings will be corrected by default. Disruptive finding remediation can be enabled by setting iosl2sstig_disruption_high
to yes
.
This role is based on Cisco IOS L2S DISA STIG: Version 2, Release: 2 Released On Jul 23 2021.
On our Discord Server to ask questions, discuss features, or just chat with other Ansible-Lockdown users
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.
General:
-
Basic knowledge of Ansible, below are some links to the Ansible documentation to help get started if you are unfamiliar with Ansible
-
Functioning Ansible and/or Tower Installed, configured, and running. This includes all of the base Ansible/Tower configurations, needed packages installed, and infrastructure setup.
-
Please read through the tasks in this role to gain an understanding of what each control is doing. Some of the tasks are disruptive and can have unintended consiquences in a live production system. Also familiarize yourself with the variables in the defaults/main.yml file or the Main Variables Wiki Page.
- Repo GitHub Page
- Getting Started
- Customizing Roles
- Per-Host Configuration
- Getting the Most Out of the Role
- Wiki
The following packages must be installed on the controlling host/host where ansible is executed:
- python2-passlib (or just passlib, if using python3)
- python-jmespath
Package 'python-xmltodict' is required if you enable the OpenSCAP tool installation and run a report. Packages python(2)-passlib and python-jmespath are required for tasks with custom filters or modules. 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. These variables can be found here in the Main Variables Wiki page. All variables are listed there along with descriptions.
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:
- CISC-L2-000010
- ip_interfaces
- motd_banner
- 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
- gh_pages - github pages
- all other branches - Individual community member branches
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.