DoveSureAccess
- Ten roles, each granted capabilities rather than checked by name
- Multi-factor authentication with single-use recovery codes
- Sessions end after 30 minutes idle or 8 hours, and can be revoked
- Sensitive actions ask you to confirm it is you again
Security & trust
A Record You Can Stand Behind
Customers, auditors and regulators rely on what DoveSure says. So the record is append-only, every change is chained, and nobody, including DoveSure’s own AI, gets more authority than they should.
Append-only evidence
Evidence, test results and approvals are never edited or deleted. A correction is a new record.
Hash-chained ledger
Every material change is chained. Your auditor can verify the whole chain from the browser.
Provenance set by the server
People can self-attest or upload. Stronger provenance is only ever assigned by the system.
Strict tenant isolation
Row-level security in the database keeps each organisation’s data separate, and it is tested on every change.
Bank-grade sign-in
Argon2id password hashing, multi-factor authentication, recovery codes and server-side sessions.
Everything on the record
Who did what, when and why, including every action Dove takes on your behalf.
Provenance
Assertion Is Not Proof
Every piece of evidence records how it was produced. A person can self-attest or upload; the stronger levels are assigned by the system, never claimed.
- 1Self-attested
- 2Manually uploaded
- 3System observed
- 4API collected
- 5Independently validated
- 6Cryptographically verifiable
Integrations
- Read-only permissions for every connected system
- Connector secrets sealed with AES-256-GCM
- Provider hosts fixed per connector
- Webhooks signed with HMAC-SHA256 and a replay window
AI
- Dove never has more authority than the person using it
- Every action waits for your confirmation
- Actor, intent, tool, input, output and approval are all recorded
- Denied actions are recorded too
Ready to prove it?
Know what you are responsible for, control whether it works, and prove it to anyone who asks.