authz

Analyze and optimize authorization models for RBAC, ABAC, and ReBAC.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/hung-phan/system-skills --skill authz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: authz
Source: https://github.com/hung-phan/system-skills/tree/main/skills/system-review/references/security/authz
Command: npx skills add https://github.com/hung-phan/system-skills --skill authz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps design and implement robust authorization logic, addressing common pitfalls in access control across various systems.

Core Features & Use Cases

  • RBAC, ABAC, ReBAC: Offers guidance on implementing Role-Based, Attribute-Based, and Relationship-Based Access Control models.
  • Policy Decision Points (PDP): Provides information on how to implement a centralized PDP for consistent policy enforcement.
  • Policy Enforcement Points (PEP): Assists in creating PEPs to enforce policies at the service level.
  • Security Best Practices: Covers common security issues such as confused-deputy attacks, IDOR, and permission cache poisoning.

Quick Start

Use the authz skill to analyze your authorization model for potential vulnerabilities and to implement best practices for secure access control.

Frequently Asked Questions about authz

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent IDOR and confused-deputy attacks in distributed systems?

Prevent IDOR and confused-deputy attacks by implementing robust authorization models with centralized Policy Decision Points and Policy Enforcement Points. This secures distributed systems by ensuring consistent policy enforcement and validating access requests against security best practices.

What is the difference between RBAC, ABAC, and ReBAC for access control?

RBAC assigns permissions via roles, ABAC evaluates user and resource attributes, and ReBAC grants access based on relationship graphs. Selecting the appropriate access control model depends on your system architecture and required policy enforcement granularity.

How do I implement a centralized Policy Decision Point for authorization?

Implement a centralized Policy Decision Point (PDP) to isolate authorization logic from application code, creating a consistent policy enforcement layer across services. This reduces confused-deputy risks and ensures access control models are evaluated uniformly across distributed architectures.

When do I need relationship-based access control for my application?

You need relationship-based access control (ReBAC) when authorization depends on complex hierarchical or graph relationships between users and resources. ReBAC is essential for distributed systems requiring fine-grained policy enforcement beyond standard RBAC or ABAC models.

What are common permission cache poisoning vulnerabilities in access control?

Permission cache poisoning occurs when cached authorization decisions are improperly invalidated or manipulated, allowing unauthorized access. Mitigate this access control vulnerability by implementing secure Policy Enforcement Points and following authorization best practices for distributed systems.