CyberKit

Instance Metadata Service

Also called IMDS, Metadata endpoint.

A link-local endpoint that hands instance credentials and config to a VM.

What it is

A non-routable endpoint reachable only from within a virtual machine that returns instance configuration and, critically, the temporary credentials of the instance's attached role. It exists so workloads can obtain credentials without embedding secrets.

Why it matters

Because a server-side request forgery flaw can trick an application into reading this endpoint, it is one of the most common bridges from a web vulnerability to live cloud credentials.

In practice

Triaging a breach, an analyst sees outbound calls fetching the metadata credentials path moments before those exact keys appeared in API logs from an attacker IP.

What to look for

  • Requests to 169.254.169.254 from web application processes.
  • Instance role credentials used from an IP address outside your cloud.
  • Instances still allowing the older, token-free metadata version.

Common mistake

Leaving the first metadata version enabled. Requiring session tokens blocks most server-side request forgery theft.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Amazon GuardDuty Cloud service

    AWS threat detection that analyzes CloudTrail, VPC flow logs and DNS logs.

  • Microsoft Defender for Cloud Commercial

    Posture and threat protection for Azure, AWS and Google Cloud.

  • Wiz Commercial

    Maps cloud resources, identities and exposures into one graph of risk.

  • Prowler Open source

    An open source tool that checks cloud accounts against benchmarks such as CIS.

Read next

Sources