Support articles

Other WithSecure Products

  • Can wildcards be used when creating a real-time scanning exclusion for Linux Security 64

    Read more
    Issue:

    Can wildcards be used when creating a real-time scanning exclusion for Linux Security 64

    Resolution:

    Wildcards are supported when creating a real-time scanning for Linux Security 64. 

    For example, the exclusions /home/*/build or /home/*/project would have a similar effect. Additionally, an exclusion such as /etc/**/hello would not only exclude /etc/foo/hello and /etc/bar/hello but also /etc/foo/bar/hello.

    Note: Linux Security 64 real-time scanning exclusions and settings do not support

    system-wide environment variables.

     

  • How can I get a new Client Security or Server Security license certificate?

    Read more
    Issue:

    Our current license certificate does not contain the most recent subscription information or license keys for Business Suite Client Security, Server Security, Linux Security 64 or Policy Manager Server.

    How can I get an updated license certificate which includes the license keycodes required for when installing or updating to the newest product versions? 

    Resolution:

    To get a new license certificate, proceed to contact your Withsecure reseller partner, they can provide a new licence certificate. 

    A WithSecure partner with access to Partner Portal can find the license certificates from the Partner Portal:

    1. Log in to the Partner Portal https://partnerportal.withsecure.com
    2. Navigate to Sales > Accounts (This will take you to the list of your customers)
    3. Search for the relevant customer using the search field at the top right (if necessary)
    4. Click on the customer name to open the details view.
    5. Navigate to the "Deal Ordering & Subscriptions" tab
    6. Scroll down to the "Assets" section
    7. Click on the "Get Certificates" button
    8. Select the desired language and download the document
  • How to manually regenerate the baseline for integrity checker in Linux Security 64 and Elements Linux Protection?

    Read more
    Issue:

    How to manually regenerate the baseline for integrity checker in Linux Security 64?

    Resolution:

    Run the following command to regenerate the baseline index and prevents modifications to the baseline files.

    # /opt/f-secure/linuxsecurity/bin/fsic protect

    While the following command allows baseline files to be modified.

    # /opt/f-secure/linuxsecurity/bin/fsic unprotect

    This checks each file in the baseline that is configured for the policy. It checks if the file has been tampered with and also scans the file for malware. The command prints every file that fails verification to the standard output.

    # /opt/f-secure/linuxsecurity/bin/fsic verify

    More details refer to the help guide: Running the integrity checker from the command line | Linux Security 64 | Latest | WithSecure User Guides 

     

  • How can I exclude files or folders from being scanned by the Client Security or Server Security Real-Time scanning or DeepGuard features?

    Read more
    Issue:

    How can I exclude files or folders from being scanned by the Client Security or Server Security Real-Time scanning or DeepGuard features? 

    Resolution:

    If you want to exclude an object (file or folder) from being scanned by the Client Security or Server Security Real-time scanning or DeepGuard features, add the the full path of the object or the folder path into the Files and applications excluded from scanning list in the Policy Manager policy.

    For example:

    • Full path with filename: C:\test\test.txt (only text.txt in the C:\test folder is excluded from Real-Time scanning)
    • Folder full path: C:\test\ (everything in C:\test\ folder is excluded from Real-Time scanning)

    How to create a combined real-time scanning and DeepGuard exclusion for Client Security and Server Security devices from the Policy Manager Console:

    1. Log into Policy Manager Console
    2. Select a host or policy domain from the domain tree
    3. Open the Settings tab
    4. Navigate to the Windows > Real-time scanning settings page
    5. Scroll down to Files and applications excluded from scanning section
    6. Enable Do not scan the following files and applications
    7. Click Add from the right side of the table
    8. Enter the full path for each files, folder or SHA-1 of the application. Example:
      • Select File path if the file that you want to exclude always uses the same path.
      • Select Folder path if you want to exclude all files in a specific folder.
      • Select Application SHA-1 if the path for the file that you want to exclude may vary across different hosts.
    9.  Click the icon to distribute the policy (Ctrl + D)

    NOTE: If the file or folder is located in share drive, you need to add the exclusion in UNC format. Example: \\servername\share\folder\to\the\app.exe

    If this location is also mapped to a drive letter (e.g. N:\), then another exclusion must also be added in the mapped format as the following:
    N:\folder\to\the\app.exe

     Applications are excluded by SHA-1 hash to avoid dependency on the application file name.
     Examples:

    • 867b54f1bc5b71045a9a00baca485a24176b202c for notepad.exe
    • ed13af4a0a754b8aaee4929134d2ff15ebe053cd for calc.exe

     Files and folders are excluded by path. Wildcards are supported. Examples:

    •  \\HarddiskVolume1\Temp\eicar.com
    •  C:\Temp\eicar.com (client versions 14.x and newer)
    •  *\HarddiskVolume1\*\eicar.com
    •  C:\*\eicar.com (client versions 14.x and newer)
    •  *\eica?.com
    •  *\eica?.com (client versions 14.x and newer)
    •  *\HarddiskVolume1\documents and settings\*\MyApplication\*.ini
    •  C:\documents and settings\*\MyApplication\*.ini (client versions 14.x and newer)
    •  C:\MyFolder (client versions 14.x and newer)
    •  \\HarddiskVolume1\MyFolder
    •  \MyFolder\
    • *\MyFolder\* (client versions 14.x and newer)
  • How to update virus databases of Linux Security 64 manually in an isolated or offline environment?

    Read more
    Issue:
    • How to update malware definition database and engines of Linux Security 64 manually in an isolated or offline environment without an internet connection?
    • Is the update package self-contained, meaning it contains all signature updates, or is it an incremental update?
    Resolution:

    In case of Linux Security 64, you need to use a separate computer that has access to WithSecure update servers and has a Policy Manager Server installed in order to create an withsecure-updates.zip archive or content package before deploying it on the Linux Security 64 client to update the virus definition databases.

    You may refer to the following user guide page for more detail information: Creating the content package for isolated environments | Linux Security 64 | Latest | WithSecure User Guides 

    It is possible to create an update archive or content package of Linux Security 64 using the virus definitions update tool (fspm-definitions-update-tool.bat) of Policy Manager for Windows and it does not need to be run on the same computer as Policy Manager for Windows. 

    Note: Make sure that the "channels.json" contains the following at least the malware definition database and engine update files, which are needed for the Linux Security 64 installation, and the channel names are configured correctly.

    Note: We recommend to not modify the channels.json file if the archive size is not an issue for you.

        "fsbspamd-100-linux-x86_64",
        "aqualnx64",
        "capricorn-linux64",
        "fmlibunix64",
        "hydra-linux64",
        "baseguard-100-linux-x86_64",
        "fsbg-100-linux-x86_64",
        "linuxsecurity-1200-linux-x86_64"

  • How to install or update Client Security clients in an offline or isolated environment?

    Read more
    Issue:

    How to install or update a Client Security client that installed in an environment that has no internet connection (offline or isolated environment)? 

    Resolution:

    To install Client Security on an isolated or offline environment, you need a working Policy Manager with which you can create the default policy that will be embedded to the MSI installer that will be exported from the Policy Manager Console. We recommend using the latest version.

    First create the policy:

    1. Log in to the Policy Manager Console
    2. Create a new policy domain in the domain tree
    3. Select the policy domain and go to the Settings tab to set up your preferred settings

    To export the Client Security MSI installer:

    1. Download the latest JAR file from here: Support - Client Security | WithSecure™ 
    2. Open the Policy Manager Console 
    3. Go to the Installation tab 
    4. Click Installation packages > Import to import the JAR file
    5. Click Export and follow the on-screen instructions
      1. Remember to select the newly created policy domain as the initial policy

    Once the MSI has been exported, run it on the offline or isolated devices. The resulting Client Security installation will not have any malware definitions updates or engines installed, so they will be installed using a separately downloaded withsecure-updates.zip and fsaua-update_32.exe. 

     

    The tool for downloading updates is bundled with Policy Manager and can be extracted with the provided scripts. When you run it on any machine with internet access, the tool downloads the latest updates and required diffs to generate an all-in-one archive.

    By default, the tool uses the data\updates folder to store the downloaded update binaries. It also stores the update history to use as a reference for downloading the relevant diffs to the latest version.

    In addition to the update binaries, you also need the fsaua-update tool to import the prepared updates. This tool is included in the Client Security installation folder: C:\Program Files (x86)\F-Secure\Client Security\fsaua-update_32.exe.

    To update the malware definitions:

    1. Run the following command on the Policy Manager machine to prepare the tool:
      • Windows: C:\Program Files\WithSecure\Policy Manager Server\bin\prepare-fspm-definitions-update-tool.bat <destination folder>
      • Linux: /opt/f-secure/fspms/bin/prepare-fspm-definitions-update-tool <destination folder>
    2. Transfer the prepared binaries to a machine that has internet access, if necessary.
    3. Modify the tool configuration, if necessary:
      • conf\channels.json: this contains a list of the channels to be updated. By default, it includes updates for all the supported clients managed by Policy Manager. Only edit the channels.json if size of the updates in an issue. 
    4. Run the tool:
      • Windows: fspm-definitions-update-tool.bat
      • Linux: fspm-definitions-update-tool

    The resulting archive contains the full set of the latest definitions and diffs to this version. If all data is up to date, no archive is generated.

    1. Transfer the prepared archive (data\withsecure-updates.zip or data\f-secure-updates.zip depending on the client version) to the isolated host: directory on the isolated Client Security host.
      • Client Security: Transfer the withsecure-updates.zip archive to the C:\Program Files (x86)\F-Secure\Client Security directory on the host.
      • Server Security: Transfer the withsecure-updates.zip archive to the C:\Program Files (x86)\F-Secure\Server Security directory on the host
      • Client Security for Mac: Transfer the archive to any convenient directory on the host.
    2. Launch the update on the isolated host:
      • Client Security: Run C:\Program Files (x86)\F-Secure\Client Security\fsaua-update_32.exe with administrator privileges.
      • Server Security: Run C:\Program Files (x86)\F-Secure\Server Security\fsaua-update_32.exe with administrator privileges.
      • Client Security for Mac: Run sudo /Library/WithSecure/bin/guts2-standalone-update --updateFile <path to withsecure-updates.zip>.
  • Do Client Security and Server Security automatically scan removable media (USB thumb drives / sticks and SD memory cards) when attached to a Windows computer?

    Read more
    Issue:

    Is it possible for Business Suite Client Security and Server Security to scan automatically all removable media (USB thumb drives / sticks and SD memory cards) when they are attached to the Windows computer? 

    Resolution:

    Business Suite Client Security and Server Security can be set to automatically scan external USB storage devices for malware.

    Steps how to configure Client Security and Server Security to scan USB drives when they are inserted to a computer:

    1. Log in to the Policy Manager Console
    2. Select a host or policy domain from the domain tree
    3. Go to the Settings tab
    4. Go to the Manual scanning settings page
    5. Scroll down to the Action when USB storage device is plugged in settings. Select drop the drop down menu your desired action_
      • Do nothing (disabled)
      • Ask user to scan USB
      • Silently scan USB
      • Scan USB and show result to user
      • Force scan USB and show result to user
    6. Distribute the policies (Ctrl + D)

    When the Ask user to scan USB action has been selected, there will be a notification prompted to ask end users to scan any USB storage devices that they plugged in. You can simply close the notification without scanning and still able to use the USB device or you may choose to scan the device.

    The Silently scan USB will scan the USB without showing a prompt and the result will not be shown to the local user. 

    The difference between "Scan USB and show result to user" and the "Force scan USB and show result to user" options is that the former allows the local user to cancel the scanning, while the latter does not allow local user to stop the scan. 

  • How do I install or upgrade WithSecure Linux Security 64 and manage it with WithSecure Policy Manager?

    Read more
    Issue:

    How do I install or upgrade WithSecure Linux Security 64 and manage it with WithSecure Policy Manager?

    Resolution:

    If you have an existing WithSecure Linux Security 11.xx installed on the machine, uninstall it first before installing the WithSecure Linux Security 64 because it is not possible to upgrade due to different products. You may refer to the following user guides on how to uninstall WithSecure Linux Security 11.xx: https://community.withsecure.com/en/kb/articles/29448-how-do-i-uninstall-withsecure-linux-security-11-xx

    Then, download the JAR package from WithSecure download page and follow the steps below on how to install Linux Security 64 and manage it with Policy Manager: https://www.withsecure.com/en/support/product-support/business-suite/linux-security

    Installation steps:

    1. Install Policy Manager: Installing the product | Policy Manager | 16.10 | WithSecure User Guides 

    2. Download the latest Linux Security 64 installation package from the WithSecure downloads page and import it on the Policy Manager Console's Installations > Installation packages page: Linux Security - WithSecure™ 

    3. Make sure that all required packages or libraries are installed before installing Linux Security 64: System requirements | Linux Security 64 | Latest | WithSecure User Guides 

    Note: Refer to the product release notes for more details about the required packages including the list of supported operating systems for Linux Security 64: Linux Security 64 | Linux Security 64 | Latest | WithSecure User Guides

    4. Follow the instructions in the following user guide to export the Linux Security 64 installer: Creating the installation package | Linux Security 64 | Latest | WithSecure User Guides 
     
    Note: Use the license keycode of "WithSecure Linux Security Server Edition" when it asks for the keycode during the creation of the installation package of Linux Security 64 on Policy Manager Console.

    5. Run the installer on the Linux server: Deploying the installation package | Linux Security 64 | Latest | WithSecure User Guides 

    Note: You can skip the withsecure-updates.zip steps if you are not installing Linux Security 64 in an offline or isolated environment. 

    6. After running the installer on a Linux server, log in to the Policy Manager Console and open the Pending list to import the device to a policy domain
     
    7. Select either a specific host or a policy domain from the domain tree and open the Settings tab. Then navigate to the Linux sections to change the configurations. After changing the configurations, distribute the policies to the Linux devices (Ctrl + D). 

  • Error: "The package you are importing is outdated" when importing JAR package to Policy Manager Console

    Read more
    Issue:

    Error "The package you are importing is outdated. Please download the newer version of the product." when trying to import a .jar installation package on the Policy Manager Console's Installations > Installation packages page. 

    Applicable products:

    • Client Security for Windows 
    • Server Security
    • Linux Security 64
    • Client Security for Mac

     

    
    
    Resolution:

    You need to make sure that you are using the latest .JAR file downloaded from the downloads page: Download Center | WithSecure™ 

    Delete the previously imported installation packages from the Policy Manager Console's Installations > Installation packages window, download the latest .jar installation packages and try to import again. 

  • Where to find end-of-life (EOL) announcements Business Suite products?

    Read more
    Issue:

    Where to find end-of-life (EOL) announcements Business Suite products? I want to know when the support for a specific version of Client Security, Server Security, Policy Manager or Linux Security 64 ends. 

    For example, when is the end of life for the support for the Client Security and Server Security 15.x versions? 

    Resolution:

    If you want to know which Business Suite Client Security, Server Security, Policy Manager or Linux Security 64 versions are currently supported and when their support ends (end-of-life), you can view our Supported product versions page: Supported product versions - WithSecure™ 

    To know more about our product lifecycle policies, you can view our general product lifecycle policies page: General product lifecycle policies - WithSecure™