Help Center> Host Security Service (Old)> FAQs> Alarm and Event Management> Intrusions> Why a Process Is Still Isolated After It Was Whitelisted?
Updated on 2022-08-11 GMT+08:00

Why a Process Is Still Isolated After It Was Whitelisted?

After you add a process to the whitelist, it will no longer trigger certain alarms, but its isolation will not be automatically canceled.

Isolating and Killing a Malicious Program

  • Choose Installation and Configuration and click the Security Configuration tab. Click the Isolation and Killing of Malicious Programs tab and enable this function.
  • Choose Intrusions > Events. In the Events area, manually isolate and kill malicious programs.

If a program is isolated and killed, it will be terminated immediately and no longer able to perform read or write operations. Isolated source files of programs or processes are displayed on the Isolated Files slide-out panel and cannot harm your servers.

Canceling the Isolation of Files

  • Choose Intrusions > Events. Click Isolated Files in the upper right corner. Cancel the isolation of the whitelisted file.
  • Choose Intrusions > Events. In the Events area, manually cancel the isolation and killing of the whitelisted file.

After you cancel isolation, the read/write permissions of files will be restored, but terminated processes will not be automatically started.

Intrusions FAQs

more