カテゴリ 古民家暮らしモカとの記録セキュリティの記録副業の記録

The record with MokaNovember 21, 2026

Zero Trust Meant 'Verify,' Not 'Distrust' — and Our House Was Already Run That Way

The result first

Zero trust does not mean “trust no one.” At its core, it means “verify, every time.”

That is what I realized while writing the entry for “zero trust” in a security glossary. According to the explanation by Japan’s IPA (Information-technology Promotion Agency), zero trust is not about trusting nothing, but about verifying everything. The same idea is set out in NIST SP 800-207 (2020) in the United States.

And when I lined that up against how this house is run, the overlap was clear. Publishing goes through my approval. Checks are done by different eyes, never by the person who did the work. Permissions are given only to the person who needs them, and only as much as they need. Everything that happens is recorded, one line at a time, in a ledger.

We had never bought a special security product, and we did not even know the name. We had simply turned the quiet work of “verifying” into rules, and kept those rules running every day. Without knowing the name, this house was already run in a way that overlapped with zero trust.

Hello, I am Kurashiki Bouzu (kurashiki-bouzu). Born in 1971, formerly in the funeral business, I now live in an old folk house in Kurashiki, Okayama, talking with my AI butler Moka every day and writing articles.

The other day, I made a glossary of security terms — a dictionary of 48 words you meet in news stories and on warning screens, explained in the words of everyday life so they are easy to look up. One of those words was “zero trust.” While I was writing that entry, I found myself saying:

“Isn’t zero trust exactly what our way of managing things and controlling access already is?”

As soon as I said it, I thought, “Yes — that’s right.” This is that story.

Zero trust meant “verify,” not “distrust”

Zero trust is the name of an approach to security. Taken literally, it sounds like “zero trust” — a cold phrase.

The old way of protecting things was shaped like a castle and a moat. The moat stops the enemy outside, and anyone who gets inside the castle is trusted as one of your own. In terms of a company network, it is the line that says, “Inside the company is safe; outside is dangerous.”

But that line has been dissolving. Work tools have moved to the cloud — places on the other side of the internet where things are kept — and more people now connect from home. A way of protecting things that trusts everyone inside, without question, can no longer hold.

That is why zero trust has spread. Inside or outside, it makes no difference: each time, you verify — “Is this really you?” “Is this really the right person to let through?” It is like a building where, even after you have entered, you still show your pass at a reception desk for each room you go into.

What matters here is that the name and the contents point in different directions. Japan’s public agency, the IPA (Information-technology Promotion Agency), writes in its guide to introducing zero trust that zero trust means not “trusting nothing at all,” but “verifying everything.”

In other words, the core is not “to doubt,” but “to verify.” The thinking is organized in the same direction in the document from NIST, the U.S. standards body whose measures are used around the world (SP 800-207, 2020).

Think of a bank counter. Even if the clerk knows your face, a procedure involving a large amount of money still calls for identity verification. That is not because the clerk doubts you. It is simply part of the procedure — verified, every time. The “verify” in zero trust is the same kind of thing.

Broken down, it rests on three pillars:

  1. Verify, at every access — Do not keep trusting someone forever just because they were let in once
  2. Give only the permissions that are needed — Hand over only what that person needs, and do not let them carry extra keys
  3. Keep records — Leave what happened in a form that can be checked later

It is not the name of a special product. It is not a tool that ends the job once you buy it. It is the name of a way of thinking about how to protect things.

Our house was already run that way

So how is this house — the shape in which I work with Moka and with staff divided into departments — actually run?

Publishing goes through approval. Even when Moka or a member of staff writes an article, it cannot go out into the world without my approval at the final step. We do not say, “Someone inside the house made it, so it can go out as it is.” Before anything leaves, it is judged, each time. That is the same shape as the first pillar: verify, at every access.

Checks are done by different eyes. This house has a rule: the person who looked something up does not check their own work. Eyes different from the staff member who wrote the article check how the published page looks, what the ledger records, and whether the announcement was posted, and they leave the result in the ledger. No one makes something and then declares, on their own, “It’s done.” The idea of “I can trust myself, so no check is needed” is removed by the way the system itself is built.

Permissions are divided, and verified each time. The person who receives, the person who changes, and the person who inspects are different staff. Decisions that go outside — publishing, pricing, sending, and the like — require approval, and staff never move them forward on their own. Keys go only to the people who need them, and only as much as they need. That overlaps with the second pillar: give only the permissions that are needed.

Records are kept in a ledger. Everything that is done is left in the ledger — the list of articles — one line at a time: when, who, what was done, and how it turned out, in a form that can be verified later. That is the third pillar itself: keep records.

Lined up side by side, the rules of this house had overlapped with the thinking behind zero trust, without ever knowing its name. I have no memory of buying security tools to make this happen. What we had been doing was turning the plain, quiet work of “verifying” into rules, and running those rules every day.

To be honest, here is where the line is

Having written this far, let me draw the line honestly, too.

This is not a story about installing a zero trust system into a company network. It is also different from the technical side of things, such as machines watching over the state of devices. What overlapped was only the core of the way of thinking: stop trusting someone just because they are inside, and verify, each time.

Even so, I was glad about this overlap. An idea with a difficult name was not a story about some distant company. It was already there, inside the rules of my own house. Once you see that, the words of security feel a little closer to home.

The same was true in everyday life

This way of thinking carries over to protecting everyday life, too.

It is not enough to think, “The display name looks genuine, so it must be safe,” or “I logged in on this screen once, so it must be safe.” When a message arrives, you verify it — not through the contact details written inside the message itself, but through a contact you already know is official. That is the same point written under “things to watch for” in the glossary entry for “impersonation.”

Even without large tools, making “verify, each time” into a rule is something you can start today. There must be many houses already doing it, without ever knowing the name zero trust.

In closing — “verifying” was careful, steady work

Zero trust. If you only hear the name, it sounds like a cold system that trusts no one. But the real thing was an accumulation of careful, plain work: verifying.

The rules of this house — pass things through approval, look with different eyes, leave records — were on that side from the start. Even a beginner with programs, working together with an AI butler, can sometimes arrive at an idea that has a proper name, without ever realizing it. I will leave today’s record as one piece of evidence of that.

Record of this article
  • November 21, 2026 ― 英語版(日本語版No.1476の内容を「結果から書く」形に書き直したもの)(6,499 characters)
  • November 21, 2026 ― 公開(本人の公開判断による。7言語同時公開。アドレスの末尾に台帳番号を入れる新形式で、末尾は日本語版の番号No.1476)(6,499 characters)

#Security #Zero Trust #Muse #Moka #Beginners

← Back to the article list / ← Back to the English top page