(Lack of) Patch Management Highlighted in US Congress

March 9, 2018 / G C Network / Comments Off

Twitter Feed

Operation Golden Phoenix

By G C Network | July 22, 2008

This week, Dataline is participating in Operation Golden Phoenix. Operation Golden Phoenix is a four-day multi-agency collaborative training event designed to assist federal, state and local agencies with large and…

DISA Reaches out to Industry on Cloud Computing

By G C Network | July 21, 2008

In an interview with Computerworld , published in the New York Times, John Garing expanded on his goals for the DISA cloud computing initiative. Garing said that, “… he and…

Cloud Computing is $160B Market

By G C Network | July 18, 2008

According to the Financial Post, a Merrill Lynch Note estimates that cloud computing could be a $160B market by 2011. The companies that they see in the marketplace are shown…

SOA-R Educational Series: What is Cloud Computing

By G C Network | July 18, 2008

On July 16th, SOA-R held it’s first of six educational sessions on cloud computing for national security missions. Presenters during this first event were: Steven L Armentrout, PhDPresident & CEOParabon…

Gartner: Cloud Computing Fraught with Security Risks

By G C Network | July 17, 2008

Cloud computing is fraught with security risks, according to analyst firm Gartner. Smart customers will ask tough questions, and consider getting a security assessment from a neutral third party before…

The Definition of “Net-centric”

By G C Network | July 16, 2008

Last week, the Google Cloud Computing Group debated the definition of net-centric. The key thought was that net-centric was nothing more than internet-centric or basically “online” and therefore it really…

Cloud Computing Journal Launched

By G C Network | July 15, 2008

“The world’s first journal devoted to the delivery of massively scalable IT resources as a service using Internet technologies has been launched by SYS-CON Media. The all-new “Cloud Computing Journal”…

SOA-R First Session Presentations Announced

By G C Network | July 14, 2008

The presentations for the first session of the SOA-R Educational Series sesion have just been announced: Steven L Armentrout, PhDPresident & CEOParabon Grids, Clouds and Computation: Getting to Ground Truth…

Cloud Storage as a Service

By G C Network | July 14, 2008

In SAN vs cloud storage – a gray or silver lining? , Joseph Hunkins review last December’s observations of cloud storage by Chris Mellor of Techworld: “Google does not use…

Google: Model for the Systems Architecture of the Future

By G C Network | July 14, 2008

In December of 2005, Prof. Paul A. Strassmann of George Mason University, provided an excellent outline for cloud computing success in a netcentric environment: Network-Centric Requirements (2010)• Downtime ( 1…

« Previous
1
…
63
64
65
66
67
…
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.