Resources

The evidence behind the argument.

Research, answers, and the vocabulary behind Continuous Identity Confidence. Written for the people who defend sessions for a living.

answers
20answers
defined terms
23defined terms
incident analyses
2incident analyses

Featured white paper

The session is legitimate. The user is not.

Our research on the post-authentication gap, available two ways. Start with the two-page executive brief, or take the full analysis.

MindVaultWhite Paper
2026 Security Research Report

The Session Is Legitimate. The User Is Not.

Why authentication is no longer enough, and what comes next.

Inside the report
  • Adversary-in-the-middle and token theft
  • Session hijacking and cookie replay
  • AI-agent and automation risk
  • Continuous identity confidence as a new signal

MFA proves who logged in. MindVault measures who stayed.

Executive summary

The two-page brief

A fast read on why a technically valid session no longer always means a trusted user, and where post-authentication visibility gaps remain.

PDF · 2 pages · No signup

Read the brief
Full white paper

The full detail

The complete analysis of the post-authentication gap: why valid sessions can still become risky, and how continuous identity confidence adds a new signal alongside MFA, SSO, and EDR.

PDF · 14 pages · Quick form

Read it online →

$4.99M

global average cost of a data breach

IBM Cost of a Data Breach 2026

39%

of breaches involved credential abuse at some stage

Verizon 2026 DBIR

80+ : 1

machine identities for every human

CyberArk 2025 Identity Security Landscape

Also available

The rest of the material.

Beyond the white paper, three more places the research lives.

Questions and definitions

Asked and answered.

The questions security teams ask during evaluation, and the vocabulary this site uses when it answers them.

No. IAM decides who gets in. EDR protects the device. MindVault adds the missing question: is the same person still operating the session? It sends that answer to the tools and team you already have.

Behavioral interaction patterns: the rhythm of how a person types, pauses, and moves the mouse, along with device and session identifiers. We use this data only to measure confidence in who is operating the session, and we treat it as sensitive security data. See our Privacy Policy for details.

A pilot starts with the sensor on an agreed group of devices, pushed through your MDM or by your MSP with simple command-line switches. Most of the setup is on our side, and we scope the timeline with your team.

A changed pattern is not always a changed person. A new keyboard or an unusual task can shift it. That is why MindVault reports confidence levels instead of yes-or-no answers, and why every pilot has your SOC review the confidence results with our team before anything is connected to a response. MindVault uses one fixed, provisional alert rule today. Per-company thresholds are not available.

AI agents and automation now act inside sessions with real user permissions, and that is a growing gap. Today MindVault measures whether the person operating a session matches the enrolled user. Dedicated bot and AI agent signals are in active development.

AI-driven SOCs move fastest when they can trust their inputs. When an alert fires, one of the first questions is whether the real user is still at the keyboard. MindVault answers that question with a continuous confidence signal, so automated playbooks and AI agents have one more piece of evidence before they act.

MindVault is designed with data minimization in mind, and we support your privacy review with clear documentation, employee notice guidance, and retention settings. Compliance depends on how each organization deploys and uses any tool, so your privacy and legal teams stay involved from day one.

Any system that accepts a webhook, including most SIEM, SOAR, and ticketing platforms. Packaged connectors for leading platforms are in active development.

Fraud-focused tools protect customer journeys and transactions. MindVault focuses on the employee operating a session on the desktop and in the browser. The two answer different questions and complement each other.

Yes, one lightweight sensor per Windows device. It covers the desktop and the browser, so MindVault sees the whole session, not just one browser tab. Your IT team or MSP deploys it through your existing tools, and users do not need to do anything.

Through the tools you already use. MindVault is a single lightweight sensor that your IT team or managed service provider pushes through your mobile device management (MDM) or software deployment tool, using simple command-line switches. There is nothing for users to click or install.

Yes. Managed service providers can roll out the sensor across your devices and manage it as part of the services they already provide.

Your organization does, the same way it does for other security tools on company devices. We help with notice language and walk your privacy and legal teams through what the sensor collects.

Tell us which teams and workflows you want to protect first. We will work with your IT and security leads to scope a pilot and agree on what success looks like.

MindVault does not analyze video or voice. But when a deepfake call tricks someone into handing over a session, a different person ends up at the keyboard, and that is the change MindVault measures.

Re-checking a credential only proves the credential is still valid. A stolen or shared session passes every time. MindVault measures the person, not the password.

A confidence verdict for the session (High, Medium, Low, or Insufficient) with the user, device, and time, delivered to the destination you choose.

No. Analysts can review MindVault's confidence verdicts alongside the alerts they already use. If your team runs automated playbooks or an AI-driven SOC, the same verdict can feed those workflows too.

No. The sensor runs quietly in the background. Users keep working while MindVault measures.

No. MindVault is a security tool. It measures confidence in who is operating a session, not how much or how well someone works.

Security glossary

Post-Login Gap
The span between a successful login and the end of a session, where most security checks stop asking who is operating.
Operator Continuity
Confidence that the person operating a session is still the person who started it.
Continuous Identity Confidence
Measuring Operator Continuity throughout the session, not only at login.
Human Confidence Signal
MindVault's output: a High, Medium, Low, or Insufficient confidence level for the person operating the session.
Session Handoff
The moment a different person or process takes over a session that is already signed in.
See the full glossary

Incident analyses

Real breaches. Real gaps.

These are not MindVault deployments. They are analyses of public breaches and government advisories that show why the session after login needs its own signal.

Incident Analysis | 2025

Healthcare services data breach

individuals affected
62M+individuals affected
days undetected
84days undetected
data exfiltrated
Multi-TBdata exfiltrated

Attackers had access to a major healthcare services provider's network for nearly three months, from October 2024 until the intrusion was discovered in January 2025. The data taken reportedly included names, Social Security numbers, medical information, and health insurance details.

Public reporting has not said how the attackers first got in. It does show how long they stayed: almost three months inside a trusted network before anyone noticed.

Long dwell time is the gap MindVault is built to shrink. When the person operating a session stops matching the enrolled user, the Human Confidence Signal gives the security team a reason to look, long before month three.

Based on public reporting. The method of initial access has not been publicly disclosed. This is not a MindVault deployment.

Sources: Fox Business · Tom's Guide · HIPAA Journal

Incident Analysis | 2024

Help desk impersonation ransomware campaign

organizations impacted
500+organizations impacted
critical infrastructure sectors hit
12 of 16critical infrastructure sectors hit
code to hand over the desktop
1code to hand over the desktop

A ransomware group flooded employees' inboxes with spam, then called or messaged them posing as the company's IT help desk. Offering to fix the problem, the caller asked the employee to open Windows Quick Assist, a built-in remote support tool, and enter a code.

That one code put the attacker in control of a real, signed-in company computer. No password had to be stolen and no MFA prompt had to be beaten. From inside that trusted session, the attackers downloaded their tools, moved across the network, and deployed ransomware.

Every login check had already passed. What changed was who was at the controls: the employee in front of the screen handed control to a remote operator. That handoff is the change MindVault measures, and the Human Confidence Signal gives the security team an answer to "Is this still our user?" while the session is still open.

Based on public reporting and a joint government advisory. This is an analysis of a campaign across many organizations, not a single company and not a MindVault deployment.

Sources: Microsoft Security · CISA · BleepingComputer

How we engage

A structured path from evaluation to production.

Every engagement begins with understanding your environment. Nothing is committed until you have seen results in your own systems.

  1. 01

    Pilot

    Evaluate in your environment

    Silent baseline collection on an agreed group of users for two weeks, then thirty days in which your SOC reviews the confidence results with our team. MindVault uses one fixed, provisional alert rule today. Per-company thresholds are not available.

  2. 02

    Production

    Deploy and expand

    Once your team has seen the results, verdicts flow into your existing response tools, and coverage widens to further user groups and workflows.

  3. 03

    Enterprise

    Full coverage

    Whole-environment coverage with custom routing and policy, and dedicated support.

Every engagement is scoped to your environment.

The cost of inaction

The impact of impersonation attacks.

What impersonation costs when nothing is watching the session after the credential clears.

39%

of breaches involved credential abuse at some stage

Verizon 2026 DBIR (opens in a new tab)

$19.5M

average annualized insider risk per organization

Ponemon 2026 Cost of Insider Risks (opens in a new tab)

We can prove who logged in. We cannot prove who is still there.