ProtocolGovGuardFinGuardExplorerPlaygroundAdoptCloudTrustDocsRequest Pilot
Product / Government Control Pack

Government Control Pack

Pre-configured EP deployment for government fraud prevention.

Request Government Pilot

Included controls

The Government Control Pack includes pre-configured policies, signoff workflows, and evidence formats designed for government fraud prevention. Deploy against a single trust surface in weeks, not months.

Benefits payment redirect controls
Cryptographic handshake required before any payment destination change commits. The handshake binds the exact new destination, program, amount, and authorizing principal. No redirect executes without satisfied trust policy.
Operator override constraints
Every caseworker or system operator override produces a named signoff record. The signoff is bound to the exact action parameters, not a session-level approval. Override without accountability does not proceed.
IG/GAO-ready audit evidence
Every handshake, signoff, and execution event produces an immutable record. Evidence packages are pre-formatted for Inspector General and GAO examination. Action-level traceability, not session-level logs.
GovGuard pre-execution gate
New GovGuard product surface (POST /api/v1/trust-receipts) wraps benefit-bank-account changes, address changes, and caseworker overrides in observe / warn / enforce modes. See /govguard.
Roadmap (pilot-track)

On the way, not yet shipped.

The following capabilities are pilot-track work that we will scope as part of an active engagement. They are listed here because pilots frequently ask about them — not because they are deliverable today.

Government identity integration (PIV / CAC / Login.gov)
Pilot-track work; not yet implemented. Pilots needing PIV/CAC integration today should contact us — we will scope the work as part of the pilot.
FISMA / FedRAMP mapping
Control-family mapping documents are not yet published. EP trust enforcement satisfies action-level accountability requirements that map onto multiple NIST 800-53 controls; the formal mapping document is on the roadmap.

Best first workflow

Start with the highest-impact trust surface. For most government deployments, that is payment destination change.

Payment destination change
A benefits recipient, vendor, or disbursement target updates their bank account, routing number, or payment address. EP generates a cryptographic handshake binding the exact new destination, the requesting identity, the authorizing caseworker, and the applicable policy. If the handshake is not satisfied, the change does not execute. The signoff record is immutable and available to Inspector General auditors in real time.
+Handshake binds exact new destination, amount, and program
+Named caseworker signoff required before change commits
+Signoff is one-time consumable and replay-resistant
+Immutable event record available to IG and GAO auditors
+Policy defines which changes require signoff based on risk class

Request Government Pilot

EMILIA Protocol — Trust Before High-Risk AI Action