CVE-2023-21513

Policy addresses roles, responsibilities, and privilege management to prevent improper privilege assignments.

Implements core proper privilege management by restricting to only required rights.

Baseline configuration documents and controls privilege assignments, making improper privilege management harder to introduce or sustain.

Requiring the most restrictive settings instead of defaults prevents incorrect default permissions on resources.

Defines roles and responsibilities to ensure proper privilege management during configuration changes.

Designates roles and review processes for managing physical privileges and access rights.

Tailoring explicitly overrides or scopes default permission assignments in the baseline to match the system's actual risk and operational needs.

Centralized privilege assignment and oversight prevent ad-hoc or excessive privilege grants that occur when each system is configured independently.

Lifecycle management can encompass permission settings, yet the control is too broad to specifically mitigate incorrect defaults.

Defining and enforcing least-privilege access permissions directly prevents overly permissive defaults at install time.

Hardened baselines and configuration management explicitly require correct default file permissions.

Secure SDLC practices include establishing secure defaults, but address only the development-phase portion of the weakness.

A.5.15 directly mandates determining access requirements, defining/enforcing topic-specific access control policy, assigning rights/restrictions by entity/role, consistency with classification, need-to-know, privileged access restrictions, segregation, formal authorization, and dynamic rules — which stops most improper privilege management from being exploitable; bounded remainder is flawed implementation of those rules (e.g. incorrect mapping or enforcement bugs).

A.5.18 directly governs the provisioning, review, modification and timely revocation of access rights (including for role changes, termination and privilege levels), which stops most improper privilege spheres from being exploitable even if the assignment flaw exists; the bounded remainder is flaws in the underlying enforcement mechanism itself (e.g. AC-3/A.8.3)

Defining and communicating authorization levels for each role limits the assignment of excessive or unnecessary privileges.