crypto-compliance

To detect banned cryptographic primitives, review changed files for unsafe hashes, ciphers, and key sizes such as MD5, SHA-1, DES, 3DES, RC4, and weak RSA. A policy gate blocks these insecure code changes from proceeding until verified.

To prevent TLS misconfigurations, enforce transport security checks that reject code changes disabling certificate verification. This ensures weakened TLS settings are blocked before they can ship to the codebase.

Cryptographic code compliance verifies that hashing, signing, encryption, key derivation, and random number generation adhere to approved primitives. You need a policy gate whenever code changes import crypto libraries or modify security-sensitive functions.

To validate code changes against an approved cryptographic primitive list, compare updated hashing, encryption, and TLS configuration code against project policy. Findings are then routed through an auth-crypto-reviewer agent for final verification.

Yes, crypto review works for changes that generate security-sensitive randomness or derive keys. It applies to any code change that hashes, signs, encrypts, or imports crypto libraries, verifying them against project policy.