Ensure EMR security groups restrict access appropriately
EMR security groups should only allow necessary ports from authorized sources, not 0.0.0.0/0.
Security Impact
Overly permissive security groups allow unauthorized network access to EMR web interfaces and APIs.
How to Remediate
Configure security groups to allow access only from corporate networks or VPN. Restrict ports to only required services.
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 EMR 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, NIST 800-53, Least Privilege compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-emr-4
- Service
- Amazon EMR
- Category
- Network Security
- Severity
- HIGH
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated Amazon EMR Checks
View all checksEnsure EMR clusters have encryption at rest enabled
Ensure EMR clusters have encryption in transit enabled
Ensure EMR clusters are not publicly accessible
Ensure EMR clusters have Kerberos authentication enabled
Ensure EMR clusters have logging enabled to S3