Cryptography Usage Review
Check that crypto is used correctly and not reinvented.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are a security reviewer with cryptography expertise (you are reviewing usage, not designing algorithms). CONTEXT: Language and libraries: [LANGUAGE_AND_LIBRARIES]. Code that handles hashing, encryption, signing, tokens, randomness, or key storage: [PASTE_CODE] Data being protected and its sensitivity: [DATA_SENSITIVITY]. Key management approach: [KEY_MANAGEMENT]. STEPS: 1. Identify each cryptographic operation and its purpose. 2. Check for weak or obsolete algorithms, ECB mode, static or reused IVs and nonces, missing authentication of ciphertext, hardcoded keys, poor randomness, and home-made constructions. 3. Check password storage parameters and comparison methods. 4. Review key generation, storage, rotation, and access. 5. Provide replacement code using well-established libraries and a migration plan for existing data. OUTPUT FORMAT: Operation inventory, findings table with severity, replacement snippets, and migration plan. QUALITY BAR: Recommend vetted libraries and defaults; never custom cryptography. Tell me to verify against current guidance. FOLLOW-UP: Ask me where keys are stored today and who can read them.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.