Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overall Review of Changes:
The correct syntax for auditd rules is -a action,filter.
The CIS Benchmark is inconsistent on this between remediation and verification on 32 vs 64 bit and the -F typo appears to have come from a line wrap issue with the CIS Benchmark example.
The rest of this same file uses
-a always,exit
except these two lines, and the AMAZON2-CIS-Audit tests also check for the correct-a always,exit
https://github.com/ansible-lockdown/AMAZON2-CIS-Audit/blob/devel/section_4/cis_4.1/cis_4.1.15.yml
I also found this discussion from 2014 about the ordering:
https://listman.redhat.com/archives/linux-audit/2014-April/009031.html
How has this been tested?:
We have run it against an Amazon Linux 2 EC2 instance and then ran the AMAZON2-CIS-Audit repo tests against it.