Add Exclusion or Add Executable
- Last UpdatedApr 22, 2019
- 2 minute read
Add Exclusion or Add Executable
Add or edit an executable to exclude from Access Protection at the policy level — or include or exclude an executable from Access Protection at the rule level.
When specifying exclusions and inclusions, consider the following:
- You must specify at least one identifier: File name or path, MD5 hash, or Signer.
- If you specify more than one identifier, all identifiers apply.
- If you specify more than one identifier and they don't match (for example, the file name and MD5 hash don't apply to the same file), the exclusion or inclusion is invalid.
- Exclusions and inclusions are case insensitive.
- Wildcards are allowed for all except MD5 hash.
- Access Protection exclusions don't apply to the Windows Services subrule type.
| Option | Definition | |
|---|---|---|
| Name | Specifies the name that you call the executable. This field is required with at least one other field: File name or path, MD5 hash, or Signer. | |
| Inclusion status | Determines the inclusion status for the executable.
Inclusion status only appears when adding an executable to a rule or the target for the Processes subrule. | |
| File name or path | Specifies the file name or path of the executable to add or edit. Click Browse to select the executable. The file path can include wildcards. | |
| MD5 hash | Indicates the (32-digit hexadecimal number) MD5 hash of the process. | |
| Signer | Enable digital signature check — Guarantees that code hasn't been changed or corrupted since it was signed with cryptographic hash. If enabled, specify:
| |
| Notes | Provides more information about the item. |
Related Links
- Add Rule or Edit Rule
Add or edit user-defined Access Protection rules.
- Add Subrule or Edit Subrule
Add or edit user-defined Access Protection subrules.
- Targets
Specify the inclusion status and definition for an Access Protection subrule target.