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
Describe the bug
The following rules are referencing an incorrect registry key. They should be updating
HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0
However they instead reference
HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 3.0
The incorrect text is rooted in
source\StigData\Archive\SQL Server\U_MS_SQL_Server_2016_Instance_STIG_V1R7_Manual-xccdf.log
source\StigData\Archive\SQL Server\U_MS_SQL_Server_2016_Instance_STIG_V1R8_Manual-xccdf.log
The incorrect key is found in all versions of the SqlServer-2016-Instance xml files for rules:
V-97521.d
V-97521.h
V-97521.l
V-97521.p
To Reproduce
Create a basic configuration containing a SqlServer resource with the SqlRole = "Instance".
Expected behavior
All references of "TLS 3.0" should be "SSL 3.0".
The text was updated successfully, but these errors were encountered:
General-Fault
changed the title
Incorrect key for TLS 1.2 rules in SqlServer-2016-Instance.*.xml
Incorrect key for SSL 3.0 rules in SqlServer-2016-Instance.*.xml
Jul 10, 2020
Describe the bug
The following rules are referencing an incorrect registry key. They should be updating
HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0
However they instead reference
HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 3.0
The incorrect text is rooted in
source\StigData\Archive\SQL Server\U_MS_SQL_Server_2016_Instance_STIG_V1R7_Manual-xccdf.log
source\StigData\Archive\SQL Server\U_MS_SQL_Server_2016_Instance_STIG_V1R8_Manual-xccdf.log
The incorrect key is found in all versions of the SqlServer-2016-Instance xml files for rules:
V-97521.d
V-97521.h
V-97521.l
V-97521.p
To Reproduce
Expected behavior
All references of "TLS 3.0" should be "SSL 3.0".
The text was updated successfully, but these errors were encountered: