Exclusions
All exclusions related to the policy are created using this feature.
Exclusion Setting | Description |
---|---|
Application Control Exclusion | Adding an application control exclusion allows application changes and additions to the specified folders. For Windows, use an absolute path, including the drive letter. Example for Windows: C:\Application |
External Device Exclusion List | Adding an external device exclusion allows the USB mass storage device to connect to a device.
|
Memory Violation Exclusion | Adding a memory violation exclusion allows the specified file to run or be installed on any device assigned to the policy. The memory violation exclusion uses a relative file path. Example for Windows: \Application\Subfolder\application.exe Example for macOS (without spaces): /Applications/SampleApplication.app/Contents/MacOS/executable Example for macOS (with spaces): /Applications/Sample Application.app/Contents/MacOS/executable See Wildcards in memory violation exclusions for more information. |
Policy Safe List | Adding a policy safe list exclusion means all agents assigned to the policy will treat the file as safe, even if BlackBerry ranks it as unsafe or abnormal. This lets you allow a file to a group of devices but not for the rest of your organization.
|
Script Exclusion | Adding a script exclusion allows scripts to run from the specified folder, including subfolders. Use the relative path to the folder. Example for Windows: \Application\Subfolder\ |
Threat Exclusion | Adding a threat exclusion means the folder is excluded from background threat detection and file watcher. This includes subfolders. For Windows, use an absolute path, including the drive letter. For macOS, use a relative path, escaping any spaces in the path. Example for Windows: C:\Application Example for macOS (without spaces): /Applications/SampleApplication.app Example for macOS (with spaces): /Applications/Sample\ Application.app |