RBAC vs ABAC Policy Evaluation Lab

Interactive evaluation of static Role-Based permissions vs dynamic Attribute-Based contextual authorization.

Access Control & Policy Evaluation

RBAC (Role-Based) vs ABAC (Attribute-Based) Engine

Target: Confidential Finance Payroll
User Role:
User Department:
Connection Security:
1. Simple RBAC Decision:ALLOWED

Checks only `role === "EDITOR"`. Ignores department and VPN connection posture.

2. Fine-Grained ABAC Decision:DENIED (Protected)

Evaluates: Role (EDITOR) + Dept (Marketing === Finance) + VPN (false).