Secure File Requests
Sensitive material should enter the organization already protected.
Ask a client, candidate, supplier or auditor for a document and receive it inside RED's protection and evidence model rather than in an inbox.
The flow
From request to protected object.
- 01
Create a request
Describe what is needed and who is being asked.
- 02
The recipient submits
The submitter provides the file without needing an account in your organization's directory.
- 03
Protection is applied
The submitted material is protected and placed in the requesting organization's environment.
- 04
Receipt is recorded
Request creation, submission and receipt are recorded as evidence.
Why it matters
The collection point is where control is usually lost.
Most organizations protect data well once it is inside a system, and lose control entirely at the moment it arrives. Identity documents, financial statements and contracts land in mailboxes that were never designed to hold them, and then get forwarded.
A file request moves the boundary earlier: the material is protected as it enters, and the organization has a record of the exchange.
In the product
Requests and their status.
See it against your own environment.
Connect your own storage, protect a document, and read the recorded evidence yourself.