Ensure RDS instances are not publicly accessible
RDS instances should not be publicly accessible. Public accessibility exposes databases directly to the internet.
Security Impact
Publicly accessible databases can be targeted for brute force attacks, SQL injection, and data exfiltration.
How to Remediate
Modify RDS instance to disable public accessibility. Use VPC security groups and private subnets for database 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 Relational Database Service (RDS) 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, CIS AWS v2.0, SOC 2 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-rds-1
- Service
- Relational Database Service (RDS)
- Category
- Network Security
- Severity
- CRITICAL
- CIS Benchmark
- 2.3.1
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated Relational Database Service (RDS) Checks
View all checksEnsure RDS instances have encryption at rest enabled
Ensure RDS instances use KMS customer managed keys
Ensure RDS instances have automated backups enabled
Ensure RDS backup retention is at least 7 days
Ensure RDS instances have Multi-AZ enabled