Version policy


1. Naming convention

1.1. Products and main components

The appliance products and their main components have two main release types: Long-term Supported and Feature releases.

Some of the products are delivered with the release type: Rolling release.

Long Term Supported or LTS Release.

LTS releases are referred to as <product name> <LTS version number> 'LTS', for example:

 syslog-ng Store Box 4 LTS

Feature Release.

Feature releases are referred to as <product name> <base LTS version number> 'F'<feature version number>, for example:

syslog-ng Store Box 4 F3

For both the LTS and the Feature Releases Balabit regularly incorporates security patches and bug-fixes and issues updated Revisions of the released product. These Revisions have a comma separated technical identifier that refers to the base Release in the first 2 digits that is followed by a sequence number. In case of a security revision it additionally includes a letter. For example:

 syslog-ng Store Box 4.0.1 -> 1st revision of syslog-ng Store Box 4 LTS 
syslog-ng Store Box 4.3.2 -> 2nd revision of syslog-ng Store Box 4 F3
syslog-ng Store Box 4.3.3a -> 1st security patch of the 3rd revision of syslog-ng Store Box 4 F3

Rolling release.

This form of software releasing is intended to achieve faster release cycle for the products. New features, bug and security fixes will be launched in the same release as they are available for production usage.

Rolling releases are referred to as <product name> <base version number if exists> <release identifier>

Note
Customers are recommended to always install the latest Revision of the used software Release.

1.2. Client modules (e.g. BAP)

Floating Release.

Client-side components of certain products (e.g. the Audit Player) have so-called floating releases, referred to as <product name> <yyyy.x>, for example:

BAP 2011.1

Note
For all the above software Releases Balabit regularly incorporates security patches and bugfixes and issues updated Revisions of the Released product. Customers are recommended to always install the latest Revision of the used software Release.

For floating releases, only the latest revision of the latest version is supported.

2. Support time-line

Each SCB and SSB LTS Release (for example, syslog-ng Store Box 4 LTS) is supported for 3 years after original publication date and for 1 year after succeeding LTS Release is published (whichever date is later).

syslog-ng PE LTS Release (from syslog-ng PE 6 LTS) is supported for 3 years after the original publication date. No succeeding LTS Release is planned. From syslog-ng PE 7 rolling release will be introduced.

Note
Only the latest revision is supported.

Each rolling release is supported for 12 months after the original publication date. Bugs are accepted on any of the supported versions. Bugfixes shall only be implemented on the newest version.

Each Feature Release (for example, syslog-ng Store Box 4 F2) is supported for 6 months after original publication date and for 2 months after succeeding Feature or LTS Release (whichever date is later).

Note
Only the latest revision is supported.

In case of Client Modules only the latest Release is supported.

  • Example 1. Support time-line example I

    LTS Releases are supported for 1 year after next LTS Release is published, or for 3 years (whichever is later).

    If syslog-ng PE 4 LTS is published January 1, 2011 and syslog-ng PE 5 LTS is published July 1, 2014, then the syslog-ng PE 4 LTS release is supported until July 1, 2015 (+1 year rule).

    If syslog-ng PE 4 LTS is published January 1, 2011 and syslog-ng PE 5 LTS is published January 1, 2013, then the syslog-ng PE 4 LTS release is supported until January 1, 2014 (3 years rule).

  • Example 2. Support time-line example II

    Feature Releases are supported for 2 months after the next Feature or LTS Release is published, or for 6 months (whichever is later).

    If syslog-ng PE 4 F1 is published January 1, 2011 and syslog-ng PE 4 F2 is published March 1, 2011, then the syslog-ng PE 4 F1 release is supported until July 1, 2011 (6 months rule).

    If syslog-ng PE 4 F1 is published January 1, 2011 and syslog-ng PE 4 F2 is published August 1, 2011, then syslog-ng PE 4 F1 is supported until October 1, 2011 (+2 months rule).

  • Example 3. Support time-line example III

    If syslog-ng PE 6 LTS is published July 30, 2016 the end of life date of syslog-ng PE 6 LTS is July 30, 2019. This LTS will be supported for 3 years without succeeding LTS.

3. Appliances

Hardware appliances are supported for 3 years after the purchase by default. This support period might be extended based on individual agreement.

Support for a hardware appliance means that Balabit assures that all supported software versions are compatible with supported hardware as described above.

Balabit changes the hardware specification of the appliance in about every 3 years. Once it is changed, new appliances are sold with the new hardware specification. The change of hardware specification does not affect the warranty or the support of previously sold appliances.

When purchased, hardware appliances are preinstalled with the latest available LTS Release. Customers may install a supported Feature Release on the appliance but in this case the appropriate support time-line (6 months +2 months) applies.


Please send your comments or documentation bugs to: [email protected]

Mitigate against privileged account risks
Get in touch

Recent Resources

The top IT Security trends to watch out for in 2018

With 2017 now done and dusted, it’s time to think ...

The key takeaways from 2017’s biggest breaches

Like many years before it, 2017 has seen a large ...

Why is IT Security winning battles, but losing the war…?

When a child goes near something hot, a parent will ...

“The [Balabit] solution’s strongest points are the privileged session management, recording and search, and applying policy filters to apps and commands typed by administrators on monitored sessions.”

– The Forrester Wave, Privileged Identity Management, Q3 2016, by Andras Cser