Risk
8/11/2010
05:21 PM
George V. Hulme
George V. Hulme
Commentary
50%
50%

Post Patch Tuesday. Don't Stop There

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?

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.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Register for Dark Reading Newsletters
Dark Reading Live EVENTS
INsecurity - For the Defenders of Enterprise Security
A Dark Reading Conference
While red team conferences focus primarily on new vulnerabilities and security researchers, INsecurity puts security execution, protection, and operations center stage. The primary speakers will be CISOs and leaders in security defense; the blue team will be the focus.
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: No, no, no! Have a Unix CRON do the pop-up reminders!
Current Issue
Security Vulnerabilities: The Next Wave
Just when you thought it was safe, researchers have unveiled a new round of IT security flaws. Is your enterprise ready?
Flash Poll
[Strategic Security Report] How Enterprises Are Attacking the IT Security Problem
[Strategic Security Report] How Enterprises Are Attacking the IT Security Problem
Enterprises are spending more of their IT budgets on cybersecurity technology. How do your organization's security plans and strategies compare to what others are doing? Here's an in-depth look.
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-0290
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

CVE-2016-10369
Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

CVE-2016-8202
Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

CVE-2016-8209
Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

CVE-2017-0890
Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.