CVE-2023-34123

Supplier evaluation and secure acquisition practices make it harder for hard-coded credentials to be introduced via procured products.

Requiring security functional requirements and acceptance criteria allows contracts to prohibit hard-coded credentials in delivered systems or components.

Supplier risk reviews identify and discourage hard-coded credentials in delivered products or services.

Enables users to notice when hard-coded credentials have been exploited for unauthorized access.

Security training explicitly warns against hard-coded credentials, lowering their use in systems.

Policy and procedures prohibit hard-coded credentials in favor of managed authentication.

External identity providers eliminate the need for hard-coded credentials in applications.

Changing default authenticators prior to first use and protecting content prevents use of hard-coded credentials.

PR.AA-01's credential/key-management processes can reduce the incentive to embed secrets but do not address or detect hard-coded values in source code, so the weakness remains fully possible.

Data-at-rest protection policies require proper key management and therefore discourage hard-coded keys.

Data-in-transit protection similarly depends on non-hard-coded keys for encryption.

Configuration baselines and reviews can prohibit hard-coded keys in deployed artifacts.

Education on secure configuration practices discourages technical staff from embedding or relying on hard-coded credentials in systems and applications.

Key-management controls that govern generation, rotation and protection of keys make the use of embedded hard-coded cryptographic keys less likely and easier to detect.

Explicit prohibition of hard-coded passwords and unauthenticated external services stops credentials from being embedded directly in source code.

Contractual requirements for secure coding practices and evidence of testing make it less likely that hard-coded credentials will be introduced or remain undetected in delivered code.