How to Use Scans Settings - Overview

This topic describes the various options under the Scan section of the "Scans Settings" page in Spirion Sensitive Data Platform.

Overview

Scans Settings is where you manage your settings for:

Scan Settings
Agent Settings
Remediation Settings
Notifications and Custom Notifications
Data Retention
Global Ignore Lists
Note: Changes to Scans Settings take effect the moment data is entered into any field.
If you wish to retain a copy of the original settings when making updates if you need to revert back to the previous settings.

How to Access Scan Settings

To access the Scan Settings screen, use the following steps:

From the left menu, click Settings.
Click Application Settings.
The "Scans Settings" page opens.
To view sections in Scans Settings:
1. Click a down arrow to expand a section.
2. Click an up arrow to collapse a section.

How the Scans Settings Page Differs From Other Settings Pages

Page	What it configures
Scans Settings (this page)	How the scanning/agent infrastructure behaves globally
Agents > Policies	Per-agent operational profiles (logging, polling, proxy)
Scans > Scans (All Scans page)	Individual scan definitions (what to scan, where, when)
Settings > User Management > Users & Roles	User management, roles, permissions

Bottom line: Scans Settings is the global configuration backbone of Spirion Sensitive Data Platform — it sets the environmental constraints and defaults that every scan, every Agent, and every data lifecycle process operates within.

How to Configure Scan Settings

To configure Scan Settings use the following steps:

From the left-side navigation menu click Settings > Application Settings > Scans Settings.
Click the down arrow to expand the Scan section.
Fill in the settings below for the appropriate sections - note that only some of these settings apply to Greyhound Agents (v13.0 and later).

Scan Section: Greyhound (v13+) Agent Settings

The sub-topics below describe the various scan settings. Before continuing note which settings apply to Greyhound Agents (version 13 and later) and which do not.

Use the table here as a reference.

Summary of which settings apply to Greyhound Agents (v13+)

Setting	Applies to Greyhound (v13.x)?	Reason
Minimum load when using distributed scanning (MB)	No	These are for the `job_queue` distribution model, which Greyhound Agents do not use.
Maximum load when using distributed scanning (MB)	No	These are for the `job_queue` distribution model, which Greyhound Agents do not use.
Minimum number of items when using distributed scanning	No	Same as above; Greyhound Agents process an assigned policy as a single unit of work.
Maximum number of items when using distributed scanning	No	Same as above; Greyhound Agents process an assigned policy as a single unit of work.
Results Streaming Chunk Size	Yes	Greyhound Agents also "batch" their findings before shipping them to the Ingress server to save bandwidth.
Delayed Policy Confirm	Yes	To prevent "thundering herd" issues, Greyhound Agents can delay their acknowledgment of a new policy.
Apply multiple rows locations actions during import	Yes	This is a Console-side setting. It affects how the server processes data, regardless of whether it came from a Windows, Mac, or Linux Agent.

Guidance for Mac/Linux Agents

If you are looking to "distribute" a scan across multiple Mac or Linux machines, the current best practice is to segment the Targets via Policies.

Example: Create one policy for "Linux Group A" to scan /var/log and another policy for "Linux Group B" to scan /home.

Because Greyhound Agents are designed for high-performance local scanning, they are optimized to handle their own file systems independently rather than acting as a distributed "worker bee" for a remote network share.