🛡️ AWS CloudTrail AWS Organizations Changes Monitoring is not enabled🟢⚪

• Contextual name: 🛡️ AWS Organizations Changes Monitoring is not enabled🟢⚪
• ID: /ce/ca/aws/cloudtrail/aws-organizations-changes-monitoring
• Tags:
  • ⚪ Impossible policy
  • 🟢 Policy with categories
  • 🟢 Policy with type
• Policy Type: COMPLIANCE_POLICY
• Policy Categories: SECURITY

Similar Policies

• Cloud Conformity: AWS Organizations Changes Alarm
• Internal: dec-x-e6b90a42

Similar Internal Rules

Rule	Policies	Flags
✉️ dec-x-e6b90a42	1

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 for changes made to AWS Organizations in the master AWS account.

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 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

If you are using CloudTrails and CloudWatch, perform the following:

... 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 AWS Organizations 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 <organizations_changes> --metric-transformations metricName=<organizations_changes>, metricNamespace='CISBenchmark', 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")) }'

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

policy.yaml

Open File

Linked Framework Sections

Section	Sub Sections	Internal Rules	Policies	Flags	Compliance
💼 CIS AWS v1.3.0 → 💼 4.15 Ensure a log metric filter and alarm exists for AWS Organizations changes			1		no data
💼 CIS AWS v1.4.0 → 💼 4.15 Ensure a log metric filter and alarm exists for AWS Organizations changes			1		no data
💼 CIS AWS v1.5.0 → 💼 4.15 Ensure a log metric filter and alarm exists for AWS Organizations changes - Level 1 (Automated)			1		no data
💼 CIS AWS v2.0.0 → 💼 4.15 Ensure AWS Organizations changes are monitored - Level 1 (Manual)			1		no data
💼 CIS AWS v3.0.0 → 💼 4.15 Ensure AWS Organizations changes are monitored - Level 1 (Manual)			1		no data
💼 CIS AWS v4.0.0 → 💼 4.15 Ensure AWS Organizations changes are monitored (Manual)			1		no data
💼 CIS AWS v4.0.1 → 💼 4.15 Ensure AWS Organizations changes are monitored (Manual)			1		no data
💼 CIS AWS v5.0.0 → 💼 4.15 Ensure AWS Organizations changes are monitored (Manual)			1		no data
💼 CIS AWS v6.0.0 → 💼 5.15 Ensure AWS Organizations changes are monitored (Manual)			1		no data
💼 Cloudaware Framework → 💼 Alerting and Notification			27		no data
💼 FedRAMP High Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)	2		65		no data
💼 FedRAMP High Security Controls → 💼 SI-4(20) Privileged Users (H)		48	51		no data
💼 FedRAMP Low Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)			65		no data
💼 FedRAMP Moderate Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)			65		no data
💼 NIST CSF v2.0 → 💼 DE.CM-01: Networks and network services are monitored to find potentially adverse events			150		no data
💼 NIST CSF v2.0 → 💼 DE.CM-03: Personnel activity and technology usage are monitored to find potentially adverse events			85		no data
💼 NIST CSF v2.0 → 💼 DE.CM-09: Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events			149		no data
💼 NIST SP 800-53 Revision 5 → 💼 AU-12 Audit Record Generation	4	47	65		no data