BEST for Linux automatic migration FAQ
In the first week of April, Bitdefender will start automatic migration of BEST for Linux from v6 to v7.
BEST for Linux v7 was launched in July 2021 alongside Bitdefender Security for Containers (BSC). This release brought a variety of new features, benefits and improvements including advanced prevention and detection technologies specifically designed to work against Linux and Container runtime oriented attacks. Additionally, due to no longer being reliant on kernel, we have eliminated Linux version compatibility issues.
To ensure a smooth transition, we continued support and availability for BEST for Linux v6. Later in 2021, v6 was placed in Limited Support. Once the migration is finished, we will continue to provide limited support for BEST for Linux v6, up until the end of Q4. After the end of Q4, we will no longer offer support for BEST for Linux v6.
With the initial feature disparity resolved, and BEST for Linux v7 offering multiple new features and enhancements, optimization of both efficacy and performance, and extended compatibility to new distributions, there is no reason to keep using version 6.
The first step consists in a BEST for Linux v6 live product update, which will prepare endpoints for the migration. Once this is finished, all endpoints with the latest version of BEST for Linux v6 will be upgraded to v7 automatically. The process will take place over time and should be finished by the end of June 2022.
For the automatic update to run successfully, these requirements must be met:
Product updates are enabled in the policy applied to the endpoint.
The latest version of BEST for Linux v6 is installed.
The operating system used on the endpoint is compatible with BEST for Linux v7.
If you are using BEST for Linux v6 with EDR, your system is able to support kprobes for the update to run.
The hardware minimum requirements are met.
5GB of free disk space at the moment of migration.
The operating system is up to date.
The migration will not apply under the following situations:
Auditd is used on the endpoint to enable EDR.
BEST for Linux v6 is installed on a custom path.
The endpoint is part of an offline network.
The update will deploy a new version number of BEST for Linux v7, different from all previous versions. At the next major v7 release, all agents will reach the same version number.
You need to perform a standalone or scripted installations on all endpoints that are not eligible. Uninstalling BEST for Linux v6 prior to the new installation is not required.
If you have any issues with the scripted installation, you can contact support for assistance.
No, we’ll have this pushed through an automatic product update, requiring no intervention from your end.
Due to the feature disparity between BEST for Linux v6 and v7, new features which are available only on v7 will be disabled by default. These features are:
Container Protection
Patch Management
Advanced Anti-Exploit
To activate these features, use the Reconfigure client task.
As long as the endpoints where BEST for Linux v6 has been deployed meet our eligibility requirements, they will be automatically updated.
Although we have structured the rollout in logical stages, we are always flexible with customer and partner requests and we can prioritize upon requests.
Yes, manual installation of BEST for Linux v6 will be available until the end of Q4. Uninstall the current version of BEST for Linux from the endpoint and manually install BEST for Linux version 6.
It will behave exactly like a regular product update and no restart is expected to take place.
We will be releasing an SDK based on BEST for Linux v7 during by the end of Q2 2022.
This environment is not supported.
The update will have the same level of security as any of our product updates.