Home / Security
Security for Redaction Software
Redaction software holds the unredacted version. That makes the security posture around it part of the redaction argument, not a separate subject.
The Controls
Encryption at rest
AES, with algorithm and key length set by configuration rather than fixed, and scopeable per content format. Keys are held in the platform database.
Encryption in transit
TLS, terminating at the application server or the load balancer in front of it. A portal can refuse plain HTTP rather than redirect it.
Access control
Role-based over files, features and administrative functions. Authorisation resolves through what the tenant licensed, what the user holds, and what the request requires.
Authentication
SSO over SAML, OAuth or OpenID Connect, enforceable as the only route in. Second factor by email passcode, or phish-resistant factors enforced at your provider.
Provisioning
A SCIM 2.0 API, so your identity provider creates, updates and deactivates accounts. Group membership synchronises, and rules map groups to an access level.
Audit
Every action recorded with user, email, IP address, timestamp and event, across roughly 36 event types. A separate administrative log covers configuration changes.
Upload safety
Malware scanning on ingest, with Microsoft Defender shipped and the scanner pluggable. Enabled per tenant rather than on by default.
Perimeter
A web application firewall, documented for Azure Application Gateway. VIDIZMO operates it on managed SaaS, you operate it on your own deployment.
Secrets
Held in a vault rather than in configuration files. HashiCorp Vault for self-hosted, Azure Key Vault for Azure, by service principal or managed identity.
What Each One Actually Means
Encryption covers renditions
Stored content is encrypted with AES, and the scope includes streaming renditions, sprite thumbnails, closed captions and timed metadata alongside the original. A system that encrypts the master and leaves the preview has left the content readable.
FIPS comes from the host
Cryptographic operations run through the host platform's providers, so a FIPS-mode host — including Azure Government — performs them in validated modules. Algorithms in use include AES for content and HMAC-SHA384 for token signing.
Enforced SSO closes the door
Single sign-on can be made the only route in, so a local password is not an alternative path around your identity provider.
Custody is role-restricted
Every action is recorded with the user, their email address, the IP address they acted from, the local date and time, and the event. Viewing custody for your own content and for all content are separate entitlements, so an investigator sees their own trail while a supervisor sees the whole one.
The trail runs to disposition
Roughly 36 event types are recorded from ingestion through to deletion, which is what makes it a custody record rather than an activity log.
How Access Is Governed
Authenticate
SSO through your identity provider, with MFA, and enforced SSO where a local password must not be an option.
Provision
SCIM creates and removes users automatically, with group membership synchronised from the directory.
Authorise
Role-based access control decides which files, features and administrative functions each role reaches.
Record
Every action is written to the custody trail with user, address and timestamp.
For a Security Questionnaire
Our security overview sets out the programme, governance and incident response in full, including vulnerability management and biannual penetration testing. Deployment covers where Redactor can run, including entirely inside your own network.
Send Us Your Security Review
Most evaluations reach the same three questions: where the unredacted original lives, who can reach it, and what is recorded when they do. We will answer all three against your own controls list.