mirror of
https://github.com/ansible-lockdown/RHEL9-CIS.git
synced 2025-12-27 23:43:06 +00:00
updates for audit section
Signed-off-by: Mark Bolwell <mark.bollyuk@gmail.com>
This commit is contained in:
parent
f83e73c1a1
commit
05fee15cb4
5 changed files with 74 additions and 92 deletions
|
|
@ -67,74 +67,56 @@ skip_reboot: true
|
|||
# default value will change to true but wont reboot if not enabled but will error
|
||||
change_requires_reboot: false
|
||||
|
||||
##########################################
|
||||
###########################################
|
||||
### Goss is required on the remote host ###
|
||||
## Refer to vars/auditd.yml for any other settings ##
|
||||
#### Basic external goss audit enablement settings ####
|
||||
#### Precise details - per setting can be found at the bottom of this file ####
|
||||
### vars/auditd.yml for other settings ###
|
||||
|
||||
## Audit setup
|
||||
# Audits are carried out using Goss. This variable
|
||||
# determines whether execution of the role prepares for auditing
|
||||
# by installing the required binary.
|
||||
# Allow audit to setup the requirements including installing git (if option chosen and downloading and adding goss binary to system)
|
||||
setup_audit: false
|
||||
|
||||
## Enable audits to run - this runs the audit and get the latest content
|
||||
# This variable governs whether the audit using the
|
||||
# separately maintained audit role using Goss
|
||||
# is carried out.
|
||||
# enable audits to run - this runs the audit and get the latest content
|
||||
run_audit: false
|
||||
# Run heavy tests - some tests can have more impact on a system enabling these can have greater impact on a system
|
||||
audit_run_heavy_tests: true
|
||||
|
||||
# Only run Audit do not remediate
|
||||
## Only run Audit do not remediate
|
||||
audit_only: false
|
||||
# This will enable files to be copied back to control node(part of audit_only)
|
||||
### As part of audit_only ###
|
||||
# This will enable files to be copied back to control node in audit_only mode
|
||||
fetch_audit_files: false
|
||||
# Path to copy the files to will create dir structure(part of audit_only)
|
||||
# Path to copy the files to will create dir structure in audit_only mode
|
||||
audit_capture_files_dir: /some/location to copy to on control node
|
||||
#############################
|
||||
|
||||
## How to retrieve audit binary(Goss)
|
||||
# Options are 'copy' or 'download' - detailed settings at the bottom of this file
|
||||
# - if 'copy':
|
||||
# - the filepath mentioned via the below 'audit_bin_copy_location' var will be used to access already downloaded Goss
|
||||
# - if 'download':
|
||||
# - the GitHub Goss-releases URL will be used for a fresh-download, via 'audit_bin_url' and 'audit_pkg_arch_name' vars
|
||||
# How to retrieve audit binary
|
||||
# Options are copy or download - detailed settings at the bottom of this file
|
||||
# you will need to access to either github or the file already dowmloaded
|
||||
get_audit_binary_method: download
|
||||
|
||||
## if get_audit_binary_method is 'copy', the following var needs to be updated for your environment
|
||||
## if get_audit_binary_method - copy the following needs to be updated for your environment
|
||||
## it is expected that it will be copied from somewhere accessible to the control node
|
||||
## e.g copy from ansible control node to remote host
|
||||
audit_bin_copy_location: /some/accessible/path
|
||||
|
||||
## How to retrieve the audit role
|
||||
# The role for auditing is maintained separately.
|
||||
# This variable specifies the method of how to get the audit role
|
||||
# options are git/copy/get_url other e.g. if you wish to run from already downloaded conf
|
||||
# onto the system. The options are as follows:
|
||||
# - 'git': clone audit content from GitHub REPOSITORY, set up via `audit_file_git` var, and
|
||||
# VERSION(e.g. branch, tag name), set up via `audit_git_version` var.
|
||||
# - 'copy': copy from path as specified in variable `audit_conf_copy`.
|
||||
# - 'archive': same as 'copy', only that the specified filepath needs to be unpacked.
|
||||
# - 'get_url': Download from url as specified in variable `audit_files_url`
|
||||
# how to get audit files onto host options
|
||||
# options are git/copy/archive/get_url other e.g. if you wish to run from already downloaded conf
|
||||
audit_content: git
|
||||
|
||||
# This variable(only used when 'audit_content' is 'copy' or 'archive') should
|
||||
# contain the filepath with audit-content to be copied/unarchived on server:
|
||||
audit_conf_copy: "some path to copy from"
|
||||
# If using either archive, copy, get_url:
|
||||
## Note will work with .tar files - zip will require extra configuration
|
||||
### If using get_url this is expecting github url in tar.gz format e.g.
|
||||
### https://github.com/ansible-lockdown/UBUNTU22-CIS-Audit/archive/refs/heads/benchmark-v1.0.0.tar.gz
|
||||
audit_conf_source: "some path or url to copy from"
|
||||
|
||||
# This variable(only used when 'audit_content' is 'get_url') should
|
||||
# contain the URL from where the audit-content must be downloaded on server:
|
||||
audit_files_url: "some url maybe s3?"
|
||||
# Destination for the audit content to be placed on managed node
|
||||
# note may not need full path e.g. /opt with the directory being the {{ benchmark }}-Audit directory
|
||||
audit_conf_dest: "/opt"
|
||||
|
||||
# Run heavy tests - some tests can have more impact on a system enabling these can have greater impact on a system
|
||||
audit_run_heavy_tests: true
|
||||
# Where the audit logs are stored
|
||||
audit_log_dir: '/opt'
|
||||
|
||||
# Timeout for those cmds that take longer to run where timeout set
|
||||
# This variable specifies the timeout (in ms) for audit commands that
|
||||
# take a very long time: if a command takes too long to complete,
|
||||
# it will be forcefully terminated after the specified duration.
|
||||
audit_cmd_timeout: 120000
|
||||
|
||||
### End Goss enablements ####
|
||||
### Goss Settings ##
|
||||
####### END ########
|
||||
|
||||
# These variables correspond with the CIS rule IDs or paragraph numbers defined in
|
||||
# the CIS benchmark documents.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue