CVE-2023-6450

Engineering principles can require explicit resource acquisition/release patterns that stop improper shutdown from being introduced.

Process isolation confines resource consumption to separate domains, reducing blast radius without stopping the root flaw.

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.

documenting procedures for secure operation, error handling, restart/recovery and resource management (including references to 8.13/8.18) is a governance and dependency control that does not itself stop exploitation of a resource-shutdown flaw; any prevention would require other controls (e.g. code changes or runtime enforcement) configured to act on it

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.

A.8.20 implements network-level protections (firewalls, segmentation, protocol hardening, monitoring, authentication of systems/devices) that can limit abuse of a resource-consuming weakness but do not stop the weakness from being exploitable; the flaw remains present in the product and can still be triggered from an authorized or internal context.