Docs
relyance.ai ↗
Browse docs

Audit Log and Reporting

Updated November 4, 2026View as Markdown ↗

Audience: compliance teams, auditors, and risk owners preparing for a risk review or an audit.

What's captured

Every change to a register risk is recorded with the user who made it and a timestamp. The audit log records:

Event What's recorded
Risk created The new risk, by name
Risk updated One entry per field changed, with the field name and its before and after values - title, description, status, review status, owners, scores, treatment, categories, applies-to, and so on
Control linked / unlinked The control and its framework
Policy linked / unlinked The policy, and whether it was enabled as part of linking it
Risk deleted The risk's name at the time it was deleted

A save that changes nothing creates no entry, so the log only shows real changes.

Where to see it

  • On a single risk - open the risk and select the Audit Logs tab. A risk with no changes yet says No changes recorded for this risk yet.
  • Across the platform - risk register events also appear in the platform-wide system audit log alongside other modules, so you can review register activity next to changes to policies, assessments, and inventory.

Provenance: sources

Separately from the change log, each risk keeps its Sources - every place that backs it:

Source Meaning
Risk library Added from a library scenario
Imported Brought in from an uploaded register or document
Assessment Raised by, or added to from, an assessment's answers - the risk links back to the assessment and the questions it was read from
Added manually Created by a person in the register, shown with who added it and when

When an assessment or import names a risk you already have, it's added as another source on that risk rather than as a duplicate. A risk backed by three assessments therefore shows all three, which is useful evidence that a risk was independently identified.

Reporting from the register

The register view is built for review meetings and audit walkthroughs:

  • Group by inherent risk, residual risk, status, treatment, monitoring, owner, source, or assessment. For example, group by Residual risk to show what's left after treatment, or by Owner to run a review owner by owner.
  • Filter to the slice you're reporting on and use Hide closed risks to focus on what's open.
  • Review status (Draft, In review, Changes requested, Approved) records where each risk stands in your review cycle.
  • Monitoring shows which risks Relyance is actively checking and how many open issues each has.

The Risks & Issues → Dashboard tab complements the register with issue-level views - open issues by category and data classification, top risky assets and identities, and obligation exposure.

AI use case compliance packages

When you export a compliance package for an AI use case, it includes a Risk Register CSV of the register risks that apply to that use case, next to its assessments and other evidence. The use case's Risks & Issues card shows the same risks in the product.

FAQ for auditors

Q: Can a risk's history be edited or removed?
A: No. Audit entries are written by the platform when a change is saved; they aren't editable in the product.

Q: What happens to the history when a risk is deleted?
A: The deletion itself is logged. Because deleting can't be undone, set a risk to Archived instead when you need it to stay visible for an audit period.

Q: How do I show that a risk was assessed before treatment?
A: The risk keeps separate Inherent risk and Residual risk scores, and the audit log shows when each was set or changed and by whom.