Views:
Workload Security on Linux allows you to define how much CPU Deep Security Agent can use.
This functionality is only available if Application Control is disabled. If Application Control is enabled, the agent is forced into an unlimited CPU usage and a warning is displayed on Overview > General.
Before defining CPU usage by the agent, you should check the cgroups CPU support status with your Linux operating system provider.
You can configure CPU usage via the Workload Security console, as follows:
  1. Open the Computer where you want to enable the agent CPU usage control.
  2. Click Settings → General.
  3. Under CPU Usage Control, select either a specific percentage or Unlimited. Note that setting this to any value other than Unlimited has a negative impact on performance during detection.
There is a backward compatibility with the earlier agent versions (see Legacy implementation):
CPU usage range
CPU usage label (legacy)
5% ~ 50%
Extremely Low
55% ~ 95%
Low
Unlimited
Unlimited

Legacy implementation Parent topic

The Workload Security agent CPU usage control was available for earlier versions of Linux agents with Anti-Malware and Activity Monitoring enabled.
The protection levels were the following:
Extremely Low
Function
Protection details
Limitations
Anti-Malware
Asynchronous deferred real-time scan for newly created and modified files.
Cannot be enabled or disabled for Predictive Machine Learning and Behavior Monitoring via Anti-Malware → General → Real-Time Scan → Malware Scan Configuration → Edit.
Activity Monitoring
Loss of activity logs of the busiest events based on their environment if the CPU usage is higher than 10%.
Low
Function
Protection details
Limitations
Anti-Malware
Synchronous real-time scan for newly created and modified files within a certain time period as well as executable files.
Activity Monitoring
Loss of activity logs of the busiest events based on their environment if the CPU usage is higher than 40%.
Unlimited
Function
Protection details
Limitations
Anti-Malware
Full protection via a real-time scan (default).
Activity Monitoring
No loss of activity logs of busiest events.