Editorials

What is Your Process for Addressing Vulnerabilities?

Featured Article(s)
Troubleshooting SQL Server 2005 Locking (Part 1)
In this article, Alexander Chigrik explains some problems that you can have with SQL Server 2005 locking. He also tells how you can resolve these problems.

What is Your Process for Addressing Vulnerabilities?
When you hear about issues with SQL Server-based applications, what do you do? I ask because there are new SQL injection vulnerabilities being announced at a conference, and there are always the continuing list of new attacks, new things people do to try to break into your systems.

Add to this the application of service packs, updates and new releases and it can keep you pretty busy testing, implementing, testing and … well, you get the idea.

What’s your approach? Do you wait for a problem to show itself on your own systems before you apply updates? Do you wait for a vulnerability to be exploited before working to address it? How do you approach this? Best practices would of course indicated that you address things as they’re identified. Reality can often dictate something quite different. Hopefully you’re not in a position of literally waiting for problems to occur before you address them, but perhaps somewhere in the middle – waiting to see the extent of an issue before you seek to address it.

Drop me a note, let me know how you go about this ongoing work.

Featured White Paper(s)
Managed .NET Connectivity
Database connections are the lifeblood of enterprise applications, administrating the secure and steady flow of information b… (read more)