Proactive Defense
117
Proactive Defense analyzes the following operations involving critical applica-
tions: their launch, changing the makeup of application modules, and starting an
application as a child process. You can select the Proactive Defense response to
each of the operations listed (allow or block the operation), and also specify
whether to log component activity in the component report. The default settings
allow most critical operations are allowed to start, be edited, or be started as
child processes.
To add an application to the critical application list and create a rule for it:
1. Click
Add
on the
Critical applications
tab. A context menu will open:
click
Browse
to open the standard file selection window, or click
Appli-
cations
to see a list of currently active applications and select one of
them as necessary. The new application will be added to the top of the
list, and allow rules (i.e. all activities are allowed) will be created for it by
default. When that application is first started, the modules that it ac-
cesses will be added to the list, and those modules will similarly be giv-
en allow rules.
Figure 38. Configuring Application Integrity Control
2. Select a rule on the list and assign rule settings in the lower portion of
the tab:
