Use cases· Last updated 2026-09-21

Security audit trail with Jev

SIEM, EDR, and SOAR already detect and can isolate. Jev judges whether the alert narrative + evidence pack is enough and whether policy allows the proposed contain class. Code aborts auto-containment unless those atoms clear. Jev does not match IOCs, isolate hosts, or write detections.

This unofficial page is the audit trail slice of the security containment-abort pack. Intent: apply the Jev (TypeSafe System One) decision model to security containment-abort audit trail. Primary search language: Security Jev audit trail. Confirm patterns on docs.typesafe.ai. This site does not sell, issue, or proxy TypeSafe keys. Use a credential you already have from the console or a documented gateway.

Independent angle (cover ≠ clone): Evidence-sufficiency + policy-allow + abort thresholds before SOAR fires isolate/disable — not a clone of support-action recipes, LLM guardrail Noul screens, or SRE incident SEV classification.

Security use-case context

An audit trail for security containment-abort is a decision trace: replayable inputs, typed answers, floors, abort reason, and the SOAR action that did or did not fire. It is not a SIEM retention product and not a clone of an EDR timeline.

Hub: Use cases. Compare, when the other tool is the real job: security automation.

Audit Trail inputs

Persist the filtered payload (the contract), not the PCAP you refused to POST:

{
  "alert": { "id": "SOC-1902", "text": "Impossible travel + new OAuth grant on finance-sso; user says travel is unexpected." },
  "asset": { "tier": "prod-idp", "owner": "identity" },
  "evidence": { "ioc_hits": 0, "enrichment_ok": true, "summary": "No hash match. New grant to unknown app. Last login US-East 40m earlier." },
  "policy": { "isolate": "Auto-isolate only if evidence_ok and asset.tier is not shared-idp.", "evidence_min": "Need either IOC hit or named user contradiction plus enrichment_ok." }
}

Redact tokens, cookies, and password material before the object hits cold storage. Hash the evidence summary if you must prove integrity without retaining raw IOC strings.

Decision signals and actions

Minimum fields:

• alert id + asset tier
• ioc_hits + enrichment_ok (code facts)
• model pin + question SHA + policy SHA
• answers + full probabilities map
• abort reason (abort_thin_evidence, abort_policy, analyst_queue, …)
• SOAR action id or explicit not_fired

Argmax-only logs cannot explain a close evidence_ok Noul. Also store usage.input_tokens (vendor meter).

Do not treat a Noul of 0.5 as a “medium” security containment-abort score — it means yes and no are equally likely. Conjunctions stay in your code.

Guardrails and escalation

If you cannot explain isolating a host or disabling a credential from the trace — including why abort did not fire — you are not ready to auto-act. TypeSafe’s confidence-gated examples use a lower bar for recoverable reads than for irreversible actions. Those numbers are illustrations. For security containment-abort, treat auto_isolate_host as the high bar (isolating a host or disabling a credential). Tune on labels — see offline evaluation.

Evaluation and rollout notes

Traces are the eval warehouse. Replay against abort-reason gold from analysts, evidence_ok gold, and whether isolate was justified after criteria or alias changes. Pin jev-1.13.0 (the versioned id) after you fit thresholds. jev-latest and the marketing line jev-1.13 can move. Log the response model. TypeSafe’s published list price for jev-1.13 is $0.042 per million input tokens (vendor claim — confirm on the models page); output tokens are free on that same page. Unused distractors still bill as input.

Official Python and JavaScript SDKs read TYPESAFE_API_KEY and retry documented 429/529. This site does not sell, issue, or proxy TypeSafe keys. Use a credential you already have from the console or a documented gateway.

Pack map

FAQ

Is the HTTP log enough? No. Persist the filtered state, full probabilities, floors, abort reason, and downstream SOAR action as a decision trace.

May I log raw tokens or malware bytes? Redact in code. Jev will not be your DLP layer. See security guide.

Where is the rest of the Security pack? Start with Security human handoff and Security evaluation. Cluster hub: Use cases.

Is this the LLM guardrails cookbook? No. Guardrails screen prompts and completions. This pack aborts containment when evidence or policy is thin. See LLM guardrails.

If IOC hits are already ≥ 1, should we wait for Jev? No. Deterministic contain wins. Jev is for leftover messy narrative.

What this page does not claim

• Not a SIEM, SOAR, EDR, or certified safety filter.
• No MTTD / MTTC benchmarks.
• Not official TypeSafe.
• Official TypeSafe status, or that jev.pro issues API keys.
• That a schema-constrained answer is automatically factually correct.

Disclaimer

This is an independent unofficial site and is not affiliated with TypeSafe AI; official documentation is available at https://docs.typesafe.ai.

Primary documentation: https://docs.typesafe.ai. Hub: Use cases.