Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Encryption is the process of transforming readable data into ciphertext with an algorithm and a key, so that only someone holding the right key can turn it back into its original form.

What Is Encryption?
Encryption is the use of a mathematical algorithm and a secret key to turn readable data (plaintext) into scrambled data (ciphertext) that is useless to anyone without the correct key. Decryption reverses the process. It is the main technical control that keeps data confidential when it travels across untrusted networks, sits on a lost laptop, or is stored with a cloud provider.
Modern encryption does not rely on keeping the algorithm secret. AES, RSA, and their peers are public and heavily analysed; security comes entirely from protecting the keys, a principle known as Kerckhoffs’s principle.
Symmetric algorithms use the same key to encrypt and decrypt. They are fast and suited to bulk data: disk encryption, database fields, backups, and the actual payload of a TLS session.
A block cipher on its own encrypts one fixed-size block. The mode decides how blocks are chained, and getting it wrong undermines a strong algorithm. ECB mode encrypts identical blocks to identical output, leaking patterns. Authenticated modes such as AES-GCM both encrypt and detect tampering, and should be your default. Reusing a nonce with GCM, however, can be catastrophic, so libraries that handle nonces for you are safer than hand-built code.
Symmetric encryption leaves one problem: how do two parties agree on a shared key over an open network? Asymmetric, or public key, cryptography solves it with a key pair. Anything encrypted with the public key can only be decrypted with the matching private key, which never leaves its owner.
RSA and elliptic curve algorithms (ECDH for key agreement, ECDSA and Ed25519 for signatures) are far slower than AES, so real systems combine the two. In TLS 1.3, for example, the client and server use ephemeral elliptic curve Diffie–Hellman to agree a session key, authenticate the server with a certificate, and then switch to AES-GCM or ChaCha20-Poly1305 for the data itself.
| State | Typical controls | What it stops |
|---|---|---|
| In transit | TLS 1.2/1.3, IPsec, SSH, a VPN | Interception on networks and Wi-Fi |
| At rest | BitLocker, FileVault, LUKS, database TDE, cloud storage encryption | Data exposure from lost or stolen devices and disks |
| End to end | Signal protocol, S/MIME, PGP | Reading by intermediaries, including the service provider |
| In use | Confidential computing enclaves | Exposure in memory on shared infrastructure |
Encryption at rest does not help once an attacker is logged in as a legitimate user, because the system decrypts data for them. That is why it must be combined with access control and monitoring.
Most real-world encryption failures are key failures: keys hard-coded in source code, stored next to the data they protect, never rotated, or held by too many administrators. Good practice includes generating keys with a proper random source, storing them in a hardware security module or a cloud key management service such as AWS KMS or Azure Key Vault, separating key administrators from data administrators, rotating keys on a schedule, and logging every use.
Ransomware shows the other side of the coin: criminals use the same strong algorithms against you. Without the attacker’s key, encrypted files are typically unrecoverable, which is why offline backups matter.
Article 32 of UK GDPR names encryption as an example of an appropriate technical measure. The ICO’s guidance notes that if a lost device was properly encrypted and the key was not compromised, the breach may be unlikely to result in a risk to individuals, which can affect whether you need to notify them. Payment environments face explicit rules too: PCI DSS requires strong cryptography for stored card numbers and for transmission over open, public networks.
A sufficiently powerful quantum computer would break RSA and elliptic curve cryptography, though not well-designed symmetric encryption at adequate key lengths. Attackers can already record encrypted traffic today and decrypt it later. In August 2024 NIST published its first post-quantum standards—FIPS 203 (ML-KEM), FIPS 204 (ML-DSA), and FIPS 205 (SLH-DSA)—and the NCSC has set out a migration timeline running to 2035. The first step is an inventory of where and how your organisation uses cryptography.
Weak TLS settings, missing encryption, and poor key storage are frequent findings in our assessments. Our cloud security services review how encryption and key management are configured across your cloud estate.
Encryption is reversible: anyone with the right key can recover the original data, which makes it suitable for protecting information you need to read later. Hashing is a one-way function that produces a fixed-length fingerprint and cannot be reversed. Hashing is used for integrity checks and password storage, where you only need to compare values, never recover them.
AES-256 is considered safe for the foreseeable future. The known quantum attack on symmetric ciphers, Grover’s algorithm, roughly halves the effective key strength, which still leaves AES-256 with ample margin. The real quantum risk lies with public key algorithms such as RSA and elliptic curves, which is why migration efforts focus on key exchange and digital signatures.
Not automatically. Under UK GDPR you must still assess every personal data breach. If the data was strongly encrypted and the key was not compromised, the risk to individuals may be low, which can remove the duty to notify them. You should still record the incident, and if the key was exposed, the encryption offers no protection at all.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.