CVE-2023-30351

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.

Central credential stores and rotation policies remove the need for hard-coded credentials in configuration files or code.

Maintaining currency with technologies and practices reduces selection of encryption mechanisms that provide inadequate strength.

Intelligence programs surface reports of campaigns that abuse hard-coded credentials in products, prompting removal or replacement and thereby reducing successful exploitation.

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.

Hardened baselines can enforce minimum cryptographic algorithm and key-length settings.

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

Requiring the organization to define and enforce minimum cryptographic strength prevents deployment of insufficient key lengths or weak ciphers that can be brute-forced.

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.