Support articles

Find clear, step-by-step solutions to common WithSecure issues across installation, configuration, updates, and product performance.

Extended Detection and Response

View all

Collaboration Protection

  • Elements Collaboration Protection shows "Organization is not available Selected organization"

    Read more
    Issue:

    When trying to access a customer's company account in Elements Collaboration Protection portal as a reseller partner, it gives the error "Organization is not available Selected organization.....".

    Resolution:

    This error can happen due to browser cache issues, especially if you as a reseller partner were already logged in to the Elements Security Center when you sold the Collaboration Protection subscription through the Partner Portal and then try to immediately access the customer's Collaboration Protection product in the Elements Portal.

    If you receive the "Organization is not available Selected organization" error when trying to access a customer's Collaboration Protection organization in the Elements Security Center portal, try first to log out from the Elements Security Center portal, restart the browser and re-login to the portal.

    If issue persists, try clearing your browser cache or try to log in using an incognito or inprivate browser window.

    If clearing the cache or logging in with an incognito or inprivate browser window did not help, make sure from the Management > Organization Settings > Security administrators page that you have Collaboration Protection access rights.

  • Elements Collaboration Protection wrong amount of used licenses after turning protection off for one or more mailboxes

    Read more
    Issue:

    Elements Collaboration Protection shows wrong amount of used licenses after turning protection off for one or more mailboxes. The Elements Security Center portal's Management > Subscriptions page's Used column shows mailboxes count to be higher than there are protected mailboxes on the Cloud service's Exchange tab. 

    Resolution:

    The Elements Collaboration Protection license usage data that is shown on the Eleemnts portal's Management > Subscriptions page is actually a daily activity/usage and not the total amount of protected mailboxes.

    Therefore, it can change each day and is likely that the number in the Subscription view will occasionally be lower comparing to the amount of protected mailboxes. 

    We advise to go to the Elements portal's Collaboration Protection > Cloud Services > "Your Service" > Exchange tab and view the Available licenses count there. 

  • Is there a way to disable the email notification alerts for detections in Elements Collaboration Protection?

    Read more
    Issue:

    Is there a way to disable the email notification alerts for detections in Elements Collaboration Protection? Users would not want to receive the notification emails when malware has been found in an attachment or an email has been quarantined because it included a malicious URL address.

    Resolution:

    Yes, it is possible to disable the notifications that are sent to the users about detections by Elements Collaboration Protection:

    If you want to disable the user notifications for detection completely for when malware has been detected in an email:

    1. Log in to the Elements Security Center portal
    2. Navigate to the Collaboration Protection > policies page
    3. Open the policy that is in use on your cloud service
    4. Go to the Exchange > Malware
    5. Untick the Notify the user about detections with the following severities:
    6. Click Save

    If you want to disable the user notifications for detection completely for when malicious URL or suspicious URL has been detected in an email:

    1. Log in to the Elements Security Center portal
    2. Navigate to the Collaboration Protection > policies page
    3. Open the policy that is in use on your cloud service
    4. Go to the Exchange > URL scanning page
    5. Untick Notify the user about detections with the following severities under both Malicious URL and Suspicious URL
    6. Click Save

    If you want to disable the user notifications for detection completely for when a compromised account detection has been made towards the users email address:

    1. Log in to the Elements Security Center portal
    2. Navigate to the Collaboration Protection > policies page
    3. Open the policy that is in use on your cloud service
    4. Go to the Exchange > Compromised accounts page
    5. Untick Notify the user about detections with the following severities
    6. Click Save

    If you only want to not send user notifications based on the severity of the alert:

    1. Log in to the Elements Security Center portal
    2. Navigate to the Collaboration Protection > policies page
    3. Open the policy that is in use on your cloud service
    4. Go to the General > Notifications page
    5. From the User notifications based on severity, select the desired severity level that triggers a user notification:
      1. All (Low, Medium, High & Critical)
      2. Medium, High & Critical
      3. High & Critical
      4. Critical
    6. Click Save

Endpoint Detection and Response

  • Elements EDR Advanced response task shows "Failed" status

    Read more
    Issue:

    After creating an advanced response task for Elements Endpoint Detection and Response (EDR), the State is shown as Finished but the Progress column shows the task Failed.

    What can cause the advanced response task to fail? 

    Resolution:

    If the EDR advanced response tasks fail, first you need to make sure that the Advanced response actions are enabled in the Elements profile:

    1. Log in to the Elements Security Center portal
    2. Navigate to the Security configurations > Profiles page
    3. Open the profile that is in use on the devices
    4. Go to the General settings page
    5. In the Integrations section, make sure that Advanced response is enabled
    6. Click Save profile

    Also make sure that the required network connections are allowed. For that you can run the wsconnectionchecker.exe tool found in the Elements Agent installation folder: C:\Program Files (x86)\F-Secure\PSB\ui

    The connection checker tool has tests for WithSecure EDR Response Server, which need to succeed for the advanced response actions to work. The addresses are also mentioned in the user guide: Turn on advanced response actions | Elements Endpoint Detection and Response | Latest | WithSecure User Guides 

    If response actions are enabled in the profile and the connections show OK status, but the response action tasks would still fail, you need to make sure that the task you have created does not have any errors. For example if you have created a retrieve files task, you need to make sure that the folder path is valid. 

  • How to install stand-alone Elements EDR without removing conflicting software?

    Read more
    Issue:

    I am installing standalone Elements Endpoint Detection and Response with the ElementsAgentInstaller.exe file, and it detects a 3rd party antivirus as a conflicting product during.

    How can I proceed with the Elements Agent installation without sidegrading or uninstalling the conflicting antivirus software?

    Resolution:

    The Elements Agent EXE installer contains sidegrade functionality, where it will detect 3rd party antivirus program as conflicting software and automatically try to uninstall it.

    If you do not wish to uninstall conflicting products when installing Elements Agent with a stand-alone Elements Endpoint Detection and Response (EDR) subscription key, you can use the command-line parameter --skip-sidegrade to turn off automatic uninstallation of the existing products:

    1. Open a Command Prompt with administrator privileges
    2. Navigate to the folder where you have saved the ElementsAgentInstaller.exe
    3. run command:
      1. ElementsAgentInstaller.exe --voucher aaaa-bbbb-cccc-dddd-eeee --language en --skip-sidegrade "*"

    This will skip the sidegrade on any conflicting products during installation. 

    More detailed information regarding the Elements Agent EXE installer's Command-line parameters can be found in the user guide: Command-line parameters | Elements Endpoint Protection | Latest | WithSecure User Guides

  • After installing Elements Agent client with EDR subscription, the message "Device sensor is not operational" show up

    Read more
    Issue:

    After installing Elements Agent client with EDR subscription, the message "Device sensor is not operational" is shown in the local Elements Agent user interface.

    Resolution:

    You need to ensure that you have allowed the network traffic to the following addresses in your network firewall. The client sensor silently collects activity from the endpoint on which it is installed and then submits a representation of this data to a backend.

    To guarantee proper transmission, the endpoints need to be able to communicate over HTTP and HTTPS, port 443 with the services listed here:
    https://community.withsecure.com/en/kb/articles/31217-network-addresses-for-withsecure-elements-cloud-managed-products

    You should also allow connections to the digicert.com domain, as the Windows API may need to verify WithSecure services that are signed with a certificate that is issued by Digicert.

    In case you have an SSL interceptor to intercept the network traffic, we recommend creating whitelisting on the SSL interceptor for the EDR addresses. EDR and Countercept use the same certificate pinning approach that prevents connectivity when TLS interception solutions are used.

    Services that need to be whitelisted in the interceptor are:

    • DIS
    • Doorman
    • FAMP/Response

     

    If the connectivity is OK on the device and you still receive the error "Device sensor is not operational", you can check if the EDR sensor has at all been installed:

    1. Right click the Elements Agent icon on the device
    2. Click "Check for updates" 
    3. Scroll down the "Update history" list and check if it includes an entry for WithSecure Sensor (64-bit) and that it shows status as "installed" 

    If the WithSecure Sensor is completely missing or status is not installed, then the sensor installation failure can be due to a device having had Elements MDR or WithSecure Countercept installed on it before and the MDR or Countercept installation hasn't been fully uninstalled. 

    Elements MDR and Countercept both have a similar WithSecure Sensor component and if it hasn't been uninstalled before installing Elements Agent, the installation of the Elements Agent version of the sensor will fail. 

    To solve the issue, you will need to run the WithSecure uninstallation tool to uninstall both Elements Agent and Elements MDR / Countercept. You need to restart the device after running the uninstallation tool, then you can try to install Elements Agent back to the device. 

     

     

    ---In case device has 3rd party agent type security---

    Example :MaLion Security Point (Intercom) 

    MaLion Security Point (Intercom) installs a Winsock LSP (MarFtpLsp.dll, pmilsp.dll). It is loaded into fshoster32.exe and breaks name resolution on the EDR sensor upload path (obusclient2 → fswinssl → WinSock). The sensor cannot submit data and is reported as disconnected.The Connectivity Tool uses WinHTTP, which does not go through the LSP the same way. A clean report therefore does not rule this issue out. Ruled out: product defect, licence, firewall or proxy, DNS or routing.

    How to confirm
    • fshoster32.exe process log shows MarFtpLsp.dll and pmilsp.dll loaded.
    • obus/client2.1.log shows Cannot resolve address and backing off.
    • ATP/submission.log shows continuous Unsuccessful submission and no Successful submission.
    Resolution
    1. Disable MaLion Security Point (do not just stop it) and reboot.
    2. Check that submission.log shows Successful submission and the backlog drains. The GUI can take up to about 1 hour to clear.
    3. Permanent fix: Have Intercom or the partner exempt the whole WithSecure installation folder in MaLion, not just fshoster32.exe. Other Elements Agent processes use the same path, and process names can change between versions.
    4. Check that the subscription is valid.

    Do not leave MaLion disabled permanently. 

Endpoint Protection

  • Elements Endpoint Protection Agent's WithSecure Plugin Hosting Service is causing high CPU usage

    Read more
    Issue:

    I am noticing high CPU usage by WithSecure Plugin Hosting Service in Windows host installed with Elements Endpoint Protection, why is this happening? It is slowing down the performance of the device. 

    Resolution:

    When WithSecure plugin hosting service is using high amounts of CPU performance and disk resources, it is an indication that: 

    • A scheduled or manual scan is currently running and it is scanning the files
    • Real-time scanning scanning files that are accessed by the system 

    If you want to confirm if a scheduled or manual scan is running, you can check from the Task Manager's Details tab if the fsscan.exe process is running. If it is, then a scheduled or manual scan is currently running and that is causing high CPU and RAM usage, especially if you have scanning of compressed files (archives) enabled in the Elements profile. 

    To change the scheduled and manual scanning settings:

    1. Log in to the Elements Security Center portal
    2. Navigate to the Security configurations > Profiles page
    3. Click on the profile that is in use on the devices 
    4. Go to the Manual scanning settings page

    Here you can find separate sections for scheduled scanning and manual scanning settings. To decrease the CPU usage during scans, you can:

    • Enable Run scanning as low priority
    • Disable Scan inside compressed files
    • Enable Scan only known file types during scheduled scanning

    To stop or cancel a scheduled scan, you can follow these steps:

    1. Open the WithSecure client's user interface
    2. Click on the three dots and select Recent events 
    3. Click on the Cancel button on the right side of the ongoing scheduled scanning event

     

    If the issue is not caused by a manual or scheduled scan, it could be that real-time scanning is scanning some files for a very long time or very frequently. If you collect a wsdiag diagnostic file from the device, you can check the fa.log (frequently accessed) log file from the path wsdiag.zip\f-secure\logs\system\FSAV\. 

    Here is an explanation of the columns in the fa.log:

    • First column: 1 means scan was longer than usual. 2 means file was scanned frequently
    • Second column: how many milliseconds the last scan took and if file has been scanned frequently, How many milliseconds in total has been spent scanning the file
    • Third column: How many times the file has been scanned 
    • Fourth column: Date and time of last scan
    • Seventh column: path to the file

    You can use the information in the fa.log to create real-time scanning exclusions in the device settings. 

    High CPU usage can also happen if Security Cloud is either disabled or it doesn't have proper network connectivity. To check the network connectivity, run the WithSecure Connectivity Tool from the product's installation folder: 

    • Elements EPP for Computers/Elements EPP for Servers: C:\Program Files (x86)\F-Secure\PSB\ui\wsconnectionchecker.exe

    If Security Cloud is disabled, you can enable it from the Elements profile from the Real-time scanning settings page, with the Upload suspicious samples to WithSecure Security Cloud setting. You can select from the drop-down menu either Upload all suspicious files or Upload suspicious executables only to enable Security Cloud. 

    If the high CPU usage appears on a Terminal Server:

    If fshoster32.exe causes high CPU usage on a Terminal server, we propose to disable the Elements Agent's local user interface:

    1. Log in to the Elements Security Center
    2. Navigate to the Security configurations > Profiles page
    3. Open the server profile 
    4. Go to the General settings page
    5. Disable Show user interface to clients 
    6. Click Save profile
  • High memory (ram) and / or CPU usage by fsulprothoster.exe on a Windows Server

    Read more
    Issue:

    High memory (RAM) and / or CPU usage by fsulprothoster.exe on a Windows Server. Performance is slow on a Windows Server after installing Elements Endpoint Protection Agent. 

    Resolution:

    When fsulprothoster.exe is using a lot of CPU resources, it is an indication that: 

    • A scheduled or manual scan is currently running and it is scanning the files
    • Real-time scanning scanning files that are accessed by the system 

    If you want to confirm if a scheduled or manual scan is running, you can check from the Task Manager's Details tab if the fsscan.exe process is running. If it is, then a scheduled or manual scan is currently running and that is causing high CPU and RAM usage, especially if you have scanning of compressed files (archives) enabled in the Elements profile. 

    To change the scheduled and manual scanning settings:

    1. Log in to the Elements Security Center portal
    2. Navigate to the Security configurations > Profiles page
    3. Click on the profile that is in use on the devices 
    4. Go to the Manual scanning settings page

    Here you can find separate sections for scheduled scanning and manual scanning settings. To decrease the CPU usage during scans, you can:

    • Enable Run scanning as low priority
    • Disable Scan inside compressed files
    • Enable Scan only known file types during scheduled scanning

     

    If you have for example a large MS SQL database or Oracle on a server, try to make both real-time scanning and manual scanning exclusions for their folders. We recommend to follow Microsoft's instructions on what to exclude: Configure antivirus software to work with SQL Server - SQL Server | Microsoft Learn 

    How to create a Real-time scanning exclusion in an Elements profile:

    1. Log in to the Elements portal 
    2. Navigate to the Security configurations > Profiles page
    3. Open the profile that is in use on the device
    4. Go to the Real-time scanning settings page
    5. Enable Allow to exclude objects 
    6. Click Add exclusion and the folder or file path
    7. Click Save profile 

    To create a Manual scanning (scheduled scan) exclusion in an Elements profile:

    1. Log in to the Elements portal 
    2. Navigate to the Security configurations > Profiles page
    3. Open the profile that is in use on the device
    4. Go to the Manual scanning page
    5. Enable Excluded objects 
    6. Click Add exclusion and enter the folder or file path
    7. Click Save profile 

    If you have on the server any processes that interacts with a large amount of files, you can try to create a process exclusion for that process. 

    How to create a process exclusion for Elements Endpoint Protection (Elements EPP for Computers and Elements EPP for Servers):

    1. Log in to the Elements Security Center at https://elements.withsecure.com
    2. Select Security Configurations
    3. Go to the Profiles page
    4. Select the profile you want to edit
    5. Go to the Real-time scanning settings page
    6. Scroll down to the Excluded processes section and turn it on
    7. Click Add exclusion
    8. Add the full path to the process in the Excluded processes field
    9. Click Save profile
  • Error: "Failed to clone profile" when trying to copy profile to another account in Elements portal

    Read more
    Issue:

    Error: "Failed to clone profile" is shown when trying to use the "copy profile to another account" feature on the Elements Security Center portal's Security configurations > Profiles page. 

    Resolution:

    If you receive the "Failed to clone profile." error when trying to copy a profile to another account in the Elements portal, you can try using these workarounds.

    If you are a partner user, instead of copying the profile directly from company to company, copy the profile through the Solution Provider (SOP) or a Service Provider (SEP) level:

    1. Log in to the Elements Security Center portal
    2. Navigate to the Security configurations > Profiles page
    3. Click on the three dots on the right side of the profile
    4. Click Copy profile to another account
    5. As the Destination company, select a Solution Provider or Service Provider account
    6. Enter a name for the profile and click Copy profile to another account
    7. Go to the SOP or SEP level and then click on the three dots on the right side of the newly copied profile and perform the same steps, but now select a customer company account as the destination company

    Another workaround would be to use the profile export and import features in the Elements Security Center portal. To export a profile as a .json file, open a profile and then click on the three dots and click Export profile. Then you can go to the another company account, click Create a profile, click on the three dots and select Import profile. 

Identity Security

  • Error "Cannot validate argument on parameter" when updating Azure Entra ID Identity script

    Read more
    Issue:

    Error when updating Azure Entra ID Identity script;

    "ERROR during Azure deployment: Cannot validate argument on parameter 'Tenant'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again.
    Collecting information on failed deployments..."

    Resolution:

    Do make sure that any older or previous script is removed before running a newer script.

     

    1. Go to Azure and open the Cloud Shell
    2. Cleanup the old script files from their Azure shell using rm -r withsecure
    3. Upload the new script to the shell and unzip it
    4. Change directory to the withsecure folder using cd withsecure
    5. execute the update command: ./deploy.ps1 -update $true

Exposure Management

View all
  • Exposure Management agent-based scans fail in WSUS-only environments after upgrading to Elements Agent 26.4 showing XM Agent status as "Enabled with errors"

    Read more
    Issue:
    After upgrading endpoints to WithSecure Elements Agent 26.4, Elements Exposure Management (XM) agent-based vulnerability scans may fail in environments where Windows devices are configured to use WSUS only and are not allowed to connect directly to Microsoft Update.
    When the issue occurs, the XM Agent status in Elements Security Center is displayed as "Enabled with errors".
     

    Resolution:
    The issue occurs because the Elements Agent attempts to query Microsoft Update directly. In environments where direct access to Microsoft Update is blocked by network or organizational policy, this can prevent the XM agent-based scan from completing successfully.

    If you check the local logfile on the affected system C:\ProgramData\F-Secure\NS\default\Log\Radar\wsradartools.log to confim the issue. If the issue is due to blocked access to Microsoft Update, the following error is visible in the log file:

    2026-11-09 23:59:53.901 [0870.0006] *E: Radar.SystemCollector.Modes.Implementation.Windows.ReaMode: WithSecure Elements VM/XM System Collector execution has failed. Radar.SystemCollector.CustomExceptions.MissingUpdatesInfoCollectorException: Missing updates searching has failed. ---> System.Runtime.InteropServices.COMException: Exception from HRESULT: 0x80072EFE
       at WUApiLib.IUpdateSearcher.Search(String criteria)
       at Radar.SystemCollector.Utilities.WuaLib.Implementation.UpdateSearcherWrapper.GetSelectedUpdates(String criteria)
       --- End of inner exception stack trace ---

     

    This issue will be addressed in an upcoming update for Elements Agent.

    WithSecure Changelogs can be accessed here: Changelogs - WithSecure™ 

     

  • Error: "No access rights - You do not have rights to Vulnerability Management content of this organization." when trying to access Exposure Management pages in Elements portal

    Read more
    Issue:

    When trying to access Elements Exposure Management related pages in the Elements Security Center portal, I receive the error: "No access rights - You do not have rights to Vulnerability Management content of this organization.".

    The Security Configurations > Scans and Scan Templates pages are locked and the error is shown when they are clicked. 

    Resolution:

    If you receive the "No access rights - You do not have rights to Vulnerability Management content of this organization." error when trying to access Elements Exposure Management related pages in the Elements portal, make sure you that have a valid Elements Exposure Management subscription and also check that your user account has the following access rights (roles):

    • Exposure Management - Exposure: Full editing
    • Exposure Management - Vulnerabilities: Team member / Management

    The access rights can be checked by following these steps:

    1. Log in to the Elements Security Center portal: https://elements.withsecure.com
    2. Navigate to the Management > Organization Settings > Security Administrators page
    3. Click on the user's email address
    4. Check that the user has both enabled:
      1. Exposure - Full Editing
      2. Vulnerabilities - Management or Team member
    5. Click Close 

    If rights are missing, then the rights can be added by another administrator who has Elements Administration - Identity and Access Management role. If you are a customer company and you do not have any colleagues with Identity and Access Management rights, contact your WithSecure partner and they can grant you the access rights for Elements Exposure Management. 

    If you are partner, check if the error only occurs when selecting a specific company from the scope-selector drop-down menu. 

    If you have the access rights but still receive "No access rights - You do not have rights to Vulnerability Management content of this organization." error when trying to access Elements Exposure Management pages, ensure that you have valid subscription for Elements Exposure Management. If you have an expired commercial or trial subscription for Elements Exposure Management but you still have Elements Exposure Management access rights, you will receive "No access rights - Failed to fetch" errors when you try to access pages meant for Elements Exposure Management.

    You can check the validity of your Elements Exposure Management subscription from the Management > Subscriptions page in the Elements portal

  • "No access rights - Failed to fetch" errors when trying to access the Elements Exposure Management pages in Elements portal

    Read more
    Issue:

    I receive multiple "No access rights - Failed to fetch" errors when trying to access the Elements Exposure Management pages in Elements portal. For example, when accessing Security configurations > Scans pages (Discovery scans, Network Scans or Scan nodes), the one or more of the following errors are shown:

    • No access rights - Failed to fetch saved filters
    • No access rights - Failed to fetch authentication context
    • No access rights - Failed to fetch scan group
    • No access rights - Failed to fetch tags
    • No access rights - Failed to fetch scan nodes
    • No access rights - Failed to fetch scan templates
    • No access rights - Failed to fetch discovery scans
    • No access rights - Failed to fetch discovery scans summary
    Resolution:

    If you receive "No access rights - Failed to fetch" errors when trying to access Elements Exposure Management related pages in the Elements Security Center portal, first make sure that you have a valid Elements Exposure Management subscription. If you have an expired commercial or trial subscription for Elements Exposure Management but you still have Elements Exposure Management access rights, you will receive "No access rights - Failed to fetch" errors when you try to access pages meant for Elements Exposure Management.

    You can check it from the Management > Subscriptions page. 

     

    If you have a valid subscription, then the issue can be caused by broken Elements Exposure Management access rights. The issue can be fixed if you yourself have Elements Administration - Identity and Access Management (IAM) rights or by another administrator with IAM access rights:

    1. Log in to the Elements Security Center portal
    2. Navigate to the Management > Organization Settings > Security administrators page
    3. Click on the user's email address who is having the issue
    4. Change Exposure Management - Exposure to No access and click Save
    5. Change the rights back to the original value and click Save
    6. Change Exposure Management - Vulnerabilities to No access and click Save
    7. Change the rights back to the original value and click Save
    8. Click Close

    IMPORTANT: User needs to wait 20 minutes after the rights have been re-added for them to be fully in use. Log out from the Elements portal, wait for 20 minutes and the log back in. 

  • How to exclude subdomain from being scanned by Elements Exposure Management Web Scan?

    Read more
    Issue:

    How to exclude subdomain from being scanned by Elements Exposure Management Web Scan? We want to block the scan for accessing specific sub-domain URL. 

    Resolution:

    If you want to exclude or block the Elements Exposure Management Web Scan from accessing a subdomain, you can enter the subdomain that you want to exclude or block in the Scan access rules section in your Web Scan Template.

    The Scan access rules can be used to control which part of the application the scanner is allowed or not allowed to access. Rules can be specified as an URL, regular expression or external regular expression. Access to domains different than a target domain is blocked by default. You can allow access to URL in different domain by specifying allow access URL rule or external regular expression rule. External regular expression rules are interpreted in the context of the URL specified in the rule. Regular expression rules work only in relation to target domain.

    Steps to add a scan access rule in the Web Scan template:

    1. Log in to the Elements Security Center portal
    2. Navigate to the Security configurations > Scan templates page
    3. Go to the Network scan templates tab
    4. Click Add web scan template or modify existing template
    5. In the Scan settings step, scroll down to the Scan access rules section
    6. Select Block from the drop-down menu and enter one of the following:
      1. Url
      2. Regular Expression
      3. External Regular Expression
    7. Click Finish
  • Elements Exposure Management Network scan stuck at "Running" status for more than 24 hours

    Read more
    Issue:

    Elements Exposure Management Network scan (system scan) stuck at "Running" status for more than 24 hours

    Resolution:

    If you are using you own internal Elements Exposure Management Scan node and scans are stuck in "running" status for a very long time, we recommend to make sure that the scan node has enough processor (CPU) performance, memory (RAM) and disk space available. 

     

    Scanning multiple scan targets at a time is a very resource heavy task, so if scans take a long time, we recommend to check that the server is up to the task. 

     

    You can from the scan group settings adjust how many scan targets are scanned simultaneously. This can improve scan performance in cases where system resources are at their limit on a scan node server:

    1. Log in to the Elements Security Center portal 
    2. Navigate to the Security configurations > Scans > Network scans page
    3. Click on the three dots for a scan group and click Edit scan group
    4. In the Group details section, modify the Max system scans value to a smaller amount.

     

    To check if the issue is caused by a lack of resources, you can start a network scan for one scan target. If the network scan goes through faster on one scan target, then the issue is with the scan nodes resources. 

Common Topics

View all
  • How to request access to the eService portal?

    Read more
    Issue:

    How to request access to the eService portal?

    Resolution:

    Note: eService access is only for customers who have Advanced or Premium support contracts.

    To gain access to the eService portal, please request a user account by sending an email request to support-service-registration@withsecure.com

    In the email, add the following details:

    • first name
    • last name
    • email address
    • phone number (international format)

    Note: Once your access request is processed, you will receive a Welcome Email to the WithSecure™eService Portal. If you have an existing WithSecure™Business Account, you can log in to the WithSecure™eService Portal by using your WithSecure™Business Account credentials.

    If you do not have a WithSecure™Business Account, we have already created one for you when processing your access request. Do the following:

    • Find the WithSecure™Business Account validation email in your inbox and activate your Business Account
    • Reset your password from the WithSecure™eService Portal login page (“Forgot your password? link), after selecting “Business Account Login” on the eService Portal’s landing page.
  • How to add a new user to the eService portal as existing Admin user

    Read more
    Issue:

    How to add a new user to the eService portal as existing Admin user

    Resolution:

    If you are an existing Admin User in your eService portal, you can grant access to your colleagues by adding them as new users. To add a new eService user, follow the steps:

    1. Sign in to the WithSecure eService portal.
    2. From the top navigation menu, select User Management.
    3. Under Manage Members, select Add Member, then click Next.
    4. Enter the required details for the new user.
    5. Choose whether the user should have Admin User permissions or not.
    6. Choose whether the user should be Active or not.
    7. Click Save to create the user and grant them access to the eService portal.
  • Where can I find the list of supported products for WithSecure Software Updater?

    Read more
    Issue:

    How to check for which software WithSecure Software Updater offers patches? Is there a list of supported vendors for WithSecure Softeware Updater? 

     

     

    Resolution:

    You can find the list of supported products for which WithSecure Software Updater feature offers patches by clicking here: Vendors included in WithSecure Software Updater - WithSecure™

Business Suite

View all
  • Business Suite Client Security or Server Security WithSecure Plugin Hosting Service is causing high CPU usage

    Read more
    Issue:

    I am noticing high CPU usage by WithSecure Plugin Hosting Service in Windows host installed with Business Suite Client Security or Server Security, why is this happening? It is slowing down the performance of the device. 

    Resolution:

    When WithSecure plugin hosting service is using high amounts of CPU performance and disk resources, it is an indication that: 

    • A scheduled or manual scan is currently running and it is scanning the files
    • Real-time scanning scanning files that are accessed by the system 

    If you want to confirm if a scheduled or manual scan is running, you can check from the Task Manager's Details tab if the fsscan.exe process is running. If it is, then a scheduled or manual scan is currently running and that is causing high CPU and RAM usage, especially if you have scanning of compressed files (archives) enabled in the host's policy settings.

    To change the scheduled and manual scanning settings for Client Security or Server Security:

    1. Log in to the Policy Manager Console
    2. Select a host or policy domain from the domain tree
    3. Open the Settings tab
    4. Navigate to the Windows > Manual scanning settings page.

    Here you can find separate sections for scheduled scanning and manual scanning settings. To decrease the CPU usage during scans, you can:

    • Disable Scan inside compressed files
    • Enable Run scanning as low priority
    • Enable Scan only known file types 

    To stop or cancel a scheduled scan, you can follow these steps:

    1. Open the WithSecure client's user interface
    2. Click on the three dots and select Recent events 
    3. Click on the Cancel button on the right side of the ongoing scheduled scanning event
      • Note: the Allow users to skip scheduled scans setting must be enabled for a local user to be able to stop a scheduled scan

    If the issue is not caused by a manual or scheduled scan, it could be that real-time scanning is scanning some files for a very long time or very frequently. If you collect a wsdiag diagnostic file from the device, you can check the fa.log (frequently accessed) log file from the path wsdiag.zip\f-secure\logs\system\FSAV\. 

    Here is an explanation of the columns in the fa.log:

    • First column: 1 means scan was longer than usual. 2 means file was scanned frequently
    • Second column: how many milliseconds the last scan took and if file has been scanned frequently, How many milliseconds in total has been spent scanning the file
    • Third column: How many times the file has been scanned 
    • Fourth column: Date and time of last scan
    • Seventh column: path to the file

    You can use the information in the fa.log to create real-time scanning exclusions in the device settings. 

    High CPU usage can also happen if Security Cloud is either disabled or it doesn't have proper network connectivity. To check the network connectivity, run the WithSecure Connectivity Tool from the product's installation folder: 

    • Client Security: C:\Program Files (x86)\F-Secure\Client Security\ui\fsconnectionchecker.exe
    • Server Security: C:\Program Files (x86)\F-Secure\Server Security\ui\fsconnectionchecker.exe

    If Security Cloud is disabled, you can enable it from the policy settings:

    1. Log in to the Policy Manager Console
    2. Select a host or policy domain in the domain tree
    3. Open the Settings tab
    4. Navigate to the Windows > Real-time scanning settings page 
    5. Enable Use Security Cloud
    6. Distribute the policy (Ctrl + D)

    If the high CPU usage appears on a Terminal Server:

    If fshoster32.exe causes high CPU usage on a Terminal server, we propose to disable the local user interface for Server Security:

    1. Log in to the Policy Manager Console
    2.  Select a host or policy domain in the domain tree
    3. Open the Settings tab
    4. Navigate to the Windows > Centralized management settings page
    5. Scroll down to the Local user interface section
    6. Disable Show local user interface 
    7. Click Save profile

     

  • What is the expected behavior for Business Suite endpoint products after the license has expired?

    Read more
    Issue:

    What is the expected behavior for Business Suite endpoint products after the license has expired? 

    Resolution:

    Business Suite Policy Manager: 

    • Admin still have a grace period of 7 days to access Policy Manager Console and apply configuration changes. 

    Client Security and Server Security endpoint clients: 

    • Endpoints will keep receiving updates for the grace period and will stop receiving it after that.
    • Endpoint's security features will stop working right after the license expires, hence system will be unprotected. 

    Before the subscription expires, we recommend to allow local uninstallation in the policy settings, so that the Client Security or Server Security clients can be uninstalled even after the subscription has expired. 

  • How to collect installation trace logs for WithSecure Linux Protection and Linux Security 64

    Read more
    Issue:
    Sometimes WithSecure Linux Protection or Linux Security 64 installation and/or activation fails and additional trace logging is required to determine the root cause. This document describes how to generate the trace logs while uninstalling and reinstalling the product on the affected system.
     
    Resolution:

    To generate the logfiles, use these instructions. Perform them as root or while using sudo

     
    Remove Linux Protection completely 
     
    • RHEL-based distributions: rpm -e linuxsecurity-installer
    • Debian-based distributions: dpkg -r linuxsecurity-installer
    • rm -rf /opt/f-secure
    • rm -rf /etc/opt/f-secure
    • rm -rf /var/opt/f-secure
    If the device is still visible in the Elements Security Center portal, remove the device from the portal as well.
     
    Reinstall Linux Protection

    • RHEL-based distributions: rpm -Uvh linuxsecurity-installer.rpm 
    • Debian-based distributions: dpkg -i linuxsecurity-installer.deb 
    Enable setup tracing

    export FSECURE_TRACE_SETUP=.

     

    Activate Linux Protection while capturing the trace output:
    /opt/f-secure/linuxsecurity/bin/activate --psb --subscription-key <insert-your-key> id> 2>&1 | tee -a setup_trace.log

    When the issue reproduces, share the following information via the support ticket.

    1. The file setup_trace.log created above
    2. Freshly created fsdiag file created by running /opt/f-secure/linuxsecurity/bin/fsdiag․sh
    3. output from the terminal used to reinstall the product (copy/paste this into a file or the email) showing the failed installation including errors.

WithSecure Cloud Protection for Salesforce

View all
  • How to upgrade Cloud Protection for Salesforce and is there a rollback option ?

    Read more
    Issue:

    How to upgrade Cloud Protection for Salesforce? Is there any roll-back option available after upgrade to latest version so that incase if there is any issue with the new version then we can rollback to old version.

    Resolution:

    The latest version of the Cloud Protection for Salesforce solution is always available in Salesforce AppExchange. Upgrading preserves all existing settings and analytics data.

    WithSecure Cloud Protection is listed on Salesforce AppExchange here: https://appexchange.salesforce.com/listingDetail?listingId=a0N3A00000EFntJUAT.

    1. Log in to Salesforce with your System Administrator account.
    2. Go to the Salesforce AppExchange marketplace, find the WithSecure Cloud Protection application, and click "Get It Now" to start installation.
    3. Depending on whether you are installing the application to your production Salesforce org or Sandbox, choose Install in production or Install in Sandbox and agree to the terms and conditions.

    More details can be found here:

    Upgrading the application | Cloud Protection for Salesforce | Latest | WithSecure User Guides

    We suggest to try things out first on the Sandbox, then Production environment.

    We would prefer to fix any issues with the new version, rather than use the old one. Technically, it is possible to uninstall the new version and install the previous one, but that should be considered as the last resort.

  • How to download the latest version of WithSecure Cloud Protection for Salesforce?

    Read more
    Issue:

    How to download the latest version of WithSecure Cloud Protection for Salesforce?
     

    Resolution:

    The latest version of WithSecure Cloud Protection for Salesforce version can be downloaded from our product Downloads page.

  • How to increase the Scan Quota Increase in the Cloud Protection for Salesforce when getting Error monthly scan usage quota limits exceeded ?

    Read more
    Issue:

    How to increase the Scan Quota in Cloud Protection for Salesforce when getting error: "monthly scan usage quota limits exceeded" ?

    1. What’s the impact on the service when we hit the monthly scan quota limit?
    2. What are the options available to optimize the scan quota usage?
    Resolution:

    You are getting that email alert because they have reached the total monthly scan quota in your purchased license. 

    If you want it to be increased, then you have to contact your sales representative or WithSecure sales contact (account owner) to purchase more licenses.

    You may consider to optimize the scan quota usage as below:

    1. Currently there is no hard limits in Cloud Protection for Salesforce, so everything will still work after the total monthly scan quota limit has been reached. Having said that, there is still a need for you to consider on purchasing license to increase the monthly scan quota.
    2. In order to optimize the scan quota usage, you could consider to limit the scanned file extension, exclude certain file extensions and set how long you will trust the cache data. Apart from that, you could also consider to limit the licensed users and locations for the objects to be scanned (for example, selected objects only).

Other WithSecure Products

View all

Business Suite

  • Business Suite Client Security or Server Security WithSecure Plugin Hosting Service is causing high CPU usage

    Read more
    Issue:

    I am noticing high CPU usage by WithSecure Plugin Hosting Service in Windows host installed with Business Suite Client Security or Server Security, why is this happening? It is slowing down the performance of the device. 

    Resolution:

    When WithSecure plugin hosting service is using high amounts of CPU performance and disk resources, it is an indication that: 

    • A scheduled or manual scan is currently running and it is scanning the files
    • Real-time scanning scanning files that are accessed by the system 

    If you want to confirm if a scheduled or manual scan is running, you can check from the Task Manager's Details tab if the fsscan.exe process is running. If it is, then a scheduled or manual scan is currently running and that is causing high CPU and RAM usage, especially if you have scanning of compressed files (archives) enabled in the host's policy settings.

    To change the scheduled and manual scanning settings for Client Security or Server Security:

    1. Log in to the Policy Manager Console
    2. Select a host or policy domain from the domain tree
    3. Open the Settings tab
    4. Navigate to the Windows > Manual scanning settings page.

    Here you can find separate sections for scheduled scanning and manual scanning settings. To decrease the CPU usage during scans, you can:

    • Disable Scan inside compressed files
    • Enable Run scanning as low priority
    • Enable Scan only known file types 

    To stop or cancel a scheduled scan, you can follow these steps:

    1. Open the WithSecure client's user interface
    2. Click on the three dots and select Recent events 
    3. Click on the Cancel button on the right side of the ongoing scheduled scanning event
      • Note: the Allow users to skip scheduled scans setting must be enabled for a local user to be able to stop a scheduled scan

    If the issue is not caused by a manual or scheduled scan, it could be that real-time scanning is scanning some files for a very long time or very frequently. If you collect a wsdiag diagnostic file from the device, you can check the fa.log (frequently accessed) log file from the path wsdiag.zip\f-secure\logs\system\FSAV\. 

    Here is an explanation of the columns in the fa.log:

    • First column: 1 means scan was longer than usual. 2 means file was scanned frequently
    • Second column: how many milliseconds the last scan took and if file has been scanned frequently, How many milliseconds in total has been spent scanning the file
    • Third column: How many times the file has been scanned 
    • Fourth column: Date and time of last scan
    • Seventh column: path to the file

    You can use the information in the fa.log to create real-time scanning exclusions in the device settings. 

    High CPU usage can also happen if Security Cloud is either disabled or it doesn't have proper network connectivity. To check the network connectivity, run the WithSecure Connectivity Tool from the product's installation folder: 

    • Client Security: C:\Program Files (x86)\F-Secure\Client Security\ui\fsconnectionchecker.exe
    • Server Security: C:\Program Files (x86)\F-Secure\Server Security\ui\fsconnectionchecker.exe

    If Security Cloud is disabled, you can enable it from the policy settings:

    1. Log in to the Policy Manager Console
    2. Select a host or policy domain in the domain tree
    3. Open the Settings tab
    4. Navigate to the Windows > Real-time scanning settings page 
    5. Enable Use Security Cloud
    6. Distribute the policy (Ctrl + D)

    If the high CPU usage appears on a Terminal Server:

    If fshoster32.exe causes high CPU usage on a Terminal server, we propose to disable the local user interface for Server Security:

    1. Log in to the Policy Manager Console
    2.  Select a host or policy domain in the domain tree
    3. Open the Settings tab
    4. Navigate to the Windows > Centralized management settings page
    5. Scroll down to the Local user interface section
    6. Disable Show local user interface 
    7. Click Save profile