Studio 02 / Architecture

Change the boundary. See the failure mode.

Inspect each trust boundary, change enforcement choices and compare outcomes from a deterministic synthetic system model. The controls are examples, not claims about your environment.

01 / Select a system

A client session crosses an API boundary before sensitive account data is returned.

Selected trust boundary

iOS / Android — Untrusted device

Holds an access token and displays account data. Integrity checks inform risk, not authority.

Device state can be tampered with.

02 / Simulate a failure

Scenario

Enforcement design

03 / Synthetic outcome

Allowed after independent policy checks

The synthetic legitimate request passes identity, resource scope and action checks.

Telemetry to check

Record the decision, principal and outcome without secrets.

Engineering guardrail

Positive tests are necessary but insufficient: exercise unauthorized and failure cases.

Try the runnable authorization lab

This is a deterministic teaching model. No production requests, vulnerability probes, real credentials or customer environments are involved. Outcomes depend on controls being correctly implemented and tested.