Skip to main content

RBAC Analyzer

Find role hierarchy cycles, redundant grants and separation-of-duty conflicts

Model

Add a role and a permission, or load an example.

Results

Ready to analyze

Load an example, import a JSON or CSV file, or build the matrix. Findings update as you edit.

No model loaded.

How to use it

  1. 1.Load an example, import a JSON or CSV file, or add roles and permissions in the Matrix tab.
  2. 2.Toggle cells to grant or revoke direct permissions; inherited cells show where they come from.
  3. 3.Edit inheritance in the Hierarchy tab or the JSON tab.
  4. 4.Review Findings, open Effective permissions for a role, and export JSON, CSV, a Markdown matrix or a Mermaid diagram.

What the RBAC Analyzer checks

The analyzer reads a role-based access control model: roles, the roles they inherit from, permissions, direct grants and separation-of-duty pairs. It detects inheritance cycles first, then expands effective permissions for every role and reports missing parent roles, duplicate or equivalent roles, redundant direct grants, roles without permissions, unused permissions and duty conflicts.

Deterministic findings and heuristics

Deterministic findings follow from the model itself, such as a cycle or a role that holds both sides of a separation-of-duty pair. Heuristic findings are labelled Heuristic: broad roles above a coverage threshold, wildcard-like permission names, access-management permissions combined with sensitive ones, and many roles for few permissions. They are review hints, not statements about business intent.

Privacy and limits

Analysis runs in your browser and the model is not saved. The analyzer covers RBAC only: attribute, relationship or policy conditions are not evaluated, and a wildcard permission is not expanded into other permissions. Large models stay responsive by showing the matrix in pages of rows and a limited number of role columns.

Frequently asked questions
Is my RBAC model uploaded anywhere?
No. Parsing, analysis and exports run in your browser, and the model is kept only in memory for the current page. Nothing is sent to CodingTool servers or saved in browser storage.
What is the difference between a deterministic and a heuristic finding?
Deterministic findings follow from the model itself, such as an inheritance cycle, a missing parent role, a redundant direct grant or a role holding both permissions of a separation-of-duty pair. Heuristic findings are labelled Heuristic and highlight patterns worth reviewing, such as a role holding at least 80% of all permissions; the threshold is configurable.
Which input formats are supported?
A JSON model with roles (optionally with inherits and a permissions shorthand), permissions (with optional resource, action and sensitive flag), grants and sod pairs, or CSV rows of role,permission with an optional header. You can also build the model directly in the matrix and hierarchy views.

CodingTool is officially live on