Case 1 high · replace-now
When
- algorithm contains one of HMAC-MD5, HMAC-SHA1
Finding title template
Apex generates {{asset.algorithm}} MACs
Current crypto template
{{asset.algorithm}}
Severity / status
high · deprecated-by-date
Effort / deadline
low · 2030-12-31
Recommended replacement
Replace with Crypto.generateMac('hmacSHA256', ...) or hmacSHA512.
Rationale
HMAC constructions over MD5 and SHA-1 are not broken the way the raw digests are, but NIST SP 800-131A Rev 3 retires all SHA-1 and MD5 based mechanisms, and BSI TR-02102 does not include them among recommended MAC mechanisms. Migrate MAC generation to SHA-256 or stronger before the 2030 retirement.
Citations
- NIST_SP_800_131A · Transitioning the Use of Cryptographic Algorithms and Key Lengths
- BSI_TR_02102_1 · Cryptographic Mechanisms: Recommendations and Key Lengths
Case 2 critical · replace-now
When
- algorithm contains one of RSA-SHA1, ECDSA-SHA1
Finding title template
Apex signs with {{asset.algorithm}} — SHA-1 signatures are disallowed
Current crypto template
{{asset.algorithm}}
Severity / status
critical · already-non-compliant
Effort / deadline
medium · 2010-12-31
Recommended replacement
Re-sign with Crypto.sign('RSA-SHA256', ...) today — SHA-1 signature generation has been disallowed since 2013 — and track the asset for ML-DSA (FIPS 204) migration alongside the rest of the signature inventory.
Rationale
NIST SP 800-131A disallows SHA-1 for digital signature generation, and the underlying RSA/ECDSA primitive is additionally on the post-quantum transition path under NIST IR 8547 and CNSA 2.0. Note that in Apex, Crypto.sign('RSA', ...) is an alias for RSA-SHA1.
Citations
- NIST_SP_800_131A · Transitioning the Use of Cryptographic Algorithms and Key Lengths
- NIST_IR_8547 · Transition to Post-Quantum Cryptography Standards
- BSI_TR_02102_1 · Cryptographic Mechanisms: Recommendations and Key Lengths
Case 3 critical · replace-now
When
- algorithm contains one of MD5, SHA-1, SHA1
Finding title template
Apex uses {{asset.algorithm}}
Current crypto template
{{asset.algorithm ?? weak hash}}
Severity / status
critical · already-non-compliant
Effort / deadline
low · 2010-12-31
Recommended replacement
Replace with Crypto.generateDigest('SHA-256', ...) or SHA-3.
Rationale
NIST SP 800-131A disallows MD5 and SHA-1 for security-relevant use, and BSI TR-02102 reaches the same conclusion.
Citations
- NIST_SP_800_131A · Transitioning the Use of Cryptographic Algorithms and Key Lengths
- BSI_TR_02102_1 · Cryptographic Mechanisms: Recommendations and Key Lengths
Case 4 critical · replace-now
When
- algorithm contains one of HARDCODED
Finding title template
Hardcoded cryptographic key in Apex
Current crypto template
Hardcoded key material in source
Severity / status
critical · already-non-compliant
Recommended replacement
Move the key to a Named Credential or Protected Custom Setting. Maintain an owner and rotation procedure for the secret, and rotate it immediately because the current value must be treated as compromised.
Rationale
Hardcoded cryptographic keys bypass key-management controls and collapse the separation between code and keying material. Once source is exposed, the embedded key must be treated as compromised.
Citations
- NIST_SP_800_53 · Security and Privacy Controls for Information Systems and Organizations
- NIST_SP_800_57_PT1 · Recommendation for Key Management: Part 1 - General
Case 5 high · plan-2030
When
- algorithm matches predicate quantum-vulnerable-signature
Finding title template
Apex signs with {{asset.algorithm}}
Current crypto template
{{asset.algorithm}}
Severity / status
high · deprecated-by-date
Effort / deadline
medium · 2030-12-31
Recommended replacement
Plan migration to ML-DSA (FIPS 204). Where the relying party cannot yet accept PQ signatures, treat the asset as a tracked transition item and move to hybrid certificate or signature strategies as the surrounding platform permits.
Rationale
NIST IR 8547 and NSA CNSA 2.0 both put digital-signature migration on the near-term transition path. Salesforce does not yet expose FIPS 204 primitives in Apex, so the immediate requirement is inventory, shortened rotation, and partner-readiness planning.
Citations
- NIST_IR_8547 · Transition to Post-Quantum Cryptography Standards
- NIST_FIPS_204 · Module-Lattice-Based Digital Signature Standard (ML-DSA)
- NSA_CNSA_2_0 · Commercial National Security Algorithm Suite 2.0 FAQ