crypto-implementation-reviewer

To audit cryptographic implementations, provide the repository path and scope to identify insecure practices, focusing on AES usage, IV/nonce handling, and key management. This review checks for modern algorithms like AES-256-GCM and flags weak ones like DES and AES-ECB.

Common cryptographic mistakes include using weak algorithms like DES, 3DES, or AES-ECB, improper IV/nonce generation, and hard-coding keys. A cryptographic audit checks for these issues and verifies keys are sourced from secure stores like KMS or environment variables.

To check for hard-coded encryption keys, an audit verifies that keys are sourced securely from environment variables or Key Management Systems (KMS) rather than directly embedded in the codebase. This prevents unauthorized access to sensitive data.

Secure data protection requires authenticated encryption algorithms like AES-256-GCM or ChaCha20-Poly1305. An audit enforces these modern algorithms to ensure data is securely encrypted at rest and in transit, preventing common crypto vulnerabilities.

The best way to ensure authenticated encryption is to use AES-256-GCM or ChaCha20-Poly1305 and verify secure IV/nonce generation. An audit enforces these standards and provides secure encryption and decryption snippets for your application.

You should avoid AES-ECB in cryptographic implementations whenever you need secure data protection, as it does not hide data patterns. A code audit flags AES-ECB as a weak algorithm and recommends modern authenticated encryption alternatives.