-
Is it possible to create a read-only account to login into Policy Manager Console?
Issue: Is it possible to create a read-only account to login into Policy Manager Console? How to create an account to login to Policy Manage Console? Resolution: If you want to limit a user's access, you can add users with either admin or read-only access to Policy Manager. The process is described in this user…
-
Login to Email and Server Security 14.x/15.x Web Console not working, page not displayed
Issue: When I am trying to login to the Email and Server Security 14.x or 15.x WebUI (Web Console) via the browser using the address https://127.0.0.1:25023 or https://localhost:25023, a message is shown that the page cannot be displayed. Resolution: Set up the Binding in Internet Information Services (IIS) Manager To…
-
Login to Email and Server Security Web console fails with error "Request failed with Status code 401"
Issue: Login to Email and Server Security Web console fails with error "Request failed with Status code 401" Resolution: If the Web Console session was opened for a long time, please terminate the current session and start the Browser as administrator to access the Web Console. The HTTP 401 Unauthorized client error status…
-
Linux Security 64: How to configure daily schedule scan using lsctl command?
Issue: Linux Security 64: How to configure daily schedule scan using lsctl command? Resolution: Run the following commands to enable schedule scan on everyday. # /opt/f-secure/linuxsecurity/bin/lsctl set ods schedule weekly_schedule monday true # /opt/f-secure/linuxsecurity/bin/lsctl set ods schedule weekly_schedule…
-
Linux Security 64: How to check schedule scanning log message's "Severity" and "Facility"?
Issue: How to check schedule scanning log message's "Severity" and "Facility"? lspmd-start: alert [source=schedule scan]: path=/root/download/eicar.txt.malware; action=rename; infection=EICAR_Test_File Resolution: If you run journalctl with "-o verbose" you can see priority and facility for each log message. For lspmd's…
-
Linux Security 64: Installation failure with error "activate: No such file or directory" when mounted "/var/opt/f-secure" as separate filesystem
Issue: Linux Security 64: Installation failure with error "activate: No such file or directory" when mounted "/var/opt/f-secure" as separate filesystem # bash f-secure-linuxsecurity/f-secure-linuxsecurity-installer f-secure-linuxsecurity/f-secure-linuxsecurity-installer: line 68: /opt/f-secure/linuxsecurity/bin/activate:…
-
Linux Security 64 "Master-Switch" command cannot stop/start the process/service
Issue: Linux Security 64 "Master-Switch" command cannot stop/start the process/service since after update, Linux Security 64 (12.0.222), BaseGuard (1.0.532) and FSBG (1.0.508). This problem is not happening in PSB mode/Standalone mode. Resolution: This problem is happening due to policy setting in LS64. * Login to Policy…
-
Launching a manual scan (fsanalyze) as a non-root user fails with an error message on Linux Security 64
Issue: I launched a manual scan(fsanalyze) as a non-root user in Linux Security 64(LS64) and it fails with the following error: fsanalyze: failed to connect to pmd:failed to connect to ctrl socket: /opt/f-secure/linuxsecurity/var/lspmd/run/socket: Permission denied Resolution: When a non-root user executes the fsanalyze…
-
Linux Security 64 failed to be installed successfully and the installation process is stuck at "Installing BaseGuard" stage
Issue: Linux Security 64 failed to be installed successfully and the installation process is stuck at "Installing BaseGuard" stage Resolution: During the installation of Linux Security 64, it will connect to the Policy Manager Server and check for the latest database updates. If Policy Manager Server does not have the…
-
Linux Security 64 Failed to Activate in SELinux (Permissive Mode)
Issue: Linux Security 64 failed to activate with error message "SELinux integration for F-Secure Linux Security 64 is supported only with the 'targeted' policy on this system (detected policy: ''). Installation is successful. Resolution: Root cause is due to missing "SELINUXTYPE=targeted" Example from /etc/selinux/config #…