The following table shows the specification for wildcard (*) to work in exclusions list.

File Extension List Exclusion

• When there is a wildcard in the File Extension List, exclusion will not work. For example, creating d*c to exclude a .doc will not work.
• When there is no wildcard in the File Extension List, exclusion works on Thin Agent.

Directory List Exclusion

• When there is a wildcard in the Directory List, exclusion works on Deep Security Virtual Appliance (DSVA). For example, creating c:\te*t\ to exclude c:\test\ will work.
• When there is no wildcard in the Directory List, exclusion works on Thin Agent.

UNC Exclusion

• When there is a wildcard in UNC (in Deep Security 9.0 SP1 P4 and Deep Security 9.5 only), exclusion works on DSVA. For example, \\192.168.0.1\t*st.txt created will exclude the test.txt EICAR when accessing 192.168.0.1.
• When there is no wildcard in UNC, exclusion works on Thin Agent.

File List Exclusion

• When there is a wildcard in the File List, it is only supported without a file path. For example, if c:\test\t*st.txt is created, file test under the c:\test folder cannot be excluded. If you need to add wildcard, t*st should be added.
• Whether or not wildcard is added in the File List, all exclusion works on DSVA.

For more information about wildcards, refer to the following links:

• Using wildcards for ESX names in an Event-Based Task
• Class Pattern