CVE-2023-36633

Documented procedures facilitate correct implementation and ongoing management of authorization decisions.

Establishing permitted attributes and values, plus auditing changes, ensures authorization decisions are based on correctly managed policy data.

Prevents overly permissive assignments to critical resources by limiting to task needs.

Role-based training addresses authorization requirements and checks, lowering the risk of improper authorization.

The process verifies authorization mechanisms function as intended before system approval.

Documenting access to processing and storage locations helps ensure correct authorization for information resources.

Mandates explicit authorization and approval for configuration-controlled changes with security considerations.

Evaluating change impacts helps avoid deployment of incorrect or missing authorization logic.

A.5.1 only requires the existence of an overarching policy and topic-specific policies (including on access control); it does not itself perform or enforce any authorization check, so the CWE-285 weakness can still be exploited.

A.5.12 only defines and communicates a classification scheme (with owners accountable for applying it); it does not itself enforce, restrict or decide any permissions, so the CWE-732 permission flaw can still be present and exploitable.

Mapping access rights to information classification and business requirements forces correct enforcement of authorization decisions, blocking the incorrect authorization weakness at the policy and implementation stage.

A.5.18 directly governs the provisioning, review, adjustment and revocation of logical access rights (including for critical resources) according to business needs, policy, SoD and risk, which stops most unintended actors from reading/modifying via incorrect permissions; the bounded remainder is incorrect permission assignments that are not access-right decisions at all (e.g. filesystem umask, ACL syntax errors).

Documented responsibility for protecting assets encourages correct permission settings rather than leaving them at insecure defaults.

Monitoring supplier policy changes and conducting audits can reveal incorrect permission assignments on resources managed by the supplier, prompting corrective action before they are exploited.