Hola quiero compartir con ustedes unos recursos de seguridad para Sql Server que encontré y que creo que les serán de gran utilidad, aquí el detalle:
- Common SQL Server Security Issues and Solutions: Have you found yourself inadvertently in charge of a SQL Server database and don’t know all the best practices for making it secure? Get a quick overview of the top 10 security areas you should worry about, common problems, and solutions.
- Securing SQL Server: Securing SQL Server can be viewed as a series of steps, involving four areas: the platform, authentication, objects (including data), and applications that access the system. Get detailed, step-by-step guidance on how to create and implement an effective security plan.
- SQL Server 2008 Replication Security: Get guidance to help you protect the replication scenarios that you deploy in SQL Server 2008 from malicious attacks and improve the security of your data.
- How Do I: Defend Against Truncation-Based Sql Injection Attacks?: This video demonstrates how this property of truncation may be used by an attacker to circumvent the above mentioned mitigation, resulting in a SQL injection attack. Various options for fixing SQL injection issues are also discussed.
- Microsoft Source Code Analyzer for SQL Injection: This static code analysis tool for finding SQL Injection vulnerabilities in ASP code will scan ASP source code and generate warnings related to first-order and second-order SQL Injection vulnerabilities. It will also provide annotation support that can be used to improve the analysis of the code.
- Tuning Microsoft Forefront Client Security Database Components: Microsoft Forefront Client Security uses SQL Server for collection and reporting databases. When you are choosing the SQL Server edition and the hardware on which it will run, take the topics discussed in this article into consideration.
Saludos
Fuente: http://blogs.msdn.com/mvplead/archive/2009/08/18/recursos-de-seguridad-para-sql-server.aspx
This post first appeared on Programo En .NET (Programa En Punto Net!), please read the originial post: here
