DESIGN-SIDE EVIDENCE
ED25519 SIGNED
Prove which version of the rule you built against.
A year later, the hard question is not what your control says. It is which version of the obligation it was designed to answer. Control attestation signs both together and pins the obligation to the exact text that was current on the day.
Creating a record needs a subscription. Verifying one is free and needs no account.
START FREE TRIAL →
VERIFY A RECORD →
WHY IT MATTERS
Control mappings usually live in a spreadsheet with a rule name and a date. When the rule is amended, that mapping quietly stops meaning what it meant, and there is no way to show which wording the control was built against. Pinning the obligation version at signing turns that into something you can hand to a reviewer.
How control attestation works
You supply the control. The registry supplies the pinned obligation versions and the signature.
01
Describe your control
You send your own control: its identifier, the statement of what it does, who owns it, its status and effective date, and an optional reference to where your evidence lives.
02
Map it to the obligations it answers
You name the registry obligations the control is meant to satisfy. Each one is pinned at signing time to the exact version and integrity hash that was current, so the record captures what you actually relied on.
03
Get back a signed record
The record is signed with the same published Ed25519 key used for the rest of our signed records. Anyone you hand it to can verify it offline against that key, with no Bidda account.
What the record holds
Three parts, signed together so none of them can drift apart later.
YOUR CONTROL
What you said you built
The control identifier, statement, owner, status, effective date and evidence reference exactly as you supplied them. Bidda does not author or assess your control.
THE OBLIGATIONS
What it was mapped to, at that version
Each obligation you mapped, pinned to the version and integrity hash current at signing. If the obligation later changes, the record still shows which text the control was designed against.
THE SIGNATURE
Proof the record has not moved
An Ed25519 signature over the record, verifiable against our published key. Retired keys stay published, so older records keep verifying after a key rotation.
WHAT A CONTROL ATTESTATION IS NOT
You author the control statement and you choose which obligations it maps to. Bidda signs what you supplied and pins the obligation versions. It does not review, score or approve your control, and a signed record is not a determination that the control is adequate or that your organisation is compliant. It is evidence of what you designed and which text you designed it against, for a qualified reviewer to weigh.
Call it from anywhere
Available as an MCP tool and a REST endpoint. A free trial counts.
MCP TOOL
create_control_attestation
Call it directly from an agent framework that speaks MCP.
REST ENDPOINT
POST /api/v1/control-attest
Fetch and re-verify any record by its id. That read is public.
Want to know when an obligation you signed against has since moved? Pair this with the obligation change feed.
OBLIGATION CHANGES →
COMMON QUESTIONS
What is a control attestation?
It is a signed record of your own control and the registry obligations you mapped it to, with each obligation pinned to the version and integrity hash that was current when you signed. It captures the design-side of your programme: what you built, and which text you built it against.
How is this different from a signed decision record?
A signed record captures a decision an agent or a team actually made at a moment in time. A control attestation captures the design instead: the control you put in place and the obligations it was meant to answer. Many teams use both, one for what was decided and one for what was designed.
Does Bidda assess or approve my control?
No. You author the control statement and you choose the mapping. Bidda signs what you supplied and pins the obligation versions. It does not review, score or approve the control, and a signed attestation is not a determination that the control is adequate or that you are compliant.
What happens when an obligation changes after I sign?
The record keeps pointing at the version you signed against, which is the point. It shows what the control was designed to answer at that date. To find out which of your mapped obligations have moved since, pair it with drift check or the obligation change feed.
Can someone verify the record without a Bidda account?
Yes. Creating a record needs an active subscription, but verifying one does not. A record can be fetched and re-verified by its identifier, and the signing keys are published so a recipient can check the signature offline with their own tooling.
How do I call it?
Control attestation is available as the create_control_attestation tool over MCP and as a REST endpoint. Pass your Bidda key as api_key. A free trial counts.
Sign the mapping while it is still true.
Control attestation is included with every subscription and a free trial counts. Verification stays free for whoever you hand the record to.
START FREE TRIAL →
SIGNED RECORDS →