You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What I expected to happen: apiclient report cis -l 2 reports PASS on 3.4.1.2 and 3.4.2.2. Because the iptables output is correct according to the CIS benchmark guide.
bash-5.2# ip6tables -L INPUT -v -n
Chain INPUT (policy DROP 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
0 0 ACCEPT all -- lo * ::/0 ::/0
0 0 DROP all -- * * ::1 ::/0
bash-5.2# ip6tables -L OUTPUT -v -n
Chain OUTPUT (policy DROP 4 packets, 224 bytes)
pkts bytes target prot opt in out source destination
0 0 ACCEPT all -- * lo ::/0 ::/0
What actually happened: apiclient report cis -l 2 -f json reports FAIL on 3.4.1.2 and 3.4.2.2.
How to reproduce the problem:
Get aws-dev variant, add a new service to execute the following. Build the AMI, start an instance and run apiclient report cis -l 2.
ExecStartPre=/sbin/iptables -A INPUT -i lo -j ACCEPT
ExecStartPre=/sbin/iptables -A OUTPUT -o lo -j ACCEPT
ExecStartPre=/sbin/iptables -A INPUT -s 127.0.0.0/8 -j DROP
ExecStartPre=/sbin/ip6tables -A INPUT -i lo -j ACCEPT
ExecStartPre=/sbin/ip6tables -A OUTPUT -o lo -j ACCEPT
ExecStartPre=/sbin/ip6tables -A INPUT -s ::1 -j DROP
The text was updated successfully, but these errors were encountered:
Package I'm using:
bloodhound
What I expected to happen:
apiclient report cis -l 2
reports PASS on 3.4.1.2 and 3.4.2.2. Because the iptables output is correct according to the CIS benchmark guide.What actually happened:
apiclient report cis -l 2 -f json
reports FAIL on 3.4.1.2 and 3.4.2.2.How to reproduce the problem:
Get aws-dev variant, add a new service to execute the following. Build the AMI, start an instance and run
apiclient report cis -l 2
.The text was updated successfully, but these errors were encountered: