Free tools Windows power users keep installed
One-click scans. No signup required.
Encryption does not switch off on one universal date. It can become too weak to trust, a key or software flaw can expose it, or a secure service can become unavailable for an operational reason such as an expired TLS certificate. Those are different problems, and each calls for a different response.
What does it mean for encryption to “stop working”?
The phrase can describe three distinct failures:
| Failure mode | What fails | Likely consequence | Typical response |
|---|---|---|---|
| An algorithm or key length becomes inadequate | The cryptographic method or strength protecting data | Confidentiality or integrity may no longer be dependable against a capable attacker. | Transition to stronger algorithms or keys according to an appropriate standards-based plan. |
| A key or implementation is compromised | A private key, cryptographic library, or related system component | An attacker may be able to decrypt, impersonate, or otherwise undermine protected communications, depending on the flaw and exposure. | Patch affected software and, when needed, revoke and replace certificates and keys. |
| A secure connection fails operationally | A certificate or the application and configuration that rely on it | Clients may refuse to connect even though no one has cracked the encryption. | Renew and install a valid certificate; check configuration and service operation. |
These distinctions matter: a connection error is not proof that the encryption algorithm has been broken, while a connection that still works is not proof that its cryptography remains adequate.
How can encryption become less trustworthy over time?
Cryptographic choices that were once considered acceptable may need to change as attacks improve, computing capabilities grow, or standards evolve. NIST’s SP 800-131A Rev. 2, published in March 2019, sets out transition guidance for cryptographic algorithms and key lengths. Its publication record notes that an initial public draft of Rev. 3 was posted on October 21, 2024; the cited Rev. 2 guidance should not be mistaken for a universal expiry date for every encrypted system.
There is no single calendar date when all encryption becomes unusable. Whether a particular system needs a change depends on the algorithms and key lengths it uses, the data it protects, the threats it faces, and applicable standards or policy requirements. Organizations need an inventory of cryptographic use so they can identify affected systems and prioritize changes rather than assume that one date applies everywhere.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →#1 Best Overall
- Hardware encrypted drive
- Simple to use pin access. RPM-5400
- Administrator password feature
- Bus powered
- Utilizes Military Grade FIPS PUB 197 Validated Encryption Algorithm
Can a quantum computer make encryption stop working?
Quantum computing is a reason to plan migration for cryptography that could be vulnerable to future quantum capabilities; it is not evidence that ordinary encryption has already been generally broken. NIST says three finalized post-quantum standards were released on August 13, 2024, and are ready for implementation. That is a count of standards, not a forecast of when any current system will fail.
NIST’s post-quantum migration project describes work that begins by finding where vulnerable public-key cryptography appears across hardware, software, and services. Organizations can then assess risk, prioritize changes, build migration roadmaps, and test interoperability. The practical point is to discover and plan, not to replace ordinary consumer devices solely because quantum computers exist.
Rank #2
- Utilizes Military Grade FIPS PUB 197 Validated Encryption Algorithm
- Super fast USB 3.0 Connection - Data transfer speeds up to 10X faster than USB 2.0
- Software Free Design - With no admin rights needed
- Sealed from Physical Attacks by Tough Epoxy Coating
- Brute Force Self Destruct Feature
NIST’s May 2022 policy explanation described a 2035 transition goal, while also saying a deprecation timeline would be developed as inventories, budgets, impacts, and quantum progress became better understood. Treat 2035 as the historical goal stated on that page, not as a current universal expiry date for encryption. See NIST’s policy explanation.
How can a key or cryptographic implementation be compromised?
Encryption depends on more than an algorithm: it also depends on keeping private keys protected and implementing cryptography correctly. A compromised certificate authority, vulnerable algorithm, or bug in a cryptographic library can require organizations to replace certificates and private keys. NIST’s National Cybersecurity Center of Excellence (NCCoE) recommends maintaining inventories and the ability to respond quickly to such incidents in its TLS Server Certificate Management guidance.
Rank #3
- Slim durable design to help take your important files with you
- Vast capacities up to 6TB[1] to store your photos, videos, music, important documents and more
- Back up smarter with included device management software[2] with defense against ransomware
- Help secure your important files with password protection and hardware encryption
- 3-year limited warranty
The remedy depends on what was exposed. A software vulnerability calls for fixing the affected implementation; a compromised key may call for revoking and replacing it and its certificate. Merely renewing an expired certificate does not address a separate software flaw or key compromise.
What happens when a TLS certificate expires?
A TLS certificate helps a client verify a server’s identity and establish a secure connection. If it expires without being replaced, clients commonly report an error and stop the connection. NIST NCCoE puts it directly: “If a server certificate is not changed before its expiration date, then clients should generate an error message and stop the connection process to the server.” That is a service-availability failure; by itself, it does not show that the encryption algorithm was cracked.
Rank #4
- Easily store and access 2TB to content on the go with the Seagate Portable Drive, a USB external hard drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Certificate handling is an operational responsibility: the owner needs to know when a certificate expires, renew it, install the replacement, and check that the service works. NIST NCCoE recommends continuous expiration monitoring and periodic checks of operation, configuration, and policy alignment. Its implementation guide gives examples such as renewing and testing at least 30 days before expiry. That is guidance in the NIST guide, not a universal deadline for every certificate environment.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What should an organization monitor and prepare?
A useful plan addresses both gradual cryptographic transitions and urgent incidents. NIST NCCoE’s certificate-management guidance supports the following practices:
- Inventory cryptography. Record where algorithms, keys, certificates, libraries, and dependent services are used, with accountable owners.
- Monitor certificate lifecycles. Track expirations continuously and check that certificates are operating, configured, and aligned with policy.
- Renew and test ahead of expiry. Plan installation early enough to test the replacement; the guide’s 30-day example is a recommendation, not a universal rule.
- Prepare for compromise. Establish a way to revoke and replace affected certificates and keys quickly, and to patch vulnerable implementations.
- Plan standards transitions. Identify algorithms and key lengths that may need to change, prioritize by risk and impact, and test replacements before broad deployment.
- Assess post-quantum exposure. Find vulnerable public-key cryptography in hardware, software, and services, then plan migration and interoperability testing.
These controls address different clocks: a certificate has a stated expiration date, an incident may require action immediately, and algorithm migration is planned around changing standards and risk—not a single countdown for all encryption.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
