Use BitLocker on Windows and FileVault on Mac under one policy that checks encryption, recovery access, and forecast file handling.
Key takeaways
- Inventory Windows hardware and Mac chip types before rollout.
- Ask IT to confirm encryption is on for each laptop.
- Store recovery material where administrators can retrieve it, and test retrieval.
- Set one rule for forecast files copied to removable drives.
Why this comes up before close
Encryption questions often wait until the week a close is due. Then someone asks whether the forecast file on a rep's laptop is protected, and nobody knows the answer for every machine in the team. A mixed fleet makes this harder. BitLocker on Windows and FileVault on Mac are encryption options whose setup must be checked on each device.
This post compares the two options: BitLocker on Windows and FileVault on Mac. It is written for revenue leaders who do not run device management but need one clear standard for forecast files on every laptop. The goal is a policy your IT team can carry out and you can check, not a technical deep dive.
The CISA industry page describes its work as helping organizations manage risk and increase resilience using all available resources, including those from the federal government and commercial vendors. Built-in tools from Microsoft and Apple are commercial resources that may already be on your laptops. The useful question is less about which vendor you trust and more about which setup your team can run the same way every time.
What encryption does and does not cover
Forecast files usually hold pipeline detail, quota assumptions, and rep-level numbers. You would not want those readable if a laptop was lost, stolen, or handed to a stranger for repair. In general terms, full-disk encryption keeps data on the drive scrambled unless the device is unlocked, which is the protection you want in those cases.
It does not cover everything. Once someone opens a forecast and copies it to a shared folder, emails it, or drops it on a USB stick, the file leaves the protection of the laptop's disk. Encryption is one control among several. A policy that only says turn on encryption will leave gaps that show up during close. Review pipeline export checks when deciding how downloaded forecast files should be handled.
There is also a timing problem. A laptop that cannot be unlocked, or whose recovery key nobody can find, can hold up a submission at the worst moment. So when you compare the two options, focus on three things: how each tool is set up, how recovery works, and what you need to verify on each device before the close window.
The two options at a glance
| Topic | BitLocker on Windows | FileVault on Mac |
|---|---|---|
| Hardware to check | TPM version and firmware when using a TPM | Apple silicon or a T2 chip for the internal volume protection described here |
| What to check on each device | TPM version and BIOS mode | Chip type |
| Recovery | A recovery password of 48 digits | A recovery key you plan and store on purpose |
BitLocker on Windows laptops
BitLocker can use the TPM, a chip on the device, as part of its protection. Microsoft's BitLocker overview states that for BitLocker to use the system integrity check provided by a TPM, the device must have TPM 1.2 or later versions. Check the TPM version on every Windows laptop before rollout. Do not assume the fleet is uniform just because the purchase order was.
Firmware settings matter too. The same overview says TPM 2.0 is not supported in Legacy and Compatibility Support Module (CSM) modes of the BIOS, and that devices with TPM 2.0 must have their BIOS mode configured as native UEFI only. A laptop set up with older boot settings may need a firmware change before BitLocker can rely on the TPM. Firmware changes are an IT task. Schedule them well before close, not the night before.
The overview also says that after BitLocker is turned on, the device should have approximately 250 MB of free space. That is not much, but check free space before you enable encryption, and clear room on laptops that are already tight.
BitLocker can also require a startup PIN. Microsoft's BitLocker questions says the PIN can consist of 4 to 20 digits, as specified by the Configure minimum PIN length for startup policy setting, and is stored internally as a 256-bit hash of the entered Unicode characters. In practice, the length is a policy decision, not an individual choice. Decide whether your team accepts a PIN at startup, since it adds a step each time a laptop boots, and set the minimum length in policy rather than leaving it to each person.
The same Microsoft page describes a recovery password of 48 digits divided into eight groups. Treat that as the thing people will need on a bad day. Store recovery passwords somewhere your administrators can reach, not only on the laptop they unlock. Before close, test retrieval on a spare device so nobody discovers the process for the first time under deadline pressure.
FileVault on Mac laptops
FileVault works differently. Apple's FileVault guide says internal volume encryption on a Mac with Apple silicon, as well as those with the T2 chip, is implemented by constructing and managing a hierarchy of keys, and builds on the hardware encryption technologies built into the chip. For whoever runs your fleet, the practical step is simple: know the chip in each Mac. Split the list into Apple silicon and T2 Macs, and everything else. The guide describes internal volume protection for those first two groups, so do not assume every Mac in your fleet is covered the same way.
Apple's guide also says encryption of removable storage devices doesn't use the security capabilities of the Secure Enclave and is performed the same way as on an Intel-based Mac without the T2 chip. That is the detail most likely to surprise a revenue team. A forecast copied to an external drive does not get the same chip-based protection as the internal disk, so the drive needs its own protection, or the file should stay off it.
Recovery planning is its own step on a Mac. Ask IT how recovery keys are generated, where they are stored, and how a rep gets help when they forget. Then test that path on a spare Mac. The steps depend on your macOS version and your management setup, so treat any written procedure as something IT confirms, not something you assume.
Trade-offs to weigh
Neither option is a reason to delay. The trade-offs are about effort, and about where your remaining risk sits once encryption is on.
BitLocker asks more of your Windows fleet up front. For TPM-based system integrity checks, the BitLocker overview requires TPM 1.2 or later; TPM 2.0 devices need native UEFI mode, and approximately 250 MB should remain free after BitLocker is turned on. Those checks take real work, but they can be verified device by device.
FileVault is simpler to reason about on supported Macs, because the protection is built on the chip. The catch is that the chip is what you have to inventory. A Mac you cannot place in the Apple silicon or T2 group is a Mac you cannot assume is covered, and it needs an answer from IT before close.
Removable storage is the shared weak point. Whatever the tool, the rule about where forecast files may be copied does most of the work, so write it once and apply it to both platforms.
Recovery is the shared cost. Either platform can leave a person locked out of their own laptop if recovery material is missing or hard to find. Plan for that before you need it, not during a close.
Where the two differ for forecast files
Neither tool is a forecast file tool. Both encrypt the laptop's storage, so the standard has to be written at two levels: the device, and the way files move off it. You cannot run one tool on both platforms, so accept two tools under one policy. Once the policy is clear, the question of which tool is "better" stops mattering.
One policy for both platforms
Here is a policy statement you can adapt. Keep it short enough that people will read it:
> Every laptop that holds forecast files must have its built-in disk encryption turned on, with a recovery method that IT can retrieve. Forecast files may not be copied to removable drives unless IT has approved the drive. Windows and Mac devices follow the same rule, using BitLocker or FileVault as appropriate.
Then work through these steps:
- Inventory every laptop. For Windows, record the OS, the TPM version, and the BIOS mode. For Macs, record the chip type. A shared spreadsheet is enough.
- Turn encryption on through your existing device management. Use the tools IT already runs rather than asking reps to click through setup screens on their own.
- Set the Windows PIN rule. Decide whether a startup PIN is required. If it is, set the minimum length in policy within the 4 to 20 digit range that Microsoft's guidance allows.
- Check free space on Windows laptops. Confirm roughly 250 MB of free space, as the overview describes, and clear room where it is tight.
- Store recovery material centrally. Recovery passwords for Windows and recovery keys for Macs go somewhere administrators control, not in a rep's email or on a sticky note.
- Test recovery on one device from each platform. Use a spare laptop, not a rep's live machine, and time how long the retrieval takes.
- Close the removable drive gap. Tell people where forecast files may go and where they may not, with one short example for each platform.
- Write exceptions down. Any Mac outside the Apple silicon and T2 groups, and any Windows device that fails the TPM or BIOS check, goes on a list with one named owner.
Related guides: Departed rep's mail: 3 steps to save deal evidence · Dropbox sharing checks for a departing rep: 3 controls · Quota and plan changes: 4 figures on rep timing.
Questions to bring to IT
Bring these questions to your IT lead. Each one is answerable in a short meeting, and the answers decide most of the work above.
- Which laptops are on Windows, which on Mac, and which Macs have Apple silicon or a T2 chip?
- Does every Windows laptop using TPM-based integrity checks meet the version and firmware requirements in Microsoft's overview?
- Where are recovery passwords and keys stored, and who can retrieve them?
- Do we want a startup PIN on Windows, and if so, what minimum length?
- Which Macs or Windows devices need an exception, and who owns each one?
For related recovery planning, see the backup and recovery checks.
Illustrative example: a mixed team
The forecast lives in a shared spreadsheet that people download to work offline. Nobody set encryption up as a project. Each laptop was set up on its own, and nobody has compared the results.
Before any laptop is changed, the team lead confirms where recovery passwords and keys will be held, and tests one retrieval on a spare device from each platform. The test shows whether the process is clear to someone who has never done it, which is exactly the person who will need it in a hurry.
The team tests recovery on 2 spare devices before reviewing encryption status across all 20 laptops. Devices with unresolved checks go on the exceptions list with owners.
A self-check for each laptop
Before close, someone should be able to answer these questions for every laptop that holds forecast files. If the answer is no or unknown, the laptop goes on the exceptions list.
- Is disk encryption turned on, and does the device record show it?
- For Windows using TPM-based integrity checks: does the TPM meet BitLocker's requirements, and is the BIOS mode native UEFI for TPM 2.0 devices?
- For Mac: has IT confirmed how this chip and device are protected?
- Is there enough free space on the Windows drive, around 250 MB after encryption is on?
- Is there a recovery method that IT can retrieve, and has it been tested on this platform?
- Are forecast files kept off removable drives unless IT has approved the drive?
A laptop that fails a check needs a named owner and a fix before close.
What to tell your reps
Reps will ask why they need to do anything. Keep the message short and concrete. Three or four points cover most of it:
- Your laptop's disk encryption is part of the standard. Leave that setting on.
- Keep recovery information where IT told you to keep it, not on a sticky note or in a personal inbox.
- Forecast files stay in the approved location. Do not copy them to a USB drive unless IT has approved that drive.
- If you are locked out, contact IT first. Do not try workarounds on deadline day.
A short message like this works better than a long policy document. Reps will read a few lines before a close, and they will not read a long one.
When something goes wrong near close
Plan the response before the problem shows up. Four situations are worth planning for, and each has a simple first move.
- A laptop is locked and the recovery material is missing. Stop. Do not guess at passwords or keys. Ask IT to retrieve the key through the central store you set up above.
- A Windows laptop fails the TPM or firmware check. Flag it on the exceptions list, and ask IT whether the fix is a firmware change they can schedule. Keep working files on an approved location in the meantime.
- A Mac is not in the Apple silicon or T2 group. Treat it as an exception until IT confirms how that machine is protected.
- A forecast file has been copied to a USB drive. Treat it as leaving the approved location. Ask the rep to remove the copy and tell the revenue operations owner, so the file-handling rule gets reinforced rather than quietly ignored.
Start today
Ask IT to check the encryption status and recovery retrieval path for a spare laptop, and record any unresolved checks with an owner.
Questions revenue leaders ask
Do we have to pick BitLocker or FileVault? No, a mixed fleet can use both tools under one policy, with encryption checked on each device. The standard is the policy, and the tools are how each platform meets it.
Does encryption replace access controls? No, encryption does not replace access controls. Encryption protects data on a device that is off or locked. It does not stop a logged-in user from sharing a file, and it does not decide who should see a forecast in the first place.
Who owns this? IT owns the setup and the recovery process. Revenue operations owns the file-handling rule and the pre-close check. Name both owners in writing, so nobody assumes the other one is handling it.
Before close
Encryption rarely fails in the abstract. It fails on the one laptop nobody checked. If you have time for only two things before close, make them the inventory and the recovery test. Those two steps tell you more about your real exposure than any comparison chart.
Once the inventory and the recovery test are done, write the standard down in one page, put the owners' names beside it, and review the exceptions list each time a laptop is replaced or rebuilt. Those are the moments when a device's setup is most likely to drift from the standard, because a replacement arrives with its own setup.