What are the standard naming conventions used for Assets?

In Spirion Sensitive Data Platform (SDP) and associated architecture standards, naming conventions for Assets apply across three primary contexts:

1. Data Assets & Targets in the SDP Platform
2. Infrastructure & Environment Resources
3. Database/API Asset Objects

1. Data Assets & Targets (Platform Discovery Assets)

When registering or organizing discovered Data Assets (endpoints, databases, cloud repositories, file shares) in the SDP Console, adopting a structured hierarchy is recommended so data custodians can easily search, filter, and assign governance rules:

$$\text{Format: } \mathbf{[ENV]-[REGION/LOCATION]-[ASSET_TYPE]-[DEPARTMENT/PURPOSE]}$$

Recommended Segment Standard:

• [ENV] — Environment Tier: PROD, STAGING, DEV, CORP
• [REGION/LOCATION] — Geographic / Data Center Location: US-EAST, EU-WEST, ONPREM-HQ, AWS-S3
• [ASSET_TYPE] — Target Category:
• • EP-WIN / EP-MAC / EP-LNX — Workstation & Server Endpoints
  • DB-SQL / DB-ORA / DB-PG — Relational Databases
  • FS-SMB / FS-NFS — Network File Shares
  • CLOUD-O365 / CLOUD-S3 / CLOUD-BOX — SaaS / Cloud Storage
• [DEPARTMENT/PURPOSE] — Business Unit or Data Scope: HR-Payroll, FIN-Contracts, R&D-SourceCode, Customer-PII

Examples:

• PROD-US-EAST-DB-SQL-CustomerData
• CORP-HQ-FS-SMB-HR-Payroll
• PROD-EU-WEST-CLOUD-S3-GDPR-Vault
• DEV-ONPREM-EP-WIN-LabWorkstations

2. SDP Environment & Infrastructure Asset Resources

For infrastructure assets (EKS/AKS Kubernetes clusters, S3 buckets, cloud databases) hosting the Spirion platform, Spirion follows a standardized resource naming convention:

$$\text{Format: } \mathbf{[Tenant][Subscription][Resource_Type][Environment_ID][Region]}$$

• Tenant Identifier (1 char): s (production spirionsaas.net), d (development tenant)
• Subscription Identifier (1 char): p (production), d (delivery), u (playground/UEBA)
• Resource Type (2 chars): k8 (Kubernetes cluster / EKS / AKS), s3 (S3 bucket), db (Database)
• Environment Name/ID: Free-form identifier spanning all resources in that environment (examples: p484)
• Region Identifier: Code denoting deployment region (examples: eus2 for East US 2, sa for South Africa, ca for Canada Central)

Example:

• spk8p484eus2 $\rightarrow$ Production Kubernetes cluster in East US 2 for environment p484.
• sps3p484eus2 $\rightarrow$ S3 storage bucket associated with the same environment.

3. Database & Code Asset Naming Standards

When interacting with Spirion's underlying schemas, API contracts, and database assets:

• T-SQL & C# / C++ Classes: Use PascalCase (examples: AssetTargetMap, UserPermission). No spaces or special characters except underscores.
• PostgreSQL Schema Objects: Use snake_case (examples: asset_object_id, created_at).
• JSON / YAML & REST API Fields: Use camelCase (examples: targetType, resultPermission).
• Constants & System Keys: Use SNAKE_CASE_CAPITALS (examples: MAX_RETRY_COUNT).