tenable/audit_scripts

Scripts to help work with configuration audit files

audit_scripts's Issues

Use Skip instead of Pass

Would it be possible to give users the ability to call out how audit exceptions are marked? For example, instead of always marking prior Failed items as Passed allow the use the Skipped option? Based off the HTML reports from Tenable IO, I am assuming Skipped it an potential option outside of the normal Passed or Failed.

Applying values issue

I am getting the following issue when the baseline script starts applying values:

Applying values
Applying values for _xx.xx.xx.xx_

The command '/bin/grep -E '^[\s]*install cramfs /bin/true' /etc/modprobe.d/* |/usr/bin/awk '{print} END {if (NR != 0) print "pass" ; else print "fail"}'' returned :

/etc/modprobe.d/CIS.conf:install cramfs /bin/true
pass

Parse error with generated Audit file

Recently I've been having issues with with the audit files that this script generated. If I export a scan from Nessus Pro and use it with the Red Hat EL 8 v2 L1 audit file, the resulting file will give me a parsing error with the following Text:

"Parse error line 771 - unknown token ‘$grubdir/user.cfg\“\”;’Could not parse the file 73c86e31-9a1f-54bc-949a-16cae5563d66-54093435-scfile_6zxUFn".

Additionally, The specified line does not line up with where the actual problem lies. I have done some digging and it appears that this may be an error with the escape characters within the file. In the provided example, I need to add an additional '' to the two on the tail end of the unknown token '$grubdir/user.cfg\\“\”;’ . Adding this additional backslash will allow the script to continue further on.

Thank you very much for your help

CIS MS_Server_2016_L1_V1 2.3.7.4

Hello,

I am noticing that when running the script, the output .audit file is not making correct exception for one of my CIS MS_Server_2016_L1_V1 audit controls. The specific control is "2.3.7.4 Configure 'Interactive logon: Message text for users attempting to log on". What is also odd is that the similar control 2.3.7.5 does not fail but 2.3.7.4 does. Anyway to have this corrected?

Python 2.7.5 support?

We tried running the script on our Tenable.sc v5.7.1 on-prem host, which has Python 2.7.5 installed. Changed the #! line to '#!/usr/bin/env python' and we get a syntax error:

  File "./create_baseline_audit.py", line 89
    print(message, file=out)
                       ^
SyntaxError: invalid syntax

I'm not a python coder, so just curious if this is something simple to address to allow the script to run on older python versions. Or can we install python3 on the host without impacting Tenable.sc functions.