CVE-2023-1071

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

Limiting concurrent sessions directly prevents uncontrolled resource consumption by capping the number of active sessions per user or account.

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.

Requiring consistency between access rights and classification plus formal approval steps ensures that the authorization logic correctly distinguishes between entities that should and should not be granted access.

A.5.18's provisioning, revocation, review and adjustment of access rights (incl. before role changes/termination, with segregation and owner approval) directly stops incorrect authorization decisions from being exploitable in the vast majority of cases; the bounded remainder is incorrectness inside the authorization logic itself (e.g. flawed conditional or missing check) rather than rights that were wrongly granted.

Pre-agreed severity-based prioritization and resource allocation during incident triage reduce the likelihood that an attacker-induced resource exhaustion will overwhelm the organization before corrective action is taken.

Early notification of anomalous resource consumption or system malfunctions enables throttling or isolation before availability is lost.

Specifying log storage limits and rotation procedures reduces the risk that unbounded log growth will exhaust disk or memory resources and cause denial of service.

Resource-utilization monitoring and alerting on bottlenecks or overloads limits the impact of denial-of-service or resource-exhaustion attacks.