(Lack of) Patch Management Highlighted in US Congress

March 9, 2018 / G C Network / Comments Off

Twitter Feed

CloudCamp Federal 2008 – Don’t miss out !!!

By G C Network | November 7, 2008

Tickets are going fast for CloudCamp Federal 2008 on November 12th in Chantilly, Virginia !! Representatives from the following organizations are already registered to attend. 3TERAAmazon Web Services (AWS)AOLAppistryApptisBooz Allen…

Private Clouds

By G C Network | November 5, 2008

Yesterday in eWeek, Chris Preimesberger, provided a very good read in “Why Private Cloud Computing is Beginning to Get Traction“. “Private cloud computing is a different take on the mainstream…

Important Cloud Computing Events

By G C Network | November 4, 2008

Mark your calendar for the following cloud computing events. These are specifically targeted to organizations looking to leverage cloud computing technologies and techniques in support of national security requirements. CloudCamp…

Forrester: Embrace Cloud Computing to Cut Costs

By G C Network | November 3, 2008

“Forrester Research advises CFOs to take a close look at cloud computing for messaging and collaboration and enterprise applications. The payoffs could be noticeable during the current economic downturn.” In…

Government still wary of cloud computing

By G C Network | October 31, 2008

Federal News Radio interviewed Ron Markezich, a corporate vice president of Microsoft, Mike Bradshaw, president of Google federal, and Michael Farber, a partner with Booz Allen on the government’s approach…

Microsoft Azure

By G C Network | October 30, 2008

With the announcement of Azure, Microsoft has finally made it’s cloud computing plans public. Maybe Larry Ellison is now ready to revise his opinion, huh? While this announcement is definitely…

Federal Grants from the Cloud

By G C Network | October 29, 2008

In case you mised it, the Department of Interior has announced that it plans to build a cloud computing platform to manage the processing and distributing of government grants. “Grants.gov…

Economist.com : Let it rise

By G C Network | October 28, 2008

This week, The Economist provides an insightful special report on cloud computing. From “Clouds and Judgement“: “Computing is fast becoming a “cloud”—a collection of disembodied services accessible from anywhere and…

Some More Cloud Computing Survey Results

By G C Network | October 27, 2008

As promised, here are some more results from the MIT/”Cloud Musings” on-line survey! Please remember, THIS IS NOT A SCIENTIFIC SURVEY !! The purpose is only to get a sense of…

Steve Ballmer comments on Microsoft’s cloud plans

By G C Network | October 24, 2008

On October 17th in the “Redmond Channel Partner Online”, a Microsoft Partner community publication, Kurt Mackie reported on Microsoft’s CEO Steve Ballmer’s comments on the company’s vision for syncing up…

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