Skip down to the research record

BitLocker encryption strength: 6 laptop checks

Quota Forecast Editorial Team · Published · 11 min read

Check a rep's BitLocker encryption strength by asking IT to confirm drive protection, TPM use, AES key length, partitions and policy settings.

Key takeaways

  • Use msinfo32 to check device encryption requirements, then ask IT to confirm actual drive protection.
  • Record the TPM version and AES key length against company policy.
  • Ask IT about partitions and any required PIN before clearing gaps.

Forecast work depends on data that often lives on a sales rep's laptop: call notes, deal spreadsheets, exported pipeline reports, and draft commit numbers. If that laptop is lost or stolen, encryption helps restrict access to its stored information. Encryption is the control meant to stop that, and a revenue leader can check it without being a security engineer.

The NIST guide on storage encryption for end user devices describes the basic idea in one line. Storage encryption is "the process of using encryption and authentication to restrict access to and use of stored information." That is the test to keep in mind. Stored data should be hard to use without the right authentication, and your job is to confirm that this is true on the specific laptop a rep uses to build numbers.

This post covers three facts about BitLocker, Microsoft's encryption feature for Windows drives. Each fact explains part of what "encrypted" means on a rep's machine, and each one gives you a question to ask. The facts cover hardware anchoring, encryption strength, and setup requirements.

One caution first. This post does not set your security policy. Where a point depends on your company's settings, the answer belongs to IT or the security team. Use this post to know what to ask and what a good answer looks like.

Why encryption status should gate forecast work

A deal without a close date or a stage does not go into the call. Device encryption belongs in the same family of checks, because the risk is the same kind of risk: the forecast data is only as safe as the place where it sits.

A laptop that is not encrypted is a quiet problem. Nothing looks wrong on the sales side. The numbers still load, the CRM still syncs, and the rep still sends the deck. The gap only shows up when the device leaves the rep's control. By then, the forecast data may already be exposed, and the team has no record showing that the device was checked.

That is why the check should happen before forecast work continues, not after an incident. A short written confirmation for each laptop gives you a record, and it gives IT a clear question to answer. It also keeps the conversation concrete. "Is the laptop encrypted?" invites a quick yes. "What key length does it use, and does a TPM back it?" forces a real answer.

Fact 1: Check the device, then check for a TPM

The fastest starting point is the System Information app. Microsoft's BitLocker overview says: "You can check whether a device meets requirements for device encryption in the System Information app (msinfo32.exe)." Ask the rep to open that app, run the check, and send you the result that shows whether the device meets the device encryption requirements. Ask for the exact text, not a summary, so you are not relying on someone's memory of what the screen said.

Be clear about what that answer means. A device that meets the requirements is a device that can be encrypted. The check does not, on its own, prove that the operating system drive is encrypted right now. Treat the result as the first half of the answer. The second half comes from IT, who can confirm the actual state of the drive and its protection settings.

The second check is hardware. The same overview says: "BitLocker provides maximum protection when used with a Trusted Platform Module (TPM), which is a common hardware component installed on Windows devices." Ask IT whether a TPM is present on this laptop and whether BitLocker is set up to use it.

Microsoft's BitLocker configuration guidance states: "The recommended practice for BitLocker configuration on an operating system drive is to implement BitLocker on a computer with a TPM version 1.2 or higher." If IT cannot tell you which TPM version the laptop has, ask for confirmation before deciding whether it meets company policy.

Fact 2: AES is the algorithm, and key length sets the level

Many people hear "encrypted" and assume there is one fixed level of protection. It states: "BitLocker uses Advanced Encryption Standard (AES) as its encryption algorithm with configurable key lengths of 128 bits or 256 bits." It then adds: "The default encryption setting is AES-128, but the options are configurable by using policy settings." Both lines come from the BitLocker questions page.

Put simply, two laptops can both show BitLocker as on and still use different key lengths. One may run the default AES-128. Another may have been set by policy to use the 256-bit option. In general, a longer key is harder to guess by brute force, so the key length is one part of how strong the encryption is. This post does not say which length your company needs, because that decision belongs to your security team and its policy.

Illustrative example: An incomplete answer

A rep reports that a laptop is encrypted, but the written reply does not identify its key length. Record the key length as unknown and ask IT to confirm the setting against company policy. If IT confirms that the setting matches policy, record that answer with the device name and check date. Keep any unanswered items open rather than treating the initial reply as clearance.

Your part is to ask two questions. Which key length does this laptop use? And does that match the policy your security team has set? If the answer is "the default," ask IT to confirm in writing that the default meets policy. A vague "it's encrypted" answers neither question, so ask again and ask for the specific setting.

Fact 3: Partitions and PIN settings decide what BitLocker can do

Setup details matter because they decide whether BitLocker can run as designed. Microsoft says: "Two partitions are required to run BitLocker because pre-startup authentication and system integrity verification must occur on a separate partition from the encrypted operating system drive." That is the same questions page. A laptop that lacks the second partition does not meet that stated requirement, so it is a gap to raise with IT, not a detail to wave through.

In plain words, the setup separates the part of the disk that handles startup checks from the part that holds the encrypted operating system. You do not need to manage that layout yourself. You do need to know that it exists on the laptop. Ask IT to confirm the partition layout as part of the check, not only whether encryption is switched on.

Microsoft also covers PINs. It says: "BitLocker hashes the user-specified personal identification number (PIN) by using SHA-256, and the first 160 bits of the hash are used as authorization data sent to the TPM to seal the volume master key." You do not need to check the math, and a revenue leader should not try. What matters is practical. Does your policy require a PIN? If it does, is a PIN set up on this laptop? If policy requires one and the laptop has none, that is a finding to raise.

Keep the PIN question separate from the TPM question, but ask IT to answer both in the same message. Microsoft's description of the PIN refers to the TPM, so the two answers are easier to read together than apart.

What a good answer looks like

A written answer from IT is only useful if it names the specific settings. A reply that says "device is compliant" tells you nothing you can check. A reply that says "BitLocker is on for the operating system drive, the TPM is present at version 1.2 or higher, AES key length matches policy, the partition layout is in place, and the PIN requirement is met" gives you something you can record and defend.

The same goes for the rep's reply. "My laptop is encrypted" is not a result. A msinfo32 result that shows the device meets the requirements, sent with the device name and a date, is a result. Ask the rep for the exact line, not a paraphrase.

Today, send IT the checklist below for the laptop used in your next forecast review and record any unanswered items.

Questions revenue leaders often ask

Is "encrypted" enough to clear a laptop? No, you also need confirmation that its settings match company policy. Ask for the key length and check it against policy.

Do I need to trust the rep's word? You can accept the rep's msinfo32 result as a first step, but the forecast gate should rest on written confirmation from IT about the drive. A rep's understanding of the settings can be honest and still incomplete.

Do I need to understand SHA-256 or the TPM seal? No, those details belong to the security team. Your job is to confirm that the settings exist and match policy, then record the answer.

What about a personal laptop? Ask your security team what evidence they accept before any forecast data goes onto a personal device. This post assumes a company-managed device. Do not assume that a personal device meets the same standard.

A check to run before forecast work continues

Put the three facts into a short checklist, and keep it in the forecast file so the check is repeatable. A checklist also makes it easy to show that the same questions were asked for every rep, not only for the reps you trust least.

  1. Ask the rep to run the msinfo32 check and send the exact device encryption requirement result. The BitLocker overview explains the check.
  2. Ask IT, in writing, to confirm that BitLocker is on for the operating system drive.
  3. Ask IT to confirm that a TPM is present and that its version is 1.2 or higher, as Microsoft recommends for an operating system drive.
  4. Ask IT to confirm the AES key length in use and whether it matches the policy your security team has set.
  5. Ask IT to confirm the partition layout and whether the PIN requirement in policy is met.
  6. Record the device name, the date of the check, and the name of the person who confirmed each item.

Forecast work can continue for a rep once every item has a written answer that matches policy. If an answer is missing, treat the laptop as unverified. Hold that rep's forecast inputs back until the gap is closed, and do not treat a verbal yes as verification. A single missing item is enough to keep the file open.

Make the checklist part of onboarding for new reps, too. Pair it with the rep laptop checks before corporate access so device questions are handled together.

If a check fails

A failed check is common enough to plan for. The most useful response is calm and specific. Do not ask the rep to turn off encryption, change settings, or move files to a personal drive to make a check pass. Those moves make the problem harder to see and do not fix the underlying gap.

Send the device to IT with the specific gap named. Say whether the problem is a missing TPM, a key length that does not match policy, a missing partition, or a PIN that policy requires and the laptop does not have. A precise report lets IT decide the fix quickly, and it gives you a record that the issue was raised.

Decide in advance how the team will handle forecast data while the fix is in progress. Ask IT which managed copy of the pipeline data the rep can use while the device is being corrected, and whether local exports should stop during the gap.

Limits of this check

This check is a snapshot. It shows the configuration at the time it was run. A laptop that passes today can change after an update, a reset, or a new user setup, so the check should be repeated on the schedule your security team sets.

The check also covers the drive settings on one laptop. It does not cover every file a rep creates. The NIST guide describes three types of solutions: "full disk encryption, volume and virtual disk encryption, and file/folder encryption." Full disk protection on the laptop does not, by itself, cover a spreadsheet after it leaves the device. If your forecast files are emailed, synced to other accounts, or copied to removable media, the device check is only part of the picture.

Finally, this post covers Windows devices and BitLocker only. Devices running other operating systems use other tools, and they need their own confirmation. Do not assume that a clean BitLocker result says anything about a rep's phone, tablet, or a different laptop. For related device planning, see the BitLocker and FileVault guide for forecast files.

Sources