Post Patch Tuesday. Don't Stop ThereWhile you may be well underway testing and deploying this month's hefty batch of patches from Redmond, it's never too soon to ask: how secure do the rest of your applications and servers look?
While you may be well underway testing and deploying this month's hefty batch of patches from Redmond, it's never too soon to ask: how secure do the rest of your applications and servers look?There's no reason to go through all of this trouble month after month deploying all of these Microsoft patches only to leave the rest of your servers and applications porous and open to anyone who has read a beginner's book about Web application hacking.
Unfortunately, that's what many medium-sized enterprises tend to do.
And there's really no reason for it, beyond not taking the time to cover the security basics.
Here a few steps that can be taken to get your organization headed in the right direction:
Harden Servers. Review your vendor guidance on how to keep the servers secured and establish an acceptable configuration. Test that configuration before deployment into production: turn off unnecessary services, make sure patches are up to date, change manufacture passwords. NIST maintains its 800 series documents, of interest to those responsible for IT security. Check out SP800-123, Guide to General Server Security. Next: make sure they stay hard.
Vulnerability Assessments. Outsource or do-it-yourself: run vulnerability assessments across your infrastructure to: make certain you're aware of all networked devices that are active and to identify and prioritize vulnerabilities that need remediation on those systems. One of the keys to a successful vulnerability management program is repetition: identify vulnerabilities, prioritize, remediate, validate remediation - and repeat.
Review Your Code. In addition to network scans, it's vital to have your application code evaluated for flaws (either by someone trained in-house, or by a consultant familiar with web application security.). The most effective way to build secure applications is to build applications with security as part of the process throughout. That includes from application design through development. With additional careful security testing before moving to production and then throughout maintenance: one wants to build security into the Software Development Life-cycle (SDLC). Microsoft has provided guidance on getting started with what it calls the Secure Development Lifecycle. And the Open Web Application Security Project (OWASP) has plenty of resources on the subject as well.
So while you labor through the pain of patching your systems with these 34 patches, save some energy to test your other applications and to make sure your servers are snug. Otherwise, you're really just wasting your time.
For my security and technology observations throughout the day, find me on Twitter.