Policy enforcement.

Dual control and approval policy shouldn’t live in a manual. Foundry enforces who must sign, blocks execution when they don’t, and proves policy was satisfied.

Book a demo

The scenario

Your policy says: two authorized signers for payee changes over $50k; finance controller plus treasury lead; separation of duties.

On Tuesday, AP updates a record after one email approval. Policy existed on paper, not at execution.

What goes wrong today

  • Policy lives in PDFs and training; enforcement is human memory.
  • Workflow tools record clicks, not cryptographically proven multi-signer approval.
  • Threshold and role rules are hard to prove after an incident.

What changes at execution

Foundry binds signing policy to the artifact: any-N or all-signers thresholds, role-qualified approvers, explicit deny paths.

Execution is blocked until the trust report shows policy satisfied, or records a provable violation.

Changes under policyExample data
ChangePolicySignedStatus
Payee change, $82,4002 of 2: Finance Controller, Treasury Lead0 of 21 of 22 of 2Challenge sentBlockedPolicy satisfiedReleased
Vendor contact changeAny 1 of 3: AP leads1 of 3Released
Wire template change2 of 2: Controller, Treasurer1 of 2Denied

01A payee change over the threshold arrives. Both role holders are challenged.02One signature is not the policy. Execution stays blocked.03The second role holder signs. The threshold is met.04The trust report shows the policy satisfied. The change executes.

Soft gate, hard gate

Configure request types and signing policies in a verification console; dispatch challenges to the right signers.

Embed the same rules via API in treasury, ERP, or ITSM so systems cannot bypass policy at runtime.

See it in action

Evidence for compliance

Trust reports document exactly which signers approved, which roles they held, and whether threshold rules were met.

Evidence auditors can verify independently.

See policy enforcement in a live demo

15 minutes. Live demo. No jargon required.

Book a demo