HOW KIN WORKS / CONTINUOUS PROOF TRUST
Conventional authentication establishes confidence at a point in time. kin implements Continuous Proof Trust by establishing machine and application provenance during provisioning, then continually renewing relationship-bound proof throughout operation.
Communications are encrypted and protected against tampering, cloning and replay, while ongoing authentication requires no stored, exchanged or managed reusable authentication artifacts. When trust changes, kin enables an operator-defined response.
Trust should be continually proven during the relationship.
Machines, software and connected infrastructure operate long after an initial login or handshake. Continuous Proof Trust (CPT) continually renews confidence in expected, provisioned participants and their communication relationships.
Authentication is an event. Trust is ongoing.
THE CONTINUOUS PROOF TRUST LIFECYCLE
Trust isn't granted once. It's continuously proven.
kin establishes provenance when machines join an approved relationship, protects their communications and continually renews proof that the participants remain the systems they claim to be.
01
Join
Provision the approved participants and establish their expected provenance.
02
Prove
Verify that the participating machines and applications match their approved relationship.
04
Renew
Continuously refresh relationship-bound proof as protected communications continue.
03
Protect
Encrypt communications using AES-256-GCM and apply packet-level anti-cloning and anti-tampering markers.
05
Respond
When provenance or trust changes, apply the response defined by the operator's policy.
THE ARCHITECTURAL DIFFERENCE
Remove the reusable credential target.
Traditional authentication frequently relies on credentials, tokens or certificates that must be stored, exchanged, managed and protected. When a valid authentication artifact is stolen, it can be presented by an unauthorized participant.
kin changes the architecture. Its ongoing authentication process does not store, exchange or manage reusable authentication artifacts. Instead, fresh, relationship-bound proof continually verifies that participating machines and applications retain their approved provenance.
CONVENTIONAL AUTHENTICATION
Possession proves access
A reusable credential can remain valid even when presented from an unauthorized machine or location.
kin / Continuous Proof Trust
The participant must prove itself
Fresh proof establishes confidence in the machine, its provenance and the specific approved relationship.
CONTINUOUS TRUST EVALUATION
Trust changes. The response is yours.
kin continually renews confidence in approved participants using their expected provenance, relationship history and relevant behavioural signals.
As those conditions change, trust may be renewed, degraded, suspended, recovered or terminated. These are trust states, not prescribed operational actions. The operator determines how systems respond according to the requirements of their environment.
TRUST STATES
Renewed · Degraded · Suspended · Recovered · Terminated
DESIGNED TO FIT
Three ways to integrate kin.
Continuous Proof Trust can be introduced into existing environments or embedded directly into new products. Start with the relationship that matters most, then expand as requirements evolve.
01
Protect a Selected Path
Apply kin to a specific machine-to-machine communication path where stronger provenance and continuously renewed trust are needed.
02
Work alongside existing controls
Introduce kin while retaining existing network security, identity and access controls where appropriate.
03
Integrate more extensively
Embed kin into products and architectures, or replace a suitable authentication approach as requirements and evaluation permit..
CONTINUOUS PROOF TRUST IN ACTION
See the difference in practice.
Architecture is one thing. Demonstrating how it behaves under attack is another.
Explore our technical demonstrations showing how kin responds to device cloning, packet replay and tampering, and man-in-the-middle attack scenarios. See how continuous provenance verification and protected communications change the security model.