Use cases· Last updated

Security production rollout 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 production rollout slice of the security containment-abort pack. Intent: apply the Jev (TypeSafe System One) decision model to security containment-abort production rollout. Primary search language: Security Jev production rollout. 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

Production rollout for security containment-abort is Operate-pillar work: pin, shadow, canary, abort. It is not a launch-checklist clone of a rival “build with System One” guide — we only talk about this pack’s blast radius (isolating a host or disabling a credential).

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

Production Rollout inputs

Ship the contracted payload, the pinned id, and a documented safe default when the API is unavailable:

{
  "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

Stage What changes Security rule
Shadow Nothing host-visible SOAR plays unchanged; log Jev contain_class + abort reason.
Canary One low-blast slice auto-acts Auto-tag ticket_only on one detector family; isolate/disable stay human or IOC-deterministic.
Abort Auto-act off Policy or evidence-min change → freeze auto_isolate_host; replay on the pinned id.

Keep the workflow code you already designed:

def contain_gate(ans, ioc_hits, enrichment_ok, asset_tier):
    if not enrichment_ok:
        return "abort_enrich"
    if ioc_hits >= 1 and asset_tier != "shared-idp":
        return "soar_isolate"
    if ans["evidence_ok"].noul < T_EVIDENCE:
        return "abort_thin_evidence"
    cls = ans["contain_class"]
    if cls.confidence < FLOOR or cls.choice == "other":
        return "analyst_queue"
    if ans["policy_allow"].noul < T_POLICY:
        return "abort_policy"
    if cls.choice in ("isolate_host", "disable_cred") and asset_tier == "shared-idp":
        return "abort_shared_idp"
    return f"soar:{cls.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.

Guardrails and escalation

Safe default if System One errors or confidence is low: do not isolate a host or disable a credential. 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

Promotion gate = evaluation green on the pinned id + audit traces for the canary. Never promote isolate from Jev until planted thin-evidence canaries abort. 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 human handoff
What to persist audit trail
How it breaks failure modes
Labeled replay evaluation
Shadow → canary you are here

FAQ

Can I ship on jev-latest? 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. Shadow first.

What is the safe default if System One is down? Fail closed on isolating a host or disabling a credential. Do not guess. IOC-deterministic SOAR can still fire in code.

Where is the rest of the Security pack? Start with Security evaluation and Security confidence thresholds. 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

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.