Docs

Console

Audit log

An immutable record of every operator action in the RenLayer Console, who changed what, when, and why, for compliance, incident response, and internal review.

The audit log records every operator action in the console: agent created, key minted, key revoked, policy edited, DLP pattern added, body unmasked, role changed. It is append-only, time-ordered, and tenant-scoped.

What gets recorded

Every action that changes state or reveals sensitive data:

  • Agents: created, deleted, upstream edited, rate limit edited.
  • API keys: minted, revoked.
  • Policies: created, edited, disabled, enabled, rolled back.
  • DLP: patterns created/edited/disabled, severities changed, allow-list entries added/removed.
  • Sessions: body unmasked, export generated.
  • Settings: tenant defaults changed, roles assigned.
  • Authentication: sign-ins, failed sign-ins, OTP verifications.

Read-only browsing is not recorded, the audit log is for change and disclosure, not pageviews.

Schema

Each entry includes:

  • When: UTC timestamp.
  • Who: operator email and role at the time of the action.
  • What: the action type (e.g. policy.update).
  • Where: the resource ID affected (e.g. the policy ID).
  • Diff: for edits, a structured before/after of the changed fields.
  • From: the IP address and user agent the action came from.

The page supports filters for operator, action type, resource type, time window, and a free-text search over the diff. Common queries:

  • “Show me every policy edit in the last 30 days.”
  • “Show me every key revocation by a specific operator.”
  • “Show me every body reveal for a specific agent.”

Compliance use

The audit log is built to support change-tracking and least-privilege review workflows that compliance and security teams typically need during audits. Exports are JSON or CSV; both are deterministic so you can hash and archive them externally.

Immutability

Entries cannot be edited or deleted from the console or via the Platform API. Retention is configurable per tenant (default: 13 months); when an entry ages out it is removed wholesale. The audit log itself records when retention boundaries fire so the chain remains explainable.

Where to go next

  • Sessions: for agent action history (a separate stream).
  • Multi-tenancy: how scoping works across the platform.
  • Policies: the resource type with the most audit traffic.

Last updated: