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 123»»»

Password Handling Expand / Collapse
Author
Message
Posted Thursday, May 17, 2012 10:03 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Yesterday @ 12:34 PM
Points: 31,181, Visits: 15,626
Comments posted to this topic are about the item Password Handling






Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1302267
Posted Friday, May 18, 2012 6:43 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Tuesday, November 19, 2013 7:51 AM
Points: 43, Visits: 218
Generally, I do my best to never let a SQL login have any sort of elevated privs on a database let alone the server. We still have one program (Microsoft Dynamics GP, can I get a security nightmare amen anyone?) that require administrators to use [sa] for some tasks. This absolutely kills me, but it is what it is.

Anyway, I will typically "randomly" generate a 15 to 20 character password. I will then use various forms of communication (email, im, text) to relay the password to the user who needs it. I never send the server/username/password in the same correspondence or using the same method.

This is not fool proof, but the best I could come up with so far. Looking forward to hearing how others handle this as well.
Post #1302458
Posted Friday, May 18, 2012 7:00 AM


SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Tuesday, September 30, 2014 6:46 AM
Points: 77, Visits: 436
Nice editorial.
For the end users, that are allowed direct access to a sql server, domain accounts are required. They are granted access thru AD groups, so their account does not exist on the sql server.
For our applications we use service accounts, both domain and sql. All of our service accounts are stored in KeyPass2 (http://keepass.info/). The system admins and dba share one safe and the developers share a separate one. KeyPass2 has a password generator built in.

When I create the accounts, the password is a minimum of 20 characters long. The person that needs the account is sent an email with the username, sql server, database and which safe the password is in. Then they look it up in the safe.

So far it works for us.


Bill Soranno
MCP, MCTS, MCITP DBA
Database Administrator
Winona State University
Maxwell 143

"Quality, like Success, is a Journey, not a Destination" - William Soranno '92
Post #1302482
Posted Friday, May 18, 2012 7:51 AM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Tuesday, February 25, 2014 2:26 PM
Points: 386, Visits: 626
Nice editorial Steve! The last 2 places that I have worked with large production systems, internal company accounts were all Windows AD accounts.

The lone exception, 3rd party vendors software. whenever they came in house and asked for SA access we could normally get the Software Engineers on the phone and get the settings lowered, example if it needed the ability to truncate or drop and create structures, that is just DDL_Admin on the database in question, not SA for the entire server.

For password's there have been different requirements. I've worked in places where the DBA's would create the account and issue the password, I would use Keypass http://keepass.info/ to randomly generate a complex password and store it.

I've worked in others where the DBA's would request an account, and we would be issued a password from a password management group. and if a SQL Authentication account was required we would get the password from this department, and then create the account and assign permissions.


Twitter: @SQLBalls
Blog: http://www.SQLBalls.com
Post #1302536
Posted Friday, May 18, 2012 8:04 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Tuesday, September 16, 2014 2:03 PM
Points: 1,334, Visits: 3,069
I also use KeePass2. It generates very strong passwords for me and I can safely store them in KeePass as well and I always have them in case someone forgets, and it is free to boot! The password length defaults to 20 but you can change that as well. In my experience 20 characters is just too much for most people, so I lower it to 8-10.You can also set up folders so you can keep your Production, QA, and Development environments separated. Nice!

http://keepass.info/download.html


"Technology is a weird thing. It brings you great gifts with one hand, and it stabs you in the back with the other. ..."
Post #1302547
Posted Friday, May 18, 2012 8:15 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: 2 days ago @ 10:28 AM
Points: 321, Visits: 1,496
In my last position as DBA, I used PasswordSafe to generate / store complex passwords. In the "Notes" section I would also include who requested it, when, and what server / database / application it was for. Access to the safe was limited to about 5 folks total (myself and a few other trusted folks / system admins).

The username / password was then emailed to the requestor in a PGP encrypted email.
Post #1302552
Posted Friday, May 18, 2012 8:15 AM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Tuesday, February 25, 2014 2:26 PM
Points: 386, Visits: 626
Hmmm between Bill, Travis, and myself I'm sensing a trend Keypass is indeed a wonderful thing.

Twitter: @SQLBalls
Blog: http://www.SQLBalls.com
Post #1302554
Posted Friday, May 18, 2012 8:45 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Friday, April 18, 2014 2:47 PM
Points: 424, Visits: 193
Where I work, we require that a SQL login be created by the DBAs. We require that the password be 10 characters long and have 2 symbols, 2 upper case, 2 lower case and 2 numbers. We then must hand deliver the password and username to the developers if they are in our building or drive it to them if they are nearby, when that fails by phone is acceptable. We also store our passwords in Password Safe.

All in all, this has worked well for us. Only problem is it leaves a physical copy of the password in the hands of the developer which may not be best.
Post #1302576
Posted Friday, May 18, 2012 9:06 AM
SSC-Enthusiastic

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

Group: General Forum Members
Last Login: Wednesday, October 15, 2014 8:57 AM
Points: 137, Visits: 452
My Scenario- mid sized managed hosting company, Sql Server used as datastore for CMS

When DB websites are created, they are done via a web interface by a WebDBA (generally myself).
The passwords used are random 12 character minimum.
The Sql Server is not accessible via the internet
I email a link to the developer needing the site where they can retrieve connection string. The webpage containing this uses Windows AD for authentication, and it too is not visible on the internet.



Director of Transmogrification Services
Post #1302605
Posted Friday, May 18, 2012 10:15 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Yesterday @ 12:34 PM
Points: 31,181, Visits: 15,626
baxterr (5/18/2012)
Generally, I do my best to never let a SQL login have any sort of elevated privs on a database let alone the server. We still have one program (Microsoft Dynamics GP, can I get a security nightmare amen anyone?) that require administrators to use [sa] for some tasks. This absolutely kills me, but it is what it is.


I dealt with GP years ago. Through some SQL traces and calls with GP support, we determined that the app needs sa for new logins and potentially new databases. However if those are setup by a DBA, the app picks them up. We removed sysadmin from the app logins and they would call us when they needed a new login added.







Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1302660
« Prev Topic | Next Topic »

Add to briefcase 123»»»

Permissions Expand / Collapse