Legacy Settings

Some Scan Options which existed in Spirion Sensitive Data Manager are either unnecessary or have been replaced/improved with updated technology in Spirion Sensitive Data Platform. These settings are listed in this article.

The following settings do not exist in Spirion Sensitive Data Platform.

Analysis Type Settings

In legacy Sensitive Data Manager, these were used to tell the agent how to calculate and distribute work for the Postgres-based job_queue. In Spirion Sensitive Data Platform v13.6, discovery and load balancing are handled automatically by the platform orchestration.

Cloud Storage Analysis Type

"Cloud Storage Analysis Type" is not a setting in Spirion Sensitive Data Platform.

In Spirion Sensitive Data Manager this setting was used to define how the Agent should calculate work for repositories like Box, Dropbox, or early versions of OneDrive (for example, whether to count by files, bytes, or user accounts).

SharePoint Analysis Type

"SharePoint Analysis Type" is not a setting in Spirion Sensitive Data Platform.

This setting is specific to the legacy Spirion Enterprise (on-premises) console. In that older architecture, "Analysis Type" was used to choose between counting by items, bytes, or site collections.

How SharePoint is handled in Spirion Sensitive Data Platform v13.6

In Spirion Sensitive Data Platform v13.6, SharePoint (both On-Premises and SharePoint Online) is managed through a modern, unified interface that automates the scaling and discovery logic:

Cloud-Native Targets: For SharePoint Online, Spirion Sensitive Data Platform v13.6 connects via the Microsoft Graph API. The platform performs its own "Discovery" phase to map out site collections, libraries, and files. You no longer need to manually tell the system whether to "Count by Bytes" or "Count by Items"—the orchestration layer handles this automatically.
Target Scoping: Instead of an "Analysis Type" toggle, you define your scan's Scope within the Target Configuration. You can choose to scan:
- The entire SharePoint tenant.
- Specific Site Collections.
- Specific Document Libraries.
Work Distribution: For SharePoint On-Premises (scanned via a Windows Agent), the Spirion Sensitive Data Platform v13.6 Agent uses a more intelligent internal mechanism to balance the load. It avoids the "Worker Imbalance" issues of older versions by dynamically adjusting how it pulls tasks from the cloud console.

Gmail Analysis Type

"Gmail Analysis Type" is not a setting in Spirion Sensitive Data Platform.

Like the "Exchange Analysis Type" and "File System Analysis Type" settings mentioned previously, this terminology was exclusive to the legacy Spirion Enterprise (on-premises) console for managing Google Workspace scans.

Exchange Analysis Type

"Exchange Analysis Type" is not a setting in Spirion Sensitive Data Platform.

Like the "File System Analysis Type" setting, this terminology belongs to the older Spirion Enterprise (on-premises) architecture. In the modern SDP v13.6 cloud-native platform, the way Exchange is handled has been significantly redesigned for better performance and scalability.

File System Analysis Type

"File System Analysis Type" is not a feature in Spirion Sensitive Data Platform.

That specific terminology and the "Count by Bytes/Items" logic for file systems were part of the Spirion Enterprise (on-premises) console architecture.

Spirion Sensitive Data Platform uses modern cloud-native architecture; these functions have been redesigned and relocated:

1. Where the "Analysis" logic went

In Spirion Sensitive Data Platform v13.6, the "Magic Number" or "File Header" identification (the core of File System Analysis Type) is handled automatically by the Agent's Inspection Engine.

Auto-Identification: Modern agents are "content-aware" by default. They generally perform a level of header inspection to identify a file's true type without needing the manual "File System Analysis Type" toggle found in older versions.
File Filters: Instead of an "Analysis Type" setting, you now use Inclusion/Exclusion Filters within your Scan Configurations or Policies to define which extensions to target.

2. What happened to "Count by Bytes/Items"?

In the newer Spirion Sensitive Data Platform architecture (v13.0 and later), the way work is distributed has changed:

Metadata Discovery: Spirion Sensitive Data Platform scans typically perform a "Discovery" phase that automatically gathers metadata (including file size and item counts).
Automated Load Balancing: The cloud console and the modern Windows agents handle the distribution of work to the job_queue using internal logic that accounts for both the number of tasks and the data volume, eliminating the need for the user to manually choose a "Count by..." preference.

3. Key Differences in v13.x

If you are looking for this setting to troubleshoot a scan in v13.6, look for these equivalent areas instead:

Scan Profile / Policy: Check your File System settings to ensure the correct "Extensions" are included.
Performance Settings: Use the Agent Resource throttles if you are concerned about the "heavy" processing that "Count by Bytes" used to manage.
Advanced OCR/Decomposition: If your goal was deep inspection of renamed files, ensure your Decomposition and OCR settings are enabled in the Policy, as these will trigger deeper file analysis regardless of the extension.

File Identification & Advanced "Magic" Settings

In Spirion Sensitive Data Manager, you manually set how the Agent identified files. In Spirion Sensitive Data Platform, the inspection engine is content-aware by default.

Enable Advanced File Identification: (Replaced by automatic content inspection)
Analysis Type: E-Mail Attachment Compressed Files: (Specific legacy performance toggle)
Analysis Type: Included File Types: (Redundant in the modern Policy/Filter model)
Analysis Type: All Files: (Thorough mode now handled via general Policy depth)

Local "Client" Interface & User-Facing Settings

Spirion Sensitive Data Platform is a "Silent Agent" or "Service-Based" architecture.

The legacy concept of a user-interactive desktop client with its own ribbon and settings has been deprecated.

Show Status Window: (Agents now run as background services)
Show Results in Client: (All results are now shipped to the Cloud Console; there is no local "Results" grid for the end-user)
Integration with Windows Explorer: (Right-click "Search with Spirion" or "Shred with Spirion" context menus)
Check for Updates (UI Animation): (Updates are now managed via the console or software deployment tools)

Legacy Action & Remediation Settings

Spirion Sensitive Data Platform v13.6 uses Playbooks to automate actions.

Many manual "Action" checkboxes in the legacy policy have been moved into the Playbook engine.

Shred / Secure Delete: (Functionality exists in Playbooks, but the "Shred" button in the local UI is gone)
Quarantine (Local): (Replaced by centralized Cloud-coordinated Quarantine actions)
Identity Finder Vaults: (Legacy password-protected .idf results files)

Specialized Discovery Settings

Search Windows Profile Only: (Modern Target scoping allows you to define paths more flexibly without a dedicated "Profile" checkbox)
Compressed Files (Checkbox): (Functionality still exists but has been renamed and expanded into the Decomposition section of the Policy)

How this is handled in Spirion Sensitive Data Platform v13.6

In the modern SDP architecture, the approach to Exchange and Microsoft 365 scanning has changed:

API-Based Scanning: For Exchange Online (M365), SDP v13.6 typically uses the Microsoft Graph API. The "Dumpster" is treated as a specific sub-folder of the mailbox. Instead of a global "Include Dumpster" toggle, the platform's discovery engine maps the mailbox structure and follows the Target Scoping rules you define.
Target Scoping: In the SDP console under Targets, you can often refine what is scanned by targeting specific folders or using inclusion/exclusion filters. The legacy "Dumpster" checkbox has been deprecated in favor of these more flexible scoping tools.

If you are transitioning from Legacy to Spirion Sensitive Data Platform:

Check your Target Configuration: When setting up your Exchange or M365 Target, review the Inclusions/Exclusions section.
Search Profiles: If you previously relied on the "Include Dumpster" setting to find "hidden" sensitive data, ensure your Policy is applied to the entire mailbox target to capture all accessible sub-folders.

Summary: The "Include Dumpster Folder" checkbox is a legacy artifact from the Enterprise Console (SDM). In SDP v13.6, you manage the depth and scope of your email scans through Target Definitions and Scan Configurations.

Summary of the Shift

The transition from Sensitive Data Manager to Spirion Sensitive Data Platform represents a shift from Manual Management (where the admin tells the agent how to count and identify) to Automated Orchestration (where the platform performs discovery and distributes work based on its own internal metadata analysis).