Microsoft has this 3 pronged approach to ensuring your infrastructure is secure, but you have to do stuff as well. This 3D security goes like this:
Secure by Design. According to Wikipedia, “means that the software has been designed from the ground up to be secure. Malicious practices are taken for granted and care is taken to minimize impact when a security vulnerability is discovered or on invalid user input.
Secure by Default. Anyone installing SQL Server 2005/8 for the first time will know that having done that, there are further tasks needed to get access to the environment remotely as all the connectivity options are turned off. This gives the DBA the opportunity to configure security before everybody turns up to use it.
Secure by Deployment. This is where Microsoft and some other software suppliers, provide resources to ensure that your systems continue to be secure. This can take several forms:
This last section is all about trust, You trust your Microsoft or whatever vendor to be open and honest about security issues it has detected and to develop the appropriate resolution. Your vendor and your users need to trust you to implement the advice and resources that have been provided. I mention this because I noticed this ComputerWorld Security article that cites most (+70%) of Oracle DBA’s are not keeping up with applying patches to their systems. This isn’t any criticism of Oracle rather it’s illustrative. However I am hoping I am evangelising to the converted to the SQL Server DBA’s here!