Home / Wiki / C / Cryptographic Key

Cryptographic Key

Compliance Risk and ControlsUpdated 06 Nov 2026

A cryptographic key is a value, usually a long string of random-looking bits, that a cryptographic algorithm uses to transform data. With the right key, an algorithm can scramble a message so outsiders cannot read it, unscramble it again, produce a digital signature, or check that a signature is genuine. Banks, card networks, payment apps and blockchains all depend on keys to protect money and data.

Keys are the variable part of cryptography. The algorithms themselves, such as AES or elliptic-curve signatures, are public and standardised; security rests on keeping the right keys secret and managing them well. In crypto-assets the stakes are direct, because the private key is what moves the coins, while the public key can be shared freely.

01

Cryptographic keys in plain terms

A padlock design can be sold in every hardware shop; what keeps your locker safe is the particular key that fits your lock. Cryptography works the same way. Everyone knows how the lock works, but only the holder of the right key can open it.

Some systems use one key that both locks and unlocks, like a house key shared with family. Others use a pair: a slot anyone can post letters into, and a single key that opens the box. In payments and crypto, losing a key is like losing the only key to a safe, and copying a key is like handing someone the safe's contents.

02

Symmetric and asymmetric keys

  • Symmetric keys. One shared secret key both encrypts and decrypts. Algorithms such as AES, published by NIST in 2001, are fast and protect stored data, network traffic and card PIN blocks; see data encryption and decryption.
  • Asymmetric key pairs. A private key and a matching public key work together. Data encrypted with the public key can be opened only with the private key, and a signature made with the private key can be checked by anyone with the public key. RSA and elliptic-curve cryptography are the main families.
  • Session and derived keys. Systems often generate short-lived keys from a master key for each session or transaction, so that a single leak exposes little.

In practice the two are combined: an asymmetric exchange agrees a fresh symmetric key, which then encrypts the bulk of the data.

03

Key length and strength

A key's strength depends largely on how many values it could take. For a key of nn random bits, the number of possible keys is:

Number of possible keys=2n\text{Number of possible keys} = 2^{n}

Here nn is the key length in bits. For a 128-bit AES key, 21282^{128} is about 3.4×10383.4 \times 10^{38} possibilities, far beyond what any computer could try one by one. Each extra bit doubles the work for an attacker, which is why AES offers 128-, 192- and 256-bit keys. Asymmetric keys need more bits for the same strength because attacks exploit their mathematical structure: Bitcoin's 256-bit elliptic-curve private keys give roughly 128 bits of security.

04

Keys in payments and crypto-assets

Card and banking systems keep their most sensitive keys inside hardware security modules, tamper-resistant devices that encrypt PINs, generate card verification values and sign messages without ever exposing the key. Customer authentication tools such as one-time passwords (OTP) and app-based strong customer authentication (SCA) also rely on keys stored on the user's device.

On a blockchain, ownership is simply control of a key. Bitcoin (BTC) and Ethereum (ETH) both derive addresses from public keys on the secp256k1 curve, and wallets usually generate all their keys from a single seed phrase. There is no password reset: whoever holds the private key can spend, which is the origin of the phrase Not Your Keys, Not Your Coins.

05

Key management

Most real-world failures come from how keys are handled, not from broken algorithms. NIST's key-management guidance (SP 800-57) describes a lifecycle that firms are expected to control:

  1. Generation, using a strong source of randomness.
  2. Distribution and storage, with keys kept in protected hardware or encrypted under other keys.
  3. Use, limited to a defined purpose and period.
  4. Rotation, replacing keys on a schedule or after any suspected exposure. Planned cryptographic key rotation limits how much data any single key protects, so a stolen or weakened key exposes as little as possible.
  5. Revocation and destruction, so old keys cannot be reused.

Crypto custodians add techniques to remove single points of failure. Cold storage of keys keeps them offline; a multi-sig wallet needs several keys to approve a transfer; and a multi-party computation (MPC) wallet splits one key into shares that are never brought together. These controls are central to crypto custody and are reviewed by auditors and supervisors.

06

Risks and future threats

Keys can be stolen by malware, phishing or insiders; tools such as a private key sweeper script empty a compromised wallet within seconds. Keys generated with poor randomness can be guessed, and lost keys mean permanently lost funds. Looking ahead, a large quantum computer running Shor's algorithm could break today's RSA and elliptic-curve keys. NIST published its first post-quantum cryptography standards, FIPS 203, 204 and 205, in August 2024, and banks, card schemes and blockchain developers are planning migrations to them.

Last updated 06 Nov 2026