(Lack of) Patch Management Highlighted in US Congress

March 9, 2018 / G C Network / Comments Off

Twitter Feed

Cloud Computing Wargames !!

By G C Network | January 22, 2009

Wikipedia “A wargame is a game that represents a military operation.” “Military simulations, also known informally as war games, are simulations in which theories of warfare can be tested and refined…

President Barack Obama. A New Day for Cloud Computing !!

By G C Network | January 20, 2009

Yesterday, President Barack Obama’s transition team released a new video touting the benefits of cloud computing and government transparency. “Cloud computing, which allows consumers and institutions to access their files…

How the Government Tweets – An Update

By G C Network | January 19, 2009

Thanks goes out to Twitter_Tips for a link to Government agencies on Twitter: a few comprehensive sites posted by lindyjb which includes the following: The Government’s A-Twitter: A Comprehensive List…

How the Government Tweets

By G C Network | January 16, 2009

Last September in “Ambient Awareness. The cloud killer app? ” and ” The Cloud Wins in Minneapolis at the RNC! “, I wrote about how the cloud infrastructure and microblogging…

Bob Gourley on Cloud Computing and NetCentric Operations

By G C Network | January 15, 2009

Bob Gourley, Crucial Point CTO and former DIA CTO, just posted Cloud Computing and Net Centric Operations on his website CTOvision . In it he outlines how the OSD and ASD NII…

Obama Administration CTO Top Suggestions

By G C Network | January 14, 2009

Check out the top vote getters for suggestions to the nations’s first CTO! #5 with 5,835 votes Open Government Data (APIs, XML, RSS) We can unleash a wave of civic…

2009 Cloud Computing Events

By G C Network | January 13, 2009

2009 is off to a fast start with the following events on the horizon! February 2009 – “Bi-Annual On-line Government Cloud Computing Survey”, On-line February 3, 2009 – Open Group…

World Summit of Cloud Computing Virtual Site

By G C Network | January 12, 2009

The Israeli Association of Grid Technologies (IGT) has made its recent IGT 2008 World Summit of Cloud Computing available on-line. Speakers include: Day 1: Stevie Clifton, Co-Founder & CTO Animoto…

1105 Government Information Group does Cloud Computing

By G C Network | January 9, 2009

Mark your calendars for April 29, 2009 ! 1105 Government Information Group has announced that there will be a Cloud Computing Conference at the Ronald Reagan Building in Washington, DC.…

Sun Acquires Q-Layer

By G C Network | January 8, 2009

Yesterday, Sun Microsystems announced their acquisition of Q-layer. This Belgium based company automates the deployment and management of both public and private clouds. In the press release, David Douglas, SUN’s…

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