Exclusions Rules

Click the folder icon in Vallum main window’s toolbar to display Vallum Exclusions View. This view lists all managed exclusions.
This view is almost empty in default configuration, it contains only hardcoded entries.
An exclusion is made of an absolute path or part of it, and a rule “pass” or “block”.
When an unmanaged app makes a connection, Vallum searches a match in Exclusions paths. If the app matches an exclusion, it will be passed or blocked accordingly. The app will not appear in main app view, the exclusion rule will be applied silently. If an app matches more than one exclusion then the first matched exclusion is the one that wins.
Exclusions can be reordered dragging and dropping them inside the table. Their order will affect filtering, so be careful. Hardcoded entries cannot be edited, moved, deleted or overridden.
Hardcoded entries may change during Vallum development. Currently the only hardcoded entry is “/usr/bin/whois”, which is needed to get IP addresses whois records.
Exclusions are useful to reduce Vallum verbosity and to reduce Notification alerts. For example you can set entire directories or volumes as passed or blocked to avoid Notification alerts. Apps matching an exclusion are ignored by main Vallum apps view to avoid crowding the apps view.
A managed app will never be matched against an exclusion. Exclusions has effect only on unmanaged apps. Exclusions are overridden by rules defined in Apps view. So, for example, if an app is set as passed in Apps view but falls within a path belonging to a blocking exclusion, then that app will be passed.
To create an exclusion click the gear button on right top of Exclusions view and click “Add New Exclusion”. A drop-down view will appear, here you have to configure your exclusion. Type the path (or click the “…” button to browse your files) and select “pass” or “block” then add it. Another way to create an exclusion is to drag a directory icon from the OS X Finder to Vallum Exclusions view, and then set its parameters.