Unknown is an answer
A trust model that always returns a confident number is easy to build and impossible to trust. The honest move is to say when you can't see enough yet.
The founder
Joe Augustine wrote the standard that organizations use to decide whether infrastructure can be trusted. SAUTERA is where that standard is put to work.
The idea
Most organizations decide to trust their infrastructure once — at design time — and then assume that decision still holds months and incidents later. Joe Augustine built his career on the conviction that this is the wrong way to treat trust. Trust is not a property you grant; it is a state you have to keep verifying.
The Infrastructure Trust Architecture (ITA) and its continuous-monitoring model (ITCM) make that possible. Together they combine identity trust with the trustworthiness of the infrastructure itself, and keep the resulting trust decision current as systems change. It is the framing behind every decision SAUTERA helps organizations make.
Authority
The framework is now referenced by the name of its author. Enterprise and government teams working through high-stakes infrastructure decisions — what to deploy, what to depend on, and how to prove it is sound — work from his model. When the stakes are high enough that the framework alone is not sufficient, they ask for the architect.
The framing of a trust decision before it is made.
An independent read on infrastructure trust posture.
The architecture-level judgment that turns a standard into a defensible decision.
What organizations come to him for
The work
Augustine operates at the architecture and strategy layer. He writes and speaks on infrastructure trust and continuous evaluation, develops the ITA and ITCM standards through SAUTERA, and is bringing the framework to a wider audience through a forthcoming book. His perspective is published openly — the ideas are meant to be used.
ITA
The architecture of how infrastructure earns trust — the lifecycle, the engines, the data path, enforcement, and governance.
ITCM
The continuous-monitoring model that keeps the trust decision current as systems, identities, and risk move — so a decision made today does not decay into a liability tomorrow.
Forthcoming
The forthcoming book brings the Infrastructure Trust Architecture to a broader audience of leaders responsible for systems people depend on — why identity alone was never enough, and what it takes to make infrastructure trust continuous and deliberate. Follow along to know when it lands.
Follow the work
One note when the book is out, plus new perspectives and framework updates along the way. No social account required.
Occasional. No spam. Unsubscribe anytime.
Perspectives
A trust model that always returns a confident number is easy to build and impossible to trust. The honest move is to say when you can't see enough yet.
A worked example of how identity trust and infrastructure trust combine into one verdict — and how a clean-looking access request gets caught, fixed, and proven.
A single number per device is only useful if you can see what's underneath it. A field note on how infrastructure trust is scored — and why it will tell you when it doesn't know.
Contact
If your organization is working through an infrastructure trust decision and you want to think it through with the person who built the framework, you are welcome to reach out directly. These exchanges tend to begin with a question rather than a brief — a real problem, framed plainly.
founder@sautera.com