You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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-eq0xffffffff) {
to:
if ($value-eq4294967295) {
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.
The text was updated successfully, but these errors were encountered:
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.
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.
@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.
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:
to:
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.
The text was updated successfully, but these errors were encountered: