CVE-2023-39214

Controls whether organization resources are exposed to external system spheres by permitting or prohibiting their use.

The control ensures information is not released into a security sphere where the recipient lacks matching access authorizations.

The control ensures information resources are not exposed to the incorrect (public) sphere through review and authorization.

Protects against data mining that would expose resources to unauthorized spheres by enforcing detection and controls.

Restricts information flows to ensure resources are not exposed to incorrect or unauthorized spheres.

Controlling internal connections prevents exposure of resources to unintended internal spheres.

Knowing exact processing and storage locations helps avoid exposure of resources to incorrect spheres.

Explicitly prohibiting dangerous or unnecessary functions and services prevents exposure of methods that could be directly exploited.

Vulnerability identification processes will surface exposed dangerous methods during assessment.

Logical access controls at the network/environment layer can limit reachability of exposed functions.

Restricting privileged utility programs reduces exposure of dangerous functions, but does not eliminate the underlying weakness.

Privileged access rights limit who can invoke dangerous methods, but do not address whether the method itself should exist.

Placing systems of differing trust levels into separate domains prevents resources from being placed in a sphere where they are reachable by unintended actors.

Secure development life cycle requires removal or protection of dangerous APIs during design and coding.

Application security requirements can mandate that dangerous methods are not exposed in interfaces.