Dashboard
Processed by Resec server
Moved without Resec — transfers that did not pass through CDR
Recent files
| File | Status | Verdict | Size | Submitted |
|---|
| File | Status | Verdict | Policy | Size | Submitted |
|---|
| When | File | Channel | CDR | Verdict | User | Size |
|---|
| When | Action | User | Detail |
|---|
Install the desktop agent
Download, install on the machine, then sign in with your API key.
Agent features
Choose which optional tabs your desktop agents show. This is the organization default; override it per agent in the table below.
| Agent | User | Status | Version | Platform | Watch | Remote | First seen | Last seen |
|---|
Agent access keys
Keys minted when users sign the agent in. Revoke one to disconnect that device.
| Device | User | Last used |
|---|
SFTP access
Partners upload to your private inbound folder over SFTP; files are sanitized and dropped in the clean folder. Manage the SSH logins below.
Add a webhook
We’ll POST signed events (HMAC-SHA256, header X-RC-Signature) when files complete.
| URL | Events |
|---|
Verify the signature
Every delivery is signed with your tenant secret over <timestamp>.<raw-body>. Always verify X-RC-Signature on the raw body before trusting the payload.
API keys
Authenticate machine-to-machine calls with the x-api-key header. Create one key per integration so you can revoke a single key without disrupting the others. Each key is shown once — store it in a secret manager.
Quick start
A live demonstration that the full sanitization service is available over the REST API. Pick a file and a policy, run it against the real service, watch every API call — then copy the exact integration code.
Connection
Integration code
Workspace
Language
Interface language for this browser.

Resec