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

Microsoft IIS10.ps1 - Ensure AES 256/256 Cipher Suite is enabled - Line 2487 #549

Open
CanMonster opened this issue Apr 11, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@CanMonster
Copy link

CanMonster commented Apr 11, 2024

The Microsoft IIS 10.0 test '"AES 256/256 Cipher is disabled"' always fails even though the registry value is correct ...

Line 2487 of the 'Microsoft IIS10.ps1' report file needs to be updated from:

if ($value -eq 0xffffffff) {

to:

if ($value -eq 4294967295) {

The Get-ItemProperty CmdLet will always read in the decimal value so updating the condition to evaluate the decimal value is easier than converting it to hexadecimal.

@TuemmlerKelch
Copy link
Collaborator

Hi @CanMonster,

thanks for the issue.

I suppose you were using ATAP 5.8.0. With 5.9.0 we actually updated the check to look for '1'.
This is because MS have updated all their documentation to not use 0xffffffff / 4294967295 anymore.

So if you configured 4294967295, the check will still fail and link you to the corresponding learn page:
https://learn.microsoft.com/en-us/windows-server/security/tls/tls-registry-settings?tabs=diffie-hellman#tls-dtls-and-ssl-protocol-version-settings

I will discuss, if we change this from False to Warn with our next iteration.

@TuemmlerKelch TuemmlerKelch added the enhancement New feature or request label Apr 15, 2024
@CanMonster
Copy link
Author

Hi @TuemmlerKelch,

Thanks for the update and I agree with the value being 1. I have just downloaded 5.9.0 and can confirm that the value '0xffffffff' is still present in the 'Microsoft IIS10.ps1' report file. Not sure if this is supposed to be the case ATM or if the change is slated for a future update.

@TuemmlerKelch
Copy link
Collaborator

@CanMonster Hey Nathan,
hang on. We will update IIS report to CIS 1.2.1 [#558] and solve this.
I will update this post as soon as we have a working branch, so you can test this before our next release, if you wish.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants