Nodra
Menu
SECURITY EVIDENCE

Nodra Evidence Store

Nodra preserves workspace-scoped runtime evidence for agents, credentials, incidents and security decisions.

Documentation Security model

Implementation checklist

Complete these steps in the customer-owned server or agent runtime.

  1. Agent and event records are workspace-scoped.
  2. Integration secrets are stored as one-way hashes.
  3. Security events retain sequence and hash-chain evidence.
  4. Credential use updates runtime evidence and last-used state.
  5. Authenticated console pages read only the active workspace context.

Security boundary

Nodra infrastructure credentials are never required in browser code and must never be exposed client-side.

The public guide explains the integration contract without exposing Nodra's private control-plane implementation.

Reference implementation

Use this as the server-side starting point.

Runtime evidence includes:
- protected agent identity
- resource and action
- authorization decision
- sequence and integrity linkage
- execution outcome
- occurrence time

Ready to validate a real workflow?

Use the Demo Lab for a self-guided sandbox, or review the 7-day technical validation for a real design-partner workflow.

Explore safe Demo Lab7-day validation