Data Security & Evidentiary Integrity

Exhibit In-Sight is engineered specifically to withstand the rigors of the Canadian judicial system. We recognize that evidentiary continuity, jurisdictional data sovereignty, and endpoint security are vital to public safety and criminal prosecutions.

1. Zero-Cloud Evidence Model & Data Sovereignty

In-Situ Software Solutions Inc. operates under a strict Zero-Cloud Evidence Rule. We maintain zero custody, zero access, and zero cloud backups of your operational data:

  • 100% Local Case Custody: All evidentiary case files (.eis containers), crime scene imagery, search warrant pages, officer notes, and continuity logs are processed and stored exclusively on your agency’s authorized physical endpoints.

  • No Cloud Exposure: Evidentiary case data is never uploaded, analyzed, or routed through external cloud infrastructure or AI models.

  • Canadian Licensing Infrastructure (Supporting Agency PIAs & FOIPPA): Core license verification services (Google Cloud Run) and licensing status records (Google Cloud Firestore) are hosted in Google Cloud's Toronto, Ontario region (northamerica-northeast2), supporting public-sector Privacy Impact Assessments (PIAs) and provincial/federal privacy alignment (including BC FOIPPA, Ontario FIPPA/MFIPPA, and PIPEDA).

2. Cryptographic Evidentiary Integrity (Canada Evidence Act s. 31.3)

To support the statutory presumption of electronic records integrity under Section 31.3 of the Canada Evidence Act, Exhibit In-Sight implements industry-standard, cryptographically verifiable controls:

  • SHA-256 Hash-Chained Audit Ledger: Operational actions—including exhibit entries, field modifications, photo attachments, continuity transfers, and active-file session authentications—are written to an append-only, internal SHA-256 hash chain linked back to a root genesis block. Any retroactive file tampering breaks the mathematical chain and is immediately flagged upon opening, automatically enforcing Read-Only protection unless a verified backup is restored.

  • Append-Only Version Control (R. v. Stinchcombe): Previously populated evidentiary fields cannot be silently overwritten. Substantive edits spawn incremental revision snapshots (e.g., v1 to v2) archived in isolated disclosure annexes alongside structured Prior and New field diffs. Deletions require mandatory, non-blank justifications preserved permanently for Crown disclosure.

  • Monotonic Clock Anchoring & Anti-Rollback Auditing: Both the desktop MDT (System.nanoTime()) and mobile companion (SystemClock.elapsedRealtime()) anchor against CPU monotonic hardware timers to detect and log manual clock shifts exceeding 30 seconds (CLOCK_SKEW_DETECTED) or timezone changes. Active MDT sessions also query Windows time synchronization sources (w32tm /query /source) and verify mobile-to-MDT time alignment during wireless sync.

3. Encryption Standards & Endpoint Hardening

In Transit (Field Hotspots & Cruiser Subnets)

  • Dual-Layer Transport Security: Field synchronization between mobile devices and MDTs does not rely solely on Wi-Fi network passwords. Communications are encapsulated within an embedded TLS 1.3 transport layer utilizing ephemeral 2048-bit RSA certificates and authenticated encryption cipher suites (such as AES-GCM) over TCP Port 51038.

  • Strict SHA-256 Certificate Pinning: The mobile application enforces cryptographic certificate pinning against the exact SHA-256 fingerprint embedded within the pairing QR code, protecting mobile connections against local Man-in-the-Middle (MitM) interception or rogue access points.

  • Zero-Evidence UDP Discovery: Workstation discovery over UDP Port 51039 broadcasts only ephemeral connection metadata (active port, case license GUID, computer name, and public TLS certificate SHA-256 hash). Zero case file numbers, exhibit descriptions, notes, or personnel details are ever exposed over UDP.

At Rest (Endpoints & Cloud)

  • Operating-System Level Storage Security: To maximize live on-scene read/write throughput, .eis containers, rolling backups, and temporary workspaces remain unencrypted at the application layer and rely on agency-enforced operating-system Full Disk Encryption (Windows BitLocker on MDTs and hardware-backed File-Based Encryption on Android devices).

  • AES-256-GCM Credential & Salted PIN Protection: Desktop MDT officer PINs are hashed using unique 128-bit random salts and SHA-256, and local officer profile caches are encrypted at rest using AES-256-GCM (AES/GCM/NoPadding) bound to a dynamic 256-bit machine salt and the active Windows OS user account before being written to the registry.

  • Mandatory Mobile Screen Lock Verification: Exhibit In-Sight Mobile interfaces directly with Android’s KeyguardManager. If an endpoint does not have an active, secure lock screen (PIN, Pattern, Password, or Biometric), the application blocks access to protect evidence from unauthorized physical extraction.

4. Enterprise Financial & Procurement Security

In-Situ Software Solutions Inc. does not store, process, or transmit credit card details. All billing transactions, tier calculations, and automated tax calculations (GST/HST/PST) are processed through Stripe, certified under PCI-DSS Level 1 Service Provider standards.

IT Implementation & Whitelist Guide