TMA-AWS-5.3
Ensure usage of the 'root' account is monitored
説明
Real-time monitoring of API calls can be achieved by directing CloudTrail Logs to CloudWatch Logs or an external Security Information and Event Management (SIEM) environment, and establishing corresponding metric filters and alarms. It is recommended that a metric filter and alarm be established for 'root' login attempts to detect unauthorized use or attempts to use the root account. CloudWatch is an AWS native service that allows you to observe and monitor resources and applications. CloudTrail logs can also be sent to an external Security Information and Event Management (SIEM) environment for monitoring and alerting. Monitoring 'root' account logins will provide visibility into the use of a fully privileged account and the opportunity to reduce its usage.
チェック方法
監査方法: 手動レビュー
この推奨事項は自動ではチェックできません。--include-manual を指定すると、スキャン結果にこの手順付きで一覧表示されます。
If you are using CloudTrail trails and CloudWatch, perform the following to ensure that there is at least one active multi-region CloudTrail trail with the prescribed metric filters and alarms configured: 1. Identify the log group name that is configured for use with the active multi-region CloudTrail trail: - List all CloudTrail trails: aws cloudtrail describe-trails - Identify multi-region CloudTrail trails: Trails with "IsMultiRegionTrail" set to true - Note the value associated with "Name":<trail-name> - Note the <trail-log-group-name> within the value associated with "CloudWatchLogsLogGroupArn" o Example: arn:aws:logs:<region>:<account-id>:log- group:<trail-log-group-name>:* - Ensure the identified multi-region CloudTrail trail is active: aws cloudtrail get-trail-status --name <trail-name> o Ensure IsLogging is set to TRUE - Ensure the identified multi-region CloudTrail trail captures all management events: aws cloudtrail get-event-selectors --trail-name <trail-name> o Ensure there is at least one event selector for a trail with IncludeManagementEvents set to true and ReadWriteType set to All 2. Get a list of all associated metric filters for the <trail-log-group-name> capt...
修正方法
修正方法: ガイダンスまたは IaC パッチ
If you are using CloudTrail trails and CloudWatch, perform the following steps to set up the metric filter, alarm, SNS topic, and subscription: 1. Create a metric filter based on the provided filter pattern that checks for 'root' account usage and uses the <trail-log-group-name> taken from audit step 1: aws logs put-metric-filter --log-group-name `<trail-log-group-name>` -- filter-name `<root-usage-metric>` --metric-transformations metricName= `<root-usage-metric>` ,metricNamespace='CISBenchmark',metricValue=1 -- filter-pattern '{ $.userIdentity.type = "Root" && $.userIdentity.invokedBy NOT EXISTS && $.eventType != "AwsServiceEvent" }' Note: You can choose your own metricName and metricNamespace strings. Using the same metricNamespace for all Foundations Benchmark metrics will group them together. 2. Create an SNS topic that the alarm will notify: aws sns create-topic --name <sns-topic-name> Note: You can execute this command once and then reuse the same topic for all monitoring alarms. Note: Capture the TopicArn that is displayed when creating the SNS topic in step 2. 3. Create an SNS subscription for the topic created in step 2: aws sns subscribe --topic-arn <sns-topic-arn> --...
プロパティ
- オペレーティングシステム
- すべて
- タグ
- awscloudmonitoring
- 参照
- CIS Amazon Web Services Foundations Benchmark v7.0.0 - 5.3 Ensure usage of the 'root' account is monitored