Hardware Encryption is not Secure
A Little History…
In the past, it was assumed that hardware encryption is far more secure than software encryption. Many people, including security experts, still believe this to be true. And in the past, it was true.
But recent history has proven that hardware encryption is highly vulnerable. The widely published recently discovered hardware encryption vulnerabilities include Spectre and Meltdown. Both Spectre and Meltdown exploit flaws in processors.
Our good friend Steve Gibson has also outlined severe security vulnerabilities in a hardware-encrypted solid-state drive (SSDs). Every SSD that researchers have examined has been found to have such a critical vulnerability that there is almost no barrier to accessing encrypted data on these drives. Steve outlined the details on his Security Now Podcast.
Reading an older article? Use the brief to stay current.
This Article Gives You the Background. The Brief Gives You What Changed Next.
Get the weekday cyber brief for the attacks, policy moves, and industry shifts that changed the picture after this article was published.
By subscribing you agree to our Privacy Policy.
Free. Weekday mornings. 5 minutes or less.
Backdoors and Poor Encryption Standards
Hardware companies are notorious for including back doors. The expectation or concern is that companies and even governments include back doors at the chip level. This is entirely feasible and also likely.
It has also been reported that poor practices lead to hardware encryption vulnerabilities. For example, encryption keys may not be held securely or may not be unique to each machine.
The Solution?
The solution is quite simple. Ensure that you encrypted your data using reputable software encryption. You will certainly keep your data more secure than with hardware encryption alone. The software should be widely accepted. Don’t use an encryption solution that is lesser-known or obscure. Strong encryption requires methodical perfection in its processes because encryption is only as secure as its weakest link.
I use VeraCrypt or AxCrypt. Both are free, widely accepted, and secure!
Reading an older article? Use the brief to stay current.
This Article Gives You the Background. The Brief Gives You What Changed Next.
Get the weekday cyber brief for the developments, risk shifts, and new signals that changed the picture after this article was published.
By subscribing you agree to our Privacy Policy.
Free. Weekday mornings. 5 minutes or less.
Newer CyberExperts coverage on this topic
This article still works as background. If you want the current picture, start with the freshest related coverage below and today's brief.
Common Encryption Methods in 2026
Practical 2026 guide to encryption methods: AES-GCM and ChaCha20-Poly1305 AEAD, RSA/ECC key exchange, NIST PQC (ML-KEM, ML-DSA, SLH-DSA), TLS 1.3 context, and...
Asymmetric Encryption Example: RSA Explained Step by Step
A step-by-step asymmetric encryption example using small-number RSA, plus how public keys work in TLS 1.3, digital signatures, SSH and email, 2026...
How to Encrypt Your Internet Connection: 7 Methods That Work
How to encrypt your internet connection in 2026: force HTTPS, encrypt DNS, secure Wi-Fi with WPA3, use a trustworthy VPN or iCloud...
Tuesday’s brief: GitLab’s critical fix, then Patch Tuesday, hijacked fridge controllers and Server 2012’s last update
The fastest way to catch up on what changed after this article was published.
Start your morning with the signal that matters.
Get the biggest cybersecurity developments, why they matter, and where to go deeper on CyberExperts.
By subscribing you agree to our Privacy Policy.
Free. Weekdays. Built for operators.
