What naming convention should I use to organize my scans?

This article provides sample naming conventions tailored for Spirion Sensitive Data Platform (SDP) scan organization.

Here is a sample naming convention standard tailored for Spirion Sensitive Data Platform (SDP) scan organization:

Standard Scan Naming Convention

Convention Format

[CATEGORY]-[SCOPE]-[TARGET_TYPE]-[CADENCE]-[ACTION]

Each segment is separated by a hyphen (-) and uses UPPERCASE for category codes and PascalCase or descriptive labels for scope/target details.

Segment Definitions & Allowed Values

[CATEGORY] — Primary Grouping Framework

Code	Meaning
COMP	Compliance / Regulatory
DEPT	Business Unit / Department
TIER	Data Sensitivity / Risk Tier
GEO	Network Topology / Geography
CADENCE	Scan Frequency / Trigger Type
ACTION	Remediation Playbook
IR	Incident Response / Ad-Hoc

[SCOPE] — Regulatory Framework, Department, or Region

Example Values
PCI, HIPAA, GDPR, CCPA
HR, Finance, Legal, Engineering, Executive
US-East, EU-West, APAC
T1 (Crown Jewels), T2 (Sensitive), T3 (General)

[TARGET_TYPE] — Type of Data Store Being Scanned

Code	Target Type
EP-WIN	Windows Endpoints
EP-MAC	macOS Endpoints
EP-LNX	Linux Endpoints
DB-SQL	SQL / Relational Databases
DB-ORA	Oracle Databases
FS	Network File Shares (SMB/NFS)
CLOUD-O365	Microsoft 365 (OneDrive, SharePoint, Exchange)
CLOUD-S3	AWS S3 Buckets
CLOUD-BOX	Box Cloud Storage
CLOUD-GDrive	Google Drive
ARCHIVE	Historical / Archive Repositories

[CADENCE] — Scan Frequency or Trigger

Code	Meaning
Daily	Runs every day (typically incremental/delta)
Weekly	Runs once per week
Monthly	Runs once per month
Quarterly	Runs every quarter
OffPeak	Runs during scheduled maintenance window
OnDemand	Ad-hoc / manually triggered

[ACTION] — Automated Playbook or Response (Optional)

Code	Meaning
Quarantine	Auto-quarantine flagged files
Redact	Auto-redact sensitive findings
Notify	Alert data custodian only
AuditOnly	Read-only risk mapping, no file changes
AutoRemediate	Full automated remediation

Example Scan Names

Scan Name	Description
COMP-PCI-DB-SQL-Quarterly-AuditOnly	Quarterly read-only SQL database scan for PCI-DSS compliance
COMP-HIPAA-EP-WIN-Weekly-Notify	Weekly Windows endpoint scan for HIPAA PHI, notifies custodian
DEPT-HR-FS-Daily	Daily incremental HR network file share scan
DEPT-Finance-CLOUD-O365-Monthly-Notify	Monthly Microsoft 365 scan for Finance department
TIER-T1-EP-WIN-Daily-Quarantine	Daily Crown Jewels Windows endpoint scan with auto-quarantine
TIER-T3-FS-Monthly-AuditOnly	Monthly general corporate file share baseline scan
GEO-EU-West-CLOUD-S3-Weekly-AuditOnly	Weekly EU-West S3 scan (GDPR sovereign, audit only)
GEO-US-East-FS-OffPeak-AutoRemediate	Off-peak US-East file share scan with auto-remediation
CADENCE-Delta-FS-Daily	Daily delta/incremental file share scan across all departments
CADENCE-Deep-ARCHIVE-Weekly-OffPeak	Weekly deep archive scan with OCR during off-peak window
ACTION-AutoQuarantine-CLOUD-S3-OnDemand	On-demand public S3 bucket scan with auto-quarantine playbook
IR-Breach-EP-MAC-OnDemand-AuditOnly	Ad-hoc macOS endpoint scan triggered during incident response

Additional Governance Rules

Max Length: Keep scan names under 80 characters for readability in the Spirion Sensitive Data Platform console list view.
No Spaces: Use hyphens (-) exclusively as separators; never use spaces or underscores.
Versioning: For scans that are significantly revised, append a version suffix.
1. Example: COMP-PCI-DB-SQL-Quarterly-AuditOnly-v2
Environment Prefix: In multi-environment deployments, prefix with PROD-, STAGING-, or DEV- to distinguish environments
1. Example: PROD-COMP-PCI-DB-SQL-Quarterly
Agent Pool Alignment: The scan name should directly correspond to a matching Agent Pool name.
1. Example: Scan GEO-EU-West-CLOUD-S3-Weekly maps to Agent Pool GEO-EU-West-AgentPool
Ownership Tag: Append the responsible team or custodian abbreviation as a suffix where ownership tracking is required.
1. Example: DEPT-HR-FS-Daily-[HR-OPS]