You have heard the phrase trust but verify, and something about it has been bothering you. Maybe someone you relied on turned out to be less than they seemed, and you are wondering whether you should have checked. Maybe you are in a position now where people are asking you to take them at their word, and part of you wants to, and another part of you remembers the last time you did. Either way, you are trying to figure out how to trust people without being a fool about it, and you suspect the answer is somewhere in that phrase.
It is. I have spent my career in security, across law enforcement, fire service, the private sector, and federal service, and the single doctrine I have carried through all of it is that security is only assumed until it is tested. The same is true of trust. Trust should be tested, not assumed. That is not cynicism. It is the only approach I have found that lets you be generous with people and still sleep at night, and I want to show you how it works in practice.
Where the Phrase Comes From and What It Actually Means
Trust but verify entered the language through arms control negotiations, where two parties who had every reason to doubt each other still needed to make agreements. The genius of the phrase is that it refuses the false choice most people accept. Most people think you either trust someone or you check on them, and that checking is an insult. The phrase says you do both, and that doing both is what makes the trust real rather than sentimental.
In security work this is simply how things are done. A locked door is assumed to be locked until someone tries the handle. A camera is assumed to be recording until someone pulls the footage. An access badge is assumed to belong to the person carrying it until someone checks the face against the photo. Every one of those assumptions is reasonable, and every one of them is where a breach happens when nobody bothers to test it. People work the same way, and the ones who mean you harm are counting on you not to check.
Why Trust Should Be Tested, Not Assumed
Assumed trust is trust that rests on how someone makes you feel. They are warm, they are confident, they say the right things, and you fill in the rest. Nearly every betrayal I have investigated or lived through ran on assumed trust. Nobody had ever asked the person to demonstrate anything, so nobody found out what they would do until it cost something. Tested trust rests on what someone has actually done when they had the chance to do otherwise. It is slower to build and much harder to fake.
There is a second reason, and it is the one people miss. Testing protects the honest as much as it exposes the dishonest. An honest person has nothing to lose from being verified and a great deal to gain, because verification turns your opinion of them into evidence. When I have been checked on in my own career, I welcomed it, because I knew what the check would find. The people who bristle at verification are usually telling you something, and it is worth listening.
How to Test Trust Without Becoming Suspicious of Everyone
Testing does not mean interrogating people or setting traps. It means extending trust in increments and paying attention to what happens. Start with something small that has a low cost if it fails. Share a minor confidence and see whether it stays where you put it. Rely on someone for a small commitment and see whether they keep it without being reminded. Disagree with them once, respectfully, and see whether they can handle it without punishing you. None of these are tricks. They are just ordinary life, observed with intent.
In my own work I use a framework I call P.R.O.O.F., and the core of it is that you do not accept a claim about security until you have seen it perform under conditions that could reveal a failure. Apply the same standard to people. When someone tells you they are loyal, that is a claim. Loyalty is proven when they had a chance to gain by leaving you exposed and did not take it. When someone tells you they are honest, that is a claim. Honesty is proven when the truth cost them something and they told it anyway. Look for the moments where a person could have failed and watch what they chose.
What the Bible Shows About Untested Trust
Scripture is honest about this in ways that a lot of modern advice is not. David trusted Ahithophel, his most respected counselor, without reservation, and Ahithophel joined Absalom’s rebellion the moment the wind shifted. Jesus kept Judas in the inner circle for three years, and Judas passed every visible test until the night he did not. These stories are not there to make you paranoid. They are there to tell you that even the wisest people who ever lived were betrayed by people they had reason to trust, and that the answer was never to stop trusting. The answer was to trust with eyes open and to keep the damage survivable.
Joseph is the positive example. When his brothers showed up in Egypt, he had every reason to assume the worst and every reason, as the one with power, to simply decide. Instead he tested them, patiently, over a long period, and let their conduct answer the question. He was not being cold. He was being careful with something that mattered, and the result was a restoration that held for the rest of their lives.
Building Trust but Verify Into Your Daily Life
Start by noticing where you have assumed instead of tested. Think about the people who currently hold real access to your life, your finances, your reputation, your family, and ask yourself what you have actually seen each of them do under pressure. For some of them the answer will be plenty, and you can rest there. For others you may realize the trust is resting entirely on personality and time. That does not mean they are dangerous. It means you have not verified yet, and you can begin.
Then make it a habit going forward. When someone new enters your life, whether a hire, a partner, or a friend, let them earn access in stages. Confirm what can be confirmed. Ask the follow-up question when a story does not add up. Keep records where records are appropriate. And when someone passes the tests, tell them so, and give them more. The point of verification is to be able to trust fully, on a foundation that will hold. I wrote about this doctrine at length in my book Until Tested: Security Is Only Assumed, and the principle is the same whether you are securing a building or your own life. What has not been tested has only been assumed, and what has only been assumed is where the damage comes from.
Go Deeper
If you learned this lesson the hard way, through a leader who used your trust against you, I wrote a book about how to keep serving well under someone who has shown you what they are. It follows David through his years under Saul and draws out how he stayed loyal without ever again being naive: The Spirit of Saul.
Commissioner William Epps is an author and security leadership consultant with a background in law enforcement, fire service, private security, and federal government. His books are published through E.P.P.S. Method Publishing Co.

Leave a Reply