Configure a PostgresSQL 12 machine to be CIS compliant
Join us on our Discord Server to ask questions, discuss features, or just chat with other Ansible-Lockdown users.
This role will make changes to the system which may have unintended consequences. This is not an auditing tool but rather a remediation tool to be used after an audit has been conducted.
Check Mode is not supported! The role will complete in check mode without errors, but it is not supported and should be used with caution. The POSTGRES-12-CIS role or a compliance scanner should be used for compliance checking over check mode.
This role was developed against a clean install of the Application. If you are implementing to an existing system please review this role for any site specific changes that are needed.
To use release version please point to main branch and relevant release for the cis benchmark you wish to work with.
The control found in defaults main also need to reflect this as this control the testing that takes place if you are using the audit component.
CIS release always contains changes, it is highly recommended to review the new references and available variables. This have changed significantly since Ansible-Lockdown initial release.
This is now compatible with python3 if it is found to be the default interpreter. This does come with pre-requisites which it configures the system accordingly.
Further details can be seen in the Changelog
- Read The Docs
- Getting Started
- Customizing Roles
- Per-Host Configuration
- Getting the Most Out of the Role
- Postgres12x
- ansible 2.10.1
- jmespath
- relevant collections
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 consequences in a live production system. Also familiarize yourself with the variables in the defaults/main.yml file.
Technical Dependencies:
- Python3
- Ansible 2.10+
- python-def (should be included in RHEL 9)
- libselinux-python
- pip packages
- jmespath ( complete list found in requirements )
- collections found in collections/requirements.yml
This role is designed that the end user should not have to edit the tasks themselves. All customizing should be done by overriding the required variables as found in defaults/main.yml file. e.g. using inventory, group_vars, extra_vars
There are many tags available for added control precision. Each control has it's own set of tags noting what level, if it's a patch or audit, and the rule number.
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 services, this task will be skipped. The opposite can also happen where you run only controls tagged with services.
tags:
- level1-postgresql
- audit
- rule_1.1We 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.