DOQEX Lite

No. Any device with a modern, standards compliant browser is compatible with DOQEX. Users don’t need to download or install anything.

Contacts interact with your private data exchange portal. 

Your portal is created as part of the DOQEX service and is branded and configured to serve your workflows.  By default your portal is served via one of your domains, e.g. https://secure.yourorganisation.com

Via automated policy.

Everything from access rights to retention periods, TTLs, download limits, password formats and data sharing agreements are automatically set via policy (set by admin).

With unlimited user cohorts, you can define and retain complete control over the data rights and interoperability between office staff, remote workers, partners, suppliers and customers.

DOQEX fileview deploys the follwing security method:

Customisable watermarks can be embedded in every file. By default this includes a timestamp, URL, IP, agent string and device ID but admins can define their own watermark content.

The fileviewing method uses a separate in-memory decryption vault for each file. Each vault decrypts and buffers a small section of each file before streaming it to the browser. After each view the file vaults and encryption keys are scrubbed, no decrypted data ever touches disk.

Yes. Admins select if (and how) folders can be shared.

By default, child folders and file data cannot be shared, viewed or downloaded.

Version control is fully configurable.

By default, files are matched by filename but may also be matched by hash or MIME type. Admins select how duplicate files are handled included renaming and extension rewriting.

Yes. In practice, the majority of DataOps amongst DOQEX data exchanges are collecting and managing inbound data.

Data uploads can be initiated in many ways including by a user, via a project workspace, published in workflow form, generated by back office systems via an API call, added by a contact via sFTP or embedded in an email.

As long as necessary.

However, every data object has an expiry date. Expiry dates are set by policy and you control what those are, who can change them, when and by how much.

To prevent indefinite and uncontrolled data retention expiry dates are compulsory in DOQEX.

As long as necessary.

However every share has an expiry date. Expiry dates are set by policy and you control what those are, who can change them, when and by how much.

To prevent accidental or uncontrolled data loss share expiry is compulsory.

Yes. DOQEX provides multiple modern APIs.

The DOQEX API playground contains reference code and implementation examples for a huge range of endpoints.

The DOQEX devOps team will work directly with you to quickly scope, develop and test functionality so you can quickly extend that back-office app or extract audit logs for your SIEM service.

Yes. DOQEX is Microsoft AIP aware. Data flows across your DOQEX service can be scanned for classification data. Configurable actions are set within the DLP engine.

DLP functionality can be enabled for data flows.

DLP policies are configured within the DLP engine allowing inspection, quarantine options and range of customisable alerts.

For further details, visit our Data Loss Prevention page.

Yes. Data flows can be passed to the in-built AV/AM engine for inspection.

Configurable actions include bounce, quarantine options and range of customisable alerts. The API interface also allows AV/AM scanning to be built into your applicatoin allowing fast call-back results.

Yes. Every email and SMS message sent by DOQEX is customisable.

There are a wide range of notification options which can be applied to different user cohorts, options include immediate, digest and scheduled notifications.