(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
A group of people standing in front of a large screen.

2018 AT&T Business Summit: Security “in” and “of” the Cloud

By G C Network | November 10, 2018

While public cloud is undoubtedly an outsized piece of the conversation, news headlines of the latest data breach can make this move a very frightening proposition. The question of how…

A group of people standing in front of a display.

My Brush with Royalty: Queen Latifah

By G C Network | November 9, 2018

Queen Latifah! Hip Hop Icon. Movie Star. Television Star. Fashion Model. Songwriter. Producer. Entrepreneurial Genius!? YES! Dana Elaine Owens, her given name, is co-owner of Flavor Unit Entertainment, a firm that includes…

What’s New in Puppet 5?

By G C Network | November 9, 2018

Puppet 5 is released and comes with several exciting enhancements and features that promise to make configuration management much more streamlined. This article will take a comprehensive look at these…

5 Reasons Why Ansible is the Best CM Tool Out There?

By G C Network | November 9, 2018

Amidst volatile markets, dynamic technology shifts, and ever-increasing customer demands, it is imperative for IT organizations to develop flexible, scalable and high-quality applications that exceed expectations and enhance productivity. A…

Machine learning APIs for Google Cloud Platform

By G C Network | November 9, 2018

Google Cloud Platform (GCP) is considered to be one of the Big 3 cloud platforms among Microsoft Azure and AWS. GCP is widely used cloud solutions supporting AI capabilities to design and…

What Is The Most Important Part of Architecture?

By G C Network | November 9, 2018

I always find it interesting to hear what people view architecture as. A lot of people think it’s just about the design aspect, where you get to put pen to…

Cloud migration best practice Part 4: Executing the migration

By G C Network | September 16, 2018

This series has stepped through cloud migration best practices. After providing an overview, we discussed: Classifying business-critical data. Updating organizational IT governance policies. Application screening and cloud workload selection. How to…

Cloud Migration Best Practice Part 3: Application Portfolio Analysis

By G C Network | September 16, 2018

In part three of this series on cloud migration best practice, I will focus on migrating the application itself. If you haven’t had the opportunity to read our recommendations from part…

Why Use Immutable Storage?

By G C Network | September 11, 2018

Data has become a global currency, and its value has nowhere to go but up.  According to The Economist online, the world’s most valuable resource is no longer oil, but…

CLOUD ACT: What Does That Mean for Your Cloud Storage

By G C Network | August 31, 2018

When Congress names a law after you, it’s getting serious.  That is where we are now with cloud computing.  The Clarifying Lawful Overseas Use of Data Act or CLOUD Act (H.R. 4943) is…

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