Menú
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-aws-foundations-5-1El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.
¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.
macOS post-exploitation for credential harvesting, DTrace monitoring, TCC bypass, and stealth operations via native tools
Windows userland post-exploitation for credential harvesting, monitoring, AMSI/ETW bypass, and stealth operations
Kubernetes post-exploitation for container escape, secret extraction, RBAC abuse, and cluster persistence
Basado en la clasificación ocupacional SOC
Mostrando SKILL.md
| name | cis-aws-foundations-5.1 |
| description | Ensure unauthorized API calls are monitored |
| category | cis-monitoring |
| version | 7.0.0 |
| author | cyberstrike-official |
| tags | ["cis","aws","monitoring","cloudwatch","cloudtrail","metric-filters","alarms","unauthorized-api"] |
| cis_id | 5.1 |
| 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 unauthorized API calls.
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 unauthorized API calls will help reduce the time it takes to detect malicious activity and can alert you to potential security incidents.
This alert may be triggered by normal read-only console activities that attempt to opportunistically gather optional information but gracefully fail if they lack the necessary permissions.
If an excessive number of alerts are generated, then an organization may wish to consider adding read access to the limited IAM user permissions solely to reduce the number of alerts.
In some cases, doing this may allow users to actually view some areas of the system; any additional access granted should be reviewed for alignment with the original limited IAM user intent.
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
TRUEEnsure 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": "{ ($.errorCode ="*UnauthorizedOperation") || ($.errorCode ="AccessDenied*") && ($.sourceIPAddress!="delivery.logs.amazonaws.com") && ($.eventName!="HeadBucket") }",
Note the <unauthorized-api-calls-metric> value associated with the filterPattern from step 3.
Get a list of CloudWatch alarms, and filter on the <unauthorized-api-calls-metric> captured in step 4:
aws cloudwatch describe-alarms --query "MetricAlarms[?MetricName == <unauthorized-api-calls-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 unauthorized API calls, 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 <unauthorized-api-calls-metric> --metric-transformations metricName=unauthorized_api_calls_metric,metricNamespace=CISBenchmark,metricValue=1 --filter-pattern "{ ($.errorCode ="*UnauthorizedOperation") || ($.errorCode ="AccessDenied*") && ($.sourceIPAddress!="delivery.logs.amazonaws.com") && ($.eventName!="HeadBucket") }"
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>
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.
aws sns subscribe --topic-arn <sns-topic-arn> --protocol <sns-protocol> --notification-endpoint <sns-subscription-endpoints>
Note: You can execute this command once and then reuse the same subscription for all monitoring alarms.
aws cloudwatch put-metric-alarm --alarm-name "unauthorized_api_calls_alarm" --metric-name "unauthorized_api_calls_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 for unauthorized API calls.
| 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 | 6.3 Enable Detailed Logging | x | x | |
| v7 | 6.5 Central Log Management | x | x | |
| v7 | 6.7 Regularly Review Logs | x | x |
Level 2 | Manual