Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQL Server Security Part 1


SQL Server Security Part 1

Author
Message
Philip Kelley
Philip Kelley
Say Hey Kid
Say Hey Kid (681 reputation)Say Hey Kid (681 reputation)Say Hey Kid (681 reputation)Say Hey Kid (681 reputation)Say Hey Kid (681 reputation)Say Hey Kid (681 reputation)Say Hey Kid (681 reputation)Say Hey Kid (681 reputation)

Group: General Forum Members
Points: 681 Visits: 232

I'm looking into the restriction of access rights (via "guest" and "public") in the master database, and have a question. In the list of procedures to remove access to, you list "xp_perfmonitor". What is this procedure? What does it do? And why can't I find it in the master database, the Microsoft web site, or anywhere on Google that doesn't show the exact same list?

Oh.

I (mostly) figured it out while writing the question, but will still post it for potential discussion purposes.

Philip





Philip Kelley
Philip Kelley
Say Hey Kid
Say Hey Kid (681 reputation)Say Hey Kid (681 reputation)Say Hey Kid (681 reputation)Say Hey Kid (681 reputation)Say Hey Kid (681 reputation)Say Hey Kid (681 reputation)Say Hey Kid (681 reputation)Say Hey Kid (681 reputation)

Group: General Forum Members
Points: 681 Visits: 232

And that goes double for xp_schedulersignal!

Philip





Tatsu
Tatsu
Old Hand
Old Hand (302 reputation)Old Hand (302 reputation)Old Hand (302 reputation)Old Hand (302 reputation)Old Hand (302 reputation)Old Hand (302 reputation)Old Hand (302 reputation)Old Hand (302 reputation)

Group: General Forum Members
Points: 302 Visits: 307

I don't think the account you log into the machine under for the installation of SQL Server has anything to do with the account that the service(s) run under afterwards. If you create domain accounts for the SQL Server services and specify those during installation, those are the accounts the services are configured to use, not the account you're logged in as. Also, when you specify those accounts, SQL Server sets up the minimum necessary permissions for the accounts so you don't need to go through the trouble of doing it manually. Also, if you change the service account later through Enterprise Manager, it sets up the appropriate permissions though it probably does not remove them from the other account.

Also, file-system encryption does put a hit on performance. Putting database files in an encrypted location is not recommended unless the sensitivity of the data warrants the performance hit and, even then, there are probably better options such as third-party solutions. Encrypting backups is not bad idea but using file-level encryption is. NTFS encryption is too heavily dependant on the keys for the service accounts. If you want to encrypt your backups, go ahead and fork out some extra dough for LightSpeed for SQL Server (http://www.imceda.com) or something similar. It will perform better and has the added bonus of providing encryption and compression simulataneously which NTFS does not permit.



Bryant E. Byrd, BSSE MCDBA MCAD
Business Intelligence Administrator
MSBI Administration Blog
Greg Larsen
Greg Larsen
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1051 Visits: 290

Under the section labeled "The SA Account" you have the following statement regarding the "sysadmin" role, "Never grant this privilege to any other user, there is simply no reason to in a production environment.> " I wonder if this holds true regardless of the environment and number of DBA's. >

>In our environment we have three DBA's that share responsibility for mananging our production SQL Server environment. We all know the SA password, and could use it to perform production work if we chose to go that route. But instead each DBA has a SQL Server Logon for performing sysadmin duties. We have done this for audit trail purposes. Doing this allows us to identify which DBA has done what. If we shared the SA account we won't be able to determine which DBA has made a particular change. >



Gregory A. Larsen, MVP
Markus
Markus
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1587 Visits: 3679

We have quite a few software packages running on SQL Server here. It is amazing when a tech. person comes to install their app. and they either create or already have an extremely simple ID with a matching password or one letter password. AND or use 'sa' or grant 'sa' rights to a new ID..... When I question this and or say I want a different password assigned to the ID they look at me like I have two heads....

Personally, I believe Microsoft needs to really change the thinking about security in SQL Server as with it being so open today small companies do this type of stuff and some of this poor security we are stuck with due to the design of the application. I know some of this has been addressed in SS2005 but I am not sure how much nor to what degree either.





Liliya Huff
Liliya Huff
SSC Journeyman
SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)

Group: General Forum Members
Points: 85 Visits: 63

sa is a tabu for remote connections (password goes as open text if there is no forced network encryption). a dba has to have a good reason to make me think they need sa to login.

another exeption for a user to be in master is sql service account (when buildin/administrators is removed). this accoun doesn't need to be windows administrator, syadmin has to be granted to it. in my case service account sit in master in addition to sa.


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