A growing consciousness of security has brought Microsoft SQL Server database security into focus as never before. Planning for database security should begin early in the development process and there are important vulnerabilities that you need to prevent in your application's SQL Server.
by Ron Talmage
December 13, 2002
lanning for database security means a number of things. First, you need to take care that the code you send to SQL Server is not vulnerable to SQL injection. Second, you need to keep up with and apply the latest Microsoft SQL Server security updates. Third, after you take care of some of the basic SQL Server security measures, you should test your servers using the Microsoft Baseline Security Analyzer, and also pay attention to other third party utilities.
There's been an intense focus on all aspects of security in the past year, and SQL Server security is no exception. It's no longer a compartmentalized concern; security is a concern for everyone. As a SQL Server developer you should be aware of the major security vulnerabilities of SQL Server. In this article you'll learn how to address the major vulnerabilities in your code; how Microsoft is adding security patches to SQL Server, and some best practices and tools you can use to assess your SQL Server's security.
It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com. Already a member?
To become a member of DevX.com create your Member Profile by completing the form below. Membership is free!
lanning for database security means a number of things. First, you need to take care that the code you send to SQL Server is not vulnerable to SQL injection. Second, you need to keep up with and apply the latest Microsoft SQL Server security updates. Third, after you take care of some of the basic SQL Server security measures, you should test your servers using the Microsoft Baseline Security Analyzer, and also pay attention to other third party utilities.
