The security model assumes a hostile network. Mutual TLS
between services, per-request authorization, structured audit
of every privileged operation. Compliance certifications are
on the roadmap; the engineering controls they require are
shipped or in flight.
LAYER TOGGLE·WHAT EACH CONTROL COVERS
PICK A LAYER. SEE THE CONTROLS.
PROTOCOLTLS 1.3 on every listener (:9200 ES · :8080 native · :8081 gRPC)GA
CIPHER SUITESModern AEAD only · TLS_AES_128_GCM · TLS_AES_256_GCM · TLS_CHACHA20_POLY1305GA
CERT ROTATIONSIGHUP reload · existing connections finish · no downtimeGA
MUTUAL TLSBetween internal services · client-cert auth option for externalGA
NO DOWNGRADETLS 1.2 and lower not accepted · no null cipher · no export-gradeGA
FIPS VALIDATION140-2 cert track · required for DoD IL5 + FedRAMP HighROAD 2027
SEGMENT + WALAES-256-GCM on every segment file and WAL segmentBETA
KEY DERIVATIONPer-index keys via HKDF from customer-root master keyBETA
AWS KMSBYOK via AWS KMS · rotation without downtimeROAD Q2
OIDC · SAMLOIDC · SAML 2.0 · AWS IAM · Azure AD · Okta · PIV / CAC bridgeROAD Q2
SCIMSCIM 2.0 provisioning for tenant and user lifecycleROAD Q3
AUDIT TRAILStructured event log · queryable as index · replayable · exportableBETA
EXPLAIN-PLANFirst-class endpoint · per-node cost + rows · audit artifact for every retrievalGA
AIR-GAPStandard binary · offline lexical mode · operator-staged archive + adjacent .sha256 integrity only · optional local model · no runtime telemetry/update/license calls · Console may attempt external Google FontsDOCS
MULTI-TENANCYTenant-isolated indices + quotas + audit · physical isolation via separate clustersGA
Each release archive has an adjacent .sha256 file. It verifies archive integrity against the published digest, not a signature or attestation.
OFFLINE BASELINE
The standard binary runs in offline lexical mode without model files. An optional local model can be staged separately when neural embedding is required.
RUNTIME BOUNDARY
The running binary makes no runtime telemetry, update, or license-activation calls. The Console may still attempt its external Google Fonts resources in a browser.
PROCEDURE
Stage the release and any model files on a connected machine, verify the adjacent digest, then transfer and verify again inside the enclave.
MINIMAL DEPENDENCIES
~36 MB static binary (no JVM). No dynamically-loaded modules, no plugin model, no runtime code download. Supply-chain attack surface shrinks with binary size.