808bits

BitLocker Dump Filter

FIPS 140-2 certificate #4688 · Microsoft Corporation · data as of 2026-08-28
Active. Sunset date 2026-09-21, 23 days away. This is the FIPS 140-2 sunset: after it, agencies may keep the module only in existing systems.
Caveat: When operated in FIPS mode with the module Code Integrity under Cert. #4602 operating in FIPS mode or Secure Kernel Code Integrity under Cert. #4640 operating in FIPS mode

Certificate

Certificate number4688
StandardFIPS 140-2
Statusactive
Sunset date2026-09-21
Overall level1
Module typeSoftware-Hybrid
EmbodimentMulti-Chip Stand Alone
VendorMicrosoft Corporation · website
Software versions10.0.17763.10021 and 10.0.17763.10127
Hardware versionsIntel Xeon Silver 4114, Intel Xeon Gold 6230, Intel Xeon Platinum 8260 and Intel Xeon D-1559

Module description

The BitLocker® Dump Filter (dumpfve.sys) is the full volume encryption filter that resides in the system dump stack. Whenever the dump stack is called (in the event of a system crash), this filter ensures that all data is encrypted before it gets written to the disk as a dump file.

Security level exceptions

  • Design Assurance: Level 2

Approved algorithms

AlgorithmCAVP certificate
AESC1577, C1583, C2044, C2049
RSAC1577, C2044
SHSC1577, C2044

Tested configurations

  • Windows Server 2019 Datacenter Core (x64) running on a Dell PowerEdge R640 Server with an Intel Xeon Gold 6230 with PAA
  • Windows Server 2019 Datacenter Core (x64) running on a Dell PowerEdge R840 Server with an Intel Xeon Platinum 8260 with PAA
  • Windows Server 2019 Datacenter Core (x64) running on a Dell XR2 with an Intel Xeon Silver 4114 with PAA
  • Windows Server 2019 Datacenter Core (x64) running on a Rugged Mobile Appliance with an Intel Xeon D-1559 with PAA (single-user mode)

Validation history

DateTypeLab
2024-04-03InitialLeidos Accredited Testing & Evaluation (AT&E) Lab

Status timeline

As observed by this tracker's snapshots. NIST publishes no dates for list moves; observation began 2026-08-21, so earlier changes carry no date.

  • 2026-08-21: first observed by this tracker, status active
  • Validation dates on record: 2024-04-03

Source documents