- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
I am working in an organization with about 25,000 machines installed with Cortex XDR solution.
Recently we have noticed that there are many frequent upgrades being rolled out within a short time span.
To date, we are still having trouble keeping up with the upgrades on older systems especially with the jump from 7.9 to 8.0 due to Azure Code Signing requirements. This upgrade requires a lot of systems/applications needed to be revisited and multiple patches to be applied. While still tackling this issue, 8.2 has already been rolled out and 8.0 will be EOL by December 2023.
I understand that using the latest version of XDR is best practice, but the question I am trying to find an answer to is:
1. Would rolling back to CE versions be more advisable at our current state? Constant version upgrades require more resources to test the stability and iron out problematic installations one by one each time.
2. How do other companies manage their new versions rollout? Do they run into problems where large numbers of the XDR agent is not able to upgrade due to various reasons? If so, what would be the best way to handle this?
Standard versions support will be provided for 9 months after the release date. These versions will be released alongside the server, approximately every 3 months with a 9-month support period.
Critical Environment versions will be released in a cadence of 12-18 months and are designed to be installed in sensitive and highly regulated environments, will be provided 24 months of support since the release date. Due to its sensitive nature, these versions will include maintenance releases of critical and high-severity issues only. Frequency of hot-fixes depends on customer impact.
Also, please note, standard versions can be upgraded to CE version subject to caveats:
The Auto Upgrade setting is disabled by default, the upgrades are not intrusive typically takes an hour, the packet is small, you have the option config delay period.
If you found this answer helpful, please select Accept as Solution.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!