SQL Server Lockdown - Step by Step procedure

Do you want to lockdown your SQL Server environment?

Hope you dont'! Though it is not a good practice or recommendation to perform, but will atleast prove how far your SQL Server environment has securit compliance as per the industry best practices. Before we go to know how you can lockdown or know the steps, I would like to visit few leads on security perspective. You may be aware about Best Practices Analyzer for SQL Server 2000 - Best Practices Analyzer Tool for SQL Server 2000  to start analyzing your SQL Server environment.  This basic tool has give much of inisght of best practices within the industry that can be deployed within your environment, so its best to consider compiling a list of best practices for your environment based on your applications, then be sure all of your current SQL Servers meet these specifications and validate all SQL Servers deployed in the future meet those needs as well. The SQL Server Best Practices Analyzer is very similar to the SQL Server 2005 Upgrade Advisor, as such if you are planning to upgrade from SQL Server 2000 to SQL Server 2005,

So with the latest version of SQL Server 2005 the Best Practices analyzer tool has no significant difference, but the advantage is this could be executed prior to deploying the instance, when testing can be performed.  This is quite opposite to the procedure you need to modifying production instances which is typically the case with SQL Server 2000 today.  Do not simply presume your policies are best to deploy and on timely basis you can run this tool against your SQL Server that are prone to 'public' network for a better security practice.

Lastly here is the LockDown-StepByStep article for your joy!