SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Preventing Unauthorized Admin Access


Preventing Unauthorized Admin Access

Author
Message
JonR76
JonR76
SSC Rookie
SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)

Group: General Forum Members
Points: 29 Visits: 257
I am wondering what other people are doing to keep people with admin access to servers out of the management tools on their SQL servers. People in our server unit that have admin access to any server are logging on to the SQL Server database server, and immediately think that they are SQL Server DBAs. I had one guy last week running a query in SSMS that selected and sorted so much data that the TempDB grew until it filled the drive it was on.

How do other organizations control this?
Luke L
Luke L
SSCarpal Tunnel
SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)

Group: General Forum Members
Points: 4090 Visits: 6128
I've seen this handled 2 ways.

1) remove the built in admin account rights from SQL. This can be done and if you google or search this site you'll find a variety of ways to accomplish it as well as numerous caveats on things to expect.

2) It's a management problem and a matter of trust. Audit the heck out of your databases and when unauthorized individuals do things like that they lose their jobs, take a couple of days off without pay or some other such punishment like you being allowed to personally smack them upside the head with the office tool of your choice. I prefer an old CRT we have here, it's heavy enough to really make them think and the cord is strong enough I can whirl it around a few times before connecting.

-Luke.

To help us help you read this

For better help with performance problems please read this
Erik Bitemo
Erik Bitemo
SSC Veteran
SSC Veteran (202 reputation)SSC Veteran (202 reputation)SSC Veteran (202 reputation)SSC Veteran (202 reputation)SSC Veteran (202 reputation)SSC Veteran (202 reputation)SSC Veteran (202 reputation)SSC Veteran (202 reputation)

Group: General Forum Members
Points: 202 Visits: 173
Luke's suggestions are pretty straightforward Smile I handle this kind of issues in the following way: all login attempts are logged into the server errorlog and I get a filtered extract every morning. When I see someone outstanding logged in to the servers, I write the ma mail stating that I saw them logging in (or trying to log inn) and I wonder if I can help them in anything stored on that server as apparently, he's not a DBA of that instance, so might not be familiar with the structure.

I write it in a very polite form, but if someone reads between the lines, it rather sounds like 'I got you, what the heck are you doing on my server?'

-- Erik http://blog.rollback.hu
Roy Ernest
Roy Ernest
Hall of Fame
Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)

Group: General Forum Members
Points: 3826 Visits: 6869
Here we have set up a rule that if anyone else other than a DBA wants to login to the server (Not just DB) they have to notify us why they want to log on. They are absolutely not allowed to log on to the SQL Server instance... :-)

-Roy
Charley Hanania-669272
Charley Hanania-669272
Forum Newbie
Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)

Group: General Forum Members
Points: 4 Visits: 25
Hi jrasmussen,

Generally the way to control access to SQL Server be it from Admins or otherwise is through adding and removing accounts from the Security Roles.

The General Rule of thumb is to:
- Create an AD Domain Group for DBA's,
- Add the DBA's to it
- Add the Group to SQL Server
- Grant the appropriate Privileges to it (eg. sysadmin SQL Server-level role)
- and then locate the local admins group and remove the excess roles and privileges from it.

This assumes that you've correctly set up the service accounts (see: "Setting Up Windows Service Accounts" in SQL Server Books Online) and ensured that your applications are not configured to use admin accounts etc as well.

Connecting through Windows Authentication is generally the tried and trusted method of authenticating to SQL Server as well. its another thing to look into in case there's an SA account lying about that hasn't been secured and can act as a back door into your SQL Server.

Hope it helps,

Charley Hanania.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search