Authorization

Authorization

Authorization is the process of determining what an authenticated subject is allowed to do on a given resource under specific conditions.

Acronym
AuthZ
Synonym
AuthZ

Definition

Authorization is the process of evaluating whether a subject, already identified and usually authenticated, is permitted to perform a specific action on a target resource within a given context. In IAM, authorization decisions can apply to applications, APIs, databases, files, workflows, business objects, or infrastructure components. Authorization is not limited to a binary allow or deny outcome; mature systems also evaluate scope, conditions, obligations, temporal constraints, risk signals, and policy hierarchies. A robust authorization model defines who can do what, on which object, in which context, under which rules, and with which level of traceability.

Why it matters

Authorization is the control layer that translates identity into effective permissions. Even strong authentication is insufficient if authorization logic is weak, excessive, inconsistent, or untraceable.

The Ariovis perspective

Ariovis separates governed entitlements, authentication and runtime authorization. When a decision depends on the user, resource, action and context, it should be made at the moment of use.

Common pitfalls

  • A common mistake is reducing authorization to static role checks while ignoring context, business rules, data sensitivity, and fine-grained decision requirements.

Standards and protocols

Reference standards
  • NIST SP 800-162
  • ISO/IEC 27001
Related protocols
  • OAuth 2.0
  • XACML
  • OPA/Rego

These concepts matter most inside a real project.

The first conversation helps establish your context, the systems involved and the next useful decision.