Latest feature: Compare your cloud architecture against known frameworks such as NIS and SOC2.Compare your cloud against NIS and SOC2.

Book a demo
AKRIBOS AI
ProductComplianceEngineersSecurityFAQ
Sign InTry AKRIBOSTry AKRIBOS
Home/Compliance/Common issues/Instance metadata without session tokens

High severity

Instance metadata without session tokens

Compute instances that answer metadata requests, including their temporary credentials, to any process that can reach the local metadata address.

Updated 13 October 2026

What it looks like in each cloud

AWS

EC2 instances and launch templates with HttpTokens set to optional, which allows IMDSv1.

Google Cloud

Instances exposing the metadata server to workloads that do not need it; requests already require a header, so the risk is lower.

Azure

The Azure IMDS already requires a Metadata header; the equivalent risk is a managed identity with broader rights than the workload needs.

Why it matters

IMDSv1 is the classic server-side request forgery path to cloud credentials: a vulnerable web app on the instance can be tricked into fetching the role's keys. Several large breaches started exactly this way.

How it happens

Instances were launched before IMDSv2 existed, or from an AMI or template that does not set the token requirement.

How to check

List every instance and launch template with its metadata options, and flag any that allow version 1.

How to fix it

Require IMDSv2 (HttpTokens: required) on every instance and template, and set the account-level default so new instances inherit it.

Frameworks that require this

The controls this issue falls under. AKRIBOS reports the finding once and maps it to each framework you have in scope.

CIS Benchmarks

AWS Foundations 5.6 (EC2 metadata service requires IMDSv2).

SOC 2

CC6.1 (protection of credentials) and CC7.1 (vulnerability management).

ISO/IEC 27001

A.8.9 Configuration management, A.8.8 Management of technical vulnerabilities.

DORA

Art. 9(4)(c) logical access, 9(4)(f) patches and updates.

NIS2

Art. 21(2)(e) vulnerability handling and secure maintenance.

PCI DSS v4

Req. 2.2 (secure configuration), 6.3 (vulnerabilities addressed).

NIST CSF 2.0

PR.PS-01 (configuration management), PR.PS-02 (software maintained).

BSI C5

OPS (vulnerability and patch management).

DNB Good Practice Information Security

Infrastructure security (hardening); vulnerability management.

How AKRIBOS handles it

AKRIBOS finds this during a read-only review of every connected account, project and subscription, shows the exact resource and setting behind the finding, and ranks it by the attack path it enables rather than in isolation. The fix is proposed as CLI commands or Terraform for you to review and approve, and the approval is recorded in the audit trail together with the compliance controls it satisfies.

Related issues

Storage bucket open to the internet

Critical

Object storage that anyone can list or read, usually from a permissive ACL, bucket policy or account-wide setting that was never switched on.

Read more

Root or owner account without MFA

Critical

The most privileged identity in the account protected by a password alone.

Read more

Database reachable from the internet

Critical

A managed database with a public address and a firewall that lets the world in.

Read more
All common issues

Attackers don't wait for your next audit. Neither does AKRIBOS.

Connect AWS, Google Cloud or Azure and get your first review today.

Run your first reviewRun your first review
Cinematic desert landscape at dusk with a lone silhouette standing before a warm amber glow, surrounded by dark rolling hills and a deep blue sky.
AKRIBOS

The AI agent that reviews and hardens your cloud, right from your terminal or our dashboard.

Navigation

How It WorksAttack PathsContinuous ReviewsComplianceCommon Cloud IssuesFor EngineersSecurityFAQ

Information

ContactPrivacy PolicyTerms of ServiceData Processing AgreementResponsible Disclosure

Socials

LinkedIn

© 2026 AKRIBOS AI B.V. All rights reserved.

AKRIBOS is a trade name of AKRIBOS AI B.V., registered with the Netherlands Chamber of Commerce (KvK) under number 83548335, Amsterdam, The Netherlands.