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
{{ message }}
This repository has been archived by the owner on Jul 22, 2021. It is now read-only.
The create-benchmark-rules.yaml template creates some checks as Metrics and some as Events. The ones created as Events do not seem to satisfy the CIS Benchmark requirements, at least as they are coded in the aws-cis-foundation-benchmark-checklist.py script.
So, my first question is, is having an Event instead of a Metric/Alarm for certain checks (3.8 and 3.9 are examples) actually violations of the Benchmark? If they are violations, is it possible to construct those as Metric/Alarm combinations instead of Events? If they are not violations, is there a way to modify the script to check for Events for these particular rules?
The text was updated successfully, but these errors were encountered:
Hello,
The create-benchmark-rules.yaml template creates some checks as Metrics and some as Events. The ones created as Events do not seem to satisfy the CIS Benchmark requirements, at least as they are coded in the aws-cis-foundation-benchmark-checklist.py script.
So, my first question is, is having an Event instead of a Metric/Alarm for certain checks (3.8 and 3.9 are examples) actually violations of the Benchmark? If they are violations, is it possible to construct those as Metric/Alarm combinations instead of Events? If they are not violations, is there a way to modify the script to check for Events for these particular rules?
The text was updated successfully, but these errors were encountered: