Pick a depth. Each prompt opens in your AI pre-loaded with the lesson. Click a row to preview the prompt.
Perimeter security assumes the inside of your VPC is safe — zero-trust assumes it's already compromised. The principles (never trust, always verify, least privilege, assume breach) translate directly into cloud controls: identity on every hop, mTLS between services, and IAM scoped to single actions. Skipping zero-trust is how a leaked AWS access key turns into ransomware on your DB.
Inspect identity-aware access controls that replace network-level trust.
*:* permissions — argue why each one violates least privilege.# Inspect a least-privilege IAM policy (one action, one resource)
aws iam get-policy-version --policy-arn <policy-arn> --version-id v1 \
--query 'PolicyVersion.Document'
# Service-to-service mTLS via ACM PCA + AWS App Mesh / VPC Lattice
aws vpc-lattice list-services --query 'items[*].[name,authType]'
# Audit who has admin (this should return very few principals)
aws iam list-policies --scope Local \
--query 'Policies[?contains(PolicyName, `Admin`)].[PolicyName,AttachmentCount]'