How do I secure Sql Server 2008 R2

Posted by Mark Tait on Server Fault See other posts from Server Fault or by Mark Tait
Published on 2012-04-03T11:32:31Z Indexed on 2012/04/03 23:31 UTC
Read the original article Hit count: 283

Filed under:
|
|

I have both a dedicated and a VPS (from Fasthosts) virtual server - the web sites/applications I run on these, access Sql Server stored on the same web server.

Until now, I have logged onto Sql Server on both the deidicated and VPS server, from Sql Server Management Studio - until I noticed in my server application logs, multiple attempts to logon to Sql Server using the 'sa' username, but failed password.

So someone/bot is trying hard (repeatedly every couple of hours, for approx 20 attempts during each instance) to log on... so obviously I have to lock down access to Sql Sever remotely.

What I have done is gone into Configuration Manager, and in Sql Server Network Configuration -> Protocols for Sql2008 and also in Sql Native Client 10.0 Configuration -> Client Protocols - I have diabled Named Pipes, TCP/IP (and VIA by default). I have left Shared Memory enabled. I also disabled in Sql Server Services, the Sql Server Browser.

Now the only way I can manage the databases on these servers, is by logging on to them via Remote Desktop.

Can anyone confirm if this is the correct way of stopping anyone maliciously logging on to Sql Server? (I'm not a DBA or security expert - and there are hundreds of articles advising all different ways - but I was hoping for the experts here to confirm, or otherwise, if what I've done is correct)

Thank you,

Mark

© Server Fault or respective owner

Related posts about sql

Related posts about sql-server