Skip to content
All guides
Authentication and SSO4 min read

What is authorization (authZ)?

Almost every incident worth writing about starts with something that was working exactly as designed.

Almost every incident worth writing about starts with something that was working exactly as designed. The design was just describing a different world than the one the system ended up in.

This piece walks through how we think about it at Paycux, what we have changed our minds about, and where the sharp edges are.

Common authorization patterns

That brings us to common authorization patterns. Detection beats prevention when prevention is uncertain. If you cannot stop a class of abuse outright, make sure it produces a signal loud enough that someone sees it the same day.

Detection beats prevention when prevention is uncertain. If you cannot stop a class of abuse outright, make sure it produces a signal loud enough that someone sees it the same day.

Role Based Access Control (RBAC)

Role Based Access Control (RBAC) is where this gets concrete. Detection beats prevention when prevention is uncertain. If you cannot stop a class of abuse outright, make sure it produces a signal loud enough that someone sees it the same day.

Rotate on a schedule, not on an incident. A rotation path that has been exercised is a routine change; one that has never been used is an outage waiting for the worst possible moment.

  • Scope credentials to the smallest useful blast radius
  • Alert on the abuse you cannot prevent
  • Exercise the rotation path before you need it
  • Log the decision, not just the outcome

Attribute Based Access Control (ABAC)

That brings us to attribute based access control (abac). Rotate on a schedule, not on an incident. A rotation path that has been exercised is a routine change; one that has never been used is an outage waiting for the worst possible moment.

Rotate on a schedule, not on an incident. A rotation path that has been exercised is a routine change; one that has never been used is an outage waiting for the worst possible moment.

Relationship Based Access Control (ReBAC)

Relationship Based Access Control (ReBAC) deserves its own treatment. Detection beats prevention when prevention is uncertain. If you cannot stop a class of abuse outright, make sure it produces a signal loud enough that someone sees it the same day.

Detection beats prevention when prevention is uncertain. If you cannot stop a class of abuse outright, make sure it produces a signal loud enough that someone sees it the same day.

Rotate on a schedule, not on an incident.

Fine Grained Authorization (FGA)

That brings us to fine grained authorization (fga). Detection beats prevention when prevention is uncertain. If you cannot stop a class of abuse outright, make sure it produces a signal loud enough that someone sees it the same day.

Detection beats prevention when prevention is uncertain. If you cannot stop a class of abuse outright, make sure it produces a signal loud enough that someone sees it the same day.

Security concerns and best practices

That brings us to security concerns and best practices. Blast radius is the metric that actually matters. A credential that can read one organization's data is an incident; the same credential scoped to every organization is a company-ending event, and the difference is a design decision made months earlier.

Rotate on a schedule, not on an incident. A rotation path that has been exercised is a routine change; one that has never been used is an outage waiting for the worst possible moment.

Deny by default (enforce least privileges)

That brings us to deny by default (enforce least privileges). Blast radius is the metric that actually matters. A credential that can read one organization's data is an incident; the same credential scoped to every organization is a company-ending event, and the difference is a design decision made months earlier.

Detection beats prevention when prevention is uncertain. If you cannot stop a class of abuse outright, make sure it produces a signal loud enough that someone sees it the same day.

Where this leaves us

None of this is exotic. It is the ordinary discipline of deciding what you own, writing down what you assume, and making the failures loud enough to notice.

If you are working through the same problem and want to compare notes, the docs cover the mechanics and the console shows the behaviour on your own data.

Everything here, already built

Sign-in, enterprise SSO, directory provisioning, roles and an audit trail behind one API.

Stop reading, start shipping

The quickstart takes about ten minutes and leaves you with a working sign-in.