Atlant ChangelogAnnounced
This is the initial release of F-Secure Atlant.
F-Secure Atlant is a platform for building applications that are able to scan and detect malicious files.
Atlant provides a REST API for scanning files and managing the product configuration. Applications and services can use the API resources to analyze content using always up-to-date heuristics and statistical techniques. Atlant provides a scanning service to protect clients against viruses and other harmful files, exploits, network-based attacks, and other security threats.
Features and Benefits
The development kit offers the scanning functionality that utilizes multiple scanning engines and cloud-based file and network reputation services.
When deployed, the scanning service:
- scans files, emails and URLs for harmful content,
- protects content in real-time using cloud-based scanning,
- includes cloud-based reputation services for both files and network addresses,
- scans both HTTP requests and responses,
- includes multiple scanning engines,
- ICAP support, and
- is always up to date.
Supported Platforms
Atlant supports the following Linux distributions:
- CentOS 7
- CentOS 8
- RHEL 7
- RHEL 8
- Oracle Linux 7
- Oracle Linux 8
- Amazon Linux 2.0
- Debian 9
- Ubuntu 16.04
- Ubuntu 18.04
- SUSE Linux Enterprise Server 12
Installation Packages
- RPM package for CentOS, RHEL, Oracle Linux, Amazon Linux, and SUSE Linux Enterprise Server
- DEB package for Ubuntu and Debian
Documentation
Atlant documentation is available as a PDF. The documentation covers product installation and documents how the API can be used.
📝 Click here to see the most recent change log and bookmark the discussion to be notified of any updates.
Find more posts tagged with
Comments
LNX-692
: Improved product's responsiveness in the presence of network connectivity issues. The product now tries to automatically detect if certain backend services are unreachable and temporarily disable their use if they cannot be reached.LNX-658
: Introduced a new hotfix update mechanism to the product. This new hotfix service is used for rapidly delivering critical fixes to the product.- Miscellaneous bug fixes and improvements.
- Atlant version 1.0.328
- FSBG version 1.0.909
- a.karma.sc2.fsapi.com
- api.disobus.fsapi.com
- api.prd.glb.us-prd.fsapi.com
- aspam.fsapi.com
- aspam.sp.f-secure.com
- baseguard.doorman.fsapi.com
- download.fsapi.com
- guts2.fsapi.com
- guts2.sp.f-secure.com
- mind-failover.sc2.fsapi.com
- restmc.mind.sc2.fsapi.com
- update.sebe.fsapi.com
- LNX-703: The update will automatically enable offline mode during installation if the system cannot access all necessary backend services.
- Miscellaneous bug fixes and improvements.
- Atlant version 1.0.328
- FSBG version 1.0.907
- a.karma.sc2.fsapi.com
- api.disobus.fsapi.com
- api.prd.glb.us-prd.fsapi.com
- aspam.fsapi.com
- aspam.sp.f-secure.com
- baseguard.doorman.fsapi.com
- download.fsapi.com
- guts2.fsapi.com
- guts2.sp.f-secure.com
- mind-failover.sc2.fsapi.com
- restmc.mind.sc2.fsapi.com
- update.sebe.fsapi.com
- LNX-503: Added support for Ubuntu 24.04.
- LNX-566: Fixed an issue where the product could cause SELinux warnings to be shown under certain conditions.
- LNX-548: Switched the product to use a new online reputation backend service.
- LNX-612: Fixed an issue where reinstalling the product could fail due to leftover configuration from the previous installation.
- LNX-578: Fixed an issue where the product could cause excessive CPU usage if Policy Manager was unreachable.
- LNX-634: Fixed an issue where the product could fail to identify device's IP address and DNS name.
- LNX-661: Fixed an issue regarding database version data included into
diagnostic packages. - LNX-576: Product installation will now show a warning if the product is being installed using a deprecated installer.
- LNX-299: Removed obsolete BaseGuard update service.
- LNX-561: Removed support for TLS 1.0.
- LNX-629: Removed dependency on libcurl.
- LNX-668: Improved support for using the product in environments with limited connectivity.
- Miscellaneous bug fixes and improvements.
- a.karma.sc2.fsapi.com
- api.disobus.fsapi.com
- api.prd.glb.us-prd.fsapi.com
- aspam.fsapi.com
- aspam.sp.f-secure.com
- baseguard.doorman.fsapi.com
- download.fsapi.com
- guts2.fsapi.com
- guts2.sp.f-secure.com
- mind-failover.sc2.fsapi.com
- restmc.mind.sc2.fsapi.com
- update.sebe.fsapi.com
- Switched the container to use a new online reputation backend service.
- Miscellaneous enhancements and bug fixes.
- The installation mode for Policy Manager now necessitates the use of the most recent installer, which must be exported from Policy Manager version 16 or later.
- The addresses of the servers that are used for downloading updates in standalone mode or when the local Policy Manager is inaccessible have been changed.
Please refer to the related announcement for changes in network addresses: - Authorization endpoint now requires TLS 1.1 or later for communication. TLS 1.0 connections are no longer accepted because of security weaknesses in TLS 1.0.
- Miscellaneous bug fixes and improvements.
- Atlant Policy Manager installation package version 3.0.10, compatible with Policy Manager Server version 16.0 and above.
- Atlant installer DEB and RPM packages, version 1.0.53-1.
- Changed the activation to use new update server addresses by default. The new installer may download product content from guts2.fsapi.com and api.prd.glb.us-prd.fsapi.com.
See related announcement for network address changes: - Installer file and package names have been changed. This would affect any automated deployment and uninstall.
- Fixed an issue where product activation would fail if Squid proxy version 6.0 or higher was used.
- Fixed an issue where invoking activate with --download and --help options would incorrectly mark the product as activated.
- Miscellaneous bug fixes and improvements.
- LNX-280: This update changes the address of the server that is used for downloading updates. This change does not affect installations that download updates from a local Policy Manager except in situations where the local
Policy Manager cannot be reached.This update also changes the address of the service that is used for downloading metadata about pinned product versions.For installations in environments with restrictive firewall policies, this update might require manual intervention to ensure that the installation can still contact all the necessary services. See Atlant manual for more information about the addresses that Atlant installations may contact. - LNX-64: Fixed an issue where Atlant VA did not configure firewall rules automatically when the endpoint configuration was changed.
- Miscellaneous bug fixes and improvements.
- Log on to the endpoint on which you intend to install updates from a ZIP archive.
- Run the command
/opt/f-secure/atlant/fsbg/bin/withsecure-migrator status
- Check the last line of output from the above command.
- If the system reports that the command does not exist, or the command reports “not-performed” or “not-ready”, you can prepare a new f-secure-updates.zip archive for updates by using any version of fspm-definitions-update-tool and channels.json files you might already have available, and install the updates as before from the f-secure-updates.zip file using the offline-update program. Before starting to prepare another ZIP archive later, however, return to step 1 of these instructions.
- If the command at step 2 reports "migrated", the procedure for installing the updates changes as follows:
- First, please verify that you are using a recent enough version of fspm-definitions-update-tool for creating update archives.
- If you are using fspm-definitions-update-tool from a Policy Manager Server 16 installation, you are already at a new enough version.
- If you are not using Policy Manager 16, or are unsure about the version of fspm-definitions-update-tool, download the latest version of fspm-definitions-update-tool from the product download page, and extract the files to a directory.
- Second, download the latest version of the channels.json file to use to configure fspm-definitions-update-tool:
As before, replace the channels.json file under fspm-definitions-update-tool's conf/ subdirectory with the downloaded file, remove the data/ directory if it exists. - Run the fspm-definitions-update-tool program. fspm-definitions-update-tool will create a fresh data/ subdirectory with two ZIP archives: f-secure-updates.zip and withsecure-updates.zip. You must now use the withsecure-updates.zip file to install updates on the endpoint using the offline-update program.
(The f-secure-updates.zip file should no longer be used for installing updates on that endpoint. When run, fspm-definitions-update-tool will however continue to create this file to support packaging updates for endpoints which still need this file.) - After installing the product updates for the first time from the withsecure-updates.zip file on an endpoint, it won't be necessary to verify the status of the installation again on that endpoint (step 2); all later product updates can be installed using the withsecure-updates.zip file.
- First, please verify that you are using a recent enough version of fspm-definitions-update-tool for creating update archives.
- LNX-200: The product will require /sys/class/dmi/id/product_uuid file to be in place only when it is being managed by Policy Manager. Previously this file was always required.
- LNX-526: Fixed an issue where HTTP proxy was not used for downloading updates from fallback update server in Policy Manager managed mode.
- LNX-471: Fixed issues with compatibility with nosetuid file systems.
- Miscellaneous bug fixes and improvements.
- LNX-379: Added support for Debian 12.
- LNX-358: Fixed an issue where the product would fail to reinstall after having been uninstalled.
- LNX-414: Upgraded to OpenSSL 3.
- LNX-435: Fixed a crash in admin menu when showing current network configuration.
- LNX-474: Added new source for AlmaLinux updates. The old source will be removed in a future online update.
- The OVA archive is signed with a new code signing certificate.
- Miscellaneous enhancements and bug fixes.
- LNX-360: Solved an issue where an error about failing to clean up previous channel content could be printed after an update.
- LNX-363: Solved an issue where certain updates could fail due to errors about incompatible product-control.
- LNX-414: Upgraded to OpenSSL 3.
- LNX-298: Removed f-secure-baseguard-av service from the product.
- Stricter configuration file processing. Unknown properties in container's configuration file will now result in an error.
- Miscellaneous enhancements and bug fixes.
- Added support for maximum scan size setting.
- Miscellaneous enhancements and bug fixes.
- Atlant version 1.0.281
- FSBG version 1.0.741
- BaseGuard version 1.0.723
- LNX-369: Fixed an issue where URL scanning was not properly working with CONNECT requests.
- LNX-359: Improved setup robustness.
- LNX-278: Fixed an issue where an unreachable proxy could prevent certain services from starting.
- CSLP-4211: Fixed an issue where certain product updates would ignore update installation schedule.
- Added support for Rocky Linux 8 and 9.
- Updated OpenSSL.
- CSLP-4043: Fixed an issue with offline updates where updater could attempt to install channels in an incorrect order.
- LNX-26: Fixed an issue where URL classification was not working correctly when used with certain ICAP clients.
- LNX-245: Fixed an issue where offline-update command did not include any help text.
- LNX-23: Merged BaseGuard contents into FSBG. Previously some parts of product's functionality was distributed as a separate BaseGuard component.
- LNX-89: Fixed an issue related to ICAP protocol parsing.
- CSLP-3646: Improved error messages in offline-update to indicate that channels cannot be downgraded.
- CSLP-4205: Added a new setting to configure (or disable) maximum file size limit for scanned files.
- LNX-238: Fixed an issue where fsanalyze command would print archive member names incorrectly.
- CSLP-4174: Fixed a possible crash configuration management service.
- CSLP-3958: Allowed offline updates to be installed even when automatic updates are enabled.
- LNX-211: Fixed an issue where invalid utf-8 could be included to the access log.
- LNX-304: Fixed an issue where scanning service could fail under a heavy load.
- Atlant version 1.0.249
- FSBG version 1.0.703
- BaseGuard version 1.0.723
- CSLP-4169: Make it possible to bypass distribution compatibility checks and run the product on systems that are not officially supported. The main use case for this feature is to enable running the product on various "clone" distributions that resemble one of the supported distributions.
- CSLP-4012: Improved SELinux support.
- CSLP-4150: Fixed an issue where SELinux prevented accessing SSSD NSS module on Red Hat Enterprise Linux 7 and CentOS 7.
- MALT-529, MALT-536, MALT-563: Fixed crashes in ICAP service.
- MALT-441: Fixed an issue where URL scanning feature did not make a distinction between harmful and suspicious URLs.
- MALT-441: Fixed an issue where in certain situations subscription was incorrectly deemed to be invalid.
- CSLP-4160: Fixed a possible race condition when taking a new SELinux policy into use.
- CSLP-4170: Minimize the number of processes created by the antispam service.
- Miscellaneous enhancements and bug fixes.
New Atlant update has been released (2024-12-02)
New FSBG update (version 1.0.913) has been released. FSBG is a component of Atlant. This update includes the following changes:
New pinnable Atlant version is available (2024-10-02)
New pinnable Atlant version atlant-2024_3
has been released. Product version pinning enables Atlant installation to be locked to a specific version of the product. When the product version has been pinned the installation will still receive new engine and definition updates. Atlant supports product version pinning in standalone mode.
Each pinnable product version is supported for a year from the release of the subsequent pinnable version.
Note: As an exception, both atlant-2024_2
and atlant-2024_3
will be supported for the same period: one year from the release of the subsequent pinnable version.
atlant-2024_3
contains the following components:
To learn more about product version pinning, please refer to the Atlant manual.
Connectivity Requirements for WithSecure Atlant
To function correctly, WithSecure Atlant requires access to several online services. The detailed list of these services can be found in the User Guide.
Required Domains
Atlant needs access to the following domains:
The domains ending with f-secure.com will not be necessary after January 1st, 2025.
Proxy Configuration
If Atlant is configured to use an HTTP proxy for internet access, it will utilize this proxy for the above connections.
Offline Mode
In environments where access to these services is restricted, Atlant can operate in offline mode. To enable offline mode, execute the following command after installing atlant-2024_3
:
/opt/f-secure/atlant/fsbg/bin/offline-mode enable
This command disables connections to certain non-essential online services, allowing Atlant to function effectively with limited network access.
Known Issues
When upgrading from a previous pinnable product version, the atlantctl status
command might display the product version status as in-progress
for several hours. During this time, you may notice several HTTP 404 errors in the update.log file. These errors are harmless, and the product should eventually reach a state where atlantctl status
reports the product version as fully applied.
Please note that any new standalone installations that make use of the pinned product version functionality must be made using the latest available Atlant installer (version 1.0.53 or later) to be supported beyond the end of 2024.
New Atlant update has been released (2024-09-25)
New FSBG update (version 1.0.909) has been released. FSBG is a component of Atlant. This update includes the following changes:
New pinnable Atlant version is available (2024-09-04)
New pinnable Atlant version atlant-2024_2
has been released. Product version pinning enables Atlant installation to be locked to a specific version of the product. When the product version has been pinned the installation will still receive new engine and definition updates. Atlant supports product version pinning in standalone mode.
Each pinnable product version is supported for a year from the release of the subsequent pinnable version.
atlant-2024_2
contains the following components:
To learn more about product version pinning, please refer to the Atlant manual.
Connectivity Requirements for WithSecure Atlant
To function correctly, WithSecure Atlant requires access to several online services. The detailed list of these services can be found in the User Guide.
Required Domains
Atlant needs access to the following domains:
The domains ending with f-secure.com will not be necessary after January 1st, 2025.
Proxy Configuration
If Atlant is configured to use an HTTP proxy for internet access, it will utilize this proxy for the above connections.
Offline Mode
In environments where access to these services is restricted, Atlant can operate in offline mode. To enable offline mode, execute the following command after installing atlant-2024_2
:
/opt/f-secure/atlant/fsbg/bin/offline-mode enable
This command disables connections to certain non-essential online services, allowing Atlant to function effectively with limited network access.
Known Issues
When upgrading from a previous pinnable product version, the atlantctl status
command might display the product version status as in-progress
for several hours. During this time, you may notice several HTTP 404 errors in the update.log file. These errors are harmless, and the product should eventually reach a state where atlantctl status
reports the product version as fully applied.
Please note that any new standalone installations that make use of the pinned product version functionality must be made using the latest available Atlant installer (version 1.0.53 or later) to be supported beyond the end of 2024.
New Atlant update has been released (2024-09-02)
New Atlant (version 1.0.328) and FSBG (version 1.0.907) updates have been released. FSBG is a component of Atlant. These updates includes the following changes:
Connectivity Requirements for WithSecure Atlant
To function correctly, WithSecure Atlant requires access to several online services. The detailed list of these services can be found in the User Guide.
Required Domains
Atlant needs access to the following domains:
The domains ending with f-secure.com will not be necessary after January 1st, 2025.
Proxy Configuration
If Atlant is configured to use an HTTP proxy for internet access, it will utilize this proxy for the above connections.
Offline Mode
In environments where access to these services is restricted, Atlant can operate in offline mode. To enable offline mode, execute the following command:
/opt/f-secure/atlant/fsbg/bin/offline-mode enable
This command disables connections to certain non-essential online services, allowing Atlant to function effectively with limited network access.
New Atlant container release is available (2024-08-15)
Atlant container 1.0.60 is now available from our container registry. This release includes the following changes:
Extending the Support for atlant-2023_1 Pinnable Product Version
We have decided to extend the support period for the pinnable product version "atlant-2023_1". The new expiry date for this version is 2024-09-30. Previously, we had committed to supporting this pinnable version until the end of June 2024.
New Atlant Virtual Appliance version is available (2024-05-27)
New Atlant Virtual Appliance version 1.0.21 is now available for download. This release contains the following changes that have been added since the 1.0.20 release:
New Atlant update has been released (2024-05-27)
New FSBG update (version 1.0.841) has been released. FSBG is a component of Atlant. This update includes the following changes:
New Atlant installers have been released (2024-05-16)
The new product installers released are as follows:
The updates include the following changes:
Please note that the old installer packages are going to stop working at the end of the year. It is recommended to always use the latest available installer.
If you have already successfully installed the product there is no need to download or install these package. The product installer is only needed for the initial setup process and does not need to be kept up to date afterwards.
New Atlant update has been released (2024-03-12)
New Atlant update (version 1.0.319) has been released. This update includes the following changes:
Note for customers using ZIP files to update their installations
This product update includes changes which will affect the procedure to install future malware definition or product updates from ZIP archives. Please continue reading if you are currently making use of ZIP archives to install updates using the offline-update program.
After updating your product installation to the new version, follow these steps to prepare update ZIP archives in the future:
New Atlant update has been released (2024-02-20)
New FSBG update (version 1.0.828) has been released. FSBG is a component of Atlant. This update includes the following changes:
New Atlant update has been released (2023-10-24)
New Atlant update (version 1.0.295) has been released. This update includes the following changes:
New Atlant Virtual Appliance version is available (2023-10-16)
New Atlant Virtual Appliance version 1.0.20 is now available for download. This release contains the following changes that have been added since the 1.0.17 release:
New Atlant update has been released (2023-10-16)
New FSBG update (version 1.0.787) has been released. FSBG is a component of Atlant. This update includes the following changes:
New Atlant container release is available (2023-09-11)
Atlant container 1.0.53 is now available from our container registry. This release includes the following changes:
New Atlant container release is available (2023-07-31)
Atlant container 1.0.40 is now available from our container registry. This release includes the following changes:
New Atlant container release is available (2023-07-24)
Atlant container 1.0.36 is now available from our container registry. This release includes the following changes:
Atlant is now available as a container (2023-07-17)
Atlant is now available as a container image. Atlant container provides the same scanning and detection capabilities as other Atlant installation variants. See Atlant documentation for more information about deploying Atlant as a container.
Atlant container images can be found from our container registry.
New pinnable Atlant version is available (2023-06-21)
New pinnable Atlant version "atlant-2023_1" has been released. Product version pinning enables Atlant installation to be locked to a specific version of the product. When the product version has been pinned the installation will still receive new engine and definition updates. Atlant supports product version pinning in standalone mode.
This pinnable version will be supported until the end of 2023.
"atlant-2023_1" contains the following components:
To learn more about product version pinning, please refer to the Atlant manual.
New Atlant update has been released (2023-06-06)
New FSBG update (version 1.0.741) has been released. FSBG is a component of Atlant. This update includes the following changes:
New Atlant update has been released (2023-04-25)
New Atlant (version 1.0.280) and FSBG (version 1.0.738) updates have been released. FSBG is a component of Atlant. These updates include the following changes:
New pinnable Atlant version is available (2022-12-07)
New pinnable Atlant version "atlant-2022_6" has been released. Product version pinning enables Atlant installation to be locked to a specific version of the product. When the product version has been pinned the installation will still receive new engine and definition updates. Atlant supports product version pinning in standalone mode.
This pinnable version is supported until the end of 2023.
"atlant-2022_6" contains the following components:
To learn more about product version pinning, please refer to the Atlant manual.
New Atlant update has been released (2022-11-28)
New Atlant (version 1.0.249), FSBG (version 1.0.703), and BaseGuard (version 1.0.723) updates have been released. FSBG and BaseGuard are components of Atlant. These updates include the following changes:
New Atlant update has been released (2025-03-25)
New FSBG update (version 1.0.918) has been released. FSBG is a component of Atlant. This update includes the following changes: