Skip to content

Phishing-resistant help desk

Phishing-resistant help desk recovery when every security key is lost

When an employee has lost every security key or passkey, phishing-resistant account recovery starts with two people. An in-person supervisor and a different help-desk agent, the HQ approver, each approve with a registered FIDO2 security key before VerifiedKnock requests a one-time credential.

No government ID, selfies or biometrics are collected. There is no face or document scan. Each person taps a registered FIDO2 security key.

How it works

Two recovery paths, each enforced by policy and recorded end to end.

Lost every security key or passkey: supervisor and HQ approval

  1. An authorized branch supervisor confirms the employee in person, using your organization’s own process, and approves with a registered FIDO2 security key.
  2. The employee opens the pickup link on their own device and confirms it with a short read-back code.
  3. A separate HQ help-desk agent reviews the request and approves with a registered FIDO2 security key.
  4. Only after both approvals, VerifiedKnock requests a single-use Microsoft Entra Temporary Access Pass, Okta Temporary Access Code or Cisco Duo bypass code. It is short-lived and shown only on the employee’s device; neither approver sees it.
  5. The employee registers a new security key or passkey. Every step is written to the audit trail.

Employee still has a registered key: dual tap

  1. The employee taps a registered FIDO2 security key.
  2. An authorized help-desk agent taps a registered FIDO2 security key.
  3. With both approvals recorded, your help desk carries out the one requested recovery action.

Phishing-resistant account recovery

Each approval uses a registered FIDO2 key and is bound to the genuine service. After both approvals, the employee receives a short-lived credential on their own device and registers a new key.

Help desk social engineering prevention

A caller who sounds convincing still cannot get a reset. Recovery requires an in-person supervisor and a different help-desk agent, each approving with a registered FIDO2 security key.

MFA reset fraud and help desk impersonation

The person asking for the reset never approves it. No one-time credential is requested until both approvals are recorded.

Built for

Organizations where account recovery has to be controlled, consistent and reviewable, and where staff can meet employees in person at a branch or site.

  • Banks and credit unions with branch networks and a central help desk.
  • Healthcare organizations with clinical and administrative staff across multiple sites.
  • Enterprises standardizing on FIDO2 security keys and passkeys.
  • CISOs and IT and identity directors who own recovery policy.
  • Help-desk and service-desk managers who run recovery day to day.

Controls and audit

Recovery policy is enforced by the product, not left to individual judgment.

  • Two-person approval: every lost-key recovery needs two different people, each with a registered FIDO2 security key.
  • Separation of duties: an administrator can be a designated branch supervisor, but never the HQ help-desk approver.
  • No self-approval: nobody can approve their own recovery, administrators included.
  • Administrator keys: one registered FIDO2 security key is required; a backup key is optional but strongly recommended.
  • One-time credentials: the pass is short-lived, single-use and never shown to approvers.
  • Audit trail: each approver, key, step and result is recorded, giving your team evidence for internal and compliance reviews.

Deployment

VerifiedKnock connects to your existing Microsoft Entra ID tenant (Temporary Access Pass), Okta org (Temporary Access Code) or Cisco Duo (bypass code). Your identity provider stays the system of record. There is no rip-and-replace: your sign-in policies, authentication methods and directory stay as they are.

Subscribe through Microsoft Marketplace or start with a pilot. Pricing is per protected user and published on the pricing page.

Questions

What is phishing-resistant help desk recovery?

When an employee has lost every security key or passkey, a supervisor and a different help-desk agent each tap a registered FIDO2 security key before a one-time credential is issued. Works with Microsoft Entra ID, Okta and Cisco Duo.

What is phishing-resistant account recovery?

When an employee has lost every security key or passkey, a supervisor and a different help-desk agent each approve with a registered FIDO2 security key. A short-lived credential is then shown only on the employee’s device.

How does this stop help-desk social engineering?

A caller who sounds convincing still cannot get a reset. An in-person supervisor and a different help-desk agent each approve with a registered FIDO2 security key before any one-time credential is requested.

Does VerifiedKnock collect government ID, selfies or biometrics?

No. No government ID, selfies or biometrics are collected, and there is no face or document scan. Your organization defines how supervisors confirm employees in person. VerifiedKnock records the approvals, each made with a registered FIDO2 security key.

How does VerifiedKnock enforce separation of duties?

Every lost-key recovery needs two different approvers, each with a registered FIDO2 security key. An administrator can be a designated branch supervisor, but never the HQ help-desk approver, and nobody can approve their own recovery.

How is VerifiedKnock priced and purchased?

Pricing is per protected user and listed on the pricing page. You can subscribe through Microsoft Marketplace or contact us to start a pilot.

Bring controlled recovery to your help desk

Subscribe through Microsoft Marketplace, or book a pilot with our team.