Collaboration Protection
-
Elements Collaboration Protection pages show "Organization is not available" in the Elements portal
Read more
Issue:
When trying to access a customer company's Elements Collaboration Protection related pages in the Elements Security Center portal as a reseller partner user, it gives the error "Organization is not available - Selected organization '<organization id>' is not available. Please select an organization you have access to."
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:
- Log in to the Elements Security Center portal
- Navigate to the Collaboration Protection > policies page
- Open the policy that is in use on your cloud service
- Go to the Exchange > Malware
- Untick the Notify the user about detections with the following severities:
- 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:
- Log in to the Elements Security Center portal
- Navigate to the Collaboration Protection > policies page
- Open the policy that is in use on your cloud service
- Go to the Exchange > URL scanning page
- Untick Notify the user about detections with the following severities under both Malicious URL and Suspicious URL
- 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:
- Log in to the Elements Security Center portal
- Navigate to the Collaboration Protection > policies page
- Open the policy that is in use on your cloud service
- Go to the Exchange > Compromised accounts page
- Untick Notify the user about detections with the following severities
- Click Save
If you only want to not send user notifications based on the severity of the alert:
- Log in to the Elements Security Center portal
- Navigate to the Collaboration Protection > policies page
- Open the policy that is in use on your cloud service
- Go to the General > Notifications page
- From the User notifications based on severity, select the desired severity level that triggers a user notification:
- All (Low, Medium, High & Critical)
- Medium, High & Critical
- High & Critical
- Critical
- Click Save
Endpoint Detection and Response
-
Is it possible to forward events from Elements Endpoint Detection and Response to SIEM (Security information and event management) ?
Read more
Issue:
Is it possible to forward events from Elements Endpoint Detection and Response (EDR) to SIEM (Security information and event management) ?
Resolution:
Yes, it is possible to forward all kinds of Endpoint Detection and Response (EDR) security events to SIEM. WithSecure offers many different options:
- Elements Connector can be deployed in a security events forwarder role to pull data from WithSecure™ Elements and forward it to almost any SIEM using Syslog, Common Event Format (CEF) or Log Event Extended Format (LEEF). Elements Connector is fully managed from the WithSecure™ Elements Security Center. You can configure the forwarding feature for the whole partner scope or limit it to a certain company.
- Elements API - Manage security features in the Elements platform through API calls instead of using the Elements Security Center portal — ideal for automation, reporting, and integrating with your internal systems.
- SIEM integration to forward events to your SIEM to centralize visibility and automate response.
You can find all information about all of these from here: WithSecure™ Connect
-
Getting 'No access rights' when accessing Broad Context Detections page in Elements portal
Read more
Issue:
User is unable to access the Events > Broad Context Detections page in the Elements portal and they receive the "No access rights".
Resolution:
Make sure that you have Extended Detection and Response access rights role on your user account:
- Log in to the Elements Security Center portal
- Navigate to the Management > Organization settings > Security Administrators page
- View the Extended Detection and Response column and check that you have rights for:
- Event Search
- Broad Context Detections
- Response
If you do not have these three rows visible, please ask another administrator or your WithSecure partner to add the access rights:
- Log in to the Elements portal
- Navigate to the Management > Organization settings > Security Administrators page
- Click on the user's email address
- Enable Extended Detection and Response role
- Select which access right the user should have for
- Event Search
- Broad Context Detections
- Response
- Click Save
-
How to to create a customized email report on security events to receive alerts for Elements Endpoint Detection and Response?
Read more
Issue:
How to to create a customized email report on security events to receive alerts for Elements Endpoint Detection and Response (EDR) Broad Context Detections (BCDs)? I want to receive alert emails for only specific risk or severity levels.
Resolution:
In the Elements Security Center portal, using the Email notification and report feature under Reports, you can create and automatically send customized Elements Endpoint Detection and Response Broad Context Detection email reports. This can be used to only send alert emails for specific risk levels.
First you need to create a custom view on the Events > Security Events page which only lists
To create a custom view:
- Log in to the Elements Security Center portal
- Navigate to the Events > Security Events page
- Create a filter where the source = EDR and then where severity = either Action needed or Attention
Note: "High" and "severe" broad context detections have the "Action needed" severity level and "medium" broad context detections have the "Attention" severity level.
- Open the View drop-down menu in the top-right corner.
- Select Save as and enter a name for your custom view.
- Select Save. The custom view appears under My views.
After creating the custom view, you can now create an email report on security events.
- Select Reports on the sidebar.
- On the Reports page, select the Email notification and report tab.
- Select Add email report.
- The Add new email report pane opens.
- Enter a name for the report.
- From the Data source drop-down menu, select Security Events.
- From the Template drop-down menu, select the template that you previously created on the Security Events page.
- Select your preferred language for the report.
- Under Schedule, the frequency for reports on security events is continuous, which means that a new report is sent every ten minutes.
- Note: The initial report that is generated shows data from last 24 hours. Subsequent reports show data from last ten minutes.
- The Send only when report has content option is on by default. If you turn it off, you will receive reports every 10 minutes even when there are no new events.
- Note: No test report will be sent if no new detections have appeared in the last 10 minutes.
- In the Recipients box, enter the email addresses of the recipients to whom you want to deliver the reports
- Note: If you have multiple email addresses, use comma to separate them.
- Select Save.
Endpoint Protection
-
Elements portal shows BitLocker recovery keys collection is disabled
Read more
Issue:
For one of more devices the "BitLocker recovery key collection is enabled" status is shown as Disabled in the Elements Security Center portal.
Why can the BitLocker recovery key collection status be disabled even if BitLocker has been enabled on the devices?
Resolution:
The Elements Security Center portal will show "Bitlocker recovery key collection" status as disabled if you haven't enabled BitLocker recovery key collection from the Elements profile that is in use on the devices. Even if you have BitLocker enabled on the devices, you still need to configure the Elements profile so that the Elements portal collects the recovery keys.To enable Bitlocker recovery key collection in the Elements Portal, refer to the below steps:- Login to the Elements Security Center https://elements.withsecure.com
- Navigate to the Security Configurations > Profiles page
- Click profile used on the devices where Bitlocker recovery key collection needs to be enabled
- Go to the General settings page
- Scroll to the BitLocker management section
- Enable the setting Collect BitLocker recovery keys
- Click Save profile
Once you have enabled the Collect BitLocker recovery keys feature from the Elements profile, select your devices from the Environment > Devices list and send a Send full status operation to the devices to immediately receive full status updates from all the devices. Then check the BitLocker recovery key collection status again. -
The device appears in both the Devices and Unmanaged Devices lists in the Elements portal
Read more
Issue:
Why does a device still appear in the Elements Security Center portal's Unmanaged devices list even after the Elements Agent has been installed on a device?
Resolution:
If you have removed and reinstalled the Elements Agent, you need to verify whether the device UUIDs remain the same. The Elements backend treats any device with a different UUID as a new device.
If the UUIDs are unchanged, you will need to perform a new unmanaged devices scan. Once completed, you can use the “Latest AD Scan Results” view to filter and display only the devices detected in the most recent scan. This ensures that devices where the agent was previously installed but are no longer found in scans will not appear in the list.
Note: Devices from previous AD scans are not automatically removed from the Unmanaged devices list. This is the reason you need to use the Last AD Scan Results view if you want to see only the devices which were found during the last AD scan.
To perform an Unmanaged devices scan,
- Log in to the Elements Security Center portal
- Navigate to the Environment > Devices page
- Open the Unmanaged devices tab
- Click on the three dots and select Unmanaged devices scan
- Select a device to use for the unmanaged devices scan and if needed, can also activate daily scans.
-
How to create an AMSI exclusion for Elements Endpoint Protection?
Read more
Issue:
How to create an AMSI exclusion for Elements Endpoint Protection?
Should AMSI (Antimalware Scan Interface) detection be excluded with a Global exclusion or real-time scanning exclusion?
Resolution:
If you have received an AMSI detection, it cannot be excluded using a Global exclusion or a real-time scanning exclusion.
If you want to exclude an AMSI detection, only a process exclusion will bypass AMSI detection.
How to create a process exclusion for Elements Endpoint Protection (Elements EPP for Computers and Elements EPP for Servers):
- Log in to the Elements Security Center at https://elements.withsecure.com
- Select Security Configurations
- Go to the Profiles page
- Select the profile you want to edit
- Go to the Real-time scanning settings page
- Scroll down to the Excluded processes section and turn it on
- Click Add exclusion
- Add the full path to the process in the Excluded processes field
- Click Save 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.
- Go to Azure and open the Cloud Shell
- Cleanup the old script files from their Azure shell using rm -r withsecure
- Upload the new script to the shell and unzip it
- Change directory to the withsecure folder using cd withsecure
- execute the update command: ./deploy.ps1 -update $true
-
Why is an Operating System flagged as End of Life (EOL) by Elements Exposure Management even if we have Extended Support?
Read more
Issue:
We are seeing a Windows Server 2019 system flagged as "End of Life" by Elements Exposure Management in the Elements Security Center Portal's Environment > Exposure page even though we have an Extended Support contract from Microsoft. Why is this happening?
Resolution:
This behavior is expected based on how our scanner evaluates operating systems.
Our scanners rely on publicly available security advisories and bulletins to determine the support status of a product. These sources typically report the official end of support (EOL) for an OS, without considering any individual extended support agreements that customers may have in place.
Because we cannot retrieve or validate customer-specific support contracts at the OS level, systems that have technically reached the official EOL date are marked accordingly in the portal - even if they are still under extended vendor support.
If the system is still supported via a valid extended support agreement and you are aware of the situation, we recommend classifying the finding as one of the following:
- Accepted Risk
- False Positive
-
No access rights to Elements Exposure Management pages in Elements portal after getting a trial license
Read more
Issue:
After receiving a trial subscription key for Elements Exposure Management, user gets "no access rights" error when trying to access the Elements Exposure Management related pages in the Elements Security Center portal. For example, unable to access the following sections in the Elements portal:
- Environment > Exposure
- Security Configurations > Scans
- Security Configurations > Scan Templates
Resolution:
The Exposure Management - Exposure rights are not granted automatically for either partners or end-customer companies even if a customer has Exposure Management - Users and Cloud subscriptions.
If you have a admin user who has Elements Administration - Identity and Access Management rights, they can add to themselves and other administrators the necessary Exposure Management - Exposure and Exposure Management - Vulnerabilities access rights so that you can access the Exposure Management related pages in the Elements Security Center portal.
How to check if an administrator has Elements Administration - Identity and Access Management rights:
- Log in to the Elements Security Center portal
- Navigate to the Management > Organization Settings > Security administrators page
- View the Elements Administration column and check if any user has Identity and Access Management access rights
If there is a user you has the rights, they can add the necessary Exposure Management rights by clicking a user's email address and then adding the Exposure Management - Exposure and Exposure Management - Vulnerabilities access rights.
If no user has Identity and Access Management, you need to contact your WithSecure partner and they can grant you the necessary access rights to be able to access Elements Exposure Management related product pages in the Elements Security Center portal.
-
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: 0x80072EFEat 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:
- Log in to the Elements Security Center portal: https://elements.withsecure.com
- Navigate to the Management > Organization Settings > Security Administrators page
- Click on the user's email address
- Check that the user has both enabled:
- Exposure - Full Editing
- Vulnerabilities - Management or Team member
- 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:
- Log in to the Elements Security Center portal
- Navigate to the Management > Organization Settings > Security administrators page
- Click on the user's email address who is having the issue
- Change Exposure Management - Exposure to No access and click Save
- Change the rights back to the original value and click Save
- Change Exposure Management - Vulnerabilities to No access and click Save
- Change the rights back to the original value and click Save
- 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.
-
When will WithSecure business products stop supporting Windows Server 2012/2012R2 Operating Systems?
Read more
Issue:
Windows Server 2012 / 2012R2 EOL (End-of-life)
Resolution:
Both Elements Endpoint Protection for Servers and Business Suite Server Security no longer support Windows Server 2012 / 2012R2 since Microsoft also stopped supporting these operating systems back in October 2023: Windows Server 2012/R2 reaches end of support | Azure updates | Microsoft Azure
You can find the Elements Endpoint Protection for Servers system requirements here: System requirements | Elements Endpoint Protection for Servers | Latest | WithSecure User Guides
You can find the Business Suite Server Security system requirements here: System requirements | Server Security | 16.00 | WithSecure User Guides
-
How to change multi-factor authentication (MFA) type
Read more
Issue:
How can we change the multi-factor authentication (MFA) / two-factor authentication (2FA) type that is used when logging in to Elements Security Center portal, Partner Portal or eService portal?
I want to change my two-factor authentication settings.
Resolution:
Even for users with only Partner Portal and eService portal access rights, the Multi-factor authentication (MFA) settings are changed from the Elements Security Center portal.
To change the multi-factor authentication (MFA) settings follow these steps:
- Log in to the Elements Security Center portal: https://elements.withsecure.com
- After you have logged in, click on the profile icon in the top-right hand corner and select My settings
- Click on the Change button on the right side of the Multi-Factor Authentication enabled text
Here you can remove or add multi-factor authentication methods. You can enable several methods simultaneously so that during login you can choose the MFA type.
If you have an authenticator application in use and you want to move the authenticator application to a new phone, you can remove your current authenticator from Elements portal's multi-factor authentication settings page and then immediately configure a new authenticator.
-
What are the recommended or best practice exclusions for WithSecure product installed on a Windows Server?
Read more
Issue:
What are the recommended or best practice exclusions for WithSecure products (Business Suite Server Security or Elements Endpoint Protection for Servers) installed on a Windows Server?
Resolution:
We recommend to check the list of recommended scanning exclusions from Microsoft's articles:
- https://support.microsoft.com/en-us/topic/virus-scanning-recommendations-for-enterprise-computers-that-are-running-windows-or-windows-server-kb822158-c067a732-f24a-9079-d240-3733e39b40bc
- https://learn.microsoft.com/en-us/microsoft-365/security/defender-endpoint/configure-server-exclusions-microsoft-defender-antivirus?view=o365-worldwide
For SQL
For IIS
For Exchange
WithSecure products do not perform any kind of Windows Server role check to create any kind of default exclusions based on that information.
-
Policy Manager Server Address and HTTP / HTTPS ports are grayed out when creating MSI installer in Policy Manager Console
Read more
Issue:
When admin is creating or exporting an MSI installer in the Policy Manager Console, they are unable to enter the values to the Policy Manager Server address, HTTP and HTTPS ports fields because they are greyed out.
Resolution:
It is normal that the Policy Manager Server address, HTTP and HTTPS ports are grayed out when exporting or creating an MSI installation package in the Policy Manager Console. The address needs to be defined in the domain policy settings before proceeding with exporting the installation package.
- Open the Policy Manager Console
- Select Root from the policy domain tree
- Go to the Settings tab
- Go to Windows > Centralized Management
- Fill the details of your Policy Manager Server Address, HTTP and HTTPS ports
- Distribute the policy (Ctrl + D)
Now you can go back to the Installation tab to export the MSI installation package.
-
How to create an AMSI exclusion for Client Security or Server Security?
Read more
Issue:
How to create an AMSI exclusion for Business Suite Client Security or Server Security?
Should AMSI (Antimalware Scan Interface) detection be excluded with an All scans or real-time scanning exclusion?
Resolution:
If you have received an AMSI detection, it cannot be excluded using an all scans or a real-time scanning exclusion.
If you want to exclude an AMSI detection, only a process exclusion will bypass AMSI detection.
How to create a process exclusion for Business Suite Client Security or Server Security:
- Log in to the Policy Manager Console
- Select a host or policy domain from the Domain Tree
- Go to the Settings tab
- Go to the Real-time scanning settings page
- Scroll down to the Processes excluded from scanning to optimize disk performance section
- Enable Do not scan the following processes
- Add the full path to the process in the Excluded processes list
- Distribute the policy (Ctrl + D)
-
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 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.
Business Suite
-
Policy Manager Server Address and HTTP / HTTPS ports are grayed out when creating MSI installer in Policy Manager Console
Read more
Issue:
When admin is creating or exporting an MSI installer in the Policy Manager Console, they are unable to enter the values to the Policy Manager Server address, HTTP and HTTPS ports fields because they are greyed out.
Resolution:
It is normal that the Policy Manager Server address, HTTP and HTTPS ports are grayed out when exporting or creating an MSI installation package in the Policy Manager Console. The address needs to be defined in the domain policy settings before proceeding with exporting the installation package.
- Open the Policy Manager Console
- Select Root from the policy domain tree
- Go to the Settings tab
- Go to Windows > Centralized Management
- Fill the details of your Policy Manager Server Address, HTTP and HTTPS ports
- Distribute the policy (Ctrl + D)
Now you can go back to the Installation tab to export the MSI installation package.