Security human handoff 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 human handoff slice of the security containment-abort pack. Intent: apply the Jev (TypeSafe System One) decision model to security containment-abort human handoff. Primary search language: Security Jev human handoff. 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
Handoff is a first-class outcome for security containment-abort, not a failure of Jev. When the abort gate cannot auto-act, an analyst sees a packed evidence bundle — not a chat transcript. We do not ask Jev to write the reviewer essay. See human handoff.
Hub: Use cases. Compare, when the other tool is the real job: security automation. Reviewer questions: questions for security.
Human Handoff inputs
Humans should see what the model saw (filtered), not the SIEM dump you correctly 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." }
}Decision signals and actions
| Signal | Typical reason enum (you name it) |
|---|---|
contain_class other / low confidence |
analyst_queue |
evidence_ok below τ |
abort_thin_evidence |
policy_allow below τ |
abort_policy |
asset.tier == shared-idp |
abort_shared_idp |
| enrichment timeout | abort_enrich |
These are application outcomes next to HTTP 200, not invented TypeSafe status codes.
Send the analyst:
- alert id + filtered narrative
ioc_hits+enrichment_ok(code facts)- answers + full probabilities
- abort reason already applied (or not)
- proposed contain class not executed
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
Do not page humans on a single Score unless your conjunction says so. Pair with confidence thresholds. 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
Write the gold label (and the abort reason the analyst kept or overrode) back into the offline set. That is how floors move. 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
| Slice | Page |
|---|---|
| Graph and primitives | decision workflow |
What may enter state |
input contracts |
| What to gather first | evidence collection |
| Atomic rules | policy checks |
| Act / review / abstain | confidence thresholds |
| Reviewer payload | you are here |
| What to persist | audit trail |
| How it breaks | failure modes |
| Labeled replay | evaluation |
| Shadow → canary | production rollout |
FAQ
Is handoff a Jev failure? No. It is a first-class outcome. Abstention is “no auto action”; handoff is the queue you send that case to (glossary). Abort is the security-specific flavor: isolate did not fire.
Should Jev draft the analyst note? No. Send structured answers and the abort reason. Generation is the wrong job.
Where is the rest of the Security pack? Start with Security confidence thresholds and Security audit trail. 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.
Sources
Public TypeSafe or adjacent documentation only. No private claims.