Understand what Nore can observe.
Follow the boundary between the agent, its unsigned proposal, the policy decision and the simulated result.
The adapter defines what the run can verify
Nore records and evaluates tool turns that pass through the configured step interface. The adapter should run in an isolated test environment without production signing credentials. Off-boundary activity is outside the report’s coverage.
Policy decisions use deterministic checks over fields such as chain ID, sender, recipient, amount and calldata. Supported operations are decoded. Unknown calldata and disallowed authority are rejected under the applicable rules.
Use unsigned proposals and disposable state
Mock runs use fixtures. Read-only RPC calls estimate or inspect supported behavior. Anvil can execute eligible cases on a disposable fork, with the chain and pinned block recorded in the evidence. The fork RPC proxy rejects upstream transaction submission.
Access, endpoints and delivery
| Surface | Control |
|---|---|
| Workspace access | Server-side workspace isolation and owner, editor and viewer roles. |
| API and session | Scoped, revocable API keys stored as digests. One-time sign-in links and origin checks for browser writes. |
| Adapter and webhook secrets | AES-256-GCM encryption for external credentials. |
| Outbound requests | Approved HTTPS origins, exact endpoints, DNS pinning, public-address validation and redirect refusal. |
| Report sharing | An owner can issue a seven-day, revocable summary link. Detailed traces stay workspace-scoped. |
| Webhook delivery | Check HMAC-SHA256 over timestamp + "." + rawBody with AgentBench-Signature, then deduplicate AgentBench-Delivery. |
What an installation operator controls
Configure HTTPS and email delivery, protect the credential encryption key, restrict worker egress and verify backups and restore. Monitor database, queue and worker readiness and set retention for reports and audit records.
Report a suspected security issue privately to the installation operator with affected behavior and relevant run IDs. Avoid attaching keys or unredacted payloads.