Ensure EC2 instances do not use default security groups
Default security groups should not be used for EC2 instances. Custom security groups provide better access control and auditability.
Security Impact
Default security groups may have overly permissive rules and are difficult to audit across multiple resources.
How to Remediate
Create custom security groups with specific rules. Modify the default security group to deny all traffic or delete unused default groups.
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 Elastic Compute Cloud (EC2) 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-ec2-8
- Service
- Elastic Compute Cloud (EC2)
- Category
- Network Security
- Severity
- MEDIUM
- CIS Benchmark
- 5.3
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free Trial