Ensure Organizations has centralized logging bucket with proper access controls
Central logging S3 bucket should have restrictive access policies, versioning, MFA delete, and encryption to protect audit logs.
Security Impact
Compromised logging bucket allows attackers to delete or modify audit trails, hiding evidence of malicious activity.
How to Remediate
Configure S3 bucket for organization logs with: encryption, versioning, MFA delete, SCM deny policies, and restricted access.
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all AWS Organizations resources across your AWS accounts every hour
- Instant Alerts
Get notified via Slack, email, or webhooks when this misconfiguration is detected
- One-Click Remediation
Fix this issue directly from the TigerGate dashboard with our guided remediation
- Compliance Evidence
Automatically collect audit evidence for SOC 2, PCI-DSS, NIST 800-53 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-organizations-15
- Service
- AWS Organizations
- Category
- Audit Protection
- Severity
- CRITICAL
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated AWS Organizations Checks
View all checksEnsure AWS Organizations has Service Control Policies (SCPs) enabled
Ensure Organizations has AWS CloudTrail enabled at organization level
Ensure Organizations has SCPs preventing CloudTrail disablement
Ensure Organizations has SCPs enforcing regional restrictions
Ensure Organizations has SCPs preventing account leaving