You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We developed WinUI3 application based on Edge WebView2. We are required that the application should be FIPS compliance. So could anyone confirm:
Does Microsoft Edge use FIPS 140-2 validated cryptography? Is it still using non FIPS validated Chromium built-in cryptographic modules (BoringSSL) or are the latest versions using FIPS validated cryptography?
If not FIPS validated cryptography used, have we way to replace the library by other FIPS validated library to inject to Edge or Edge WebView2? or any other methods we can ensure Edge WebView2 FIPS compliance, then our application can be FIPS compliance?
The text was updated successfully, but these errors were encountered:
We developed WinUI3 application based on Edge WebView2. We are required that the application should be FIPS compliance. So could anyone confirm:
Does Microsoft Edge use FIPS 140-2 validated cryptography? Is it still using non FIPS validated Chromium built-in cryptographic modules (BoringSSL) or are the latest versions using FIPS validated cryptography?
If not FIPS validated cryptography used, have we way to replace the library by other FIPS validated library to inject to Edge or Edge WebView2? or any other methods we can ensure Edge WebView2 FIPS compliance, then our application can be FIPS compliance?
The text was updated successfully, but these errors were encountered: