Manage file and directory exclusions using wildcards
Last Modified: 2023-03-09 09:27:30 Etc/GMT
Affected Products
Languages:
This article is available in the following languages:
Trellix CEO, Bryan Palma, explains the critical need for security that’s always learning.
As per Gartner, "XDR is an emerging technology that can offer improved threat prevention, detection and response."
Trellix announced the establishment of the Trellix Advanced Research Center to advance global threat intelligence.
Trellix Advanced Research Center analyzes threat data on ransomware, nation-states, sectors, vectors, LotL, MITRE ATT&CK techniques, and emails.
After December 1, 2024, please log in to the Thrive Portal for support, knowledge articles, tools, and downloads. For information about using the Thrive Portal, view the Trellix Thrive Portal User Guide.
Manage file and directory exclusions using wildcards
Technical Articles ID:
KB88807
Last Modified: 2023-03-09 09:27:30 Etc/GMT Environment
Endpoint Security for Linux Threat Prevention (ENSLTP) 10.x
Summary
This article provides guidance on how to create file and directory exclusions with ENSLTP. Configure exclusions for ePolicy Orchestrator (ePO)-managed computers by following the steps below:
The sections below explain how to use these wildcards correctly. Single asterisk for file name or path exclusions To denote single directory names, use a single asterisk (*) wildcard. For example, the exclusion /data/name2/sub/ /data/backup/sub/ /data/abc.* NOTE: Don't use trailing backslashes for file name matches; doing so excludes the wrong items. To clarify this important point, examine the following two examples: /data/def/ The first exclusion is treated as a file name, and the second is treated as a directory.
Double asterisk for directory exclusions
When the policy is enforced on the system, the local command shows as follows for the above examples: ENSLTP 10.6.6 and later, including 10.7.x: ENSLTP 10.6.5 and earlier: 1 /data/*/sub/ Disabled readandwrite 2 /data/def/ Disabled readandwrite 3 /data/abc Not Applicable readandwrite The result is that "Exclude Subfolder" shows as "Not Applicable" for the exclusion item Double asterisks (**) allow a wider directory exclusion called a Multiple Depth Exclusion. These exclusions are where the same target folder name might occur multiple times in subdirectories originating from a common directory.
For example, a directory named "cache" can exist under one or more subdirectories at any depth under the
/data/user/jim/cache/ /data/admin/cache/ /data/user/family/a1/b2/cache/ The following example uses a double asterisk to exclude the contents of any directory named cache under the When the policy is enforced on the system, the local command shows as follows in the above example for the exclusion item ENSLTP 10.6.6 and later, including 10.7.x: ENSLTP 10.6.5 and earlier: 1 /data/**/cache/ Disabled readandwrite 2 /data/*/sub/ Disabled readandwrite 3 /data/def/ Disabled readandwrite 4 /data/abc Not Applicable readandwrite Question mark for file-type exclusions Use a question mark wildcard to denote single-character replacement within file-type strings. For example, you can use the question mark wildcard for any of the three characters below:
A?C ?BC When the policy is enforced on the system, the local command shows as follows in the above example for the exclusion item ENSLTP 10.6.6 and later, including 10.7.x: ENSLTP 10.6.5 and earlier: 1 /data/**/cache/ Disabled readandwrite 2 /data/*/sub/ Disabled readandwrite 3 /data/def/ Disabled readandwrite 4 /data/abc Not Applicable readandwrite 5 /data/time-? Not Applicable readandwrite 6 A?C Related Information
ENSLTP doesn't support For example, a default ENSLTP doesn't support regex Here's the list of default exclusions in ENSLTP:
Affected ProductsLanguages:This article is available in the following languages: |
|