Authorize at Trust Boundaries: Identity-First Access Reasoning
Identity-first authorization treats a private subnet as a path control, not proof of access, and names the caller and permission at every trust boundary. This interactive lesson traces storefront admin, service, and database hops. Covers: JWT claims for shoppers, federated admin access, workload identity, resource-level permissions, IAM roles, Azure managed identities, Google Cloud service accounts. Practice: Trust boundary access. Prerequisites: Cloud IAM basics.
An evaluator points to the seasonal storefront diagram and asks, “It’s in a private subnet, so it’s secure, right?” A strong answer corrects the premise. A private subnet can restrict network paths, but security is scored on whether we can state who can do what to which resource under which conditions.
Let’s label a trust boundary as a point where a request crosses from one level of trust to another. The storefront has three visible boundaries: an internet user reaches the edge or ingress layer, the ingress layer forwards to the ...