omniaTRIAGE™

Native MSSP case triage platform. Purpose-built for security operations teams managing multiple tenants — malware, incidents, exposures, and phishing — with automatic evidence write to custodia™ on case closure.

Request Access MSSP deployments · Questions? steven.hasson@omniapan.ai

The Problem

MSSP triage tools weren't built for MSSPs.

Generic ticketing platforms — ServiceNow, Jira, even purpose-built SOAR tools — force MSSPs to operate as if they're a single-tenant SOC. Multi-tenant data isolation is bolted on. Compliance evidence is never generated automatically. Case closure produces a ticket status change, not a compliance artifact.

For MSSPs managing clients under CMMC, NIST, or ISO 27001, every case closure is a missed compliance opportunity. The work gets done — the evidence never gets written. omniaTRIAGE was built to fix both problems at once.

How It Works

Triage cases. Generate evidence automatically.

omniaTRIAGE is a multi-tenant case management platform with per-tenant database isolation. Every case is typed — malware, incident, exposure, phishing — and each type maps to a specific set of compliance controls. When a case closes, the platform automatically writes signed evidence to the custodia™ sovereign compliance ledger.

The MSSP operator never has to manually cross-reference a case to a control. The mapping is built in. The evidence write is automatic. The ledger entry is cryptographically signed.

Malware

CMMC: SI.L2-3.14.2/3
NIST: DE.AE-05 · RS.RP-01

Incident

CMMC: IR.L2-3.6.1/2
NIST: DE.AE-05 · RS.RP-01

Exposure

CMMC: RA.L2-3.11.1/2
NIST: ID.RA-01 · RS.RP-01

Phishing

CMMC: IR.L2-3.6.1 · AT.L2-3.2.2
NIST: DE.AE-05 · RS.RP-01

Vulnerability

CMMC: RA.L2-3.11.1
NIST: ID.RA-01 · ID.RA-06

Default

CMMC: IR.L2-3.6.1
NIST: DE.AE-05 · RS.RP-01

The Pipeline

Case closure → compliance evidence. Automatic.

The omniaTRIAGE → custodia™ pipeline is the first MSSP-native compliance evidence pipeline in the market. No competitor connects operational case closure directly to a sovereign compliance ledger. This is MOAT #1.

Evidence Pipeline — Live

Case Closed

→

Control Map Resolved

→

custodia™ API

→

Sovereign Ledger

Pipeline failure never blocks case closure · try/except · log and continue · API-to-API · no DB-to-DB coupling

Slug-based tenant identity — cross-system lookup without UUID dependency

Dedicated service key — isolated, revocable, never shares platform SECRET_KEY

One evidence record per impacted control per case closure

All evidence writes signed to custodia™ sovereign ledger — HMAC-SHA256

Architecture

Per-tenant database isolation. MSSP-native.

omniaTRIAGE provisions a dedicated database per tenant — complete data isolation, no shared schema risk. Isolated internal networking, task queue for async processing, and bot blocking at the perimeter. semelpass.ai gated authentication.

Per-tenant DB isolation — Dedicated isolated database per client — complete data separation

Multi-tenant deployment live — active MSSP clients onboarded

Case types: malware · incident · exposure · phishing · vulnerability

Bot blocking at ingress perimeter — scanner paths dropped before reaching backend

semelpass.ai authentication — no credentials stored in omniaTRIAGE