CVE-2023-0181

Access control policy can specify and enforce secure default permissions for resources.

Guides setting of default permissions to the minimum required level.

Establishes requirements for appropriate default permissions on system resources as part of configuration management.

Baseline establishment and updates on install/upgrade ensure correct default permissions rather than insecure ones.

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

Requires documented processes that include setting and maintaining correct default permissions for configuration items.

Requires addressing secure default permissions in physical and environmental protection controls.

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

Runtime monitoring of software and data surfaces adverse events triggered by unhandled permission failures.

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

Defining, enforcing and reviewing access permissions with least privilege directly prevents code paths that mishandle insufficient privileges.

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

Generating logs of permission-related events enables detection and analysis of improper handling.

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

A.5.15 only requires determining requirements, defining a topic-specific policy on access control, and considering various factors; it does not itself enforce, implement, or prevent exploitation of mishandled insufficient permissions.