THE CISP PLATFORM

One protocol.
Verifiable session authority.

CISP connects device-bound request verification, BCCP trust evaluation and governed SessionDNA recovery.

SESSION LIFECYCLECONCEPTUAL VIEW / 01
LEGITIMATE DEVICEBound session key01 / REQUEST PROOFContext · freshness · possessionBLOCKCHAIN (BCCP)Consent + policy recordbccp://consent-recordCISPVERIFY + AUTHORISEREJECTInvalid protected requestPERMITValid + authorised actionSESSIONDNARecovery + lineage bccp://permit bccp://reject
DATA SOVEREIGNTY / FLIGHT TRACKERCONCEPTUAL VIEW / 02
ZONE UK-SOV-01CLIENTUK GATEWAYUK STORENON-ZONE✓ RESIDENCY: ALLOW✕ EXPORT: DENY BY DEFAULTEVIDENCE · bccp://consent-record bccp://data/uk-sov-01 bccp://data/blocked
ILLUSTRATIVE ARCHITECTURE · NOT LIVE TELEMETRY · DATA PATHS ARE CONCEPTUAL
CONNECTED ROLES

Make every responsibility explicit.

BCCP

Blockchain-Consent Protocol is the consolidated trust architecture within CISP. Permission semantics and revocation conditions belong to the integration profile.

Request verification

Validate signed context, proof of possession and replay handling before the protected operation.

SessionDNA

Apply bounded containment and authorised recovery, retaining predecessor/successor evidence.

SHARED RESPONSIBILITY

The application still owns its permissions.

Integrations must define protected operations, object and tenant permissions, session transitions, signature policy and recovery authority. A valid signature is not business authorisation.

Ledger semantics must distinguish pending and completed evidence. Every HTTP request need not imply a new consensus round.

START WITH THE SESSION

See the session lifecycle under test.

Explore the boundary. Inspect the decision. Trace the recovery.

Plan your evaluation ↗