Data Protection
Encrypt Data at Rest and in Transit
Check how sensitive files are protected on devices and when sent between systems. Confirm encryption settings and how you would recover a locked device.
Content review: 2026-09-22 · Estimated effort: Medium
Priority and effort are suggestions, not risk scores or deadlines. Check business impact, vendor instructions, licenses and obligations before making changes. Test before wider rollout.
Before you start
Before starting: identify sensitive data and owners. Verify backups and authorized recovery-key access before changing disk or storage encryption.
Put it into practice
- Check encryption features included with your operating systems and cloud services. Pilot on a supported device, following vendor instructions and licensing requirements.
- Verify recovery keys are securely stored and retrievable by authorized staff. Never keep the only recovery key solely on the device it unlocks.
- Expand coverage to sensitive storage and backups. Check provider encryption settings and key ownership before changing keys or access policies.
- Use supported HTTPS/TLS configurations and valid certificates with renewal monitoring. Test service dependencies before disabling obsolete protocols. Review sharing permissions too: encryption does not prevent authorized-account misuse.
- Verify: inspect actual encryption status, test authorized key retrieval without exposing keys, and confirm certificate validity and service connectivity after changes.
Use what you have
Tools and templates
“Included” tools require an eligible product or subscription. Options reviewed 2026-09-22; check current vendor terms.
Start without another software subscription
Check whether the existing Windows device supports BitLocker or Device Encryption and verify recovery access before changing settings.
What to account for: Where neither is available, record the gap and assess a supported upgrade or suitable device. File-only encryption is not an equivalent substitute for whole-device protection; central management may need separate licensing.
Allow for equipment, storage and staff time. Eligibility details are linked below.
Windows BitLocker and Device Encryption
Edition- and hardware-dependent Windows features; check eligibility
Check encryption status and confirm authorized recovery-key retrieval before enabling or changing encryption. Follow the Microsoft instructions for your device and edition.
Limits: Full BitLocker management is not in every Windows edition; Device Encryption depends on hardware and configuration. Intune management is separately licensed. Disk encryption does not prevent an authorized signed-in user from copying files.
Your information: Recovery material may be backed up to an account or directory according to setup. Confirm the approved location and access; never put keys in the worksheet.
Official instructions: Windows BitLocker and Device Encryption ↗Download a working template
Open the Excel or Word file using your existing Microsoft Office license. Replace fictional entries, fill in the blanks and save your own copy. These manual worksheets have no macros, scoring or automatic verification.
- Encryption and recovery-access review (Excel (.xlsx)) ↓
Track actual encryption state and whether authorized staff can retrieve recovery material. Record a protected location reference, never a recovery key.
Fictional worksheet preview: Encryption and recovery-access review Asset or service reference Actual encryption state Authorized recovery access checked EXAMPLE-LAPTOP-01 Not verified Not tested Three columns shown. The full worksheet also records device capability, recovery storage references and follow-up. Never enter a recovery key in the worksheet.
Fictional worked example
Use these invented entries as a guide when filling in your worksheet. They are not a customer story or lab result. Record what you observe in your own checks.
A team checks a business laptop before an employee takes it off-site.
Use the Encryption and recovery-access review template.
What to enter before testing
- Asset or service reference
- EXAMPLE-LAPTOP-03
- Actual encryption state
- Not verified
- Recovery storage reference - NEVER KEY
- Restricted location reference only
- Authorized recovery access checked
- Not tested
How to verify
With permission, inspect actual encryption status and protection state, confirm edition and capability, and check that authorized staff can retrieve the matching recovery material securely. Confirm backup prerequisites before changing settings. Do not place the recovery key in the worksheet.
If the result is unexpected
If protection is suspended, encryption incomplete or recovery access unavailable, record the gap and involve the device owner before rollout. Do not force a recovery lockout to test access. Disk encryption alone does not verify encryption for email, network traffic or cloud services.
Keep completed worksheets private. Leave out passwords, recovery keys and confidential messages. This site does not receive your edits, but a cloud editor or synced folder may send them to its provider.
Sources and review approach
These guides use selected NIST CSF 2.0 alignments. They are not official crosswalks or complete framework implementations. We have not tested these steps in your environment.
- NIST CSF 2.0: PR.DS-01, PR.DS-02: encryption contributes to, but does not fully satisfy, data protection
- https://www.nist.gov/publications/nist-cybersecurity-framework-csf-20 ↗
- https://www.nist.gov/itl/smallbusinesscyber/guidance-topic ↗