Skip to main content

🛡️ AWS CloudTrail IAM Policy Changes Monitoring is not enabled🟢⚪

Similar Policies​

Similar Internal Rules​

RulePoliciesFlags
✉️ dec-x-43f99d791

Description​

Open File

Description​

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 changes made to Identity and Access Management (IAM) policies.

Rationale​

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 changes to IAM policies will help ensure authentication and authorization controls remain intact.

Impact​

Monitoring these changes may cause a number of "false positives" more so in larger environments. This alert may need more tuning then others to eliminate some of those erroneous alerts.

Audit​

If you are using CloudTrails and CloudWatch, perform the following to ensure that there is at least one active multi-region CloudTrail with prescribed metric filters and alarms configured:

... see more

Remediation​

Open File

Remediation​

If you are using CloudTrails and CloudWatch, perform the following to setup the metric filter, alarm, SNS topic, and subscription:

  1. Create a metric filter based on filter pattern provided which checks for IAM policy changes and the <cloudtrail_log_group_name> taken from audit step 1:
aws logs put-metric-filter --log-group-name `<cloudtrail_log_group_name>` --filter-name `<iam_changes_metric>` --metric-transformations metricName= `<iam_changes_metric>` ,metricNamespace='CISBenchmark',metricValue=1 --filter-pattern '{($.eventName=DeleteGroupPolicy)||($.eventName=DeleteRolePolicy)||($.eventName=DeleteUserPolicy)||($.eventName=PutGroupPolicy)||($.eventName=PutRolePolicy)||($.eventName=PutUserPolicy)||($.eventName=CreatePolicy)||($.eventName=DeletePolicy)||($.eventName=CreatePolicyVersion)||($.eventName=DeletePolicyVersion)||($.eventName=AttachRolePolicy)||($.eventName=DetachRolePolicy)||($.eventName=AttachUserPolicy)||($.eventName=DetachUserPolicy)||($.eventName=AttachGroupPolicy)||($.eventName=DetachGroupPolicy)}'

... [see more](remediation.md)

policy.yaml​

Open File

Linked Framework Sections​

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
💼 CIS AWS v1.2.0 → 💼 3.4 Ensure a log metric filter and alarm exist for IAM policy changes1no data
💼 CIS AWS v1.3.0 → 💼 4.4 Ensure a log metric filter and alarm exist for IAM policy changes1no data
💼 CIS AWS v1.4.0 → 💼 4.4 Ensure a log metric filter and alarm exist for IAM policy changes1no data
💼 CIS AWS v1.5.0 → 💼 4.4 Ensure a log metric filter and alarm exist for IAM policy changes - Level 1 (Automated)1no data
💼 CIS AWS v2.0.0 → 💼 4.4 Ensure IAM policy changes are monitored - Level 1 (Manual)1no data
💼 CIS AWS v3.0.0 → 💼 4.4 Ensure IAM policy changes are monitored - Level 1 (Manual)1no data
💼 CIS AWS v4.0.0 → 💼 4.4 Ensure IAM policy changes are monitored (Manual)1no data
💼 CIS AWS v4.0.1 → 💼 4.4 Ensure IAM policy changes are monitored (Manual)1no data
💼 CIS AWS v5.0.0 → 💼 4.4 Ensure IAM policy changes are monitored (Manual)1no data
💼 CIS AWS v6.0.0 → 💼 5.4 Ensure IAM policy changes are monitored (Manual)1no data
💼 Cloudaware Framework → 💼 Alerting and Notification27no data
💼 Cloudaware Framework → 💼 General Access Controls11no data
💼 FedRAMP High Security Controls → 💼 AC-2(4) Automated Audit Actions (M)(H)16no data
💼 FedRAMP High Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)265no data
💼 FedRAMP High Security Controls → 💼 SI-4(20) Privileged Users (H)4851no data
💼 FedRAMP Low Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)65no data
💼 FedRAMP Moderate Security Controls → 💼 AC-2(4) Automated Audit Actions (M)(H)16no data
💼 FedRAMP Moderate Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)65no data
💼 NIST CSF v2.0 → 💼 DE.CM-01: Networks and network services are monitored to find potentially adverse events145no data
💼 NIST CSF v2.0 → 💼 DE.CM-03: Personnel activity and technology usage are monitored to find potentially adverse events85no data
💼 NIST CSF v2.0 → 💼 DE.CM-09: Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events142no data
💼 NIST SP 800-53 Revision 5 → 💼 AC-2(4) Account Management _ Automated Audit Actions1416no data
💼 NIST SP 800-53 Revision 5 → 💼 AU-12 Audit Record Generation44765no data