Last month I argued that trust must move at machine speed. This month I want to ask a different question.
When trust breaks, why are the people harmed still expected to do so much of the recovery themselves?
For decades, organizations have invested heavily in preventing failure. They have built security programs, compliance frameworks, governance structures, risk models, monitoring systems, and incident response teams.
Yet when a failure occurs, it is often the person whose identity was compromised, the patient whose information was exposed, the customer whose account was misused, or the citizen whose data was mishandled who is left to deal with what follows.
The institution manages the incident. The individual manages the consequences.
Somehow, we have come to accept this as normal. It shouldn't be.
The Hidden Cost of Trust Failure
When trust breaks, organizations typically mobilize. Investigations begin, notifications are issued, vendors are engaged, and compliance obligations are addressed. Many organizations also offer support to the people affected.
These actions matter. They should not be overlooked.
But for many affected individuals, the difficult part is only beginning. They are left to manage a problem they did not create—often across several organizations, and often for months.
Many of today's recovery practices took shape before digital identities and interconnected services became so deeply embedded in everyday life. That context has changed. When something goes wrong today, the consequences can reach further and faster—yet recovery still depends heavily on the person affected.
The institution experiences an incident. The individual experiences a disruption to daily life.
Those are not the same thing.
Who Carries the Burden?
In my previous Perspective, Trust Must Move at Machine Speed, I looked at the gap between the speed of digital threats and the speed at which affected people receive protection.
But speed is only part of the problem. Even if recovery becomes faster, we must still ask whether the right party is carrying the responsibility.
Organizations are routinely asked:
How secure are our systems?
Are our controls effective?
Are we compliant?
How quickly can we respond?
These questions are essential. But another deserves equal attention:
Who bears the burden when trust fails?
Too often, a substantial share falls on the person harmed. Not because organizations lack concern, and not because they never help, but because many existing processes are designed primarily to manage incidents and fulfill institutional obligations.
This is another side of what I have called the Trust Restoration Gap™.
Organizations can usually show that they detected an event, investigated it, reported it, and responded to it. What is far less clear is whether the people affected were able to recover.
An institution may close the incident. The individual may still be living with the consequences.
A Question Boards Should Begin Asking
Boards increasingly oversee cybersecurity, AI, operational resilience, privacy, and enterprise risk. They examine the effectiveness of controls, the adequacy of investments, and the organization's readiness to respond when something goes wrong.
Yet one question deserves greater attention in board discussions and post-incident reviews:
When harm occurs, who is responsible for recovery?
The answer matters because responsibility shapes behavior. What boards expect gets funded. What boards review becomes an organizational priority.
How an institution supports people after a failure can also shape customer confidence, long-term relationships, and institutional value.
If the practical burden remains primarily with the affected individual, boards should ask whether that outcome reflects the organization's values, responsibilities, and long-term trust objectives—and whether the experience of the people affected is part of how the organization judges its own response.
This question also deserves attention from policymakers and regulators. As digital systems become more interconnected and autonomous, we should examine whether existing consumer protection frameworks adequately address the recovery burden placed on individuals when trust fails.
Greater Responsibility, Without Less Control
Taking greater institutional responsibility does not mean taking control away from individuals. People should remain informed, understand what has happened, and keep meaningful choices about decisions that affect their identities, information, and finances.
The aim is not to replace individual judgment with institutional decisions. It is to reduce the burden placed on individuals while preserving their rights and choices.
Trust cannot be restored by taking away the very agency that makes trust possible.
The Next Standard
Cybersecurity has long emphasized prevention. Detection and response have become increasingly sophisticated. Resilience is receiving greater attention. All remain essential.
But the objective should be larger than restoring systems, closing incidents, or completing regulatory obligations. It should include reducing the burden placed on people when trust fails.
This is not a substitute for prevention or compliance, and it does not remove individual choice. It is a broader understanding of accountability.
As digital systems become more powerful, institutions may need to accept a greater share of responsibility for the consequences those systems create.
Not merely because regulation may require it.
But because trust depends on it.
The organizations best positioned to earn lasting trust may not be those that claim they will never fail, but those that demonstrate through their actions that the people who trusted them will not be left to face the consequences alone.
And perhaps the most important question is not simply whether a failure occurred.
It is whether the right person is doing the recovery.
This is the sixth article in my Founder's Perspective series, where I share my thinking on digital trust, AI, accountability, and the evolving relationship between organizations, technology, and the people they serve. I welcome your perspectives and look forward to the conversation.
— Naray Viswanathan, PhD · Founder & CEO, SecuShift™ · Tampa, Florida · November 2026
Earlier in this series
From trust as infrastructure, to what happens when trust breaks, to why the response must move faster.