Adding new level of security between guest OS and Sql Server management tools.

  • Hi all,

    Our client has asked us a good question:

    We need to add security to our sql server management tools in our cliente servers. All of them share the same password for the user 'sa'. Also, all the applications in production use 'sa' in their connection strings. The password of 'sa' user is almost public (everybody knows it).

    The cliente asked us a way to use a new level of security for our management tools so nobody can log on the sql server and backup any data... WITHOUT changing SA password.

    We can´t also use OS users security, cause the servers must have public access. We are looking for some sort of application that works between SO and Sql Server management tools.

    That kind of application/software exists?... Someone has any idea of what can we do?.

    Thanks in advance,

    Regards,

  • Are you saying that SQL Server management tool is accessible by Public? That is scary. If I am wrong, please correct me.

    You could just set up a SQL Server Job to take back up and do other maintenance. Please give more detail so that we could give you better advice.

    -Roy

  • Really scary. Server has public access. The 'sa' user is also known. (We have about 400 servers of our client in this situation).

    Each server has a few applications that uses in their connection string the 'sa' login to access to the data.

    Our scenario objetive is:

    - Server must still be "public" (Cause the real owner of the server is NOT the client....). We can NOT remove administrator priviliges to the "public" user.

    - Sql Server user must be only used by us, but WITHOUT changing the 'sa ' password, so we do not have to change 400 applications web.config. 🙂

    So, we are loooking for some kind of product/software that can be placed between OS and Sql Server Management Studio so nobody with administrator privileges can open any SQL Tools, without knowing a new special password.

    Any idea?.

    thanks in advance!

  • As long as the SA user name and password is out there, your security is shot into tiny pieces what ever application you put. You could try putting a firewall that has some complicated rules in it. Make sure that you have only Port 1433 open. 1434 UDP port is used for adminsitrative connection between the SSMS and the SQL Server.

    Maybe you could put some login triggers that refuses connection based on the application name and the host name.

    Keep in mind that they could do almost everything using POWER SHELL if they the SA username and password. This is going to be a real tough challenge for you.

    -Roy

  • Tell them to quit moaning about all the work and schedule the time to fix the 400 web.config files.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply