Micro-segmentation is the guardrail that keeps that story from repeating. It limits the blast radius. It draws lines between workloads that should never speak to each other. Combined with AWS CloudTrail, it gives you the visibility to detect when those lines are crossed. The missing link is speed—the ability to turn a suspicion into a verified answer right away. That is where precise CloudTrail query runbooks matter.
A CloudTrail query runbook is not a static document. It’s a living set of queries, tuned to your environment, ready to run at any sign of unusual behavior. Well-built, these runbooks define the exact sequence: the event filters, the service types, the resource patterns, and the expected baseline. They skip guesswork and lead straight to signal.
In a micro-segmented cloud network, you care about east-west movement, permissions escalation, and resource drift. Your runbooks should focus on those. For example:
- Detect IAM role assumption outside intended VPC boundaries.
- Find API calls from blocked network segments.
- Flag resource creation in non-approved zones.
- Surface unusual S3 PutObject requests between isolated workloads.
Each query needs precision. Broad filters create noise. Overly narrow filters miss attacks. Start with the highest-value conditions—privilege changes, unusual logins, cross-segment requests—then refine with iterative tuning.