Fail-closed. Everywhere.
A governance platform is only as trustworthy as its own security. AIOPS is engineered on a single non-negotiable rule: when a security control cannot run, the operation it protects does not run either.
Degraded means denied — not "best effort."
Most platforms treat a failed security check as a warning to log. AIOPS treats it as a stop signal.
PII scanning halts ingestion
Every uploaded document is scanned before storage. If the scanning service is unreachable, ingestion returns an error — unscanned data never enters the governance record.
Injection detection blocks prompts
Semantic and pattern-based detection screens LLM traffic for prompt-injection attempts. Detected attacks are blocked and logged, not sanitized and forwarded.
Streaming redaction guards output
Model outputs stream through a token-buffering PII redactor before reaching any client — sensitive data is caught mid-stream, not in a post-hoc scan.
Defense in depth, by construction.
Identity & sessions
Short-lived signed JWTs verified on every request — claims are never trusted before signature verification. Server-side token revocation means a compromised session dies the moment you kill it.
RS256 JWT · server-side revocation · OIDC/SAML federationZero-trust service mesh
SPIRE issues cryptographic workload identities; every service-to-service call requires mutual TLS. There is no "trusted internal network" — each hop authenticates.
SPIRE · SPIFFE identities · mTLS everywhereTamper-evident evidence
Evidence packages are Ed25519-signed and chained into an append-only SHA-256 ledger stored on WORM object storage. Altering history is detectable by anyone holding the public key.
Ed25519 · SHA-256 ledger · WORM retentionHardened supply chain
Containers run as non-root users, CI actions are pinned to immutable digests, dependencies are scanned continuously, and no credentials ever ship in version control.
Non-root containers · pinned CI · secret hygienePrecision arithmetic
Every compliance score and monetary value uses exact decimal arithmetic end to end. Floating-point drift has no place in numbers a regulator or an invoice depends on.
Decimal end-to-end · reproducible scoringAudit & key management
Structured audit logging with request correlation across services, documented key-rotation procedures, and SOC 2 aligned control mapping maintained as living documentation.
SOC 2 controls · key rotation · threat modelSecurity as a process, not a page.
The controls above are backed by the operational discipline your vendor-risk team will ask about.
- Documented threat model and incident-response runbooks
- SOC 2 aligned control framework with mapped evidence
- Continuous dependency and container scanning in CI
- Principle of least privilege across services and tenants
- Coordinated disclosure — see below
contact: [email protected]
policy: coordinated disclosure
scope: oceks.com, AIOPS platform
pgp: available on request
# We acknowledge reports within 48 hours
# and credit researchers who report in good faith.
Send us your security questionnaire.
We answer vendor-risk assessments with specifics, not marketing language. Ask for the architecture deep-dive.