Supported FMOS Releases
We constantly update our software to ensure consistent support for the latest versions of firewalls, routers, and other network security enforcement points. We also update our software to offer new functionality, correct defects, and improve security. We recommend customers update to our latest release to get all the benefits of these changes.
Previously, FireMon only provided full support for the two most current releases of FMOS. Now, we will maintain support for Enterprise and Feature release tracks. We will attempt to support customers running unsupported releases, but support will be limited and best effort only. Customers running an unsupported release are encouraged to update to a supported release in order to receive the full support experience. A complete list of supported releases is listed below.
We can provide assistance with updating to a supported release. Customers wanting to receive assistance should contact us at support@firemon.com and specify the release number they are on and the release number they want to update to. A customer support agent will reach out to assist.
Release Process
We have transitioned from our traditional, larger updates, which were delivered on a less frequent schedule, to a more agile model. This means that we will be releasing more frequent, smaller updates. This approach will allow us to respond to your feedback quicker, rapidly implement enhancements, and swiftly address any issues that may arise.
Here are some key benefits of our updated release process:
-
Shorter feedback cycle: More iterations enable us to respond promptly to your feedback, ensuring the software evolves according to your needs. More frequent releases mean you can access new features, improvements, and bug fixes quicker than before.
-
Predictability: Established timeline for each release.
-
Quality: Smaller, more regular updates mean less downtime. This results in a minimized impact on your daily operations.
Please note that these changes will take effect immediately, beginning with our next scheduled software update—the 2023.1.0 Enterprise release. We will provide detailed guidance on managing and applying these updates, ensuring a seamless transition for your team.
FireMon offers four types of releases and two distinct release update tracks.
Release Types
FireMon offers four types of releases within two release tracks.
| Type | Purpose | Cadence | Name Example |
|---|---|---|---|
| Enterprise Release |
Annual “gold standard” baseline. Contains new/revised components, all features from the prior year, and maintenance fixes. |
Yearly | 2025.1 |
| Feature Release | Adds new features during the year on top of current Enterprise Release. Includes latest maintenance fixes. | Monthly | 2025.2.0 |
| Maintenance Release | Bug and security fixes only, no new features. Maintains backward compatibility. | Monthly | 2025.1.1 |
| Patch Release |
Urgent fixes for critical bugs and security issues. |
As needed | 2025.1.2 |
Enterprise Release
An Enterprise Release represents our golden standard version. It includes new or significantly revised software components, enabling support for new functionality or hardware while managing the risks of migrating from older releases to a single test cycle. It serves as a container for Feature and Maintenance Releases (e.g., 2025.1).
Feature Release
The Feature Release supports ongoing feature development within an Enterprise Release. Its aim is to introduce new features aligned with the Enterprise Release over time. It integrates new features, hardware support, and bug fixes. Multiple Feature Releases occur within each Enterprise Release, functioning as a container for Maintenance Releases (e.g., 2025.2).
Feature Releases occur monthly and include the latest maintenance release along with any newly added features.
Maintenance Release
A Maintenance Release derives from the Enterprise Release, freezing its software functionality and behavior at a specific point in time to ensure stability. It focuses on bug fixes without introducing new features, with behavior changes limited to necessary fixes. Backward compatibility is maintained (e.g., 2025.1.1).
Maintenance Releases are monthly, comprising all individual fixes tested together and released as a single patch. This release corrects security flaws or minor bugs without altering core components or adding new features. Best practices permit only fixes in a maintenance branch, prohibiting enhancements and interface changes unless absolutely necessary. The goal is to maintain product stability, as customers expect reliability.
Occasionally, with leadership approval, an important feature may be back-ported to a maintenance release, provided it does not disrupt existing functionality. All other changes must be deferred to an upcoming release in a professionally managed project.
Patch Release
Patch releases are issued as needed to address critical bugs, specifically those creating security vulnerabilities or system failures (e.g., 2025.1.1 or 2025.2.1).
Release Tracks
| Track | Audience | Cadence | Contents |
|---|---|---|---|
|
Enterprise Upgrade Release Track |
Customers prioritizing stability |
Annual Enterprise Release + Monthly Maintenance | All prior year’s features + bug & security fixes |
|
Feature Upgrade Release Track |
Customers wanting latest features | Monthly Feature Release + Maintenance | New features + bug & security fixes |
Enterprise Upgrade Release Track
-
Conducted once a year, with monthly maintenance updates.
-
It will include:
-
All content from the previous enterprise release
-
New features developed since the last enterprise release (all feature releases from the previous year)
-
All maintenance and patch releases since the last enterprise release (all maintenance and patch releases from the previous year)
-
-
The Enterprise Upgrade Release Track appeals to customers seeking stability, providing annual new content while ensuring monthly maintenance updates and patches.
Feature Upgrade Release Track
-
Conducted monthly.
-
It will include:
-
All content from the latest enterprise release (current year)
-
Content from previous feature release(s)
-
New features developed since the last feature release
-
All maintenance and patch releases since the last feature release
-
-
The Feature Upgrade Release Track attracts customers interested in the latest features while keeping up with monthly maintenance updates and patches.
Supported Releases
This new release process will also impact and change our supported releases.
Previously, FireMon only provided full support for the two most current releases of FMOS. Now, we will maintain support for Enterprise and Feature release tracks for 2 years after initial release date.
For example...
The Enterprise and Feature releases will receive support for a duration of two years from the initial release date, encompassing the 12-month period of active development and an additional 12 months dedicated to security updates. As an illustration, the release of version 2023.1.0 transpired on August 1, 2023, and our commitment extends to active development support until August 1, 2024, followed by exclusive provision of security patches until August 1, 2025.
To obtain fixes, you are encouraged to update to the corresponding 2023.1.x maintenance release. This principle also applies to customers following the Feature release track. For instance, if you are currently on release 2023.4, the recommended course of action is to update to the latest available release, such as 2023.7, to ensure continued access to support updates.
We will continue to attempt to support customers running unsupported releases, but it will be limited and best effort. Customers running an unsupported release are encouraged to update to the Enterprise or Feature release update track to receive the full support experience.
Updating Paths
Updating to specific releases using the fmos update command requires an intermediate update. For an intermediate update, you must contact FireMon Support.
The table below lists the update path to get to (2023.1.5 / 2023.5.0) and later.
| Current Release | Update Path |
|---|---|
| 9.0.0 - 9.10.7 | Intermediate update to 2023.1.0 (or up to 2023.1.4) required |
| 9.12.0 - 9.12.4 | Intermediate update to 2023.1.0 (or up to 2023.1.4) required |
| 9.13.0 - 9.13.2 | Intermediate update to 2023.1.0 (or up to 2023.1.4) required |
| 9.10.9 | Can update directly to 2023.1.5 / 2023.5.0 and later |
| 9.12.6 | Can update directly to 2023.1.5 / 2023.5.0 and later |
| 9.13.3 | Can update directly to 2023.1.5 / 2023.5.0 and later |
| 2023.1.0 | Can update directly to 2023.1.5 / 2023.5.0 and later |
Once the Feature release track is chosen, you must stick with it until the next Enterprise release. For example, if you chose the 2023.2 Feature release, you cannot switch to the Enterprise release track until the 2024 Enterprise release.
However, if the Enterprise release track is chosen, you can switch to the Feature release as long as it is a newer Feature release. For example, you can update from Enterprise 2023.1.7 to Feature 2023. 8.