Skip to content
SAUTERASAUTERA
← Blog
Infrastructure Trust··2 min read

The decision that was right at design time and wrong by Tuesday

Most infrastructure is trusted once, at design time, and never re-examined. The decision doesn't get revoked when the facts change — it just quietly stops being true.

By Joe Augustine

Here is a pattern I have watched play out more times than I can count. A team stands up a host. They do it carefully — current operating system, disk encrypted, ports closed, patches applied. Someone signs off. The host is trusted, and rightly so. The decision was correct.

Then time passes.

Six months later that same host is running an operating system that went end-of-life in the spring. A patch was rolled back during an incident and never reapplied. A management port was opened at 2 a.m. to fix something urgent and never closed. None of this was reckless — each step had a reason. But nobody ever went back and asked the original question again: can this still be trusted?

The sign-off from six months ago is still in force. The host is still treated as trusted. And it is no longer true.

Trust isn't a property. It's a verdict with an expiry date.

The mistake is in treating a trust decision like a property you stamp onto a system once — trusted — the way you'd set a flag. Properties persist until something changes them. But nothing changes this one, because the act of changing it requires someone to notice, re-investigate, and re-decide. That rarely happens on a schedule, and it never happens for the host you forgot you owned.

A trust decision is really a verdict rendered against a set of facts at a moment in time. When the facts move, the verdict should move with them. If it doesn't, you are not running on a trust decision anymore — you are running on a memory of one.

What the Infrastructure Trust Architecture changes

The Infrastructure Trust Architecture (ITA) starts from the opposite assumption: that the facts will move, so the verdict has to be re-derived continuously rather than asserted once. The trustworthiness of a host is read on a live cadence — by the SAUTERA Witness sensor on the host, or agentlessly over SSH, WMI, and SNMP — and the trust score updates as the facts do.

The end-of-life slip, the reverted patch, the port that got left open: each of these moves the score the moment it is observed. The host that was trusted in January and degraded by July doesn't keep coasting on January's verdict. The verdict expires the instant the evidence stops supporting it.

That is the whole idea, stated plainly. The dangerous host is almost never the one you decided not to trust. It is the one you decided to trust, correctly, and then never looked at again.

The fix is not better sign-offs. It is refusing to let any sign-off be the last word.

#infrastructure trust#trust decay#lifecycle#drift

Written by

Joe Augustine

Author of the Infrastructure Trust Architecture (ITA) and the Infrastructure Trust Continuous Monitoring model (ITCM) — the standard organizations use to decide whether infrastructure can be trusted.

About the author

Follow the work

Read the next one

New perspectives on infrastructure trust and updates to the ITA / ITCM framework, by email. No social account required.

Occasional. No spam. Unsubscribe anytime.

← All perspectives