Skip to content

Add supplement to FIPS compliance page for documenting known confounding patterns #41565

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

Open
leecow opened this issue Jun 26, 2024 · 2 comments
Labels
discussion Indicates issues that are being discussed dotnet/svc security-practices/subsvc

Comments

@leecow
Copy link
Member

leecow commented Jun 26, 2024

Describe the issue or suggestion

FIPS compliance - .NET Core - .NET | Microsoft Learn describes in general terms how an application can be in FIPS compliance. However, dotnet/runtime#94979 introduces a scenario that could introduce confusion. It might make sense to track such patterns either as an added section to the above doc, or in a supplement.

Opening this issue to discuss and track.

cc @omajid @adegeo

@dotnet-bot dotnet-bot added ⌚ Not Triaged Not triaged labels Jun 26, 2024
@adegeo adegeo added discussion Indicates issues that are being discussed doc-idea dotnet/svc security-practices/subsvc labels Jun 26, 2024
@dotnet-bot dotnet-bot removed the ⌚ Not Triaged Not triaged label Jun 26, 2024
@adegeo
Copy link
Contributor

adegeo commented Jun 26, 2024

@Rick-Anderson is the author of that original article. Is this an area you own?

@Rick-Anderson
Copy link
Contributor

Rick-Anderson commented Jun 26, 2024

@Rick-Anderson is the author of that original article. Is this an area you own?

No, I don't own that area.

I'll do a PR to change author. I originally edited the content and 5 years ago we used to put the editor as the owner.

Unless I get a better suggestion, I'll make @leecow the new owner. I'd be happy to review the PR and suggest edit changes.

I don't remember the PU member who wrote the draft that I edited over 5 years ago.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion Indicates issues that are being discussed dotnet/svc security-practices/subsvc
Projects
None yet
Development

No branches or pull requests

5 participants