CME-911

Fine-Grained Administrative Permission Scoping

Description

Decompose coarse-grained administrative roles into fine-grained permission sets and assign each administrator the minimum permission scope required for their operational duties. Instead of granting broad management roles that bundle unrelated capabilities, the application defines atomic permissions (view-users, create-idp-mapper, assign-role, modify-client-settings) and composes them into purpose-specific administrative profiles. Administrators who manage identity providers receive only idp-configuration permissions without role-assignment capability; administrators who manage user accounts receive user-management permissions without IdP access. Regular audits compare each administrator is effective permissions against their documented job function and revoke unnecessary grants. Reduces the blast radius of compromised or malicious admin accounts by ensuring that exploiting one administrative capability does not grant access to unrelated privileged operations.

CVSS Vector Impacts

Metric Transition Rationale
Confidentiality (C) H L A compromised administrative account can only access resources within its scoped permission set; data outside the administrator is designated domain is inaccessible, limiting confidentiality impact to the attacker is authorized scope.
Integrity (I) H L Write operations are confined to the administrator is scoped permission domain; cross-domain modifications — such as an IdP admin assigning realm-level roles — are rejected by the fine-grained permission model, limiting integrity impact to the attacker is authorized scope.

CWE Relationships

Verification

Verify that administrative roles are decomposed into atomic permissions and each admin account holds only the permissions required for their role. Attempt a cross-domain action (e.g., IdP admin trying to assign a realm-admin role) and confirm it is rejected.

$ kcadm.sh get ui-ext/brute-force/realms/master/admin-permissions
# Expected: Shows fine-grained permission policies; no admin should hold permissions outside their designated scope
Platform: any
← CME-910: Role Separation / Duty Segregation CME-912: HTTP Header Normalization and Request Smuggling Prevention →