Skip to content

EPP Exclusions

Exclusions tell the SenseOn antimalware component not to scan specific files, directories or processes. This page tells you about the available exclusion types and how each type works internally. It also helps you to select the correct type for your situation.

There are two kinds of file exclusion. They work differently:

  • Scanning exclusions (the Alert Exclusions list): the antimalware component does not scan the file at all. Thus, there is no detection and no alert.
  • Response exclusions: the antimalware component still scans and detects the file. But it gives access to the file, and it does not quarantine or block the file. On Windows, SenseOn still raises an alert and an observation. On macOS, SenseOn does not raise an alert or an observation.

ℹ Linux: The Linux sensor does not do antimalware scans. Thus, exclusions have no effect on Linux devices. But the configuration form accepts the settings without a warning.

💡 Where to configure exclusions: You configure exclusions in Device Configuration, in the Antimalware and Process Protection sections. You can scope them to specific device segments. For the steps to create segments and apply a configuration, refer to Endpoint Protection. If those sections show as locked, Endpoint Protection is not enabled for your organisation. Contact SenseOn to enable it.


Exclusion Types

Path Exclusions

A path exclusion excludes files or directories from scans by their path. You can use absolute paths. You can also use wildcard patterns with these characters:

  • * matches any sequence of characters, also across subdirectories.
  • ? matches zero or one character.

On Windows and macOS, the match is case-insensitive. On Windows, you can use UNC paths (for example, \\server\share\path\*).

On Windows, a path that ends in \ and has no wildcard (for example C:\MyApp\data\) excludes the whole folder. Always end a folder path with \. If you do not, a folder with a dot in its name, such as C:\My.App, counts as a single file.

Examples: - C:\MyApp\data\: excludes the whole folder (Windows) - C:\MyApp\data\*: excludes all files under that directory and its subdirectories - C:\MyApp\data\*.tmp$: excludes all .tmp files under that directory and its subdirectories - \\server\share\builds\*: network path exclusion - ?:\*\MyApp.exe: excludes MyApp.exe in any folder on any drive. It does not cover a file at the top of a drive, such as D:\MyApp.exe. To cover that file, add a separate ?:\MyApp.exe entry - M:\*: excludes everything on the M: drive. Use whole-drive exclusions as little as possible, because no file on that drive gets a scan

How patterns match

A pattern applies to the full path, and it does not have to reach the end of the path. Without an end marker, C:\MyApp\logs\*.log also excludes C:\MyApp\logs\a.log.old. To mean "end of the path", add $ at the end of the pattern. For example, C:\MyApp\logs\*.log$.

These characters have a special meaning in a pattern:

Character Meaning
* Any number of characters, including \
? Zero or one character
# Exactly one character
+ One or more characters
| Or, so a|b matches either
^ Start of the path
$ End of the path
> Any characters except /

⚠ Characters such as +, #, ^ and $ are not matched literally in a pattern. For example, C:\Program Files\Notepad++\* also excludes C:\Program Files\Notepadxx\a.exe, because + means "one or more characters". On Windows, to match the real name, use the plain folder path with a \ at the end (C:\Program Files\Notepad++\).

⚠ On Windows, only plain paths avoid locking entirely. The scanning engine itself processes a plain file path, or a folder path that ends in \. Thus, no file lock occurs.

The agent, not the scanning engine, matches a pattern that contains * or ?, and each UNC path. While the agent compares the path with the exclusion list, a short file lock can occur. For most workloads, you cannot see this effect. But for processes that quickly delete or create large numbers of files, it can cause temporary lock contention. On macOS, the agent matches each path exclusion.

If you cannot list the exact file paths, use a process exclusion on the tool that accesses the files. An example is a software management tool that deletes temporary files with dynamic names. Process exclusions bypass all file locks at the driver level. This applies to all files that the process accesses.


Environment Variables in Paths

⚠ Environment variables are not expanded in exclusions. The configuration form accepts entries such as %windir%\CCM\* or %TEMP%\MyApp\*. But the variable stays unresolved. Thus, the exclusion matches nothing. Write the full path as an alternative, for example C:\Windows\CCM\*.

To cover a location in the profile of each user, use a wildcard. For example, C:\Users\*\AppData\Local\Temp\* or C:\Users\*\AppData\Roaming\MyApp\*. This method assumes that the profiles use the default layout under C:\Users. If a profile moved to a different drive or path, that profile must have its own entry for that location.


Process Exclusions

A process exclusion excludes all files that a specific process accesses from on-access scans. This is the most effective solution when a process accesses a large number of files. Examples are build systems, backup agents, deployment tools and cleanup scripts.

When a process is in the exclusion list, the exclusion applies at the driver level. When that process accesses a file, there is no scan callback at all. Thus, there is no window for a file lock.

⚠ Process exclusions need the exact path of the program, and wildcards are not supported. A process exclusion matches the path of the process itself, not the files that it opens. You can save an entry that contains * or ?, and no error shows. But the entry never matches. Thus, the process is not excluded.

⚠ The process executable must be code-signed. The agent does a check of the signature before it registers the exclusion. You cannot use this method to exclude an unsigned executable, even if it is in the list.

⚠ Exclusions apply on next process start. If the process already runs when you add the exclusion, you must restart the process before the exclusion takes effect.

Examples: - C:\MyApp\bin\cleanup.exe - C:\Program Files\MyBuildTool\builder.exe

💡 Known issue: UNC paths sometimes do not match for process exclusions. The Windows kernel gives network paths to the sensor in NT device format, not in the UNC format that you configure. Thus, it is possible that an exclusion such as \\server\share\app\tool.exe does not match at runtime. As a workaround, try to add the exclusion with each of these alternative path prefixes, one at a time, until one works: - \Device\Mup\server\share\app\tool.exe, the most common form from the kernel - \Device\LanmanRedirector\server\share\app\tool.exe

Each entry must be the exact path of one executable, because process exclusions do not support wildcards. SenseOn will correct this issue in a future sensor release.


Hash Exclusions (SHA-1)

Use a response exclusion with a hash to suppress the response to detections for a specific file. This is useful for files that you know are safe, but that SenseOn can flag as suspicious. Examples are internal tools or custom binaries. Enter the hash as SHA-1.

Scanning exclusions (the Alert Exclusions list) do not support hashes.

⚠ macOS: a hash allows that file content at every path. If a response exclusion has a hash, files with that content get through in all locations. This is true even when the path in the same entry matches nothing. On macOS, a hash with no path has no effect. Always give the entry a path also. Treat the hash as if it applies to the whole device.

⚠ Hash exclusions are post-detection only. The antimalware component first scans the file. Then it does a check of the hash to decide if it suppresses the response to the detection. Thus, hash exclusions do not prevent the short file lock that occurs during the scan. The best use of hash exclusions is to suppress false positives on known-safe binaries. They are not a method to decrease lock contention.


Extension Exclusions

❌ Not supported. As a workaround, use path wildcards. For example, use C:\MyApp\logs\*.log$ to exclude .log files under a directory.


Choosing the Right Exclusion Type

Scenario Recommended type
A process deletes or modifies many files rapidly Process exclusion
A specific directory contains known-safe files Path exclusion (absolute path preferred)
A specific binary is flagged as a false positive Hash exclusion
You want to exclude files with a specific extension Path wildcard (for example C:\App\logs\*.ext$)
Mixed or dynamic paths, too many to list Process exclusion

Common Scenarios

A process is failing because SenseOn is locking files it tries to delete

This is expected behaviour. The antimalware component locks files for a short time during on-access scans. The recommended solution is a process exclusion on the process that deletes the files. This removes the file locks fully, and you do not have to list the file paths. When there are many paths or the paths are dynamic, it is also more robust than path exclusions.

Note: the process executable must be code-signed, or the exclusion has no effect.

Scanning is slowing down compilation on a build server

Use a process exclusion on the executable of the compiler or build tool. As an alternative, use a path exclusion with an absolute path on the build output directory. Do not use wildcard path exclusions on directories that have a high frequency of file access. Under load, the time windows for pattern matches can accumulate.

A known internal tool is being flagged as malware

To suppress the false positive, use a hash exclusion (SHA-1). If the tool gets frequent updates and the hash changes, talk about alternatives with support@senseon.io.


Key Limitations

  • Process exclusions require a signed executable: you cannot exclude unsigned binaries.
  • Process exclusions apply on next process start: changes do not apply to processes that already run.
  • Wildcard and UNC path exclusions have a small locking window on Windows: for frequent file deletion, it is better to use process exclusions, exact file paths or folder paths that end in \.
  • Process exclusions do not support wildcards: you can save an entry with * or ?, but it never matches.
  • Hash exclusions are post-detection only, and SHA-1 only: they suppress the action on a flagged file, but they do not prevent the scan or its file lock.
  • Environment variables are not expanded: the form accepts an entry such as %windir%\CCM\*, but the entry matches nothing. Use the full path. For locations in each user profile, use a C:\Users\*\... wildcard.
  • Extension exclusions are not available: as a workaround, use wildcard path patterns that end in $.