End of Life Policies for Software and Hardware
Overview
LogRhythm provides full engineering and technical support for the LogRhythm SIEM software for 24 months after the General Availability release date. Hardware support lifetime is five years from shipment date. This document outlines LogRhythm’s policies regarding the LogRhythm hardware and software product end of life. LogRhythm reserves the right to modify this policy.
The LogRhythm Solution consists of software and optional hardware, each with its own product lifecycle. Support for either is contingent upon your current maintenance agreement. The End of Life policies of any third party products resold by LogRhythm are maintained by the respective third party.
End of Life Tables
End of Life Dates for SIEM Software Releases
Version | Original GA Release Date | Last Supported Version | End of Sale | End of Support Life |
|---|---|---|---|---|
| 7.17.x | 01 July 2024 | TBD | TBD | 31 July 2026 |
| 7.16.x | 01 April 2024 | 7.16.0.45 | 01 July 2024 | 30 April 2026 |
| 7.15.x | 04 January 2024 | 7.15.0.64 | 01 April 2024 | 31 January 2026 |
| 7.14.x | 02 October 2023 | 7.14.0.107 | 04 January 2024 | 31 October 2025 |
| 7.13.x | 29 June 2023 | 7.13.0.78 | 02 October 2023 | 31 July 2025 |
| 7.12.x | 03 April 2023 | 7.12.0 | 29 June 2023 | 31 March 2025 |
| 7.11.x | 05 January 2023 | 7.11.0.43 | 03 April 2023 | 28 February 2025 |
| 7.10.x | 28 September 2022 | 7.10.0.123 | 05 January 2023 | 31 October 2024 |
| 7.9.x | 23 June 2022 | 7.9.0 | 28 September 2022 | 31 July 2024 |
| 7.8.x | 11 October 2021 | 7.8.0 | 23 June 2022 | 30 November 2024 |
| 7.7.x | 05 April 2021 | 7.7.0 | 11 October 2021 | 31 May 2024 |
| 7.6.x | 18 November 2020 | 7.6.0 HF 2 | 05 April 2021 | 28 February 2024 |
| 7.5.x | 22 July 2020 | 7.5.1 | 18 November 2020 | 31 October 2023 |
| 7.4.x | 23 October 2018 | 7.4.10 | 22 July 2020 | 31 March 2022 |
7.3.x | 01 February 2018 | 7.3.5 | 23 October 2018 | 31 October 2020 |
7.2.x | 14 November 2016 | 7.2.7 | 01 February 2018 | 31 December 2018 |
End of Life Dates for Hardware Generations
Version | Original Release Date | End of Sale | End of Support Life |
|---|---|---|---|
| Gen6 | October 2023 | TBD | Five years from Date of Sale |
| Gen5 | July 2018 | TBD | Five years from Date of Sale |
Gen4 | July 2014 | September 2018 | Five years from Date of Sale |
Gen3 | March 2013 | July 2016 | Five years from Date of Sale |
Gen2 (LRX) | August 2009 | April 2013 | Five years from Date of Sale |
Gen1 (LR) | August 2006 | November 2009 | Five years from Date of Sale |
LogRhythm Software Product Lifecycle
LogRhythm Software Products
LogRhythm software products may include multiple components such as the Data Processor (DP), Platform Manager (PM), Advanced Intelligence (AI) Engine, Data Indexer (DX), Network Monitor (NM), and others as defined by the software version.
Software Product Lifecycle Definitions
Software Version. The version number associated with a release consists of a major, minor, and patch in the following format: major.minor.patch (7.2.3).
Major Release. 6, 7
Minor Release. 7.10, 7.11
Patch. 7.10.1, 7.10.2, 7.10.3
Release. Any major (e.g., 6.3 → 7.1) or minor software version (7.10 → 7.11) increment that is made available to customers.
General Availability (GA) Date. The date a software release version is made generally available to customers for installation, not including beta or early access programs.
Knowledge Base (KB) Updates. Knowledge base updates include:
New log processing rule sets.
New analytics modules that might include: Reports, Alarm Rules, AI Engine Rules, Investigations, Lists, and other supporting content
Updates to existing log processing rule sets and analytics modules.
End of Sale (EoS). When a product release version reaches End of Sale, the version will no longer be available for sale.
End of Support Life (EoSL). When a product release version reaches End of Support Life, it will no longer be supported by LogRhythm’s technical support services.
LogRhythm Software Product Support Policies
- End of Sale (EoS). LogRhythm sells and ships the current software release only. Upon the General Availability of a new release, any previous release is considered End of Sale (EoS).
For example, when v7.13 becomes generally available, the v7.12 release will be considered End of Sale. - End of Support Life (EoSL). Support will work with customers on versions up to 24 months old from current release to help determine and fix issues. If a fix/hotfix/vulnerability or patch is required, customers will be required to upgrade to a later version where the defect/vulnerability no longer exists.
- All log archives created by previous software versions are supported by new releases.
LogRhythm Hardware Product Lifecycle
LogRhythm Hardware Products
LogRhythm hardware product lifecycle includes all products entitled as a LogRhythm appliance, including dark spares and test appliances.
LogRhythm Hardware Product Lifecycle Definitions
Date of Ship (DoS). The date the hardware was shipped to the end user.
Hardware Generation. The generation level of the hardware.
The Gen1 Hardware generation includes the LR500, LR1000, and LR2000 product series.
The Gen2 Hardware generation products are all prefixed with LRX (e.g., LRX1, LRX2, and LRX3).
The Gen3 Hardware generation is designated by the second number in the product code (e.g., XM4310, EM5350, and LM7310).
The Gen4 Hardware generation is designated by the second number in the product code (e.g., XM4410, PM7410, and DX5410).
The Gen5 Hardware generation is designated by the second number in the product code (e.g., XM4550, PM7500, and DX5500).
- The Gen6 Hardware generation is designated by the second number in the product code (e.g., XM4650, PM7600, and DX5600).
Midlife Generation Updates. LogRhythm may introduce enhancements to a hardware generation, such as improved storage capacity, memory, and/or processing. Hardware updates are designed by a change in the last digit of the product code (e.g., XM4431 and DX7411).
End of Sale (EoS). When hardware reaches End of Sale, the version will no longer be available for order. Appliances and optional peripherals may be available as inventory allows.
End of Support Life (EoSL). When hardware reaches End of Support Life, technical support services such as hardware debugging and hard drive replacement will no longer be available. This includes the ability to order replacement parts.
LogRhythm Hardware End of Life Policy
- End of Sale (EoS). LogRhythm resells and ships the current hardware generation only. Upon the introduction of a new hardware generation, any previous hardware generation is considered End of Sale (EoS). LogRhythm may allow sales of previous hardware generations and optional peripherals as inventory on hand allows.
For example, when fourth hardware generation is introduced, the third-generation hardware will no longer be available for sale. - End of Support Life (EoSL). Hardware End of Support Life (EoSL) occurs five years after Date of Ship. All appliances supplied by LogRhythm have a maximum five-year serviceable lifetime.
For a list of hardware generations and their End of Life dates, see the End of Life Dates for Hardware Generations table in the End of Life Tables section above.
End of Engineering Support for Log Sources with Log Source Optimization (LSO) Policies
LogRhythm has rewritten parsing rules, configuration guides, and mapping documentation for the most problematic legacy log source types as identified by LogRhythm Support and Engineering teams. We encourage customers to use the new LSO policies under the LogRhythm Default v2.0 Log Processing Policy. LogRhythm is not providing enhancements or parsing changes on the LogRhythm Default Log Processing Policy for these log source types going forward and will maintain the LogRhythm Default v2.0 Log Processing Policy.
More information about log source optimization and how to use log sources is available at Log Source Optimization. The log sources listed on that page have been updated to use the LogRhythm Default v2.0 Log Processing Policy. Additionally, a list of all log sources on the LogRhythm Default v2.0 Log Processing Policy can be found in the Deployment Manager under the Log Processing Policies tab.
End of Engineering Support for Open Collector Pipelines
LogRhythm’s Open Collector has changed the way LogRhythm SIEM acquires and normalizes data, allowing for MDI Fabric to extract the most important parts of the log message. As of LogRhythm version 7.14, our System Monitor Agent (SMA) is taking steps to assist in the process and increase overall performance when collecting large datasets.
A new JSON Normalization Engine has been introduced on the SMA to help with this collection. These rules are easy to create, manage and customize. All LogRhythm Beats currently support forwarding to the SMA for the JSON Normalization, bypassing the old OC Pipeline to normalize the data. Now that this new engine has been running smoothly for nearly a year in some environments, support for OC Pipelines for Beats is coming to a close, and updating beats to send a SMA is now encouraged. Ending development on OC Pipelines means that the shift to JSON normalization on the SMA will produce faster and better normalization outputs.
The OC Pipeline will remain in place and functional for the time being. This means you can continue to use and run things as you do today, but when working with LogRhythm Technical Support Engineers, moving to the new SMA normalization will be a preferred route to normalization for logs collected by Beats. Tools such as OC Admin will continue to work and use the OC Pipeline for log normalization.
Refer to the Configure Beats for JSON Parsing topic in the Open Collector documentation for more information on configuring your Beats for JSON.