As DBAs, security is not usually a primary concern. Connectivity and availability are more immediate concerns, but unless you want an angry visit from your security administrator, security should be added to the list. Below is a checklist that SearchSecurity.com writer Mike Chapple advises security administrators to use when locking down SQL Server; it can be taken into consideration by DBAs as well.
Here are four actions you can take today to help ensure the security of your SQL Server:
- Limit the number of database administrators. This is a common-sense rule that's often violated. Make sure that only people who need administrative powers (and know how to use them!) have DBA access. SQL Server's tight integration with Windows makes it far too easy to simply grant database administration rights to all domain administrators. This can be a grave mistake.
- Apply the rule of least privilege. Ensure that folks with administrative access (and user-level access, for that matter) have the smallest subset of privileges necessary to carry out their job functions.
- Avoid hard-coded passwords like the plague. Database developers like to hard-code passwords in their programs because it's the easy way out. Don't let them do it! Use SQL Server's Integrated Authentication mode to tie into Windows security or force users to authenticate to the database itself. If you hear the statement, "We can't change
Requires Free Membership to View
When you register, you’ll also receive targeted emails from my team of award-winning editorial writers. Our goal is to keep you informed on the hottest topics and biggest challenges faced by today's SQL Server database pros.
Hannah Smalltree, Editorial Director
- the password or XYZ will break," consider it a big red flag waving in your face!
- Make use of roles. SQL Server offers a number of predefined user roles that grant specific administrative privileges. You may also create your own customized roles for your environment-specific needs. Assign permissions on your database to these roles, and then add and remove users/groups from these roles as their job responsibilities change. This makes for a much tidier security environment and allows you to keep tabs on access controls.
Mike Chapple, CISSP, currently serves as Chief Information Officer of the Brand Institute, a Miami-based marketing consultancy. He previously worked as an information security researcher for the U.S. National Security Agency. His publishing credits include the TICSA Training Guide from Que Publishing, the CISSP Study Guide from Sybex and the upcoming SANS GSEC Prep Guide from John Wiley. He's also the About.com Guide to Databases.
This was first published in March 2005