What naming convention should I use to organize my scans?
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 |
|---|---|
| Compliance / Regulatory |
| Business Unit / Department |
| Data Sensitivity / Risk Tier |
| Network Topology / Geography |
| Scan Frequency / Trigger Type |
| Remediation Playbook |
| Incident Response / Ad-Hoc |
[SCOPE] — Regulatory Framework, Department, or Region
Example Values |
|---|
|
|
|
|
[TARGET_TYPE] — Type of Data Store Being Scanned
Code | Target Type |
|---|---|
| Windows Endpoints |
| macOS Endpoints |
| Linux Endpoints |
| SQL / Relational Databases |
| Oracle Databases |
| Network File Shares (SMB/NFS) |
| Microsoft 365 (OneDrive, SharePoint, Exchange) |
| AWS S3 Buckets |
| Box Cloud Storage |
| Google Drive |
| Historical / Archive Repositories |
[CADENCE] — Scan Frequency or Trigger
Code | Meaning |
|---|---|
| Runs every day (typically incremental/delta) |
| Runs once per week |
| Runs once per month |
| Runs every quarter |
| Runs during scheduled maintenance window |
| Ad-hoc / manually triggered |
[ACTION] — Automated Playbook or Response (Optional)
Code | Meaning |
|---|---|
| Auto-quarantine flagged files |
| Auto-redact sensitive findings |
| Alert data custodian only |
| Read-only risk mapping, no file changes |
| Full automated remediation |
Example Scan Names
Scan Name | Description |
|---|---|
| Quarterly read-only SQL database scan for PCI-DSS compliance |
| Weekly Windows endpoint scan for HIPAA PHI, notifies custodian |
| Daily incremental HR network file share scan |
| Monthly Microsoft 365 scan for Finance department |
| Daily Crown Jewels Windows endpoint scan with auto-quarantine |
| Monthly general corporate file share baseline scan |
| Weekly EU-West S3 scan (GDPR sovereign, audit only) |
| Off-peak US-East file share scan with auto-remediation |
| Daily delta/incremental file share scan across all departments |
| Weekly deep archive scan with OCR during off-peak window |
| On-demand public S3 bucket scan with auto-quarantine playbook |
| 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.
- Example:
COMP-PCI-DB-SQL-Quarterly-AuditOnly-v2
- Example:
- Environment Prefix: In multi-environment deployments, prefix with
PROD-,STAGING-, orDEV-to distinguish environments - Example:
PROD-COMP-PCI-DB-SQL-Quarterly
- Example:
- Agent Pool Alignment: The scan name should directly correspond to a matching Agent Pool name.
- Example: Scan
GEO-EU-West-CLOUD-S3-Weeklymaps to Agent PoolGEO-EU-West-AgentPool
- Example: Scan
- Ownership Tag: Append the responsible team or custodian abbreviation as a suffix where ownership tracking is required.
- Example:
DEPT-HR-FS-Daily-[HR-OPS]
- Example: