Contain. Recover. Retain the lineage.
The SessionDNA Immune System is deterministic by design.
The design and its boundary.
The self-healing SessionDNA Immune System within CISP is not artificial-intelligence, machine-learning, anomaly, behavioural, malware-signature (antivirus/IDS), or pattern-matching detection, and it is not an intrusion-detection system. It does not learn, score, guess, or match against a library of known-bad fingerprints. Replay and impersonation are caught deterministically, by cryptographic proof-of-possession verified on every request; the response — isolate the compromised session and heal a clean successor on the legitimate device — is engineered the way the human immune system neutralises a pathogen and restores the host, not the way a trained detector recognises one.
This is the owner-described design. Operationally, containment is bounded by explicit policy; recovery needs an authorised path, predecessor invalidation and verifiable lineage.
A clean successor means newly authorised session state, not a malware-free operating system. Session renewal is not automatically device-key rotation. Suspected key compromise requires a separate re-enrolment or recovery path.
See the session lifecycle under test.
Explore the boundary. Inspect the decision. Trace the recovery.