Live-Presence Authorization Demo

Enrollment / User

Derived ECG Template

operator-014Raw waveform stored: false

Protected Asset

Demo Mode

Simulation Controls

Checks Running

Scenario-Specific

Both ECG and pulse signals are present for the same access attempt.

The system checks whether the two signals behave like one live body.

Demo Mode

Compare the current ECG features to the selected user's enrolled ECG template.

Use the ECG match score as an identity signal before issuing access.

Blood-Flow / PPG Path

Is a downstream pulse / blood-flow signal present?

Does each ECG heartbeat line up with a later pulse signal?

Is the ECG-to-pulse delay in a believable human range?

Does that delay vary naturally from beat to beat?

Asset Policy

If this check fails, the selected asset uses its configured fail-secure response.

Common Security Pipeline

Is the ECG clean enough to trust for a security decision?

Can we find real heartbeat events in the ECG trace?

Do the heartbeat intervals vary like a live person instead of a recording?

Does the sensor contact look physically plausible?

Does the signal show signs of replay, injection, or synthetic generation?

Does this result satisfy the policy for this exact asset?

Create a short-lived signed token bound to this user and asset.

Add the event to a hash-chained audit log for later review.

How to read the demo

Run a test to see the full authorization chain.

Choose a user, asset, demo mode, and signal scenario. The system will score live presence, apply the asset policy, issue a signed assertion, simulate downstream integrations, and write an audit record.

Decisionwaiting

Live Confidence--

ECG Identity--

Coupling--

Signal Evidence

Run an access attempt to show ECG, PPG, and timing evidence.

Policy Result And Reason Codes

The decision path and reason codes will appear here after a test.