Security confidence thresholds 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 confidence thresholds slice of the security containment-abort pack. Intent: apply the Jev (TypeSafe System One) decision model to security containment-abort confidence thresholds. Primary search language: Security Jev confidence thresholds. 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
Thresholds are a confidence threshold pair: Choice/Score confidence and Noul distance from 0.5. For this pack the distinctive axis is abort — evidence_ok below T_EVIDENCE is not “review later,” it is do not isolate. Official TypeSafe routing numbers are illustrations; fit on your labels.
Hub: Use cases. Compare, when the other tool is the real job: security automation.
Confidence Thresholds inputs
Fit floors against the same contract you ship:
{
"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
| Action | Typical second axis | Why |
|---|---|---|
ticket_only |
Lower Choice floor | Recoverable; analyst still sees it |
analyst_queue |
Mid-band Noul or other |
Ambiguous narrative |
abort_thin_evidence |
evidence_ok < T_EVIDENCE |
Missing pack — not a guess |
soar:isolate_host |
Highest Choice floor and both Nouls | Irreversible blast radius |
def threshold(ans, ioc_hits, asset_tier):
if ioc_hits >= 1 and asset_tier != "shared-idp":
return "soar_isolate"
if ans["evidence_ok"].noul < T_EVIDENCE:
return "abort_thin_evidence"
if ans["contain_class"].confidence < FLOOR_ISOLATE:
return "analyst_queue"
if ans["policy_allow"].noul < T_POLICY:
return "abort_policy"
return f"soar:{ans['contain_class'].choice}"
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. Choice confidence and Noul τ are not interchangeable (official jaggedness).
Guardrails and escalation
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.
Over-gating every ticket hides calibration and dumps the queue on analysts. Fit per action — ticket_only can be looser than isolate.
Evaluation and rollout notes
Fit loop: pin jev-1.13.0 → replay → plot error vs confidence → pick floors where auto-isolate error ≤ your SLA. 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 | you are here |
| Reviewer payload | human handoff |
| What to persist | audit trail |
| How it breaks | failure modes |
| Labeled replay | evaluation |
| Shadow → canary | production rollout |
FAQ
Should auto_isolate_host use 0.9 everywhere?
No. Over-gating hides calibration and dumps the queue on humans. Fit per action. Isolate is the high bar; ticket_only is not.
Can I reuse a Noul τ as Choice confidence? No. Jaggedness: they are not interchangeable. See confidence.
Where is the rest of the Security pack? Start with Security policy checks and Security human handoff. 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.