Ensure EC2 instances use IMDSv2
Instance Metadata Service Version 2 (IMDSv2) provides enhanced security through session-based authentication, protecting against SSRF attacks.
Security Impact
IMDSv1 is vulnerable to SSRF attacks that can steal IAM credentials from the metadata service.
How to Remediate
Require IMDSv2 for all instances by setting HttpTokens to 'required'. Update existing instances using: aws ec2 modify-instance-metadata-options --instance-id INSTANCE_ID --http-tokens required
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, 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-ec2-6
- Service
- Elastic Compute Cloud (EC2)
- Category
- Instance Configuration
- Severity
- HIGH
- CIS Benchmark
- 5.6
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free Trial