CVE-2023-0971

Periodic review and update of procedures reduces incorrect authorization implementations over time.

Supervision identifies cases where authorization logic incorrectly permits unauthorized actions.

Defining permitted attribute values and auditing modifications reduces the chance of incorrect authorization outcomes due to tampered or missing labels.

The authorization process and usage restrictions help prevent incorrect authorization for remote access types.

Establishing configuration and connection requirements helps ensure correct rather than incorrect authorization for wireless access.

Establishing connection authorization processes for mobile devices helps ensure authorization decisions are correctly implemented rather than incorrect.

Monitoring account use, notifying on changes, and reviewing accounts for compliance corrects incorrect authorization assignments.

Ensures authorization decisions for external system use are correctly implemented and enforced.

Least-privilege policy definition and enforcement directly limits unsafe privilege combinations while the control also addresses broader policy lifecycle activities.

Access control policies can limit the combination of privileges that enable unsafe actions.

A.5.18's provisioning, review, SoD, and revocation steps (esp. c, f, i) directly block unsafe privilege/role combinations at assignment and change time, but leave a bounded remainder (e.g. runtime dynamic chaining, combinations arising from un-reviewed legacy rights, or non-identity-based privilege escalation) unaddressed by this clause alone.

A.5.3 directly requires determining and enforcing segregation of the very duties/roles whose unsafe combination is CWE-268, so well-implemented segregation stops the chained privilege from being exercisable; the bounded remainder is small organizations or sanctioned exceptions where segregation cannot be achieved and the clause itself falls back to monitoring/supervision instead.