Security Domain

Overview#

A defence attorney challenges the integrity of a dashcam video introduced as evidence. The investigating agency uses the Security domain's public verification portal: the attorney enters the verification code and independently confirms that the file hash matches the original collection record, and that no modifications have been recorded in the cryptographic audit chain. No platform access required, no trust in the agency's word alone. The Security domain provides this kind of verifiable, transparent evidence handling for every item in the platform: chain of custody tracking, tamper-evident audit trails, compliance framework assessments, and the ability to quarantine files that fail integrity checks before they contaminate an active investigation.

Key Features#

Compliance Framework Support: Assess and maintain compliance with industry standards including CJIS, FIPS, NIST, SOC2, ISO 27001, and GDPR through automated compliance checking and gap identification.
Cryptographic Audit Trails: Record security-relevant events in tamper-evident audit chains that provide verifiable proof of system activity for regulatory audits and legal proceedings.
Evidence Integrity Verification: Verify that evidence items have not been altered since collection using hash-based integrity checking, supporting legal admissibility requirements.
Chain of Custody Tracking: Maintain a complete, auditable record of every access, transfer, and modification to evidence items from collection through disposition.
Public Verification Portal: Enable external parties to verify evidence authenticity through secure verification codes without requiring platform access, supporting transparency in legal proceedings.
Evidence Quarantine: Isolate evidence items that fail integrity checks or are flagged for review, preventing compromised materials from being used in active investigations.
Security Monitoring: Track security events and policy violations in real time to detect and respond to potential threats to platform data and operations.

Use Cases#

Rigorous evidence security and compliance management are prerequisites in any field where data integrity carries legal or regulatory weight. Primary industries include law enforcement and criminal justice, defence, and financial services.

Legal Evidence Management: Ensure all evidence maintains a verifiable chain of custody with integrity guarantees that satisfy court admissibility standards.
Regulatory Compliance: Demonstrate compliance with applicable security frameworks through automated assessment, gap analysis, and remediation tracking.
Security Auditing: Review comprehensive audit trails of security events, access patterns, and administrative actions for periodic security reviews.
Public Accountability: Provide external verification capabilities that allow defence attorneys, courts, and other parties to independently verify evidence authenticity.

Integration#

The Security domain provides foundational protections across the platform:

Evidence Management: Integrity verification and chain of custody for all evidence items
Investigation Management: Security controls govern investigation access and data handling
Audit and Compliance: Security events feed into comprehensive audit reporting
User Management: Authentication and authorisation decisions are security-logged

Open Standards#

FIPS 140-2 (Cryptographic Module Standard): the security service enforces FIPS 140-2 Level 2 approved algorithms exclusively, using AES-256-GCM for encryption, SHA-256/SHA-512 for integrity hashing, RSA-PSS with SHA-256 for digital signatures, and PKCS#11 for optional HSM key management.
NIST SP 800-53 (Security and Privacy Controls): compliance assessments map directly to NIST 800-53 control identifiers including AU-2 (event logging), AC-2 (account management), SC-8 (transmission confidentiality), and SC-13 (cryptographic protection).
OWASP Application Security Verification Standard (ASVS): chain-of-custody hash verification uses constant-time comparison per ASVS V6.2.8 to prevent timing-oracle attacks, and ASVS is tracked as a named compliance framework in gap analysis reporting.
ISO/IEC 27001 (Information Security Management): the compliance engine assesses controls against ISO/IEC 27001 and its cloud-specific extensions ISO 27017 and ISO 27018, producing gap reports and remediation tracking aligned to the standard's Annex A control set.
EU General Data Protection Regulation (GDPR): compliance controls are mapped to GDPR Articles 25 (data protection by design), 32 (security of processing), and 33 (breach notification), with supervisory-authority breach-notification tracking using ISO 3166-1 alpha-2 jurisdiction codes.
FBI CJIS Security Policy: the platform assesses compliance with the Criminal Justice Information Services Security Policy as a named framework, supporting law-enforcement customers who handle criminal justice evidence with court-admissibility requirements.
ArcSight Common Event Format (CEF): the audit-trail export service produces CEF-formatted log lines for ingestion by SIEM platforms (Splunk, Elastic, Microsoft Sentinel, IBM QRadar), enabling external correlation of security events from the cryptographic audit chain.
SOC 2 (Trust Services Criteria): compliance reporting generates SOC 2 assessments covering security, availability, and confidentiality criteria, stored as typed compliance reports alongside FIPS 140-2 and NIST findings.

Last Reviewed: 2026-02-05 Last Updated: 2026-04-14