Zero Trust Engineering — Endpoint isolation and quarantine

/02 About

Devices and endpoints engineering reference for endpoint isolation and quarantine, including policy, logical interfaces, recovery and assurance.

Purpose: Endpoint isolation and quarantine. Domain: Devices and endpoints. Family: decision. Scenario trigger: Receive device quarantine authorization. Input assurance: Risk classification, device identity and access topology. Evaluation: Determine scope of isolation and allowed remediation channels. Governing policy: Quarantine exemptions, duration and release policy. Resource-side obligation: Block nonessential traffic while retaining approved repair path. Protected concern: Quarantined endpoint segment. Logical interface: Device isolation scope permitted repair channels expiration and verification. Evidence: Isolation decision, applied control and release evidence. Failure: Containment bypass or quarantine that blocks recovery. Required recovery: Escalate containment and open restricted recovery channel. Architectural invariant: Quarantine is a reversible controlled state, never only a network label Adoption: replace reference roles with concrete owner-controlled services. Specify exact provider/consumer identities, schema fields and classifications, signal provenance and freshness, idempotency, authorization lifetime, timeout/retry limits, observation and tamper evidence. A denied or failed operation must not silently become a permitted one. Scope: original vendor-neutral, implementation-agnostic technical reference model. Illustrative logical components and behaviors are neither a deployed system nor evidence of regulatory compliance. Package identities remain stable within the package; cross-package semantic reconciliation requires separate explicit registry support.

Curated · other · unspecified · Published by Lattix · 28 elements · 34 relationships · validated on publish