-
How to replace the default self-signed Policy Manager certificate with a trusted certificate authority (CA) created certificate?
Read more
Issue:
How can I replace the default self-signed Policy Manager certificate with a trusted certificate authority (CA) created certificate?
Resolution:
Assume that you have:
- The signed or maybe self-signed certificate (with full chain of intermediate CA) and private key for it inside PKCS12 Keystore.
- It is protected with password "srcpassword"
- Your certificate and the private key are referenced by name (alias) "server".
- The Keystore file is "server.p12" and it is located in the same directory as "fspms.jks".
Steps to replace the default Policy Manager certificate:
- Launch an elevated command prompt
- Change the default folder to the directory where "fspms.jks" and import the new trusted certificate using the following commands:
- Policy Manager 15.x:
- cd "C:\Program Files (x86)\F-Secure\Management Server 5\data"
- "C:\Program Files (x86)\F-Secure\Management Server 5\jre\bin\keytool" -importkeystore -destkeystore fspms.jks -deststorepass superPASSWORD -destalias fspms -destkeypass superPASSWORD -srckeystore server.p12 -srcstoretype PKCS12 -srcstorepass srcpassword -srcalias server
- Policy Manager 16.x:
- cd "C:\ProgramData\WithSecure\NS\Policy Manager\Policy Manager Server\data"
- "C:\Program Files\WithSecure\Policy Manager\jre\bin\keytool" -importkeystore -destkeystore fspms.jks -deststorepass superPASSWORD -destalias fspms -destkeypass superPASSWORD -srckeystore server.p12 -srcstoretype PKCS12 -srcstorepass srcpassword -srcalias server
- You are replacing the certificate in "fspms.jks" so the following message will appear:
- Existing entry alias server exists, overwrite? [no]:
- Type "yes" and hit enter.
- Restart the Policy Manager server to start using the new certificate. Use a Command Prompt to run the commands:
- Policy Manager 15: net stop fsms and net start fsms
- Policy Manager 16: net stop wspms and net start wspms
NOTE: When you execute the importkeystore command pay attention to "-destkeypass", it should be the same as "-deststorepass". If you forget to insert proper "-destkeypass", the command can complete successfully but problems on Policy Manager server startup may occur.
-
How to replace default self-signed Policy Manager Linux certificate with trusted CA created certificate
Read more
Issue:
How can I replace the default self-signed Policy Manager Linux certificate with trusted CA created certificate?
Resolution:
The Policy Manager for Linux keystore is located inside "/var/opt/f-secure/fspms/data/fspms.jks" (version 12.30 and higher) or "/opt/f-secure/fspms/config/fspms.jks" for previous Policy Manager versions.
You can use the following command to query details about certificates stored in fspms.jks:
- /opt/f-secure/fspms/jre/bin/keytool -list -v -keystore fspms.jks -storepass superPASSWORD
- You should see the following output:
Keystore type: JKS
Keystore provider: SUNYour keystore contains 1 entry
Alias name: fspms
Creation date: 20.09.2010
Entry type: PrivateKeyEntry
Certificate chain length: 1
Certificate[1]:
Owner: CN=f-secure.com, OU=f-secure.com, O=f-secure.com, C=EN
Issuer: CN=f-secure.com, OU=f-secure.com, O=f-secure.com, C=EN
Serial number: 4c977fcc
Valid from: Mon Sep 20 18:37:48 EEST 2010 until: Wed Aug 27 18:37:48 EEST 2110
Certificate fingerprints:
MD5: 00:2D:4E:23:3A:9C:68:22:CD:CE:72:43:2B:CC:98:00
SHA1: 7C:F7:E1:2D:2E:6C:0A:86:66:53:E2:C7:59:2C:F2:9E:89:B6:4F:BD
SHA256: 02:87:BD:AF:BB:2B:F2:BB:13:A5:96:A8:F1:5D:DC:5C:67:AB:77:68:AF:36:85:1F:F2:F7:DE:29:88:AD:DF:D1
Signature algorithm name: SHA1withDSA
Version: 3You can follow the steps below to replace the default self-signed Policy Manager Linux certificate:
Assume that you have:
- The signed or maybe self-signed certificate (with full chain of intermediate CA) and private key for it inside PKCS12 keystore.
- It is protected with password " srcpassword "
- Your certificate and the private key are referenced by name (alias) " server ".
- The keystore file is " server.p12 " and it is located in the same directory as " fspms.jks ".
NOTE: When you execute importkeystore command pay attention to "-destkeypass", it should be same as "-deststorepass". If you forget to insert proper "-destkeypass" command can complete successfully but problems on Policy Manager server startup may occur.
- Type the following command:
- /opt/f-secure/fspms/jre/bin/keytool -importkeystore -destkeystore fspms.jks -deststorepass superPASSWORD -destalias fspms -destkeypass superPASSWORD -srckeystore server.p12 -srcstoretype PKCS12 -srcstorepass srcpassword -srcalias server
- You are replacing certificate in "fspms.jks" so following message will appear:
- Existing entry alias server exists, overwrite? [no]:
- Type "yes" and hit enter
- Type the following command to restart the Policy Manager server to start using the new certificate:
- /etc/init.d/fspms restart
-
How to check what version of virus definitions are currently installed with the Windows Command line?
Read more
Issue:
How to check what versions of virus definitions are currently installed on WithSecure Client Security 16.00 (and above) or Server Security 16.00 (and above) with the Windows command line?
Resolution:
Follow these steps to run the fs_oneclient_command.exe tool to print out product information:1. Open the command prompt (cmd.exe) or a PowerShell as an Administrator2. Depending on the product, navigate to either working directory:
Server Security 16 C:\Program Files (x86)\F-Secure\Server Security Client Security 16 C:\Program Files (x86)\F-Secure\Client Security 3. Execute the following: fs_oneclient_command.exe --productinfoThis will print information about:
- General product information
- License status: License validity and expiration date
- Update status: Update server info, last update date and list of latest installed or failed to install updates
- Setting status: Management settings and profiles
- Feature status: Which features are enabled
-
How to free up the subscription usage for a Endpoint Detection and Response for Business Suites key?
Read more
Issue:
How to release a license to free up the subscription usage for a Endpoint Detection and Response for Business Suites subscription key?
Resolution:
For Client Security/Server Security 16.x, you can do the following through the Policy Manager Console:
1. Select the target domain.
2. Go to the Settings tab, and in Standard view, select Windows > Endpoint Detection and Response.
3. Uncheck Activate Endpoint Detection and Response module.
4. Distribute the policyFor Client Security 15.20 and Server Security 15.10 and later, we recommend having Client Security / Server Security 15.30 together with hotfix03 installed, to have the full support of activation/reactivation.
The hotfix03 can be downloaded at https://download.withsecure.com/corpro/cs/cs15.30/fscs1530-hf03-signed.jar
Also, to free up the subscription usage for the client older than Client Security 15.20 and Server Security 15.10, you need to uninstall the product from the device using the normal uninstallation method.
Next, you need to remove the Endpoint Detection and Response subscription key you have entered into the Policy Manager Console at Settings (Standard view) > Endpoint Detection and Response > Sensor activation. After removing the subscription key, distribute the policy (Ctrl + D).
Last, you need to remove the inactive device from the Elements Security Center. To remove a device from the portal, you need to do the following:
- Select Environment
- Select Devices
- Select the devices (a menu will appear from the bottom of the page)
- Click Remove device and confirm that you want to remove the device
NOTE: If you have both Elements Endpoint Protection devices and Business Suite EDR devices on the devices list, you can use the filter "Subscription type" or "Subscription key" to show only the corresponding devices.
-
How to schedule Business Suite Software Updater to install updates automatically to Client Security and Server Security devices?
Read more
Issue:
How to schedule Business Suite Software Updater to check missing updates and install updates automatically to computers with Client Security and servers with Server Security?
Resolution:
By default Business Suite Client Security and Server Security scan for missing Software Updater updates at Windows startup and then once per day. You can change the rescanning time by following these steps:
- Log in to the Policy Manager Console
- Select a host or policy domain from the Domain Tree
- Go to the Settings tab
- Navigate to the Windows > Software updater settings page
- In the General section, modify the Maximum rescanning period
- Distribute the policy (Ctrl +D)
By default, installation of software updates is manually triggered by the Policy Manager administrator or by the local user if they have been given the "Show Software updater options to users" rights. To automatically install updates:
- Log in to the Policy Manager Console
- Select a host or policy domain from the Domain Tree
- Go to the Settings tab
- Navigate to the Windows > Software updater settings page
- Scroll down to the Automatic installation section and change the Install updates automatically to one of the following
- All security
- Critical and important
- Critical
- All missing
- Then from the "Install every" and "installation time" drop-down menus you can select the appropriate installation date and time
- Distribute the policy (Ctrl + D)
You can exclude specific updates from being automatically installed with the "Exclude software from automatic installation" feature. Note that this does not hide the update itself, so the installation of the update can still be manually triggered by the Policy Manager administrator or by the local user.
You may also refer to our User Guide regarding Business Suite Software Updater feature.
-
How to migrate the Policy Manager Server to the new Windows Server?
Read more
Issue:
How to move the WithSecure Policy Manager Server to the new Windows Server?
Resolution:
Follow these steps to transfer the WithSecure Policy Manager Server to a new server.
- Backup the current Policy Manager database from the old server:
- Stop the Policy Manager Server service
- Policy Manager 15: net stop fsms
- Policy Manager 16: net stop wspms
- Create a backup of the following directory:
- Policy Manager 15: C:\Program Files (x86)\F-Secure\Management Server 5\data\
- Policy Manager 16: C:\ProgramData\WithSecure\NS\Policy Manager\Policy Manager Server\Data\
- Stop the Policy Manager Server service
- Start the Policy Manager Server service on the old server:
- Policy Manager 15: net start fsms
- Policy Manager 16: net start wspms
- Install the Policy Manager Server on to the new server
- Apply the back-up copy of the Policy Manager database folder to the new Policy Manager server:
- Stop Policy Manager Server service
- Policy Manager 15: net stop fsms
- Policy Manager 16: net stop wspms
- Replace the directories with the back-up versions from step:
- Policy Manager 15: C:\Program Files (x86)\F-Secure\Management Server 5\data\
- Policy Manager 16: C:\ProgramData\WithSecure\NS\Policy Manager\Policy Manager Server\Data\
- Restart Policy Manager Server service:
- Policy Manager 15: net start fsms
- Policy Manager 16: net start wspms
- Stop Policy Manager Server service
- Configure both, new and old, Policy Manager Server address value in the policy to point to the new Policy Manager Server:
- Open Policy Manager Console
- Select a host or policy domain from the domain tree
- Go to Settings > Windows > Centralized management
- In the Policy Manager Server address text field, type in the new Policy Manager Server address and in the respective HTTP/HTTPS text fields the designated values for these ports
- Set the padlock icons tailing these text fields to the locked position, which will ensure to enforce the new value
- Distribute (Ctrl+D) the new policy
Once the managed hosts have fetched the new communication settings from the old Policy Manager, they will start to communicate with the new Policy Manager Server.
Note #1: If the WithSecure clients continue communicating with the old Policy Manager Server, be sure to verify connectivity from the clients to the new Policy Manager Server's designated ports (HTTP/HTTPS).Note #2: If the new host will preserve the DNS name of the old Policy Manager Server host and you are using that address the as main management server address, you can simply paste the H2-Database file from step 1 to the new Policy Server Manager host.
- Backup the current Policy Manager database from the old server:
-
How to scan files that are linked by symbolic link in Linux Security 64?
Read more
Issue:
How to scan files that are linked by symbolic link in Linux Security 64?
Resolution:
Realtime scan is able to scan symbolic link, as long as the target file's original location is included in RTS scan target. For manual scan (using remote command from PMC) and schedule scan, symbolic link will not be scanned. For fsanalyze, we need to use "--follow" or "-L" option in order to scan the target file's original location.
-
How to configure F-Secure Policy Manager Server to listen on multiple TCP ports for HTTPS traffic
Read more
Issue:
In default configuration, Policy Manager Server listens to HTTPS traffic on port 443. However, if there is a requirement for changing this port, clients connected to the Policy Manager may end up in state where they are no longer able to communicate with the server.
Resolution:
This article describes, how to configure port forwarding on the server running windows. Effectively, this allows the Policy Manager Server to listen to multiple TCP ports.
To accomplish this, we use "Netsh interface portproxy " documented here.
Also ensure, the correct listening port is provided in the Policy Manager policy.
The following command forwards TCP port traffic from port 443 to port 444. (Note: PMS=Policy Manager Server):
-
C:> netsh interface portproxy add v4tov4 listenaddress=<insert PMS IP address> listenport=443 connectaddress=<insert PMS IP address> connectport=444
To print the current settings:
-
C:> netsh interface portproxy show all
To remove the netsh portproxy forward from port 443 to 444:
-
C:> netsh interface portproxy delete v4tov4 listenport=443 listenaddress=<insert PMS IP address>
Remember to ensure, all configured TCP ports are open in the windows firewall on the server hosting PMS.
-
-
How to mass uninstall Client Security or Server Security hosts using Policy Manager Console?
Read more
Issue:
How to centrally remote mass uninstall Client Security or Server Security from several / multiple hosts at the same time using Policy Manager Console / Server?
Resolution:
Business Suite (Client Security and Server Security) has a remote uninstallation operation feature, which can be used to uninstall the product remotely from Windows hosts. Mac or Linux hosts require manual local uninstallation using an uninstallation tool.
- Log in to the Policy Manager Console
- Go to the Installation tab
- Select a host or policy domain from the domain tree
- Click on the uninstall button from the "Installed products summary" table
- Distribute the policy (CTRL + D)
Once the host receives the operation, the Client Security or Server Security client will be silently uninstalled from the host.
Note: For the uninstall button to appear on the "installed products summary" table, you will need to have the .jar file of that particular Client Security or Server Security version imported in the Policy Manager Server's installation packages.
-
How to install Client Security or Server Security 15.30 with Endpoint Detection and Response for the Citrix/XenApp environment
Read more
Issue:
How to install Client Security or Server Security 15.30 with Endpoint Detection and Response for the Citrix/XenApp environment ?
Resolution:
Installation steps:
- Install Client Security / Server Security 15.30 to the master without EDR keycode distributed to it
- Wait for OK in [ProtectionStatus] (See Note)
- Apply the FSCS1530-HF03 hotfix from support, so that the clones have this binary updated.
- Hotfix is required for all kind of "cloned" setups. This is required for VMWare, Xen, HyperV and many more scenarios.
- Make it as a master image
- Create (a) clone(s), import them to the subdomain with the EDR keycode, wait for the clones to register
Note: Starting from Client Security 15.20, a registry key was introduced to avoid broken installations when creating images:
- HKLM\SOFTWARE\WOW6432Node\F-Secure\NS\default\OneClient\CosmosMirror\ProtectionStatus
Must be checked for all kind of installations. This is not limited to XEN or software distribution using image files. All kind of (managed) installations must ensure not to reboot directly after MSI finishes.
Monitor registry HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\F-Secure\NS\default\OneClient\CosmosMirror\[ProtectionStatus] as soon as it is changed to OK, all updates are installed and ready to go.