Join our Newsletter — 33% off our NHI Course
Home› Glossary› Governance, Ownership & Risk› Authorization Model
Governance, Ownership & Risk

Authorization Model

← Back to Glossary
By NHI Mgmt Group Updated November 2, 2026 Domain: Governance, Ownership & Risk

An authorization model is the structure an organisation uses to decide who can do what, and under which conditions. It combines decision logic with enforcement so access is granted or denied in a consistent way across applications and services.

What the authorization model does

An authorization model defines the rules an organisation uses to decide which actions an identity, application, workload, or service may perform, and under what conditions. It turns policy into repeatable decisions, so the same request is treated consistently across systems instead of being judged ad hoc inside each application.

That consistency matters because authorisation is not just a yes-or-no gate. A mature model can account for context such as resource type, relationship, role, entitlement, location, time, device state, or delegated authority. When the model is weak or inconsistent, access decisions drift, and the organisation starts to rely on scattered exceptions rather than a controlled security posture.

Common authorization model patterns

Most organisations encounter authorization models as patterns rather than as a single universal design. Authorisation Models Guide is useful here because it compares RBAC, ABAC, ReBAC and policy-based access control, including how those models support externalised authorisation.

RBAC is often the simplest starting point because it maps access to roles and is easy to understand at scale. ABAC adds more context by evaluating attributes such as user, resource or environment. ReBAC goes further by deciding access from relationships, which is especially useful where permissions depend on ownership, collaboration or graph-like structures. Many organisations end up combining these patterns rather than using only one.

The practical trade-off is that simpler models are easier to operate, while more expressive models handle finer-grained decisions. The right choice depends on whether the organisation needs broad, stable access rules or highly contextual authorisation that can change with business relationships and runtime conditions.

Decision logic and enforcement

An authorization model usually separates decision-making from enforcement. The decision layer determines whether access should be allowed, and the enforcement layer applies that decision at the application, API, service or policy gateway. That separation is valuable because it keeps logic consistent and makes access rules easier to audit, test and change.

IAM and IGA Basics is a useful companion because it explains how authentication, authorisation, provisioning and access governance fit together, including separation of duties, access reviews and entitlement management. An authorisation model works best when those governance processes and the runtime policy engine tell the same story.

In modern environments, the model may be implemented through a central policy service, embedded application logic, or a hybrid pattern. The main requirement is that the enforcement point follows the same policy logic everywhere, otherwise the organisation ends up with policy fragmentation and inconsistent access outcomes.

Where authorization models are most important

Authorization models become most important where access is dynamic, distributed or fine-grained. That includes enterprise applications, APIs, cloud services, shared data platforms and environments where access depends on relationships rather than simple job titles. The model also becomes critical when humans, workloads and AI agents all need controlled access in the same environment.

AI Agent Authorisation Guide shows why this matters for autonomous software: agent access should be task-scoped, time-bounded and checked per action rather than granted broadly. Permission-Aware RAG Guide is another strong example because retrieval systems must respect permissions at query time, not merely at storage time, or they can overexpose sensitive content.

In these settings, the model is not just a control description. It becomes part of the system architecture, because business logic, data access and security enforcement all depend on how authorisation is expressed and applied.

Risk and Threat Considerations

Authorization models create risk when they are too coarse, too permissive, or implemented differently across systems. The main danger is not just denied access, but silent overexposure, where users or services receive more privilege than intended and the control fails in ways that are hard to notice.

Failure mechanism: Broken or inconsistent policy logic can produce privilege creep, broken object-level authorisation, overbroad service access, or policy drift between the decision point and the enforcement point.

Impact: Attackers or insiders can access data, functions, or relationships they should not reach, and compromise can spread further when one weak access rule applies across many applications or services.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5 provides the primary governance reference for this term.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5AC-3 — Access EnforcementDefines enforcing allow and deny decisions for access requests.
AC-6 — Least PrivilegeConstrains what users and services can do after authorization is granted.
IA-9 — Service Identification and AuthenticationCovers machine and service access patterns that authorization models must govern.
Recommendation — Implement AC-3 to enforce consistent allow and deny decisions across applications and services. Apply AC-6 to limit permissions to the minimum needed for each identity or service. Use IA-9 to authenticate services before their access is authorised.

Practitioner Guidance

Why practitioners should care: The authorisation model is a governance decision as much as a technical one. If teams do not agree on the model, they usually end up with a mix of hard-coded rules, local exceptions and inconsistent privilege decisions that are difficult to review or change.

What to watch for: Look for places where the application bypasses central policy, where roles are overloaded with exceptions, or where resource-level decisions are being approximated by broad group membership. Those are common signs that the model is drifting away from the real business rules it is supposed to enforce.

Practitioner takeaway: Treat the authorization model as a durable control design, not an implementation detail. The best model is the one that matches the organisation’s real decision logic and can be enforced consistently everywhere it matters.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 2, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org