lacework-global-66
Ensure a log metric filter and alarm exists for AWS Organizations changes (Automated)
Profile Applicability
• Level 1
Description
Achieve real-time monitoring of API calls by directing CloudTrail Logs to CloudWatch Logs and establishing corresponding metric filters and alarms. Best practices recommend using a metric filter and alarm for AWS Organizations changes made in the master AWS Account.
Rationale
Monitoring AWS Organizations changes can help you prevent any unwanted, accidental or intentional modifications that may lead to unauthorized access or other security breaches. This monitoring technique helps you to ensure that any unexpected changes performed within your AWS Organizations can be investigated and any unwanted changes can be rolled back.
Audit
- Perform the following to ensure that there is at least one active multi-region CloudTrail with prescribed metric filters and alarms configured:
- Identify the log group name configured for use with active multi-region CloudTrail:
- List all CloudTrails:
aws cloudtrail describe-trails
Identify Multi region CloudTrails, Trails with
"IsMultiRegionTrail"
set to trueFrom value associated with CloudWatchLogsLogGroupArn note <cloudtrail_log_group_name> Example: for CloudWatchLogsLogGroupArn that looks like
arn:aws:logs:<region>:<aws_account_number>:log-group:NewGroup:*, <cloudtrail_log_group_name>
would be NewGroupEnsure Identified Multi region CloudTrail is active:
aws cloudtrail get-trail-status --name <Name of a Multi-region CloudTrail>
Ensure IsLogging
is set to TRUE
- Ensure identified Multi-region CloudTrail captures all Management Events:
aws cloudtrail get-event-selectors --trail-name <trailname shown in describe-trails>
- Ensure there is at least one Event Selector for a Trail with
IncludeManagementEvents
set to true andReadWriteType
set toAll
.
- Get a list of all associated metric filters for this <cloudtrail_log_group_name>:
aws logs describe-metric-filters --log-group-name "<cloudtrail_log_group_name>"
- Ensure the output from the above command contains the following:
"filterPattern": "{ ($.eventSource = organizations.amazonaws.com) && (($.eventName = "AcceptHandshake") || ($.eventName = "AttachPolicy") || ($.eventName = "CreateAccount") || ($.eventName = "CreateOrganizationalUnit") || ($.eventName = "CreatePolicy") || ($.eventName = "DeclineHandshake") || ($.eventName = "DeleteOrganization") || ($.eventName = "DeleteOrganizationalUnit") || ($.eventName = "DeletePolicy") || ($.eventName = "DetachPolicy") || ($.eventName = "DisablePolicyType") || ($.eventName = "EnablePolicyType") || ($.eventName = "InviteAccountToOrganization") || ($.eventName = "LeaveOrganization") || ($.eventName = "MoveAccount") || ($.eventName = "RemoveAccountFromOrganization") || ($.eventName = "UpdatePolicy") || ($.eventName = "UpdateOrganizationalUnit")) }"
Note the
<organizations_changes>
value associated with the filterPattern found in step 3.Get a list of CloudWatch alarms and filter on the
<organizations_changes>
captured in step 4:
aws cloudwatch describe-alarms --query 'MetricAlarms[?MetricName== `<organizations_changes>`]'
Note the AlarmActions value - this will provide the SNS topic ARN value.
Ensure there is at least one active subscriber to the SNS topic:
aws sns list-subscriptions-by-topic --topic-arn <sns_topic_arn>
at least one subscription should have "SubscriptionArn" with valid aws ARN. Example of valid "SubscriptionArn":
"arn:aws:sns:<region>:<aws_account_number>:<SnsTopicName>:<SubscriptionID>"
Remediation
Perform the following to setup the metric filter, alarm, Simple Notification Service (SNS) topic, and subscription:
- Create a metric filter based on filter pattern provided which checks for AWS Organizations changes, providing a
<cloudtrail_log_group_name>
.
aws logs put-metric-filter --log-group-name <cloudtrail_log_group_name> --filter-name <organizations_changes> --metric-transformations metricName=<organizations_changes>,metricNamespace='cis_benchmark',metricValue=1 \
--filter-pattern '{ ($.eventSource = organizations.amazonaws.com) && (($.eventName = "AcceptHandshake") || ($.eventName = "AttachPolicy") || ($.eventName = "CreateAccount") || ($.eventName = "CreateOrganizationalUnit") || ($.eventName = "CreatePolicy") || ($.eventName = "DeclineHandshake") || ($.eventName = "DeleteOrganization") || ($.eventName = "DeleteOrganizationalUnit") || \
($.eventName = "DeletePolicy") || ($.eventName = "DetachPolicy") || ($.eventName = "DisablePolicyType") || ($.eventName = "EnablePolicyType") || ($.eventName = "InviteAccountToOrganization") || ($.eventName = "LeaveOrganization") || ($.eventName = "MoveAccount") || ($.eventName = "RemoveAccountFromOrganization") || ($.eventName = "UpdatePolicy") || ($.eventName = "UpdateOrganizationalUnit")) }'
You can choose your own metricName and metricNamespace strings. Use the same metricNamespace for all Foundations Benchmark metrics to group them together.
- Create an SNS topic for the alarm to notify:
aws sns create-topic --name <sns_topic_name>
You can execute this command once and then re-use the same topic for all monitoring alarms.
- Create an SNS subscription to the topic created in step 2:
aws sns subscribe --topic-arn <sns_topic_arn> --protocol <protocol_for_sns> --notification-endpoint <sns_subscription_endpoints>
You can execute this command once and then re-use the SNS subscription for all monitoring alarms.
- Create an alarm associated with the CloudWatch Logs Metric Filter created in step 1 and an SNS topic created in step 2:
aws cloudwatch put-metric-alarm --alarm-name <organizations_changes> --metric-name <organizations_changes> --statistic Sum --period 300 --threshold 1 --comparison-operator GreaterThanOrEqualToThreshold --evaluation-periods 1 --namespace 'cis_benchmark' --alarm-actions <sns_topic_arn>
You can utilize Lacework's remediation template to resolve violations of this policy. See Remediation Templates.
References
https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudwatch-alarms-for-cloudtrail.html
https://docs.aws.amazon.com/organizations/latest/userguide/orgs_security_incident-response.html