appsec.fyi

AuthZ — A Practical Guide

A curated AppSec resource library covering XSS, SQLi, SSRF, IDOR, RCE, XXE, OSINT, and more.

AuthZ: A Practical Guide

Curated and synthesized by . Last updated 2026-11-01. Synthesized from 272 of 272 curated resources. Browse all 272 AuthZ resources →

Problem Framing

Authorization, or AuthZ, is the mechanism by which systems determine what actions an authenticated user is permitted to perform. While authentication verifies who a user is, authorization dictates what they can do. In modern, complex applications, especially those leveraging microservices, APIs, and cloud-native architectures, authorization is increasingly challenging to implement correctly and consistently. Flaws in authorization logic are consistently found to be among the most prevalent and impactful vulnerabilities, directly leading to data breaches, privilege escalation, and unauthorized system control. The sheer volume and interconnectedness of resources, coupled with the dynamic nature of cloud environments and the rise of AI agents, have created a fertile ground for sophisticated authorization bypasses and misconfigurations.

The consequences of broken authorization are severe and far-reaching. They can range from a user accessing another user's private data (horizontal privilege escalation) to an unauthenticated attacker gaining administrative control of an entire system (authentication bypass leading to authorization compromise). The OWASP Top 10 consistently ranks Broken Access Control (BAC) as a top concern, reflecting its pervasive nature and the significant risks it poses [1]. Vulnerabilities like Insecure Direct Object References (IDOR) and Broken Object-Level Authorization (BOLA) are specific manifestations of these flaws, allowing attackers to manipulate object identifiers to access resources they shouldn't [2][3]. In the cloud, misconfigurations in Identity and Access Management (IAM) and container orchestration platforms like Kubernetes (e.g., overly permissive RBAC) create silent backdoors and facilitate lateral movement [4][5]. Furthermore, the emergence of AI agents introduces new attack vectors, such as "Agent Goal Hijack" and "Prompt Injection," which manipulate the agent's authorization context or actions [6].

Core Mechanics of Authorization

At its heart, authorization involves checking permissions against a subject (user, service, or agent) attempting to perform an action on a resource. This can be achieved through several models:

In practice, applications often implement authorization checks in several places:

1. API Gateways/Edge Proxies: Performing initial checks for broad access rights. 2. Service-Level Authorization: Each microservice or component verifies permissions for its specific resources and actions. This is critical because trust in edge components can be exploited if internal services don't re-validate. 3. Application Logic: Within the code itself, performing fine-grained checks, often interacting with an authorization service or database. 4. Database Level: Using features like Row-Level Security (RLS) in databases to restrict data access [15].

A fundamental principle for secure authorization is "Deny by Default," meaning access is prohibited unless explicitly granted [12]. Furthermore, the principle of "Least Privilege" dictates that users and services should only have the minimum permissions necessary to perform their intended functions [16][17].

Notable Techniques and Vulnerabilities

A significant portion of authorization flaws stems from improper implementation of these core mechanics. Common attack patterns include:

Detection and Prevention Strategies

Effective authorization security requires a multi-layered approach:

1. Secure Design Principles:

2. Input Validation and Sanitization: Rigorously validate all user-supplied input, especially identifiers, to prevent IDOR, path traversal, and command injection [27].

3. Contextual Authorization Checks: Ensure authorization checks are performed based on the authenticated user's identity and permissions at the point of action, not solely on client-side controls or initial authentication. Re-validate permissions for every sensitive operation [1].

4. Consistent Policy Management:

5. Identity and Access Management (IAM) Best Practices:

6. Secure API Development:

7. AI Agent Security:

8. Code Review and Static Analysis: Integrate security checks into the development lifecycle, including AI-assisted code reviews, to catch authorization flaws early [30][20].

9. Dynamic Analysis and Penetration Testing: Regularly test applications and infrastructure for authorization vulnerabilities using tools and manual techniques [4][40]. Focus on identifying IDOR, forced browsing, and privilege escalation paths.

10. Container Security: Implement strict Role-Based Access Control (RBAC) in Kubernetes, network policies for segmentation, and limit pod privileges to prevent lateral movement and privilege escalation within the cluster [5][31][4].

Notable Tooling

A variety of tools can assist in identifying, preventing, and managing authorization vulnerabilities:

Recent Developments and Emerging Threats

The landscape of authorization vulnerabilities is constantly evolving:

Where to Go Deeper

For practitioners looking to deepen their understanding and defensive capabilities in authorization:

Sources cited in this guide

  1. Broken Access Control: The 40% Surge in 2025 — instatunnel.my
  2. Insecure Direct Object References (IDOR) | PortSwigger — portswigger.net
  3. How To Find Broken Access Control Vulnerabilities in the Wild | HackerOne — hackerone.com
  4. OperTraitors: How Kubernetes Operators Betray Your Security Posture — unit42.paloaltonetworks.com
  5. New EKS Access Management and Pod Identity features: a security analysis — wiz.io
  6. AI Agents Keep Falling to 'Goal Hijack' (Copilot, Cursor, Grok) — darkmarc.substack.com
  7. Rights Management Approaches: ACL, RBAC, ABAC, ReBAC — system-design.space
  8. Basic ABAC with OPA and Rego - AWS — docs.aws.amazon.com
  9. Introduction to Google Zanzibar — authzed.com
  10. Relationship-Based Permissions in SpiceDB — authzed.com
  11. OpenFGA: Open-Source Engine for Access Control — helpnetsecurity.com
  12. Authorization Concepts - OpenFGA — openfga.dev
  13. What is Open Policy Agent (OPA)? — wiz.io
  14. Cedar Policy Language Complete Guide — strongdm.com
  15. Wiz Data Foundations: Where’s My Sensitive Data—And Who Can Access It? — wiz.io
  16. Wiz launches support for Google Cloud excessive access findings based on audit logs — wiz.io
  17. Secure non-human identities with Wiz’s newest CIEM dashboard — wiz.io
  18. Zilliz / Attu | 2.6.5 — bishopfox.com
  19. AhsayCBS Deep-Dive: Auth Bypass to RCE — horizon3.ai
  20. How to scan for vulnerabilities with GitHub Security Lab’s open source AI-powered framework — github.blog
  21. Unprotected admin functionality — PortSwigger Access control vulnerabilities Lab 1 — infosecwriteups.com
  22. Uncontrolled Access Control: Compromising Paxton10 — techanarchy.net
  23. New Kerberos Abuse Path Discovery - Constrained Delegation without Protocol Transition against SPN-less accounts — hunio.org
  24. Privilege escalation from IIS AppPool to NT Authority/SYSTEM via AD CS RPC endpoint — mannulinux.org
  25. How I Found a $113,337 AF_ALG Linux Local Privilege Escalation Before Copy Fail — idnsec.com
  26. Popping Root on UniFi OS Server: Unauthenticated RCE Chain Detection & Analysis — bishopfox.com
  27. Looting UniFi Controllers: Detecting and Weaponizing CVE-2026-22557 — bishopfox.com
  28. Implementing Google Zanzibar: A Demonstration of Its Basics — permify.co
  29. Broken Authentication: Advanced Exploitation Guide | Intigriti — intigriti.com
  30. What Is AI Pentesting and How Does It Works? — snyk.io
  31. New attack vectors in EKS — wiz.io
  32. Azure's Weakest Link - Five Full Cross-Tenant Compromises — binsec.no
  33. CosmosEscape: Taking Over Every Database in Azure Cosmos DB — wiz.io
  34. New Developments in LLM Hijacking Activity — wiz.io
  35. Defeating Kubernetes Privilege Escalation: A Cloud Detection & Response Case Study — wiz.io
  36. How an Unpatched N-Day Let Any Anonymous Visitor Rewrite WooCommerce Prices in ND Booking — infosecwriteups.com
  37. OPA, Cedar, OpenFGA: Why Are Policy Languages Trending Right Now? — dev.to
  38. Identiverse 2026: The Challenges Of Solving Identity For AI Agents At Scale — blog.gitguardian.com
  39. The Machine With Many Faces: Post-Exploitation Identity Misuse in SPIFFE/SPIRE — unit42.paloaltonetworks.com
  40. Testing for Privilege Escalation | OWASP WSTG — owasp.org
  41. Automate your API hacking with Autorize — danaepp.com
  42. Announcing OpenFGA — auth0.com
  43. Exploiting Volvo/Eicher's fleet platform to gain control over all users/vehicles — eaton-works.com
  44. Access Control Vulnerabilities and Privilege Escalation | PortSwigger — portswigger.net
  45. Off Guard: Breaking LiteLLM from authentication bypass to cloud compromise — wiz.io
  46. A GUID is Not a Credential: Unauthenticated RCE in Veeam Service Provider Console — bishopfox.com
  47. Wiz Research Identifies Exploitation in the Wild of Aviatrix Controller RCE (CVE-2024-50603) — wiz.io
📚 This guide is synthesized from the full text of resources curated in the AuthZ library, and refreshed as new material is added.