-
Elements Endpoint Protection scheduled or manual scan takes a very long time, how to make it faster?
Read more
Issue:
Elements Endpoint Protection manual or scheduled scanning is slow and it takes a very long time, how to change the settings so that it takes shorter amount of time?
Resolution:
There are a few settings in the Elements Endpoint Protection profile that can make a scheduled scan to be quicker.
The settings are:
- Disable Run scanning as low priority
- Disable Scan inside compressed files
- Enable Scan only known file types during scheduled scanning
By disabling Run scanning as low priority, the scheduled scan scan will take more CPU resources but it will also scan the files faster.
By disabling Scan inside compressed files, the scheduled scan will skip archived files which saves a lot of CPU resources and does not decrease the security on the device since files inside compressed files aren't harmful until they are uncompressed.
By enabling Scan only file types during scheduled scanning, it will skip certain file types.
As for Manual scanning, you can make sure that Scanning priority is set at Normal priority and that Scan inside compressed files is disabled.
How to change these settings:
- Log in to the Elements Security Center portal
- Navigate to the Security configurations > Profiles page
- Open the profile that is in use on the devices
- Go to the Manual scanning settings page
- Here you can edit the previously mentioned settings
- Click Save profile
-
Some websites show ERR_SSL_PROTOCOL_ERROR or SSL_ERROR_ACCESS_DENIED_ALERT in the browser
Read more
Issue:
When a user tries to access some websites with their internet browser, they are shown the following error depending on the browser in use:
- Google Chrome and Microsoft Edge: "The connection for this site is not secure – <website address> sent an invalid response – ERR_SSL_PROTOCOL_ERROR
- Firefox: "Secure Connection Failed – The page you are trying to view cannot be shown because the authenticity of the received data could not be verified – Error code: SSL_ERROR_ACCESS_DENIED_ALERT"
Why are these errors shown only on specific sites and how can we fix these errors from appearing?
Resolution:
This error is shown because the Browsing Protection feature has blocked the website and the Browsing Protection by WithSecure browser extension / add-on is either not installed or activated in the browser. The extension / add-on is required to be able to show the Browsing Protection block page on HTTPS websites. On HTTP sites the block page can be shown even when the extension / add-on is not installed or active in the browser.
A website can be blocked for example if:
- Website is rated as harmful or suspicious by Browsing Protection
- Website category has been blocked by the Web Content Control feature
- Connection Control is active and the website is not rated as safe for banking
You need to make sure that the Browsing Protection by WithSecure browser extension / add-on is installed and active in your browser.
How to install the extension / add-on:
- Right-click the Elements Agent or Client Security icon in Windows the system tray
- Click Open settings
- Go to the Browser extensions settings page
- Follow the instructions to install the browser extension
-
After removal or quarantine of malware, virus or malicious file, why does Elements Endpoint Protection sometimes want the user to restart / reboot the computer?
Read more
Issue:
When a malicious file has been successfully put to quarantine, why does Elements Endpoint Protection sometimes want to reboot the computer?
Resolution:
If the file was detected by the Universal System Scanner (USS) component, it will ask to restart the computer because the infection cannot be completely cleaned up while Windows is running.
You check the removal.log file in the wsdiag diagnostic file if you want to make sure that the detection was made by Universal System Scanner (USS).
-
Keytool error: java.lang.Exception: Keystore file does not exist: /var/opt/f-secure/fspms/data/fspms-ca.jks on Elements Connector for Linux
Read more
Issue:
When exporting the self signed / self-generated certificate from the Elements Connector key store, I receive the error:
- keytool error: java.lang.Exception: Keystore file does not exist: /var/opt/f-secure/fspms/data/fspms-ca.jks
Resolution:
Make sure that you have used the correct command and run it as root:- /opt/f-secure/fspms/jre/bin/keytool -keystore /var/opt/f-secure/fspms/data/fspms-ca.jks -alias fspm-ca -exportcert -file connector-ca.crt -rfc -protected
If you have used the correct command and the issue persists, try to reinstall Elements Connector.Perform the full uninstallation and reinstall Elements Connector on their Linux server by following the instructions below:1. Uninstall Elements Connector
rpm -e f-secure-elements-connector2. Remove installation directories manually
rm -rf /opt/f-secure /etc/opt/f-secure /var/opt/f-secure3. Download the installation package from the Elements Security Center portal's Management > Downloads page
4. Reinstall Elements Connector
rpm -i elements-connector.rpm5. Run the command below to export the certificate from the Connector keystore
/opt/f-secure/fspms/jre/bin/keytool -keystore /var/opt/f-secure/fspms/data/fspms-ca.jks -alias fspm-ca -exportcert -file connector-ca.crt -rfc -protected
-
How to encrypt system drive for a device which has Elements Agent installed on it?
Read more
Issue:
We have Elements Agent installed on our devices with an Elements Endpoint Protection (Elements EPP for Computers or Servers) subscription. How can we from the Elements Security Center portal encrypt the system drive / disk?
Resolution:
Turning drive encryption on or off is an advanced security feature that comes with the WithSecure Elements EPP for Computers Premium and the WithSecure Elements EPP for Servers Premium subscriptions.
You must have a Windows device with Elements Endpoint Protection installed and a disk that was encrypted using BitLocker or FileVault.
- 1. Navigate to the Environment > Devices page in the Elements portal
- 2. Select the device whose drive you want to encrypt.
- 3. From the action menu at the bottom of the page, select drive encryption > Encrypt system drive, and then select one of the following:
- Encrypt only the used disk space (faster and the best for new PCs and drives)
- Encrypt the entire drive (slower but the best for PCs and drives that are already in use)
- 4, Select Encrypt
Note: The device must have a Trusted Platform Module (TPM) version 2 or higher. You can find information about your device's TPM version on the left-side menu in the Device details page.
Recovery keys are an important part of managing disk encryption. If valid users get locked out of their devices or you need to restore data from an encrypted drive using a different device, you need the recovery key to access the data. There are many tools to collect these keys, but it is important that you use one of them. WithSecure Elements Endpoint Protection can collect recovery keys for you, if needed. you can find the setting in the General tab under Profiles.
Note: For collecting recovery keys, you need a Windows device with Elements Endpoint Protection installed and a disk that was encrypted using BitLocker with "recovery password protector". After turning on the feature, we recommend verifying that recovery keys were successfully collected and that the keys are visible in WithSecure Elements Security Center.
The recovery key can be found in the Elements portal on the device details page for a device:
- Log in to the Elements Security Center portal
- Navigate to the Environment > Devices page
- Open the device details for a device by clicking the device
- In the Protection status tab, expand the Endpoint encryption section
- Expand the Encrypted drives section and you will then see the Show recovery key button
- You can copy the Recovery key and the Recovery key ID with the Copy to clipboard buttons
-
When an Elements Endpoint Protection scheduled scanning task is missed, will the task start immediately when device is running?
Read more
Issue:
When an Elements Endpoint Protection scheduled scanning task is missed, for example if computer is in sleep mode or turned off / shut down, will the task start immediately when device is turned on?
Resolution:
If you create a Scheduled scan for malware Automated task in the Elements Endpoint Protection profile, you can set the task to Never skip if the previous start time has been missed.
- Log in to the Elements Security Center portal
- Navigate to the Security configurations > Profiles page
- Select the profile you want to modify
- Go to the Automated tasks settings page
- Click Add task
- Select Scheduled scan for malware from the Type drop-down menu
- Use CRON expressions in the Schedule column to set the task start time
- Enable Never skip toggle from the Never skip column
- Click Save profile
Note: The Scheduled scanning setting on the Manual scanning settings page in the profile does not support any kind of Never skip setting. If a scheduled scan is missed when using the Manual scanning – Scheduled scanning setting, then the scan will start the next scheduled time.
-
Can the Elements EPP firewall Isolation profile be activated if there is a GPO rule to ignore locally defined rules?
Read more
Issue:
Can the Elements Endpoint Proteciton Firewall Isolation profile be activated if there is a GPO rule to ignore locally defined rules? What will happen if a firewall rule distributed by GPO to 'Ignore locally defined rules' and Elements Endpoint Protection tries to isolate the device from the network?
Resolution:
Firewall rules configured via Elements Security Center Portal are considered local, hence if there is a GPO rule to ignore local rules it WithSecure rules or profiles will no longer work.
Our general recommendation is to choose one – either manage Windows Firewall with GPO, or with WithSecure profiles (or with the smallest possible input from GPO), otherwise in case of any conflicting settings GPO will have a higher priority and override WithSecure firewall rules. Also, if there are conflicts, it might impact the host performance negatively
-
Alerts of “Connection refused” related to the doorman backend are being output frequently by Elements Linux Protection
Read more
Issue:
Alerts of "Connection refused" related to the doorman backend are being output frequently by Elements Linux Protection.
Example:
doormand: Failed to send request to Doorman: generic:111 = Connection refusedResolution:
Make sure that the connections to the following Security Cloud domains are allowed on your Firewall and proxy.
Business Suite 16 onwards
- corp-reg.fsapi.com This server is used by Policy Manager for license registration. Blocking this server will prevent license validation.
guts2.fsapi.com (also TCP/80) This server is used to deliver updates for scanning engines and detection rules, and for some products updates to the software itself. Blocking this server will completely stop security updates. - a.karma.sc2.fsapi.com
- restmc.mind.sc2.fsapi.com
- mind-failover.sc2.fsapi.com
- api.doorman.fsapi.com Backend services needed for Security Cloud functionality
- api.prd.glb.us-prd.fsapi.com Used to control updates for Linux Security 64
- download.fsapi.com Used for the hotfix update mechanism for Linux Security 64
If you have allowed the connections, you could check the connectivity status to the domains by accessing to the following URLs from any affected server.
https://baseguard.doorman.fsapi.com/doorman/v1/healthcheck
https://doorman.sc.fsapi.com/doorman/v1/healthcheck
https://a.karma.sc2.fsapi.com/healthcheckIf you are using a proxy, check the connectivity status from your Linux server to the proxy server and make sure that it could be done successfully.
- corp-reg.fsapi.com This server is used by Policy Manager for license registration. Blocking this server will prevent license validation.
-
How to check which device is blocked by the Device Control feature in the Elements portal?
Read more
Issue:
Can we find out which device has been blocked by the Elements Endpoint Protection Device Control feature in the Elements Security Center portal?
Resolution:
When Elements Endpoint Protection Device Control feature blocks a device that matches a Device access rule in the profile, an alert will be sent to the Elements Security Center portal's Events > Security Events page. By clicking on the arrow on the left side of the detection you can show all the details of the block, such as which rule caused the device to be blocked and the Device ID of the blocked device.
If you want to allow the device which was blocked, you can copy the device id from the security event and follow these steps to create a device filtering rule:
- Go to the Security Configurations > profiles page
- Open the profile that is in use on the device
- Go to the Device control settings page
- Scroll down to the Device filtering rules list
- Click Add rule
- Enter the Device ID that was shown in the security event
- Click Save profile
Now the device is which was shown in the security event will no longer be blocked by the Elements Endpoint Protection device control feature.
Device Control can list all the devices which are connected to a computer in the Elements Security Center portal. To see the list of devices:
1. Navigate to the Environment > Devices page
2. Click on a Device
3. Switch to the Connected Devices tabHere you can see all the devices and their IDs.
-
Browsing Protection is missing on Elements Endpoint Protection for Computers (Mac) with error Security application not found
Read more
Issue:
Browsing Protection by WithSecure is missing from Firefox on Elements Endpoint Protection for Computers (MacOs) with the error "Security application not found". On macOS there's a constant popup about missing Firefox browser extension.
Resolution:
If you receive the error "Security application not found" and Browsing Protection by WithSecure browser extension is missing from Firefox, manually install the Browsing Protection by WithSecure extension for Firefox.
- To set up the browser extension for Firefox:
- Select the product icon in the menu bar.
- Select Settings… from the menu.
- Open the Secure Browsing tab.
- Select Install browser extension.
- The Browsing protection installation window opens.
- From the drop-down, select Firefox and then Install now.
- Select Add.
- Once the extension is installed, a user consent dialog opens. The browser extension requires your permission to access information about the web addresses you visit.
- Select Accept.
- Note: If you decline to grant the permission, you will not be able to use the extension and Browsing protection cannot block harmful websites nor show search result ratings. Also, the extension will be removed from the browser.
- To complete setting up the extension, select OK.
You can now use Firefox to browse the internet safely.
More details about the installation of Mac browser extensions and how to check if they are in use can be found in the User Guide: Checking that browser extensions are in use | Elements Endpoint Protection for Computers | Latest | WithSecure User Guides