(Lack of) Patch Management Highlighted in US Congress

March 9, 2018 / G C Network / Comments Off

Twitter Feed

Why the Cloud? Processing, Exploitation and Dissemination

By G C Network | October 23, 2008

So why is the intelligence community so interested in cloud computing? Three letters: PED (Processing, Exploitation, Dissemination). Take these two real life examples from the publishing industry. Jim Staten of…

World Summit of Cloud Computing: “Enterprise Cloud Computing” work group

By G C Network | October 22, 2008

To leverage attendees of the World Summit of Cloud Computing, a kick-off meeting of the “Enterprise Cloud Computing” work group will be held near Tel Aviv, Israel on December 3,…

Cloud Package Management

By G C Network | October 21, 2008

In his post “Missing in the Cloud: package management“, Dave Rosenberg highlights a critical issue in the adoption of cloud computing by government agencies. “I dare say that a standard…

PlugIntoTheCloud.com

By G C Network | October 20, 2008

Information Week has just launched PlugIntoTheCloud.com as their cloud computing destination. In his Non Linear Thinking blog, Bill Martin calls it a movement aimed at “providing a source and forum…

Is the cloud computing hype bad?

By G C Network | October 17, 2008

From Gartner “Why a little cloud hype might be useful“: “It’s too simplistic to say cloud hype is bad . If we are technically expert is might irritate us with…

Stop the FUD (Fear, Uncertainty and Doubt) !!

By G C Network | October 16, 2008

Dan Morrill! Count me in !! In his excellent article, “Cloud Computing is Scary – But the FUD Has to Stop“, Dan makes some excellent points: It is time to…

IBM, Microsoft and Google

By G C Network | October 15, 2008

On October 6th, IBM launched their cloud services initiative. This is a: “[C]ompany-wide initiative that extends its traditional software delivery model toward a mix of on-premise and cloud computing applications…

Government in the Cloud

By G C Network | October 13, 2008

Back in mid-September, there was quite a thread in the Google Cloud Computing Group on the use of cloud computing by the federal government. Some of the interesting comments were:…

CloudCamp Partners With SOA-R !!

By G C Network | October 10, 2008

I’m proud to announce that the final SOA-R Cloud Computing Education Event will be held in collaboration with CloudCamp. Now dubbed CloudCamp:Federal, the event will be held as an “unconference” to help…

Federal Cloud Computing Wiki

By G C Network | October 9, 2008

With the fast growing interest in cloud computing, the Federal Government community has established a Federal Cloud Computing Wiki. This wiki is managed by Dr. Brand Niemann, Senior Enterprise Architect…

« Previous
1
…
56
57
58
59
60
…
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.