The alarms were silent, but the logs told a different story. Identity federation access had spiked, and CloudTrail was the only witness. Without fast, targeted queries, threats hide in the noise. Runbooks make the hunt exact.
Identity Federation CloudTrail Query Runbooks combine automated detection with precise investigation steps. They let you turn raw event streams into actionable data in minutes. Instead of scrolling through thousands of JSON records, you run filtered queries that focus on federated identity events—STS AssumeRole, SAML logins, OIDC token exchanges—and capture only what matters.
The first step is building CloudTrail queries that isolate identity federation activity. Use eventName filters for AssumeRole and federation-related logins. Add parameters that match your trusted identity providers. Include source IPs, MFA context, session tags, and request parameters. This ensures your runbook captures both the legitimate and the suspicious.
Next, define conditions for escalation in your runbook. Examples: role assumption from unapproved regions, unexpected IAM principal usage, or elevated permissions granted outside normal patterns. Pair each condition with exact CloudTrail SQL query samples. This means no guesswork during an incident—the runbook tells you what to run, and why.