CVE-2023-3456

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.

The control prevents exposure of the media resource to the wrong security sphere.

Network segmentation and unauthorized-access protections reduce the chance of resources being reachable by the wrong sphere.

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-coding guidelines and mandatory security testing (including code scans) compel developers to validate and sanitize inputs at design and implementation time, lowering the incidence of malformed or malicious data reaching downstream components.

Mandating input controls that include integrity checks and input validation ensures that untrusted data is examined before use, blocking the root cause of many injection and malformed-data weaknesses.

Security-by-design principles explicitly call for data validation and sanitization at every layer, reducing the chance that malformed or malicious input will be processed without scrutiny.

Requiring language-specific secure coding standards, peer review, SAST and documented mitigation of common programming errors forces validation of all inputs before they are trusted.