Windows 10: FIPS 140-3 Compliance in Windows 11 Pro with BitLocker XTS-AES-256

StartFragmentHello, I would like to know if Windows 11 Pro currently supports or includes any cryptographic modules that are validated under FIPS 140-3. Our organization uses BitLocker with XTS-AES-256 encryption, and we are evaluating systems for compliance with the FIPS 140-3 standard. Specifically, I’d appreciate clarification on: Whether Windows 11 Pro has cryptographic modules that are officially FIPS 140-3 validated.If not, is there a roadmap or estimated timeline for such validation?Are there any current Microsoft products or configurations that meet FIPS 140-3 requirements? Any guidanc

:)

 

Windows FIPS -140-2 & 140-3 Compliance

I notice information on Windows FIPS compliance is located here: Federal Information Processing Standard (FIPS) 140 Validation - Windows security | Microsoft Learn to include information regarding NIST certificates. Every certificate listed is marked "Historical", meaning they are no longer active certificates. Many of them were pushed to this state due to SP 500-56rev3.

Does Microsoft have an approach, or timeline to getting these revalidated? Or if they've been revalidated can the page be updated to include the new Cert #s?

 

Bitlocker hardware encryption on M500 + XTS-AES 256-bit setting

I recently discovered that the november update of Windows 10 (1511) supports a new, better mode of encryption for Bitlocker, namely XTS-AES. I also discovered that you can use 256-bit instead of 128-bit encryption on both the old method of encryption, and
the new XTS-AES encryption.

I've got a single drive that supports eDrive/hardware encryption with Bitlocker-Crucial's M500. It was working before, but when I set Windows to use XTS-AES 256-bit, it can't get past the test Bitlocker screen...I punch in my password and the computer just
locks up. I have to reboot, then hit escape to get back to Windows, which tells me the attempt failed.

I'm not sure what kind of encryption the M500 uses...it's supposed to be 256-bit, but maybe turning on XTS-AES 256-bit causes this to not work?

There's a setting in Windows to just use software encryption, and maybe doing that, bypassing hardware would actually be better encryption than what the drive does?

Any thoughts on this, why this isn't working, whether I should switch to software encryption on it?

 

Microsoft brings FIPS 140 Compliance to Authenticator

Source: https://techcommunity.microsoft.com/...g/ba-p/2365671