Issue:

• I have added a site into the denied list for the Browsing Protection feature via the Elements Endpoint Protection portal Profile Editor. However, the site is not blocked with Browsing Protection enabled in the on the device using EPP for Computers or for Servers. Same goes to the allowed site. Why is this happening?
• Google's search results show the deny rating icon, but when user clicks the link it proceeds to the page.

Resolution:

Check from the Endpoint Protection profile you are using that the web site exceptions setting is enabled. If it is disabled the allowed sites and denied sites rules are not in use. 

Follow these steps to enable Web site exceptions:

1. Log in to the Elements portal: https://elements.withsecure.com
2. Open the Security configurations section from the menu on the left
3. Go to the Profiles page
4. Select the profile you want to edit
5. Go to the Browsing Protection tab
6. Scroll down until you see the Web site exceptions section and enable it
7. Click Save profile

Now the Web site exceptions in the allowed sites and denied sites lists are enabled.

If this does not fix the issue and you are certain that the correct exclusions have been created and the correct profile is in use on the device, try to reset the reputation cache from the local Elements Agent settings:

1. Right-click the Elements Agent icon
2. Click Open Settings 
3. Go to the Support tab
4. Click Reset reputation cache 

Note that resetting the reputation cache requires local administrator rights for the device. 

Issue:

Elements EPP for Servers or Linux Protection clients are showing a status of "Malware protection" as "No paths are protected" or "disabled" in the Elements Security Center portal's Environment > Devices page. 

Resolution:

Normally, this is "No paths are protected" Malware protection status is caused by the default policy with an empty configuration of "Files and folders to scan" being assigned to the WithSecure™ EPP Elements for Servers (Linux client) or Linux Protection clients.

In order to make the real-time scan work, there is a need to clone the default profile and add a path (for example, root directory of "/" for scanning all files) to that configuration in the profile.

You can perform the following steps to clone the default profile if it has not been done yet, change the configuration for real-time scanning, assign the cloned profile and trigger the full status update to solve this issue.

1. Log in to the Elements Security Center Portal 
2. Open the Security configurations section from the menu on the left
3. Go to the Profiles page
4. Click the three dots which are next to the profile you want to clone (WithSecure™ for Linux in this case)
5. Select Clone Profile
6. Enter a profile name (Label and description are optional)
7. Select Real-time scanning in the profile
8. Click on Add path under Files and folders to scan
9. Add root directory of "/" to scan all files 
10. Click Save profile

Once the profile has been created you can assign it to the Linux devices:

1. Go to the Devices tab
2. Select the affected Linux device
3. Click on Assign > Assign Profile
4. Select the cloned profile from the list
5. Click on Assign button

Now you can send a full status update:

1. On Devices tab, select the affected Linux device again
2. Choose Send full status update

If the default profile has been cloned before but the configurations for real time scanning are not changed yet, follow the steps below to solve the issue.

1. Log in to the Elements Security Center Portal 
2. Open the Security configurations section from the menu on the left
3. Go to the Profiles page
4. Open the assigned profile
5. Select Real-time scanning in the profile
6. Click on Add path under Files and folders to scan
7. Add root directory of "/" to scan all files 
8. Click Save and Publish
9. Go to the Devices tab
10. Select the affected Linux device
11. Choose Send full status update

Note: If setting this configuration does not fix the issue, try reinstalling Elements Linux Protection on the device. 

Issue:

Elements Connector unable to forward logs with error "Message too long".

Resolution:

This typically occurs when trying to send a UDP packet that exceeds the maximum allowed size.

UDP has a maximum payload size of 65,507 bytes (65,535 bytes total – 8 bytes for UDP header – 20 bytes for IP header). However, likely the SIEM system has some smaller limit. It’s recommended instead to use TCP protocol for the event forwarding. It’s overall more reliable. This can be configured in the Elements Connector’s profile.

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

Issue:

Error "Failed to fetch remove operations data" when trying to load a certain BCD ID. Only that specific BCD ID is displaying the error. Other BCDs have no issue.

Resolution:

Do check if the device linked to the problematic BCD is still in the device list, or has not been removed. As the reason this error could occur is possibly due to the Device no longer being listed.

Issue:

How to grant an administrator the Elements Administration – Identity and Access Management role?

Resolution:

The Elements Administration – Identity and Access Management (IAM) role can only be given by an administrator who already has the role. If your company does not have any users with the IAM role and you have a Partner Managed subscription, please contact your WithSecure partner and they can grant the IAM rights for the first administrator in your company. 

If you are a WithSecure partner and no administrator in your solution provider level account has the IAM role, please open a "User Management Assistance" ticket using the Partner Portal.  

Issue:

Resolution:

Elements Agent

We will be releasing Elements Agent 25.4 which contains Tahoe compatibility. In Q4 there is going to be a Elements Agent 25.5 built with full Xcode 26 & macOS 26 SDKs 

MDR

MDR 25.1 will be compatible with macOS 26. 

Client Security (Business Suite)

CS16.02 will have compatibility with macOS 26. We are planning to make a new CS16.10 release which will be built with latest Xcode26 & macOS 26 SDKs. ETA is unknown as of now.