Edit Template

Industries Enterprise security

Check the action at the gateway, after identity.

A Trust Packet™ scopes each sensitive call to one action and one recipient, checked before the call runs.

For security architects who place a verifier in front of sensitive calls, and for vendors who would embed one.

Gateway checktp_31f8a2c6Illustrative
GET /v1/exports/example_dataset
Host: gateway.corp.example.com
Authorization: Bearer example_service_tokenidentity says who
Trust-Packet: tp_31f8a2c6.example_signature_onlythe packet says what
Content-Type: application/json

The header name is illustrative. The packet travels with the request on the channel it already uses.

APPROVEDChecked at the gateway before the call runs. Written to the ledger as al_000812. The export runs.

01 · Where it fits

After identity, check the action.

Your identity stack decides who is calling. A Trust Packet decides what this one call may do.

A sensitive call, like a data export, carries a packet scoped to one action and one recipient, and your gateway checks it before the call runs.

What the verifier checks

Who signed?
The calling service’s key, checked against its Authority Anchor.
What for?
This export, these records.
For whom?
This gateway only.
How many times?
Once. A replayed packet is refused.

02 · Approved and refused

The same action, approved and refused.

In scopetp_31f8a2c6
  1. Signatureagainst the Authority Anchor in DNSpass
  2. Time windowinside the short validity windowpass
  3. Not replayednonce not seen beforepass
  4. Audiencenamed for this recipientpass
  5. Scope and chainaction and limits inside what was signedpass
APPROVEDWritten to the ledger as al_000812. The export runs.
Export outside the signed scopetp_31f8a2c6
  1. Signatureagainst the Authority Anchor in DNSpass
  2. Time windowinside the short validity windowpass
  3. Not replayednonce not seen beforepass
  4. Audiencenamed for this recipientpass
  5. Scope and chainaction and limits inside what was signedrefused
REFUSEDThe records asked for are outside the signed scope. Written to the ledger as al_000813. The export does not run.
Authorization Ledgergateway.corp.example.comIllustrative
ChainRecordActionSenderVerdictCommits to
al_000812export_recordsreporting.corp.example.comAPPROVEDprev ex-5a10hash ex-b7e3
al_000813export_recordsreporting.corp.example.comREFUSED
Outside the signed scope
prev ex-b7e3hash ex-2c94
al_000814export_recordsreporting.corp.example.comREFUSED
Signed for another recipient
prev ex-2c94hash ex-d06f

Each record commits to the hash of the record before it, so a changed or missing row shows. Sample ids and hashes.

03 · Two readers

Place the verifier, or embed it.

If you run the gateway

Put the verifier in front of the calls that matter: exports, writes and payment calls.

Machine to machine

If you ship a security product

Embed the verifier in a control you already ship. It adds a per-action check and does not replace that control.

Answers for a vendor review

04 · Where the verifier sits

On top of what you run, in front of the action.

UniKey limits and contains what a stolen credential can do in this setting: one action, one recipient, one use.

05 · What it looks like

A sample packet for a scoped data export.

A reporting service asks to export records. The packet names the action, the service, the gateway and the scope.

The Trust Packet, field by field
Sample Trust PacketIllustrative
{
  "action": "export_records",
  "sender": "reporting.corp.example.com",
  "audience": "gateway.corp.example.com",
  "dataset": "example_dataset",
  "rows": "example_scope",
  "expires": "in a few minutes",
  "nonce": "example_nonce_31f8",
  "signature": "example_signature_only"
}

Sample fields, for illustration. RFC-2001 defines the required fields, and a deployment can add its own. Example domains and masked values throughout.

Pilot

Try it in a sandbox first.

No live customer data sits on UniKey systems.

A UniKey property. © 2026 Swoop In Technologies LLC

Edit Template