← Back to The Wire№ 2 · Sep 6, 2026
Shipped.
4 shipped this week

This one's bigger than a quick hits list, so it gets the lead slot to itself. Plus two real bugs squashed in Metrics. Issue № 2 — same deal as always: what changed, why it matters, no roadmap theater.

Lead item

TrustZero: one setting instead of a rulebook

Writing every allow/deny rule by hand doesn't scale, and it doesn't get easier as your catalog grows. TrustZero replaces that with one org-wide choice: Allow by Default for a permissive starting point, or Catalog Onlyto deny everything except what's already in your app catalog and not blocked. Flip the setting and Threatmatic writes and maintains the underlying policies for you — no more hand-authoring a rule per app. A third mode, Learn, Then Enforce, is coming next (see below).

Set your posture →

Quick hits

  • NEWPolicies screen has a "Show TrustZero-managed" switch — the rules TrustZero writes for you stay out of your way by default, one click to see them.
  • FIXMetrics → Events shows what's actually happening now, not a "last 7 days" window frozen at whatever moment the server last restarted.
  • FIXSorting and filtering no longer crashes on a table with an empty field — zones, policies, devices, and several others were affected.

Next up

→

Learn, Then Enforce — the third TrustZero posture. Point it at your fleet, let it quietly build your catalog for a window, then it switches to enforcing only what it actually saw. In development now.

Field note

A prospect asked us why they'd need another "zero trust" product when they already own six. Fair question — most of what's on the market makes you write the trust yourself, rule by rule, app by app. TrustZero watches what's actually running and writes it for you. Trust earned from what's really there, not assumed from what someone imagined in advance.— from a call this week, paraphrased