(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

From PC Break/Fix to CloudMASTER®

By G C Network | August 29, 2016

https://www.linkedin.com/in/stevendonovan It was late 2011 and Steven Donovan was comfortable working at SHI International Corporation, a growing information technology firm, as a personal computer break/fix technician. His company had been…

Is Data Classification a Bridge Too Far?

By G C Network | August 17, 2016

Today data has replaced money as the global currency for trade. “McKinsey estimates that about 75 percent of the value added by data flows on the Internet accrues to “traditional”…

Vendor Neutral Training: Proven Protection Against Cloud Horror Stories

By G C Network | August 10, 2016

Cloud computing is now entering adolescence.  With all the early adopters now swimming in the cloud pool with that “I told you so” smug, fast followers are just barely beating…

Cognitive Business: When Cloud and Cognitive Computing Merge

By G C Network | July 21, 2016

Cloud computing has taken over the business world! With almost maniacal focus, single proprietors and Board Directors of the world’s largest conglomerates see this new model as a “must do”.…

Government Cloud Achilles Heel: The Network

By G C Network | July 9, 2016

Cloud computing is rewriting the books on information technology (IT) but inter-cloud networking remains a key operational issue. Layering inherently global cloud services on top of a globally fractured networking…

System Integration Morphs To Cloud Service Integration

By G C Network | June 19, 2016

Cloud Service Brokerage is changing from an industry footnote toward becoming a major system integration play.  This role has now become a crucial component of a cloud computing transition because…

Networking the Cloud for IoT – Pt 3 Cloud Network Systems Engineering

By G C Network | June 17, 2016

Dwight Bues & Kevin Jackson (This is Part 3 of a three part series that addresses the need for a systems engineering approach to IoT and cloud network design.  Networking the Cloud for IoT –…

Networking the Cloud for IoT – Pt. 2 Stressing the Cloud

By G C Network | June 12, 2016

Dwight Bues & Kevin Jackson This is Part 2 of a three part series that addresses the need for a systems engineering approach to IoT and cloud network design. Part…

Networking the Cloud for IoT – Pt. 1: IoT and the Government

By G C Network | June 7, 2016

  Dwight Bues & Kevin Jackson This is Part 1 of a three part series that addresses the need for a systems engineering approach to IoT and cloud network design:…

Parallel Processing and Unstructured Data Transforms Storage

By G C Network | May 31, 2016

(This post originally appeared on Direct2Dell, The Official Dell Corporate Blog) Enterprise storage is trending away from traditional, enterprise managed network-attached storage (NAS) and storage area networks (SAN) towards a…

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