(Lack of) Patch Management Highlighted in US Congress

March 9, 2018 / G C Network / Comments Off

Twitter Feed

The Time is Now for 21st Century Leadership

By G C Network | November 10, 2013

I’ve just had the opportunity to preview my good friend Melvin Greer’s newest effort, “21st Century Leadership: Harnessing Innovation, Accelerating Business Success“. Now in pre-release, this book highlights the compelling…

Public Cloud IaaS : A Price/Performance vs. Security Analysis

By G C Network | October 25, 2013

Industry’s transition from custom made, one-of-a-kind IT infrastructures to the standardize, commodity based cloud paradigm is well on it’s way. IBM’s recent “Under Cloud Cover” study highlights the rapidly of…

Catch the Cloud with DorobekINSIDER LIVE!

By G C Network | October 17, 2013

Yesterday I thoroughly enjoyed an opportunity to participate in the DorobekINSIDER LIVE edition on cloud computing. The conversation was both lively and informative. Joining me on the show were:…

Cloud Shines Brightly as Future of Disaster Response IT

By G C Network | September 14, 2013

The call for help began as a rumble. Twenty miles beneath the ocean’s surface, a rupture in a massive tectonic plate ripped a 310 mile-long break in the sea floor,…

NCOIC/NGA Demonstrates Use of Cloud in Disaster Response

By G C Network | September 5, 2013

When the world’s next major earthquake, tsunami or other disaster hits, military, government and civilian NGA project is available on the NCOIC website. responders will need to manage and…

NBC4 Puts On A Great GovCloud Show !!

By G C Network | August 25, 2013

NBC 4 in Washington, DC highlighted government cloud computing today as part of their GovInnovate show. Below is just a taste of the informative public service they provided. Go to…

OMB’s Evidence Memo: A Call for Cloud Services Brokerage

By G C Network | August 21, 2013

by Ray Holloman and Kevin Jackson In a late July memo the Office of Management and Budget requested cloud services brokerage. Well, not in so many words. Rather, OMB requested…

Cloud Services Brokerage Lessons From Alex Rodriguez, Baseball’s Trade Deadline

By G C Network | August 8, 2013

( A guest post from Ray Holloman, NJVC Corporate Communications) Two stories sat atop baseball’s marquee in the final days of July. The first was the non-waiver trade deadline, baseball’s…

Lessons Learned: VA Cloud Email Termination

By G C Network | July 17, 2013

According to a Federal Computer Week article by Frank Konkel, The Department of Veterans Affairs terminated its five-year, $36 million cloud computing contract for email and calendaring services with HP…

Deconstructing Cloud: An Excellent Guide to the Cloud Computing World

By G C Network | July 15, 2013

On an almost daily basis, I’m approach for my views on “cloud computing technology”. Although typically innocent in nature, I always cringe at the thought of enduring yet another hours…

« Previous
1
…
26
27
28
29
30
…
73
Next »

According to the former Equifax CEO’s testimony to Congress, one of the primary causes of this now infamous data breach was the company’s failure to patch a critical vulnerability in the open source Apache Struts Web application framework. Equifax also waited a week to scan its network for apps that remained vulnerable.[1]Would you like to appear at the next Congressional hearing on patch management?

Patch management is the process of identifying, acquiring, installing, and verifying patches for products and systems. Patches not only correct security and functionality problems in software and firmware, but they also introduce new, and sometimes mandatory, capabilities into the organization’s IT environment. It is so useful, the CERT® Coordination Center (CERT®/CC) claims that 95 percent of all network intrusions are avoidable by using proper patch management to keep systems up-to-date.

This nightmare true story and compelling endorsement from CERT®/CC, however, masks the ugly operational patch management implementation complexities. Key enterprise challenges include:

Timing, prioritization, and testing of patches often present conflicting requirements. Competitive prioritization of IT resources, business imperative, andbudget limitations often leave patching tasks on the back burner
Technical mechanisms and requirements for applying patches may also conflict and may include:
- Software that updates itself with little or no enterprise input
- Use of a centralized management tool
- Third-party patch management applications
- Negative or unknown interactions with network access control, health check functions, and other similar technologies
- User initiated manual software updates
- User-initiatedpatches or version upgrades
Typical enterprise heterogeneous environment that includes
- Unmanaged or user managed hosts
- Non-standard IT components that require vendor patching or cannot be patched
- Enterprise owned assets that typically operate on non-enterprise networks
- Smartphones, tablets, and other mobile devices
- Patching of rehydrating virtual machines
- Firmware updates

Piling up on these purely operational tasks are the change management steps associated with:

Maintaining current knowledge of available patches;
Deciding what patches are appropriate for particular systems;
Ensuring proper installation of patches;
Testing systems after installation; and
Documenting all procedures and any specific configurations.

This challenge can also be significantly exacerbated in an IT environment that blends legacy, outsourced and cloud service provider resources. Environment heterogeneity and the sheer volume of patches released is why any patching strategy that primarily relies solely on manual implementation is untenable.

According to the SANS Institute, meeting the patch management challenge requires the creation of a patch management methodology and the automation of that methodology.[2]The methodology itself should include:

A detailed inventory of all hardware, operating systems, and applications that exist in the network and the creation of the process to keep the inventory up-to-date.
A process to identify vulnerabilities in hardware, operating systems, andapplications.
Risk assessment and buy-in from management and business owners.
A detailed procedure for testing patches before deployment.
A detailed process for deploying patches and service packs, as well as a process for verification of deployment.

As for the automation component, it should deliver an automated, comprehensive server lifecycle approach that can provision and configure software, update patches and implement configurations that can improve security and compliance across physical, virtual and cloud servers.

It should also encompass a policy-based approach with support for all major operating systems on physical servers and leading virtualization and cloud platforms. An ability to automate continuous compliance checks and remediate any security or regulatory shortcoming is also paramount. If appropriately implemented, IT Staff should be able to manage patching via a web interface. Having this feature increases server to admin ratio, enhances operational productivity, accelerates audit timelines and reduces incident response latency.

A leading solution in this space is BladeLogicServer Automation by BMC. It was specifically designed to address the dual enterprise requirements of (1) ensuring compliance with rules and regulations and (2) software patching to reduce security vulnerabilities. In the market for over 10 years, it is a comprehensive server lifecycle automation solution that helps organizations provision and configure software, update patches and configurations to improve security and compliance across physical, virtual and cloud servers. Advanced capabilities include script automation, compliance tracking and the ability to stage and test patches before committing them. The latter feature is used to copy patch bundles to the targeted servers before maintenance windows open.The full-function suite integrates with change management systems to facilitate change record creation. Vulnerability management and remediation are automated by importing vulnerability management scan data from vendors like Qualys, Tenable and Rapid 7, and mapping the vulnerabilities back to underlying patches in BladeLogic.

Secure IT operations start with the identification and prioritization of critical vulnerabilities paired with the capability to deliver multi-tier remediation. These reinforcing goals are why an advance patch automation solution is a “must have” for today’s modern enterprise.

[1] https://arstechnica.com/information-technology/2017/10/a-series-of-delays-and-major-errors-led-to-massive-equifax-breach/

[2] https://www.sans.org/reading-room/whitepapers/sysadmin/meeting-challenges-automated-patch-management-1468

This post is brought to you by BMC and IDG. The views and opinions expressed herein are those of the author and do not necessarily represent the views and opinions of BMC.