Support articles
Find clear, step-by-step solutions to common WithSecure issues across installation, configuration, updates, and product performance.
Slowness and system performance issues when using WithSecure Linux Security 64 or Linux Protection when the real time scanning is enabled.
Last updated
Issue:
Slowness and system performance issues when using WithSecure Linux Security 64 or Linux Protection when the real time scanning is enabled. How can I check which file or directories are being scanned? Is there any setting to to limit the CPU usage?
Resolution:
It is typical for Linux Security 64 or Linux Protection to take up a higher CPU usage during the scanning when other applications are consuming less system resources so that it could be completed as soon as possible. This is an expected behavior.
If there are other applications or services that require CPU resources, normally system resources will be shared among all running applications including Linux Security or Linux Protection.
If real time scanning is constantly running, it means that some applications are constantly processing files or are having frequent file and directory accesses. In such situation, generally we would recommend to have those frequent accessed files and directories to be excluded in the policy.
If you are not sure or would like to check which files or directories that are causing the high CPU usage, there is a need to enable the trace logging for the real time scanning of WithSecure Linux Security 64 or Linux Protection in order to determine the actual files and directories that are being scanned frequently on your Linux server, which is causing the slowness or performance issue.
Follow the steps below to enable the trace logging, reproduce the issue and disable the trace logging again.
1. Enable the trace logging for on-access scanning
echo '"SEND-REQ|RETURN-ACC|CACHE-REJ"' >/etc/opt/f-secure/fsbg/mgmt/cosmos/linux/linux_security/services/fsaccd/tracing/include_regex
Note: After enabling the trace logging, the output file (trace.log) is saved to the "/var/opt/f-secure/baseguard/fsaccd/log" directory and it is rotated automatically so that there are at most ~100MB of trace*.log files at any given time.
2. Reproduce the issue and collect the trace logs from the directory above, together with the diagnostic file. Visit this article on how to create a diagnostic file.
How do I create an WSDIAG diagnostic file on Linux systems? - WithSecure™
For example:
========================================================================================
2021-04-13 13:04:39.618053 FSACCD-MAIN-RETURN-ACCESS DEV=2064 INO=11273138 PATH=/example folder 1/user/folder2/folder3/Firstname%2520lastname%2520GJ2013%2520User/DCIM/159_2706/IMG_2883.JPG VERDICT=FSACCD_VERDICT_ALLOW DURATION=0.042613673999999997
2021-04-13 13:04:39.790352 FSACCD-MAIN-RETURN-ACCESS DEV=2064 INO=11273139 PATH=/example folder 1/user/folder2/folder3/Firstname%2520lastname%%2520GJ2013%2520User/DCIM/159_2706/IMG_2884.JPG VERDICT=FSACCD_VERDICT_ALLOW DURATION=0.21417376099999999
2021-04-13 13:04:40.246659 FSACCD-CACHE-REJUVENATE DEV=2064 INO=11273139 PATH=/example folder 1/user/folder2/folder3/Firstname%2520lastname%2520GJ2013%2520User/DCIM/159_2706/IMG_2884.JPG
========================================================================================
3. Disable the trace logging for on-acces scanning
echo '"X^"' >/etc/opt/f-secure/fsbg/mgmt/cosmos/linux/linux_security/services/fsaccd/tracing/include_regex
Based on the findings from the trace logs, you could consider to exclude those frequently scanned files or directories which could improve the situation.
Currently, there is no setting or feature that could limit the CPU usage when Linux Security 64 or Linux Protection processes are running thus the exclusion setting could be considered to reduce the CPU consumption during the scanning. Other than that, you could also consider to exclude large files from scanning or disable the archive file scanning.
You could also consider inclusions by deciding the files or directories to be scanned by the real time scanning instead of scanning all files and configure to scan only executables, which will help to improve the overall scanning performance on your Linux server.
In case of scanning only executable files, you could configure it on Policy Manager Console by going to "Settings" > "Linux" > "Real-time Scanning" > "Scan only executables".
The scanning of executable files are determined based on the file permissions (execute) and if there is embedded executable code in non executable file, it will not be scanned.
Another option is to include less folders to real-time scanning, and then schedule a full manual scanning for less busy times.
Apart from that, you should also consider to increase the total amount of memory (e.g, 8GB) so that there will be enough memory to run our products and other applications on your Linux server.
If the issue still persists, you could consider to update the product components to the latest version or reinstall the product, and check if there is any improvement.
Additional information:
After enabling real‑time scanning for the root path /, the Linux endpoint started monitoring all filesystem events, including virtual system paths.
On Linux, this causes extremely high kernel event rates on monitoring servers and can lead to processes entering uninterruptible sleep, resulting in very high load without visible traffic or CPU usage.
This is expected behavior and not a defect.
Best practice is to configure real‑time scanning only for relevant executable and data paths and to explicitly exclude virtual filesystems such as /proc, /sys, /dev, and /run.
Use targeted paths only
Examples:
/usr
/bin
/sbin
/lib
/lib64
/var/lib
/var/www
/home
Explicitly exclude virtual and volatile filesystems
Always exclude:
/proc
/sys
/dev
/run
/tmp
/var/run
/var/cache
Monitoring servers (checkmk / nagios)
Additionally exclude:
/var/lib/check_mk
/usr/lib/check_mk
Why this does not reduce security
- Malware rarely persists in /proc, /sys, or /run
- Executables live in well‑defined directories
- On‑access scanning of real executables + user‑writable paths provides effective protection
- Full scans (scheduled or manual) can still include broader coverage if needed