Fix it now
ESET PROTECT Advanced is bought for two things: full disk encryption managed from the same console as everything else, and cloud sandbox analysis of files the local layers cannot judge. Both replace a manual process rather than adding another alert stream, which is the right shape for a business with no security staff.
- Buy it if laptops leave the building with client or personal data on them and you cannot currently show that they are encrypted.
- Buy it if unknown attachments and downloads are your realistic risk and you want them judged before they run.
- Skip it if every machine is a desktop that never moves and you already escrow encryption keys through something you run.
- Skip it if your actual weak point is mailbox protection for Microsoft 365, which is a different part of the range.
- Test recovery on a pilot machine before you enable encryption anywhere else, and have the component list written on your quote.
An encryption rollout is the one part of this product that can destroy data. Take a backup, prove you can recover a locked pilot machine, and exclude any device with a failing disk or an unusual boot configuration before enabling it anywhere else.
If that settles it you can stop here. If you want the detail on encryption, the sandbox and the licensing questions, read on.
Why it happens
ESET Full Disk Encryption is the component this tier is bought for, and its shape is worth understanding. ESET documents it as an add-on native to its remote management consoles, managed from ESET PROTECT and ESET PROTECT On-Prem and integrating with Groups, Policies, Tasks and Reports. It supports Windows and macOS and adds pre-boot login. In other words, it is not a separate tool bolted alongside your endpoint management; it is administered from the console you already use, which is most of its value.
Encrypting a laptop is not the hard part. Windows and macOS both include whole-disk encryption at no cost, and for a handful of machines with a careful owner that is sufficient. The hard parts are proving that a specific laptop was encrypted on the day it went missing, and recovering a machine whose user has forgotten the passphrase. Those are administration problems rather than cryptography problems, and they are what a managed encryption product exists to solve.
One caution on recovery, because it decides how you should roll this out. ESET’s Full Disk Encryption documentation does not state that the console holds recovery keys centrally, so we are not going to tell you that it does. Treat recovery as the thing you test first: encrypt one pilot machine, deliberately lock yourself out of it, and prove you can get back in before a second machine is touched. That advice is correct whichever way the escrow question turns out, and following it costs an afternoon.
The cloud sandbox is the second reason to be at this tier, and ESET is precise about how it behaves. Proactive protection blocks execution until analysis completes, with a configurable maximum wait time, a manual unblock and the option to switch it off. That is a real usability decision rather than a background nicety: held files introduce a delay the user feels. Set the policy deliberately, and consider applying the cautious version to the groups that need it rather than to everyone and then wondering why staff complain about downloads.
Vulnerability and patch management is the quieter capability in this part of the range and often the more valuable one. For most small businesses the realistic route to compromise is an out-of-date browser plugin or document reader rather than anything exotic, so a console that inventories installed software and deploys updates on your schedule does more good than another detection layer would. What we cannot tell you is exactly where its scope ends, because we could not reach ESET documentation that defines it. Ask what it does and does not update, in writing, before you build a patching process around it.
The protection engine itself does not change between tiers, and that is worth saying plainly because tier charts imply otherwise. You are buying management capabilities, not a better scanner.
Full reference
What to have written on the quote
ESET’s public product pages were not reachable during this review, which is a good reason to insist on the component list rather than reproduce a matrix from memory. The tier names change, components move between them, and a quotation is a document you can hold someone to. Ask for these, itemised.
- Full disk encryption: included or add-on, which platforms, and how recovery keys are held and retrieved.
- Cloud sandbox analysis: included, and what the default hold behaviour is.
- Vulnerability and patch management: included, and precisely what categories of software it updates.
- Mail and cloud application protection: whether it is in this tier or the one above.
- Server and mobile coverage: how each is counted against your seat total.
- Term length, seat count, and how a mid-term tier change is credited.
Encryption, done in the right order
- Take a full backup of the pilot machine and confirm you can restore from it.
- Enable encryption on that one machine through a policy, not by hand, so you are testing the thing you will actually deploy.
- Prove recovery before anything else: establish exactly where the recovery key lives and retrieve it from that place, with the machine locked.
- Check the console’s encryption state reporting and confirm it says what you would need it to say to a client or an insurer.
- Exclude devices with failing disks, unusual boot configurations or dual-boot arrangements from the rollout policy.
- Roll out in batches, confirming each batch reports as encrypted before starting the next.
Encrypting a machine that then fails to boot is an inconvenience if you have the recovery key and a catastrophe if you do not. Nothing in this list is optional, and the order matters.
The sandbox and the delay it introduces
| Policy choice | What the user experiences | Where it fits |
|---|---|---|
| Hold until a verdict returns | A wait on unknown files, bounded by the maximum wait time you set | High-risk groups: finance, anyone handling inbound documents from strangers |
| Allow while analysing | No delay, with the verdict arriving afterwards | General staff, where the delay would cost more than it buys |
| Off | No sandbox behaviour at all | Rarely correct at a tier you bought for the sandbox |
ESET documents a manual unblock as well, which is the pressure valve that makes the cautious setting survivable. Make sure whoever will be asked to press it knows that they are the one who does.
Encryption against what the operating systems already give you
Be honest about the comparison before you spend. If you already escrow BitLocker or FileVault keys through a directory or device management platform you run, and you can produce a report on demand showing the encryption state of every machine, you have the important part and this tier adds less than it appears to. If you cannot do both of those things today, that gap is exactly what you are buying, and it is the gap that a data protection questionnaire asks about.
Licensing
Licensing is per device on subscription terms, and the tier applies to the licence rather than to individual machines, so you cannot sensibly run one tier on the laptops and another on the desktops within a single estate. Price the whole device count at the tier you need. When stepping up mid-term, ask how the remaining time is credited and whether the encryption component needs a separate deployment step on machines already running the agent. Neither is difficult; both are easier to plan than to discover.
When a licence is the actual fix
ESET PROTECT Advanced is the licence that turns encryption and unknown-file analysis into things your console does rather than things somebody remembers to do. If the reason you are shopping is a laptop fleet you cannot evidence as encrypted, that is a real gap and this is a real answer to it. Arco supplies ESET PROTECT licences across the range, can size the device count including servers, and will insist on one thing before you order: the component list itemised on the quote, including how encryption recovery keys are held and retrieved. If your existing tooling already escrows keys and reports encryption state, we will tell you the lower tier is enough.
Questions people ask about this
Does this replace BitLocker?
It gives you encryption managed from the same console as your endpoint policies, with pre-boot login, on Windows and macOS. Whether it replaces what you have depends on whether you can currently escrow keys and produce an encryption-state report. If you can, you hold the important part already.
Where do the recovery keys live?
Get that answered in writing before you deploy. ESET’s Full Disk Encryption documentation describes the component as managed from the PROTECT consoles and integrated with Groups, Policies, Tasks and Reports, but does not state that the console stores recovery keys, so we are not going to tell you it does. Test a recovery on a pilot machine before touching a second one.
Will the sandbox delay attachments and downloads?
Only if you configure it to. ESET documents proactive protection that blocks execution until analysis completes, with a configurable maximum wait time, a manual unblock and the option to turn it off. Choose the cautious setting for high-risk groups rather than for everyone.
What does the patch management actually cover?
Ask, and get it in writing. It inventories installed software and deploys updates on your schedule, but we could not reach ESET documentation defining its scope, so treat any claim about what it does or does not update, including operating system feature updates, as something to confirm against your quote.
Is it worth the step up for ten machines?
If those ten include laptops carrying client data, usually yes, because one lost unencrypted laptop costs more than the difference. If they are ten desktops in one room and you already patch them, the lower tier is a defensible and cheaper choice.
