Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FIPS Compliance #3684

Closed
headsea opened this issue Aug 3, 2023 · 0 comments
Closed

FIPS Compliance #3684

headsea opened this issue Aug 3, 2023 · 0 comments
Assignees

Comments

@headsea
Copy link

headsea commented Aug 3, 2023

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?

@novac42 novac42 assigned LiangTheDev and aluhrs13 and unassigned LiangTheDev Aug 7, 2023
@MicrosoftEdge MicrosoftEdge locked and limited conversation to collaborators Oct 10, 2023
@victorhuangwq victorhuangwq converted this issue into discussion #4054 Oct 10, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants