Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SCCM Security Config for SQL Servers Expand / Collapse
Author
Message
Posted Monday, June 17, 2013 3:56 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, April 15, 2014 4:02 AM
Points: 177, Visits: 789
Hi All,

I prefer my systems to work on the least privilege wherever possible but I have an account connecting for SCCM and it has been put in a AD group that has sysadmin, and that makes me unhappy. I understand that this account has to connect and the reasoning but for some reason it creates two connections to every database on my server about every 5 mins. This worries me even more as the server in question has in excess of 1600 db's on it (don't ask - an old design, which is too expensive to change) and that means it's hammering the connections + 3200 which will have an effect on the other connections and threading

Does anyone know the required permissions for a SCCM SQL service account and what perms it needs at the db level (for monitored databases not SCCM itself)?


SQL DBA
Every day is a school day, and don't trust anyone who tells you any different.
http://sqlblogness.blogspot.co.uk
Post #1464050
Posted Monday, June 17, 2013 12:19 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Wednesday, April 16, 2014 9:25 AM
Points: 7,070, Visits: 12,523
If all SCCM is doing in inspecting System Views, Catalog Views and DMOs then you may be able to go to something like this:

1. Create a Login for the SCCM service to use to login, or add the SCCM service account if that's how it authenticated to the DB instance (probably done already).
2. Create a User in every user database on the instance for that Login plus model (to support having a user in all new DBs) and leave the user in the public Database Role only, i.e. the user should not need any explicit permissions.
3. While in master grant VIEW SERVER STATE to the Login.
4. While in master grant VIEW ANY DEFINITION to the Login. The ANY is very important because it denotes a sever-level permission that permeates all databases as well, as long as the login has a user in the database.

That will offer the SCCM Login the ability to view all server-level and database-level metadata. Any permissions required to allow the SCCM login to modify server or database level settings will require additional grants.


__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato

Believe you can and you're halfway there. --Theodore Roosevelt

Everything Should Be Made as Simple as Possible, But Not Simpler --Albert Einstein

The significant problems we face cannot be solved at the same level of thinking we were at when we created them. --Albert Einstein

1 apple is not exactly 1/8 of 8 apples. Because there are no absolutely identical apples. --Giordy
Post #1464305
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse