In NIST 800-53 environments, that collapse often starts with large-scale role explosion. One project adds a dozen new roles. Another project redefines existing ones. Soon, hundreds of overlapping roles compete in a single system. Permissions sprawl. The principle of least privilege breaks quietly but completely.
NIST 800-53’s access control (AC) family demands strict definition, documentation, and enforcement of roles. Role-based access control works when scope is tight. It fails when roles multiply without a clear lifecycle. Large-scale role explosion fuels audit headaches, risk exposure, and operational slowdown. Misaligned role design collides with control requirements from AC-2 (Account Management) and AC-3 (Access Enforcement). Overlapping privileges become invisible threats until the report comes back red.
The root cause is simple: uncontrolled growth. Teams create “one-off” roles to meet short-term needs. Migration scripts replicate old roles into new systems. Integration with external identity providers adds yet more. Without enforcement, each addition moves farther from the NIST 800-53 baseline. Large-scale role explosion becomes a systemic vulnerability.