-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CIS v1.4.0 - Control: 3.1 Ensure CloudTrail is enabled in all regions #408
Comments
@Sirbank Appreciate the feedback! I will take a look; meanwhile, if you have any recommendations to change the query, happy to see that 👍 |
@Sirbank, thanks for waiting; here are some analysis updates There are two problem statements, [1] - when we have no trail or current query, CTE block does not return, and the control runs to render no data. Hence, the CIS control does not answer what it is intended to do. As @vkumbha raised above and you also observed the same. The proposed query for [1] (not finalised)
[2] - Even if we tried to address the issue [1] by changing the query to evaluate based on regions, the control works to result in data; however, it fails to fetch data for The OBSERVATION is
So we have been playing to accurate the solution; however, we see some anomalies in the AWS SDK response I know it's an extended response; sorry for that. Meanwhile, I see your screenshot has one trail listed, even though the control listed zero results. Can you help share the details as per the below query? This will help to understand your trail setting for the current account. select event_selectors, name, is_multi_region_trail, home_region, region from aws_cloudtrail_trail |
@rajlearner17 Here the query as you mention sir. |
@Sirbank, I see the |
@rajlearner17 this is my setting on AWS Management Console. |
@Sirbank THANKS, this will help. We will be investigating the behaviour If you update the and the below query is expected to evaluate properly for all regions for CIS control. Again this is an alternative for now
The outcome, if there is no trail in the account and If there is one global trial is set as shown in your image, it will render as below |
@Sirbank hope you are doing well.
|
Describe the bug
When there are no trails in the account, the control should throw ALARM.
Steampipe version (
steampipe -v
)steampipe version 0.13.0 (I know I am on an outdated version :p)
Plugin version (
steampipe plugin list
)aws@latest - 0.63.0
To reproduce
steampipe check control.cis_v140_3_1
Expected behavior
CIS v1.4 - 3.1 control expects a multi-regions trail with logging enabled, in our case since there are no trails to begin with, this should go to ALARM. However, as of today this says (idk how to interpret 0/0 for everything, but for sure) not alarm.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: