AWSOverview
Overview
EC2 Instances should not allow a metadata hop count greater than 1 when source/destination check is disabled. This ensures that containers or other VMs cannot access the metadata service of the instance.
Remediation guidance
Using Command-line
aws ec2 modify-instance-metadata-options --instance-id $instanceID --http-put-response-hop-limit 1 --http-endpoint enabled
Service-wide remediation
Recommended when many resources are affected: fix the platform baseline first so new resources inherit the secure setting, then remediate the existing flagged resources in batches.
AWS
Use AWS Organizations guardrails, AWS Config rules or conformance packs where they fit, approved account baselines, and IaC modules so new resources inherit the secure setting.
Operational rollout
- Fix the baseline first at the account, subscription, project, cluster, or tenant scope that owns this control.
- Remediate the currently affected resources in batches, starting with internet-exposed and production assets.
- Re-scan and track approved exceptions with an owner and expiry date.
Query logic
These are the stored checks tied to this control.
AWS VM Source Destination Check Disabled and Hop Count Greater Than 1
Connectors
AWS
Covered asset types
VM
Expected check: eq []
{
vms (
where: {
networkInterfaces_SOME: {
sourceDestCheck: false
}
metadataOptionHTTPPutResponseHopLimit_GT: 1
}
) {...AssetFragment}
}
