Security Architecture View
Overlay public entry points, identities, authorization, trust boundaries, encrypted links, sensitive stores, privileged services and audit sinks on the ordinary system diagram.
Frame the problem
Security starts with a concrete asset, attacker capability and trust crossing.
Why the system fails
The diagram shows components but omits exposure, identities, data classification and enforcement, so reviewers cannot see a missing control or oversized blast radius.
The important question is not “what is Security Architecture View?” but “which assumption let untrusted data or an over-scoped identity cross functional architecture → explicit security architecture?” Trace the decision at the boundary, then constrain what can happen after the first control fails.
Design the control in layers
Start with the control closest to the interpretation or privilege boundary: Make exposure, trust, identity and privilege visible on every architecture Then add a control that reduces blast radius and telemetry that proves the decision was enforced.
The resulting design is not labelled secure. Record the identified controls, the known failure paths, the remaining exposure, and the evidence you would need during an incident.
| Prevent | Detect | Recover |
|---|---|---|
| Make exposure, trust, identity and privilege visible on every architecture · Name the enforcement point on each privileged flow · Record sensitive stores, secrets and audit evidence | Review overlays for public-to-sensitive paths with no guard or telemetry | Contain the affected identity or component, scope impact from audit evidence, and preserve a regression test. |
Key points
- Asset: A reviewable map of where security decisions and high-value data actually live.
- Boundary: Functional architecture → explicit security architecture
- Primary control: Make exposure, trust, identity and privilege visible on every architecture
- Detection signal: Review overlays for public-to-sensitive paths with no guard or telemetry
- Always ask what limits damage when the primary control fails.
Secure This Architecture
Change the system and observe which assumption moves.
A legitimate, authenticated user changes a resource id in the URL.
If it works: Cross-tenant disclosure through traffic that looks entirely normal.
Residual: Sharing, delegation and support tooling bypass ownership by design.
Prevented by Resource-scoped authorization · contained by Row-level tenant policy · seen by Audit log or Anomaly alerting
- • None yet.
- • Credential read in transit
- • Anonymous caller reaches a privileged operation
- • Credential stuffing
- • Customer reads another customer’s record
- • Input interpreted as SQL
- • Stolen session replayed
- • Database reachable beyond the backend
- • Database credential leaks
- • Compromised backend exfiltrates data
- • One request exhausts the database
- • Unexpected shape reaches business logic
- • No record of a privileged action
- Add a control to see what survives it.
- • Whether each control is actually applied on every endpoint, or only on the ones that were reviewed.
- • What the admin, support and reporting paths do — they usually bypass ownership checks by design.
- • Where copies of this data already exist: replicas, backups, exports, search indexes, logs, analytics.
- • Whether revocation and restore have ever been exercised, rather than merely implemented.
Follow the attack
Safe conceptual simulation: capability → missing control → crossed boundary → asset impact.
- 1Attacker starts with: Any caller or compromised component whose path is hidden by a functional-only diagram.
- 2The diagram shows components but omits exposure, identities, data classification and enforcement, so reviewers cannot see a missing control or oversized blast radius.
- 3The weak or missing boundary control is crossed: Functional architecture → explicit security architecture
- 4Impact: Security assumptions remain implicit and alternate attack paths survive design review.
- Security assumptions remain implicit and alternate attack paths survive design review.
Defend, detect, recover
One prevention is a single point of security failure. Layer it and make failure observable.
- • Make exposure, trust, identity and privilege visible on every architecture
- • Name the enforcement point on each privileged flow
- • Record sensitive stores, secrets and audit evidence
- • Review overlays for public-to-sensitive paths with no guard or telemetry
- • Contain the affected identity or component.
- • Scope access from audit evidence.
- • Fix the boundary and add a regression test.
- • Misconfiguration and new access paths can bypass the intended control.
- • A privileged insider or compromised control plane may still reach the asset.