Ensure EC2 instances have required tags
EC2 instances should have required tags for cost allocation, ownership, and environment identification.
Security Impact
Untagged resources are difficult to track for billing, ownership, and security purposes.
How to Remediate
Implement tagging policies using AWS Organizations SCPs or AWS Config rules. Required tags typically include Environment, Owner, and Project.
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 SOC 2 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-ec2-24
- Service
- Elastic Compute Cloud (EC2)
- Category
- Governance
- Severity
- LOW
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free Trial