Skip to content
MD-5

Choose which cookies we can use. You can change this at any time from “Cookie settings” at the bottom of every page.

AES vs DES: key differences, security and which to use

AES vs DES compared on key size, block size, structure, speed and compliance, with the public record of how DES was broken and how to find DES still in use.

By Updated 6 min read

On this page

AES vs DES isn’t a close contest. AES is stronger, faster on modern hardware and required by every current standard. DES can be brute-forced cheaply and has been withdrawn as a standard for over twenty years. The more useful questions are why the gap is so large, and what to do when DES still turns up in a system you’re responsible for.

For the fundamentals of both families of encryption, start with symmetric vs asymmetric encryption.

Side by side

DES AES
Standardized 1977 (FIPS 46 (opens in a new tab)) 2001 (FIPS 197 (opens in a new tab))
Designed by IBM, with NSA input Joan Daemen and Vincent Rijmen, via open competition
Key size 56 bits 128, 192 or 256 bits
Block size 64 bits 128 bits
Structure Feistel network, 16 rounds Substitution-permutation network, 10 to 14 rounds
Hardware support in CPUs None AES-NI (x86, since 2010), ARMv8 crypto extensions
Status Withdrawn 2005 Current standard

Each row matters for a different reason.

Key length: the decisive difference

Every extra key bit doubles the work of a brute-force search. The gap between 56 and 128 bits is therefore a factor of 2^72, about 4.7 × 10^21. No improvement in hardware closes a gap that size.

The fall of DES happened in public, which makes it one of the best-documented examples in cryptography:

  • 1997: the DESCHALL project, a volunteer network of ordinary PCs, found the key for RSA Security’s first DES Challenge in 96 days.
  • 1998: the Electronic Frontier Foundation built Deep Crack (opens in a new tab), a machine costing under $250,000 that found a DES key in 56 hours.
  • January 1999: Deep Crack and the distributed.net volunteer network together found a key in 22 hours and 15 minutes.
  • 2006: university researchers built COPACOBANA (opens in a new tab) from 120 off-the-shelf FPGAs for under $10,000. It found a DES key in 8.7 days on average.

Today, cracking a single DES key is a cheap commercial service. Meanwhile 2^128 has not moved: it remains far beyond the total computation humanity has ever performed.

Block size: the difference people overlook

A 64-bit block means only 2^64 distinct ciphertext blocks. By the birthday bound, you expect a repeated block after about 2^32 blocks, roughly 32 GB, under one key. In chaining modes a repeat leaks the XOR of two plaintext blocks, which is enough to recover secrets from a long-lived stream without touching the key. The Sweet32 attack (opens in a new tab) did exactly this to 3DES in HTTPS and Blowfish in OpenVPN in 2016.

AES’s 128-bit block pushes that threshold to around 2^64 blocks, far beyond any realistic volume.

Structure: how each resists analysis

DES’s Feistel network transforms half the block each round and swaps halves, so encryption and decryption share the same circuit, which was valuable on 1970s hardware. AES’s substitution-permutation network transforms the whole block each round and reaches full diffusion (every output bit depending on every input bit) after two rounds, which is why 10 rounds give it a large security margin.

DES’s internals were actually well designed. When Eli Biham and Adi Shamir published differential cryptanalysis around 1990, DES turned out to be unusually resistant to it, and in 1994 IBM’s Don Coppersmith confirmed the designers had known about the technique in 1974 and tuned the S-boxes against it. Mitsuru Matsui’s linear cryptanalysis (1993) did better, needing about 2^43 known plaintexts, still impractical. Brute force was always the cheaper route. DES failed on its key length, not its design.

AES, by contrast, was designed after both techniques were public and evaluated against them during the competition. The best published attack on full AES is only about four times faster than brute force, as covered in our AES guide.

Speed

DES was designed for dedicated hardware. Its bit-level permutations cost nothing in a custom chip but need sequences of masks and shifts on a general-purpose CPU. AES went the other way: since 2010, x86 processors have included AES-NI instructions that execute a full AES round in silicon, and 64-bit ARM cores have equivalent extensions. AES now runs at several gigabytes per second per core, which is why full-disk encryption and universal HTTPS became practical defaults.

There is no performance argument for DES, or for Triple DES, which runs DES three times.

Compliance status

In the frameworks that matter, DES isn’t discouraged. It’s disallowed.

  • NIST: FIPS 46-3 was withdrawn in 2005 (opens in a new tab). SP 800-131A Rev. 2 (opens in a new tab) then disallowed Triple DES for encryption after December 31, 2023. Decrypting legacy data remains allowed, so old records can be migrated.
  • FIPS 140 validated modules may only use approved algorithms in approved mode. That requirement flows to every vendor selling into US government, which is why AES became universal in commercial products.
  • PCI DSS defines “strong cryptography” as a minimum of 112 bits of effective key strength. DES’s 56 bits fails that by arithmetic.
  • GDPR, HIPAA and similar laws don’t list algorithms, but their relief for breached encrypted data depends on the encryption actually protecting it. A cipher that can be broken for the price of a cloud server is unlikely to qualify.

Where DES still hides

DES rarely appears in an asset register. It hides in protocol settings and defaults:

  • TLS cipher suites: 3DES suites (for example TLS_RSA_WITH_3DES_EDE_CBC_SHA) still enabled on older load balancers, mail servers and appliances. Every mainstream scanner flags them.
  • Windows authentication: LM hashes and NTLMv1 are built on DES, and legacy Kerberos DES encryption types can be re-enabled by old group policies. Our DES guide explains each.
  • Network management: SNMPv3 configured with DES privacy, and IPsec profiles left on 3DES for a partner who migrated years ago.
  • Application code: DES, DESede or TripleDES in a utility class nobody has touched in a decade.

Migrating off DES

  1. Inventory: scan externally and internally, search code and configuration, and ask vendors directly about appliances.
  2. Disable what nothing needs: most 3DES cipher suites can be switched off immediately with no client impact.
  3. Re-encrypt stored data: decrypt with the old key, re-encrypt under AES-GCM, verify, and only then destroy the old keys.
  4. Isolate what you can’t remove yet: put a gateway in front of a partner who hasn’t migrated, and set a retirement date.
  5. Verify: rescan to confirm the old ciphers are gone. A vulnerability assessment does this across your external estate.

What about quantum computers?

Quantum computing threatens asymmetric algorithms (RSA and elliptic curves) far more than symmetric ones. For AES, Grover’s algorithm offers at best a quadratic speed-up of brute force, which halves effective key strength in theory, and in practice parallelizes poorly. AES-256 keeps a comfortable margin, and it’s what the NSA’s CNSA 2.0 suite specifies for national security systems. DES, already broken by classical computers, doesn’t enter the discussion.

Which to use

  • AES is more secure than DES by every measure, and faster on modern hardware.
  • DES can be brute-forced in hours for little money, and the standard was withdrawn in 2005.
  • Triple DES was a stopgap and has been disallowed for encryption since the end of 2023.
  • Any DES or 3DES still running is a compliance finding and a migration to plan.

Sources

Published by

· Certified cybersecurity services

Articles are researched and written in-house and link to their primary sources (standards, advisories, papers and public datasets) so you can check every claim. Spotted an error? Email contact@md-5.com and we’ll correct it.