Solved

Windows Small Business standard server needs to disable SSL2 and SSL3

Posted on 2014-12-30
8
325 Views
Last Modified: 2015-01-21
Hello I have a server that is up and running but it has fail a world pay scan for our credit card, it states that we have to disable SSL2 and SSL3 I have look around on the net but only seeing registry fixes and I am a bit nervous to just do it, do you know any other ways to disable this two connections
0
Comment
Question by:Deerek11
  • 3
  • 3
  • 2
8 Comments
 
LVL 7

Accepted Solution

by:
Deadman earned 250 total points
ID: 40524021
There is no other way to do it. It's a vulnerability in the protocol.

In Windows Server 2003 to 2012 R2 the SSL / TLS protocols are controlled by flags in the registry set at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\Schannel\Protocols.

To disable SSLv3, which the POODLE vulnerability is concerned with, create a subkey at the above location (if it's not already present) named SSL 3.0 and, under that, a subkey named Server (if it's not already present). At this location (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\Schannel\Protocols\SSL 3.0\Server) create a DWORD value named Enabled and leave it set at 0.

Disabling SSL 2.0, which you should also be doing, is done the same way, except that you'll be using a key named SSL 2.0 in the above registry path.

check this link

http://support.microsoft.com/kb/245030
0
 

Author Comment

by:Deerek11
ID: 40524045
I just did SSL2 but under protocols there is only SSL2 no SSL3 folder ...
0
 
LVL 4

Assisted Solution

by:Damien Kay
Damien Kay earned 250 total points
ID: 40524052
I went through this with several SBS2003, SBS2008, and SBS2011 servers, as well as both a WSE2012 server and a WSE2012R2 server.  I combined all the Microsoft suggested Registry entries into one REG file, and merged it into the Registry on the server, and then rebooted. I've attached a text file that you can rename to a .REG file for merging.

I used the SSL Labs website to test my changes (I would run the test before and after merging the REG file):
  https://www.ssllabs.com/ssltest/ (using the external FQDN of the server).  

Older 2003 servers will never get a better grade than a C.  SBS2008 servers should be able to get a B, as they don't support TLS 1.2.

I have not attempted disabling the RC4 cipher yet, so my SBS2011 and WSE2012 servers are also capped at a B. This MS Technet Article describes how to completely disable RC4:
    http://support.microsoft.com/kb/2868725
Disable-SSL-Protocols.txt
0
Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

 
LVL 7

Assisted Solution

by:Deadman
Deadman earned 250 total points
ID: 40524066
To disable SSLv3  create SSL 3.0  a subkey at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\Schannel\Protocols and again create Server subkey
2880599.png
create a DWORD value named Enabled and leave it set at 0.
0
 

Author Comment

by:Deerek11
ID: 40524133
Hello I just tried to run the scan for the network using https://www.ssllabs.com/ssltest/ but it will not allow IP address ... any suggestions?
0
 
LVL 4

Expert Comment

by:Damien Kay
ID: 40524195
Do you have access to your domain DNS?  Since you have SSL Enabled, you have an SSL Certificate installed, so you must have a domain name associated with that in some way...
0
 

Author Comment

by:Deerek11
ID: 40524279
Yes the domain name is with go daddy but world pay had us run it on that domain name at first and it failed with about 30 something critical errors they told me that was wrong I should run it within the network IP address so I did a what is my ip inside the network so we ran the scan on the IP address of the network
0
 
LVL 4

Assisted Solution

by:Damien Kay
Damien Kay earned 250 total points
ID: 40524531
That is correct, an IP Address will not work.

First, for the SSL Certificate to work right, you must have a FQDN to browse to it.  That FQDN must resolve to the external IP Address of the server you are trying to secure.  It is that name that you must use in the SSLLABS test.  

A typical example of a FQDN for remote access to a WSE2012R2 server would be "https://remote.domain.com"

If you have some other configuration, please let me know so I can help you further...
0

Featured Post

Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
A procedure for exporting installed hotfix details of remote computers using powershell
In this Micro Tutorial viewers will learn how they can get their files copied out from their unbootable system without need to use recovery services. As an example non-bootable Windows 2012R2 installation is used which has boot problems.
In this Micro Tutorial viewers will learn how to restore single file or folder from Bare Metal backup image of their system. Tutorial shows how to restore files and folders from system backup. Often it is not needed to restore entire system when onl…

860 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question