Menü
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-aws-foundations-5-3Der Befehl bleibt in einer Zeile. Scrollen Sie horizontal, um ihn vor dem Kopieren vollständig zu prüfen.
Sie bevorzugen eine lokale Kopie? Laden Sie die Dateien herunter, die SkillsMP derzeit vorliegen.
Basierend auf der SOC-Berufsklassifikation
SKILL.md wird angezeigt
| name | cis-aws-foundations-5.3 |
| description | Ensure usage of the 'root' account is monitored |
| category | cis-monitoring |
| version | 7.0.0 |
| author | cyberstrike-official |
| tags | ["cis","aws","monitoring","cloudwatch","cloudtrail","metric-filters","alarms","root-account"] |
| cis_id | 5.3 |
| cis_benchmark | CIS AWS Foundations Benchmark v7.0.0 |
| tech_stack |
| ["aws"] |
| cwe_ids | [] |
| chains_with | ["cis-aws-foundations-4.1","cis-aws-foundations-4.2"] |
| prerequisites | [] |
| severity_boost | {} |
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.
N/A
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:
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"
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>
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>
IncludeManagementEvents set to true and ReadWriteType set to All<trail-log-group-name> captured in step 1:aws logs describe-metric-filters --log-group-name <trail-log-group-name>
"filterPattern": "{ $.userIdentity.type = "Root" && $.userIdentity.invokedBy NOT EXISTS && $.eventType != "AwsServiceEvent" }"
Note the <root-usage-metric> value associated with the filterPattern from step 3.
Get a list of CloudWatch alarms, and filter on the <root-usage-metric> captured in step 4:
aws cloudwatch describe-alarms --query 'MetricAlarms[?MetricName==<root-usage-metric>]'
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>
arn:aws:sns:<region>:<account-id>:<sns-topic-name>:<subscription-id>A metric filter exists with the filter pattern matching root account usage, a CloudWatch alarm is configured for the metric, and the alarm has an active SNS topic with at least one subscriber.
If you are using CloudTrail trails and CloudWatch, perform the following steps to set up the metric filter, alarm, SNS topic, and subscription:
<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.
aws sns create-topic --name <sns-topic-name>
aws sns subscribe --topic-arn <sns-topic-arn> --protocol <sns-protocol> --notification-endpoint <sns-subscription-endpoints>
aws cloudwatch put-metric-alarm --alarm-name `<root-usage-alarm>` --metric-name `<root-usage-metric>` --statistic Sum --period 300 --threshold 1 --comparison-operator GreaterThanOrEqualToThreshold --evaluation-periods 1 --namespace 'CISBenchmark' --alarm-actions <sns_topic_arn>
By default, no CloudWatch metric filters or alarms exist to monitor root account activity. Root usage is logged in CloudTrail, but proactive monitoring must be configured.
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v8 | 8.5 Collect Detailed Audit Logs | x | x | |
| v8 | 8.11 Conduct Audit Log Reviews | x | x | |
| v7 | 4.9 Log and Alert on Unsuccessful Administrative Account Login | x | x | |
| v7 | 6.3 Enable Detailed Logging | x | x |
Level 1 | Manual