Security

Last updated 23 October 2026

Detent exists so a person, not software, approves what AI agents do. That only works if software cannot fake the person. Here is how Detent is built for that, and how to report a problem.

Approvals software can't forge

• Every Detent makes its own secret key and signs each answer it gives: who, which request, what was on its screen, the decision, and a counter that only goes up.
• Your company's Detent server checks the signature, the device and the counter. Unsigned, forged, replayed or revoked approvals are refused when your company turns on "Only signed approvals count".
• Pairing shows the device's key as a code on its own screen, never on the computer. Pairing again replaces the key. A lost device can be revoked in one click.
• High-risk actions need a full turn of the knob and a press within five seconds, after a short pause so a reflex press is ignored.

Your data

• The bridge removes common secrets (API keys, tokens, passwords, private keys) before anything is shown, recorded or sent. Companies can choose to record control names only.
• The bridge accepts connections only from your own computer and rejects requests from web pages on other sites.
• Companies can run the Detent server inside their own network, so records never leave it.
• On the server: approval records are chained with SHA-256 so any change or deletion is detectable; device keys are encrypted with a separate key; passwords use PBKDF2 with 310,000 iterations; every token is stored only as a hash; sign-in, enrolment and approval checks are rate limited; cookies are HttpOnly and SameSite=Strict; pages send a strict Content Security Policy.
• Admin actions (pairings, revocations, settings, rollouts) are recorded in an activity log.

Hardware

Production devices will ship with encrypted flash, secure boot (only Detent-signed firmware runs) and debug ports disabled, so the key can't be read out of a stolen device. Prototype units used in pilots do not have these protections yet; pilot customers are told this in writing.

What we don't claim

Detent has not yet completed an independent audit such as SOC 2 or ISO 27001, or an external penetration test. We will publish when we have. Detent recognises common risky actions and your company's rules; it cannot recognise every risky action an agent might take.

Report a vulnerability

Email devvratpathak.dp@gmail.com with "Security" in the subject. Please include steps to reproduce. We will reply within three working days, keep you updated, and credit you if you wish. Please give us reasonable time to fix an issue before publishing it, don't access data that isn't yours, and don't disrupt anyone's service. We won't take legal action against good-faith research that follows these rules.