Trust · Security

Secured the same way it governs.

Default-deny capability, a tamper-evident ledger, signed releases, and a disclosure program with a safe harbor. The controls, stated plainly.

S-01 Architecture is the control

Sentinel's security story starts with where it runs: inside your boundary. There is no Settlegate cloud holding your vehicle data, no cross-tenant database, no traffic to intercept between you and us. The attack surface we can affect is the runtime binary itself, and everything below is about that.

S-02 Default-deny, enforced twice

An agent's capabilities come only from the tool policy you compile — the registry grants nothing by default, and a call outside the grant fails closed at the policy layer and at the transport layer, so a bug in one enforcement point is not a bypass. Every denied call is itself a ledger event; probing the boundary leaves footprints.

S-03 The ledger cannot be quietly edited

Provenance entries are hash-chained and append-only. Deleting or altering an entry breaks the chain visibly, which is the point: the record's value is that nobody — including us, including you — can rewrite history without it showing. Ledger integrity is checked on every read and attested in every export.

S-04 Supply chain & release integrity

Runtime releases are built from a locked dependency set, signed, and shipped with a software bill of materials. Your deployment verifies signatures before an update installs. We publish checksums independently of the download channel, so a compromised mirror cannot hand you a compromised runtime unnoticed.

S-05 Our own house

Settlegate's corporate systems follow the same philosophy: hardware-key MFA everywhere, least-privilege access reviewed quarterly, laptops encrypted and centrally managed, production access just-in-time and logged. Independent penetration tests run annually against both the runtime and our release pipeline.

S-06 Telling us something is wrong

Found a weakness in the runtime, this site, or our release pipeline? Write to security@settlegate.xyz — PGP key and safe-harbor commitment at /.well-known/security.txt. We acknowledge within one business day, keep you informed while we fix, and credit you if you want credit. Good-faith research within the safe harbor will never meet legal threats from us.

Maintained by the Settlegate security team · last revised June 19, 2026