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
Version (please complete the following information):
Current
Additional context
Having SCM set to a minimum TLS version of 1.2 ensure that data-in-transit will be encrypted using a current TLS version, which is less likely subject to attack, and also required by some regulatory requirements.
Even if by default it is set to 1.2, it's always good to have a check that ensure that if someone specified the parameter with an version not equal to 1.2, it would be flagged
The text was updated successfully, but these errors were encountered:
Describe the issue
It seems that there are no checks in order to ensure that web apps have their SCM minimum TLS version is set to 1.2
Examples
Version (please complete the following information):
Additional context
Having SCM set to a minimum TLS version of 1.2 ensure that data-in-transit will be encrypted using a current TLS version, which is less likely subject to attack, and also required by some regulatory requirements.
Even if by default it is set to 1.2, it's always good to have a check that ensure that if someone specified the parameter with an version not equal to 1.2, it would be flagged
The text was updated successfully, but these errors were encountered: