Exclusions¶

An exclusion stops a piece of software from coming back into your inventory after you have removed it.

Without one, deleting a product achieves nothing for long: the agent finds the same software on the next scan and adds it again. The exclusion list is what the agent checks before adding anything.

Products → Exclusions.

Excluding something¶

The usual route is from the product itself. When you delete a product, tick exclude from future scans. It goes on the list and stays off your inventory.

You can also add one directly from the Exclusions page.

What an exclusion holds¶

Leaving the version empty excludes the software entirely. Filling it excludes only that version, and a different one will still be picked up, which is what you want when you are excluding a specific build rather than a product.

Write the reason. It is the only part of an exclusion that explains itself six months later, and an exclusion nobody can explain is the thing an auditor asks about.

Exclusions are per organization¶

An exclusion applies to the organization it was created in. Excluding something for one client does not exclude it for another.

Good and bad reasons to exclude¶

Good:

• software that was uninstalled and keeps being re-detected from a leftover directory
• a vendored copy of a library that is not actually executed
• a test or lab machine's software that you track elsewhere

Bad:

• a product with findings you do not want to look at. That is not an exclusion, it is hiding the finding, and Risk Exceptions is the mechanism that does it honestly, with a reason and an end date

The difference matters: an exclusion removes the software from the inventory, so it stops being counted at all. A risk exception leaves the finding in place, recorded and exported, and it expires.

Undoing one¶

Remove the exclusion from the list. The software reappears on the next agent report, with its findings.