Antivirus Exclusions for the Stairwell Forwarder

Exclude three Stairwell paths from your endpoint protection software, so the two are not competing to read the same files.

Your antivirus and the Stairwell forwarder both want to read every file on the machine, and left alone they will read each other's work. Excluding three Stairwell paths from real-time scanning stops that contention. This applies on both Windows and macOS; only the paths differ.

This is worth doing rather than optional. Customers report a substantial improvement in file scanning performance after adding these exclusions in Microsoft Defender on Windows, and the same contention exists on the Mac. If the forwarder feels heavy on a fleet, this is the first thing to check, before performance tuning or anything else.

What to exclude

Windows

ComponentPath
Forwarder data directoryC:\ProgramData\Stairwell
Forwarder kernel driverC:\Windows\System32\drivers\SWAgent.sys
Forwarder processC:\Program Files\Stairwell\SwellService\SwellService.exe

macOS

ComponentPath
Forwarder data directory/Library/Application Support/Stairwell
Forwarder application/Applications/Inception Forwarder.app
Forwarder system extension/Library/SystemExtensions/*/com.stairwell.Inception.ProcessMonitor.systemextension

On macOS, the system extension is the process that does the work. Its running executable is:

/Library/SystemExtensions/<UUID>/com.stairwell.Inception.ProcessMonitor.systemextension/Contents/MacOS/com.stairwell.Inception.ProcessMonitor

macOS chooses the <UUID> folder when it activates the extension, so it differs from Mac to Mac and changes when the forwarder is upgraded. Exclude it with a wildcard, by process name, or by code signature (see below), rather than copying the path from one machine.

Both Application Support and Inception Forwarder.app contain a space. Enter the paths exactly as shown, and do not escape the space with a backslash unless your vendor's documentation says to.

Two details that decide whether it works

Include subfolders on the directory exclusions. A policy that excludes the data directory but not what is under it does very little, since that is where the work happens. On macOS the same goes for Inception Forwarder.app, which is a folder with the executables inside it.

Exclude from on-access and real-time engines specifically. A scheduled-scan exclusion does not address the contention, because the contention is real-time.

Other antivirus vendors

Some vendors require a wildcard or trailing asterisk on path exclusions:

C:\ProgramData\Stairwell\*
/Library/Application Support/Stairwell/*

On macOS, some vendors also let you exclude by code signature instead of by path. If yours does, the forwarder is signed with Apple Team ID 677UQVFGY8 (Stairwell, Inc.), and the system extension's bundle identifier is com.stairwell.Inception.ProcessMonitor. A signature exclusion keeps working when the extension's UUID folder changes on upgrade, which a path exclusion does not.

Check your vendor's documentation for the exact format. A path exclusion in the wrong syntax is usually accepted without complaint and silently matches nothing, which looks identical to having made no change at all. If performance does not improve after applying these, suspect the syntax before suspecting the advice.

Does this create a blind spot?

Not in the sense that matters. You are excluding Stairwell's own working directory and binaries from your antivirus, not excluding anything the forwarder collects. Stairwell continues to collect and analyze files across the machine exactly as before, and your antivirus continues to protect everything except the three paths for your platform.

What should I read next?


Did this page help you?