Rudder plugins » CIS

On control point 3.4.2.5, as we should get nothing from the command in the benchmark, we can just keep the commands without the test part and expect an exit code of 1.
(for information, the actual commands fails with following error : bash: test: =: unary operator expected).

_3_4_2_5 = hardening.Leaf {
    _item_nb = "3.4.2.5" 
    id = "c5e98ff1-a92a-423b-ab2b-abf579858075" 
    _audit_items = [
        rudder.Method {
            method = "audit_from_command" 
            params = {
                command = r"test $(nft list ruleset | grep 'hook input' | grep -v 'policy drop') = '' && test $(nft list ruleset | grep 'hook forward' | grep -v 'policy drop') = ''" 
                compliant_codes = "0" 
            }
        }
    ]
}