Security Guide for Private Investigation Service

1. Hardening the Declarative Data Perimeter

In the investigative sector, the baseline assumption is that no field operative or analyst should have access to a case file unless explicitly assigned. To enforce this, Organization-Wide Defaults (OWD) for the primary operational objects must be set to strictly Private. This creates a zero-trust foundation. Access is then systematically opened up via a strict vertical Role Hierarchy. A Senior Investigator can view the `Investigation_Case__c` records of their direct subordinate field operatives, but lateral visibility between operatives in different units remains cryptographically and declaratively blocked. We construct Permission Set Groups to manage field-level security, ensuring operatives only see the fields required for their phase of the investigation.

Visualizing the Baseline Access Control Topology

2. Dynamic Declarative Record Routing

An investigation is highly dynamic; a case transitioning from background research to active surveillance requires immediate realignment of access privileges. We orchestrate this using Salesforce Flow. When an `Investigation_Case__c` record updates its status to 'Active Surveillance', a record-triggered Flow executes asynchronous evaluation logic. It automatically provisions access to a targeted Public Group (e.g., 'Surveillance Team Alpha') by generating the required sharing records, while simultaneously revoking access from the initial background research group. This ensures adherence to the principle of least privilege throughout the investigation lifecycle without requiring manual administrative intervention.

Automated Recalibration Architecture

3. Advanced Cryptography using Salesforce Shield Platform Encryption

Protecting Personally Identifiable Information (PII) such as Social Security Numbers, financial assets, and informant identities requires robust cryptographic controls at rest. We implement deterministic AES-256 encryption via Salesforce Shield Platform Encryption for highly sensitive structured fields, allowing field operatives to query records securely while ensuring the database layer stores only ciphertext. For unstructured data like uploaded surveillance photos or forensic financial documents, we employ probabilistic encryption. Furthermore, implementing a Bring Your Own Key (BYOK) model allows the firm to maintain strict control over Tenant Secrets, instantly destroying the key material if a systemic breach is detected, thereby cryptographically shredding the underlying data.

End-to-End Cryptographic Flow

4. Threat Prevention via Shield Event Monitoring

Malicious actors or compromised insiders often exhibit specific digital footprints before exfiltrating data, such as querying an abnormally high volume of contact records or exporting large matrix reports. We achieve comprehensive visibility into these behaviors via Salesforce Shield Event Monitoring. By leveraging the API to query the `EventLogFile` object, we capture 40+ granular event types—including `ReportEvent`, `ApiQuery`, and `LoginEvent`. This raw telemetry data is then ingested into a third-party Security Information and Event Management (SIEM) tool for real-time anomaly detection, allowing security teams to intercept a rogue investigator attempting to download a client list before departing the firm.

Event Telemetry Ingestion Architecture

5. Matrixed Visibility using Apex Managed Sharing

In high-stakes private investigation operations, standard declarative sharing is occasionally insufficient for managing complex conflicts of interest. When an analyst requires temporary access to an `Investigation_Case__c` record outside their standard Role Hierarchy, we utilize Apex Managed Sharing. An Apex Trigger executes complex business logic to verify conflict-of-interest clearance, explicitly running via the with sharing keyword to enforce the current user's baseline context. Upon validation, the system executes a DML insert operation into the `Investigation_Case__Share` table. Crucially, we stamp this share record with a custom `RowCause` (e.g., `Conflict_Cleared__c`), providing compliance auditors with explicit, immutable justification for why access was granted.

Programmatic DML Sharing Execution

6. Applied Threat Modeling and Mitigation Scenarios

The architectural concepts outlined above provide theoretical resilience, but their true value is demonstrated in neutralizing active threats targeting Professional Services and Private Investigation operations. Below are the top five threat vectors facing the industry and exactly how this Salesforce architecture mitigates them.