Mcafee Application Control 8.2.0 - Windows Product Guide 3-18-2020 PDF

McAfee Application Control 8.2.
0 -
Windows Product Guide
Contents
Product overview 7
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Key features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
How it works in a managed environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
How it works in a standalone environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Using Application Control 11

Application Control modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Enabling the software using McAfee ePO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Enabling the software in a standalone environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Add the license. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Create the whitelist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Place Application Control in Enabled mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Run CLI commands on McAfee ePO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Use the command-line interpreter in a standalone environment. . . . . . . . . . . . . . . . . . . . . 14
Methods for allowing execution of files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Checks that Application Control runs for a file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Allow or block an executable file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
File and certificate reputation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Reputation sources and communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Reputation values received from sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
McAfee ePO workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Endpoint workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
How reputation is computed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Change file reputation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Memory-protection techniques. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Configuring CASP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Configuring bypassing rules for NX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Configuring Forced DLL Relocation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Using checksum values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Authorize binaries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Ban binaries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Remove authorized or banned binaries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Authorize execution of binaries by name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Ban execution of binaries by name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
View authorized and banned binaries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Remove authorized and banned rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Using trusted directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Add trusted directories in a managed environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Add trusted directories in a standalone environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Specifying directory paths. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
View trusted directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Exclude specific directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Remove trusted directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Using rule groups in a managed environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
What are rule groups?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Manage rule groups and policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Using execution control rules in a standalone environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Defining attribute-based rules for file execution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Add attribute-based rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Remove attribute-based rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
View attribute-based rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Using certificates in a managed environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
What are certificates?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Add certificates in a managed environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Search for a certificate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Verify assignments for a certificate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Add a certificate to a policy or rule group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Using certificates in a standalone environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Add certificates in a standalone environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Extracting certificates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
View certificates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Remove certificates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Using updaters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
What are updaters?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Script as Updater feature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Add updaters in a managed environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Add updaters in a standalone environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Discover potential updaters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
View updaters in a standalone environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Remove updaters in a standalone environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Configure processes and certificates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Using interpreters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Map an interpreter with a file extension. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
View interpreter and file extension associations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Remove interpreter and file extension associations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Using installers in a managed environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
What are installers?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Add an installer to McAfee ePO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Add an installer to a policy or rule group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Verify assignments for an installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
McAfee Application Control 8.2.0 - Windows Product Guide 3

Configure Package Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Using events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
What are events?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
View and manage events in a managed environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
View and manage events in a standalone environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Customize end-user notifications on McAfee ePO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
List of events in McAfee ePO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
List of events in standalone mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Managing the inventory with McAfee ePO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
How the inventory is updated. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Configure inventory updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Configure settings for fetching the inventory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Fetch the inventory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Export SHA-1s. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Run the Offline GTI tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Import the GTI result file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Set enterprise reputation for files and certificates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Review the inventory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Manage the inventory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Define filters for inventory data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Create an approved repository of known applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Compare the inventory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Using dashboards and queries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Dashboards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Queries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
View queries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Using trusted users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
What are trusted users?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Add trusted users in a managed environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Add trusted users in a standalone environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
List trusted users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Remove trusted users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Deploying Application Control in Observe mode 84

What are observations?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Managing Observe mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Configure processes and certificates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Place endpoints in Observe mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Policy discovery permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Allow non-global administrators to manage enterprise-wide requests. . . . . . . . . . . . . . . . . . . . . . . . . 86
Managing requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Review requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Allow a file on all endpoints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Allow a file by certificate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
4 McAfee Application Control 8.2.0 - Windows Product Guide

Allow network files on all endpoints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Ban by SHA-1 or SHA-256 on all endpoints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Define rules for specific endpoints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Allow by adding to whitelist for specific endpoints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Define bypass rules for all endpoints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Change file reputation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Delete requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Define filters for observations and events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Define filters for user comments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Throttling observations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Define the threshold value for throttling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Review filter rules for throttling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Restart observation generation for throttling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Exit Observe mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Self-approval requests 94
What is self-approval?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Enable self-approval on endpoints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Self-approval dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Policy discovery permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Allow non-global administrators to manage enterprise-wide requests. . . . . . . . . . . . . . . . . . . . . . . . . 95
Review approval requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Process approval requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Allow a file on all endpoints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Allow a file by certificate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Ban by SHA-1 or SHA-256 on all endpoints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Define rules for specific endpoints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Allow by adding to whitelist for specific endpoints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Change file reputation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Delete requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Maintaining your system with McAfee ePO 100

Monitoring enterprise health. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Review congestion status and trend. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Configure notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Make emergency changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Place the endpoints in Update mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Place the endpoints in Enabled mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Administering throttling for your enterprise. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Set up throttling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Configure throttling values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Manage throttling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Identify endpoints where throttling is initiated. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Review throttling status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Process data where throttling is initiated. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Configure CLI breach notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Change the CLI password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Collect debug information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Place the endpoints in Disabled mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Sending McAfee GTI feedback. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Configure server tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Purge reporting data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Maintaining your system in standalone mode 109

View product status and version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Manage the whitelist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Configure whitelist thread priority. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Add and remove components from the whitelist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
View whitelisted files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Check and update the status of whitelisted components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Review product features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Enable or disable features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Package Control feature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Configure Package Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Making emergency changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Switch to Update mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Exit Update mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Enable or disable password protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Reviewing changes using events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Configure event sinks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Set the event cache size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Define the limits for the event cache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
View events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Configuring log files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Disable Application Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Using the command-line interface 121

List of Commands for Application Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Command short forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Argument details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Product overview

Overview
McAfee® Application Control blocks unauthorized executables on servers, corporate desktops, and fixed-function devices.
Application Control uses dynamic whitelisting to guarantee that only trusted applications run on servers, devices, and desktops.
It eliminates the need for IT administrators to manually maintain lists of approved applications. It also gives IT control over
endpoints to help enforce software license compliance.
The software uses a dynamic trust model and innovative security features to prevent advanced persistent threats (APT) without
requiring signature updates. It guarantees protection without impacting productivity.
With Application Control, you can:
• Prevent any malicious, untrusted, or unwanted software from being executed.
• Automatically identify trusted software and grant it authorization to run.
• Block users from introducing software that poses a risk to your company.
Important: You can deploy Application Control in a managed McAfee® ePolicy Orchestrator® (McAfee® ePO™) environment or
in an unmanaged environment, also called standalone, or self-managed.
Key features
Application Control protects your organization against malware attacks before they occur by proactively controlling the
applications that run on your desktops, laptops, and servers. It enforces control on connected or disconnected servers, virtual
machines (VMs), and endpoints.
Dynamic whitelisting
Application Control protects your organization against malware attacks before they occur by proactively controlling the
applications that are executed on your system.
You can manage your whitelist in a secure and dynamic way. IT administrators don't need to manually maintain lists of approved
applications. Application Control groups executables (binaries, libraries, and drivers) across your company by application and
vendor.
You can easily search for useful information such as:
• Applications added this week
• Uncertified binaries
• Systems running outdated versions
• Files with unknown reputations (in a McAfee ePO managed environment only)
Protection against threats

Application Control extends coverage to executable files, libraries, drivers, Java applications, ActiveX controls, and scripts for
greater control over application components. It enforces control on connected or disconnected servers, virtual machines,
endpoints, and fixed devices, such as kiosks and point-of-sale (POS) terminals. It also locks down protected endpoints against
threats and unwanted changes, with no file system scanning or other periodic activity that might impact system performance.
Advanced memory protection

Application Control offers multiple memory-protection techniques to prevent zero-day attacks. Memory-protection techniques
provide extra protection over the protection from native Windows features or signature-based buffer overflow protection
products. These techniques also prevent whitelisted applications from being exploited by memory buffer overflow attacks on
Windows 32-bit and 64-bit systems.
Knowledge acquisition
Application Control allows you to switch to Observe mode to discover policies for dynamic desktop environments without
enforcing a whitelist lockdown. This mode helps you deploy the software in pre-production environments without affecting the
operation of existing applications.
Note: This feature is available only in a McAfee ePO managed environment.

Reputation-based execution
Application Control integrates with a reputation source to receive reputation information for files and certificates. Based on the
reputation received from one of these sources, Application Control allows or bans the execution and software installation.
Centralized management
Application Control integrates with McAfee ePO software for consolidated and centralized management, and a global view of
enterprise security from a single console.
How it works in a managed environment

Application Control creates a whitelist of all authorized executable files. When you run an executable file that isn't whitelisted,
Application Control checks the reputation of the file and allows or blocks its execution.
1. A user or application tries to execute a file on a managed endpoint where Application Control and McAfee® Agent are
installed.
2. Application Control checks the reputation of the file and allows or blocks its execution.
3. Application Control communicates with the McAfee® Threat Intelligence Exchange (TIE) servers to receive reputation
information for the file and any associated certificates. Based on this information, Application Control allows or blocks the file
execution.
4. If the TIE server is unavailable, Application Control communicates with the McAfee® Global Threat Intelligence™ (McAfee GTI)
server to fetch the reputation of the file.
5. McAfee® Data Exchange Layer (DXL) provides the framework for communication between Application Control and TIE or
McAfee GTI, so products can share threat information.
6. The administrator manages all endpoints, deploys policies, creates rules, adds certificates, manages the inventory, monitors
activities, and approves requests.
7. Information about the attempt to run the application is sent to the McAfee ePO server, where it appears in a dashboard,
report, or log.
How it works in a standalone environment

Application Control creates a whitelist of all authorized executable files. When you run an executable file that isn't whitelisted, the
software blocks its execution.

The whitelist details authorized files and determines trusted or known files. In Enabled mode, only files that are present in the
whitelist are allowed to run. All files in the whitelist are protected and can't be changed or deleted. An executable binary or script
that isn't in the whitelist is said to be unauthorized and is prevented from running.
Application Control stores the whitelist for each drive or volume at the following location:
• <drive>\Solidcore\scinv
Here is a list of the types of files included in the whitelist.
• Binary executables (.exe, .sys, and .dll files)
• Script files (such as .bat, .cmd, and .vbs files)
Note: When the whitelist is created for Windows, Application Control doesn't include system-specific files that are protected by
the operating system. For example, pagefile.sys and hiberfil.sys.
When you execute a file on a system with a whitelist, Application Control compares the checksum and path of the binary with the
checksum and path stored in the whitelist and allows the execution only if the checksum value and path match.

Using Application Control
Application Control modes
Application Control ensures that only legitimate and authorized applications run on the system. It can operate in four different
modes. Each mode is different in principle and usage.
Disabled mode
This mode indicates that Application Control isn't running on your system. Although the application is installed, its features are
disabled. After installation, the application appears in Disabled mode by default. You can then switch to Observe, Update, or
Enabled mode.
Enabled mode in a standalone environment

This mode indicates that only whitelisted applications and files are allowed to run. Execution of unauthorized software, such as a
virus or spyware, is prevented. In Enabled mode, Application Control protects files in the whitelist from unauthorized change.
After the initial whitelist is created, switch to Enabled mode which makes sure that no unauthorized changes are allowed.
Enabled mode in a managed environment

This mode indicates that Application Control is running and protection is enabled. Enabled mode supports reputation-based
execution. When you execute a file, Application Control fetches its reputation and that of all certificates associated with the file to
determine whether to allow or ban the file execution. Application Control works with TIE Server and McAfee GTI to fetch
reputation information for a file.
These are the available reputation values:
• Trusted files— If the reputation is trusted, the file is allowed to run, unless it is blocked by a predefined ban rule. No
observation or event is generated.
• Malicious files— If the reputation is malicious, the file isn't allowed to run. An event is generated and displayed on the Solidcore
Events page. You can configure the reputation values that are banned in your endpoints. You can ban Known Malicious, Most
Likely Malicious, Might be Malicious files, or all malicious files.
• Unknown— If the reputation is unknown, reputation values aren't used to determine execution. Instead, Application Control
performs other checks to determine whether to allow or block the file.
In Enabled mode, Application Control:
• Allows only trusted (based on reputation) or authorized (based on rules) applications and installers to run on servers and
endpoints.
• Protects against memory-based attacks and application tampering.
Regardless of the file's reputation, if a ban by name, SHA-1, or SHA-256 rule exists for an executable file, its execution is banned.
No corresponding observation is generated. A corresponding event is generated and displayed on the Solidcore Events page.
Observe mode
This mode indicates that Application Control is running but it only monitors and logs observations. The application does not
prevent any execution or changes made to the endpoints. Instead, it monitors execution activities and compares them with the
local inventory and predefined rules.
Observe mode also supports reputation-based execution. When you execute a file, Application Control fetches its reputation and
that of all certificates associated with the file to determine whether to allow or ban the file execution.
All files that are allowed to run in Observe mode are automatically added to the whitelist, if not already present in the whitelist.
An observation is logged that corresponds to the action Application Control takes in Enabled mode.
Important: This mode is available only in a McAfee ePO managed environment.
Update mode
This mode indicates that protection is effective but changes are allowed on protected endpoints. When you perform software
updates in Update mode, Application Control tracks and records each change. Also, it dynamically updates the whitelist to make
sure that the changed or added binaries and files are authorized to run when the system returns to Enabled mode. In Update
mode, all changes are tracked and added to the whitelist. If you delete any software and program files from the system, their
names are also removed from the whitelist.

In a managed environment, Update mode supports reputation-based execution. When you execute a file at an endpoint, the
software fetches the file's reputation and the reputation of all associated certificates to determine whether to allow or ban the
file execution.
Tip: Best practice: Use Update mode only for Installing minor software updates. For example, define an interval to allow the IT
team to complete maintenance tasks, such as install patches or upgrade software.
Switching between modes

• From Observe mode, you can switch to Enabled or Disabled mode.
• From Enabled mode, you can switch to Disabled, Update, or Observe mode.
• From Update mode, you can switch to Enabled or Disabled mode.
• From Disabled mode, you can switch to Enabled, Update, or Observe mode.
Enabling the software using McAfee ePO

When Application Control is running in Enabled mode, the only programs that are allowed to run are trusted and authorized.
Malicious or unauthorized programs are not allowed to run.
Before you begin

If your endpoints are running in Disabled mode, use the SC: Pull Inventory client task to fetch the inventory before placing them in
Enabled mode. This ensures that the inventory is updated to prevent any mismatch.
Task
1. On the McAfee ePO console, select Menu → Systems → System Tree.
2. Select a group or an endpoint:
◦ Group — Go to System Tree and click the Assigned Client Tasks tab.
◦ Specific endpoint — On the Systems tab, select the endpoint you want to work with and click Actions → Agent → Modify Tasks on a
Single System.
3. Click Actions → New Client Task Assignment to open the Client Task Assignment Builder page.
a. For Product, select Solidcore 8.x.x.
b. For Task Type, select SC: Enable.
c. For Task Name, click Create New Task to open the Client Task Catalog page.
d. Enter the task name and add any descriptive information.
e. Select the platform and sub-platform, then select Application Control.
4. Based on the sub-platform, perform these actions, then click Save.
◦ Windows NT/2000 — Select Reboot endpoint to restart the endpoints when solidification is complete, which enables the
software.
◦ All except NT/2000
◦ Select the initial scan priority of the thread that creates the whitelist on the endpoints:
◦ Low — Minimal performance impact
◦ High — Faster results
◦ Select an option for activation
◦ Limited Feature Activation — Endpoints aren't restarted and limited features of Application Control are activated.
Memory Protection and Script As Updater (SAU) features are available only after the endpoint is restarted.
◦ Full Feature Activation — Endpoints are restarted, whitelist created, and all features including Memory Protection are
active.
◦ (Optional) Select Start Observe Mode to place the endpoints in Observe mode.
◦ (Optional) Select Pull Inventory to manage the inventory with McAfee ePO.
Five minutes before the endpoint is restarted, a message is displayed at the endpoint to allow the user to save important work
and data.
5. Click Next to open the Schedule page.
6. Specify scheduling details, then click Next.
7. Review and verify the task details, then click Save.
8. (Optional) Wake up the agent to send your client task to the endpoint immediately.

Enabling the software in a standalone environment
Add the license
The license determines if the product features are available.
You can specify the license during or after installation.
Task
1. Verify if a license is already added by entering the following command and pressing Enter.
◦ sadmin license list
All licenses that are already installed on the system are listed.
2. If no license is listed, add a license now: sadmin license add <license_key>
3. Restart Application Control.
a. net stop scsrvc
b. net start scsrvc
Create the whitelist

Application Control creates a whitelist of authorized executable files. When you run an executable file that isn't whitelisted,
Application Control blocks its execution.
Task
1. Run this command at the command prompt.
sadmin so
The time the system takes to create the whitelist varies from a few minutes to an hour, depending on your system
configuration, including CPU speed, RAM, and applications installed on the system. After the whitelist is created, a message
similar to this message appears.
Solidifying volume C:\
00:04:11: Total files scanned 12265, solidified 6342
2. Verify that the drive or volume is whitelisted.

a. Run this command at the command prompt.
sadmin status
The status of Application Control is displayed. You can view the operational mode, operational mode on system restart,
connectivity with McAfee ePO, CLI access status, and whitelist status of the drives or volumes. However, in the standalone
configuration of the product, connectivity with McAfee ePO is not applicable.
b. Review the whitelist status of the drives or volumes, and make sure that the status is Solidified.
Place Application Control in Enabled mode

Place Application Control in Enabled mode to allow only whitelisted applications to run on your system.
Task
sadmin enable
2. Place Application Control in Enabled mode using one of these methods:
◦ Restart the system to enable Application Control, memory protection feature and Script As Updater (SAU) feature.
◦ Restart the Application Control service to enable the software without the memory protection feature: net stop scsrvc or
net start scsrvc
3. Verify that Application Control is in Enabled mode: sadmin status.

The status is displayed. You can view the operational mode, operational mode on system restart, CLI access status, and
whitelist status of all drives.
a. Review the operational mode.
b. Verify that the current operational mode is Enabled.

Run CLI commands on McAfee ePO
You can run CLI commands on the Solidcore client and send them to the endpoint.
Task
2. Select a group or an endpoint, then go to Actions → Agent → Run Client Task Now.
3. Under Product, select the version of Solidcore you want, then under Task Type, select SC: Run commands and click Create New Task.
4. Next to Run Commands enter the command you want.
5. Select Requires Response to receive a response from the selected endpoint.
6. Click Run Task Now.
Note: Go to Menu → Solidcore Client Task Log to see messages received from the endpoint.
Use the command-line interpreter in a standalone environment

The command-line interpreter (sadmin) allows you to manage the Application Control configuration and features.
The method you use to open the command-line interpreter depends on your operating system.
Task
1. To open the command-line interpreter on Windows:
◦ On Windows 2008, Windows 2008 R2, Windows 2012, Windows 8, Windows 8.1, Windows 10, and Windows 7 (with UAC
enabled) platforms, right-click the McAfee Solidifier Command-line icon on the desktop and select Run as administrator.
◦ On other Windows platforms, double-click the McAfee Solidifier Command-line icon on the desktop.
◦ Click Start → Programs → McAfee → Solidifier → McAfee Solidifier Command Line menu option.
2. Use these commands to get help information:
◦ sadmin help — Lists basic help information.
◦ sadmin help <command> — Provides basic help for the specified command.
◦ sadmin help-advanced <command> — Provides advanced help for the specified command.
Methods for allowing execution of files

Application Control accepts new software only when it is added through an authorized process. This dynamic trust model allows
you to configure what can run on devices in your environment.
Before allowing or blocking a file, Application Control considers the file reputation and whether it is added to the whitelist, and
checks other existing rules.
Reputation
Application Control supports reputation-based execution. When you run an executable file, Application Control checks the
reputation of the file and its associated certificates and allows or blocks the file execution based on the reputation settings.
Important: Reputation information is available only in a McAfee ePO managed environment.
Whitelist
Application Control creates a whitelist of executables (binaries, libraries, and drivers) and script files. The whitelist includes all
authorized files and determines trusted or known files. All files in the whitelist are protected and cannot be changed or deleted.
In Enabled mode, only executables or script files included in the whitelist or files with trusted reputation are allowed to run.
Other methods
Application Control provides multiple other methods to authorize execution of a program or file on a protected endpoint. To
design a trust model and allow additional users or programs to execute or change files on a protected endpoint, you can use one
these methods on endpoints running in Enabled mode.
• Updater process — An application allowed to update the endpoint
• Executable file — An executable file allowed or restricted from running on the endpoints
• Certificate — A trusted certificate (associated with a software package) that is permitted to install and change files on a
protected endpoint.

• Installer — An application identified by its SHA-1 or SHA-256 that is allowed to install or update software.
• Directory — A trusted directory (local or network share) identified by its Universal Naming Convention (UNC) path.
• Authorized user — An authorized Windows user with rights to dynamically add files and applications to the whitelist.
Checks that Application Control runs for a file

When you execute a file, Application Control performs multiple checks in a set order and allows or blocks execution based on the
result.
Application Control starts with the check that has the highest precedence and moves down the list to determine whether to allow
or block the executable or script file.
Precedence Check Description
1 File unauthorized check If the file is unauthorized by name, it isn't allowed to run. This is set
by a rule.
2 Banned SHA-1 or SHA-256 If the file is banned by SHA-1 or SHA-256, it isn't allowed to run.
This is set by a rule.
3 TIE reputation Important: Reputation information is available only in a McAfee

ePO managed environment.
If the TIE server is configured, these checks are performed.
• Is the executable file signed?
◦ Yes — Application Control fetches the reputation for
all certificates associated with the file.
◦ No — Application Control uses file reputation to allow
or deny execution.
• Is reputation for associated certificates set to Unknown on the
TIE server?
◦ Yes — Application Control ignores certificate
reputation and uses file reputation to allow or deny file
execution.
◦ No — Application Control computes reputation based
on reputation of all certificates associated with the file
and it uses resultant reputation to allow or deny file
execution.
Note: Trusted reputation takes precedence over malicious
reputation when determining the resulting certificate reputation.
For example, if a file is signed by two malicious and one trusted
certificate, the file is trusted.
If the reputation for certificates associated with the file or file
reputation is:
• Known Trusted, Most Likely Trusted, Might be Trusted — The
file is allowed to run.
• Might be Malicious, Most Likely Malicious, Known Malicious
— The file is not allowed to run.
• Unknown — Certificate reputation is ignored and file reputation
is used to determine execution. Application Control continues
with the next check.
• Not set — Application Control continues with the next check.
4 File authorized check If the file is always authorized by file name, it is allowed to run. This
is set by a rule.

5 Allowed SHA-1 or SHA-256 If the file is allowed by SHA-1 or SHA-256, it is allowed to run. This
is set by a rule.
6 Allowed certificate If the certificate associated with a file is allowed, the file is allowed
to run. This is set by a rule.
Note: This check does not apply to script files.
7 McAfee GTI reputation Important: Reputation information is available only in a McAfee

These checks are performed.
• Is the file signed with one or more certificates?
◦ Yes — If reputation isn't set on the TIE server,
Application Control fetches McAfee GTI reputation for
certificates associated with the file from the TIE server
or McAfee GTI file reputation service.
◦ No — Application Control fetches file McAfee GTI
reputation from the TIE server or McAfee GTI file
reputation service to allow or deny execution.
Important: If certificate reputation on the TIE server is set to
Unknown, McAfee GTI certificate reputation is not checked.
Similarly, if file reputation on the TIE server is set to Unknown,
McAfee GTI file reputation is not checked for the file.
• Application Control computes reputation based on reputation of
all certificates associated with the file. Application Control uses
reputation to allow or deny file execution. If certificate reputation
isn't available, Application Control fetches the McAfee GTI file
reputation from the TIE server to allow or deny execution.
Note: Trusted reputation takes precedence over malicious
reputation while determining certificate reputation. For example,
if a file is signed by two malicious and one trusted certificate, the
resulting reputation based on certificates associated with the file
is trusted.
If the reputation for certificates associated with the file or file
reputation is:
• Known Trusted, Most Likely Trusted, Might be Trusted — The
file is allowed to run.
• Might be Malicious, Most Likely Malicious, Known Malicious
— The file isn't allowed to run.
• Unknown — Application Control continues with the next check.
• Not set — Application Control continues with the next check.
8 Advanced Threat Defense reputation Important: Reputation information is available only in a McAfee
If ATD is configured in your setup, the TIE server integrates in real
time with ATD to provide detailed assessment and data on
malware classification. If ATD is configured and the reputation
received is:
• Might be Malicious, Most Likely Malicious, Known Malicious —
The file isn't allowed to run.
• Unknown or Not set — Application Control continues with the
next check.

9 Updater rule If the file or its parent process is set as an updater, it is allowed to
run.
Note: Any process or script defined as updater must be added to
the whitelist or have a specific allow execution rule.
10 Update mode If the endpoint is running in Update mode, the file is allowed to
run.
11 User permissions If the user is added as a trusted user, they can execute the file.
12 Volume status If the file is stored on a trusted volume, the file is allowed to
execute. If the volume is defined as a trusted network path, the file
is allowed to run.
13 Removable media If the file is stored on a removable media, the file is not allowed to
run.
14 Whitelist Application Control checks the whitelist.

• If the file is in the whitelist, it is allowed to run.
• If the file isn't in the whitelist, it isn't allowed to run.
• If the file is not in the whitelist, Application Control checks the
skip list rules.
◦ If a corresponding rule for the file is in the skip list, the
file is allowed to execute.
◦ If no rule is present for the file in the skip list, the file is
not allowed to run.
Allow or block an executable file

If a reputation source is available in your environment, executable files are automatically allowed or blocked from running based
on their reputation.
Based on your requirements, you can manually authorize or restrict an executable file, based on its name, SHA-1, or SHA-256.
This ensures that the file is blocked or allowed to run, regardless of the source of the file.
Task
1. On the Rule Groups tab, locate your Group Name and under Actions, click Edit.
2. On the Executable Files tab, click Add.
3. Specify an identifier for the rule in the Rule Name field.
4. Indicate whether to allow or block the file.
5. Indicate whether to allow or block the file based on the file's name, SHA-1, or SHA-256.
6. Enter the name, SHA-1 value, or SHA-256 value.
7. Click OK.
File and certificate reputation

Reputation sources and communication
Application Control works with multiple sources to fetch reputation information for files and certificates.
Application Control supports reputation-based execution. When you run a file at an endpoint, the software fetches its reputation
and reputation of all certificates associated with the file to determine whether to allow or ban the file execution. The settings
configured for your enterprise determine the reputation values that are allowed and banned.

Reputation sources
Based on the configuration, the software regularly synchronizes with these sources:
• TIE server – The TIE server is a local reputation server that communicates with multiple reputation sources. It effectively
combines and collates intelligence from global sources with local threat intelligence and customized organizational knowledge
to provide aggregated reputation values.
• McAfee GTI server – McAfee GTI is a cloud-based service that functions as a reputation source. Application Control periodically
synchronizes with the McAfee GTI server to fetch ratings for executable files and certificates. The Fetch File Details from McAfee GTI
Server and Fetch Certificate Reputation from McAfee GTI Server tasks are internal tasks that run automatically several times a day to fetch
McAfee GTI ratings for executable files and certificates.
Communication with TIE server and McAfee GTI.

Here is how Application Control communicates with the TIE server and McAfee GTI server.
• TIE server – Application Control communicates directly with the TIE server configured in your environment.
• McAfee GTI– Application Control communicates directly with the McAfee GTI server. But, if a proxy server is configured in your
setup, Application Control uses it to communicate with the McAfee GTI server. The proxy server is configured on the Menu →
Configuration → Server Settings → Proxy Settings page.
Reputation values received from sources

Application Control communicates with TIE and McAfee GTI servers at regular intervals to fetch reputation information for
executable files and certificates.
Values from TIE server

The TIE server offers scores from various providers, such as McAfee® Advanced Threat Defense, McAfee GTI, and event trace
logs (ETL) that Application Control uses to compute reputation.
• Known trusted – A trusted file or certificate.
• Most likely trusted – Almost certainly a trusted file or certificate.
• Might be trusted – Seemingly a benign file or certificate.
• Unknown – The reputation provider can't determine its reputation at the moment.
• Might be malicious – A suspicious file or certificate.
• Most likely malicious – Almost certainly a malicious file or certificate.
• Known malicious – A malicious file or certificate.
• Not set – Undetermined file or certificate reputation.
Values from McAfee GTI

For each executable file, McAfee GTI provides the reputation and classification values.
• File Hash Reputation indicates if the file is trusted or malicious. Based on information fetched from McAfee GTI, the application and
files are sorted into categories on the Application Control pages.
• File Hash Classification indicates the reliability or credibility of the file. The assigned value indicates if the file is trusted, unknown, or
malicious.
For each certificate, McAfee GTI provides a score that indicates its reputation.
McAfee GTI score for

McAfee GTI classification for files certificates Description
known_clean 99 Known trusted
analysed_clean, assumed_clean 85 Most likely trusted
raiden_analyzed_clean, noise_clean 70 Might be trusted
unknown 50 Unknown
assumed_dirty, assumed_dirty2 30 Might be malicious
assumed_dirty3, assumed_dirty4 15 Most likely malicious

McAfee GTI score for
McAfee GTI classification for files certificates Description
pup, trojan, virus, app 1 Known malicious
Not available 0 Not set
Values from Application Control

Application Control can track the enterprise trust level or reputation by Application Control value for each executable file. When
edited, this value for a file overrides the existing reputation for the file.
For example, your organization uses an internally developed application that is set as an unknown application because it is
specific to your organization. Because you trust the application, you can recategorize it as a trusted file by editing its reputation.
The values are:
• Known Malicious
• Unknown
• Known Trusted
McAfee ePO workflow

Application Control communicates with the McAfee GTI server at regular intervals to fetch reputation information for executable
files and certificates. But, if the TIE server is configured in your environment, Application Control also continuously listens to
reputation change notifications received from the TIE server.
A change to the reputation of a file triggers a Reputation change notification. Values are updated and a corresponding Reputation changed
entry is added to the Server Task Log Details page. Each entry includes information about the file, its old and updated reputation, and
file SHA-1.
If communication with the TIE server is temporarily suspended, all missed notifications are synced after communication
resumes.
Endpoint workflow
The Solidcore client supports reputation-based execution on endpoints.
When the user executes a file, Application Control contacts the reputation source to fetch reputation information as follows:
• If the TIE server is configured, the endpoint communicates with the server to fetch reputation for the executable file or all
certificates associated with the file.
• If the TIE server isn't installed or is unavailable, the endpoint communicates with the McAfee GTI server to fetch reputation for
the executable file or all certificates associated with it.

Note: To verify if fetching reputation from TIE server or McAfee GTI server is enabled for an endpoint, review the value for the
Reputation (TIE) or Reputation (GTI) property for the endpoint. To navigate to the property, click the row corresponding to the endpoint
on the Systems page and click the Solidcore row in the Products tab.
1. Check if an explicit ban rule exists for the file.

◦ If yes, prevent file execution.
◦ If no, verify the file and certificate reputation.
2. Allow or block file execution based on reputation according to the defined reputation settings.
Application Control also uses defined rules and policies to determine file execution status.
How reputation is computed

On the McAfee ePO console, reputation information for a file is received from various sources, then collated to compute
reputation. Application Control uses values and parameters provided by these sources to determine final reputation for files and
certificates.
Here is how final reputation is computed for an unsigned file.

Here is how final reputation is computed for a signed file.
Change file reputation

Application Control works with multiple sources to fetch reputation information. The software regularly synchronizes with TIE
and McAfee GTI. You can review or edit the reputation for a file on the TIE Reputations page.
Task
1. Select Menu → Application Control → Policy Discovery.
2. On the Policy Discovery page, select a request and click Actions → More → Change File Reputation (TIE)
3. Review the file information about the TIE Reputations page.
4. (Optional) Edit file reputation: click Actions, then select an action.
Memory-protection techniques
Memory-protection techniques prevent malware execution and unauthorized attempts to gain control of a system through
buffer overflow. Application Control offers multiple techniques to prevent zero-day attacks.
At a high-level, the available techniques stop two kinds of exploits.
• Buffer overflow followed by direct code execution.
• Buffer overflow followed by indirect code execution using Return-Oriented Programming.
For a detailed and updated list of exploits prevented by memory-protection techniques, subscribe to McAfee Threat Intelligence
Services (MTIS) security advisories.
Description
Technique
CASP
CASPis a memory-protection technique that renders useless any shellcode running from the non-code area. This shellcode is
an
—abnormal event that usually happens because of a buffer overflow.
CASP
Critical
allows code to execute from non-code area but disallows the code from invoking any meaningful API calls, such as
CreateProcess()
Address and DeleteFile(). When exploit code invokes these APIs, CASP blocks it and it fails to do any damage.
SpaceWhen you use CASP, it protects all processes running on your Windows system except for those processes that are
Note:
Protection
already protected by Windows protection feature.
(mp-
Supported
casp) operating systems 32-bit and 64-bit — Windows Server 2008, Windows 7, Windows Embedded 7,
Windows 8, Windows Embedded 8, Windows 8.1, Windows Embedded 8.1,
Windows 10, Windows 10 IoT Enterprise, and Windows Server 2016.
Default state Enabled

Description
Technique
Event generated PROCESS_HIJACK_ATTEMPTED
The
NX NX feature uses the Windows Data Execution Prevention (DEP) feature to protect processes against exploits that try to
execute
— code from writable memory area (stack/heap). NX also provides granular bypass capability and raises violation
events
No that can be viewed on the McAfee ePO console.
Windows
eXecute DEP prevents code from being run from a non-executable memory region. This abnormal event mostly occurs due
to(mp-
a buffer overflow. The malicious exploit attempts to execute code from these non-executable memory regions.
nx)
Supported operating systems 64-bit — Windows Server 2008, Windows Server 2008 R2, Windows 7, Windows
Embedded 7, Windows 8, Windows Embedded 8, Windows 8.1, Windows
Embedded 8.1, Windows 10, Windows 10 IoT Enterprise, Windows Server 2012,
Windows Server 2012 R2, and Windows Server 2016.
This feature isn't available on the IA64 architecture.
Event generated NX_VIOLATION_DETECTED
This
Forced
feature forces relocation of those dynamic-link libraries (DLLs) that have opted out of the Windows native ASLR feature.
Some
DLL malware relies on these DLLs always being loaded at the same and known addresses. By relocating such DLLs, these
attacks
Relocation
are prevented.
(mp-
Supported
vasr- operating systems 32-bit and 64-bit — Windows Server 2008, Windows Server 2008 R2, Windows 7,
forced- Windows Embedded 7, Windows 8, Windows Embedded 8, Windows 8.1, Windows
relocation) Embedded 8.1, Windows 10, Windows 10 IoT Enterprise, Windows Server 2012,
Windows Server 2012 R2, and Windows Server 2016.
Event generated VASR_VIOLATION_DETECTED
Occasionally, some applications (as part of their day-to-day processing) might run code in an atypical way and be prevented from
running by the memory-protection techniques. To allow such applications to run, you can define specific rules to bypass the
memory-protection techniques.
Configuring CASP
CASP is a memory-protection technique that renders useless any shellcode running from the non-code area. This shellcode is an
abnormal event that usually happens because of a buffer overflow.
CASP allows code to execute from non-code area but disallows the code from invoking any meaningful API calls.
To protect the code in a non-code area from making API calls, configure rules to add executables to CASP.
Syntax
Task Description
Bypassattr add –c <filename1 ... filenameN>

sadmin Specify
executables one
from or
CASP. more
executables
where
CASP
must
be
bypassed.

Syntax
Task Description
For
example,
sadmin
attr
add
–
c
alg.exe
Remove
sadmin attr remove –c <filename1 ... filenameN> Specify
executables one
from or
CASP more
bypass. executables
to
remove
from
CASP
bypass;
in
effect
CASP
is
enforced.
For
example,
sadmin
attr
remove
–
c
alg.exe
List
sadmin attr list –c Lists
the all
executables executables
that that
CASP CASP
bypasses. bypasses.
For
example,
sadmin
attr
list
–
c
Flush attr flush –c

sadmin Removes
the the
CASP CASP
bypass bypass
rules rules
from from

Syntax
Task Description
all all
executables. executables
For
example,
sadmin
attr
flush
–
c
Configuring bypassing rules for NX

The NX feature uses the Windows Data Execution Prevention (DEP) feature to protect processes against exploits that try to
execute code from writable memory area (stack/heap). MP-NX also provides granular bypass capability and raises violation
events that can be viewed on the Windows Event Viewer console.
To protect processes against exploits that try to execute code from writable memory area, configure rules to add executables to
NX. This technique prevents code from being run from a non-executable memory region.
Syntax
Task Description
Bypassattr add –n <filename1 ... filenameN>

sadmin Specify
executables one
from or
NX. more
executables
where
NX
must
be
bypassed.
For
example,
sadmin
attr
add
–
n
alg.exe
Bypassattr add –n -y <filename1 ... filenameN>

sadmin Specify
an an
executable executable
and where
its NX
child must
processes be
from bypassed,
NX. including
its
child
processes.
You
can

Syntax
Task Description
specify
the
-
y
option
only
with
the
-
n
option.
For
example,
sadmin
attr
add
–
n
-
y
alg.exe
Remove
sadmin attr remove –n <filename1 ... filenameN> Specify
executables one
from or
NX more
bypass. executables
to
remove
from
NX
bypass;
in
effect
NX
is
enforced.
For
example,
sadmin
attr
remove
–
n
alg.exe
List
sadmin attr list –n Lists
the all
executables executables
that that
are NX
bypassed bypasses.

Syntax
Task Description
from For
NX. example,
sadmin
attr
list
–
n
Flush attr flush –n

sadmin Removes
NX the
bypass NX
rules bypass
from rules
all from
executables. all
executables
For
example,
sadmin
attr
flush
–
n
Configuring Forced DLL Relocation

This feature forces relocation of those dynamic-link libraries (DLLs) that have opted out of the Windows native ASLR feature.
Some malware relies on these DLLs always being loaded at the same and known addresses. By relocating such DLLs, these
attacks are prevented.
Configure rules to add one or more executables to Forced DLL Relocation.
Syntax
Task Description
Bypassattr add –v <filename1 ... filenameN>

sadmin Specify
executables one
from or
Forced more
DLL protected
Relocation. component
where
you
bypass
Forced
DLL
Relocation.
For
example,
sadmin
attr
add
–
v
AcroRD32.e

Syntax
Task Description
Enforceattr remove –v <filename1 ... filenameN>

sadmin Specify
Forced one
DLL or
Relocation more
on component
executables. where
you
enforce
Forced
DLL
Relocation.
For
example,
sadmin
attr
remove
–
v
AcroRD32.e
List
sadmin attr list –v Lists
the all
executables component
that that
Forced Forced
DLL DLL
Relocation Relocation
bypasses. bypasses.
For
example,
sadmin
attr
list
–
v
Flush attr list –v

sadmin Removes
Forced Forced
DLL DLL
Relocation Relocation
rules rules
from from
all all
executables. executables
For
example,
sadmin
attr
flush
–
v

Syntax
Task Description
Bypassattr add -o module=<DLLmodulename> -v <processname>

sadmin Bypass
a the
DLL DLL
module module
that name
is for
loaded a
for process.
a For
specific example,
process. sadmin
attr
add
–
o
module=wua
-
v
svchost.ex
Using checksum values

You can override the protection applied to a system by authorizing certain files based on their SHA-1 or SHA-256 values.
Authorizing files by their SHA-1 or SHA-256 value allows them to run on a protected system. If a file is not added to the whitelist
but configured as an authorized file, it is allowed to run. Regardless of the source of a file, if the SHA-1 or SHA-256 value matches,
the file is allowed to run.
You can also provide updater permissions to an authorized file. Configuring an authorized binary as an updater provides the
updater permissions in addition to the execution. An authorized file that is configured as an updater is allowed to run and
update software on a protected system. Installers can also be authorized by SHA-1 or SHA-256 value and configured as updaters
to allow them to install new software and update the software components. For example, if you authorize the installer for the
Microsoft Office 2010 suite by SHA-1 or SHA-256 and also configure the installer as an updater, if the SHA-1 or SHA-256 value
matches, the installer is allowed to install the Microsoft Office suite on the protected systems.
Authorize binaries
You can authorize binaries to allow them to execute on a protected system.
Syntax Description
sadmin auth –a –c <checksumvalue> Specify the SHA-1 or SHA-256 value of the binary to be
authorized.
For example:
sadmin auth –a –c
803291bcc5aa45a0221b4016f62d63a26d3ee4af
sadmin auth –a [–t tagname] –c <checksumvalue> Include the tag name and the checksum value of the binary to
be authorized.
For example:
sadmin auth –a –t Win_up_schedule1 –c

Syntax Description
sadmin auth –a –u –c <checksumvalue> Authorize a binary and also provide updater permissions.
Specify the checksum value of the binary to be authorized
and added as an updater.
For example:
sadmin auth –a –u –c
Note: Use sadmin auth -l to list authorized binaries.
Ban binaries
You can restrict binaries from executing on a protected system.
Syntax Description
sadmin auth –b –c <checksumvalue> Specify the SHA-1 or SHA-256 value of the file to be banned.
For example:
sadmin auth –b –c
sadmin auth –b –t <tagname> –c <checksumvalue> Include the tag name and SHA-1 or SHA-256 value of the file
to be banned.
For example:
sadmin auth –b –t AUTO_1 –c
583291bcc5aa45a0221b4016f62d63a26d3ee9at
Note: Use sadmin auth -l to list banned binaries.
Remove authorized or banned binaries

You can remove authorized or banned binaries from your system.
Syntax Description
sadmin auth -r <checksumvalue> Specify the SHA-1 or SHA-256 value of the file to be removed.
For example:
sadmin auth –r
sadmin auth -f This command removes all authorized or banned binaries.
Authorize execution of binaries by name

You can override the applied protection by specifying the name of binaries (programs or files) to authorize their execution.
When you specify a binary name to authorize its execution on a protected system, all binaries that have the same name and are
present on the system or network directories are authorized to execute. Similarly, if you ban a binary by specifying its name, all
binaries that have the same name are not allowed to execute.
Task
1. Run this command to authorize binaries.
sadmin attr add -a <filename>
For example, sadmin attr add -a setup.exe
2. You can specify the absolute path of the file to make sure that only the required file is allowed to run.
For example, sadmin attr add -a "C:\Program Files\Google\Picasa3\setup.exe"

Note: On Windows platforms, the drive letter is truncated. So, if the file path \Program Files\Google\Picasa3\setup.exe is
located in any other drive instead of C, the file is still authorized to execute.
Ban execution of binaries by name

You can restrict execution of binaries on a protected system by specifying their names.
For example, sadmin attr add -u setup.exe
Task
Run this command at the command prompt:
sadmin attr add -u <filename>
For example, sadmin attr add -u "C:\Program Files\Google\Picasa3\setup.exe"
Note: On the Windows platform, the drive letter is truncated. So, even if the file path \Program Files\Google\Picasa3\setup.exe is
located in any other drive instead of C, the file isn't authorized to execute.
View authorized and banned binaries

You can view authorized and banned files on a protected system.
Task
Run these commands at the command prompt.
Command Description
sadmin attr list -a Lists all files that are authorized by name.
sadmin attr list -m Lists all the files that are blocked in interactive mode.
sadmin attr list -u Lists all files that are banned by name.
Remove authorized and banned rules

You can remove binaries authorized by name to prevent them from executing on a protected system.
Task
Command Description
sadmin attr remove -a <filename> Removes the added rule to authorize the specified binary by
name. Specify the same file name or path that was used to
add the rule.
sadmin attr remove -m <filename> Removes the added rule to block the interactive mode for a
file.
sadmin attr remove -u <filename> Removes the added rule to ban the specified binary by name.
Specify the same file name or path that was used to add the
rule.
sadmin attr flush -a Removes the authorized by name rules for all files.
sadmin attr flush -m Removes the block in interactive mode rules for all files.
sadmin attr flush -u Removes the banned by name rules for all files.

Using trusted directories
You can override the protection applied to a system using trusted directories. After you add directories as trusted directories,
systems can run any software present in these directories.
Application Control tracks files and blocks the execution of binaries and scripts on the network directories. The software also
supports tracking files on the Server Message Block (SMB) mount points. This feature is identified as network-tracking in the
features list. By default, this feature is enabled and prevents the execution of binaries and scripts on network directories.
When this feature is disabled, execution of scripts on network directories is allowed. But, execution of binaries on network
directories is not allowed. Also, write-protecting or read-protecting components on a network directory is not in effect.
Add trusted directories in a managed environment

Add directories (local or network share) as trusted directories to run any software in these directories on a protected endpoint.
Task
1. On the McAfee ePO console, create or modify an Application Control policy or rule group.
3. On the Directories tab, click Add.
4. Enter the location of the directory.
5. Select Include or Exclude.
Use Exclude to exclude a specific folder or subfolder within a trusted directory.
6. Click OK.
Add trusted directories in a standalone environment

You can add directories as trusted directories to run any software present in these directories on a protected system.
This table describes how to add trusted directories.
Command Description
sadmin trusted –i <pathname1...pathnameN> You can specify one or more paths to the directories to be
added as trusted directories. You can also specify paths to the
directories located on network shares.
For example:
• sadmin trusted –i C:\Documents and Settings\admin
\Desktop\McAfee
• sadmin trusted –i \\192.168.0.1\documents
sadmin trusted –u <pathname1...pathnameN> You can specify one or more paths to the directories to be
added as trusted directories. This command adds all binaries
and scripts present in the directories as updaters. You can
also specify paths to the directories located on network
shares.
For example:
• sadmin trusted –u C:\Documents and Settings\admin
\Desktop\McAfee
• sadmin trusted –u \\192.168.0.1\documents
Note: You can also add a trusted volume by specifying a
volume name with this command to include all binaries and
scripts present in the specified volume as updaters. Use the
sadmin trusted –i -u <volumename> command to specify
the volume name.

Specifying directory paths
You can specify directory paths to be added as trusted directories on a mounted network file system.
Command Description
sadmin trusted –i \\server-name\share-name You can specify the server name that has a network share or
the name of the network share.
sadmin trusted –i \\server-name You can specify the server name.
sadmin trusted –i \\* You can specify all network shares by all servers.
Paths can include the wildcard characters to specify file paths and file names. When using wildcards, ensure that specified string
matches a limited set of file paths or file names. If the specified string matches many files, we recommend you revise the string.
Paths can include the * and ? wildcard characters. When specifying a trusted directory, \\10.10.10.10\*****\User2, \
\10.10.10.10\????\User2, \\10.10.10.10\*AD*\* and \\10.10.10.10\?AD?***\User1 are allowed while \\*\AD\User1, \\*.
10.10.10\AD*\User1, and \\10.**10.10\AD*\User1 are not supported.
View trusted directories

You can view the list of directories that are added as trusted directories on the system.
Task
Run this command at the command prompt:
sadmin trusted -l
This command lists all trusted directories added on the system.
Exclude specific directories

You can exclude specific directories from the list of directories that you added as trusted on the system.
Task
1. Run this command at the command prompt:
sadmin trusted –e <pathname1...pathnameN>
2. Run this command to specify one or more paths to the directories to be excluded from the list of trusted directories:
◦ sadmin trusted –e C:\Documents and Settings\admin\Desktop\McAfee
◦ sadmin trusted –e \\192.168.0.1\documents
Remove trusted directories

You can remove trusted directories to restrict them to run any software present in them.
Task
Remove the trusted directories using these methods.
Command Description
sadmin trusted –r <pathname1...pathnameN> To specify one or more paths to the directories to be removed
as trusted directories.
For example:
• sadmin trusted –r C:\Documents and Settings\admin
\Desktop\McAfee
• sadmin trusted –r \\192.168.0.1\documents

Command Description
sadmin trusted –f To flush all rules for trusted directories. If you specify this
argument, all rules for the trusted directories are removed
from the system.
Using rule groups in a managed environment

What are rule groups?
A rule group is a collection of rules. Although you can directly add rules to any McAfee ePO-based policy, the rules defined in a
policy are specific to that policy. In contrast, a rule group is an independent unit that collates a set of similar or related rules.
After you define a rule group, you can reuse the rules by associating the group with different policies. Also, when you change or
update a rule group, the change is automatically introduced into all associated policies.
Application Control provides predefined rule groups to allow commonly used applications to run smoothly. Although you can't
edit the predefined rule groups, you can use an existing rule group as a starting point to develop new rule groups. If needed, you
can also import or export rule groups.
Rule groups can drastically reduce the effort required to define similar rules across policies. If you have a large setup and you are
deploying the software across numerous endpoints, use rule groups to minimize the deployment time and effort.
Rule group ownership

Users can edit and delete only the rule groups that they own. A user who creates a rule group, is automatically set as the owner
of the rule group. Only the owner and McAfee ePO administrator can edit and delete the rule group. Also, the administrator can
assign ownership to other users or revoke ownership from the owner. In this case, the ownership is automatically granted to the
McAfee ePO administrator.
Users who don't own a rule group can only view the rule group and its policy assignments, duplicate the rule group, and add the
rule group to policies. But, if the owner or the McAfee ePO administrator updates a rule in the rule group, the change cascades
across all associated McAfee ePO policies.
This scenario suits non-global administrators who want to use a rule group (created by theMcAfee ePO administrator) without
maintaining it. If this scenario does not suit your requirements, duplicate the rule group that you don't own, then assign the
duplicate to policies. This method provides you ownership of the duplicated rule group.
Rule group example

Here is an example of how rule groups are used.
An organization runs Oracle on multiple servers. Each of these servers is used by the HR, Engineering, and Finance departments
for different purposes. To reduce rule redundancy, we define an Application Control rule group (named AC-Oracle) with rules to
define the relevant updaters for Oracle to function.
After the rule group is defined, we can reuse these rule groups across policies for the different departments. So, when defining
the HR Servers policy, add the AC-Oracle rule group to the policy with rule groups for the other applications installed on the HR
server. Similarly, add the AC-Oracle rule group to the relevant policies for the Engineering Servers and Finance Servers. After
defining the policies, if the rule for a critical file was not created, directly update the rule group to automatically update all
policies.
Manage rule groups and policies
Create a rule group

You can create a rule group from scratch or copy an existing rule group and change it as needed.
Task
1. On the McAfee ePO console, select Menu → Configuration → Solidcore Rules.
2. On the Rule Groups tab, select Application Control from the Type menu.
3. Create a rule group or copy an existing rule group.
◦ Create a rule group:
◦ Click Add Rule Group to open the Add Rule Group dialog box.

◦ Specify the rule group name, type, and platform, then click OK.
◦ Under Actions, click Edit to specify the required rules, then click Save Rule Group to save all changes.
◦ Copy an existing rule group:
◦ Under Group Name, select the rule group you want to duplicate.
◦ Under Actions, click Duplicate to open the Duplicate Rule Group dialog box.
◦ Specify the rule group name, then click OK.
◦ Under Actions, click Edit to specify the required rules, then click Save Rule Group to save all changes.
Manage permissions for rule group tabs

Specify permissions for the Rule Groups, Certificates, Installers pages, and the tabs contained in rule group and policy pages.
Task
1. On the McAfee ePO console, select Menu → User Management → Permission Sets.
2. Click New Permission Set to create a permission set.
3. Enter a name for the permission set.
4. Select the users you want to assign the permission set to.
The selected level of permissions is granted to the user.
Note: When multiple permission sets are applied to a user account, they aggregate. Consider this as you plan your strategy
for granting permissions to the users in your environment.
5. Click Save.
6. Under Permission Sets, click Solidcore Admin or Solidcore Reviewer.
7. In the right pane, click Edit on the Solidcore General permissions category.
8. Grant permissions for Certificates, Installers, and Rule Groups, as needed.
9. Grant permissions selectively for the tabs (Updater Processes, Certificates, Installers, Directories, Users, Executable Files, Exclusions, Filters, and
Execution Control) contained in rule group and policy pages, as needed.
10. Click Save.
Delete or rename rule groups

You can delete or rename a rule group, as needed.
Task
2. Complete one of these actions from the Rule Groups tab.
◦ To rename a rule group, click Rename, specify a new name, and click OK to close the Rename Rule Group dialog box.
◦ To delete a rule group, click Delete and click Yes to close the Delete Rule Group dialog box.
View assignments for a rule group

Instead of navigating through all created policies, you can directly view all policies where a rule group is being used. This feature
provides a convenient way to verify if each rule group is assigned to the relevant policies.
Task
2. On the Rule Groups tab, click Assignments for a rule group to view its assigned policies.
Attribute-based rules
Application Control performs multiple checks to determine whether to allow or block a file's execution. If a file's execution is
allowed after the Application Control checks, attribute-based or granular rules, if any are defined, come into play. The rules are
based on the concept of fine-grained whitelisting and can be created on the attributes of a file.
You can define specific rules using attributes to allow, block, or monitor the file. Rules that allow execution take precedence over
rules that block or monitor execution.
Attribute-based rules help you allow or block files in different scenarios based on file context. On a protected system, only
whitelisted interpreters are allowed to run. But, in certain scenarios, whitelisted interpreters might be misused to execute

malicious scripts. You can prevent misuse of interpreters by defining attribute-based rules to block potentially malicious
scenarios.
Attribute-based rules provide flexibility to allow or block file execution, as needed. If an administrator needs to block a user from
running a specific file, they can add an attribute-based rule to prevent its execution by that user. Similarly, an administrator can
choose to block execution of a certain file altogether, unless when run by a specific parent process.
Tip: We recommend that before creating a block rule for a file, create a monitor rule to observe the file's use and execution in your
setup. After you define the monitoring rule, if no OBSERVED_FILE_EXECUTION events are generated for the file over a reasonable
time window, you can safely define a block rule for a file. But, the applied rules are ineffective when the system is in update
mode, observe mode, or when any process is selected as updater process and only the events are generated.
Define attribute-based rules for file execution

Attribute-based rules provide flexibility to allow or block file execution, as needed.
Task
2. On the Execution Control tab, click Add.
3. To define an attribute-based rule for a file, select Based on specified attributes.
4. Select the type of rule to define: Allow, Block, or Monitor.
5. Specify the file name.
6. Specify the attributes to define the rule.
You can use one or all attributes to define the rule. Available attributes are path, command line, parent process, and user. You
can use the AND operator to combine rules based on different attributes.
a. Select the checkbox associated with the attribute.
b. Select the operator for the attribute.
c. Enter the string.
7. (Optional) Enter the rule description.
8. Click OK.
Create a policy
Add specific rules to a rule group or policy. Most Application Control policies are multi-slot policies; a user can assign multiple
policies to a single endpoint in the System Tree.
Task
1. On the McAfee ePO console, select Menu → Policy → Policy Catalog.
2. Select Solidcore 8.x.x: Application Control for the product.
3. Click New Policy to open the Create a new policy dialog box and select the category.
4. Based on the category, perform one of these actions:
◦ If you selected Application Control Options (Windows) category, select the policy you want to duplicate from Create a policy based on this
existing policy list.
◦ If you selected any other category, select Blank Template from Create a policy based on this existing policy list to define a policy from
scratch.
5. Specify the policy name, then click OK to open the Policy Settings page.
6. Add a rule group to the policy.
a. Select the rule group in the Rule Groups tab.
b. Select Add in the Rule Groups tab to open the Select Rule Groups dialog box.
c. Select the rule group to add, then click OK.
7. Add the rules to the policy and save changes.
Predefined rules in default policies

Application Control includes predefined rules for commonly used applications for all supported operating systems.
Apply these default policies to the endpoints to ensure proper product functionality. If available, you can use the blank template
or duplicate these policies to configure the settings. These are the predefined rules included in these policies.

Default
policy Product Category Policy type Description Blank template available
McAfee Default Solidcore 8.x.x: General Configuration Single-slot Default settings for CLI, No
(Client) throttling, and more for the
Solidcore client.
McAfee Default Solidcore 8.x.x: General Exception Multi-slot Default exception rules for the Yes
Rules (Unix) UNIX platform.
McAfee Default Solidcore 8.x.x: General Exception Multi-slot Default rules for memory Yes
Rules protection and other bypass
(Windows) techniques on the Windows
platform.
McAfee Default Solidcore 8.x.x: Application Single-slot Default settings for self- No
Application Control Control approval, end-user
Options notifications, inventory,
(Windows) reputation, and Application
Control features on the
Windows platform.
My Default Solidcore 8.x.x: Application Single-slot Default settings for self- No

Application Control Control approval, end-user
Options notifications, inventory,
(Windows) reputation, and Application
Control features on the
Windows platform.
McAfee Default Solidcore 8.x.x: Application Multi-slot Default rules to design the trust Yes
Application Control Control model on the UNIX platform.
Rules (Unix) This policy also includes default
filters to exclude events that
aren't relevant for your setup.
McAfee Default Solidcore 8.x.x: Application Multi-slot Default rules to design the trust Yes
Application Control Control model on the Windows
Rules platform. This policy also
(Windows) includes default filters to
exclude events that aren't
relevant for your setup.
McAfee Solidcore 8.x.x: Application Multi-slot McAfee-specific rules that allow No

Applications Application Control Control other McAfee products to run
(McAfee Default ) Rules successfully on protected
(Windows) endpoints. These rules are also
included in the McAfee Default
policy for the Application
Control Rules (Windows)
category.
Common ActiveX Solidcore 8.x.x: Application Multi-slot Predefined read-only rules to No

Rules Application Control Control install commonly used ActiveX
Rules controls on endpoints.
(Windows)

Default
policy Product Category Policy type Description Blank template available
Throttling Rules Solidcore 8.x.x: Application Multi-slot Predefined read-only rules to No

Application Control Control filter and stop observations
Rules received from managed
(Windows) endpoints.
When the number of
observations received at the
McAfee ePO server reaches the
defined threshold, this policy is
applied to all systems and
groups in your organization.
Throttling Rules Solidcore 8.x.x: Application Multi-slot Predefined read-only rules to No

(Deprecated) Application Control Control filter and stop observations
Rules received from managed
(Windows) endpoints.
When the number of
observations received at the
McAfee ePO server reaches the
defined threshold, this policy is
applied to all systems and
groups in your organization.
Path considerations when defining rules

Regardless of whether you create a policy or define a rule group, the framework available to define rules is the same.
Supported system variables

The path specified in a rule can include system environment variables. This table lists the supported system variables.
Variable Example value (most Windows platforms)
%ALLUSERSPROFILE% C:\Documents and Settings\All Users
%APPDATA% C:\Documents and Settings\{username}\Application
%COMMONPROGRAMFILES% C:\Program Files\Common Files
%COMMONPROGRAMFILES (x86)% C:\Program Files (x86)\Common Files
%HOMEDRIVE% C:
%HOMEPATH% C:\Documents and Settings\{username} (\ on earlier Windows

versions)
%PROGRAMFILES% C:\Program Files
%PROGRAMFILES (x86)% C:\Program Files (x86) (only for 64-bit versions)
%SYSTEMDRIVE% C:
%SYSTEMROOT% C:\windows (C:\WINNT on earlier Windows versions)
%TEMP% (system) %tmp% (user) C:\Documents and Settings\{username}\local Settings\Temp

C:\Temp

Variable Example value (most Windows platforms)
%USERPROFILE% C:\Documents and Settings\{username} (C:WINNT\profiles\

{username} for earlier versions)
%WINDIR% C:\Windows
Path considerations
These considerations apply to path-based rules.
• Paths don't need to be absolute when specifying rules. For example, when defining an updater, you can specify partial or fully
qualified paths.
◦ Partial paths — If you specify partial paths, such as AcroRd32.exe or Reader\AcroRd32.exe, all programs with names
that match the specified string are assigned updater rights. Similarly, when blocking a file, all programs with names
that match the specified string are blocked.
◦ Fully qualified paths — When you specify fully qualified paths, such as C:\Program Files\Adobe\Reader 9.0\Reader
\AcroRd32.exe or \Program Files\Adobe\Reader 9.0\Reader\AcroRd32.exe only the specified program is assigned
updater rights. When blocking a file, if you specify the fully qualified path, for example C:\Windows
\system32\notepad.exe, only the specified file is blocked.
• Paths can contain white spaces.
• Paths can include the wildcard characters to specify file paths and file names. When using wildcards, ensure that specified
string matches a limited set of file paths or file names. If the specified string matches many files, we recommend you revise the
string.
• Paths can include the * and ? wildcard characters.
Wildcard patterns
Paths specified in a rule can include the * and ? wildcard characters.
These are the valid and invalid wildcard patterns you can use based on each feature.
Feature Valid pattern Invalid pattern
Read protect • C:\Test1\*\*\Test.txt • *:\Test1\Test2\Test.txt

Write protect • C:\Test1\*\***\Test.txt • ?:\Test1\Test2\Test.txt
• C:\Test1\*****\Test.txt • *\Test1\Test2\Test.txt
• C:\*\*\Test.txt • ?\Test1\Test2\Test.txt
• C:\*\Test.txt • *:\Test1\*\*\Test.txt
• C:\Test1\?\?\Test.txt • C:\Test1\Test2\Test.*
• C:\Test1\?\???\Test.txt • C:\Test\****
• C:\Test1\?????\Test.txt • C:\Test\*.*
• C:\Test1\?\?.txt • C:\Test\Test****
• C:\?\?\Test.txt • C:\*?
• C:\?\Test.txt • C:\?*
• C:\?\?.txt • Test\Test1*\Test.txt
• C:\Test*\Test1\Test.txt • Test\Test1*\Test.*
• C:\Test?\Test1\Test.txt • Test\Test1*\Test.?
• C:\Test*\Test1*\Test.txt
• C:\Test?\Test1?\Test.txt
• C:\Test\Test?????
• C:\*Test\Test1\Test.txt
• C:\?Test\Test1\Test.txt
• C:\*Test?\Test1\Test.txt
• C:\?Test*\Test1\Test.txt
• C:\*Test?QA\Test1\Test.txt
• C:\?Test*QA\Test1\Test.txt
Registry • HKEY_LOCAL_MACHINE\TestLevel1\Level2 • *\TestLevel1\Level2

Write protect • HKEY_LOCAL_MACHINE\TestLevel*\Level2 • HKEY_*_MACHINE\TestLevel1\Level2
Monitor-registry • HKEY_LOCAL_MACHINE\Test*1\Level2 • HKEY_LOCAL_MACHINE\TestLevel1\*
• HKEY_LOCAL_MACHINE\*TestLevel1\Level2 • HKEY_LOCAL_MACHINE\TestLevel1\*Level*
• HKEY_LOCAL_MACHINE\*TestLevel*\Level2 • HKEY_LOCAL_MACHINE\TestLevel1\Level*
• HKEY_LOCAL_MACHINE\*\Level2 • ?\TestLevel1\Level2
• HKEY_LOCAL_MACHINE\*\*\Test • HKEY_?_MACHINE\TestLevel1\Level2
• HKEY_LOCAL_MACHINE\TestLevel1\*Level2 • HKEY_LOCAL_MACHINE\TestLevel1\?
• HKEY_LOCAL_MACHINE\TestLevel?\Level2
• HKEY_LOCAL_MACHINE\Test?1\Level2
• HKEY_LOCAL_MACHINE\?TestLevel1\Level2
• HKEY_LOCAL_MACHINE\?TestLevel?\Level2
• HKEY_LOCAL_MACHINE\?\Level2
• HKEY_LOCAL_MACHINE\?\?\Test
• HKEY_LOCAL_MACHINE\TestLevel1\?Level2
• HKEY_LOCAL_MACHINE\TestLevel1\?Level?
• HKEY_LOCAL_MACHINE\TestLevel1\Level?
• HKEY_LOCAL_MACHINE\*?Test?Level1*
\Level2
Trusted Directory • \\*\AD\User1 • \\10.10.10.10\AD*\User1

• \\10.10.10.10\AD*\User1 • \\10.**10.10\AD*\User1
• \\10.10.10.10\*AD*\*User1 • \\10.10.10.10\*AD*\User1
• \\?\AD\User1 • \\10.10.10.10\*****\User2
• \\10.??10.10\AD?\User1 • \\10.10.10.10\*AD\User1
• \\10.10.10.10\?AD?\User1 • \\10.10.10.10\*AD*\User*
• \\10.10.10.10\????\User2 • \\10.10.10.10\*AD*\*User1*
• \\10.10.10.10\?AD\User1 • \\10.10.10.10\*AD*\*
• \\10.10.10.10\AD?\User1
• \\10.10.10.10\?AD?\User?
• \\10.10.10.10\?AD?\?User1
• \\10.10.10.10\?AD?\?User1?
• \\10.10.10.10\?AD?\?
• \\10.10.10.10\?AD?***\User1
• \\10.10.10.10\?***?***\User1
• \\10.10.10.10\Test1\User**?
Monitor File Changes • *:\Test1\Test2\Test.txt • C:\Test1\Test2\Test.*

• ?:\Test1\Test2\Test.txt • C:\Test\****
• *\Test1\Test2\Test.txt • C:\Test\?????
• ?\Test1\Test2\Test.txt • C:\Test\*.*
• *:\Test1\*\*\Test.txt • C:\Test\?.?
• C:\Test1\*\*\Test.txt • C:\Test\Test****
• C:\Test1\*\***\Test.txt • C:\*?
• C:\Test1\*****\Test.txt • C:\?*
• C:\Test1\*\*.txt • Test\Test1*\Test.txt
• C:\*\*\Test.txt • Test\Test1*\Test.*
• C:\*\Test.txt • Test\Test1*\Test.?
• C:\*\*.txt
• C:\Test1\?\?\Test.txt
• C:\Test1\?\???\Test.txt
• C:\Test1\?????\Test.txt
• C:\Test1\?\?.txt
• C:\?\?\Test.txt
• C:\?\Test.txt
• C:\?\?.txt
• C:\Test1\Test2\Test.?

• C:\Test*\Test1\Test.txt
• C:\Test?\Test1\Test.txt
• C:\Test*\Test1*\Test.txt
• C:\Test?\Test1?\Test.txt
• C:\*Test\Test1\Test.txt
• C:\?Test\Test1\Test.txt
• C:\*Test?\Test1\Test.txt
• C:\?Test*\Test1\Test.txt
• C:\*Test?QA\Test1\Test.txt
• C:\?Test*QA\Test1\Test.txt
Monitor Process • *:\Test1\Test2\Test.exe • C:\Test1\Test2\Test.*

• ?:\Test1\Test2\Test.exe • C:\Test\****
• *\Test1\Test2\Test.exe • C:\Test\?????
• ?\Test1\Test2\Test.exe • C:\Test\*.*
• *:\Test1\*\*\Test.exe • C:\Test\?.?
• C:\Test1\*\*\Test.exe • C:\Test\Test****
• C:\Test1\*\***\Test.exe • C:\*?
• C:\Test1\*****\Test.exe • C:\?*
• C:\Test1\*\*.exe • Test\Test1*\Test.*
• C:\*\*\Test.exe
• C:\*\Test.exe
• C:\*\*.exe
• C:\Test1\?\?\Test.exe
• C:\Test1\?\???\Test.exe
• C:\Test1\?????\Test.exe
• C:\Test1\?\?.exe
• C:\?\?\Test.exe
• C:\?\Test.exe
• C:\?\?.exe
• C:\Test1\Test2\Test.?
• C:\Test*\Test1\Test.exe
• C:\Test?\Test1\Test.exe
• C:\Test*\Test1*\Test.exe
• C:\Test?\Test1?\Test.exe
• C:\*Test\Test1\Test.exe
• C:\?Test\Test1\Test.exe
• C:\*Test?\Test1\Test.exe
• C:\?Test*\Test1\Test.exe
• C:\*Test?QA\Test1\Test.exe
• C:\?Test*QA\Test1\Test.exe
• Test\Test1*\Test.exe
• Test\Test1*\Test.?
Updaters • C:\Test1\*\*\Test.exe • *:\Test1\Test2\Test.exe

• C:\Test1\*\***\Test.exe • ?:\Test1\Test2\Test.exe
• C:\Test1\*****\Test.exe • *\Test1\Test2\Test.exe
• C:\Test1\*\*.exe • ?\Test1\Test2\Test.exe
• C:\*\*\Test.exe • *:\Test1\*\*\Test.exe
• C:\*\Test.exe • C:\*\*.exe
• C:\Test1\Test2\Test.* • C:\Test1\?\?.exe
• C:\Test1\?\?\Test.exe • C:\Test1\Test2\Test.?
• C:\Test1\?\???\Test.exe • C:\Test\****
• C:\Test1\?????\Test.exe • C:\Test\?????

• C:\?\?\Test.exe • C:\Test\*.*
• C:\?\Test.exe • C:\Test\?.?
• C:\?\?.exe • C:\Test\Test****
• C:\Test*\Test1\Test.exe • C:\Test\Test?????
• C:\Test?\Test1\Test.exe • C:\*?
• C:\Test*\Test1*\Test.exe • C:\?*
• C:\Test?\Test1?\Test.exe • Test\Test1*\Test.*
• C:\*Test\Test1\Test.exe • Test\Test1*\Test.?
• C:\?Test\Test1\Test.exe
• C:\*Test?\Test1\Test.exe
• C:\?Test*\Test1\Test.exe
• C:\*Test?QA\Test1\Test.exe
• C:\?Test*QA\Test1\Test.exe
• Test\Test1*\Test.exe
Define bypass rules

Define specific rules in a policy to bypass applied memory-protection and other techniques.
Some applications (as part of their day-to-day processing) run code in an atypical way and hence are prevented from running. To
allow such applications to run, define appropriate bypass rules. A bypassed file or application is no longer considered by the
memory-protection features of Application Control.
Task
1. On the McAfee ePO console, perform one of these actions.
◦ Create an Application Control policy or rule group.
◦ Create an Application Control policy (to apply bypass rules to one endpoint).
2. Select the Exclusions tab.
3. Click Add to open the Add exclusion rules dialog box.
4. Expand nodes for the options where you want to add bypass rules.
◦ Memory protection
◦ Installation detection
◦ Advanced options
5. (Optional) Select the Memory protection options where you want to add bypass rules, then provide the needed information.
◦ Disable buffer overflow protection (CASP) for a process — Specify a process in the Process Name field to bypass the process from the
Critical Address Space Protection (CASP) technique.
◦ Disable buffer overflow protection (NX) for a process on 64-bit Windows — Specify a process in the Process Name field to bypass the process
from the No eXecute (NX) technique. Select Enable Inheritance to bypass child processes started by the file from the No eXecute
(NX) technique.
◦ Disable ROP protection for a process using Forced Relocation (VASR) — Specify a process in the Process Name field to bypass the process
from the VASR Forced-Relocation technique. Optionally, specify the name of the DLL file associated with the process in the
Library Name field.
◦ Disable ROP protection for a DLL using DLL Relocation (VASR) — Specify a DLL file in the Library Name field to bypass the DLL file from the
VASR DLL Relocation technique. The file isn't rebased and is loaded from its preferred base address.
◦ Disable ROP protection for a process using Stack Randomization (VASR) — Specify a process in the Process Name field to bypass the process
from the VASR Process Stack Randomization technique.
6. (Optional) Select Allow uninstallations and provide the needed information.
7. (Optional) Select Advanced options where you want to add bypass rules, then provide the needed information.
◦ Exclude file from write-protection rules and allow script execution — Specify a process in the Process Name field to bypass the process from
write protection rules and also allow execution for a script file using the Process Context File Operations bypass technique.
Optionally, specify the name of the parent process in the Parent Process Name field to allow the file to bypass only if it is
launched by the specified parent.
◦ Ignore path for file operations — Specify a relative path in the Relative Path field to ignore the relative path for file operations using
the skiplist -i command.

◦ Exclude path from file operations — Specify a relative path in the Relative Path field to bypass the relative path from file operations
using the skiplist -f command.
◦ Exclude path from write-protection rules, specify a relative path in the Relative Path field to bypass the relative path from file write
protection rules using the skiplist -d command.
◦ Exclude local path and all its contained files and sub-directories from the whitelist, specify a local path in the Path field to bypass the local path
and all its contained files and subdirectories from the whitelist using the skiplist -s command.
◦ Exclude volume from Application Control protection, specify a volume in the Volume field to bypass the volume from Application Control
protection using the skiplist -v command. This option detaches the specified volume from the whitelist and the volume is
not protected by Application Control.
8. Click OK to apply the rules.
Important: Contact McAfee Support before applying these exclusions.
Using execution control rules in a standalone environment

Defining attribute-based rules for file execution
Application Control performs multiple checks to determine whether to allow or block a file's execution. If a file's execution is
allowed after the Application Control checks, attribute-based or granular rules, if any are defined, come into play. The rules are
based on the concept of fine-grained whitelisting and can be created on the attributes of a file.
Note: This feature is also known as Execution Control and it is enabled by default. To disable this feature, use this command:
sadmin features disable execution-control
You can define specific rules using one or more attributes to allow, block, or monitor the file. Rules that allow execution take
precedence over rules that block or monitor execution.
Attribute-based rules help you allow or block files in different scenarios based on file context and offer flexibility.
• Context-based allowing or blocking of files — On a protected system, only whitelisted interpreters are allowed to execute. But,
in certain scenarios, whitelisted interpreters might be misused to execute malicious scripts. For example, a powershell.exe
script can be used to execute unsolidified scripts and execute file-less scripts by invoking its execution with atypical input
arguments. You can prevent misuse of interpreters by defining attribute-based rules to block potentially malicious scenarios.
• Flexibility and control — Attribute-based rules provide flexibility to allow or block file execution, as needed. You might need to
block a user from running a specific file. If an administrator wants to block the execution of powershell.exefor a specific user, a
rule can be added to prevent its execution. You can achieve such scenarios using attribute-based rules.
Similarly, you might choose to block execution of a certain file in your setup completely, unless when run by a specific parent
process. You can achieve this by creating a generic block rule and a parent process-based allow rule for the file. Because the
allow rule has precedence over the block rule, it overrides the block rule when applied.
Or, you might choose to only observe or monitor a file to determine its execution in your setup. To do this, you can define a
monitor rule for the file.
Note: We recommend that before creating a block rule for a file, create a monitor rule to observe the file's use and execution in
your setup. After you define the monitoring rule, if no OBSERVED_FILE_EXECUTION events are generated for the file over a
reasonable time window, you can safely define a block rule for a file.
When configuring an attribute-based rule, you can choose to allow, block, or monitor a file. This table describes the behavior of a
rule in various supported modes.
Type of rule Enable Update
Allow • Allow file execution. • Allow file execution.

• No event is generated. • No event is generated.
Block • Block file execution. • Allow file execution.

• The PREVENTED_FILE_EXECUTION event is generated. • The OBSERVED_FILE_EXECUTION event is
generated.
Monitor • Allow file execution. • Allow file execution.

• The OBSERVED_FILE_EXECUTION event is generated.

Type of rule Enable Update
• The OBSERVED_FILE_EXECUTION event is
generated.
Note: The applied rules are ineffective when any process is selected as an updater. Only the events are generated.
Add attribute-based rules

You can create rules based on one or more attributes of a file to allow, block, or monitor its execution.
Task
1. Enter the command with attribute type as command_line:
◦ sadmin ruleengine add <ruletype> processname command_line <operation> <REGEX/STRING>
This table describes the command's tokens and their functionality.
Token Possible values Description
Ruletype ◦ allow Allows you to create a rule to allow, block or

◦ block monitor execution.
◦ monitor
Attributetype ◦ command_line Defines the command_line argument with which

a process is launched. The attribute-based rule
can be formed on it for decision making in the
rule engine.
Operation ◦ matches Performs the rule based on operation

◦ notmatches configured on the attribute of a process. Only
◦ equals matches and notmatches support REGEX. For
◦ notequals others, string is used.
REGEX A regular expression Includes a regular expression or a string of

characters. It describes a grammar that can be
constructed based on ECMA script.
STRING Any characters Defines a string of characters.
2. Enter the command with attribute type as parent_process_name, user, or path:

◦ sadmin ruleengine add <ruletype> processname <attributetype> <operation> STRING
Ruletype ◦ allow Allows you to create a rule to allow, block or

◦ monitor
Attributetype ◦ user Defines the attribute type on which attribute-

◦ parent_process_name based rules can be formed for decision making
◦ path in the rule engine.
Operation ◦ equals Performs the rule based on operation

◦ notequals configured on the attribute of a process.

You can use multiple attributes when creating attribute-based rules. Use AND as a connector while creating a rule based on
two or more attribute types. For example, sadmin ruleengine add block powershell.exe command_line matches .*iex*
AND user equals "user1" rule prevents user1 from running powershell.exe when run with command-line argument that
matches regex *iex* in this case. In other scenarios, user1 is allowed to execute powershell.exe.
Remove attribute-based rule

You can remove attribute-based rules defined on the system.
Task
1. Remove one rule with attribute type as command_line:
◦ sadmin ruleengine remove <ruletype> processname command_line <operation> <REGEX/STRING>
This table describes the command's tokens and their functionality in detail.
Ruletype ◦ allow Allows you to create a rule to allow, block, or

◦ monitor
Attributetype ◦ command_line Defines the command_line argument with which

a process is started. The attribute-based rule
can be formed on it for decision making in the
rule engine.
Operation ◦ matches Performs the rule based on operation

◦ notmatches configured on the attribute of a process. Only
◦ equals matches and notmatches support REGEX. For
◦ notequals others, string is used.
REGEX A regular expression Includes a regular expression or a string of

characters. It describes a grammar that can be
constructed based on ECMA script. See this
article for more details.
2. Remove one rule with parent_process_name, path, or user attribute type:

◦ sadmin ruleengine remove <ruletype> processname <attributetype> <operation> STRING
Ruletype ◦ allow Allows you to create a rule to allow, block, or

◦ monitor
Attributetype ◦ user Defines the attribute type on which attribute-

◦ parent_process_name based rules can be formed for decision making
◦ path in the rule engine.

Operation ◦ equals Performs the rule based on operation

◦ notequals configured on the attribute of a process.
You can use multiple attributes when creating attribute-based rules. Use AND as a connector while creating a rule based on
two or more attribute types. For example, sadmin ruleengine remove block powershell.exe command_line matches .*iex*
AND user equals "user1" rule removes the rule that is preventing user1 from running powershell.exe when run with
command-line argument that matches regex.*iex* in this case.
3. Remove or flush all attribute-based rules defined on the system:
◦ sadmin ruleengine flush
View attribute-based rules

You can view all attribute-based rules added to your system.
Task
Run this command at the command prompt.
sadmin rulengine list
Using certificates in a managed environment

What are certificates?
Application Control allows trusted certificates that are associated with software packages to run on a protected system.
After you add a certificate as a trusted or authorized certificate, you can run all software, signed by the certificate on a protected
system without entering Update mode. For example, if you add Adobe's code-signing certificate, all software issued by Adobe
and signed by Adobe's certificate are allowed to run.
Note: Application Control supports only X.509 certificates.
To allow in-house applications to run on protected systems, you can sign the applications with an internal certificate and define
the internal certificate as a trusted certificate. After you do so, all applications signed by the certificate are allowed.
You can also provide updater permissions to the certificate. All applications and binary files that are either added or changed on
a system and signed by a certificate that has the updater permissions are automatically added to the whitelist. Use this option
carefully because it makes sure that all executable files signed by the certificate acquire updater rights.
Add certificates in a managed environment

You can add a certificate before defining rules to permit installation and execution of software signed by the certificate.
To add a certificate, you can follow one of these actions:
• Upload an existing certificate.
• Extract certificates from signed executable files on a network share.
• Schedule a server task to routinely extract certificates from signed executable files on a network share.
Task
1. Upload an existing certificate.
a. On the McAfee ePO console, select Menu → Configuration → Solidcore Rules.
b. On the Certificates tab, select Actions → Upload to open the Upload Certificate page.
c. Browse to and select the certificate file to import, then click Upload.
2. Extract certificates.
a. Select Menu → Configuration → Solidcore Rules.
b. On the Certificates tab, select Actions → Extract Certificates to open the Extract Certificate from File page.
c. Type the path of the file.
Make sure that the file path is accessible from the McAfee ePO server.
d. Type your network credentials to access the specified network location.

e. Click Extract.
3. Schedule extraction: You can schedule and regularly extract the certificates associated with signed executable files on a
network share.
a. Select Menu → Automation → Server Tasks.
b. On the Server Tasks page, click New Task to open the Server Task Builder wizard.
c. Type the task name, then click Next.
d. From the Actions drop-down list, select Solidcore: Scan a Software Repository.
e. Specify the Software Repository Path.
Note: All subfolders in the specified path are also scanned for installers and certificates.
f. Type your network credentials to access the specified network location.
g. Click Test Connection to make sure that the specified credentials work.
h. Select Add extracted certificates and installers to Rule Group to add the certificates and installers extracted by the task to a user-
defined rule group and select the user-defined rule group from the list.
Note: You can add extracted certificates and installers only to user-defined rule groups.
i. Click Next, specify the schedule for the task, then click Next.
j. Review the task summary, then click Save.
4. (Optional) Specify an alias or friendly name for a certificate.
a. Select Menu → Configuration → Solidcore Rules.
b. On the Certificates tab, select a certificate.
c. Click Actions → Edit to open the Edit window.
d. Enter the friendly name, then click OK.
Search for a certificate

You can add a certificate to permit installation and execution of software signed by the certificate.
You can search for a certificate based on its category.
Task
2. On the Certificates tab, under Search Certificate, select a category to sort the listed certificates.
◦ Issued To — Sorts the list by the name of the organization that publishes the certificate.
◦ Issued By — Sorts the list by the name of the signing authority.
◦ Extracted From — Sorts the list by the path of the file from which the certificate was extracted.
◦ Friendly Name — Sorts the list by the friendly name of the certificate.
3. Type the string to search for and click Search.
Verify assignments for a certificate

You can verify if each certificate is assigned to the appropriate policies and rule groups.
Task
2. On the Certificates tab, select a certificate, then click Actions → Check Assignments.
Results
The Certificate Assignments dialog box lists the rule groups and policies where the selected certificate is assigned.
Add a certificate to a policy or rule group

After you add a certificate to McAfee ePO, you can assign it to a policy or rule group. After you add a certificate as trusted or
authorized, you can run all software, signed by the certificate on a protected system without entering Update mode.
Task
1. Assign a certificate to a policy by defining a trusted certificate in a policy.
a. On the Rule Groups tab, locate your Group Name and under Actions, click Edit.
b. On the Certificates tab, click Add.

c. Search for and add the certificate.
d. (Optional) Select Add Certificate as Updater to provide updater rights to the certificate.
e. Click OK.
2. Assign a certificate to an existing rule group.
b. On the Certificates tab, select the certificates to add to a rule group.
c. Click Actions → Add to Rule Group to open the Add to Rule Group dialog box.
d. Select the user-defined rule group for adding the certificates, then click OK.
Using certificates in a standalone environment

Add certificates in a standalone environment
You can add certificates as trusted or authorized certificates to run all software signed by those certificates on a protected
system.
Note: Application Control supports only X.509 certificates.
Task
Add a certificate:
sadmin cert add
Use an existing certificate or extract certificates from one or more signed files. You can extract certificate from any signed file
using ScGetCerts.exe (<Install_dir>\Tools\ScGetCerts\ScGetCerts.exe).
Syntax Description
sadmin cert add <certificatename> Adds a certificate as a trusted certificate.

For example: sadmin cert add mcafee.cer
sadmin cert add –c Use the -c argument to specify the certificate content as trusted.
<certificatecontent> For example: sadmin cert add –c
MIIFGjCCBAKgAwIBAgIQbwr3oyE8ytuorcGnG3VhpDANBgkqhkiG9w0BAQUFADCB
tDELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2Ug
YXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwNDEuMCwGA1UEAxMl
VmVyaVNpZ24gQ2xhc3MgMyBDb2RlIFNpZ25pbmcgMjAwNCBDQTAeFw0wNTEyMTAw
MDAwMDBaFw0wNjEyMTAyMzU5NTlaMIHdMQswCQYDVQQGEwJVUzETMBEGA1UECBMK
Q2FsaWZvcm5pYTERMA8GA1UEBxMIU2FuIEpvc2UxIzAhBgNVBAoUGkFkb2JlIFN5
c3RlbXMgSW5jb3Jwb3JhdGVkMT4wPAYDVQQLEzVEaWdpdGFsIElEIENsYXNzIDMg
LSBNaWNyb3NvZnQgU29mdHdhcmUgVmFsaWRhdGlvbiB2MjEcMBoGA1UECxQTSW5m
b3JtYXRpb24gU3lzdGVtczEjMCEGA1UEAxQaQWRvYmUgU3lzdGVtcyBJbmNvcnBv
cmF0ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAJcS8Tyuz/JSB6XlyV5Z
d02tIo4iZoXANFxbGVXS3Yg4v7zIR8k2K0Tzzpmz3Y00Qr237nTslDnLb4rMx9Fr
+DmH1Fq2CwQBCVTnrwbtdUyv2v977Fc05B09WEJvZmvcm22iNrfpCV5wqd7OTp1F
qP2HIMa0ihztWAc3R9cn8xPPAgMBAAGjggF/MIIBezAJBgNVHRMEAjAAMA4GA1Ud DwEB/
wQEAwIHgDBABgNVHR8EOTA3MDWgM6Axhi9odHRwOi8vQ1NDMy0yMDA0LWNy
bC52ZXJpc2lnbi5jb20vQ1NDMy0yMDA0LmNybDBEBgNVHSAEPTA7MDkGC2CGSAGG
+EUBBxcDMCowKAYIKwYBBQUHAgEWHGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9y
cGEwEwYDVR0lBAwwCgYIKwYBBQUHAwMwdQYIKwYBBQUHAQEEaTBnMCQGCCsGAQUF
BzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20wPwYIKwYBBQUHMAKGM2h0dHA6
Ly9DU0MzLTIwMDQtYWlhLnZlcmlzaWduLmNvbS9DU0MzLTIwMDQtYWlhLmNlcjAf
BgNVHSMEGDAWgBQI9VHo+/49PWQ2fGjPW3io37nFNzARBglghkgBhvhCAQEEBAMC
BBAwFgYKKwYBBAGCNwIBGwQIMAYBAQABAf8wDQYJKoZIhvcNAQEFBQADggEBAFY7
rAYt9WjCDFQ+YNHfnEZxav3zhGhTdTwqGpWZJh/wg9IgLnyRqMnoQNjDFsSCduxf
FryGREMwCHI/PvEYq7hKZsUXSGWRNl+Auuomg0OFGG1ZlBv/rWtQEbwmGKgtwXMD

Syntax Description
Dm2IYY3t7O7shG3KW4qHg+Tq04pR8VGTGJodwZWEsj9JavErsujI7SFDMkj9xFz4 VD/
ilkWF+AyzSLAyUTq797y/7TsG5Y1SeMtze49cVbJVRrbGtq3kSzF56adsA4Hv
v2CjM379GkYX0Atro74YLEwcfwdAogZ+F+XtOU9CR48bPvkFP5xMLUJ46HPs1u83
Jk2lrr5OYmtMqd7f0
sadmin cert add –u Add trusted certificates as updaters using the -u argument.
<certificatename> For example:
sadmin cert add –u mcafee.cer
Caution: Selecting this option makes sure that all files signed by a certificate
acquire updater rights. For example, if you set the Microsoft certificate that signs
the Internet Explorer application as an updater, Internet Explorer can download
and execute any application from the Internet. In effect, any file added or modified
by an application that is signed by the certificate is added to the whitelist
automatically.
Extracting certificates
The ScGetCerts utility extracts a certificate from a file. This utility can also run on systems where the whitelist is not created.
The ScGetCerts utility is shipped with the product and it gets installed in the Application Control installation directory. The default
location of ScGetCerts is C:\Program Files\McAfee\Solidcore\Tools\ScGetCerts.
Here is the syntax of the command to extract certificates.
scgetcerts.exe [<FILEPATH: filename|directory>] [OUTPUT PATH] [--cab] <-A> <-O> <-n|-c> [<DOMAIN>] [<USERNAME>]
[<PASSWORD>]
To extract certificate from a file, specify the file path with the file name or the directory path where the file is located. If you
specify a directory name, certificate, or installer information, certificates are extracted recursively from all files to the specified
directory. Also, specify the output directory path where you want to store the extracted certificates, installer information, or both.
This table describes the supported parameters:
Parameter Description
--cab It extracts certificate from a cab file. When you specify the --cab parameter, you must
specify the -O parameter with it.
-A It extracts all certificates from a file. By default, only the root certificate is extracted.
-O Specify this optional parameter if only the certificates are required to be extracted and not
the additional information. But, this parameter is not optional if --cab parameter is also
specified.
-c It checks if the path of the file is accessible on the network.
-n It provides authentication to the directory path on the network. The -n option is specified
only when you specify the directory path.
Note: Mention the domain, user name, and password when –n or –c parameter is used.
View certificates
You can view certificates in the Application Control certificate store to verify that the trusted certificates are added to the system.
Task

Syntax Description
sadmin cert list Lists the SHA-1 and SHA-256 of certificates that are added as
trusted or authorized certificate in the Application Control
certificate store.
sadmin cert list -d Lists details of the issuer and subject of the certificates added
to the system.
sadmin cert list -u Lists all certificates with updater permissions.
Remove certificates
You can delete certificates from the Application Control certificate store to remove their trusted or authorized status. Such
certificates cannot run the software signed by the trusted certificates on a protected system.
Task
sadmin cert remove
Syntax Description
sadmin cert remove <SHA-1 or Removes a certificate that is added as a trusted certificate using the SHA-1 or
SHA-256> SHA-256 value. Specify the SHA-1 or SHA-256 value of the certificate to remove the
certificate from the Application Control certificate store.
For example:
sadmin cert remove 7ecf2b6d72d8604cf6217c34a4d9974be6453dff
sadmin cert remove –c Use the –c argument to remove specified certificate content from the Application
<certificatecontent> Control certificate store.
For example:
sadmin cert remove –c
MIIFGjCCBAKgAwIBAgIQbwr3oyE8ytuorcGnG3VhpDANBgkqhkiG9w0BAQUFADCB
tDELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2Ug
YXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwNDEuMCwGA1UEAxMl
VmVyaVNpZ24gQ2xhc3MgMyBDb2RlIFNpZ25pbmcgMjAwNCBDQTAeFw0wNTEyMTAw
MDAwMDBaFw0wNjEyMTAyMzU5NTlaMIHdMQswCQYDVQQGEwJVUzETMBEGA1UECBMK
Q2FsaWZvcm5pYTERMA8GA1UEBxMIU2FuIEpvc2UxIzAhBgNVBAoUGkFkb2JlIFN5
c3RlbXMgSW5jb3Jwb3JhdGVkMT4wPAYDVQQLEzVEaWdpdGFsIElEIENsYXNzIDMg
LSBNaWNyb3NvZnQgU29mdHdhcmUgVmFsaWRhdGlvbiB2MjEcMBoGA1UECxQTSW5m
b3JtYXRpb24gU3lzdGVtczEjMCEGA1UEAxQaQWRvYmUgU3lzdGVtcyBJbmNvcnBv
cmF0ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAJcS8Tyuz/JSB6XlyV5Z
d02tIo4iZoXANFxbGVXS3Yg4v7zIR8k2K0Tzzpmz3Y00Qr237nTslDnLb4rMx9Fr
+DmH1Fq2CwQBCVTnrwbtdUyv2v977Fc05B09WEJvZmvcm22iNrfpCV5wqd7OTp1F
qP2HIMa0ihztWAc3R9cn8xPPAgMBAAGjggF/MIIBezAJBgNVHRMEAjAAMA4GA1Ud DwEB/
wQEAwIHgDBABgNVHR8EOTA3MDWgM6Axhi9odHRwOi8vQ1NDMy0yMDA0LWNy
bC52ZXJpc2lnbi5jb20vQ1NDMy0yMDA0LmNybDBEBgNVHSAEPTA7MDkGC2CGSAGG
+EUBBxcDMCowKAYIKwYBBQUHAgEWHGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9y
cGEwEwYDVR0lBAwwCgYIKwYBBQUHAwMwdQYIKwYBBQUHAQEEaTBnMCQGCCsGAQUF
BzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20wPwYIKwYBBQUHMAKGM2h0dHA6
Ly9DU0MzLTIwMDQtYWlhLnZlcmlzaWduLmNvbS9DU0MzLTIwMDQtYWlhLmNlcjAf
BgNVHSMEGDAWgBQI9VHo+/49PWQ2fGjPW3io37nFNzARBglghkgBhvhCAQEEBAMC
BBAwFgYKKwYBBAGCNwIBGwQIMAYBAQABAf8wDQYJKoZIhvcNAQEFBQADggEBAFY7

Syntax Description
rAYt9WjCDFQ+YNHfnEZxav3zhGhTdTwqGpWZJh/wg9IgLnyRqMnoQNjDFsSCduxf
FryGREMwCHI/PvEYq7hKZsUXSGWRNl+Auuomg0OFGG1ZlBv/rWtQEbwmGKgtwXMD
Dm2IYY3t7O7shG3KW4qHg+Tq04pR8VGTGJodwZWEsj9JavErsujI7SFDMkj9xFz4 VD/
ilkWF+AyzSLAyUTq797y/7TsG5Y1SeMtze49cVbJVRrbGtq3kSzF56adsA4Hv
v2CjM379GkYX0Atro74YLEwcfwdAogZ+F+XtOU9CR48bPvkFP5xMLUJ46HPs1u83
Jk2lrr5OYmtMqd7f0
sadmin cert flush Removes all certificates from the Application Control certificate store.
Using updaters
What are updaters?
Updaters are authorized components that are allowed to make changes to the system.
If a program is configured as an updater, it can install new software and update existing software. By default, if you provide
updater rights to a component, the child component automatically inherits the same rights.
Updaters work at a global-level and aren't application-specific or license-specific. When a program is defined as an updater, it can
change any protected file.
An updater isn't authorized automatically. To be authorized, an updater must be in the whitelist or given explicit authorization
(defined as allowed via a policy or added as updater based on SHA-1 or SHA-256).
Caution: We advise caution when assigning updater rights to executable files. If you set an executable as an updater and invoke
any executable from it, it can perform any change on the protected endpoints.
You can also add scripts as updaters. This feature is called Script as Updaters (SAU) and it gives updater rights to scripts (such
as .bat, .vbs, and .py). When enabling Application Control, the SAU feature is available by default after the endpoint is restarted.
Application Control also includes predefined default updater rights for commonly used applications that might need to update
the systems frequently. These applications are known as default updaters.
Script as Updater feature

If a program is configured as an updater, it can install new software and update existing software. With the Script as Updaters
(SAU) feature, you can give updater rights to scripts (such as .bat, .vbs, and .py).
Script as Updater (SAU) and Memory-protection (MP) features are enabled by default. But when you perform a clean installation
and enable Application Control, you can permanently disable these features.
Important: These features can be permanently disabled only when installing Application Control in a managed McAfee ePO
environment. In standalone mode, the SAU feature is available by default after the endpoint is restarted.
Disabling SAU and MP features in the Initial Feature configuration is permanent. You can’t enable them again after installation. Any
change of MP or SAU status through a policy is ignored by the endpoint.
Permanently disable SAU

When you perform a clean installation and enable Application Control, you can permanently disable Script as Updater (SAU) and
Memory-protection (MP) features.
Important: This initial feature configuration is available only in a clean install. If you upgrade from a previous version, the SAU
feature is enabled. If after the upgrade you want to disable SAU, you must introduce the change with a policy.
Task
2. Select a group or an endpoint and go to Actions → Agent → Run Client Task Now.
a. Under Product, Select Solidcore 8.2.0.
b. Under Task Type, select SC: Enable.
c. Under Task Name, click Create New Task.
3. On the Run Client Task Now page:
a. Choose the Platform and Sub Platform.

b. Under Enable, select Application Control.
4. For Initial Feature configuration, you can select:
a. MP disabled
b. SAU disabled
5. Select an option for activation:
a. Limited Feature Activation
b. Full Feature Activation
6. (Optional) Select Start Observe Mode to place the endpoints in Observe mode.
7. (Optional) Select Pull Inventory to manage the inventory with McAfee ePO.
8. Click Run Task Now.
Results
Important: Disabling SAU and MP features in the Initial Feature configuration is permanent. You can’t enable them again after
installation. Any change of MP or SAU status through a policy is ignored by the endpoint.
Add feature columns to the System Tree

On McAfee ePO, you can configure the columns on the System Tree page to see the status of the features.
You can see the status of the features (SAU, MP, and others) in all endpoints by adding the corresponding feature columns. These
columns allow you to filter all endpoints depending on the status of the features.
Task
2. Select the endpoints and go to Actions → Choose Columns.
3. On the left pane, go to Application Control Features Status and select the columns you want to add to the System Tree.
4. Click Save.
Disable SAU after upgrading the software

If you upgrade from a previous version, the Script as Updater (SAU) feature is enabled by default. If after the upgrade you want to
disable SAU, you must introduce the change with a policy.
Task
1. Go to Menu → Policy → Policy Catalog.
a. Select the Solidcore 8.2.0: Application Control product.
b. Select Application Control Options (Windows) category.
2. Choose McAfee Default or My Default policy and click Duplicate.
3. Once the policy is duplicated, click the name of the policy and go to the Features tab.
a. Select Enforce feature control from McAfee ePO.
b. Select or deselect the features you want to disable.
c. Click Save.
4. To implement the policy, go to System Tree and select the endpoint.
5. Go to Actions → Agent → Set Policy & Inheritance.
a. Select the Product, Category, and Policy.
b. Click Save.
6. Select the endpoint and click Wake up Agent.
a. Complete the information on the Wake Up McAfee Agent page.
b. Select Force complete policy and task update.
c. Click OK.
7. Reboot the endpoints to implement the policy.
Add updaters in a managed environment

If a program is configured as an updater, it can install new software and update existing software.
You can add an updater to a policy or a rule group.

Task
1. Add an updater to a rule group.
b. Locate the rule group and under Actions, click View.
c. On the Updater Processes tab, you can Add, Edit, or Remove an updater.
2. Add an updater to a policy.
a. On the McAfee ePO console, select Menu → Policy → Policy Catalog.
b. On the Policy Catalog page, select the product and category from the list.
c. Click the selected policy.
3. Complete the addition of an updater to a rule group or policy.
a. On the Updater Processes tab, click Add.
b. Specify whether to add the updater based on the file name, SHA-1, or SHA-256.
If you add the updater by name, the updater is not authorized automatically. The file must be added to the whitelist.
c. Enter the location of the file (when adding by name), or the SHA-1 or SHA-256 value of the executable file.
d. Specify an identification updater label for the program.
e. When adding an updater by name, specify conditions that the file must meet to run as an updater.
◦ Select condition None to allow the file to run as an updater without any conditions.
◦ Select condition Library to allow the file to run as updater only when it has loaded the specified library. For example, when
configuring iexplore.exe as an updater to allow Windows Updates using Internet Explorer, specify wuweb.dll as the
library. This makes sure that the iexplore.exe program has updater rights only until the web control library (wuweb.dll) is
loaded.
◦ Select condition Parent to allow the file to run as an updater only if it is launched by the specified parent. For example,
when configuring updater.exe as an updater to allow changes to Mozilla Firefox, specify firefox.exe as the parent.
Although updater.exe is a generic name that can be part of any installed application, using the parent makes sure that
only the correct program is allowed to run as an updater.
f. When adding an updater by name, indicate whether to disable inheritance for the updater.
For example, if Process A (that is set as an updater) starts Process B, disabling inheritance for Process A makes sure that
Process B does not become an updater.
g. When adding an updater by name, indicate whether to suppress events generated for the actions performed by the
updater. Typically, when an updater changes a protected file, a File Modified event is generated for the file. If you select this
option, no events are generated for changes made by the updater.
h. Click OK.
Add updaters in a standalone environment

You can add components such as installers, scripts, binaries, users, or certificates as updaters.
Important: If a program is configured as an updater, it can install new software and update existing software.
Task
◦ sadmin updaters add <filename>
2. Add installers as updaters.
◦ Windows installer – To add Windows installer for Hotfix KB893803 as an updater, use this command: sadmin updaters add
WindowsInstaller-KB893803-v2-x86.exe
◦ Microsoft installer (MSI-based installer) – To add MSI-based installer Ica32Pkg.msi and perform automatic updates on
protected files or registry keys, use this command:sadmin updaters add Ica32Pkg.msi
3. Add scripts as updaters.
◦ sadmin updaters add <scriptname>
◦ sadmin updaters add myscript12.bat
Use the cmd interpreter with the /C parameter (cmd /C) to run scripts as updaters. For example, cmd /C myscript12.bat. Using
the /C parameter ensures that the specified command is executed and stopped.
Note: Adding scripts as updaters is available on all Windows platforms except Windows Server 2003 (IA64).
4. Add binaries as updaters.

◦ sadmin updaters add <filename>
◦ sadmin updaters add update.exe
5. Add users as updaters.
◦ sadmin updaters add –u <username>
◦ sadmin updaters add –u john_smith|john_smith@mycompany.com|mydomain\john_smith
6. Add certificates as updaters.
◦ sadmin cert add –u <certfilename>
◦ sadmin cert add –u firefox.cer
All components signed by these certificates are allowed to change binaries on the system and start new applications.
7. This table lists the supported arguments, descriptions, and examples.
Argument Description
-d Excludes the child process of the file from inheriting the updater permissions.
sadmin updaters add –d <filename>
sadmin updaters add –d winlogon.exe
-n Disables event logging for a file to be added as an updater.

sadmin updaters add –n <filename>
sadmin updaters add –n winlogon.exe
-l Use this argument to add an execution file as an updater only when the specified library name is
loaded for the execution file.
sadmin updaters add -l <associated libraryname> <filename>
sadmin updaters add –l system32\wuauserv.dll svchost.exe
-t Performs these operations:

◦ Include the tags for a file to be added as an updater.
sadmin updaters add -t <associated tag> –l <associated libraryname> <filename>
sadmin updaters add –t Win_up_schedule1 –l system32\wuauserv.dll svchost.exe
◦ To add a user with a tag name as an updater.
sadmin updaters add –t <tagname> –u <username>
sadmin updaters add –t McAfee001 -u john_smith
-p Adds a file as an updater, only when its parent execution file is running.
sadmin updaters add -p <parentname> <filename>
sadmin updaters add –p svchost.exe iexplore.exe
-u Adds a user as an updater. All update operations by the specified user name are allowed.
Note: When you specify the –u argument, other arguments, such as -l, -p, -d, and –n are not
applicable.
sadmin updaters add –u <username>
Here are the types of user names that can be added as updaters.
◦ Simple name
For example, john_smith.
If you specify a simple name, users with this name in all domains are added as updaters.
◦ Domain name (username@domain name)
For example, john_smith@mycompany.com.
◦ Hierarchical domain name (domain name\user name)
For example, mydomain\john_smith.
If you right-click a file and select Run as <updater user name>, the file can run as an updater only if the file is
added to the whitelist and authorized to run.

Specifying files to be added as updaters
You can specify files using the file name or checksum value.
This table describes the methods to specify a file to be added as an updater.
Method Description
Specify the file name If the file name is added as an updater, the updater permissions apply only to the
file name and, even if the file path is changed, the updater permissions are in
effect.
You can specify the absolute or relative path of the file. But, if you specify the
absolute path of the file as an updater, the updater permissions are applicable
only to that specific path. For example, if dir\file.exe is specified, the updater rule
applies only if file.exe is in a directory named dir.
If you specify full path names with the drive letter, the drive letter isn't considered.
For example, if you specify C:\foo\bar.exe, the updater rule is added for \foo
\bar.exe only and does not include the drive letter.
Paths can include wildcard characters to specify file paths and file names.
• Paths can include the * and ? wildcard characters. When specifying a file path
for an updater rule, ?:\Test1\Test2\Test.exe, C:\?Test*QA\Test1\Test.exe, C:
\Test1\?\?\Test.exe and C:\*\*\Test.exe are allowed while *:\Test1\Test2\Test.exe
and *:\Test1\*\*\Test.exe aren't supported.
Specify the file SHA-1 or file SHA-256 If the file SHA-1 or file SHA-256 is added as an updater, it allows only the file with
that SHA-1 or SHA-256 value to be added as an updater. This makes sure that
regardless of the source of the file, if the SHA-1 or SHA-256 value matches, the file
is allowed as an updater.
You can specify the checksum value to be added as an updater by using the
sadmin auth –a –u –c <checksumvalue> command.
Note: Specifying checksum value to be added as an updater isn't supported for
scripts. Scripts can't be added as updaters by this method.
Discover potential updaters

You can identify a list of possible updaters that can be added in a Windows system. In the feature list, this is identified as
discover-updaters.
When running in Enabled mode, Application Control protection can prevent a legitimate application from running (if the required
rules are not defined). The software tracks all failed attempts made by authorized executable to change protected files or run
other executable files. You can review the information of failed attempts to identify update rules to allow legitimate applications
to run.
Task
1. Get a list of components that can be added as updaters: sadmin diag
Note: Review the list to ensure that no restricted program or programs with generic names such as, setup.exe, are set as
authorized updaters.
The output of executing this command displays these configuration parameters.
Symbol Configuration Rules
! The configuration for the program exists. The existing configuration is displayed on the next
line.
* The configuration is for a restricted program, which can provide capability to change the
system. Hence, such programs must have restricted configuration.

Symbol Configuration Rules
* and ! The configuration of the program exists but some changes are required in the configuration
to execute the program successfully.
2. Apply the diagnosed configuration changes: sadmin diag fix

3. Apply the diagnosed configuration changes for restricted programs: sadmin diag fix -f
Restricted programs are Windows critical programs. For example, services.exe, winlogon.exe, svchost.exe, and explorer.exe.
View updaters in a standalone environment

Updaters are authorized components that are permitted to update the system. When a program is defined as an updater, it can
change any protected file.
Task
View the list of all components defined as updaters on the system: sadmin updaters list
Remove updaters in a standalone environment

You can remove updaters to restrict them from making changes to the system.
Task
1. Delete all components from the updaters list:
sadmin updaters flush
2. Remove a specific component from the updaters list:
sadmin updaters remove
This table lists how to remove specific components as updaters.
Component Command
Installers sadmin updaters remove <installername>

sadmin updaters remove Ica32Pkg.msi
Scripts sadmin updaters remove <scriptname>

sadmin updaters remove myscript12.bat
Binaries sadmin updaters remove <filename>

sadmin updaters remove update.exe
Note: After using this command, restart the system to remove the binaries from the
updaters list.
Users sadmin updaters remove -u <username>

sadmin updaters remove -u john_smith
Note: After using this command, restart the system to remove users from the updaters
list.
Configure processes and certificates

On the McAfee ePO console, you can configure updaters by editing the list of generic launcher processes and restricted
certificate names.
You can configure these settings:
• Generic launcher processes — Certain processes on the Windows operating system, such as explorer.exe and iexplore.exe,
start other processes and can be used to start any software. Such processes are referred to as generic launcher processes and
must never be configured as updaters. A predefined list of such processes is available on the Application Control configuration
interface. You can review and edit the list of generic launcher processes. No updater rules are generated for generic launcher
processes at the endpoints.

• Restricted certificate names — Certificates from certain vendors such as Microsoft are associated with multiple commonly
used applications. They should not be used to define rules based on the certificate. A predefined list of such certificates is
available on the Application Control configuration interface. You can review and edit the list of restricted certificate names. If
the file in a request is signed by one of these certificates, you can't create rules based on the certificate associated with the file.
Task
1. On the McAfee ePO console, select Menu → Configuration → Server Settings → Solidcore.
2. Review and edit the list of generic launcher processes.
a. Review the processes listed in the Generic launcher processes field.
b. Click Edit to update the list.
c. Add the process name to the end of this list (separated by a comma), then click Save.
3. Review and edit the list of restricted certificates.
a. Review the names listed in the Restricted certificate names field.
c. Add the vendor name to the end of this list (separated by a comma), then click Save.
For example, to prevent creation of rules based on the Microsoft certificate, add Microsoft to the list. Use the value listed
in the ISSUED TO field of the certificate.
Using interpreters
You can configure interpreters to control the execution of additional scripts.
Unlike executables, a script needs an interpreter to read and execute the instructions written in a scripting language. To manage
execution of scripts in your setup:
1. Check that relevant interpreters and scripts are whitelisted.

2. Map appropriate file extensions of scripts with specific interpreters.
On the Windows platform, by default, if no interpreter is associated with a script file, the script is allowed to execute because
Application Control doesn't treat it as a script file. By default, the software supports standard interpreters and script files that are
integrated with Windows operating system, such as batch files (.bat), command interpreter (.cmd), script files (.vbs), PowerShell
files (.ps1), and Command files (.com).
When you execute an interpreter to run a script file, these checks that are performed.
Application Control provides additional and granular control for file and script execution. For example, you can choose to block
an interpreter from running except when run by a specific user or by specific arguments.
Map an interpreter with a file extension

You can associate an interpreter with a file or script extension to control execution for a certain script type.

Task
sadmin scripts add extension interpreter1 [interpreter2]...
The file with specified extension or type is associated with the specified interpreters.
sadmin scripts add .vbs wscript.exe cscript.exe
This command enables Application Control to enforce that wscript.exe and cscript.exe can execute a .vbs script (when the script
file and interpreters are whitelisted). After the association is defined, wscript.exe and cscript.exe can also execute other script
files (provided the interpreter can read and understand the instructions in the script file). The association is effective immediately
and applies to all new interpreter instances initiated after running this command.
If needed, you can add associate additional interpreters with a script or file type. For example:
sadmin scripts add .vbs zscript.exe
If you try to add an interpreter that is already associated with a file or extension type, no action is taken.
Note: Application Control supports a special tag 16 Bits as a synthetic extension for the 16-bit binaries. To control execution for
the 16-bit binaries, execute these commands.
• sadmin scripts add 16Bit wowexec.exe
• sadmin scripts add 16Bit ntvdm.exe
View interpreter and file extension associations

You can view the existing interpreter and file or script extension associations defined in your setup to control file execution.
Task
sadmin scripts list
Sample output appears like this:
.ps1 "powershell.exe"
.bat "cmd.exe"
.cmd "cmd.exe"
.pif "ntvdm.exe"
.sys "ntvdm.exe"
.vbe "cscript.exe" "wscript.exe"
16Bit "ntvdm.exe" "wowexec.exe"
.vbs "cscript.exe" "wscript.exe"
.exe "ntvdm.exe"
Remove interpreter and file extension associations

Remove existing interpreter and file or script extension associations defined in your setup.
Task
Run one of these command at the command prompt.
• sadmin scripts remove extension [interpreter1 [interpreter2]]... — Removes the specified interpreter associations for
the file or script type.
• sadmin scripts remove extension — Removes all interpreter associations for the specified file or script type.
Using installers in a managed environment

What are installers?
On a McAfee ePO console, when a program is configured as an authorized installer, it gets attributes of authorized executable
and updater. It can execute and update software on the endpoint.
An authorized installer is allowed based on its SHA-1 or SHA-256 which is specified while configuring the policy. Regardless of the
source of the installer, if the SHA-1 or SHA-256 matches, the installer is allowed to run. But, if the reputation of the installer is
malicious, its execution is blocked. The reputation of the installer is determined based on the SHA-1 value of an executable file.
Reputation sources, such as McAfee GTI and TIE server don't support SHA-256 reputation-based workflows. For example, if you
add the installer for the Microsoft Office 2010 suite as an installer and if the SHA-1 or SHA-256 matches, the installer can install
the Microsoft Office suite on the protected endpoints.

Control installation and uninstallation
You can manage the installation and uninstallation of software packages using the Package Control feature.
This feature allows or denies installation, uninstallation, upgrade, and repair actions for software packages. It also prevents any
unauthorized installation and uninstallation.
Package Control is identified as pkg-ctrl in the features list and it supports all types of installers on the Windows platform. By
default, this feature is enabled and it allows or blocks the installation based on the reputation information and defined rules.
• If the reputation information is available, this feature allows or blocks installation of software packages based on these
conditions.
Installer type Description Condition

Microsoft Installers (MSI) This installer type includes multiple variants such If the reputation of the certificate (that
as .msp, .mst, and .msm. has signed the installer file) is trusted,
installation of software packages is
allowed.
EXE-based installer This installer includes MSI files embedded with If the installer file is configured as an
the installer. updater, the reputation of the installer
file is trusted, or if the reputation of any
associated certificate is trusted,
installation of software packages is
allowed.
Non-MSI-based installers This installer does not include an MSI file Package Control considers these
embedded with it. conditions to allow or block installation:
◦ It considers the reputation of
the installer file or the
reputation of the certificate.
The reputation must be
trusted.
◦ It uses a heuristics-based
identification for the installer
file.
◦ It considers whether the
installer file is included or
excluded from the list of
generic launcher processes,
such as explorer.exe and
svchost.exe.
• If the reputation information isn't available, installation is allowed or blocked based on the defined rules such as updater by
name or path, users, directories, certificate as an updater, SHA-1 or SHA-256 as an updater.
When this feature is disabled, software installation and uninstallation are blocked.
Package Control includes these subfeatures.
Subfeature Description
Allow Uninstallation It controls the uninstallation of software packages. When this feature is enabled, software
uninstallation, upgrade, and repair actions are allowed. By default, this feature is enabled and
identified as pkg-ctrl-allow-uninstall in the features list.
Bypass Package Control This feature controls bypassing from the Package Control feature. When this feature is enabled,
Package Control feature is bypassed and software installation and uninstallation is allowed. By
default, this feature is disabled and identified as pkg-ctrl-bypass in the features list.

By default, the Package Control and Allow Uninstallation features are enabled. You can uninstall any software from the system.
But, if the reputation of the uninstall file is malicious (Known Malicious, Most Likely Malicious, or Might be Malicious), software
uninstallation isn't allowed regardless of the Package Control configuration. If the reputation of the installer file or MSI file is
malicious, software installation isn't allowed regardless of the Package Control configuration. Use this default configuration for
desktop and System Center Configuration Manager (SCCM)-managed environments. This configuration allows change, repair,
remove, or upgrade operations for software that are useful in these scenarios.
• Explicit software upgrades.
• Software upgrades through Windows update mechanisms.
• Software upgrades of existing software while installing new software packages in chained installations.
• Rollback if there is a power failure or if you restart your system during installation. This is called a suspended installation. The
installer tracks the installation that is in progress. When resumed, you can roll back the suspended installation or continue the
suspended installation.
If needed, you can also change the default configuration to:
• Disable the Allow Uninstallation feature — Prevents you from uninstalling software from the system. Use this configuration for
fixed-function devices and server environments for all actions except upgrades. For upgrading software in server
environments, you must switch to the default configuration because it blocks change, repair, remove, or upgrade operations
for software.
• Enable the Bypass Package Control feature — Allows software installation and uninstallation on the system except when the
file has malicious reputation.
• Disable the Package Control feature — Prevents software installation and uninstallation on the system.
• Place the system in Update mode — this configuration allows software installation and uninstallation on the system except
when the file has malicious reputation.
Add an installer to McAfee ePO

Before defining rules to permit an installer to install or update software on endpoints, you must add the installer. You can add an
executable or script file.
Use one of these methods to add an installer.
Task
1. Add an existing installer.
b. On the Installers tab, select Actions → Add Installer to open the Add Installer page.
c. Enter the installer details.
d. Click Add.
2. Schedule a server task to routinely add installers.
a. Select Menu → Automation → Server Tasks.
b. Click New Task to open the Server Task Builder wizard.
c. Type the task name, then click Next.
d. Select Solidcore: Scan a Software Repository from the Actions drop-down list.
e. Specify the repository path.
All subfolders in the specified path are also scanned for installers and certificates.
f. Specify the network credentials to access the specified network location.
g. Click Test Connection to make sure that the specified credentials work.
h. Select Add extracted certificates and installers to Rule Group to add the certificates and installers extracted by the task to a user-
defined rule group and select the user-defined rule group from the list.
Note: You can add extracted certificates and installers only to user-defined rule groups.
i. Click Next.
j. Specify the schedule for the task.
k. Click Next to open the Summary page.
l. Review the task summary, then click Save.

Add an installer to a policy or rule group
After you add an installer, you can assign it to a policy or rule group to allow users to install new software and update the
software components on a protected endpoint.
Task
1. On the McAfee ePO console, create or change an Application Control policy or rule group.
Note: To create a rule group, see Create a rule group.
3. On the Installers tab, click Add.
4. Search for and add the installer.
5. Specify an identification label for the installer.
6. Click OK.
Verify assignments for an installer

This feature provides a convenient way to verify if each installer is assigned to the relevant policies and rule groups.
Task
2. On the Installers tab, select an installer, then click Actions → Check Assignments.
The Installer Assignments dialog box lists the rule groups and policies where the selected installer is assigned.
3. Click OK.
Configure Package Control

You can configure Package Control to control the installation and uninstallation of software packages on a system.
Task
2. Select the Solidcore 8.x.x: Application Control product.
3. Select the Application Control Options (Windows) category.
4. Click the My Default policy to edit it.
Note: By default, the My Default policy is applied to all endpoints in your enterprise. To configure the feature for selected
endpoints, duplicate the My Default policy, edit the settings, and apply the policy to only the relevant endpoints.
5. On the Features tab:
a. Select Enforce feature control from McAfee ePO.
By default, the Package Control and Allow Uninstallation options are selected.
b. Select an option for configuring Package Control.
Option Action Description
Package Control Enable When enabled, all subfeatures revert to their default state. But,
if you enable the Bypass Package Control subfeature, disable
and re-enable Package Control, the Bypass Package Control
subfeature is still enabled and in effect.
Disable Disabling this feature also disables all its subfeatures.
Allow Uninstallation Enable When enabled, this feature allows uninstallation of software
packages on endpoints.
Disable When disabled, it prevents uninstallation of software packages

on endpoints.
Bypass Package Control Enable When enabled, Package Control is bypassed and you can't
control the installation and uninstallation of software packages.

Option Action Description
Disable Disables the feature.
Using events
What are events?
Any action to change or execute a file or program on a protected system causes Application Control to prevent the action and
generate a corresponding event on the endpoint.
When using the software in a standalone environment, you can review the event list using McAfee Agent.
All events for managed systems are sent to the McAfee ePO server. You can review and manage the generated events to monitor
the status of the managed endpoints.
View and manage events in a managed environment

All generated events for managed systems are sent to the McAfee ePO server. You can review and manage the generated events
to monitor the status of the managed endpoints.
Task
1. On the McAfee ePO console, select Menu → Reporting → Solidcore Events.
2. Specify the time duration for which to view events by selecting an option from the Time Filter list.
3. Choose the endpoints where you want to view events.
a. Select the required group in the System Tree.
b. Select an option from the System Tree Filter list.
4. (Optional) View only specific events by applying one or more filters.
a. Click Advanced Filters to open the Edit Filter Criteria page.
b. Select a listed property.
c. Specify the comparison operator and property value.
For example, to view only Execution Denied events, select the Event Display Name property, set comparison to Equals, and select
the Execution Denied value.
d. Click Update Filter.
Events matching the specified criteria are displayed.
5. (Optional) Add user comments for one event or multiple events:
◦ One event — Click Add a comment link.
◦ Multiple events — Select the events, click Actions → Add Comments, then enter your comments and click OK.
Create custom rules

For most events, you don't need to take any action. But, if the protection that is in effect is preventing a legitimate application
from executing, you must define rules.
To allow you to define rules with ease, Application Control generates events and corresponding observations for these events.
Task
2. Specify the time duration for viewing events by selecting an option from the Time Filter list.
3. Specify the endpoints whose events you want to view.
a. Select the required group in the System Tree.
b. Select an option from the System Tree Filter list.
4. Under Actions, click Create Policy for an event.
Detailed information for the selected event is displayed.
5. On the Monitoring Events Details page, click Create Custom Policy and define the needed rules.
6. Specify the rule group for the rules.
◦ To add the rules to an existing rule group, select Choose existing and select the rule group from the list.
◦ To create a rule group with the rules, select Create new and enter the rule group name.

7. (Optional) Add the modified or created rule group to a policy.
a. Select Add rule group to existing policy.
b. Select the policy where you want to add the rule group.
8. Click Save.
Make sure that the updated rule group is included in a policy applied to the endpoint.
Exclude events
You can define rules to prune routine system-generated events not relevant for monitoring or auditing. Exclude or ignore events
not required to meet compliance requirements.
Task
2. Select the events to exclude and click Actions → Exclude Events to open the Events Exclusion wizard.
3. Select the target platform for the rules and the rule group type, then click Next to open the Define Rules page.
Rules are auto-populated based on the selected events. Review and refine existing rules and add new rules, as needed.
4. Click Next to open the Select Rule Group page.
5. Add the rule to an existing or new rule group, then click Save.
Make sure that the rule group is added to the relevant policy and the policy is assigned to the endpoints.
View and manage events in a standalone environment

Application Control generates events when an action is taken to change or execute a file on a protected system. You can review
and manage events to monitor the status of the managed endpoints.
Task
Go the McAfee Agent icon on your desktop and select Quick Settings → Application and Change Control Events
You can see a list with all events generated for that endpoint.
Customize end-user notifications on McAfee ePO

If Change Control or Application Control prevent an action on an endpoint, you can choose to display a customized notification
message for the event on the endpoint.
You can configure the notification to be displayed on the endpoints for these events.
• Execution Denied
• File Write Denied
• File Read Denied
• Process Hijack Attempted
• Nx Violation Detected
• ActiveX Installation Prevented
• Installation Denied
• VASR Violation Detected
• Blocked Interactive Mode of Process
• Prevented File Execution
Task
2. Select the Solidcore 8.x.x: Application Control product.
3. Select the Application Control Options category and click the My Default policy to edit it.
4. Click the End User Notifications tab and select Show the messages dialog box when an event is detected and display the specified text in the message to
display a message box at the endpoint each time any of the earlier mentioned events is generated.
5. Enter the Help Desk information.
Mail To Represents the email address to which all approval requests

are sent.

Mail Subject Represents the subject of the email message sent for
approval requests.
Link to Website Indicates the website listed in the Application Control and
Change Control Events window on the endpoints.
McAfee ePO IP Address and Port Specifies the McAfee ePO server address and port.
6. Customize the notifications for the various types of events.

a. Enter the notification message.
You can use the listed variables to create the message string.
b. Select Show Event in Dialog to make sure that all events of the selected event type (such as Execution Denied) are listed in the
Application and Change Control Events window on the endpoints.
7. Save the policy and apply to the relevant endpoints.
8. From the endpoints, users can review the notifications for the events and request for approval for certain actions.
a. Right-click the McAfee Agent icon in the notification area on the endpoint.
b. Select Quick Settings → Application and Change Control Events.
The Application and Change Control Events window appears.
c. Review the events.
d. Request approval for a certain action by selecting the event and clicking Request Approval.
List of events in McAfee ePO

This table provides a detailed list of all Change Control and Application Control events.
Event names with a suffix (_UPDATE) indicate that events are generated in Update mode.
In the Event type column, these abbreviations indicate the applicable type for the event.
• SC — Solidcore client-related event
• CC — Change Control event
• AC — Application Control event
Threat event ID
Event ID (on (on McAfee Event display Solidcore client McAfee ePO
endpoints) ePO) Event name string severity severity Event type
1 20700 BOOTING_DISABLED
Booted in Disabled Warning Warning SC
mode
2 20701 BOOTING_ENABLED
Booted in Enabled Info Information SC
mode
3 20702 BOOTING_UPDATEBooted in Update Info Information SC

_MODE mode
4 20703 ENABLED_DEFERRED
Enabled On Reboot Info Information SC
5 20704 DISABLED_DEFERRED
Disabled On Reboot Warning Warning SC
6 20705 BEGIN_UPDATE Opened Update Info Information SC

Mode
7 20706 END_UPDATE Closed Update Mode Info Information SC
8 20707 COMMAND_EXECUTED
Command Executed Info Information SC
15 20714 REG_KEY_CREATEDRegistry Created Info Information CC

Threat event ID
16 20715 REG_KEY_DELETEDRegistry Deleted Info Information CC
18 20717 REG_VALUE_DELETED
Registry Deleted Info Information CC
19 20718 PROCESS_TERMINATED
Process Terminated Major Error AC
20 20719 WRITE_DENIED File Write Denied Major Error CC
21 20720 EXECUTION_DENIED
Execution Denied Major Error AC
_UNAUTH_SYSCALL
_UNAUTH_API
31 20730 MODULE_LOADING
Module Loading Major Error SC
_FAILED Failed
41 20740 FILE_ATTR_SET File Attribute Set Info Information CC
42 20741 FILE_ATTR_CLEAR File Attribute Cleared Info Information CC
43 20742 FILE_ATTR File Attribute Set Info Information CC

_SET_UPDATE
44 20743 FILE_ATTR File Attribute Cleared Info Information CC

_CLEAR_UPDATE
49 20748 REG_VALUE Registry Write Major Error CC

_WRITE_DENIED Denied
50 20749 REG_KEY Registry Write Major Error CC

_WRITE_DENIED Denied
51 20750 REG_KEY Registry Created Info Information CC

_CREATED_UPDATE
52 20751 REG_KEY Registry Deleted Info Information CC

_DELETED_UPDATE
54 20753 REG_VALUE Registry Deleted Info Information CC

_DELETED_UPDATE
56 20755 OWNER_MODIFIEDFile Ownership Info Information CC

Changed
57 20756 OWNER_MODIFIEDFile Ownership Info Information CC

_UPDATE Changed
61 20760 PROCESS_HIJACKED
Process Hijack Major Error AC
Attempted
62 20761 INVENTORY_CORRUPT
Inventory Corrupted Critical Critical AC

Threat event ID
Booted in Disabled Warning Warning SC
_SAFEMODE mode
Booted in Disabled Critical Critical SC
_INTERNAL_ERRORmode
70 20769 FILE_CREATED File Created Info Information CC
71 20770 FILE_DELETED File Deleted Info Information CC
72 20771 FILE_MODIFIED File Modified Info Information CC
73 20772 FILE_ATTR_MODIFIED
File Attribute Modified Info Information CC
74 20773 FILE_RENAMED File Renamed Info Information CC
75 20774 FILE_CREATED File Created Info Information CC

_UPDATE
76 20775 FILE_DELETED File Deleted Info Information CC

_UPDATE
77 20776 FILE_MODIFIED File Modified Info Information CC

_UPDATE
78 20777 FILE_ATTR File Attribute Modified Info Information CC

_MODIFIED_UPDATE
79 20778 FILE_RENAMED File Renamed Info Information CC

_UPDATE
80 20779 FILE_SOLIDIFIED File Solidified Info Information AC
82 20781 FILE_UNSOLIDIFIED
File Unsolidified Info Information AC
84 20783 ACL_MODIFIED File Acl Modified Info Information CC
85 20784 ACL_MODIFIED_UPDATE
File Acl Modified Info Information CC
86 20785 PROCESS_STARTEDProcess Started Info Information CC
87 20786 PROCESS_EXITED Process Exited Info Information CC
88 20787 TRIAL_EXPIRED Trial license expired Major Error SC
89 20788 READ_DENIED File Read Denied Major Error CC
90 20789 USER_LOGON User Logged On Info Information CC

_SUCCESS
91 20790 USER_LOGON_FAILUser Logon Failed Info Information CC
92 20791 USER_LOGOFF User Logged Off Info Information CC
93 20792 USER_ACCOUNT User Account Info Information CC

_CREATED Created

Threat event ID

_DELETED Deleted

_MODIFIED Modified
96 20795 PKG_MODIFICATION
Installation Denied Critical Critical AC
_PREVENTED
Installation Allowed Info Information AC
_ALLOWED_UPDATE
Installation Denied Critical Critical AC
_PREVENTED_2
99 20798 NX_VIOLATION Nx Violation Detected Critical Critical AC

_DETECTED
100 20799 REG_VALUE Registry Modified Info Information CC

_MODIFIED
101 20800 REG_VALUE Registry Modified Info Information CC

_MODIFIED_UPDATE
102 20801 UPDATE_MODE Update Mode On Info Information SC

_DEFERRED Reboot
103 20802 FILE_READ_UPDATE

File read in update Info Information CC
mode
106 20805 STREAM_CREATEDAlternate Data Info Information CC

Stream Created
107 20806 STREAM_DELETEDAlternate Data Info Information CC

Stream Deleted
108 20807 STREAM_MODIFIED

Alternate Data Info Information CC
Stream Modified
109 20808 STREAM_ATTR Attribute Modified in Info Information CC

_MODIFIED Data Stream
110 20809 STREAM_CREATEDAlternate Data Info Information CC

_UPDATE Stream Created
111 20810 STREAM_DELETEDAlternate Data Info Information CC

_UPDATE Stream Deleted
112 20811 STREAM_MODIFIED

_UPDATE Stream Modified
113 20812 STREAM_ATTR Attribute Modified in Info Information CC

_MODIFIED_UPDATE
Data Stream

Threat event ID
114 20813 STREAM_ATTR_SETAttribute Added in Info Information CC

Data Stream
115 20814 STREAM_ATTR_CLEAR

Attribute Cleared in Info Information CC
Data Stream
116 20815 STREAM_ATTR Attribute Added in Info Information CC

_SET_UPDATE Data Stream
117 20816 STREAM_ATTR Attribute Cleared in Info Information CC

_CLEAR_UPDATE Data Stream
118 20817 STREAM_RENAMED

Stream Renamed
119 20818 STREAM_RENAMED

_UPDATE Stream Renamed
120 20819 BEGIN_OBSERVE Start Observe Mode Info Information AC
121 20820 BEGIN_OBSERVE Start Observe Mode Info Information AC

_DEFERRED On Reboot
122 20821 END_OBSERVE End Observe Mode Info Information AC
123 20822 END_OBSERVE End Observe Mode Info Information AC

_DEFERRED On Reboot
124 20823 INITIAL_SCAN Initial Scan Info Information AC

_TASK_COMPLETED
Completed
125 20824 BOOTING_OBSERVE

Booted in Observe Info Information AC
Mode
126 20825 ACTX_ALLOW_INSTALL

ActiveX installation Info Information AC
Allowed
127 20826 ACTX_INSTALL ActiveX installation Major Error AC

_PREVENTED Prevented
129 20828 VASR_VIOLATION VASR Violation Critical Critical AC

_DETECTED Detected
131 20830 THROTTLING_STARTED

Data Throttled Major Warning SC
132 20831 THROTTLING_CACHE

Data Dropped Major Error SC
_FULL
Not applicable 20950 THREAT_DETECTEDMalicious File Found - Based on CC, AC

(server-side (1) reputation.(2)
event)
Not applicable 20951 ASSUMED_THREATMalicious File is - Based on CC, AC

(server-side _NOT_PRESENT * Trusted reputation.‡
event)

Threat event ID
Not applicable 20952 OBSERVATION_THRESHOLD

Observation - Warning CC, AC
(server-side _EXCEEDED * Threshold Exceeded
event)
Not applicable 20953 OBSERVATION_REQUEST

Observation Request - Warning CC, AC
(server-side _THRESHOLD_EXCEEDED
Threshold Exceeded
event) *
Not applicable 20954 DATA_CONGESTION_DETECTED

Data Congestion - Warning CC, AC
(server-side Detected
event)
Not applicable 20955 CLOGGED_DATA_DELETED

Clogged Data - Warning CC, AC
(server-side Deleted
event)
133 20832 LOCAL_CLI_ACCESS_DISABLED

Disabled Local CLI Major Error CC, AC
Access
134 20833 LOCAL_CLI_RECOVER_SUCCESS

Recovered Local CLI Info Information CC, AC
135 20834 LOCAL_CLI_RECOVER_FAILED

Unable to Recover Info Information CC, AC
Local CLI
136 20835 OBSERVED_FILE_EXECUTION

Observed File Info Information AC
Execution
137 20836 PREVENTED_FILE_EXECUTION

Prevented File Major Error AC
Execution
138 20837 INVENTORY_RECOVERED

Recovered Inventory Critical Error AC
139 20838 INVENTORY_RECOVER_FAILED

Unable to Recover Critical Error AC
Inventory
140 20839 BLOCKED_PROCESS_INTERACTIVE_MODE

Blocked Interactive Critical Error AC
Mode of Process
1 This event is displayed only on the Threat Event Log page.

2 The McAfee ePO severity for this event is based on reputation value. If the reputation value is Known Malicious, Most Likely
Malicious, or Might be Malicious, the severity value is Alert, Critical, or Error, respectively. If the reputation value is Unknown, the
severity value is Warning. Also, if the reputation value is Might be Trusted, Most Likely Trusted, or Known Trusted, the severity
value is Warning, Notice, or Information, respectively.
List of events in standalone mode

Application Control specific events with the name, event ID, severity, and the description are described in this table.
Event names with a suffix (_UPDATE) indicate that events are generated in Update mode.

Event ID
(on Threat event ID (on McAfee
systems) ePO) Event name Severity Description
19 20718 PROCESS_TERMINATED Major McAfee Solidifier prevented an

attempt to hijack the process
<string> (Process Id: <string>, User:
<string>), by illegally calling the API
'<string>'. The process was
terminated.
20 20719 WRITE_DENIED Major McAfee Solidifier prevented an

attempt to change file <string> by
process/script <string> (sha1:
<string> , md5: <string>, sha256:
<string> ) (Process Id: <string>,
User: <string>).
21 20720 EXECUTION_DENIED Major McAfee Solidifier prevented

unauthorized execution of
'<string>' (sha1: <string>, md5:
<string>, sha256: <string>, File
Type: <string>) by process <string>
(Process Id:<string> , User:
<string>) whose parent is process
<string> , deny_reason : <string>
(deny reason code: <string>)
reputation score: <string>.
29 20728 PROCESS_TERMINATED_UNAUTH_SYSCALL
Major McAfee Solidifier prevented
process <string>, run by <string>,
from making unauthorized syscall
%d (return address %d). The
process was terminated.
30 20729 PROCESS_TERMINATED_UNAUTH_API Major McAfee Solidifier prevented

process <string>, run by <string>,
from making unauthorized access
to API <string> (return address
<string>). The process was
terminated
49 20748 REG_VALUE_WRITE_DENIED Major McAfee Solidifier prevented an

attempt to change Registry key
'<string>' with value '<string>' by
process <string> (Process Id:
<string>, User: <string>).
50 20749 REG_KEY_WRITE_DENIED Major McAfee Solidifier prevented an

attempt to change Registry key
'<string>' by process <string>
(Process Id: <string>, User:
<string>)

Event ID
51 20750 REG_KEY_CREATED_UPDATE Info McAfee Solidifier detected creation

of registry key '<string>' by
program <string> (User: <string>,
Workflow Id: <string>).
52 20751 REG_KEY_DELETED_UPDATE Info McAfee Solidifier detected deletion

of registry key '<string>' by
54 20753 REG_VALUE_DELETED_UPDATE Info McAfee Solidifier detected deletion

of registry value '<string>' under
key '<string>' by program <string>
(User: <string>, Workflow Id:
<string>).
57 20756 OWNER_MODIFIED_UPDATE Info McAfee Solidifier detected

modification to OWNER of
'<string>' by program <string>
<string>).
61 20760 PROCESS_HIJACKED Major McAfee Solidifier detected an

attempt to exploit process <string>
(sha1: <string>, md5: <string>,
sha256: <string>) from address
<string>.
62 20761 INVENTORY_CORRUPT Critical McAfee Solidifier detected that its

internal inventory for the volume
<string> is corrupt.
75 20774 FILE_CREATED_UPDATE Info McAfee Solidifier detected creation

of '<string>' by program <string>
(User: <string>, Original User:
<string>, Workflow Id: <string>).
76 20775 FILE_DELETED_UPDATE Info McAfee Solidifier detected deletion

of '<string>' by program <string>
77 20776 FILE_MODIFIED_UPDATE Info McAfee Solidifier detected

modification of '<string>' by
Original User: <string>, Workflow
Id: <string>)
79 20778 FILE_RENAMED_UPDATE Info McAfee Solidifier detected

renaming of '<string>' to '<string>'
by program <string> (User:

Event ID
<string>, Original User: <string>,
80 20779 FILE_SOLIDIFIED Info <string>' was solidified which was

created by program <string>(User:
82 20781 FILE_UNSOLIDIFIED Info <string>' was unsolidified which

was deleted by program
<string>(User: <string>, Workflow
Id: <string>).
89 20788 READ_DENIED Major McAfee Solidifier prevented an

attempt to read file '<string>' by
process <string> (Process Id:
<string>, User: <string>).
96 20795 PKG_MODIFICATION_PREVENTED Critical McAfee Solidifier prevented

package modification by
'<string>'(sha1: <string>, md5:
<string>, sha256: <string>) by user:
'<string>'.
97 20796 PKG_MODIFICATION_ALLOWED_UPDATEInfo McAfee Solidifier allowed package

modification by <string>'(sha1:
<string>, md5: <string>, sha256:
<string>) by user: '<string>'.
(Workflow Id: <string>).
98 20797 PKG_MODIFICATION_PREVENTED_2 Critical McAfee Solidifier prevented

package modification by '<string>'
by user: '<string>'.
99 20798 NX_VIOLATION_DETECTED Critical McAfee Solidifier prevented an

'<string>' (Process Id: '<string>',
SHA1: <string>, MD5: <string>,
SHA256: <string>, User: '<string>'),
by executing code from an address
outside of code pages region.
Faulting address '<string>'. The
process was terminated.
101 20800 REG_VALUE_MODIFIED_UPDATE Info McAfeeSolidifier detected

modification to registry value
'<string>' of type '<string>' under
key '<string>' by program '<string>'
<string>), with data: <string>
103 20802 FILE_READ_UPDATE Info McAfee Solidifier detected read for

'<string>' by program <string>

Event ID
<string>, Workflow Id: <string>)
124 20823 INITIAL_SCAN_TASK_COMPLETED Info McAfee Solidifier Initial Scan task is

complete and Application Control
is enforced on the system now.
126 20825 ACTX_ALLOW_INSTALL Info McAfee Solidifier allowed

installation of ActiveX <string>
Workflow Id: <string> by user
<string>
127 20826 ACTX_INSTALL_PREVENTED Major McAfee Solidifier prevented

installation of ActiveX <string>
Workflow Id: <string> by user
<string>
129 20828 VASR_VIOLATION_DETECTED Critical McAfee Solidifier prevented an

'<string>' (Process Id: '<string>',
sha1: <string>, md5: <string>,
sha256: <string>, User: <string>'),
by executing code from non-
relocatable dll '<string>'. Faulting
address <string>. Target address
'<string>'.
133 20832 LOCAL_CLI_ACCESS_DISABLED Major Local CLI has been disabled due to
wrong password attempts and it
can be recovered after <string>
minutes.
134 20833 LOCAL_CLI_RECOVER_SUCCESS Info Local CLI successfully recovered.
135 20834 LOCAL_CLI_RECOVER_FAILED Info Failed to recover Local CLI.
136 20835 OBSERVED_FILE_EXECUTION Info McAfee Solidifier observed start of

'<string>'(Process Id: <string>,
sha256: <string>, User: <string>,
Workflow Id: <mode>: AUTO_2,
original_procname: <string> ,
parent_name = <string>) with
command-line: '<string>'.
137 20836 PREVENTED_FILE_EXECUTION Major McAfee Solidifier blocked start of

'<string>'(Process Id: <string>,
sha256: <string>, User: <string>,
original_procname: <string>,
parent_name = <string>) with
command-line: '<string>'.

Event ID
138 20837 INVENTORY_RECOVERED Critical McAfee Solidifier has detected that

the inventory for volume <string>
is corrupt. The backup dated
<string> is loaded.
139 20838 INVENTORY_RECOVER_FAILED Critical McAfee Solidifier has detected that

the inventory for volume <string>
is corrupt. The backup could not
be loaded. Review the system and
perform solidification to create
whitelist.
140 20839 BLOCKED_PROCESS_INTERACTIVE_MODE

Critical McAfee Solidifier blocked process
<string> in interactive mode.
(Process Id: <string>, sha1:
<string>, md5: <string>, sha256:
<string>, User: <string>,
original_procname: <string>,
parent_name = <string>).
Managing the inventory with McAfee ePO

You can review, fetch, and manage the software inventory for protected endpoints. The software inventory for an endpoint
contains information about the executable files and script files present on the endpoint. The information stored in the inventory
includes complete file name, file size, SHA-1, SHA-256, file reputation, file type, embedded application name, certificate details,
and version.
The software inventory for a managed endpoint is available on the McAfee ePO console and updated regularly based on changes
made to the endpoint.
You can review and manage the inventory for endpoints from the McAfee ePO console. If needed, you can also fetch inventory
for endpoints. You can perform multiple tasks, such as allow or ban executable files, review all occurrences of an executable file
in the enterprise, and compare the endpoint inventory with a gold system to view image deviation.
You can use the Pull Inventory client task to view the list of executable or inventory details from endpoints in the McAfee ePO
console. When you run the Pull Inventory client task, it performs the following actions in the background:
1. The client task is sent to the endpoint.

2. When an endpoint receives the task, it computes the inventory information in an XML file.
3. Inventory information is split into multiple chunks based on the size of the inventory. Each chunk is about 60–100 KB. For
example, if the inventory is 180 KB in size, the endpoint creates three XML files with sequence numbers 1, 2, and 3, and size 65
KB, 65 KB, and 50 KB respectively.
4. When an agent-server communication interval (ASCI) ends, the endpoint sends the event XML with inventory information to
the McAfee ePO server.
5. The event parser parses the XML file, the Application Control extension processes data, and stores data in the database. This
information is displayed over inventory UI and used for the Image Deviation feature from the ePO console.
How the inventory is updated

Inventory information available on the McAfee ePO console for endpoints is updated at regular intervals based on changes made
at the endpoints.
A change to an endpoint's inventory triggers inventory information to be pushed to the McAfee ePO server after the agent-server
communication interval. This keeps the inventory information about the McAfee ePO server updated with changes to inventory
at the endpoints. Also, this avoids the need to manually fetch inventory for an endpoint to get the updated inventory.

These changes on an endpoint cause corresponding changes to the inventory information about the McAfee ePO server.
• Addition of a file
• Change of an existing file
• Rename of a file
• Deletion of a file
• Solidification or unsolidification of a file
Configure inventory updates

Inventory information is updated at regular intervals based on changes made at the endpoints running Application Control. By
default, this configuration is enabled but you can edit this value.
Task
2. Select the Solidcore 8.x.x: General for the product.
3. In the Configuration (Client) category, click Duplicate for the McAfee Default policy.
4. Specify the policy name, then click OK.
5. Open the policy and click the Miscellaneous tab.
6. Edit the value for the Inventory Updates: Configuration field.
7. Save the policy and apply it to the relevant endpoints.
Configure settings for fetching the inventory

For most enterprises, the default settings configured for fetching the inventory suffice. But, if needed, you can change the default
settings.
Task
2. Select Solidcore 8.x.x: Application Control for the product and Application Control Options (Windows) for the category.
4. Click the Inventory tab.
5. Click Hide Windows OS files to include the Windows-specific files in the inventory.
By default, the Windows-specific files are excluded from the inventory. This prevents overwhelming the inventory with
legitimate Windows files in the <system drive>\Windows folder (that are signed by the Microsoft certificate) and files in the
<system drive>\Windows\winsxs folder.
6. Specify a value for the Pull Complete Inventory Interval field. This value indicates the minimum interval (in number of days) between
consecutive inventory runs. By default, this value is set to seven days.
Note: This value takes precedence over any scheduled tasks to fetch inventory.
7. Specify a value for the Receive Inventory Updates Interval field.
This value indicates the minimum lag (in number of hours) between the generation of consecutive inventory updates. By
default, this value is set to three hours.
Save the policy and apply it to the relevant endpoints.
Fetch the inventory

Although Application Control maintains the current inventory for managed endpoints, you can fetch the inventory for one or
more managed endpoints, as needed.
Task
2. Perform one of these actions.
◦ To apply a client task to a group, select a group in the System Tree and click the Assigned Client Tasks tab.
◦ To apply a client task to an endpoint, select the endpoint on the Systems page, then click Actions → Agent → Modify Tasks on a Single
System.

4. Select Solidcore 8.x.x for the product and SC: Pull Inventory for the task type, then click Create New Task to open the Client Task Catalog
page.
Specify the task name and add any descriptive information.
5. Click Save, then click Next to open the Schedule page.
6. Specify schedule details, then click Next.
8. (Optional) Wake up the agent to send your client task to endpoints immediately.
Export SHA-1s
You can use the Offline McAfee GTI tool to fetch ratings for isolated McAfee ePO environments with no access to the Internet.
You can export SHA-1s of executable files and public key SHA-1s of certificates in the Application Control inventory to a file. The
created file is compressed and encrypted.
Task
1. On the McAfee ePO console, select Menu → Application Control → Inventory.
2. On the By Applications tab, select Actions → Export Inventory for Offline GTI Tool to create the inventory file.
The file name is appended with the date and time when the file is created. Here is the syntax of the file name.
App-Control-Inventory-<year>-<month>-<day>_<hour>-<minute>-<second>.zip
3. Save the inventory file.
Application Control and Change Control support SHA-256 values of executable files. But, reputation-based execution
workflows don't work on SHA-256 values because reputation sources, such as McAfee GTI and TIE server don't support file
SHA-256 values. So, only SHA-1 values of executable files and certificates are exported in the inventory file.
4. Copy the inventory file to a system with access to the Internet.
Run the Offline GTI tool

You can use the Offline McAfee GTI tool to fetch ratings for files and certificates with no access to the Internet.
Before you begin

• Make sure that Java Runtime Environment (JRE) 1.6.0_33 or later is installed on the system.
• Verify that the system is connected to the Internet.
• Make sure that you have downloaded and saved the OfflineGTITool.zip file from the McAfee download site.
For all file SHA-1s, File Hash Reputation and File Hash Classification values are fetched from the McAfee GTI file reputation
service. Similarly, for public key SHA-1s of certificates, corresponding reputation values are fetched from the McAfee GTI server.
The Offline GTI tool fetches the McAfee GTI ratings and saves the information to a result file.
Note: McAfee GTI file reputation service and the server don't support SHA-256 files and public key SHA-256 certificates.
Task
1. Set the GTI_TOOL_JAVA_HOME environment variable.
a. Open a command window.
b. Type this command and provide the path to the JRE.
set GTI_TOOL_JAVA_HOME=<JRE path>
For example:
set GTI_TOOL_JAVA_HOME=C:\Program Files\Java\jre6
2. Run the Offline GTI tool.
a. Extract the OfflineGTITool.zip file to a system with access to the Internet.
The OfflineGTITool directory is created. This directory contains the readme.txt file that explains the prerequisites,
procedure, configuration, and logging details. For detailed information about using the Offline GTI tool, we recommend
that you read this file.
b. Change to the OfflineGTITool directory.
cd <directory path>
Make sure that you specify the absolute path to the OfflineGTITool directory.
c. Verify that the current directory is OfflineGTITool.
cd

d. Run the tool.
runOfflineGTITool.cmd <Inventory file path>
Specify the tool name followed by the path to the inventory file that you saved on this system.
For example:
runOfflineGTITool.cmd c:\inventory\App-Control-Inventory-yyyy-MM-dd_HH-mm-SS.zip
The Offline GTI tool connects to the McAfee GTI server and fetches McAfee GTI ratings for the file SHA-1s and certificate public
key SHA-1s. When ratings for all SHA-1s and public key SHA-1s are fetched, a success or failure message is displayed at the
command prompt. The created GTI result file contains the McAfee GTI ratings and its contents are encrypted. The file name is
appended with the date and time when the file is created.
GTI-Result-<year>-<month>-<day>_<hour>-<minute>-<second>.zip
3. Copy the GTI result file to a system connected to the McAfee ePO server.
Import the GTI result file

You can import the GTI result file to a system connected to the McAfee ePO server to update the Application Control inventory
with the fetched McAfee GTI ratings.
Important: After the GTI result file is successfully generated, you must import the McAfee GTI ratings to McAfee ePO in seven
days. If you exceed seven days, you can't update the Application Control inventory with the McAfee GTI ratings. Although the
default setting is seven days, you can configure it, as needed. To configure this setting, contact McAfee Support.
Task
2. On the By Applications tab, select Actions → Import GTI ratings to open the Import GTI ratings dialog box.
3. Click Browse to select the GTI result file, then click OK.
4. Click OK.
5. Verify the import:
a. Select Menu → Automation → Server Task Log.
b. Specify the task name Imports GTI ratings from file to Inventory in the Quick find text box, then click Apply.
c. Check that the status of this server task is Completed.
Set enterprise reputation for files and certificates

You can change the enterprise reputation for files and certificates on the TIE server to suit your environment. But, changing the
enterprise reputation has a global impact on your environment. When you change the enterprise reputation for a file or a
certificate, the information is immediately updated in the database and sent to devices in your environment that are listening to
TIE change notifications, such as endpoints running Application Control or other clients.
Task
1. On the McAfee ePO console, select Menu → Systems → TIE Reputations.
2. Click the File Search or Certificate Search tab.
3. Search for files or certificates, then use the Actions menu to set enterprise reputation.
Review the inventory

You can manage and take actions on the software inventory for an endpoint.
Task
2. Define how to manage the inventory:
◦ For all managed endpoints, click the By Applications tab.
◦ For a selected endpoint, click the By Systems tab and click View for the relevant endpoint. The inventory for the selected
endpoint is listed.

3. Review the applications in the inventory. By default, based on the information received from the configured reputation source,
the applications are sorted into Trusted Applications, Malicious Applications, and Unknown Applications categories. The executable files are
assigned one of these reputation values.
◦ Known Trusted
◦ Most Likely Trusted
◦ Might be Trusted
◦ Unknown
◦ Might be Malicious
◦ Most Likely Malicious
◦ Known Malicious
4. Review application details (only when you review all files sorted by applications).
a. Click Inventory Actions → Application Details to open the Application Details page.
b. View the details for the application.
c. In the Executable Files pane, review the files associated with the selected application.
d. In the Systems pane, review the endpoints where the selected application is present.
e. (Optional) Perform any action on the listed endpoints.
f. Click Close.
5. Click Allow or Ban to allow or block the file on an endpoint.
Manage the inventory

Application Control sorts your inventory items based on reputation received from the configured reputation source.
Before you begin

To review and manage inventory items for all systems in your setup, you must be a McAfee ePO administrator. If you are a non-
global administrator, you can only review and manage inventory items for systems for which you have the required permissions.
If you need permissions to manage enterprise-wide inventory items, contact the McAfee ePO administrator.
Task
1. Define how to manage the inventory:
◦ For all managed endpoints, navigate to Menu → Application Control → Inventory → By Applications.
◦ For a selected endpoint, navigate to Menu → Application Control → Inventory → By Systems and click View for the relevant endpoint.
2. Prevent malicious executable files or script files from running.
a. Select the files to block.
b. Select Actions → Ban Files to open the Allow or Ban Files wizard.
c. Specify the rule group for the rules.
◦ To add the rules to an existing rule group, select Add to Existing Rule Group, select the rule group from the list, and specify the
operating system.
◦ To create a rule group with the rules, select Create a New Rule Group, enter the rule group name, and specify the operating
system.
Note: You can define rules to allow or ban a file based on both SHA-1 and SHA-256 values of the file.
d. Click Next.
e. Review the rules, then click Save.
3. Allow trusted executable files or script files to run.
a. Select the files to allow.
b. Select Actions → Allow Files to open the Allow or Ban Files wizard.
c. Perform one of these actions.
◦ To allow the file only on the selected endpoint, add the file to the whitelist of the endpoint by selecting Add Files to Whitelist.
◦ To allow the file on multiple endpoints, and to add the rules to a rule group, Select Add to Existing Rule Group or Create a New
Rule Group.
d. Click Next.
e. Review the rules, then click Save.

4. Recategorize an unknown executable file or script file as a trusted file by editing the reputation by Application Control for the
file.
a. Select the files.
b. Select Actions → Set Reputation by Application Control to open Set Reputation by Application Control.
c. Select the reputation value.
5. Add the updated rule group to the policies applied to the endpoints.
Define filters for inventory data

Specify advanced exclusion filters to exclude non-meaningful inventory data from the endpoints.
Task
2. Select the Filters tab and expand Inventory.
3. Click Add Rule.
A new filter row appears. You can create filters based on file, file type, application, application version, application vendor, and
file signed by certificate (Microsoft certificate only).
Note: When you create a filter to exclude inventory items based on the application name, version, or vendor, the filter works
on the embedded values associated with the application.
4. Edit the settings to specify the filter.
5. Click + or Add Rule to specify more AND or OR conditions, respectively.
6. Click Save.
Create an approved repository of known applications

You can set the base image for your enterprise to create an approved repository of known applications.
If the inventory for an endpoint in your setup includes known and trusted applications, you can set it as a base image for your
enterprise. This creates an approved repository of known applications, including internally developed, recognized, or trusted
(from a reputed vendor) applications. Also, this makes management of desktop systems easier by verifying the corporate
applications.
Task
1. On the McAfee ePO console, select Menu → Application Control → Inventory → By Systems to display the endpoints in your setup.
2. Navigate to the endpoint where the known and trusted applications exist.
3. Select Mark Trusted for the endpoint.
This recategorizes all unknown executables (binaries, libraries, and drivers) and scripts on the endpoint as trusted files and
edits the enterprise trust level for the files. No changes are made to the malicious executable file or script files on the
endpoint.
Compare the inventory

Image deviation is used to compare the inventory of an endpoint with the inventory that is fetched from a designated gold
system. This helps you to track the inventory present on an endpoint and identify any differences that occur.
Task
1. Fetch the inventory for your gold host.
2. Fetch the inventory for the endpoint.
3. Review the Menu → Automation → Solidcore Client Task Log page to make sure that both client tasks completed successfully.
4. Compare the inventory of gold host with the inventory of the endpoint. This is known as Image Deviation.
5. Review the comparison results.
Run the inventory comparison

Compare the inventory of the gold host with the inventory of an endpoint.
Task
1. On the McAfee ePO console, select Menu → Automation → Server Tasks.

2. Click Actions → New Task to open the Server Task Builder wizard.
a. Type the task name, then click Next.
b. Select Solidcore: Run Image Deviation from the Actions drop-down list.
c. Specify the gold system.
d. Configure these options to select the endpoint to compare with the gold system.
◦ Systems to compare with Gold System — Click Add to search for the endpoint that you want to compare with the gold system. Type
the name of the endpoint in the System Name field and click Search.
◦ Groups to compare with Gold System — Click Add to search for the group that you want to compare with the gold system. Type the
name of the group in the Group Name field and click Search.
◦ Include Systems with Tags — Click Add to search for endpoints based on their tag names. Type the tag name in the Tag Name field
and click Search.
◦ Exclude Systems with Tags — Click Add to search for endpoints based on their tag names. Type the tag name in the Tag Name field
and click Search. Select the required tag from the search result. All endpoints with the selected tags are excluded from
comparison with the gold system.
4. Specify the schedule for the task.
5. Click Next to open the Summary page.
6. Review the task summary, then click Save.
7. Run the server task immediately to instantly review the comparison results.
Review results of inventory comparison

You can review the results of inventory comparison (image deviation).
Task
1. On the McAfee ePO console, select Menu → Application Control → Image Deviation.
2. Locate the comparison of the gold host and endpoint.
To quickly find the corresponding row, enter the endpoint name in the Search Target System field, then click Search.
3. Click Show Deviations.
4. Review the comparison details.
◦ Select the view type. You can organize the results based on applications or executable files.
◦ Use the available filters to sort the results. Using the filters, you can view new (added), changed, and removed (missing) files.
Use the Execution Status Mismatch filter to view files with changes to the execution status. Use the path filter to sort the results
based on the file path.
Using dashboards and queries

Dashboards
Dashboards are collections of monitors that help you keep an eye on your environment.
Application Control provides these default dashboards:
• Solidcore: Inventory allows you to observe the inventory for the endpoints.
• Solidcore: Application Control helps you keep a check on the protected endpoints.
• Solidcore: Health Monitoring helps you monitor the health of the protected endpoints in your enterprise.
Queries
Use the available queries to review information for the endpoints based on the data stored in the McAfee ePO database.
These Application Control and Health Monitoring queries are available from the McAfee ePO console.
Application Control queries
Query Description
Alerts Displays all alerts generated in the last 3 months.

Query Description
Application Control Agent Status Displays the status of all endpoints with the Application
Control license which are managed by the McAfee ePO server.
The pie chart categorizes the information based on the client
status. Click a segment to review endpoint information.
Attempted Violations in the Last 24 Hours Displays the attempted violation events detected during the
last 24 hours. The line chart plots data on a per hour basis.
Click a value on the chart to review event details.
Attempted Violations in the Last 7 Days Displays the attempted violation events detected during the
last 7 days. The line chart plots data on a per day basis. Click a
value on the chart to review event details.
Non Compliant Solidcore Agents Lists the endpoints that are currently not compliant. The list is
sorted based on the reason for noncompliance. An endpoint
can be noncompliant if:
• It is in Disabled, Observe, or Update mode.
• It is operating in limited feature activation mode.
• The local command line interface (CLI) access is recovered.
Policy Assignments By System Lists the number of policies applied on the managed
endpoints. Click a system to review information about the
applied policies.
Policy Discovery Requests for Automatically-Approved Installations Lists all files that were identified as installers on the
endpoints and executed automatically with installer rights in
the last 1 month.
Self-Approval Audit Report Displays a list of all approval requests that are received from
the endpoints in the last month.
Solidcore Agent License Report Indicates the number of Solidcore Agents that are managed
by the McAfee ePO server. The information is categorized by
the license information and further sorted by the operating
system on the endpoint.
Solidcore Agent Status Report Displays the status of all endpoints managed by the McAfee
ePO server. This report combines information for both the
Application Control and Change Control licenses. The pie
chart categorizes the information based on the client status.
Click a segment to review detailed information.
Summary Server Reboot Log - Rolling 30 Days Displays the reboot log grouped by system name.
Systems for which Inventory Cannot be Fetched Currently List the systems in your enterprise for which inventory
information can't be fetched currently. You can't fetch
inventory for a system if the specified interval between
consecutive inventory runs hasn't been reached. This interval
value is configurable.
Systems for which Inventory Information has not been Fetched for in Last 1 Lists the systems in your enterprise for which inventory
Month hasn't been fetched in the last month. We recommend that
you fetch inventory weekly.

Query Description
Top 10 Application Vendors Displays the top 10 application vendors in the enterprise with
the maximum number of applications. The chart includes a
bar for each vendor and lists the applications for each
vendor. The bar chart sorts the data in descending order.
Click a section on a bar on the chart to review detailed
information for the associated application.
Top 10 Systems with Most Violations in the Last 24 Hours Displays the top 10 systems with the maximum number of
violations in the last 24 hours. The chart includes a bar for
each system and indicates the number of violations for each
system. Click a bar on the chart to review detailed
information.
Top 10 Systems with Most Violations in the Last 7 Days Displays the top 10 systems with the maximum number of
violations in the last 7 days. The chart includes a bar for each
system and indicates the number of violations for each
system. Click a bar on the chart to review detailed
information.
Top 10 Users with Most Violations in the Last 7 Days Displays the top 10 users with the most policy violation
attempts in the last 7 days. The chart includes a bar for each
user and indicates the number of policy violation attempts for
each user. The bar chart sorts the data in descending order.
Click a bar on the chart to review detailed information.
Top 10 Users with Most Violations in the Last 24 Hours Displays the top 10 users with the most policy violation
attempts in the last 24 hours. The chart includes a bar for
each user and indicates the number of policy violation
attempts for each user. The bar chart sorts the data in
descending order. Click a bar on the chart to review detailed
information.
Health Monitoring queries
Query Description
Client Task Logs Data Congestion Trend in Last 7 Days Displays the data congestion trend for client task logs on the
last 7 days. The line chart plots data on a per day basis. Click a
value on the chart to review details.
Inventory Data Congestion Trend in Last 7 Days Displays the data congestion trend for inventory in the last 7
days. The line chart plots data on a per day basis. Click a value
on the chart to review details.
Number of Systems where Throttling Initiated in Last 7 days Displays the number of systems where Events, Inventory
Updates, or Policy Discovery (Observations) throttling is
initiated in last 7 days. The summary table sorts the data in
descending order.
Observations Data Congestion Trend in Last 7 Days Displays the data congestion trend for observations in the last
7 days. The line chart plots data on a per day basis. Click a
value on the chart to review details.

Query Description
Self-Approval Data Congestion Trend in Last 7 Days Displays the data congestion trend for self-approval requests
in the last 7 days. The line chart plots data on a per day basis.
Click a value on the chart to review details.
Systems with Most Pending Requests Generated in Observe Mode Displays systems running in Observe mode with pending
Policy Discovery requests. The summary table sorts the data
in descending order.
Top 10 Events for 10 Most Noisy Systems in Last 7 days Displays the top 10 events for the most noisy systems in last 7
days. The bar chart sorts the data in descending order. Click a
bar on the chart to review detailed information.
View queries
View an Application Control or Solidcore Health Monitoring query.
Task
1. On the McAfee ePO console, select Menu → Reporting → Queries & Reports.
2. Select the Application Control or Solidcore Health Monitoring group under McAfee Groups.
3. Review the queries in the list.
4. Navigate to the required query and click Run.
The results for the selected query are displayed.
5. Click Close to return to the previous page.
Using trusted users

What are trusted users?
A trusted user is an authorized user with updater permissions to dynamically add to the whitelist.
You can add users as updaters to allow users to perform update operations on a protected system. If you provide updater
permissions to a user, the user is defined as a trusted user. For example, add administrators as trusted users to allow them to
install or update any software. While adding the user information, you can also provide the domain details.
Note: Of all strategies that allow changes to protected systems, this is the least preferred one because it offers minimal security.
After a trusted user is added, there are no restrictions on what the user can change or run on the system.
Add trusted users in a managed environment

A trusted user is an authorized user with rights to change the whitelist. A trusted user can override protection and perform
update operations on protected endpoints. For example, you can add administrators as trusted users to allow them to install or
update any software. You must add the user details and the domain details.
You can enter user details or import user or group details from an Active Directory.
Task
2. On the Users tab, click Add.
3. Create two rules for each user.
◦ With UPN/SAM and domain account name (in domainName\user format)
◦ With domain netbiosName (in netbiosName\user format)
4. Specify a unique identification label for the user.
For example, if you specify John Doe's Changes as the identification label for the John Doe user, all changes made by the user
are tagged with this label.
5. Type the user name.
6. Click OK.

Add trusted users in a standalone environment
Add trusted users to allow them to perform update operations on a protected system.
Task
sadmin updaters add –u <username>
This table lists the supported arguments, descriptions, and examples.
Argument Description
-u Specify the –u argument to add a user as a trusted user. All update operations by the specified user
name are allowed.
You can add these types of user names as trusted users.
• Simple name
For example john_smith.
sadmin updaters add –u john_smith
• Domain name
For example john_smith@mycompany.
sadmin updaters add –u john_smith@mycompany
• Hierarchical domain name (domain name\user name)
For example mydomain\john_smith.
sadmin updaters add –u mydomain\john_smith
Note: When you specify the –u argument, other arguments supported for sadmin updaters add
command, such as -l, -p, -d, and –n are not applicable.
-t Specify the –t argument to add a user with a tag name as an updater. Tag name is an identification
label which is present in the logs for all files processed by this rule.
sadmin updaters add –t <tagname> –u <username>
sadmin updaters add –t McAfee001 -u john_smith
List trusted users

You can view the list of all users who have updater permissions on the system.
Task
sadmin updaters list
This command lists all trusted users and other components defined as updaters in the system.
Remove trusted users

When you remove a trusted user, the updater permissions assigned to that user are removed.
Task
sadmin updaters remove -u <username>
For example, sadmin updaters remove -u john_smith
Note: After using this command, restart the system to remove updater permissions from the users.

Deploying Application Control in Observe mode
Observe mode indicates that Application Control is running but it only monitors and logs observations. When running in Observe
mode, the application doesn't prevent any execution or changes made to the endpoints. Instead, it monitors execution activities
and it compares them with the local inventory and predefined rules.
Important: Observe mode is available only in a McAfee ePO managed environment.
Observe mode also supports reputation-based execution. When you execute a file, Application Control fetches its reputation and
that of all certificates associated with the file to determine whether to allow or ban the file execution. When running in Observe
mode, Application Control emulates Enabled mode but only logs observations.
All files that are allowed to execute in Observe mode are automatically added to the whitelist, if not already present in the
whitelist. An observation event is logged that corresponds to the action Application Control takes in Enabled mode. For example,
if not authorized, the execution of Adobe Reader is prevented in Enabled mode. In Observe mode, the file is allowed to execute
unless banned by a specific rule or has malicious reputation.
Observe mode offers two benefits.
• It helps you develop policies and determine rules that allow applications to run in Enabled mode.
• It performs a dry run for the product to run or install software without any blockages.
What are observations?

Observations record execution, installation, and uninstallation activities for managed endpoints.
When Application Control is running in Observe mode, it allows most operations on the endpoints. In Observe mode, a file is
allowed to execute unless it is banned by a specific rule or has malicious reputation. All observations generated on an endpoint
are sent to the McAfee ePO server after agent-server communication intervals (ASCI). When an endpoint is in Observe mode, no
Application Control events are generated for the endpoint.
Observe mode also supports reputation-based execution. When you execute a file at an endpoint, the software fetches its
reputation and reputation of all certificates associated with the file to determine whether to allow or ban the file execution.
• Trusted files — If the reputation for an executable file or its associated certificate is trusted, the file is allowed to run, unless
blocked by a predefined ban rule. No corresponding observation or event is generated.
• Malicious files — If the reputation for an executable file or its associated certificate is malicious, the file isn't allowed to
execute and no corresponding observation is generated. A corresponding event is generated and displayed on the Solidcore
Events page. The settings configured for your enterprise determine the reputation value that is banned. You can choose to ban
only Known Malicious, Most Likely Malicious, Might be Malicious files, or all such files.
• Unknown — If the reputation for an executable file or its associated certificate is unknown, reputation isn't used to determine
execution. Application Control performs multiple other checks to determine whether to allow or block the file.
Note: Regardless of the file's reputation, if a ban by name, SHA-1, or SHA-256 rule exists for an executable file, its execution is
banned. No corresponding observation is generated. A corresponding event is generated and displayed on the Solidcore Events
page.
Observations are generated in both Enabled mode and Observe mode.
• For all processes without updater rights, these observations are generated in Enabled mode and Observe mode.
◦ Execution Denied
◦ File Write Denied
◦ ActiveX Installation Prevented
◦ Process Hijack Attempted
◦ Nx Violation Detected
◦ Installation Denied
• For a process that is assigned updater rights, observations are generated for these memory protection-related operations in
Enabled mode and Observe mode.
◦ Process Hijack Attempted
◦ Nx Violation Detected

Managing Observe mode
Deploying Application Control in Observe mode involves these high-level steps.
1. Identify the staging or test endpoints for deployment.

If you have multiple types of endpoints in your setup, group similar types of endpoints to roll out Observe mode. This allows
you to analyze product impact on each group of endpoints, discover policy groups, and validate the policies that apply to each
group of endpoints.
2. Place Application Control in Observe mode for a few days and perform day-to-day tasks on the endpoints.
If a reputation source is available and configured, you can review the reputation of files and certificates in your enterprise.
This helps you make informed decisions for the received requests. The settings configured for your enterprise determine the
reputation values that are allowed and banned.
Requests are created based on observations generated for the endpoints. These requests allow you to discover Application
Control policy rules for the software installed on the endpoints.
3. Periodically review and create rules for the received requests.
4. Validate the recently added policies by running frequently used workflows. This helps you verify if more requests are received
for the applications.
5. When the number of requests received reduces considerably, exit Observe mode and place the endpoints in Enabled mode.
Configure processes and certificates

On the McAfee ePO console, you can configure updaters by editing the list of generic launcher processes and restricted
certificate names.
You can configure these settings:
• Generic launcher processes — Certain processes on the Windows operating system, such as explorer.exe and iexplore.exe,
start other processes and can be used to start any software. Such processes are referred to as generic launcher processes and
must never be configured as updaters. A predefined list of such processes is available on the Application Control configuration
interface. You can review and edit the list of generic launcher processes. No updater rules are generated for generic launcher
processes at the endpoints.
• Restricted certificate names — Certificates from certain vendors such as Microsoft are associated with multiple commonly
used applications. They should not be used to define rules based on the certificate. A predefined list of such certificates is
available on the Application Control configuration interface. You can review and edit the list of restricted certificate names. If
the file in a request is signed by one of these certificates, you can't create rules based on the certificate associated with the file.
Task
1. On the McAfee ePO console, select Menu → Configuration → Server Settings → Solidcore.
2. Review and edit the list of generic launcher processes.
a. Review the processes listed in the Generic launcher processes field.
c. Add the process name to the end of this list (separated by a comma), then click Save.
3. Review and edit the list of restricted certificates.
a. Review the names listed in the Restricted certificate names field.
c. Add the vendor name to the end of this list (separated by a comma), then click Save.
For example, to prevent creation of rules based on the Microsoft certificate, add Microsoft to the list. Use the value listed
in the ISSUED TO field of the certificate.
Place endpoints in Observe mode

After installation, we recommend placing selected endpoints in Observe mode to perform a test run for the Application Control
product.
Select at least one endpoint for each type you have in your environment. Use one of these client tasks to place the endpoints in
Observe mode.
• SC: Enable — Use this client task to place the endpoints in Observe mode after fresh installation of Application Control.

• SC: Observe Mode — Use this client task to place the existing endpoints (running in Enabled mode) in Observe mode.
Task
◦ Group — Select the group in the System Tree and click the Assigned Client Tasks tab.
◦ Endpoint — Select the endpoint on the Systems page and click Actions → Agent → Modify Tasks on a Single System.
4. Select Solidcore 8.x.x → SC: Enable, then click Create New Task to open the Client Task Catalog page.
a. Specify the task name and add any descriptive information.
b. Select Windows for the platform, All except NT/2000 for the subplatform, then select Application Control.
c. Specify the scan priority.
The set scan priority determines the priority of the thread that is run to create the whitelist on the endpoints. We
recommend setting the scan priority to Low. This makes sure that Application Control causes minimal performance impact
on the endpoints but might take longer (than when you set the priority to High) to create the whitelist.
d. Specify the activation option.
◦ Limited Feature Activation — Endpoints are not restarted, whitelist created, and limited features of Application Control
are activated. Memory protection and Script As Updater (SAU) features are available only after the endpoint is restarted.
◦ Full Feature Activation — Endpoints are restarted, whitelist created, and all features of Application Control including
memory protection are active. Restarting the endpoints is needed to enable the memory protection features. The
endpoint is restarted 5 minutes after the client task is received at the endpoint. A pop-up message is displayed on the
endpoint before the endpoint is restarted.
e. Select Start Observe Mode.
f. (Optional) Select Pull Inventory.
If you select this option, the inventory (including the created whitelist) is sent to McAfee ePO. Select this option because
inventory information is used in multiple workflows available from McAfee ePO.
g. Click Save.
Policy discovery permissions

By default, non-global administrators can view, manage, and delete requests generated only by endpoints in their associated
group (in My Organization).
If you review request details about the Request Details page, the number of requests listed in the Enterprise Level Activity pane might be
less than the value displayed in the Global Prevalence column on the Policy Discovery page. This is because the Global Prevalence column
indicates the enterprise-wide prevalence for the requests regardless of any groups. For example, if a request is generated by two
systems in different groups across the enterprise, the value in the Global Prevalence is 2. But, because non-global administrators
can only view the requests generated for their group, the non-global administrator might see only one request generated by the
system in their group in the Enterprise Level Activity pane.
Note: The McAfee ePO administrator can review and manage all requests generated in the enterprise (My Organization). Also,
McAfee ePO administrator can add rules to any rule group, and provide permissions to all non-global administrators to review
and take custom actions on the requests generated in the enterprise.
If you are a non-global administrator, you can add rules (for a request) to only the rule groups that you own. Rule groups that
you don't own are not displayed on the Policy Discovery: Custom Rules page. Also, if you take an action for a request, the action
doesn't impact the same request generated by the system in a different group.
Allow non-global administrators to manage enterprise-wide requests

If you are a McAfee ePO administrator, you can assign permissions to all non-global administrators (who have access to groups
in My Organization) to review and manage requests generated in your enterprise.

Task
1. On the McAfee ePO console, select Menu → Configuration → Server Settings.
2. From the Setting Categories pane, select Solidcore, then click Edit to open the Edit Solidcore page.
3. Change the value of Allow group administrators to manage Policy Discovery requests for entire System Tree to Yes (overrides System Tree group access
permissions).
4. Click Save.
Results
All non-global administrators are allowed to review and take custom actions on enterprise-wide requests. Non-global
administrators can't perform global actions.
Managing requests
Review requests
You can review the requests received from endpoints.
Task
1. On the McAfee ePO console, select Menu → Application Control → Policy Discovery to open the Policy Discovery page.
2. Review the listed requests using one of these methods.
◦ Specific interval — Select an option from the Time Filter list, then click Update Results to view requests received during a specific
interval.
◦ Request status — Select a value for the request status from the Approval Status list, then click Update Results to view requests
that match the selected status.
◦ Activity — Click Additional filters and select a value from the Activity list. Click Update Results to view requests for a certain activity.
◦ Reputation — Click Additional filters and select a value from the Final Reputation list. Click Update Results to view requests for files
that match the selected reputation value. For more information about how the software determines final reputation for files
or certificates, click What's Final Reputation.
◦ Specific endpoint — Click Additional filters and enter an endpoint name in the System Name field. Click Update Results to view
requests received from the endpoint. Make sure that you specify the complete system name because no partial matches are
performed.
◦ Multiple criteria — Specify values for the Time Filter, Approval Status, Activity, Final Reputation, and System Name fields, as needed,
then click Update Results to perform a search based on the specified criteria.
◦ Specific search string — Enter a search string in the Quick find field for Object Name, Application Name, Certificates, and User Comments,
then click Apply to view requests that match the specified search string. Partial matches are performed based on the text you
specify.
◦ Sort — Sort the list based on the global prevalence, final reputation, reputation source, execution time, activity, object
name, application name, certificate, or user comments by clicking the column heading.
◦ Selected requests — Select requests of interest, then click Show selected rows to review only the selected requests.
Note: The Policy Discovery page lists only the requests for which the McAfee ePO administrator can make rules. To view other
requests, such as those for installers with trusted reputation, run the Policy Discovery Requests for Automatically-Approved Installations
query. The query lists all files with trusted reputation that were executed automatically on the endpoints with installer
permission in the last one month.
3. (Optional) Add user comments for one or multiple events:
◦ One event – click Add a comment.
◦ Multiple events – select the requests and click Actions → Add Comments, then enter your comments and click OK.
4. Review individual requests that make up a collated request and detailed information for the file.
a. Click a row to open the Request Details page.
b. Review file details, such as name, version, path, parent process, files changed, final reputation, and user comments, if any.
c. Review the SHA-1, SHA-256, and MD5 information for the file.
d. Click the file SHA-1 value to review file details about the File Details page.
e. Review the certificate vendor name for the file. The certificate vendor name for a file is color coded to indicate trusted
(green), malicious (red), or unknown (orange) reputation.
f. Click certificate name to view certificate details, such as issuer, certificate reputation, reputation source, public key
algorithm, public key length, public key hash, certificate hash, valid from, and valid to.

g. Review the individual requests that make up the collated request in the Enterprise Level Activity pane.
h. Click Close.
Allow a file on all endpoints

You can define rules to allow an application or executable file to run on all endpoints in the enterprise.
Task
2. Select the requests where you want to define rules.
3. Click Actions → Allow File Globally.
The Allow File Globally dialog box provides details and prompts you to confirm the action.
4. Click OK.
Results
Rules are created for the files associated with the selected requests and added to the Global Rules rule group included in the
McAfee Default policy.
Allow a file by certificate

You can define rules to allow an application, executable file, or ActiveX control to run on all endpoints in the enterprise based on
the certificate associated with the file.
Task
2. Select the request where you want to define rules.
3. Click Actions → Allow by Certificate Globally.
4. The Allow by Certificate Globally dialog box provides details and prompts you to confirm the action. Based on the file associated
with a selected request, the certificate is assigned or not assigned updater privileges. If the certificate has updater privileges,
allowing based on certificate allows all applications signed by the certificate to make changes to existing executable files or
start new applications on the endpoints.
5. Click OK.
The Allow by Certificate Globally action is unavailable if the main executable associated with the request is signed by a certificate
included in the Restricted certificate names list.
Allow network files on all endpoints

You can define rules to allow a network file (file placed on a network path) to run on all endpoints in the enterprise.
Task
3. Click Actions → Allow Trusted Path Globally.
The Allow Trusted Path Globally dialog box provides details and prompts you to confirm the action. Based on the network path
associated with a selected request, suggested alternate paths (sorted based on path length) and corresponding number of
matching requests that are pending for each suggested path are displayed.
Caution: When you allow the path, updater rights are provided to all software present in that network path and its
subdirectories. Use caution and carefully add the trusted path.
When a request from a network path is approved globally, no further requests for the approved network path and its
subdirectories are received at McAfee ePO.
4. Click OK.
Results
Rules to allow the specified network path (with updater rights to all software present in that network path and its subdirectories)
are added to the Global Rules rule group included in the McAfee Default policy.

Ban by SHA-1 or SHA-256 on all endpoints
You can define rules to ban an application or executable file from running on all endpoints in the enterprise based on the SHA-1
or SHA-256 value of the file.
Task
3. Click Actions → Ban File Globally.
The Ban File Globally dialog box provides details and prompts you to confirm the action.
4. Click OK.
5. Ban the files that have already been added to the endpoint.
a. Click the application name link.
The Files page lists all executable files installed on the endpoint.
b. Select all listed files.
c. Click Actions → Ban Files to open the Allow or Ban Files wizard.
d. Specify the rule group for the rules.
operating system.
system.
e. Make sure that the rule group where you add the rules is added to a policy that is applied on the endpoint where the
request was received.
f. Click Next.
g. Review the rules, then click Save.
Define rules for specific endpoints

If you are a McAfee ePO administrator, you can add prepopulated rules to allow or ban an application, executable file, or ActiveX
control for specific endpoints in your administered groups. Or, you can define custom rules for specific endpoints or groups, as
needed.
Task
2. Select the request where you want to define custom rules.
3. Click Actions → Create Custom Policy to open the Policy Discovery: Custom Rules page.
4. You can review rules or define custom rules:
◦ Review or add rules — Select Approve Request, Ban Request, Allow By Certificate, Allow Trusted Path, or Bypass Memory Protection, then
review or add more rules as needed.
◦ Define custom rules — Select Clear and define Rules, then review the request details and define relevant rules as needed.
Note: When adding rules to allow a network path, select your rule group carefully. If you add rules to the Global Rules rule
group, all future requests received from that network path are automatically approved. Or, if you add your rules to a custom
rule group, future requests from that network path aren't automatically approved.
6. (Optional) Add the changed or created rule group to a policy.
7. Click Save.

This approves all grouped requests. For requests received from network paths, when you click Save, the Approve Requests for
Subdirectories pop-up window appears that includes a checkbox to approve all related requests. If needed, select the checkbox,
then click OK to approve all requests received from the network path and its subdirectories.
Allow by adding to whitelist for specific endpoints

You can add one or more executable files to the whitelist to allow the files to run on the endpoint.
Task
2. Click a row to review request details in the Request Details page.
Each row in the Enterprise level activity pane represents an executable file and endpoint combination.
3. Click Allow Locally for a row.
The Allow Locally dialog box lists one or more paths to add to the whitelist.
Note: The Allow Locally action is available only for requests that are generated when you execute an application that isn't in the
whitelist (Application Execution activity).
4. Review and customize the listed paths.
For example, if you execute proc.exe for an endpoint, these paths might be listed.
C:\Program Files\<App Name>\proc.exe
C:\Program Files\<App Name>\a.dll
C:\Program Files\<App Name>\b.dll
To avoid redundancy, add only the C:\Program Files\App Name path.
5. Click OK.
Results
The specified paths are added to the whitelist and allowed to run on the endpoint.
Define bypass rules for all endpoints

You can define rules to allow an application or executable file to bypass applied memory protection and other techniques.
Task
2. Select the request where you want to define bypass rules.
3. Click Actions → Bypass Memory Protection Globally.
4. When prompted to confirm, click OK.
Results
Rules are created for file associated with the selected request and added to the Global Rules rule group included in the McAfee Default
policy.

Task
Delete requests
You can remove requests from the Policy Discovery page and database.

Note: For optimal performance, the Solidcore: Auto Purge Policy Discovery Requests server task is run weekly to remove policy discovery
requests older than three months.
Task
2. Select the requests to delete.
3. Click Actions → Delete Requests.
Results
All selected collated requests and contained individual requests are deleted from the page and database.
Define filters for observations and events

You can specify advanced exclusion filters to exclude non-meaningful observations and events from the endpoints.
Task
2. Select the Filters tab and expand Observations & Events.
3. Click Add Rule to add a filter row.
You can create filters based on files, events, programs, registry keys, and users. By default, all defined filters are applied to
observations.
4. Edit the settings to specify the filter.
5. Click + or Add Rule to specify additional AND or OR conditions, respectively.
6. Select Apply rule to events also for a set of rules to apply the filter rules to events.
You can also define advanced exclusion filters from the Solidcore Events page.
Define filters for user comments

You can apply a filter on user comments to view the requests and identify which requests are to be processed. Only the requests
matching the specified filter criteria are displayed.
Task
1. On the McAfee ePO console, select Menu → Reporting → Queries & Reports, then click New Query to open the Query Builder page.
2. Select ePO → Solidcore → Policy Discovery Collated Requests, then click Next to open the Chart tab and the filters tab.
3. Select User Comments from the available properties and define the comparison and value.
4. Click Run to apply the filter.
Requests matching the specified criteria are displayed.
5. Click theActivity bar on the chart or click a row to open the Request Details page.
6. Click Back to return to the previous page or Click Save to save the query.
7. Click Save to save the query.
This query is saved to the Query Group.
Throttling observations
Frequently reviewing and managing requests for the generated observations allows you to define the relevant rules for your
setup. If you don't process observations in a timely manner, you continue to get similar and repeated observations from
endpoints.
Also, if you place additional endpoints in Observe mode or perform multiple activities simultaneously on existing endpoints (in
Observe mode), the absence of relevant rules might result in excessive generation of observations. If a high number of
observations are received at the McAfee ePO server from the endpoints, the McAfee ePO interface might become sluggish.
Observation throttling helps you take care of the non-responsiveness of the McAfee ePO interface. When the number of
observations received at the McAfee ePO server reaches the defined threshold, observation throttling is initiated. When
observation throttling starts, Application Control performs these actions:
• It stops further processing of observations at McAfee ePO to prevent non-responsiveness of the McAfee ePO interface.

• It applies the Throttling Rules policy to the My Organization group to prevent the generation of observations on all endpoints after
agent-server communication interval.
• It generates the Observation Request Threshold Exceeded event. This event is displayed on the Threat Event Log page and can be used to
create an automatic response.
• It displays a warning message on the Policy Discovery page stating that observation generation has stopped.
Define the threshold value for throttling

By default, Application Control can process 100,000 observations in 24 hours. You can configure this setting to define the
threshold value for your enterprise.
When the number of observations received at the McAfee ePO server in the last 24 hours reaches the defined threshold,
observation throttling is initiated.
Task
2. From the Setting Categories pane, select Solidcore.
3. Change the value of Threshold count at which to initiate throttling and suspend observation generation (6.1.1 and older endpoints) setting.
Review filter rules for throttling

To implement throttling, rules that filter and stop observations are added to the Stop Observation Requests rule group.
This rule group is read only and is assigned to the default read-only Throttling Rules policy. Initially, this policy isn't assigned to any
system or group. When the number of observations reaches the defined threshold, this policy is applied to My Organization (all
systems and groups in your organization).
Task
3. Click the Throttling Rules policy.
4. From the Rule Groups pane, select Stop Observation Requests.
5. Select the Filters tab.
6. Review the listed rules.
Restart observation generation for throttling

After you process existing requests and define rules for the accumulated requests, restart observation generation at endpoints.
Task
1. On the McAfee ePO console, select Menu → Application Control → Policy Discovery.
The Policy Discovery page displays a message stating that the observation generation has stopped.
2. In the warning message, click Enable Observation Generation.
Exit Observe mode

Once you are done monitoring the system and logging observations, you must exit Observe Mode.
Task
2. You can apply a client task to a group or an endpoint:
◦ Group — Select the group in the System Tree and switch to the Assigned Client Tasks tab.
◦ Endpoint — Select the endpoint on the Systems page and click Actions → Agent → Modify Tasks on a Single System.
4. Select Solidcore 8.x.x → SC: Observe Mode and click Create New Task to open the Client Task Catalog page.
b. Select End Observe Mode and choose to place the endpoints in Enabled or Disabled mode.

6. Specify scheduling details, click Next, then click Save.

Self-approval requests
What is self-approval?
Application Control prevents any new or unknown applications from running on protected endpoints. When the self-approval
feature is enabled and users try to run an unknown or new application on a protected endpoint, they are prompted to approve
or deny the application execution.
Important: Self-approval is available only in a McAfee ePO managed environment.
When a user approves the application execution, the business need or justification, if any, provided by the user for running the
application is sent to the McAfee ePO administrator. The administrator reviews the approval request and can define rules to
allow or ban the application for one or all endpoints in the enterprise.
The rules that are applied through policies have precedence over the self-approval feature. For example, if the self-approval
feature is enabled and the user tries to run an application that is banned through a policy, the user isn't prompted to take action.
Also, you can't self-approve and perform any actions that are prevented by Application Control memory-protection techniques.
The self-approval feature is available for binary or executable files, scripts, installers, ActiveX controls, and supported files that
you run from network shares and removable devices. This feature is available on all supported Windows platforms except
Windows NT, Windows 2000, and Windows 2003 (IA-64 platform).
Note: Although the self-approval feature is available in Limited Feature Activation mode, use this feature in Full Feature
Activation mode (after restarting the endpoints). This feature requires patching of some system libraries and patching might
require a restart to work effectively.
Enable self-approval on endpoints

By default, the self-approval feature is disabled on endpoints. You can configure a policy to enable this feature on selected
endpoints.
After the feature is enabled, users can approve an unknown or new application on a protected endpoint and run it.
Task
3. Select Application Control Options (Windows) for the category.
Note: By default, the My Default policy is applied to all endpoints in your enterprise. To enable the self-approval feature for
selected endpoints, duplicate the My Default policy, edit the settings, and apply the policy to only the relevant endpoints.
5. Select Enable Self-Approval.
6. (Optional) Specify the message to display to the users on the endpoints when they try to run a new or unknown application.
This specified text is displayed on the endpoint in the McAfee Application Control - Self-Approval dialog box.
7. Specify a timeout value for the user to take an action when the McAfee Application Control – Self-Approval dialog box is displayed.
If the user doesn’t take action in the specified time, the attempted action is automatically denied and the dialog box closes.
8. Specify whether it is mandatory or optional for the user to provide a business need while allowing an action on the endpoint.
9. (Optional) Specify the advanced options.
If you select this option, all applications that run on the system while it is booting or when an interactive session is unavailable
are allowed to execute.
10. Save the policy and apply to endpoints.
After the policy is applied, the self-approval feature is enabled on the endpoints.
Self-approval dialog box

When users try to run a new application on the endpoints, the McAfee Application Control - Self-Approval dialog box indicates that
execution of the application has been detected and prompts the user to take action.
For trusted and malicious executable files and certificates, execution is determined based on reputation received from the
configured reputation source. So, the McAfee Application Control - Self-Approval dialog box isn't displayed for trusted and malicious files.

But, if the file or certificate reputation is unknown, the McAfee Application Control - Self-Approval dialog box prompts the user to take
action. Perform one of these tasks:
• Provide a justification (if mandatory) and click Allow to allow the action immediately. When you choose to self-approve the
action, an approval request is sent to the administrator who reviews the provided justification to determine whether to allow or
ban the action for one or more endpoints in the enterprise. The McAfee ePO administrator allows the action only if it is in
accordance with the corporate policies and the application is trusted and known.
• Click Deny to deny the action. Users can deny the action when it isn't user-initiated or the changes seem irrelevant. The deny
action is event-specific. If the same event is generated again, the user is prompted again to take an action.
Users can review the event notifications and request approval for certain actions.
1. Right-click the McAfee Agent icon in the notification area on the endpoint.
2. Select Quick Settings → Application and Change Control Events.
3. Request approval for an action from the McAfee ePO administrator by selecting the event and clicking Request Approval. The
McAfee ePO administrator receives an email including all relevant event details and a link. The administrator can click the
link to open the needed event in the Solidcore Events page and define needed rules.
Policy discovery permissions

By default, non-global administrators can view, manage, and delete requests generated only by endpoints in their associated
group (in My Organization).
If you review request details about the Request Details page, the number of requests listed in the Enterprise Level Activity pane might be
less than the value displayed in the Global Prevalence column on the Policy Discovery page. This is because the Global Prevalence column
indicates the enterprise-wide prevalence for the requests regardless of any groups. For example, if a request is generated by two
systems in different groups across the enterprise, the value in the Global Prevalence is 2. But, because non-global administrators
can only view the requests generated for their group, the non-global administrator might see only one request generated by the
system in their group in the Enterprise Level Activity pane.
Note: The McAfee ePO administrator can review and manage all requests generated in the enterprise (My Organization). Also,
McAfee ePO administrator can add rules to any rule group, and provide permissions to all non-global administrators to review
and take custom actions on the requests generated in the enterprise.
If you are a non-global administrator, you can add rules (for a request) to only the rule groups that you own. Rule groups that
you don't own are not displayed on the Policy Discovery: Custom Rules page. Also, if you take an action for a request, the action
doesn't impact the same request generated by the system in a different group.
Allow non-global administrators to manage enterprise-wide requests

If you are a McAfee ePO administrator, you can assign permissions to all non-global administrators (who have access to groups
in My Organization) to review and manage requests generated in your enterprise.
Task
2. From the Setting Categories pane, select Solidcore, then click Edit to open the Edit Solidcore page.
3. Change the value of Allow group administrators to manage Policy Discovery requests for entire System Tree to Yes (overrides System Tree group access
permissions).
4. Click Save.
Results
All non-global administrators are allowed to review and take custom actions on enterprise-wide requests. Non-global
administrators can't perform global actions.
Review approval requests

Review the requests received from the endpoints.
On the Solidcore: Health Monitoring dashboard, check the Top 10 Pending Policy Discovery Requests monitor to take notice of the data that
might require immediate action.

Task
After the requests are received from the endpoints, Application Control collates and groups requests based on these
parameters.
◦ SHA-1 value of the executable file or .cab file (if there is a request for an ActiveX control) where the request is received.
Note: Although Application Control supports SHA-256 value of files, only SHA-1 values are used for collating and grouping
requests on the Policy Discovery page.
◦ Status of the request.
Note: The Activity field for each request indicates the action performed by the user on the endpoint. For example, if the user
installs MSI-based software, the Activity field lists Software Installation for the request.
2. Review the listed requests using one of these methods.
◦ Specific interval — Select an option from the Time Filter list and click Update Results to view requests received in a specific
interval.
◦ Request status — Select a value for the request status from the Approval Status list and click Update Results to view requests
that match the selected status.
◦ Activity — Select a value from the Activity list and click Update Results to view requests for a certain activity.
◦ Reputation — Select a value from the Final Reputation list and click Update Results to view requests for files that match the
selected reputation level. For more information about how the software determines final reputation for files or certificates,
click What's Final Reputation.
◦ Specific endpoint — Enter an endpoint name in the System Name field and click Update Results to view requests received from
the endpoint. Make sure that you specify the complete system name because no partial matches are performed.
◦ Multiple criteria — Specify values for the Time Filter, Approval Status, Activity, Final Reputation, and System Name fields, as needed, and
click Update Results to perform a search based on multiple criteria.
◦ Specific search string — Enter a search string in the Quick find field and click Apply to view requests that match the specified
search string. Partial matches are performed based on the text you specify.
Note: You can enter User Comments field value as a search string.
◦ Sort — Sort the list based on the global prevalence, execution time, activity, object name, application name, certificate, final
reputation, or reputation source by clicking the column heading.
◦ Selected requests — Select requests of interest and click Show selected rows to review only the selected requests.
Note: The Policy Discovery page lists only the requests for which the McAfee ePO administrator can make rules. To view other
requests, such as those for software uninstall, run the Self-Approval Audit Report query. This report lists all requests received from
the endpoints in the last month.
3. Review individual requests that make up a collated request and detailed information for the file.
a. Click a row to open the Request Details page.
b. Review file details, such as name, version, path, parent process, files changed, and final reputation.
c. Review the SHA-1, SHA-256, and MD5 information for the file.
d. Click the file SHA-1 to review file details about the File Details page.
e. Review the certificate vendor name for the file. The certificate vendor name for a file is color coded to indicate trusted
(green), malicious (red), or unknown (orange) reputation.
f. Click certificate name to view certificate details, such as issuer, certificate reputation, reputation source, public key
algorithm, public key length, public key hash, certificate hash, valid from, and valid to.
g. Review the individual requests that make up the collated request in the Enterprise Level Activity pane.
h. Click Close.
Process approval requests

When the self-approval feature is enabled, administrators receive approval requests from users. Administrators review the
requests and can define rules for one or all endpoints.
The reputation value for a file is color-coded to indicate trusted, malicious, and unknown reputation:
• Values in green indicate that the file is Known Trusted, Most Likely Trusted, or Might be Trusted.
• Values in orange indicate that the file is unknown.
• Values in red indicate that the file is Known Malicious, Most Likely Malicious, or Might be Malicious.
• Values in grey indicate that reputation value is Not applicable (only for network path execution requests).

The reputation source indicates the source from where the reputation is fetched. Possible values for reputation source are TIE,
GTI, Application Control, Not synchronized, or Not Applicable. If you click the TIE value, it opens the TIE Reputations page where you can
view relevant details for the selected file.
Allow a file on all endpoints

You can define rules to allow an application or executable file to run on all endpoints in the enterprise.
Task
3. Click Actions → Allow File Globally.
The Allow File Globally dialog box provides details and prompts you to confirm the action.
4. Click OK.
Results
Allow a file by certificate

You can define rules to allow an application, executable file, or ActiveX control to run on all endpoints in the enterprise based on
the certificate associated with the file.
Task
3. Click Actions → Allow by Certificate Globally.
4. The Allow by Certificate Globally dialog box provides details and prompts you to confirm the action. Based on the file associated
with a selected request, the certificate is assigned or not assigned updater privileges. If the certificate has updater privileges,
allowing based on certificate allows all applications signed by the certificate to make changes to existing executable files or
start new applications on the endpoints.
5. Click OK.
Note: The Allow by Certificate Globally action is unavailable if the main executable associated with the request is signed by a
certificate included in the Restricted certificate names list.
Ban by SHA-1 or SHA-256 on all endpoints

You can define rules to ban an application or executable file from running on all endpoints in the enterprise based on the SHA-1
or SHA-256 value of the file.
Task
3. Click Actions → Ban File Globally.
The Ban File Globally dialog box provides details and prompts you to confirm the action.
4. Click OK.
5. Ban the files that have already been added to the endpoint.
a. Click the application name link.
The Files page lists all executable files installed on the endpoint.
b. Select all listed files.
c. Click Actions → Ban Files to open the Allow or Ban Files wizard.
d. Specify the rule group for the rules.

operating system.
system.
e. Make sure that the rule group where you add the rules is added to a policy that is applied on the endpoint where the
request was received.
f. Click Next.
g. Review the rules, then click Save.
Define rules for specific endpoints

You can add prepopulated rules to allow or ban an application, executable file, or ActiveX control for specific endpoints in your
administered groups. Or, you can define custom rules for specific endpoints or groups, as needed.
Task
2. Select the request where you want to define custom rules.
3. Click Actions → Create Custom Policy to open the Policy Discovery: Custom Rules page.
4. You can review rules or define rules:
◦ Review and add prepopulated rules – Select Approve Request, Ban Request, or Allow By Certificate.
◦ Define custom rules – Select Clear and define Rules.
6. (Optional) Add the changed or created rule group to a policy.
7. Click Save.
Results
This approves all grouped requests.
Allow by adding to whitelist for specific endpoints

You can add one or more executable files to the whitelist to allow the files to run on the endpoint.
Task
2. Click a row to review request details in the Request Details page.
Each row in the Enterprise level activity pane represents an executable file and endpoint combination.
3. Click Allow Locally for a row.
The Allow Locally dialog box lists one or more paths to add to the whitelist.
Note: The Allow Locally action is available only for requests that are generated when you execute an application that isn't in the
whitelist (Application Execution activity).
4. Review and customize the listed paths.
For example, if you execute proc.exe for an endpoint, these paths might be listed.
C:\Program Files\<App Name>\proc.exe
C:\Program Files\<App Name>\a.dll
C:\Program Files\<App Name>\b.dll
To avoid redundancy, add only the C:\Program Files\App Name path.
5. Click OK.
Results
The specified paths are added to the whitelist and allowed to run on the endpoint.

Task
Delete requests
You can remove requests from the Policy Discovery page and database.
Note: For optimal performance, the Solidcore: Auto Purge Policy Discovery Requests server task is run weekly to remove policy discovery
requests older than three months.
Task
2. Select the requests to delete.
3. Click Actions → Delete Requests.
Results
All selected collated requests and contained individual requests are deleted from the page and database.

Maintaining your system with McAfee ePO
Monitoring enterprise health
You can monitor the health of the protected endpoints in the enterprise. The Solidcore: Health Monitoring dashboard provides health
status at-a-glance.
The Solidcore: Health Monitoring dashboard includes specific monitors to indicate congestion levels for inventory items and
observations on the McAfee ePO console. You can also add more monitors to review congestion for self-approval requests and
client task logs. Possible values for the congestion levels are No congestion, Low, Moderate, High, and Data deleted.
Congestion level value Value for trend monitors Description
No congestion 0 This value indicates that no congestion is present in the McAfee ePO
database.
Low 1 This value indicates that data older than 5 days is present in the
McAfee ePO database and is yet to be parsed by the software.
Typically, Low congestion levels are automatically resolved. When
congestion begins, the Data Congestion Detected event is generated to
notify the user.
Moderate 2 This value indicates that data older than 5 days is still present in the
McAfee ePO database and is yet to be parsed by the software. You
might experience sluggish responses from the user interface at this
stage. When congestion levels reach Moderate, the Data Congestion
Detected event is generated to notify the user.
High 3 This value indicates that data older than 5 days is still not parsed by
the software and the McAfee ePO database is choked. If the
congestion level reaches High, old data is deleted from the McAfee
ePO database to resolve congestion. When congestion levels reach
High, the Data Congestion Detected event is generated to notify the user.
Data deleted 3 This value indicates that data pending for parsing for the feature has
been deleted from endpoints to resolve congestion. When data is
deleted from the McAfee ePO database, the Clogged Data Deleted event
is generated to notify the user.
Review congestion status and trend

You can review the monitors on the Solidcore: Health Monitoring dashboard to assess enterprise health status and trend.
Task
1. Select Menu → Reporting → Dashboards.
2. Select the Solidcore: Health Monitoring dashboard from the Dashboard list.
You can review the overall health of the enterprise.
3. Review congestion levels for inventory items:
◦ Review the Inventory Data Congestion Level monitor to validate if congestion is present for inventory items in the McAfee ePO
database.
◦ Check the Inventory Data Congestion Trend in Last 7 Days monitor to review the weekly trend.
4. Review observation requests:
◦ Review the Observations Data Congestion Level monitor to validate if congestion is present for observations in the McAfee ePO
database.
◦ Check the Observations Data Congestion Trend in Last 7 Days monitor to review the weekly trend.

5. (Optional) Review congestion levels for self-approval requests and client task logs.
a. From the McAfee ePO console, select Dashboard Actions → Duplicate for Solidcore: Health Monitoring dashboard, click OK in the Duplicate
Dashboard dialog box, then click Add Monitor.
b. Select Solidcore from the Category list.
c. Click and drag the Self-Approval Data Congestion Level and Client Task Logs Data Congestion Level monitors.
d. Select Queries from the Category list.
e. Click and drag the Queries monitor.
f. In the New Monitor dialog box, click the Monitor Content drop-down list.
g. Navigate to the McAfee Groups - Solidcore Health Monitoring section (McAfee ePO console), select the Self-Approval Data Congestion Trend
in Last 7 Days query, and click OK.
h. Repeat steps d through g for the Client Task Logs Data Congestion Trend in Last 7 Days query.
i. Review the Self-Approval Data Congestion Level and the Self-Approval Data Congestion Trend in Last 7 Days to review the weekly trend.
j. Review the Client Task Logs Data Congestion Level and the Client Task Logs Data Congestion Trend in Last 7 Days monitor to review the
weekly trend.
Configure notifications
You can configure alerts or automatic responses to receive a notification when data congestion begins for your environment.
To receive a notification when congestion begins for your setup, you can configure an alert for the Data Congestion Detected event.
Similarly, to receive a notification when data is deleted from the McAfee ePO database to resolve congestion, you can configure
an alert for the Clogged Data Deleted event.
Task
1. Select Menu → Automation → Automatic Responses.
2. Click Actions → New Response, then enter the alert name.
3. Select the ePO Notification Events group and Threat event type.
4. Select Enabled, then click Next to open the Filter page.
5. Select My Organization for the Defined at property, then Select Threat Name from the Available Properties pane.
6. Include this information in the Value field:
a. Type DATA_CONGESTION_DETECTED and click +.
b. Type CLOGGED_DATA_DELETED and click Next.
7. Specify aggregation details, then click Next to open the Actions page.
8. Select Send Email, specify the email details, and click Next to open the Summary page, then review the details and click Save.
Make emergency changes

To implement an emergency change, you can create a change window that overrides all protection and tamper proofing that is in
effect. Use a change window only when the other available mechanisms can't be used.
Place the endpoints in Update mode, then make the required emergency changes and place the endpoints in Enabled mode.
Place the endpoints in Update mode

Place the endpoints in Update mode to make emergency changes.
Task
1. Select Menu → Systems → System Tree.
◦ Group — Select a group in the System Tree and click the Assigned Client Tasks tab.
◦ Endpoint — Select the endpoint on the Systems page, then click Actions → Agent → Modify Tasks on a Single System.
4. Select Solidcore 8.x.x for the product, SC: Begin Update Mode task type, then click Create New Task to open the Client Task Catalog page.
b. Enter the Workflow ID and any comments you want.
c. Click Save.

Place the endpoints in Enabled mode

Place the endpoints back in Enabled mode after you complete the required changes in Update mode.
Task
◦ To apply the client task to a group, select a group in the System Tree and click the Assigned Client Tasks tab.
◦ To apply the client task to an endpoint, select the endpoint on the Systems page, then click Actions → Agent → Modify Tasks on a
Single System.
a. Select Solidcore 8.x.x for the product, SC: End Update Mode for the task type, then click Create New Task to open the Client Task Catalog
page.
b. Specify the task name and add any information you want.
c. Click Save, then click Next.
d. Specify the task name and add any information you want.
e. Specify scheduling details, then click Next.
f. Review and verify the task details, then click Save.
Administering throttling for your enterprise

When several events, policy discovery requests (observations), or inventory updates are received on the McAfee ePO server, the
McAfee ePO interface might become unresponsive or sluggish. The throttling feature helps avoid such scenarios.
You can control the flow of events, policy discovery requests, and inventory updates. When the data sent to the McAfee ePO
server reaches the defined threshold for an endpoint, throttling is initiated and these actions are taken.
1. Data is no longer sent to the McAfee ePO server.

2. Data is stored in a cache at the endpoints. When the cache is full, data starts dropping with the oldest.
Note: Data is stored in the cache only for event and policy discovery requests. The inventory data isn't stored in the cache;
instead, it is updated at the endpoints locally.
3. Throttling is reset no less than 24 hours after the first event, policy discovery request, or inventory update for the day.
Note: When throttling of inventory updates is initiated, the Pull Inventory client task is disabled. This indicates that you can't
fetch inventory until throttling resets.
4. Data stored in the cache is sent to the McAfee ePO server in batches (starting with the oldest data).
After throttling resets for events and policy discovery requests, further generated data is stored in the cache and not sent to the
McAfee ePO server until the cache is empty.
The throttling feature is available on all supported Windows platforms. You can manage throttling by identifying the endpoints
where throttling is initiated and taking remedial actions. If needed, you can configure throttling for your enterprise.
Set up throttling
By default, the throttling feature is enabled for events, inventory updates, and policy discovery requests.
Enabling or disabling this feature also enables or disables all its subfeatures.
Task
2. Select the Solidcore 8.x.x: General product.
5. Open the policy and click the Throttling tab.

6. Enable or disable throttling by clicking Enable Throttling.
This enables or disables the throttling feature for events, inventory updates, and policy discovery requests.
7. (Optional) Disable the throttling feature selectively for Events, Inventory Updates, and Policy Discovery (Observations).
When the throttling feature is enabled, you can disable one or more types of throttling by deselecting the corresponding
checkbox.
Configure throttling values

For most enterprises, the default settings for the throttling feature are enough. But, if needed, you can change the default
configuration for the feature.
Task
2. Select Solidcore 8.x.x: General for the product.
5. Open the policy and click the Throttling tab.
6. Edit the values for events, inventory updates, and policy discovery requests, as needed.
Value Description
Events The value for threshold and cache size is defined in number
of event XML files. By default, 2000 XML files can be
processed per endpoint in 24 hours. Also, the default event
cache size is set to 7000 XML files per endpoint.
Inventory Updates The value for threshold is defined in number of file elements
containing inventory updates. By default, 15000 files
elements can be processed per endpoint in 24 hours.
Policy Discovery (Observations) The value for threshold and cache size is defined in number
of request XML files. By default, 100 XML files can be
processed per endpoint in 24 hours. Also, the default event
cache size is set to 700 XML files per endpoint.
Manage throttling
You can determine if throttling is initiated for any endpoint in your setup and you can take action to manage the feature.
On the Solidcore: Health Monitoring dashboard, check the Number of Systems where Throttling Initiated in Last 7 days monitor to take notice of the
systems that might require immediate action.
Task
1. Determine if throttling is initiated and identify the affected endpoints.
Event Description
Data Throttled Generated for an endpoint when event or policy discovery request
throttling is initiated. After throttling resets, this event is generated
daily until the cache is empty.
Data Dropped Generated in 2 scenarios for an endpoint.

◦ When the cache is full and the oldest data is dropped from the
event or request cache.

Event Description
◦ When throttling of inventory updates is initiated for the endpoint.
2. Review the throttling status for each affected endpoint.

3. Process data generated for affected endpoints and create relevant rules. You must process data quickly to make sure that data
isn't dropped.
Identify endpoints where throttling is initiated

You can identify endpoints where Data Throttled and Data Dropped events are generated.
You can create an automatic response for these events.
Task
2. Review the event list and locate endpoints where these events are generated.
Event Action
Data Throttled Review the Object Name column for information about throttling of events or policy
discovery requests (observations) for the corresponding endpoints. Based on the type
of throttling, you must immediately review the throttling status and process data for
the endpoint to make sure that you don't lose data.
Data Dropped Review the Object Name column for information about throttling of inventory updates.
This column also provides information if data has started dropping for events and
policy discovery requests (observations). Typically, this occurs when data isn't
processed quickly for the endpoint. Based on the type of throttling, you must
immediately process data or manage inventory updates.
Review throttling status

For endpoints where throttling is initiated, you can review the throttling status.
Task
1. From the McAfee ePO console, select Menu → Systems → System Tree.
2. On the Systems page, click the endpoint where throttling is initiated to view its details.
3. Click the Products tab.
4. Click the Solidcore row to view product details.
5. Review the values for the listed throttling properties.
Property Description
Throttling Status: Events Provides this information.

◦ Cache usage
Throttling Status: Policy Discovery (Observations)
This indicates the percentage of event or request cache
that is already used by the stored events or requests.
◦ Number of dropped events or requests
When the cache usage reaches 100%, events or requests
start dropping and the Data Dropped event is generated and
displayed on the Threat Event Log and Solidcore Events pages.
◦ Time when the threshold was reached
This indicates the time when event or request throttling
was initiated.

Property Description
Inventory Fetch Time (Last) Indicates the time when the inventory was last fetched.
When throttling of inventory updates is initiated, the Pull
Inventory client task is disabled and you can't fetch the
inventory until throttling resets.
Inventory Fetch Time (Next) Indicates the time when you can fetch the inventory for the
endpoint. When throttling of inventory updates resets (24
hours after the first inventory update was generated), the
Pull Inventory client task is enabled again to allow you to fetch
the inventory. In such scenarios, this property displays the
time when throttling resets.
Process data where throttling is initiated

On endpoints where throttling is initiated, you can create relevant rules or filters to process data. This helps you control the flow
of data by gradually reducing the amount of received data.
Task
On the McAfee ePO console, take relevant actions based on the type of data.
a. Events — Select Menu → Reporting → Solidcore Events.

On the identified endpoints where throttling is initiated, review the generated events, then create relevant rules for events
based on details such as event type, generation time, and number of occurrences. Define advanced exclusion filters to exclude
non-meaningful events from the endpoints.
b. Requests — Create relevant rules to process requests and define advanced exclusion filters to exclude non-meaningful
requests from the endpoints.
c. Inventory updates — Define advanced exclusion filters to exclude non-meaningful inventory updates from the endpoints.
Configure CLI breach notifications

Administrators need to be aware of any attempt to recover the CLI with an incorrect password. In case any attempt is made to
breach security, the CLI needs to be disabled immediately to thwart the attempt.
You can configure Application Control and Change Control products to notify the administrator of any unsuccessful attempts to
recover the CLI on the endpoint.
Note: This feature is available only in McAfee ePO-managed configuration and unavailable in standalone configuration.
Task
2. Select Solidcore 8.x.x: General for the product.
5. Open the policy and click the CLI tab.
6. Enable the feature by clicking Enable.
By default, this feature is disabled.
7. Specify the number of failed attempts and the interval after which to disable the CLI in case of a security breach.
By default, the CLI is disabled if a user makes three unsuccessful attempts in 30 minutes.
8. Specify how long to disable the CLI if any user makes unsuccessful logon attempts.
By default the CLI is disabled for 30 minutes.
9. Click Save.
10. Apply the policy to the endpoints.
Results
After you enable the feature:

• Each attempt to recover the CLI with the correct password generates the Recovered Local CLI event.
• Any attempt to recover the CLI with an incorrect password generates the Unable to Recover Local CLI event.
When the user exceeds the permitted number of failed attempts (as defined in the policy), the CLI recovery is disabled to prevent
the breach attempt. The Disabled Local CLI Access event is generated. This is priority event and is sent immediately to the McAfee
ePO console.
Change the CLI password

You can change the default command line interface (CLI) password to prevent others from accessing the CLI.
Task
2. Select the Solidcore 8.x.x: General product.
The Duplicate Existing Policy dialog box appears.
The policy is created and listed on the Policy Catalog page.
5. Click the policy to open it.
6. Type the new password in the CLI tab.
7. Confirm the password.
8. Click Save.
9. Apply the policy to the endpoints.
Collect debug information

Before contacting McAfee Support to help you with a Solidcore client issue, collect configuration and debug information for your
setup.
This helps McAfee Support quickly identify and resolve the issue. Run the Collect Debug Info client task to create an archive with
endpoint configuration information and Solidcore client log files. The .zip file is generated on the endpoint and its location is
listed on the Client Task Log page. Send the .zip file to McAfee Support with details of the encountered issue.
Create a .zip file with configuration and debug information.
Task
4. Select Solidcore 8.x.x for the product, SC: Collect Debug Info task type, then click Create New Task to open the Client Task Catalog page.
5. Specify the task name and add any descriptive information.
Place the endpoints in Disabled mode

When you place the endpoints in Disabled mode, the software isn't in effect. Although it is installed, the associated features
aren't active.
Task
1. Select Menu → Systems → System Tree.

4. Select Solidcore 8.x.x for the product, SC: Disable task type, then click Create New Task to open the Client Task Catalog page.
5. Specify the task name and add any descriptive information.
6. Select or deselect Reboot endpoint based on the Solidcore cliente version:
◦ Version 5.1.2 or earlier — Select Reboot endpoint to restart the endpoints.
◦ Version 6.0.0 and later – Select Reboot endpoint to restart the endpoints.
◦ Version 6.1.0 and later — Deselect Reboot endpoint to restart the endpoints.
8. Specify scheduling details, click Next, then click Save.
Sending McAfee GTI feedback

Application Control includes seeded server tasks to send feedback to McAfee about your current use of the McAfee GTI and
Application Control features.
• Solidcore: Send Event Feedback to McAfee GTI Server (disabled by default)
• Solidcore: Send Policy and Inventory Feedback to McAfee GTI Server (enabled by default to run daily)
• Solidcore: Send Policy Discovery Request Feedback to McAfee GTI Server (enabled by default to run daily)
Note: No information about individual computers or users is sent to McAfee. McAfee stores no data that can be used to track the
feedback information to a specific customer or organization.
Server task settings

You can configure the server tasks to send information about how you are currently using one or all these parameters.
Events Send information, such as file name and SHA-1 for the Execution Denied, Process Hijack Attempted, and
Nx Violation Detected events. You can also send information about the number of endpoints where the
event occurred with the full path of the file.
This information helps McAfee determine how frequently and effectively Application Control blocks
actions, and helps to improve product functionality and efficacy.
Policies Send information about user-editable Change Control, Application Control, and General policies.
Information is also sent for the Global Rules and Global Observation Rules (Deprecated) rule groups.
This information helps McAfee understand how you are currently using polices and applying rules, and
helps to improve the default policies and rules.
Inventory Send detailed information for files, including base name, application name, application version, file
version, and enterprise trust level. You can also send information about the number of endpoints where
the file is present, its execution status, and full path of the file. The feedback does not include any
information to identify the endpoints, such as system name or IP address.
This information helps McAfee determine how you are using (and changing) the File Hash Trust Score
(GTI) and File Hash Reputation (GTI) values assigned to files. This information also helps to improve the
McAfee GTI file reputation service.
Policy Discovery SenMcAfee GTId information for policy discovery requests and include details about the certificate
requests associated with the file.
This information helps McAfee determine the type of requests generated for your setup and identify
certificates associated with commonly used applications.
ePO base Sends information about the number of nodes managed by McAfee ePO and number of nodes where
information Application Control is installed.
Configure server tasks

You can configure the server tasks that send feedback, as needed.

Task
2. Select Edit for a server task to open the Server Task Builder wizard.
3. Change the schedule status for the task.
4. Click Save.
Purge reporting data

You can purge Solidcore reporting data by age or other parameters. When you purge data, the records are permanently deleted.
Task
2. Click New Task to open the Server Task Builder wizard.
3. Type the task name, then click Next.
4. Select Solidcore: Purge from the Actions list.
5. Configure these options, as needed.
◦ Choose Feature — Select the reporting feature for which to purge records.
◦ Purge records older than — Select this option to purge the entries older than the specified age.
◦ Purge by query — Select this option to purge the records for the selected feature that meet the query criteria. This option is
only available for reporting features that support queries in McAfee ePO. Also, this option is supported only for tabular
query results.
Note: No seeded queries are available for purging. Before purging records, you must create the query from the Menu →
Reporting → Queries & Reports page.
7. Specify schedule details, then click Next open the Summary page.
8. Review and verify the details, then click Save.

Maintaining your system in standalone mode
View product status and version
You can view the status of Application Control, such as operational mode, operational mode after restart, and whitelist status.
You can also view details such as software version and copyright information.
Task
1. View Application Control status:
sadmin status [volume]
Include [Volume] to view details of a single volume.
A message similar to this example displays the system details.
McAfee Solidifier: Disabled
McAfee Solidifier on reboot: Disabled
ePO Managed:No
Local CLI access: Recovered
[fstype] [status] [driver status][volume]

* NTFS Solidified Unattached C:\
Status detail Description
McAfee Solidifier Specifies the operational mode of Application Control.
McAfee Solidifier on reboot Specifies the operational mode of Application Control after
system restart.
ePO Managed Displays the connectivity status of Application Control with

McAfee ePO. In standalone configuration of the product, this
status is No.
Local CLI access Displays the lockdown or recovered status of the local CLI. In
standalone configuration of the product, this status is
Recovered.
fstype Displays the supported file systems for a volume.
status Displays the current whitelist status for all supported

volumes on a system. If a volume name is specified, only the
whitelist status for that volume is displayed.
driver status Displays whether the Application Control driver is loaded on

a volume. If the driver is loaded on a volume, status is
attached; otherwise the status is unattached.
volume Displays the volume names.
2. View version and copyright details of Application Control installed on the system.
sadmin version
Manage the whitelist

Configure whitelist thread priority
The whitelist thread priority (SoPriority) determines the usage of system resources and the time required to create the
whitelist.

You can configure the whitelist thread priority before creating the initial whitelist. By default, the thread runs on low priority
(value of 0) and if you do not specify the thread priority, Application Control considers the default priority to create the whitelist.
Task
Run this command and specify the SoPriority value.
• sadmin config set SoPriority=<value>
The SoPriority value that you specify should be based on your preference. This table describes the SoPriority values
that you can specify.
Advantages
Priority
Value and disadvantages
The
Low
0 low value, takes more time to create the whitelist but causes minimal performance impact on the system.
(Recommended)
N/A
Medium
1
The
High
2 high value takes less time but uses more system resources and can cause performance impact on the system.
Add and remove components from the whitelist

You can add new components to the initial whitelist to allow their execution on a protected system. If needed, you can remove
components from the whitelist.
Task
Specify the components as file names, directory names, or volume names.
Command
Description
syntax
Action
After
Add the initial whitelist is created, execution is blocked for the components that are not included in the whitelist. If needed,
sadmin
add
components
more components to the whitelist.
solidify
to
[<arguments>
the
<components>]
whitelist.
Remove
Removeall components from the whitelist using this command. When you remove components from the whitelist, they are
sadmin
no
alllonger protected by Application Control.
unsolidify
components
from
the
whitelist.
Specify
Remove
sadmin the components that you want to remove from the whitelist.
selected
unsolidify
components
[<arguments>
from
<components>]
the
whitelist.
You can add or remove components from the whitelist as described in this table.
Component Description
File name Add files to the whitelist. For example,

sadmin solidify filename1 ... filenameN

Remove files from the whitelist. For example,

sadmin unsolidify filename1 ... filenameN
Directory name Add all supported files (recursively) under specified directories to the whitelist. For example,
sadmin solidify directoryname1 ... directorynameN
Remove all supported files in one or more directories from the whitelist. For example,
sadmin unsolidify directoryname1 ... directorynameN
Volume name Add all supported files (recursively) under specified system volumes to the whitelist. For example,
sadmin solidify volumename1 ... volumenameN
Remove all supported files in one or more system volumes from the whitelist. For example,
sadmin unsolidify volumename1 ... volumenameN
File name Optionally, you can specify supported arguments with the command.
Directory name • Add — sadmin solidify [ –q | –v ] filename1 ... filenameN | directoryname1 ...
Volume name directorynameN | volumename1 ... volumenameN
• Remove — sadmin unsolidify [ –v ] filename1 ... filenameN | directoryname1 ...
directorynameN | volumename1 ... volumenameN
Here are the arguments descriptions:

• The -q argument displays only error messages.
• The -v argument displays all messages.
View whitelisted files

You can view lists of all whitelisted and non-whitelisted files, directories, and drives/volumes on your system.
Task
1. List all whitelisted components.
◦ sadmin list-solidified
2. List all non-whitelisted components.
◦ sadmin list-unsolidified
You can narrow the results by specifying components as described in this table.
File name List all whitelisted files. If only one file name is specified, this command shows the file name
only if it is whitelisted.
sadmin list-solidified filename1 ... filenameN
List all non-whitelisted files. If only one file name is specified, this command shows the file
only if it is not whitelisted.
sadmin list-unsolidified filename1 ... filenameN
Directory name List all whitelisted files present in the specified directories.
sadmin list-solidified directoryname1...directorynameN
List all non-whitelisted files present in the specified directories.

sadmin list-unsolidified directoryname1...directorynameN
Volume name List all whitelisted files present in the specified drives/volumes.
sadmin list-solidified volumename1...volumenameN

List all non-whitelisted files present in specified volumes.

sadmin list-unsolidified volumename1...volumenameN
File name List details about the files, such as file type, file path, and file checksum.
Directory name sadmin list-solidified [ -l ] filename1 ... filenameN |
Volume name directoryname1...directorynameN | volumename1...volumenameN
Check and update the status of whitelisted components

You can compare the current whitelist status and checksum values of whitelisted files, directories, and volumes with the status
and values stored in the whitelist. If they are not current, you can update the whitelist and fix inconsistencies.
If the components in the whitelist are changed or removed and the whitelist is not updated, the execution of these components
is blocked. This results in inconsistencies in the whitelist.
Task
sadmin check [ -r ] file | directory | volume
You can narrow the results by specifying the names of files, directories, and drive/volumes with this command.
Also, you can specify the -r argument with this command. This argument fixes inconsistencies by updating the whitelist with the
latest checksum values of the components and adds the components to the whitelist, if the components are not already present.
If you don't specify a component, inconsistencies in all supported drives/volumes are fixed.
Review product features

You can review the list of all Application Control features and their status (enabled or disabled) on your system.
Task
sadmin features list
The features list is displayed on the screen.
Note: Starting from the Application Control 6.0.0 release, the features list has been minimized to show only the features that
require changes regularly.
Supported Operating
Feature Description Default status System
activex It installs and runs ActiveX controls on the Enabled Windows

protected system. Only the Internet Explorer
browser is supported for the ActiveX control
installations. Simultaneous installation of
ActiveX controls using multiple tabs of Internet
Explorer is not supported.
checksum It compares the checksum of the file to be Enabled Windows and Linux
executed with the checksum stored in the
whitelist.
deny-read It read-protects the specified components. Disabled Windows and Linux

When this feature is applied on components,
they cannot be read. Read protection works
only when Application Control is running in
Enabled mode.

Supported Operating
deny-write It write-protects the specified components. Enabled Windows and Linux

When this feature is applied on the
components, they are rendered as read-only to
protect your data.
discover-updaters It generates a list of potential updaters that can Enabled Windows

be included in the system.
It tracks all failed attempts made by authorized
executable to change protected files or run
other executable files. It also generates a list of
possible updaters that can be configured on
the system to perform an update.
enduser-notification It displays a customized notification message Enabled Windows

on the system when Application Control
prevents an action on the system. This feature
is supported only in the McAfee ePO-managed
configuration.
execution-control It defines attribute-based rules using one or Enabled Windows

more attributes of a process to allow, block, or
monitor the process.
integrity This feature: Enabled Windows and Linux

• Protects Application Control files and registry
keys from unauthorized tampering.
• Allows the product code to run even when the
components are not present in the whitelist.
• Ensures that all product components are
protected.
• Prevents accidental or malicious removal of
components from the whitelist to ensure that
the product doesn't become unusable.
• Is disabled in update mode to facilitate
product upgrades.
mp It protects running processes from hijacking Enabled Windows

attempts. Unauthorized code injected into a
running process is trapped, halted, and logged.
It also attempts to gain control of the system
through buffer overflow and similar exploits are
rendered ineffective.
mp-casp It renders useless code that is running from the Enabled Windows
non-code area, which happens due to a buffer
overflow being exploited on 32-bit Windows
platforms.
mp-vasr It forces relocation of those dynamic-link Enabled Windows

mp-vasr-forced- libraries (DLLs) that have opted out of the
relocation Windows native ASLR feature.
Some malware relies on these DLLs always
being loaded at the same and known

Supported Operating
addresses. By relocating such DLLs, these
attacks are prevented.
network-tracking It tracks files over network directories and Enabled Windows

blocks the execution of scripts over network
directories. By default, this feature is enabled
and prevents the execution of scripts over
network directories. When this feature is
disabled, execution of scripts over network
directories is allowed. Also, write-protecting or
read-protecting components over a network
directory is not effective.
pkg-ctrl It manages installation and uninstallation of Enabled Windows

MSI-based and non-MSI-based installers.
script-auth It prevents the execution of supported script Enabled Windows and Linux
files that are not in the whitelist. Only
whitelisted script files are allowed to execute on
the system. For example, supported script files
such as .bat, .cmd, .vbs (on Windows), and
script files with #! (hash exclamation point) for
supported local file systems (on Linux) are
added to the whitelist and are allowed to run.
throttle It controls the flow of data (events, policy Enabled Windows

discovery requests, and inventory updates)
from each system to the McAfee ePO server.
Note: This feature is available only in a McAfee
Enable or disable features

You can change the default status of a feature by enabling or disabling features. After disabling a feature, the system is no longer
protected by that feature.
Caution: Contact Technical Support before enabling or disabling a feature. It can affect the core functionality of the product and
make your system vulnerable to security threats.
Task
Run these commands to enable and disable features.
Task Command
Enable a feature. sadmin features enable <featurename>
Disable a feature. sadmin features disable <featurename>
Package Control feature

You can manage the installation and uninstallation of software packages using the Package Control feature.
This feature allows or denies installation, uninstallation, and upgrade or repair actions for software packages. It prevents any
unauthorized installation and uninstallation.
Package Control feature supports these types of installers.

• MSI installers — Include multiple variants such as .msp, .mst, and .msm.
• EXE-based installers — Include MSI files embedded with the installer.
• Non-MSI-based installers — Don't include an MSI file embedded with the installer.
This feature is identified as pkg-ctrl in the features list. By default, this feature is enabled and allows installation of software
packages by adding rules, such as updater and trusted user. When this feature is disabled, software installation and
uninstallation are blocked.
Package Control includes these subfeatures.
Subfeature Description
Allow Uninstallation Controls uninstallation of software packages. When this feature is enabled, software
uninstallation is allowed. By default, this feature is enabled and identified as pkg-ctrl-allow-
uninstall in the features list.
Bypass Package Control Controls bypassing from the Package Control feature. When this feature is enabled,
Package Control feature is bypassed and software installation and uninstallation is
allowed. By default, this feature is disabled and identified as pkg-ctrl-bypass in the features
list.
Configure Package Control

You can configure Package Control to control the installation and uninstallation of software packages on a system.
Task
Use these commands to configure Package Control.
Action Command Description
Disable the feature. sadmin features disable pkg-ctrl When you disable Package Control, all its
subfeatures are also disabled.
Enable the feature. sadmin features enable pkg-ctrl When you enable Package Control, all its
subfeatures revert to their default state.
But, if you enable the Bypass Package Control
subfeature, disable Package Control and re-
enable Package Control, the Bypass Package
Control subfeature is enabled.
Configure these Package Control subfeatures.
Feature Default state Feature configuration
Allow Uninstallation Enabled Disable the feature. sadmin features disable pkg-ctrl-allow-
Prevent uninstallation of uninstall
software packages on the
system.
Enable the feature. sadmin features enable pkg-ctrl-allow-

uninstall
Bypass Package Disabled Enable the feature. sadmin features enable pkg-ctrl-bypass
Control The Package Control feature
is bypassed and you cannot
control the installation and

Feature Default state Feature configuration
uninstallation of software
packages.
Disable the feature. sadmin features disable pkg-ctrl-bypass
Making emergency changes

Run Application Control in Update mode to perform emergency changes on a protected system.
When the product is in effect, you can allow scheduled or emergency changes to the system and track the changes made to the
system by running the product in Update mode. Use Update mode to make changes that cannot be made when Application
Control is running in Enabled mode. When possible, use these other methods to allow changes.
• Trusted users
• Trusted directories
• Trusted certificates
• Checksum (SHA-1 or SHA-256)values
• Updaters
In Enabled mode, if you install new software or add new files, the files aren't added to the whitelist or allowed to execute unless
you use a trusted method to add them. But, if you install or uninstall software, or add new files in Update mode, changes are
tracked and added to the whitelist.
To approve changes to the system, a change window is defined, where users and programs can make changes to the system.
Update mode allows you to perform these tasks:
• Schedule software and patch installations.
• Remove or change software.
• Dynamically update the whitelist.
Memory-protection techniques are enabled in Update mode, so that running programs cannot be exploited.
From Update mode, you can switch to Enabled or Disabled mode.
Switch to Update mode

Switch Application Control to Update mode to perform scheduled or emergency changes in a system. If the product is in Enabled
or Disabled mode, perform these steps to switch to Update mode.
Task
sadmin bu [workflow-id [comment]]
Optionally, specify these arguments with the command.
Attribute Description
workflow-id Specify a workflow ID for the current Update mode session. This is an identification
ID that can be used for a Change Management or Ticketing System.
If you don't provide the workflow ID, the workflow ID is set to an automatically
generated string, AUTO_n, where n is a number that is incremented each time an
update window is opened.
comment Specify a comment that describes the current Update mode session.
This information can be used for a Change Management or Ticketing System.
If Application Control is in Enabled mode, it is switched to Update mode.

If Application Control is in Disabled mode, perform one of these extra steps.

Step Description
Restart the system. When you restart the system, the product is switched to Update
mode. Restarting the system is a recommended way to switch to
Update mode.
Restart the Application Control service. Or, you can restart the Application Control service to switch to
Update mode. But only limited features will be enabled after service
restart.
Key product features, such as memory-protection and Script As
Updater (SAU) aren't enabled. To enable all features, you must
restart the system.
Exit Update mode

Exit Update mode after making scheduled or emergency changes, patch installations, or software updates in your system.
Task
sadmin eu
Enable or disable password protection

You can restrict users from running critical sadmin commands by enabling password protection. When password protection is
enabled, Application Control allows these critical commands to run only when the user enters the correct password.
Passwords are encrypted with the SHA2 hashing algorithm. To protect password details, a random number is added to the
password before the hash is computed. The SHA5012 encryption algorithm, a subset of SHA2, generates a hash of 512 bits,
which protects the password from rainbow table attacks.
If you don't need password protection, remove the password, which allows users to run all sadmin commands.
Task
1. Type the sadmin passwd command to set a password.
When you set a password, users can no longer run critical commands without providing the correct password. Only a limited
set of non-critical commands can run without the password.
You can use the -z switch to prevent the system from prompting for the password. It can be used in all CLI commands. For
example, sadmin solidify -z <password> is used for unmanaged CLI operations, and is different from the password for the
McAfee ePO administrator used for CLI lockdown.
◦ If you already set the password, Application Control prompts you to enter your password. Type the old password and press
Enter. You are now asked to set the new password and retype it.
◦ If you didn't set the password earlier, Application Control prompts you to enter a new password. Set the new password and
retype it.
2. Type the sadmin passwd -d command to remove the password.
3. Press Enter.
Reviewing changes using events

Application Control generates events for all changes that are made to a protected component. Use events to review the changes
and diagnose unauthorized execution attempts and failures in the system.
When an attempt is made to access or change a protected resource, an event is generated. Application Control tracks these
changes and records events. For example, every time the attributes or contents change for a protected file, a corresponding
event is generated.
Configure event sinks

Events are stored at locations called event sinks. You can add, view, or remove an event.

You can log events in many types of event sinks, including:
• Operating system log (oslog)
• System controller (sc)
Note: When sc event sink is enabled, it sends the events to McAfee ePO.
• Debug output (debuglog)
• Pop-up (Windows only)
You can review the event sinks details and add or remove events as needed.
Task Command Description
Add an event sadmin event sink -a <event_name> Add an event by specifying both the
<sink_name> event name and the event sink where
you want to log the event. The specified
event is added to the event sink.
View the event sink details sadmin event sink View the event sink details for all events
generated in the system. You can view
the associated event sinks for each
event. Event sink details configured in
the system for all events are listed.
Remove an event sadmin event sink -r <event_name> Remove an event by specifying both the
<sink_name> event name and the event sink from
where you want to remove the event.
Removing an event from an event sink
allows you to stop logging the event to
that event sink.
Set the event cache size

Set the event cache size to define the buffer limit for the event cache.
Task
sadmin config set EventCacheSize=<value>
Include a value for the EventCacheSize parameter. This value determines the event cache size.
Define the limits for the event cache

You can set the upper and lower limits for the event cache. When the limits are set, an alert is generated to notify that the cache
is about to overflow or has recovered from overflow.
Command Description
sadmin config set EventCacheWMHigh=<value> This command sets an upper limit.

Include a value for the EventCacheWMHigh parameter. The
specified value for this parameter should be between 50% to
100% of the event cache size.
sadmin config set EventCacheWMLow=<value> This command sets a lower limit.

Include a value for the EventCacheWMLow parameter. The
specified value for this parameter should be above 20% of the
event cache size. The value of the low watermark level must
always be less than the value of the high watermark level.

View events
You can view events specific to Application Control to track changes related to the product.
Task
1. Open the Event Viewer application:
◦ Windows Server 2008 — Select Start → Run and type eventvwr.
◦ Windows 7 — Select Start → Search and type eventvwr.
◦ Windows 8, 8.1, Server 2012, and Windows 10 — Press [Windows] + [R] on the keyboard, then type eventvwr.
2. Press Enter.
3. Perform these steps based on your platform:
◦ Windows Server 2008 — From the navigation pane, select Application and under the Source column, double-click McAfee Solidifier
event to view its description.
All application events categorized by type, date, time, source, category, event, user, and computer columns are displayed.
Events are listed by order of occurrence, with most recent first.
◦ Windows 7 and later — From the navigation pane, expand Window Logs and select Application. Under the Source column, look for
the McAfee Solidifier events.
Double-click an event to view its description.
Configuring log files

Application Control generates log messages for all actions and errors related to the product. These log messages are stored in
log files that are used for troubleshooting errors.
Operating
Log file system Path Description
solidcore.log Windows <system drive>\Documents After the product is deployed

Server 2008 and Settings\All users on a system, a log file named
\Application Data\McAfee solidcore.log is created in the
\Solidcore\Logs Logs foder. This file is also
known as debuglog.
You can configure the
solidcore.log file size and
number of solidcore.log files
that you want to create on the
system.
Note: Configuring log files is
applicable only to the
solidcore.log file. You can't
change the configuration of
any other log file.
s3diag.log Windows <system drive>\Documents s3diag.log file stores logs for

Server 2008 and Settings\All users all operations performed on
\Application Data\McAfee the supported files.
\Solidcore\Logs
Solidcore_Installer.log and Windows (all <system drive>\Windows Application Control

solidcore_setup.log supported installation logs are stored in
versions) this file.
Disable Application Control

Switch to Disabled mode to deactivate the features of Application Control.

Task
1. Type the sadmin disable command.
2. Press Enter.
3. Restart the system.

Using the command-line interface
List of Commands for Application Control
When using Application Control in a standalone configuration, you can use different commands and arguments to manage the
software and its features.
attr
This command changes or lists the software configuration attributes.
Command syntax conventions
• sadmin attr add -a|-c|-h|-j|-l|-m|-p|-u filename
• sadmin attr add -o parent= filename2 -i filename1
• sadmin attr add -v filename (Windows 7 and later)
• sadmin attr remove -a|-c|-h|-i|-j|-l|-m|-p|-u filename
• sadmin attr remove -v filename (Windows 7 and later)
• sadmin attr list -a|-c|-h|-i|-j|-l|-m|-p|-u filename
• sadmin attr list -v filename
• sadmin attr flush -a|-c|-h|-i|-j|-l|-m|-p|-u filename
• sadmin attr add -n filename (Windows 64-bit)
• sadmin attr remove -n filename (Windows 64-bit)
• sadmin attr list -n filename (Windows 64-bit)
• sadmin attr flush -n filename (Windows 64-bit)
auth
This command authorizes an application (executable, installer, or batch file) as a whitelist, or unauthorizes an application by
adding to the blacklist. The application can be locally installed, invoked, or installed or invoked from a shared drive.
• sadmin auth -a [ -t rule id ] [ -u ] -c checksum
• sadmin auth -b -c checksum
• sadmin auth -b [ -t rule id] -c checksum
• sadmin auth -f
• sadmin auth -l
• sadmin auth -r checksum
begin-update (bu)
This command initiates Update mode to help perform software updates and installations.
• sadmin begin-update/bu [workflow-id [ comment]]
cert
This command manages certificates for digitally signed files. You can add, remove, or list the certificates in the Application
Control certificate store, which is a directory in the install directory <instlall_dir>/Certificates
• sadmin cert add certificate_name
• sadmin cert add -u certificate_name
• sadmin cert add -c certificate_content
• sadmin cert remove SHA-1
• sadmin cert remove SHA-256
• sadmin cert remove -c certificate_content
• sadmin cert list [-d|-u]
• sadmin cert flush
check
This command validates and fixes the attributes of the specified file against the inventory.

• sadmin check [-r] file/directoryname/volumename...
config
This command exports current configuration settings to a file or imports configuration settings from a file to an existing
installation.
• sadmin config export file
• sadmin config import [-a]file
• sadmin config set name=value
• sadmin config show
diag
This command runs diagnostics and offers suggestions on programs and applications to authorize (to perform updates).
• sadmin diag
• sadmin diag fix [ -f ]
disable
This command activates Disabled mode. Restart the system to make sure that the command is applied.
• sadmin disable
enable
This command activates Enabled mode. Restart the system to make sure that the command is applied.
• sadmin enable
end-update(eu)
This command ends Update mode and activates Enabled mode.
• sadmin end-update/eu
event
This command configures the log targets (sinks) for generated events.
• sadmin event sink [eventname sinkname]
• sadmin event sink -a|-r { eventname | ALL } { sinkname | ALL }
features
This command enables, disables, or lists the features on an existing installation.
• sadmin features enable|disable|list featurename
help
This command provides information about basic commands.
• sadmin help [command]
help-advanced
This command provides information about advanced commands.

• sadmin help-advanced [command]
license
This command adds or displays licensing information.
• sadmin license add licensekey
• sadmin license list
list-solidified (ls)
This command lists the whitelisted files, directories, and volumes.
• sadmin list-solidified/ls [-l] [filename|directoryname|volumename]
list-unsolidified (lu)
This command lists the files, directories, and volumes that are not whitelisted.
• sadmin list-unsolidified/lu [filename|directoryname|volumename]
lockdown
This command disables the local command line interface. After lockdown, you can only issue the help, help-advanced, status,
version, and recover commands.
• sadmin lockdown
passwd
This command sets a password for the command line interface. If the password is set, you must verify the password before
executing critical commands. Using sadmin passwd -d command removes the password.
• sadmin passwd
• sadmin passwd -d
read-protect (rp)
This command displays or changes the read protection rules. You must specify complete file or directory names with this
command.
• read-protect/rp [-e | -i | -r ] PATH...
recover
This command recovers the local command line interface from locked down state.
• sadmin recover [-f]
ruleengine
This command specifies rules on various attributes of a process whose execution is undetermined. This enables the user to
allow, block, or monitor its execution. You can combine one or more unique attribute types in one rule using AND operator.
• sadmin ruleengine add allow processname command_line { matches | not matches } regex
• sadmin ruleengine add allow processname { command_line | user | parent_process_name | path } { equals | not
equals } string
• sadmin ruleengine add block processname command_line { matches | not matches } regex
• sadmin ruleengine add block processname { command_line | user | parent_process_name | path } { equals | not
equals } string
• sadmin ruleengine add monitor processname command_line { matches | not matches } regex

• sadmin ruleengine add monitor processname { command_line | user | parent_process_name | path } { equals | not
equals } string
• sadmin ruleengine remove allow processname command_line { matches | not matches } regex
• sadmin ruleengine remove allow processname { command_line | user | parent_process_name | path } { equals | not
equals } string
• sadmin ruleengine remove block processname command_line { matches | not matches } regex
• sadmin ruleengine remove block processname { command_line | user | parent_process_name | path } { equals | not
equals } string
• sadmin ruleengine remove monitor processname command_line { matches | not matches } regex
• sadmin ruleengine remove monitor processname { command_line | user | parent_process_name | path } { equals |
not equals } string
• sadmin ruleengine list
• sadmin ruleengine flush
skiplist
This command bypasses a path component from a feature to remove the protection applied by that feature. You can also define
skip rules to skip path components from the whitelist. Use caution and take advice from McAfee Support before applying skiplist
rules because doing so can affect the core functionality of the product and can make your system vulnerable to security threats.
• sadmin skiplist add -c|-d|-f|-i|-r|-s|-v pathname
• sadmin skiplist remove -c|-d|-f|-i|-r|-s|-v pathname
• sadmin skiplist list -c|-d|-f|-i|-r|-s|-v
• sadmin skiplist flush -c|-d|-f|-i|-r|-s|-v
solidify (so)
This command adds specified files in a directory or system volume to the whitelist.
• sadmin solidify/so
• sadmin solidify [filename|directoryname|volumename] [-q|-v]
status
This command displays the status of Application Control. You can view the operational mode, operational mode on system
restart, connectivity with McAfee ePO, access status, and whitelist status of the local CLI.
• sadmin status
trusted
This command identifies a local or remote share as a trusted file path, volume, or directory. You can include, exclude, remove,
list, or flush the trusted volumes or directories.
• sadmin trusted -e|-i|-r|-f|-l [pathname|volumename]
unsolidify (unso)
This command removes specified files from the whitelist.
• sadmin unsolidify [ -v ] [filename|directoryname|volumename]
updaters
This command adds, deletes, lists, or flushes programs from the list of authorized updaters.
• sadmin updaters add [-d|-n] binaryname
• sadmin updaters add [-p parent-binaryname] binaryname
• sadmin updaters add [-t rule-id] binaryname
• sadmin updaters add [-d] [-n] [-t rule-id] [-p parent-binaryname] binaryname

• sadmin updaters add [-l libraryname] binaryname
• sadmin updaters remove [-p parent-binaryname] binaryname
• sadmin updaters remove [-l libraryname] binaryname
• sadmin updaters remove -u username
• sadmin updaters list
• sadmin updaters flush
version
This command displays the version of Application Control that you have installed in your system.
• sadmin version
write-protect (wp)
This command write-protects specified files including the whitelisted files. You must specify complete file or directory names with
this command.
• sadmin write-protect -e|-i|-r pathname
• sadmin write-protect -f|-l
write-protect-reg (wpr)
This command write-protects specified registry keys including the whitelisted registry keys.
• sadmin write-protect-reg -e|-i|-r registrykeyname
• sadmin write-protect-reg -f|-l
Command short forms

You can use the short forms of the Application Control commands. These commands are interchangeable.
Command Short form
sadmin write-protect sadmin wp
sadmin write-protect-reg sadmin wpr
sadmin read-protect sadmin rp
sadmin solidify sadmin so
sadmin unsolidify sadmin unso
sadmin list-solidified sadmin ls
sadmin list-unsolidified sadmin lu
sadmin begin-update sadmin bu
sadmin end-update sadmin eu
Argument details
This table lists the commands with the supported arguments and their description. In the Argument column, the supported
arguments for the commands are listed in alphabetical order.

Argument details
Command Description
Argument
attr Always
-
authorizes
a
by
file
name.
This
is
a
deprecated
technique.
For
more
information
contact
McAfee
Support.
Configures
-
bypass,
b
restore,
list,
and
flush
rules
for
a
component
protected
using
the
Mangling
technique.
This
is
a
deprecated
technique.
For
more
information
contact
McAfee
Support.
Configures
-
bypass,
c
restore,
list,
and
flush

Command Description
Argument
rules
for
a
component
protected
using
the
Critical
Address
Space
Protection
technique.
Bypasses
-
from
f
full
crawl
attribute.
This
is
a
deprecated
technique.
For
more
information
contact
McAfee
Support.
Adds
-
ah
binary
to
MP
Compat
protection.
Configures
-
bypass,
i
restore,
list,
and
flush
rules
for
a
binary
using
the
Package
Control
feature.

Command Description
Argument
Bypasses
-
aj
binary
from
MP
Compat
protection.
Configures
-
bypass,
l
restore,
list,
and
flush
rules
for
a
component
using
the
Anti-
Debugging
technique.
This
is
a
deprecated
technique.
For
more
information
contact
McAfee
Support.
Configures
-
the
m
add,
remove,
list,
and
flush
rules
for
blocking
the
process
in
the
interactive
mode.

Command Description
Argument
Configures
-
the
n
bypass,
restore,
list,
and
flush
rules
for
a
component
using
the
mp-
nx
technique.
Includes
-
child
y
processes
for
a
component
to
be
bypassed
using
the
mp-
nx
technique.
This
argument
can
only
be
specified
with
the
-
n
argument.
Indicates
-
to
o
specify
the
DLL
module
name
for
a
specified

Command Description
Argument
process.
This
argument
can
be
used
with
-
p,
-
v,
and
-
i
arguments
On
the
Linux
platform,
use
this
argument
to
specify
the
parent
program
for
the
-
p
attribute.
Bypasses
-
from
p
process
context
file
operations
attribute.
Always
-
unauthoriz
u
by
file
name.
This
is
a
deprecated
technique.
For
more

Command Description
Argument
information
contact
McAfee
Support.
Bypasses
-
from
v
Forced
DLL
relocation
attribute.
auth Authorizes
-
a
a
binary
using
the
checksum
value.
Bans
-
ab
binary
using
the
checksum
value.
Specifies
-
the
c
checksum
value.
Flushes
-
all
f
authorized
or
banned
binaries.
Lists
-
all
l
authorized
and
banned
binaries.
Removes
-
the
r
authorized
or
banned
binaries.

Command Description
Argument
Includes
-
the
t
associated
tag
name
for
a
binary
to
be
banned.
Authorizes
-
au
binary
and
also
provides
updater
rights
when
used
with
the
-
a
and
-
c
arguments
begin-update (bu) Indicates

workflow-
to
id
specify
an
ID
while
switching
to
the
Update
mode.
This
ID
can
be
used
for
tracking
purposes
in
a
change

Command Description
Argument
manageme
for
ticketing
system.
Indicates
comment
to
use
a
descriptive
text
for
the
workflow
ID.
cert Specifies
-
the
c
certificate
content
as
trusted.
Lists
-
all
d
details
of
the
issuer
and
subject
of
the
certificates
added
to
the
system.
Provides
-
updater
u
rights
to
a
certificate
that
is
added
as
a
trusted
certificate
or
list

Command Description
Argument
the
trusted
certificates
with
updater
rights.
check Fixes
-
any
r
inconsisten
that
are
encountere
config Appends
-
the
a
configuratio
values.
diag Applies
-
the
f
diagnosed
configuratio
changes
for
the
restricted
programs,
such
as
winlogon.e
and
svchost.exe
disable NA
enable NA
end-update (eu) NA
event Adds
-
sinks
a
to
the
specified
event.
Removes
-
sinks
r
from
the
specified
event.

Command Description
Argument
features Lists
-
all
d
features
(including
the
hidden
features).
For
more
information
contact
McAfee
Support.
help NA
help-advanced NA
license NA
list-solidified (ls) Lists

-
details
l
of
the
whitelisted
files.
list-unsolidified (lu) NA
lockdown NA
passwd Removes
-
the
d
password
for
using
Application
Control.
read-protect (rp) Excludes

-
specific
e
component
from
a
read-
protected
directory,
or
volume.
Flushes
-
all
f
component
from

Command Description
Argument
read
protection.
Includes
-
files,
i
directories,
or
volumes
for
read
protection.
Lists
-
the
l
read-
protected
component
Removes
-
read
r
protection
applied
to
files,
directories,
or
volumes.
recover Forcefully
-
closes
f
the
McAfee
ePO
command
and
recover
the
local
CLI.
ruleengine A
allow
rule
type
for
adding
or
removing
the
allow
rules
on
any
attribute
of

Command Description
Argument
a
process.
Ablock
rule
type
for
adding
or
removing
the
block
rules
on
any
attribute
of
a
process.
Amonitor
rule
type
for
adding
or
removing
the
monitor
rules
on
any
attribute
of
a
process.
This
command_l
attribute
type
specifies
the
command-
line
argument
to
execute
a
process.
A
rule
type
can

Command Description
Argument
be
applied
to
either
allow,
block,
or
monitor
a
process
when
executed
using
command_
This
user
attribute
type
specifies
the
user
who
tries
to
execute
a
process.
A
rule
can
be
applied
to
either
allow,
block,
or
monitor
the
process
started
by
a
user.
This
parent_pr
attribute
type
specifies
a
particular
process
which

Command Description
Argument
a
parent
process
tries
to
execute.
A
rule
can
be
applied
to
either
allow,
block,
or
monitor
its
execution
when
a
parent
process
tries
to
execute
it.
This
path
attribute
type
denotes
the
path
where
the
process
resides
whose
execution
is
undetermin
A
rule
can
be
applied
to
allow,
block,
or
monitor
the

Command Description
Argument
process
execution
from
that
path.
Aregex
regular
expression
of
one
or
more
characters
that
defines
the
search
pattern.
It
describes
a
grammar
that
can
be
constructed
based
on
ECMA
script.
See
this
article
for
more
details.
Specifies
string
a
string
of
characters.
skiplist Skips
-
path
c
component
from
the
monitoring
feature.
This
command

Command Description
Argument
is
applicable
to
Application
Control
only
in
Update
mode
where
changes
are
tracked.
User
mode
paths
and
paths
with
volume
name
do
not
work
with
this
command.
Text
added
with
this
command
is
treated
as
complete
component
For
example,
text
can
start
with
a
slash
(/)
and
end
with
a
slash
(\),

Command Description
Argument
dot
(.),
or
null
character.
No
events
are
generated
for
files
that
contain
the
specified
text.
Also,
the
whitelist
is
not
updated
for
such
paths.
Skips
-
path
d
component
from
write
protection
to
remove
write
protection
applied
to
all
files
in
that
path.
User
mode
paths
and
paths
with
volume
name
do
not

Command Description
Argument
work
with
this
command.
Text
added
with
this
command
is
treated
as
complete
component
For
example,
text
can
start
with
a
forward
slash
(/)
and
end
with
a
backward
slash
(\),
dot
(.),
or
null
character.
Skips
-
path
f
component
from
file
operations
and
the
script-
auth
feature.
User
mode
paths
and
paths

Command Description
Argument
with
volume
name
do
not
work
with
this
command.
Text
added
with
this
command
is
treated
as
substring
in
a
path.
No
events
are
raised
and
the
whitelist
is
not
updated
for
the
skipped
path
component
Also,
script
execution
control
does
not
work
for
paths
added
with
this
command.
Skips
-
path
i
component

Command Description
Argument
from
file
operations
using
the
ignore
path
list.
This
works
similar
to
the
sadmin
add
-
f
command.
User
mode
paths
and
paths
with
volume
name
do
not
work
with
this
command.
When
the
path
component
are
specified
on
Windows
64-
bit
platforms,
even
the
deny-
exec
feature
is
skipped.

Command Description
Argument
Skips
-
registry
r
path
component
from
write
protection
for
registry
to
remove
write
protection
applied
on
the
registry
paths.
Text
added
with
this
command
is
treated
as
complete
component
For
example,
text
can
start
with
a
forward
slash
(/)
and
end
with
a
backward
slash
(\),
dot
(.),
or
null
character.

Command Description
Argument
Removes
-
files
s
present
under
the
specified
path
component
and
subdirector
from
the
whitelist.
Network
path
names
cannot
be
specified
with
this
command.
Volume
relative
rules
can
also
be
specified
using
*
\<vol_rel_na
Bypasses
-
volumes
v
from
attaching
to
Application
Control.
File
system,
such
as
NTFS
or
FAT,
can
also
be
specified
with

Command Description
Argument
this
argument.
When
you
specify
a
volume
name
with
this
argument,
Application
Control
is
not
attached
to
that
volume.
Script-
auth
and
deny-
exec
features
are
also
not
effective
on
the
specified
volume.
Componen
in
that
volume
are
allowed
to
execute
on
the
system.
You
can
specify
a
path
component
using
user

Command Description
Argument
mode
volume
names,
such
as
C:
and
D:.
Also,
device
names,
such
as
\device
\harddiskvo
and
file
systems,
such
as
NTFS
and
FAT,
can
also
be
specified.
solidify (so) Suppresses

-
all
q
output
except
for
errors.
Displays
-
all
v
processed
component
status NA
trusted Excludes
-
one
e
or
more
specified
paths
to
the
directories
or
volumes
from

Command Description
Argument
a
list
of
trusted
directories
or
volumes.
Removes
-
all
f
directories
and
volumes
from
the
trusted
rule.
Adds
-
one
i
or
more
specified
paths
to
the
directories
or
volumes
as
trusted
directories
or
volumes.
Lists
-
all
l
trusted
directories
and
volumes.
Removes
-
the
r
specified
directories
or
volumes
from
the
trusted
rule.

Command Description
Argument
Provides
-
updater
u
rights
to
all
binaries
and
scripts
in
the
trusted
directories
or
volumes.
unsolidify (unso) Displays

-
all
v
processed
component
updaters Excludes
-
the
d
child
processes
of
a
binary
file
to
be
added
as
an
updater
from
inheriting
the
updater
rights.
Includes
-
the
l
library
name
for
an
execution
file
to
be
added
as
an

Command Description
Argument
updater
(for
Windows).
Disables
-
event
n
logging
for
a
file
to
be
added
as
an
updater.
Adds
-
ap
file
as
an
updater
only
when
it
is
started
by
specified
parent
process.
Performs
-
these
t
operations:
•
Includes
the
tags
for
a
file
to
be
added
as
an
updater.
•
Adds
a
user
with

Command Description
Argument
a
tag
name
as
an
updater.
Adds
-
au
user
as
an
updater
(for
Windows).
version NA
write-protect (wp) Excludes

-
specific
e
component
from
a
write-
protected
directory
or
volume.
Flushes
-
all
f
component
from
write
protection.
Write-
-
protects
i
files,
directories,
or
volumes.
Lists
-
the
l
write-
protected
component
Removes
-
write
r
protection
applied
to
files,

Command Description
Argument
directories,
or
volumes.
write-protect-reg (wpr) Excludes

-
one
e
or
more
registry
keys
from
write
protection.
Flushes
-
all
f
registry
keys
from
write
protection.
Flushing
the
registry
keys
from
write
protection
removes
all
write
protection
rules
applied
to
the
registry
keys.
Write-
-
protects
i
registry
keys.
Lists
-
all
l
write-
protected
registry
keys.
Removes
-
write
r
protection

Command Description
Argument
from
one
or
more
registry
keys.

COPYRIGHT
Copyright © 2020 McAfee, LLC
McAfee and the McAfee logo are trademarks or registered trademarks of McAfee, LLC or its subsidiaries in the US and other countries. Other
marks and brands may be claimed as the property of others.

Mcafee Application Control 8.2.0 - Windows Product Guide 3-18-2020 PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Mcafee Application Control 8.2.0 - Windows Product Guide 3-18-2020 PDF

Încărcat de

Drepturi de autor:

Formate disponibile

McAfee Application Control 8.2.

Using Application Control 11

McAfee Application Control 8.2.0 - Windows Product Guide 3

Deploying Application Control in Observe mode 84

4 McAfee Application Control 8.2.0 - Windows Product Guide

Maintaining your system with McAfee ePO 100

McAfee Application Control 8.2.0 - Windows Product Guide 5

Maintaining your system in standalone mode 109

Using the command-line interface 121

6 McAfee Application Control 8.2.0 - Windows Product Guide

McAfee Application Control 8.2.0 - Windows Product Guide 7

Protection against threats

Advanced memory protection

8 McAfee Application Control 8.2.0 - Windows Product Guide

How it works in a managed environment

How it works in a standalone environment

McAfee Application Control 8.2.0 - Windows Product Guide 9

10 McAfee Application Control 8.2.0 - Windows Product Guide

Enabled mode in a standalone environment

Enabled mode in a managed environment

McAfee Application Control 8.2.0 - Windows Product Guide 11

Switching between modes

Enabling the software using McAfee ePO

Before you begin

12 McAfee Application Control 8.2.0 - Windows Product Guide

Create the whitelist

2. Verify that the drive or volume is whitelisted.

Place Application Control in Enabled mode

3. Verify that Application Control is in Enabled mode: sadmin status.

McAfee Application Control 8.2.0 - Windows Product Guide 13

Use the command-line interpreter in a standalone environment

Methods for allowing execution of files

14 McAfee Application Control 8.2.0 - Windows Product Guide

Checks that Application Control runs for a file

Precedence Check Description

3 TIE reputation Important: Reputation information is available only in a McAfee

McAfee Application Control 8.2.0 - Windows Product Guide 15

7 McAfee GTI reputation Important: Reputation information is available only in a McAfee

16 McAfee Application Control 8.2.0 - Windows Product Guide

14 Whitelist Application Control checks the whitelist.

Allow or block an executable file

File and certificate reputation

McAfee Application Control 8.2.0 - Windows Product Guide 17

Communication with TIE server and McAfee GTI.

Reputation values received from sources

Values from TIE server

Values from McAfee GTI

McAfee GTI score for

known_clean 99 Known trusted

analysed_clean, assumed_clean 85 Most likely trusted

raiden_analyzed_clean, noise_clean 70 Might be trusted

assumed_dirty, assumed_dirty2 30 Might be malicious

assumed_dirty3, assumed_dirty4 15 Most likely malicious

18 McAfee Application Control 8.2.0 - Windows Product Guide

pup, trojan, virus, app 1 Known malicious

Not available 0 Not set

Values from Application Control

McAfee ePO workflow

McAfee Application Control 8.2.0 - Windows Product Guide 19

1. Check if an explicit ban rule exists for the file.

How reputation is computed

20 McAfee Application Control 8.2.0 - Windows Product Guide

Change file reputation