Is WithSecure services Down Right Now? Check if there is a current outage ongoing.

We are investigating a delay in the creation of Broad Context Detections (BCD) in WithSecure Elements Endpoint Detection and Response. BCDs appear with a delay of up to 40 Minutes in the WithSecure Elements portal. We are working to reduce the delay with the highest priority.

The issue is now resolved as of 14:27 UTC

We are investigating an issue where remote operations in WithSecure Elements Endpoint Protection, Endpoint Detection and Response, Managed Detection and Response as well as Business Suite Client Security and Server Security are executed with a delay. Push notifications from clients may also arrive with a delay to the WithSecure Elements portal.

The issue is now resolved as of 14:27 UTC

We are investigating an issue where remote operations in WithSecure Elements Endpoint Protection, Endpoint Detection and Response, Managed Detection and Response as well as Business Suite Client Security and Server Security are executed with a delay.Push notifications from clients may also arrive with a delay to the WithSecure Elements portal.

The issue has been resolved.

We are investigating an issue where login to the WithSecure Elements portal fails and already logged in users receive various errors when navigating the portal.

The issue has been resolved.

We are investigating an issue where login to the WithSecure Elements portal fails and already logged in users receive various errors when navigating the portal.

This incident has been resolved.

We are in the process of releasing a new version that resolves this issue. This version is currently pending Microsoft approval. In the meantime, you can manually upgrade the WithSecure Elements API connector for Microsoft Sentinel (deployed from Azure Marketplace) by following these steps: Login to Azure CLI az login Download the Fixed Version of the Connector App from: https://github.com/WithSecureOpenSource/elements-api/releases/download/1.0.1/connector.zip Run the Function App Deployment (Modify the MyResourceGroupName and MyFunctionAppName as needed): az functionapp deployment source config-zip --resource-group MyResourceGroupName --name MyFunctionAppName --src ./connector.zip

We are currently investigating an issue where the Microsoft Sentinel connector is not receiving security event data from WithSecure Elements. Affected are all customers using the Sentinel connector.

We have found the root cause of the issue and a fix was done in production. However a refresh of permissions for sharepoint is required for Elements collaboration protection. The refresh can be completed with the following steps: 1: Logging in to the Elements security Center 2: Navigating to the Collaboration Protection section 3: Select Cloud Services from the left hand menu 4: From the Cloud Services pages select the Tenant an action menu will become visible and select "Refresh permissions to Sharepoint" a new permission consent will be requested, including all the necessary permissions This must be completed by all Elements Collaboration Protection users to maintain Sharepoint and Teams coverage.

We are investigating an issue with WithSecure Elements Collaboration Protection. When a cloud connection is newly established or refreshed, despite the UI showing "connected", there will be no SharePoint sites or Teams Channel listed as protected. The Exchange functionality and One Drive are working as expected. We are working on resolving the issue.

We have published a fix today. This will be automatically taken into use and resolve the issue.

We have released a fix for the issue to our Early Access program. We expect to release it to all clients early next week. We recommend assigning a small number of endpoints to participate in the Early Access program. Selected workstations and servers receive updates prior to the general availability. You can configure the Early Access in the profile in the WithSecure Elements Portal by navigating to - Security Configurations - Profiles - Linux - Edit profile - General - Early access to client software - Save and publish

We are investigating an issue where WithSecure Elements Endpoint Detection and Response Linux sensor as well as the response components may stop running after a reboot. Other platforms are not affected. To workaround the issue, execute the master-switch off command, followed by master-switch on on the affected host. This will restore full functionality on the host. We are working on resolving the issue for all affected hosts.

This incident has been resolved.

The process of recreating the Identity findings was successfully completed overnight. Please note that the calculation process may take some time before the results are fully available.

We have identified the issue and are gradually restoring identity findings.

We are investigating an issue where WithSecure Exposure Management findings for identities are inconsistent. The portal may falsely report "no issues found", hence previously visible recommendations related to Identities might be missing. Any new issues will continue to be detected and recommendations given for.

We have published a fix to the issue. The fix is taken into use automatically, no administrator or user action is needed. If you wish, you can verify the installation in the WithSecure Elements portal under Environment - Devices - Computers. The latest installed hotfixed client version will show 25.1.85.0 If the hotfix version is not visible in the table, click "select columns" and search for "hotfix".

We have identified the issue and are working on a solution. We aim to publish a fix early next week (week from 14th of April).

We are investigating an issue where WithSecure Elements Endpoint Protection automated tasks do not start. Affected platforms are Windows Client & Server as well as Mac. Symptoms are: Software Updater automatic installation does not work at all File scanning task, which is configured via Automated Tasks, does not start Shutdown, restart, and other automated tasks do not start 3 or more fshoster32.exe processes are running

This incident has been resolved.

We are investigating an issue were WithSecure Elements Endpoint Detection and Response (EDR) response actions might fail when using non-english portal localization. We recommend to switch to English if you encounter the issue until we have resolved it. We apologize for the inconvenience.

This incident has been resolved.

The service has now been restored, logging in to Elements Security Center working correctly.

We are currently investigating an issue where logging in to WithSecure Elements security Center fails.

This incident has been resolved.

We have deployed changes that resolve the issue for all but one use case. Currently. when changing Allow custom DNS server(s) in End User Rights section, the profile can not be saved. We continue working on this with the highest priority.

We are investigating reports that the WithSecure Elements Endpoint Protection profile editor for mobile profiles is not working correctly. Changes can not be saved.

This incident has been resolved. Ordering functionality is restored. We apologize for the disruption.

We are investigating an issue where ordering is not available in WithSecure Partner Portal. We are asking our partners to follow this incident and file orders once the service is restored.

We have restored the service. The downtime lasted from 09:30 UTC to 13:15 UTC in which significant portion of content was not scanned.

We are investigating a major outage of WithSecure Elements Collaboration Protection. We estimate that a significant portion of mailboxes are not protected. Also Sharepoint, OneDrive and Teams protection are partially affected. We work with the highest priority on this issue.

We apologize for an error in our recent communication regarding access to the Partner Portal Extension. Due to a technical issue, you received an email stating that you have been granted access to the Partner portal extension on Thursday 27.2. or Friday 28.2. Unfortunately, this message was sent to you by mistake, and you do not currently have access to the Partner Portal Extension. We sincerely apologize for any confusion or inconvenience this may have caused. Please rest assured that we are taking steps to prevent such errors in the future. Please be aware that some partners will receive a similar message over the weekend of 1st-2nd March and this message is correct.

We are investigating an issue where the ordering functionality in WithSecure Partner Portal is unavailable for some partners. We are working with the highest priority on restoring the functionality. Please refrain from submitting manual orders.

This incident has been resolved.

We have resolved the issue for the vast majority of affected customers and devices and continue to work on the issue.

We have limited the impact to a small set of customers. Affected customers may experience also an TX-ID error when elevating a BCD from an affected device. In this case, please reach out to Technical Support with the BCD ID. https://www.withsecure.com/en/support/contact-support/call-support We continue working on this issue.

We are investigating an issue where some installed WithSecure Elements devices may not be visible in the Elements Security Center despite devices being protected and licenses are taken into use.

Scan results may take 36 hours to populate and we are working on further improvements in the future, reducing (initial) scanning time. For more information, please visit https://community.withsecure.com/en/kb/articles/31640-after-onboarding-a-new-elements-exposure-management-customer-to-the-cloud-account-the-identities-view-in-the-elements-security-center-does-not-populate-data

The Identities view in Elements Exposure Management fails to display data after a successful scan for newly onboarded customers. The message displayed will be "No identities found."

This incident has been resolved.

We are investigating an issue where some WithSecure Elements Exposure Management network scans using cloud scan nodes remain at 0% even after sufficient wait time.

This incident has been resolved.

We have deployed changes that will be visible in the coming hours as results are re-calculated. We continue to monitor the issue.

We are currently testing improvements and plan to deploy those at the beginning of next week. Please continue to follow this incident for updates.

We are currently investigating an issue where WithSecure Elements Exposure Management may not show recommendations despite findings on the devices. Please subscribe for further updates.

The WithSecure Browsing Protection extension is again available in Google Chrome webstore and can be installed.

The WithSecure Browsing Protection extension is currently not available in Google Chrome webstore. We are working with google to restore it. Security is not reduced, as Browsing Protection continues to work without the plugin. Certain functionality such as block pages may not display correctly.

The issue has been resolved. Affected machines are recovering automatically. We apologize for the inconvenience.

We are investigating an issue where newly installed WithSecure Elements Endpoint Detection and Response and WithSecure Countercept sensors can not communicate with our servers. This may show as "Device sensor is not operational" in WithSecure Elements Endpoint Detection and Response. We investigate this issue with the highest priority.

The incident has been resolved.

We are currently investigating an issue, where cloud accounts (AWS/Azure) are not shown in the WithSecure Elements Exposure Management portal and cloud scans fail.

The issue now has been resolved, and we are monitoring the issue. Currently Elements Portal is working normally. We sincerely apologize for the inconvenience.

Currently Elements Portal is malfunctioning for organizations in EPP APAC region. Only the portal is affected and will not affect the Endpoints Protection to our users. We are currently investigating to understand root cause and find a solution to the issue. We sincerely apologize for the inconvenience.

We have released WithSecure Countercept Agent 24.3 to resolve the issue. It is being taken into use automatically.

We have now released WithSecure Elements Agent for Mac 24.6. The new version will be installed and taken into use automatically. No administrator action is required. We continue working on a new WithSecure Countercept Agent release and estimate to release it mid-January.

We are continuing to work on a fix for this issue.

We have published a new version of WithSecure Client Security for Mac 16.02 that addresses this issue. Administrators should take action and roll out this version to affected systems. We are working on WithSecure Elements and Countercept Agent releases and are planning to roll those out as automatic updates. Please follow this incident to get notified on the releases. The installation package can be downloaded from https://www.withsecure.com/en/support/product-support/business-suite/client-security#download and selecting macOS.

We are currently investigating an issue with our products for Mac, and customers may experience any of the following symptoms: - The WithSecure Agent doesn't start normally at computer startup. - The WithSecure user interface menu is not visible on the menu bar - Active application window focus lost repeatedly without an apparent reason Affected products: WithSecure Elements Agent for MacOS 24.5 WithSecure Client Security for Mac 16.01 WithSecure Countercept Agent 24.2 Please subscribe for further updates.

This incident has been resolved.

We have received reports that devices go missing in the Elements Security Center after performing the subscription change operation. We have released a fix and currently monitoring the issue.

We have received reports that devices go missing in the Elements Security Center after performing the subscription change operation. We are currently investigating the issue and working diligently to resolve it. Thank you for your patience as we work towards a solution.

This incident has been resolved.

Issue is now resolved, all backlogs are cleared, and it is now back working as normal. We will continue to monitor the situation.

The queues are clearing quickly, and we anticipate that the system will be back to normal in the next few hours.

We are currently experiencing significant delays in WithSecure Elements Detection and Response. We have already deployed a solution. We can see that the queues are now being process at nominal delay, but it will take some time to clear the backlog. Please follow this incident for further updates.

We are currently experiencing significant delays in WithSecure Elements Detection and Response. We have already deployed a solution. We can see that the queues are being processed faster, but it will take some time to clear the backlog. Please follow this incident for further updates.

The issue has been resolved. We apologize for the inconvenience caused.

We are currently investigating reports of an error message when attempting to remove a device from the WithSecure Elements portal’s Environment > Devices page.

We're pleased that a fix has been deployed to production. Customers outside the EU tenant can now download Advanced Response job attachments.

We continue working on the issue. In the meantime, we can confirm that WithSecure Countercept customers are not affected.

We have identified an issue where downloading any Advanced Response jobs attachments fails for customers outside of our EU tenant. Affected products are WithSecure Elements Endpoint Detection and Response and WithSecure Countercept.

This incident has been resolved.

We can confirm that the clients are recovering automatically, however it may take up to 48h for all devices to recover. We are investigating options to speed up the recovery.

A fix has been implemented and we are currently monitoring the issue.

We are continuing to work on a fix for this issue.

The current update rolled out yesterday of Mac Elements EDR version 24.3 is causing an issue and the sensors may stop sending events after the update. We have identified the issue and working on the fix.

This incident has been resolved.

Issue has been resolved after the HTTP proxy is setup to allow the connections to WithSecure backends.

We are investigating reports of performance degradation of WithSecure Atlant and Linux Security 64 in some restricted environments since 2nd of September 2024. Further symptoms that may be visible are: - slow login to the server - SSH/HTTPS connections failing - Services or databases processing is slow To resolve the issue, we recommend to review your firewall configuration and ensure the product can communicate to our backend services. See https://community.withsecure.com/en/kb/articles/31208-network-addresses-for-withsecure-on-premise-products for detailed instructions. Alternatively, you can disable non-essential network services from the product by enabling offline mode: For Linux Security 64: /opt/f-secure/fsbg/bin/offline-mode enable For Atlant: /opt/f-secure/atlant/fsbg/bin/offline-mode enable If the number of affected Linux servers is high that the offline mode is difficult, you can consider to disable Security Cloud feature by going to the following settings on Policy Manager Console. For Linux Security 64: Settings > Linux > Real-time scanning > uncheck "Use Security Cloud" For Atlant: Settings > Atlant > Scanning service > uncheck "Check file reputation" and "Check URL reputation" It is also possible to disable the Security Cloud feature locally on Atlant server by using the "atlantctl" command utility tool. /opt/f-secure/atlant/atlant/bin/atlantctl set scanning reputation file_check false /opt/f-secure/atlant/atlant/bin/atlantctl set scanning reputation url_check false In case of Elements EPP for Servers (Linux) or Linux Protection with the restricted internet access that may encounter the same issue, we recommend to allow the connections to our backend services indicated in the following community article. https://community.withsecure.com/en/kb/articles/31217-network-addresses-for-withsecure-elements-cloud-managed-products Alternatively, you can disable non-essential network services from the product by enabling the offline mode or disable Security Cloud feature in the profile configurations. To enable offline mode: /opt/f-secure/fsbg/bin/offline-mode enable To disable Security Cloud in Linux profile: Basic > Real-time scanning > Unknown files reputation > turn off "Use Security Cloud" setting

We are investigating reports of performance degradation of WithSecure Atlant and Linux Security 64 in some restricted environments since 2nd of September 2024. Further symptoms that may be visible are: - slow login to the server - SSH/HTTPS connections failing - Services or databases processing is slow To resolve the issue, we recommend to review your firewall configuration and ensure the product can communicate to our backend services. See https://community.withsecure.com/en/kb/articles/31208-network-addresses-for-withsecure-on-premise-products for detailed instructions. Alternatively, you can disable non-essential network services from the product by enabling offline mode: For Linux Security 64: /opt/f-secure/fsbg/bin/offline-mode enable For Atlant: /opt/f-secure/atlant/fsbg/bin/offline-mode enable If the number of affected Linux servers is high that the offline mode is difficult, you can consider to disable Security Cloud feature by going to the following settings on Policy Manager Console. For Linux Security 64: Settings > Linux > Real-time scanning > uncheck "Use Security Cloud" For Atlant: Settings > Atlant > Scanning service > uncheck "Check file reputation" and "Check URL reputation" It is also possible to disable the Security Cloud feature locally on Atlant server by using the "atlantctl" command utility tool. /opt/f-secure/atlant/atlant/bin/atlantctl set scanning reputation file_check false /opt/f-secure/atlant/atlant/bin/atlantctl set scanning reputation url_check false

We are investigating reports of performance degradation of WithSecure Atlant and Linux Security 64 in some restricted environments since 2nd of September 2024. Further symptoms that may be visible are: - slow login to the server - SSH/HTTPS connections failing - Services or databases processing is slow To resolve the issue, we recommend to review your firewall configuration and ensure the product can communicate to our backend services. See https://community.withsecure.com/en/kb/articles/31208-network-addresses-for-withsecure-on-premise-products for detailed instructions. Alternatively, you can disable non-essential network services from the product by enabling offline mode: For Linux Security 64: /opt/f-secure/fsbg/bin/offline-mode enable For Atlant: /opt/f-secure/atlant/fsbg/bin/offline-mode enable

This incident has been resolved.

Performance of the WithSecure Elements Vulnerability Management portal has been restored. Reports still experience a delay, but we expect this delay to clear within the next 24 hours.

We are currently investigating a performance issue in WithSecure Elements Vulnerability Management. Symptoms are: - Long load times navigating the portal - Reports arriving with significant delays

This incident has been resolved.

We have released a new version of WithSecure Elements Endpoint Protection for Mac 24.1. This release addresses reported performance issues. We continue to investigate the performance impact and monitor the situation closely.

We are preparing to release a new version that will address this issue during April. There are some steps needed to prepare for the release. For more information, please see our community: https://community.withsecure.com/en/kb/articles/31284-pre-announcement-new-withsecure-client-for-macos

We are continuing the investigation into this issue.

We apologize for the duration of this incident and assure you that we continue working on resolving this issue with the highest priority.

We are investigating reports of WithSecure Elements Endpoint Protection causing performance issues on MacOS 14 Sonoma when using applications such as Microsoft Teams and Slack. Other applications may be affected too.

The issue has been resolved. We apologize for the inconvenience caused.

We have identified the cause of the issue and are currently rolling back.

We are currently investigating reports that logging in to WithSecure Elements Security Center fails.

This incident has been resolved.

Earlier, Element EPP 24.4 is preventing user from saving documents from document editor such as MS Office, PDF24, Notepad and more. A fix has been released and we are currently monitoring the issue.

Currently Element EPP 24.4 is preventing user from saving documents from document editor such as MS Office, PDF24, Notepad and more. We're working diligently to identify and investigate the issue.

The issue has been resolved. We apologize for the inconvenience caused.

We are investigating a partial outage of our telephony system. Finland based phone numbers are unavailable. Phone numbers in other countries are not affected. Our phone numbers are listed here: https://www.withsecure.com/en/support/contact-support/call-support You can also create a support request through Partner Portal, eService Portal (customers with advanced or premium support) as well as from our public webform. https://www.withsecure.com/en/support/contact-support/email-support If you would like us to call you back, please indicate it in your support request. We apologize for the inconvenience.

We have released a new version of WithSecure Elements Agent for Mac 24.1 that resolves this issue.

We have identified that the upgrade to Elements Agent for Mac 24.1.51782 is unable to remove Elements Agent for Mac 23.2 automatically if the setting "Allow user to uninstall the product" is disabled. The root cause of the problem has been identified and fixed will be applied in the next release of agent for Mac. We sincerely appreciate your patience on this matter and apologize for the inconvenience caused.

This incident is now resolved, WithSecure Elements Endpoint Detection and Response is now working as expected and not showing any error after creating response action.

We are investigating an issue where you receive a error message after creating a response action in WithSecure Elements Endpoint Detection and Response. Response actions are performed but the portal shows an error. WithSecure Countercept is not affected. We are working to resolve the issue with the highest priority.

This incident has been resolved.

We are investigating an issue where downloading installers from our downloads page at https://www.withsecure.com/en/support/download may randomly fail. Our End User License Agreement may also fail to load. We are working on restoring the service with the highest priority.

This incident has been resolved.

The issue has been resolved. We apologize for the inconvenience caused.

Currently you'll not be able to raise a support ticket via support page, submission page showing the error "404: The page could not be found". We're in the midst of investigating the root cause and to fix the issue. Meanwhile, please find our support contact number here to file a ticket to us, https://www.withsecure.com/en/support/contact-support/call-support. We sincerely appreciate your patience on this matter and apologize for the inconvenience caused.

This incident has been resolved.

Fix has been identified and deployed. Meanwhile if you still have issue to submit a support ticket via https://www.withsecure.com/en/support/contact-support/email-support, please clear the browser's cache.

You'll encounter error "Please check the data you sent" while trying to file a support ticket with us. We're in the midst of investigating the root cause and to fix the issue. Meanwhile, please find our support contact number here to file a ticket to us, https://www.withsecure.com/en/support/contact-support/call-support. We sincerely appreciate your patience on this matter and apologize for the inconvenience caused.

This incident has been resolved.

The WithSecure Elements portal is available again. We continue to monitor the situation. We apologize for the incident.

We are investigating an outage of our WithSecure Elements portal.

This incident has been resolved.

We have implemented changes that resolve the issue. We continue to monitor the situation.

We are investigating an issue with the Microsoft Exchange API which leads to some scanning errors on WithSecure Elements Collaboration Protection. Items that could not be scanned will be retried automatically.

This incident has been resolved.

A fix has been implemented and we are monitoring the results. If you continue to experience issues with WithSecure Policy Manager 16 downloading updates for F-Secure Client Security/Server Security 15.x, please empty your DNS cache.

It looks like it is taking more time than expected due to some configuration issues. We are currently working on it and we will provide you with an update once it is done. We sincerely appreciate your patience on this matter and apologize for the inconvenience caused.

We have deployed a change to fix the issue. It will take up to 4 hours until it is available to all customers. Updates will start automatically, no administrator action is required.

We are investigating reports where WithSecure Policy Manager 16.x is unable to download updates for F-Secure Client Security 15.x and F-Secure Server Security 15.x. Updates for version 16 clients are not affected.

This incident has been resolved.

We released WithSecure Mobile Protection 23.4 to Google Play. The app is currently under review by Google and we expect Google to make it available to all users in the next 24 hours.

Currently Mobile Protection 23.3 for Android does not allow user to disable VPN or add applications to bypass the VPN. We're in the midst of identifying the issue and working towards fixing it. We sincerely apologize for the inconvenience caused and are working on fixing the issue as soon as possible.

This incident has been resolved.

Currently we have identified missing Countercept detections in OpenSearch L2 from 2023-10-19 10:00 UTC to 2023-10-20 03:00 UTC. We're in the midst of checking if other layers are affected. This doesn't affect the functionality of Countercept. We sincerely apologize for the inconvenience caused and are working on fixing the issue as soon as possible.

We have released WithSecure Policy Manager 16.01, which resolves the issue. You can download the new version from our download pages: https://www.withsecure.com/en/support/product-support/business-suite/policy-manager#download

We are investigating an issue where upgrading F-Secure Policy Manager 15.x to WithSecure Policy Manager 16 results in a fresh installation when F-Secure Policy Manager 15.x was installed in a non-default installation path. We are working on fixing the issue. If you have already performed the upgrade and encountered the issue, please follow these instructions: 1. Stop the PMS service using CMD: net stop wspms 2. Copy the content from ?:\Program Files (x86)\F-Secure\Management Server 5\data\events\ ?:\Program Files (x86)\F-Secure\Management Server 5\data\guts2\ ?:\Program Files (x86)\F-Secure\Management Server 5\data\h2db\ ?:\Program Files (x86)\F-Secure\Management Server 5\data\fspms.jks ?:\Program Files (x86)\F-Secure\Management Server 5\data\fspms.db.config ?:\Program Files (x86)\F-Secure\Management Server 5\data\fspms.proxy.config ?:\Program Files (x86)\F-Secure\Management Server 5\data\fspms-ca.jks ?:\Program Files (x86)\F-Secure\Management Server 5\data\sdata to C:\ProgramData\WithSecure\NS\Policy Manager\Policy Manager Server\data\events\ C:\ProgramData\WithSecure\NS\Policy Manager\Policy Manager Server\data\guts2\ C:\ProgramData\WithSecure\NS\Policy Manager\Policy Manager Server\data\h2db\ C:\ProgramData\WithSecure\NS\Policy Manager\Policy Manager Server\data\fspms.jks C:\ProgramData\WithSecure\NS\Policy Manager\Policy Manager Server\data\fspms.db.config C:\ProgramData\WithSecure\NS\Policy Manager\Policy Manager Server\data\fspms.proxy.config C:\ProgramData\WithSecure\NS\Policy Manager\Policy Manager Server\data\fspms-ca.jks C:\ProgramData\WithSecure\NS\Policy Manager\Policy Manager Server\data\sdata If prompted, select to replace any existing files. 3. Execute the maintenance tool: C:\Program Files\WithSecure\Policy Manager\Policy Manager Server\bin\fspms-db-maintenance-tool 4. Check and ensure, the https and https ports are correctly defined in registry and match the settings for the previous F-Secure installation Old location for settings in WithSecure Policy Manager version 15.00 (and older) HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Data Fellows\F-Secure\Management Server 5 New location for settings in WithSecure Policy Manager version 16.00 (and newer) HKEY_LOCAL_MACHINE\SOFTWARE\WithSecure\Policy Manager\Policy Manager Server\ 5. Start the PMS service using CMD: net start wspms Note: replace "?" with the source drive for your previous Policy Manager installation. If you are unsure, where the old version is installed, check the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Data Fellows\F-Secure\Management Server 5\InstallationDirectory An example is below: D:\Program Files (x86)\F-Secure\Management Server 5 In this case, the source drive is D:

This incident has been resolved.

We have taken the decision to revert the latest release and have just published the Ultralight Core 2023-08-31_01 update. The update will be taken automatically in use. No reboot is required. This update resolves the issue for all affected customers. We continue to investigate the root cause of the issue with high priority.

We have received reports that some Windows servers running WithSecure Elements Endpoint Protection or WithSecure Business Suite Server Security are suffering from generally slow performance. This may manifest as users not being able to logon to terminal servers or some applications responding unusually slow. Currently we have released the fix and we are monitoring the issue. Please subscribe to this incident for status updates. We apologize for the inconvenience.

We have received reports that some Windows servers running WithSecure Elements Endpoint Protection or WithSecure Business Suite Server Security are suffering from generally slow performance. This may manifest as users not being able to logon to terminal servers or some applications responding unusually slow. We are working to isolate the issue and resolve it. Please subscribe to this incident for status updates. We apologize for the inconvenience.

This incident has been resolved.

Investigating - We are investigating an issue where clients of Cloud Protection for Salesforce may notice scan requests failing , this started at around 07:20 UTC , this could also have had minor impacts on Elements Collaboration Protection, with minor impact to Elements Endpoint Protection clients , where as request could have failed. Monitoring - As of 12:55 UTC a fix was released that upon rescan this should complete successfully and new connections fúnction as normal. Currently we have released the fix and we are monitoring the issue. Please subscribe to this incident for status updates. We apologize for the inconvenience.

WithSecure Elements Endpoint Protection 23.7 was released and is installed automatically by hosts. This release resolves the issue.

We are continuing to work on a fix for this issue.

We have released a fix for the issue for our customers using Business Suite. The update is automatically installed. The update is listed as released F-Secure Software Updater Engine 2023-09-21_01. For customers using WithSecure Elements, the fix is included in the next version 23.7 which we aim to release late next week. The new version is already available to customers in Early Access. You can join the Early Access program through the WithSecure Elements Portal. Navigate to profile settings, general settings, early access.

Currently Software Updater detects cumulative update (KB5029263) for Windows 11 repeatedly even after update and restart. This issue only affects Windows 11. We apologize for the inconvenience and are working on fixing the issue.

This incident has been resolved.

Issue has been identified and a fix for Collaboration Protection has been deployed. We sincerely apologize for the inconvenience.

A subset of WithSecure Elements Collaboration Protection customers are receiving alerts for detections in old emails. We found that changes on Microsoft side caused the scanning of these older items. We continue investigating the issue. We apologize for the inconvenience caused.

This incident has been resolved.

The issue is fixed now. Newly created account can now login to the Elements Security Center. We apologize for the inconvenience and the issue is fixed now, we are currently monitoring the issue and will provide an update if there is anything on fixing the issue.

The issue is fixed now. Newly created account can now login to the Elements Security Center. We apologize for the inconvenience and the issue is fixed now, we are currently monitoring the issue and will provide an update if there is anything on fixing the issue.

We have identified newly created Elements Security Center accounts have issue to login. Login will result in getting error "503 Service Temporarily Unavailable". We're in the process of identifying the root issue. We apologize for the inconvenience and are working on fixing the issue.

This incident has been resolved.

We have identified that our Elements Endpoint Protection Portal is not accessible. Found that it is due to a service disruption by the authentication service that we used. It seems the issue is just a glitch and temporary, the issue is now fixed and we will continue to monitor it. We sincerely apologize for the inconvenience.

We have identified that our Elements Endpoint Protection Portal is not accessible. Currently, it is showing these errors intermittently ; 'Incorrect login credentials' and also 'Cannot load the page'. The related team is working on to fix the issue. We sincerely apologize for the inconvenience caused and are working on fixing the issue as soon as possible.

We have identified that our Elements Endpoint Protection Portal is not accessible. Currently, it is showing these errors intermittently ; 'Incorrect login credentials' and also 'Cannot load the page'. The related team is working on to fix the issue. We sincerely apologize for the inconvenience caused and are working on fixing the issue as soon as possible.