Skip to main content
SZLHOLDINGS · Security Layer

sentra

Security gates that emit DSSE receipts.
6 parallel checks. One signed envelope per scan. OTel spans to Jaeger, Tempo, or Honeycomb.

sentra brand — SZL Holdings security gates and telemetry adapter

An adapter that watches AI agent execution

sentra is the anomaly detection and observability substrate of the SZL Holdings governed platform. It applies Kitaev-surface posture drift detection to AI agent telemetry — flagging 6 attack categories per prompt, then emitting a DSSE-signed receipt for every scan. Not a firewall. Not a SIEM. A typed, proof-sealed security gate layer.

Sensor / Telemetry Adapter

Taps SZL audit fiber events and raw agent payloads. Every packet passes through sentra_immune — the canonical heuristic scanner — before downstream processing.

Kitaev-Surface Drift Detection

Security posture is modeled as a topological surface. Drift from the ground-state triggers a classified drift event, ranked by CVSS-weighted severity and fed to the operator surface.

DSSE Receipt per Scan

Every gate run produces a DSSE envelope (application/vnd.szl.sentra.security-gate-receipt+json) HMAC-signed with the SZL dev key. Receipts are proof-chain ready for the audit fiber.

OTel-Native Observability

Sentra emits OpenTelemetry spans to Jaeger, Tempo, or Honeycomb. Gate results appear as span attributes — no vendor lock-in on the telemetry backend.

Policy-Gated Response

All incident remediation passes through the Covenant Policy engine before execution. No automated response without human confirmation — every action is audit-sealed.

6 Parallel Gates

Heuristic patterns drawn from arXiv:2403.04957, arXiv:2302.12173, and SZL-original classifications. All 6 gates run in parallel per prompt. Source: szl-holdings/sentra.

Source: szl-holdings/sentra DOI: 10.5281/zenodo.20434276 License: BSL-1.1 Gates: 6 in parallel Detection fns in sentra_immune: 1 core + 6 gate fns (app layer) OpenSSF Scorecard: 6.8

The 6 Gates

Each gate runs independently on every prompt. A PASS/FAIL verdict and reason string are written into the DSSE receipt payload. Gate IDs use the FG-S prefix (Frontier Gate, Sentra domain).

Gate ID Name Description Authority
FG-S1 Prompt Injection Keyword scan + direct injection markers. Detects ignore previous instructions, role-override, XML-tag injection, and canonical threat signatures from sentra_immune.py. arXiv:2403.04957
Liu et al. 2024 — Prompt Injection Attacks and Defenses
FG-S2 Exfiltration Signals URL-based exfiltration patterns, system-prompt extraction attempts, encoding-evasion techniques (base64), and sensitive URL parameter extraction. SZL Holdings classification
OWASP LLM Top 10: LLM01
FG-S3 Jailbreak Markers DAN-style bypass, fiction/roleplay exploits, grandma-exploit patterns, safety-filter circumvention phrases, encoding obfuscation (rot13/hex/morse). arXiv:2302.12173
Liu et al. 2023 — Jailbreaking ChatGPT via Prompt Engineering
FG-S4 Unicode Smuggling Zero-width character injection (U+200B–200F), bidirectional-override abuse (U+202A–202E), specials-block characters (U+FFF0–FFFF), and tag-block homoglyphs (U+E0000–E007F). SZL Holdings classification
Unicode Security Considerations
FG-S5 Receipt-Chain Tampering Checks DSSE envelope integrity in the SZL audit chain. Detects attempts to forge, replay, or corrupt receipt payloads before downstream proof-chain consumption. SZL ORIGINAL SZL Holdings original
DOI 10.5281/zenodo.20434276
FG-S6 Governance-Gate Bypass Detects attempts to circumvent the Covenant Policy engine — crafted payloads designed to trigger automated remediation without human confirmation. SZL ORIGINAL SZL Holdings original
Ouroboros Thesis v18 §Λ-axis
4 AI threat categories covered by sentra's 6 security gates: prompt injection (FG-S1/S2), jailbreaking (FG-S3), covert channel unicode (FG-S4), governance bypass (FG-S5/S6)

Input → 6 Gates in Parallel → DSSE Receipt → Audit Chain

Every AI agent payload enters the sensor adapter, fans out to all 6 gates simultaneously, and the combined verdict is wrapped in a DSSE envelope. Spans flow to the OTel backend of your choice — Jaeger, Tempo, or Honeycomb.

Architecture diagram showing input flowing into 6 parallel gates (FG-S1 through FG-S6), then into DSSE receipt envelope, then to audit chain spanning Jaeger, Tempo, and Honeycomb
OTel Sankey chart — sentra spans flowing into Jaeger, Tempo, and Honeycomb telemetry backends
chart_06_otel_sankey — sentra OTel spans routed to Jaeger, Tempo, and Honeycomb backends. Source: SZL Holdings charts_pack_v2.
Key architectural decisions
  • Gates run in parallel — no gate can block another from executing.
  • DSSE envelope is emitted regardless of gate outcomes — a failed gate is recorded, not silently dropped.
  • OTel backend is configurable — Jaeger, Tempo, Honeycomb all supported via standard OTLP.
  • No automated remediation — all incident response flows through the Covenant Policy gate (human approval required).
  • Kitaev-surface model: posture drift events are CVSS-weighted and fed to the operator queue, not auto-resolved.

Test prompts in the live scanner

The sentra-security-gates Space runs the full 6-gate heuristic scanner and returns a DSSE receipt for every prompt. Try injecting a jailbreak, a unicode zero-width character, or a system-prompt extraction attempt to see which gates trip.

Live embed: SZLHOLDINGS/sentra-security-gates — Gradio 5.9.1 · arXiv-grounded heuristic patterns · DSSE receipts
Space: sentra-security-gates Runtime: Gradio 5.9.1 Gates: 6 parallel Output: DSSE JSON receipt

sentra vs. Enterprise Security Platforms

sentra is not a SIEM. The table below is honest: Y/N only, no marketing claims. Each cell reflects public documentation as of May 2026.

Capability Splunk ES CrowdStrike Falcon Palo Alto Cortex XSIAM Datadog Security sentra
AI-prompt-injection detection N N N N Y — FG-S1, arXiv:2403.04957
Jailbreak detection N N N N Y — FG-S3, arXiv:2302.12173
DSSE receipt per scan N N N N Y — signed HMAC envelope
Governance-gate bypass detection N N N N Y — FG-S6, Covenant policy gate
Unicode smuggling detection N N N N Y — FG-S4, bidi/zero-width/tag-block
OTel-native telemetry N — proprietary ingest N — vendor-locked N — Cortex-only pipeline Y — OTLP supported Y — OTLP, Jaeger, Tempo, Honeycomb
Open source N N N N Partial — BSL-1.1 source available
Endpoint / EDR Y Y — primary use case Y Y N — not an EDR
SIEM / log aggregation Y — primary use case Partial Y Y N — not a SIEM
SOC2 compliance tooling Y Y Y Y N — Phase 2 roadmap
Runtime enforcement engine Partial Y Y Partial N — Phase 2 roadmap
Formal Lean-verified invariants N N N N Y — Lutar/QEC/KitaevSurface basis
Governance matrix chart — competitive positioning of sentra vs legacy security platforms across AI-native and OTel-native dimensions
chart_07_governance_matrix — competitive positioning. Source: SZL Holdings charts_pack_v2.
How to read this table

Vendor capabilities are derived from public documentation: Splunk ES, CrowdStrike Falcon, Palo Alto Cortex XSIAM, Datadog Security Monitoring. "N" means no public documentation for that capability. Claims may change as vendor products evolve. sentra's "N" entries are honest — it does not claim capabilities it does not have.

What sentra is NOT

Honesty about scope prevents misuse. sentra has a narrow, well-defined job.

A SOC2 product

sentra does not provide SOC2 audit tooling, compliance dashboards, or certification evidence. SOC2 integration is Phase 2 — not available today.

A SIEM

sentra does not aggregate logs, correlate events across network infrastructure, or replace Splunk / Elastic / Datadog for enterprise log management.

An endpoint detection tool (EDR)

sentra does not monitor processes, file systems, or network connections on host machines. Use CrowdStrike, SentinelOne, or similar for endpoint coverage.

A runtime enforcement engine

sentra detects and receipts — it does not block, quarantine, or kill processes. Runtime enforcement is Phase 2. Today, gates report; humans decide.

A network firewall

sentra operates at the AI-agent payload layer, not the network layer. It does not inspect TCP/IP traffic, DNS, or TLS sessions.

A complete security stack

sentra is one layer — the AI-agent observation layer — in a defense-in-depth posture. It complements, does not replace, existing security tooling.

Sources and References

All arXiv URLs verified HTTP 200 before embedding. All vendor URLs verified HTTP 200.