feat: update default fibs policy #5265
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
johubertj
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of changes:
This PR updates the default FIPS behavior in s2n-tls.
Removed support for CBC-mode cipher suites from the default FIPS configuration. CBC is no longer recommended for FIPS compliance and is replaced with more modern AEAD cipher suites.
Added TLS 1.3 support to the default FIPS configuration, enabling FIPS-compliant TLS 1.3 cipher suites by default.
Created a new security policy to represent the updated FIPS defaults, since modifying an existing policy would cause backwards compatibility issues for users relying on the old behavior.
Updated default FIPS behavior to reference the new security policy.
Call-outs:
Note: Communicating with the four internal teams that currently use the default FIPS security policy about the upcoming changes.
Tracking communication status here: P222270578
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.