key management
3 articles with this tag
Coincheck NEM Heist (2018) — How ~$530M Was Stolen, and the Key-Management Defense
The entry point was reported to be spear-phishing / malware aimed at employees, which stole the private key of an internet-connected hot wallet; ~523 million XEM (~$530M at the time) was then moved out in one sweep. The core failure was keeping a huge, instantly-spendable balance 'hot' and with no multisig — a single stolen key moved almost everything. Defend by keeping important keys cold / in a dedicated vault, minimizing the hot balance, removing single points of failure (multi-approval), and detecting and stopping abnormal bulk operations.
Don't give root keys to environments that can be compromised: SSH key least privilege
Registering a root key into production from an ephemeral, compromisable environment (GPU pod, CI runner, throwaway VM) means that the moment the environment is compromised, production is taken with root. Fix: no root keys on ephemeral environments; remove keys when unused; if needed again, use a non-root user plus a command-restricted key that limits the key to one operation. A reused key is your most critical asset — never build a 'one leak, everything' setup.
Heartbleed (CVE-2014-0160) — when memory leaked from the foundation of encrypted traffic
OpenSSL's memory over-read could leak private keys and sessions. The cause: the server trusted a claimed length and read adjacent memory. The lesson: act as if it all leaked — re-issue certificates, rotate all secrets — plus the weight of foundational software and memory safety.