No direct identity writes
HNPT consumes verified Shared Auth claims and owns its own product authorization. It does not mutate identity-provider storage.
Defensive by construction
A security product must make its own blast radius legible.
HNPT separates authentication from product authorization, customer identity from operator identity, evidence from telemetry, and suspicious sessions from production reachability.
What the platform is designed to deliver
Each capability carries an explicit delivery state. We do not present a roadmap item as a deployed control.
- Shared Auth verification
The authentication proxy validates exact issuer, audience, client, realm, scope, and assurance contracts before HNPT authorization runs.
Integration in development - Product-owned authorization
HNPT remains authoritative for tenant membership, application roles, case access, quarantine scope, and response policy.
Contract available - Separated identity realms
Customer and operator identities fail closed and never fall back to one another.
Safety invariant - Evidence containment
Attacker-controlled values are bounded at ingestion, parameterized in storage, encoded at output, and excluded from metric labels.
Safety invariant - Isolated playpen
Synthetic workloads deny production data, credentials, and reachability while preserving reviewable session evidence.
In development
Defaults that fail safely.
Degraded identity, missing tenant context, ambiguous scope, stale leases, and unknown policy states do not silently become access.
No secret-shaped marketing
This static site handles no credentials, sessions, provider tokens, introspection credentials, or customer evidence.
Build with us
Start with a bounded, observable pilot.
Define what may be observed, what a quarantine can affect, how it expires, and who reviews the evidence before connecting a production system.