Skip to content
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

Move away from static Cipher Suite order check towards checking for usage of strong ciphers #589

Open
TuemmlerKelch opened this issue May 14, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request patch Includes bug fixes, focusing on enhancing stability.
Milestone

Comments

@TuemmlerKelch
Copy link
Collaborator

Description

As cipher suite order is highly individual, it is more important to make sure there are no weak or insecure ciphers configured.
This affects both SBD-072 and Risk Score Setting 4.1

What are the benefits?

Fair assessment

Acceptance Criteria!

A cipher suite order following all of the necessary criteria (Correct registry path and type) AND not containing weak or insecure ciphers will be considered passed

Linked Issues?

No response

Additional Information!

No response

@TuemmlerKelch TuemmlerKelch added the enhancement New feature or request label May 14, 2024
@TuemmlerKelch TuemmlerKelch added this to the 5.10 milestone May 14, 2024
@TuemmlerKelch TuemmlerKelch added the patch Includes bug fixes, focusing on enhancing stability. label May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request patch Includes bug fixes, focusing on enhancing stability.
Projects
None yet
Development

No branches or pull requests

2 participants