ENCRYPTION

There are lots of different encryption solutions on the market, some which come with other applications and some that are stand alone. I’m not going to attempt to put one up against another but rather have a more generic look at the subject. I’m also not going to worry too much about the technicalities of how they work as frankly, most clients, many of which are SMEs, don’t really care about that. It’s the effectiveness and what they are going to get for their buck, that they care about.
There are essentially two main types of encryption, whole disc encryption (WDE) and file level encryption (FLE). WDE protects the device if the disk is offline or stolen. It’s the type of encryption that comes with Windows (Bitlocker) and with a Mac (File Vault). FLE on the other hand protects the data itself, even if stored on unlocked or shared systems. It encrypts on a file-to-file basis i.e. it encrypts the files you want to protect, and leaves others unencrypted. It generally operates as an agent-based system and often, but not always, comes as part of another application.
WDE is easy to describe. As you log off, the disc is encrypted so that if the hardware, laptop etc, is stolen, the data on the disc is protected. However as soon as you log on, the disc is unencrypted and so the data is unprotected from an intrusion.
FLE proactively encrypts sensitive files at the file level using AES 256-bit encryption. This makes stolen data completely worthless to attackers, as it cannot be accessed or decrypted without the proper decryption key, which is managed through an agent and defined access controls. By encrypting data automatically and in real-time, FLE ensures data remains protected even if the system is compromised, which can be more effective than traditional reactive security measures that rely on detecting attacks after they occur.
Let’s take a look in a bit more detail at the differences between WDE and FLE.
| Feature | Whole-Disk Encryption (WDE) | File-Level Encryption (FLE) |
| What gets encrypted | The entire drive (OS, apps, swap, all files) | Individual files or folders |
| When data is decrypted | Automatically after the device boots and the user authenticates (e.g., login, pre-boot PIN, TPM key) | Each encrypted file decrypts only when accessed by an authorised app/user |
| Protection scope | Strong against physical theft, lost devices, or disk removal | Strong for protecting sensitive data, shared storage, or cloud backups |
| Visibility of encrypted content | Drive appears unreadable until unlocked | File names can still be visible (depends on tool), but contents are encrypted |
| Use cases | Laptops, desktops, mobile devices | Encrypting documents, databases, specific secrets, or user-chosen data |
| Performance impact | Minimal today, because decryption happens in bulk after unlock, and often uses hardware acceleration | Can be higher if many encrypted files are accessed frequently |
| Granularity / control | Low (all-or-nothing) | High (encrypt only what needs protection) |
| Key management | One main disk key (often protected by TPM or secure hardware) | Many file keys or per-user/per-file keys possible |
| Security if system is compromised while powered on | Weak (disk is unlocked, malware can read everything) | Better (files are only decrypted when opened, limiting exposure) |
One question I get asked a lot is, does encryption protect against Ransomware. The short answer is no. WDE only protects the data when the machine is switched off. Once booted up the data is unencrypted. FLE protects data against data leakage or theft in that it can’t be read by unauthorised persons. However, it can’t prevent encrypted data from being encrypted again by a ransomware attack.
A secondary aim of most ransomware attacks is to steal the data to sell on or to use for other things. In those cases, FLE does help protect because the ransomware can’t decrypt the already encrypted data. So, there is a level of protection using FLE that you can’t get with WDE.
FLR can help a little (but still not enough):
It can slow or limit ransomware only if:
- Keys are stored in a separate secure environment (HSM, smart card, enclave, etc.)
- Decryption requires per-file user interaction ransomware cannot mimic
- The storage supports immutable or version-protected encrypted blobs
Even in those cases:
- Ransomware can still delete files, encrypt them again, or lock the device
- It usually cannot be used as a full defence strategy
What it does not prevent
- Files being encrypted again by ransomware
- Files being deleted or corrupted
- The system being locked or made unusable
What it can still be good for
• Preventing data theft if files are exfiltrated
• Limiting extortion via stolen data leaks
• Protecting backups stored in cloud/shared drives from being read by attackers
My focus as always is on the SME community and therefore I always aim to keep costs down to a level that makes sense to them. I am much more a fan of FLE than WDE however, as WDE comes from with both Windows and Mac, then let’s use it. Many corporate organisations use both as a belt and braces protection. But remember, on its own it’s not a total solution and should be implemented as part of a more holistic cyber defence.
I hope this has given an insight into the subject and answered some basic questions. If you would like to understand more about this then please give me a call or an email, I’d be delighted to chat it over.

Recent Comments