Support articles

Extended Detection and Response

  • Why is no action taken by Elements Collaboration Protection to quarantine a high severity email detection?

    Read more
    Issue:

    Why does not Elements Collaboration Protection automatically quarantine a high severity email detection, but an email with a medium severity detection is quarantined?

    Resolution:

    The Elements Collaboration Protection Severity level indicates whether an administrator action is needed to mitigate the immediate risk.

    • Low: No action is needed because the item is coming from a trusted source.
    • Medium: No action is needed. The item was automatically either quarantined or deleted.
    • High: Action required. No automatic action is specified in the policy.
    • Critical: Immediate action is required to mitigate the risk.

    If some emails are quarantined and not others, it can be that in the policy you have set only specific content (URLs or files) to trigger a quarantine action.

    In case of URLs, they are divided into harmful and suspicious in the policy. Both can be given differend actions. 

    How to check the action for both malicious and suspicious URLs:

    1. Log in to the Elements portal
    2. Open the Collaboration Protection section from the menu on the left
    3. Go to the Policies page
    4. Open the policy that is in use on your cloud service
    5. Open the Exchange tab and go to the URL scanning page

    Here in the Action section you can make sure that both Malicious URL and Suspicious URL are set to Move the item to quarantine. Take no action would result in the admin having to manually delete or take action on the item (resulting in a high severity classification).

    If the email with high severity classification includes a malicious file, make sure that the malware scanning action has been set up to quarantine the file:

    1. Open the policy that is in use on the cloud service
    2. Open the Exchange tab and go to the Malware scanning page
    3. In the Action section, make sure that the action is set to Move whole item into quarantine

     

  • Why is Elements Collaboration Protection mailbox shown as "Unavailable" instead of "Unprotected" ?

    Read more
    Issue:

    We have a client where an email address was deleted (in Office 365). Now, I see in the portal that there is a free license available, but when I try to assign the license to another user, it doesn’t seem to be available. Is it possible that the license is still linked to the deleted mailbox? I also cannot delete the user in the portal.

    Resolution:

    This is caused by Microsoft 365. Our Elements Collaboration Protection simply reflect the status provided by Microsoft. If Microsoft shows the mailbox, everything is fine. If not, we mark it as unavailable until Microsoft restores it. This doesn’t always indicate an issue with the mailbox but rather an incomplete response from Microsoft, which happens frequently. If the "unavailable" status persists for more than 1-2 days, you should verify whether the mailbox still exists (e.g., the AD user behind it may have been canceled or the mailbox may have been terminated).

    Whenever a mailbox is unreachable, it is marked as "unavailable." Every 2-3 hours, we request an updated list of resources (mailboxes, sites, etc.) from Microsoft. If a mailbox previously existed in our system but is no longer returned by Microsoft, we mark it as unavailable. This status can occur due to temporary Microsoft issues, which are often resolved within a few hours. By marking mailboxes as unavailable instead of removing them, we can restore them to "unprotected" status if they reappear in future updates without needing to recreate them in the database.

  • When trying to create an offline MSI installer for Elements Endpoint Protection using the FSMSI tool, user receives error: "FsMsiTool is not recognized as an internal or external command." 

    Read more
    Issue:

    When trying to create an offline MSI installer for WithSecure Elements EPP for Computers or for Servers using the FSMSI tool, user receives error: "FsMsiTool is not recognized as an internal or external command."

    Resolution:

    You have to execute the FSMSI tool command from the directory where the tool is saved to or else you will get the error. Using the command prompt, navigate to the folder where you have saved the tool and then run the command mentioned in this help guide.

  • Why is a customer company or a subscription key not visible in the Elements Security Center in a reseller partner's account?

    Read more
    Issue:

    Reseller partner has sold a subscription to a customer. However, when the reseller partner check in the Elements Security Center, they are unable to see / view the customer company or the subscription key / code under the reseller partner's solution provider/service partner account.

    Resolution:

    Make sure that you have logged in to the correct Elements user with the solution provider/service partner rights. If anyone else in your company has an  Elements user too, they can verify Elements user access level on the Management > Organization settings > Endpoint Protection Accounts page in the Endpoint Security Center. If you are the only Elements user, you may contact your WithSecure sales contact for assistance.

    If you have logged in using the correct Elements user but are unable to see the customer company in the scope drop-down menu on your account, make sure that you have sold the Endpoint Protection product as Partner Managed and not Company Managed. If the product has been sold as Company Managed, neither the customer company nor the subscription will be shown in the reseller partner's account.

    There is also a risk that something has gone wrong with the order itself. If the order provisioning fails it will be left pending a manual correction. These are done regularly and if this occurs, your order should become visible at the latest within the next business day (unless further information is required from you in which case you would be contacted). 

    If you have accidentally purchased a Company Managed asset, and want to change it to be Partner Managed, or if you want to verify the state of your order, contact our Order Services team or your WithSecure Sales contact.

    If you are unable to reach your WithSecure Sales contact, contact WithSecure Customer Care: https://www.withsecure.com/en/support/contact-support/email-support

    Note: If customer has only Business Suite products, such as Client Security or Server Security, these products are not part of the Elements portfolio and therefore do not use the Elements Security Center.

  • Why are the quick action buttons (such as “Isolate Affected Device” and “Scan Device”) under the Broad Context Detection details view greyed out in the Elements Security Center?

    Read more
    Issue:

    Why are the quick action buttons (such as “Isolate Affected Device” and “Scan Device”) under the Broad Context Detection detail's view greyed out in the Elements Security Center?

    Resolution:

    The remote operations (such as “Isolate Affected Device” and “Scan Device”) in the Elements Security Center are only available for a device with Elements agent installed using the Elements EDR for Computers/Elements EDR for Servers or Elements EDR and EPP for Computers/Elements EDR and EPP for Servers subscription.

    If you have Business Suite product (Client Security/Server Security) installed on the device with the Endpoint Detection & Response sensor activated, we are unable to trigger remote operations from the Elements Security Center. We need to do this using Operations tab in the Policy Manager Console.

  • What do private and public breach types mean in compromised account in Elements Collaboration Protection?

    Read more
    Issue:

    In compromised account, there's private and public as breach type shown in the detection detail page.
    What do those breach types mean?
     

    Resolution:

    Private - Breach details are not publicly available on the internet. Attackers are selling for cryptocurrency on Tor forums ("dark web")

    Public - Breach details are easily found on the internet. Attackers have shared publicly online e.g. forums for script kiddies, pastebin etc
     

  • What time is the scheduled report generated in Collaboration Protection?

    Read more
    Issue:

    What time is the scheduled report generated in Collaboration Protection?

    Resolution:

    Report generation starts at 3 AM (according to the timezone selected in report task) and takes up to a few minutes.
    Generation frequency depends on a frequency selected in report tasks

    daily: every day
    weekly: every Monday
    monthly: every 1st day of a month

  • The message "Policy does not require the password" is seen next to the user properties under the device status in the Elements Security Center

    Read more
    Issue:

    * The message "Policy does not require the password" is seen next to the user properties under the device status in the Elements Security Center. What goes wrong with the user on the device in this case?
    * The issue "Device at risk due to accounts for which password is not required" is showing up in the dashboard in the Elements Security Center. How can I get this fixed?

    Resolution:

    The message "Policy does not require the password" is showing up under the device status if the local user is not subject to the password policy regarding the length of password. We do not have the option to hide this issue in the portal without fixing this.

    In this case, the local user can have a shorter password than it is required, or it may even have no password at all. You need to check and tweak the UserAccountControl attribute of the user to remove the flag "UF_PASSWD_NOTREQD" if it is found.

    You may run the following command to validate the flag of the local user:

    net user <username>

    If password required flag is "NO" for the user, run the following command to fix it:

    net user <username> /passwordreq:yes

    We would recommend to get this fix soon as possible to avoid any password leak and other potential issues.

  • Unable to access WithSecure Elements portal from the old f-secure.com address

    Read more
    Issue:

    Unable to access WithSecure Elements portal from the old elements.f-secure.com or emea.psb.f-secure.com addresses. 

    Connection ends in errors such as: 

    • Hmmm… can't reach this page. (Edge)
    • This site can't be reached (Chrome)
    • Hmm. We're having trouble finding that site (Firefox)
    Resolution:

    As announced early in 2023, we have changed all of our domain names used by WithSecure Elements to use the withsecure.com address space. Until recently, the old elements.f-secure.com redirected to elements.withsecure.com, but now that redirection has been removed as we no longer have any influence on f-secure.com.

    Please always use https://elements.withsecure.com/ to access the Elements Security Center

  • The Application Control rule "Block rare and unknown files in Temp folder" or "Block rare and unknown files in Downloads folder" in the Elements Endpoint Protection client block an application from running

    Read more
    Issue:

    The Application Control rule "Block rare and unknown files in Temp folder" or "Block rare and unknown files in Downloads folder" in the Elements Endpoint Protection client (Elements EPP for Computers or Elements EPP for Servers) block an application from running.

    How can we create an Application Control exclusion to allow the application to run?

    Resolution:

    The Application Control exclusion can be created using several different conditions. To view the details of the application or file which was blocked:

    1. Log in to the Elements Security Center
    2. Navigate to Events > Security Events
    3. Click the arrow on the left of the corresponding security event to view the details.

    From here, you can easily copy details such as the Target Product Name, Target Signature Signer Name, etc., of the blocked file.

    Once you have the details of the blocked file, you can create an Application Control exclusion.

    1. Navigate to Security Configurations > Profiles.
    2. Select the profile that you want to edit.
    3. Go to the Application Control settings.
    4. Click Add a new top rule
    5. Select Application start and module load from the Event drop-down menu and Allow from the Action drop-down menu.
    6. Define the condition(s) accordingly, such as:
      • Target signer name > is equal to > Target signature signer name (copied from the corresponding security event details), or
      • Target Path > is equal to > Target path (copied from the corresponding security event details), etc.
    7. Click Save profile

    In step 6, you can also use any other condition that suits your needs. You do not have to use the Target signer name, or Target Path. Target product name, Target company, etc. are other conditions that could be used in this situation. All of these can be found from the block detection on the Security Events page.

    Additionally, ensure that the newly created whitelisting rule is moved to the top, so it stays above the blocking rule. Application Control processes rules from top to bottom.

    If necessary, you can refer to the product help guide for more information: Adding application control rules | Elements Endpoint Protection | Latest | WithSecure User Guides