How RepSec works

The trust precondition

RepSec adds a policy-bound trust condition at a control point. Live data presented with the required evidence can proceed; a copied or replayed payload without valid evidence can be declined.

Accepted path

1. The producer associates the asset with the agreed policy context.
2. The request reaches the selected enforcement point with its attestation.
3. The enforcement point validates the evidence and current policy condition.
4. If the condition is satisfied, the request is accepted and the decision is recorded.

Declined path

1. A copied or replayed payload reaches the enforcement point.
2. The required attestation is missing, invalid or no longer permitted by policy.
3. Validation fails and the request is declined with an auditable reason.

What to demonstrate

A useful demonstration shows both paths, a policy change or revocation, and the resulting evidence record. Any performance observations must come from the agreed evaluation environment rather than simulated counters.