Ensure Redshift clusters have audit logging enabled
Audit logging records connection attempts, authentication attempts, and SQL statements executed, providing security monitoring and compliance evidence.
Security Impact
Without audit logs, security incidents, unauthorized access attempts, and suspicious queries cannot be detected or investigated.
How to Remediate
Enable audit logging in cluster configuration. Configure S3 bucket to receive logs and set appropriate retention periods.
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 Amazon Redshift 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 CIS AWS v1.5.0, SOC 2, PCI-DSS compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-redshift-4
- Service
- Amazon Redshift
- Category
- Logging and Monitoring
- Severity
- HIGH
- CIS Benchmark
- 5.3
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated Amazon Redshift Checks
View all checksEnsure Redshift clusters are not publicly accessible
Ensure Redshift clusters have encryption at rest enabled
Ensure Redshift clusters have encryption in transit enabled
Ensure Redshift clusters have automated snapshots configured
Ensure Redshift cluster snapshots are encrypted