An unsecured SQL Server is like an open invitation to Internet hackers: They may exploit weaknesses in the operating system running SQL Server, take control of SQL Server services or simply access pieces of data that were intended to be inaccessible. Whatever the technique,
Requires Free Membership to View
your data will ultimately be compromised. Here you will learn how to lock down SQL Server from the get-go and prevent attacks before any damage is done. You'll also get a technical overview of new security enhancements in SQL Server 2005, set to launch in November. When you're done, please take a moment to vote in our poll on SQL Server security and e-mail us to let us know what other guides you'd like to see on SearchSQLServer.com.
| Installing and Configuring SQL Servers | Return to Table of Contents |
- Webcast: SQL Server Security School: Securing SQL Servers using Group Policy
- White paper: Microsoft SQL Server 2000 security
- White paper: Microsoft SQL Server 2000 SP3 security features and best practices
- White paper: An enterprise-class plan for securing Microsoft SQL Server databases
- Tip: Netlibs: Why is less more (secure)
- Expert advice: Resource for hardening SQL Server 2000
- Step-by-Step Guide: Ensuring data integrity in SQL Server
| Hardening access to SQL Servers | Return to Table of Contents |
- Webcast: SQL Server Security School: Minimizing SQL Server service, login and user accounts
- Tip: How SQL Server is hacked
- Tip: User rights and privileges
- Tip: Accessing, manipulating and backing up data
- Tip: Top four ways to secure SQL Server
- Checklist: SQL Server user security
- Expert advice: Secure way to share access to SQL Server running multiple databases
- Expert advice: Secure data from the DBA
- Expert advice: Permanently prevent Query Analyzer from accessing a particular database
| Encrypting SQL Server data | Return to Table of Contents |
- Tip: Encrypting data in SQL Server: Dos and don'ts
- Tip: How to improve SQL Server security
- Tip: jTDS: Open-source JDBC 3.0 middleware driver for SQL Server
- Expert advice: Permanently prevent Query Analyzer from accessing a particular database
- Expert advice: Hiding the source for a stored procedure
- Expert advice: Encrypting password fields
| Finding and patching SQL Servers | Return to Table of Contents |
- Webcast: SQL Server Security School: SQL Server discovery challenges and solutions
- Tip: How to improve SQL Server security
- Step-by-Step Guide: How to patch SQL Server, part 1
- Step-by-Step Guide: How to patch SQL Server, part 2
| Security enhancements in SQL Server 2005 | Return to Table of Contents |
- Article: Security is a catch word for SQL Server's sequel
- Book excerpt: New security features in SQL Server 2005
- Book excerpt: Optional features are turned off by default
- Book excerpt: A quick review of SQL Server security concepts with enhancements
- Book excerpt: SQL Server password policies and credentials
- Book excerpt: Separation of users and schemas
- Book excerpt: Specifying execution context for procedural code
- Book excerpt: SQL Server permissions and new objects
- Book excerpt: Assembly permissions -- Who can catalog and use an assembly?
- Book excerpt: Permissions, visibility, UDTs and user-defined aggregates
- Book excerpt: What can .NET code do from within SQL Server: Safety levels
- Poll: Which new SQL Server 2005 security enhancement is most significant?
VISIT OUR LEARNING GUIDE ON SQL SERVER BASICS...
This was first published in July 2005
There are Comments. Add yours.