Security & compliance posture

Where we actually are.

We are a small company selling into regulated institutions. The temptation is to imply more certification than we hold. This page is the antidote: current state, what triggers the next step, and what to ask us instead in the meantime.

The short version

Sentinel holds no third-party security certification today. Not SOC 2, not ISO 27001. If a certificate is a hard procurement gate for you, we are not yet a fit, and we would rather tell you now than three meetings in.

Certification status

SOC 2 Type II
Not started
No auditor engaged, no observation window begun. We will name the auditor and the window on this page when that changes, rather than describing it as “in progress” beforehand.
ISO 27001
Not started
Not scoped. Likely to follow SOC 2 rather than run alongside it.
Penetration test
Not commissioned
No third-party test has been run. Internal adversarial testing exists in the suite, which is not the same thing and we will not present it as such.
GDPR posture
Partial
Self-hosted deployments keep personal data inside your infrastructure. Our own processing is described in the privacy policy, which is a template pending counsel and says so.

What triggers the audit

The first design-partner contract. A SOC 2 observation window costs real money and takes months, and running it before a single institution has committed would be spending a founder’s runway on a certificate rather than on the product. When a partner signs, the audit starts, and the dates get published here and owned.

If you are that partner and the timing matters to you, say so — it is a legitimate thing to negotiate into the agreement.

What we do have

None of this substitutes for an audit. It is what a security team can evaluate directly, today, without taking our word for it.

Self-hosted by default
Shipped
Decision data, audit chain and evidence bundles stay inside your infrastructure. We do not receive them and have no means of retrieving them. This is the strongest control on this page, and it is architectural rather than procedural.
Independently verifiable evidence
Shipped
Published hash-chain spec, a dependency-free verifier that imports nothing of ours, and a sample bundle. Check our evidence yourself before believing anything else here.
Reproducible performance claims
Shipped
Every latency number on this site comes from a harness you can run, with the hardware and payloads stated. See the benchmarks.
Authentication and authorisation
Shipped
API keys stored as SHA-256 hashes and unrecoverable in plaintext; role-based access control; SSO via SAML and OIDC with role mapping.
Tamper-evident audit
Shipped
Hash-chained append-only events. Tamper-evident, not tamper-proof: it detects modification of retained events and does not by itself prevent deletion. Put the log on object-lock storage if you need that, and do not accept copy from anyone claiming WORM without one.
Model risk pack
Shipped
For your MRM function: whether Sentinel is a model under SR 26-2, the AST-verified determinism evidence either way, inventory fields, validation evidence and Section VII obligations. The pack.
Security whitepaper
Shipped
Architecture, data residency, key management, audit integrity and a threat model that names what we do not defend against. Read it or download the PDF.
Published detection eval
Shipped
Injection detection measured against a public benchmark, with the misses and two false-positive defects it found in our own product published alongside. See the numbers, including the unflattering one.
Coordinated disclosure
Shipped
A reported bypass becomes a failing test, a corpus entry and a republished number. The process, including what we will not do.
Automated test suite
Shipped
Over 2,200 tests covering the rule engine, security stages, governance controls and the published artefacts. Evidence of discipline, not a substitute for an external assessment.

What to ask us instead

A questionnaire designed around certificates will not tell you much about a company this size. These questions will:

  • “What leaves our network?” In a self-hosted deployment, nothing operational. Make us walk the data flow and point at the boundary.
  • “Show us an evidence bundle and let us verify it ourselves.” The tooling is already public. If it does not verify, that is a finding you can generate without us in the room.
  • “What does the product not do?” The security stages detect known attack families. They are defence in depth and not a solved problem, and we publish the measured numbers rather than a footnote.
  • “What happens when the gate is unreachable?” A fair question for anything inline, and one we would rather answer precisely than confidently.
  • “Who is accountable, and what is the escalation path?” One person. You will have their number.

If something on this page is out of date, it is a bug. Tell us and we will fix it.

Design partners

Bring your security questionnaire anyway.

We would rather work through it and mark the honest gaps than have you discover them later. The gaps are the reason the first three partnerships are priced as partnerships.

Design partner programme Verify our evidence