(Lack of) Patch Management Highlighted in US Congress

March 9, 2018 / G C Network / Comments Off on (Lack of) Patch Management Highlighted in US Congress

Review: Executive’s Guide to Cloud Computing by Eric Marks and Bob Lozano

By G C Network | January 26, 2010

Recently, I had the privilege of reviewing an advance copy of Executive’s Guide to Cloud Computing by Eric Marks and Bob Lozano. Available now for pre-order on Amazon, this guide is a…

DoD Cloud Computing Session at 5th International Cloud Expo

By G C Network | January 22, 2010

I’m happy to announce that I will be presenting on DoD Cloud Computing Advances at the 5th International Cloud Expo, April 19-21, 2010 at the Javits Convention Center in New…

InformationWeek Prediction: Cloud Computing for Classified Software

By G C Network | January 20, 2010

Yes, I know you’re sick of all the predictions, but I just can’t resist pointing you to Nick Hoover’s “5 Predictions For Government IT in 2010“. In summary: 1. Cybersecurity…

“Shaping Government Clouds” Just Released

By G C Network | January 12, 2010

As part of the On The Frontlines series, Trezza Media Group has just released it latest on-line electronic magazine. “Shaping Government Clouds” includes: Pete Tseronis, Chairman of the Federal Cloud…

Fed Tech Bisnow: If Nostradamus Did RFPs?

By G C Network | January 6, 2010

Nostradamus may no longer be with us, but check out the “beltway” predictions from Tech Bisnow! “Two hot trends almost all mentioned: early uptick on M&A and cloud computing ubiquity”…

Navy CANES and Cloud Computing

By G C Network | January 4, 2010

During the first quarter of 2010, the Navy is expected to make the first selection for the Consolidated Afloat Network Enterprise System (CANES). CANES is just one component of the…

GovCloud, “Cloud Musings” rated “Influential” by Topsy

By G C Network | January 3, 2010

Log in with Twitter A search engine powered by tweets My sincere appreciation and thanks goes out to Topsy for rating my tweets as “Influential”! Topsy is a new kind…

Jill Tummler Singer Appointed NRO CIO

By G C Network | January 1, 2010

Effective January 1, 2010, Jill Tummler Singer will take the reigns as CIO for the National Reconnaissance Office (NRO). As the CIA Deputy CIO, Ms Tummler has been a proponent…

Most Influential Cloud Bloggers for 2009

By G C Network | January 1, 2010

Thank you Ulitzer and SYS-CON Media for naming me to your list of the most influential cloud computing bloggers for 2009. My hearty congratulations go out to the other bloggers…

2009: The Government Discovers Cloud Computing

By G C Network | December 23, 2009

2009 was truly a watershed year for Federal information technology professionals. After inaugurating the first Cyber-President we saw the appointment of our first Federal CIO and the rapid adoption of…

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.

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.
Cloud Musings

( Thank you. If you enjoyed this article, get free updates by email or RSS – © Copyright Kevin L. Jackson 2016-2018)

Follow me at https://Twitter.com/Kevin_Jackson
Posted in

G C Network

Cloud Computing

Cybersecurity