Perspectives on digital trust.

Not technical deep-dives. A view from management, policy and society on how trust should work for the actions that matter.

Articles

The structural weaknesses in Japan’s cybersecurity

Attacks have become cheaper and faster. Have the organizations and decision structures that defend against them kept up?

Why critical actions need intent verification

Authentication confirms who someone is. It does not confirm what they wanted.

Designing to limit misuse after a breach

No one can guarantee zero leaks. So design systems in which leaked data alone cannot complete a critical action.

01

The structural weaknesses in Japan’s cybersecurity

Attacks have become cheaper and faster. Have the organizations and decision structures that defend against them kept up?

The cost of attack keeps falling

Generative AI makes it possible to produce fluent phishing messages and convincing fake interfaces quickly and at scale. Attacks that once took skill and effort can now be launched against more targets for less money. As the attacker’s costs fall, the defender’s burden keeps rising.

The whole supply chain is the attack surface

Japanese industry is organized around large companies connected to many suppliers and partners. The least-defended organization becomes the way in, and damage spreads through business relationships. No single company can secure the whole by itself.

The gap between management and technology

Security investment is a management decision. Yet leadership teams that can translate technical risk into business risk — and prioritize accordingly — are still too rare. Where engineers are treated as implementers of instructions rather than experts at the decision table, the risks the front line can see rarely reach the board.

Rethinking what we protect

Most defenses have focused on keeping intruders out and protecting the login. That remains essential. But if we accept that intrusions and data leaks cannot be eliminated entirely, the asset to protect lies further in: confirming that critical actions — transfers, account changes, privilege grants — genuinely reflect the holder’s intent. That is where we believe the next focus of defense belongs.

This article reflects the author’s views and does not guarantee the effect of any specific product.

02

Why critical actions need intent verification

Authentication confirms who someone is. It does not confirm what they wanted.

Authentication and authorization are different questions

Authentication asks whether the person accessing a system is a legitimate user. Whether that person wants a particular action to happen is a separate question. A successful sign-in does not prove intent behind everything that happens next.

Match the check to the risk

Strict checks on every action burden users and erode the value of the service. What matters is varying the level of confirmation with the significance of the action: routine actions flow smoothly, while irreversible ones require the holder to review the details and approve them deliberately. That distinction is what lets usability and trust coexist.

Accountability

When a fraudulent transaction occurs, a provider must be able to explain whether the action reflected the customer’s intent. Recording who approved what, and from which device, serves both customer protection and institutional accountability.

When AI acts on our behalf

AI agents are likely to make more bookings, purchases and applications for people. The question then is not only whether the agent was authenticated, but who delegated which authority, and whether a human approved the decisions that matter. Intent verification connects directly to that new challenge.

This article reflects the author’s views and does not guarantee the effect of any specific product.

03

Designing to limit misuse after a breach

No one can guarantee zero leaks. So design systems in which leaked data alone cannot complete a critical action.

Assume a breach

Preventing data leaks is essential, but no amount of effort reduces the probability to zero. The more useful question becomes: when a leak happens, how far can the leaked data be abused?

The risk of concentration

Concentrating authentication secrets or personal data in one place makes that place the prime target, and a single breach can affect huge numbers of users at once. Keeping stored data to a minimum and avoiding central stores of secrets is an effective way to limit the scale of harm.

Leaked data should not be enough

Even if a name, an account number or a password is exposed, executing a critical action should still require explicit approval by the rightful holder through their own device. In that kind of design, stolen data is worth considerably less.

Separate roles, combined well

Identity verification, authentication and transaction authorization each play a distinct role. Rather than relying on one mechanism for everything, separating these roles and combining them deliberately prevents a single weakness from becoming a systemic failure. That is our view of the next generation of digital trust infrastructure.

This article reflects the author’s views and does not guarantee the effect of any specific product.

Contact

We handle inquiries by email. Each button opens a new message with the subject line and a short template filled in. We respond in English or Japanese.

Request a technical briefing

PassProof overview, scope and deployment models.

Email us

Discuss a use case

Work out with us which operations in your business need intent verification. Proof-of-concept discussions welcome.

Email us

Explore partnership

Systems integrators, resellers, technology partners and international business partners.

Email us

General inquiries

Media, speaking requests and other inquiries about the company.

Email us

Privacy notice

Personal information you send us — such as your name, organization and contact details — is used only to respond to your inquiry and related communication, and is not disclosed to third parties without your consent except as required by law. Please do not include confidential information in your first email.