Evaluate C=US
Independent evaluators can audit the C=US agent control plane end to end: hardware-key enrollment, agent registration, the c=US and c=CA directories, and the relying parties that consult them. Access follows the pattern AI labs use with outside evaluators: an agreement with your organisation, a time-boxed and tiered access code, and your own hardware security key.
How access works
- Your organisation signs an engagement agreement with C=US naming you, your access level and the dates.
- You register below from your organisation email address, and name a contact there who can confirm you.
- The administrator confirms you with that contact and sends your access code by a separate route.
- You open the evaluator page, enter the code and set up your YubiKey with PIN and touch. The code is bound to that key: it is useless to anyone else once you have used it.
- You register test agents in the c=US or c=CA directory (evaluation branch) and call agents.cequs.com and the sugarbushagent.com edges as a peer, with certificates C=US issues for keys on your own device.
Access levels
| Level | What it allows |
|---|---|
| Standard | Run enrollment, login and agent registration in the evaluation branch, and test the result |
| Elevated | Standard, plus read the issuance records and the evaluator session log |
Codes last at most 30 days and can be withdrawn. Every evaluator session is logged.
What you need
- A YubiKey from any seller, with a PIN (the setup window will ask you to create one if it has none).
- An email address at your organisation, and a contact there with the same email domain.
- Optional: an identity-validated certificate from a public CA. If you hold one, tick the box below and we will ask you to sign your request with it, for stronger proof of identity.
Evaluator terms
- Purpose. You are evaluating the C=US agent control plane: security-key enrollment, agent registration, the c=US and c=CA directories, and the relying parties that consult them. You are not a pilot participant, and nothing you register grants real authority.
- Access. An administrator approves your request by hand and sends you an access code. It lasts at most 30 days and carries one access level. Standard: run enrollment, login and agent registration, and test the result, including the sugarbushagent.com edges as relying parties. Elevated: standard, plus read the issuance records and the evaluator session log.
- Where you may test. Only the evaluator page on cequs.com and the entries it creates in the evaluation branch of each directory (
ou=Evaluation). Do not touch pilot participants' entries, and do not load-test or attack the servers. Agents you register stay in the evaluation branch and are never granted authority over real lots. - Logging. Your sessions are logged: when you unlock the page, enroll, log in and register agents, under your code's identifier.
- Confidentiality. Do not publish personal data you happen to see, or private keys, secrets or exploit details for an unfixed vulnerability. Report vulnerabilities to the administrator first; they are recorded in the project's defect log.
- Publication. You may publish your findings. The administrator may review a draft only to correct factual errors and to redact the material in section 5; you decide the final text.
- Transparency. You may always disclose, without the administrator's consent: that this evaluation took place, your access level and dates, these terms, and whether anything was redacted.
- Ending. Either side may end the evaluation at any time; your code stops working when it expires or is withdrawn.