Security for Redaction Software

Stored content is encrypted with AES, with the algorithm and key length set by configuration rather than fixed, and scopeable per content format. Encryption covers the streaming renditions, sprite thumbnails, closed captions and timed metadata files alongside the source file.

Cryptographic operations run through the host platform's cryptographic providers. On a FIPS-mode host, including Azure Government, they are performed in validated modules. Algorithms in use include AES for content encryption and HMAC-SHA384 for token signing.

• Role-based access control over files, features and administrative functions
• Single sign-on, with enforced SSO available so local passwords are not an alternative route
• SCIM user provisioning, plus identity-provider attribute mapping and group synchronisation
• Multi-factor authentication
• Password policy and token and session policy
• Built-in security groups and group management
• Service application credentials and API authentication for machine access

Every action on an item is recorded from ingestion through to disposition, and custody visibility is restrictable to supervisors.

The full custody model — what each entry records, the event types, and how the trail is exported as release evidence — is on defensibility.

Malware scanning on upload. A web application firewall. Custom security headers. Vault-backed secret management. Infrastructure hardening, security patching, log access levels, and a documented security incident response process.

• Encryption covers the content formats named in the setting. Additional encoding profiles produced outside that set follow the storage provider rather than the platform setting.
• Keys are held by the platform. Customer-held keys are a storage-provider arrangement rather than a platform one.
• FIPS validation is a property of the host cryptographic module, not of the application. VIDIZMO does not hold a CMVP module certificate of its own, and FIPS mode is configured on the host operating system rather than by the application.
• The custody trail records actions taken within the platform. Integrity verification depends on the hash recorded at ingest.

• AES content encryption at rest, configurable by algorithm and key length, scopeable per format, covering derived renditions as well as sources.
• Cryptographic operations invoked through the OS provider, so a FIPS-mode host performs them in validated modules.
• RBAC, SSO with enforcement, SCIM provisioning, IdP attribute mapping and group sync, MFA, password and session policy.
• Every action is recorded and auditable; see defensibility for the custody detail.
• Malware scanning, WAF, custom security headers, vault-backed secrets, documented incident response.

Our security overview sets out the programme, governance and incident response in full. Deployment covers where Redactor can run.