crypto-storage-auditlisted

# Crypto / Secure Storage Audit Almost no real-world crypto breaks because the algorithm was weak. It breaks because of key handling, nonce reuse, or a policy check enforced in the wrong layer. This skill checks those specifically, not whether AES is a good cipher. ## Check these, in order of how often they're the actual bug 1. **Hand-rolled primitives** — any custom encryption, hashing, or "obfuscation" scheme that isn't a standard, reviewed algorithm via a maintained library. This is an automatic highest-severity finding regardless of how the rest of the code looks — no amount of surrounding code quality offsets inventing your own crypto. 2. **Nonce/IV reuse** — the single most common real-world implementation bug. Check that every encryption operation uses a nonce/IV that is never reused with the same key, and that the generation mechanism actually guarantees this (a counter that can reset, or randomness with a birthday-bound collision risk at the actual usage volume, both count as reuse risk). 3. **Key hierarchy correctness (DEK/KEK or similar envelope schemes)** — verify the data-encryption key is never written to persistent storage or logs in plaintext, and that only the key-encryption key (itself protected, e.g. by a hardware-backed keystore or policy gate) ever touches the DEK in the clear, and only in memory. 4. **Policy/access-control enforcement point** — for policy-gated decryption, verify the gate is actually enforced at the point of decryption/key release, no