liveBook · Manning

Authorization

As explained in Software Architecture Decision-Making

Access control is the enforcement of rules governing which identities or processes may access particular resources or operations.

Access control governs who or what may perform sensitive operations, but its required rigor depends on consequences rather than category. Internal systems may tolerate flexibility around screens or workflows while demanding stronger controls around permissions, audit trails, data integrity, and financial reconciliation. section 3.5

Treat access control as a high-rigor decision when failure is difficult to detect, reverse, or contain:

  • Increase rigor when incorrect permissions can expose sensitive data, affect money, create legal or regulatory exposure, or disrupt core operations. section 3.5
  • Use feedback from tests, monitoring, and operational signals to distinguish visible, reversible mistakes from silent permission failures. section 3.5
Table 3.5 Decision rigor rubric
Factor
Lower rigor may be acceptable when...
Higher rigor is justified when...
Reversibility
The decision can be changed, rolled back, or replaced without major disruption.
The decision is hard to reverse once data, users, integrations, or operational processes depend on it.
Detectability
Failure is visible quickly through tests, monitoring, user feedback, or operational signals.
Failure can remain hidden, appear later, or silently corrupt data, calculations, permissions, or business outcomes.
Blast radius
Failure affects a small internal group, a temporary workflow, or a non-critical capability.
Failure affects customers, money, safety, compliance, sensitive data, or core operations.
Cost of failure
The consequence is inconvenience, rework, delay, or local operational pain.
The consequence is legal exposure, financial loss, security breach, regulatory failure, physical harm, or major reputational damage.
Recovery
The team can recover through rollback, retry, correction, or a known manual process.
Recovery requires coordinated incident response, data repair, customer communication, regulatory reporting, or complex restoration.

The decision-rigor rubric helps evaluate access control through reversibility, detectability, blast radius, and cost of failure. section 3.5

How Software Architecture Decision-Making covers it

How deep it goes
Evaluates access control through reversibility, detectability, blast radius, and failure cost without specifying implementation procedures.
Examples
Uses internal pricing or billing support systems, permissions, audit trails, and financial reconciliation as examples.
What you can do after
Evaluate access-control rigor against failure consequences rather than applying uniform standards across a system.
How it connects
Connects access control with security, sensitive data, audit trails, data integrity, financial systems, and risk assessment.

Also explained in

Compare how 38 books explain authorization →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Software Architecture Decision-Making. The section links point to the parts of the book it draws on.