(Lack of) Patch Management Highlighted in US Congress

March 9, 2018 / G C Network / Comments Off

Twitter Feed

Cloud Computing and the Process Integration Era

By G C Network | December 17, 2008

The Industry Advisory Council (IAC) is a non-profit, non-partisan organization dedicated to fostering improved communications and understanding between government and industry. through its affiliation with the American Council for Technology…

The Tactical Cloud

By G C Network | December 16, 2008

When cloud computing first came in vogue, there was a rather serious discussion about the private cloud concept. The whole idea of cloud computing seemed to argue against implementing such…

“Cloud Musings” Now on SYS-CON Media “Cloud Computing Journal” !!

By G C Network | December 15, 2008

I’m happy to announce that a recent “Cloud Musings” article, “Commercial vs Federal Cloud Computing ” has been reposted on SYS-CON Media’s “Cloud Computing Journal“. Thank you SYS-CON for making…

How to make clouds interoperable and standard !!

By G C Network | December 12, 2008

This has been a huge part of my life over the past few weeks! This is my personal view. WARNING: DON’T EXPECT THE ANSWER TO BE FOUND BELOW !!! There…

The Tension between Public and Private Clouds

By G C Network | December 11, 2008

Last week, during discussion on cloud interoperability and standards in Israel, I saw for the first time a real dichotomy in the value of public (external) and private (internal) clouds.…

Cloud Computing for Continuity of Operations (COOP)

By G C Network | December 10, 2008

Recently, I’ve been focusing on cloud computing for COOP. The way I looked at it, many government agencies are already using commercial shared facilities as COOP sites and that the…

NCOIC Plenary Session

By G C Network | December 9, 2008

Hopping a plane to the west coast today to attend the NCOIC Plenary in Costa Mesa, California. First day “Cloud Computing for Net-Centric Operations” agenda includes: David Ryan, Chief Architect…

Dataline named “Top 100 Cloud Computing Company”

By G C Network | December 9, 2008

SYS-CON’s Cloud Computing Journal included Dataline in its expanded list of the most active players in the cloud ecosystem. In adding Dataline to the “Top 100” list, Jeremy Geelan noted…

Autoscaling into the cloud- Good or Bad?

By G C Network | December 8, 2008

I always thought saw the ability to autoscale into a cloud infrastructure as a good thing. George Reese presented a differing view on the O’Reilly blog recently. “Auto-scaling is the…

Cloudera must be reading the script!

By G C Network | December 4, 2008

“Cloud computing leapt out as the most obvious way to address enterprise large data problems” – Ken Pierce, IT Specialist, DIA-DS/C4ISR “We view Hadoop as the key enabler…[in] optimizing the…

« Previous
1
…
52
53
54
55
56
…
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.