Overview and Implementation Guide
About this document set
This is the entry point to the Relyance Risk Register documentation. Start here, then branch out to the guide that matches your role:
| Document | Audience | What's in it |
|---|---|---|
| Overview and Implementation Guide (this doc) | Everyone | What the Risk Register is, how risks, controls, policies, and issues connect, and a rollout plan |
| Admin Configuration Guide | Risk owners, GRC, privacy, security, and AI governance teams | Adding risks, scoring and treating them, mapping controls, linking monitoring policies, and working the register day to day |
| Legal and Compliance Guide | Legal, compliance, and audit teams | The risk-management requirements the register supports and what its records demonstrate - no UI steps |
| Audit Log and Reporting | Compliance, auditors, risk owners | What's captured for every risk, where to see it, and how to report on the register |
| Scoring and Risk Library Reference | Everyone | The scoring scale and bands, every status and treatment value, and what the risk library covers |
| FAQ: Risk Register | Prospects, new customers, sales and CS | Common questions in plain language |
What is the Risk Register?
The Risk Register is where your organization records the risks it has decided to manage - privacy, security, AI, and third-party - and where Relyance keeps watch over them. Your team defines and owns each risk: its scenario, its likelihood and impact, its owner, and how you plan to treat it. Relyance then does the work that usually falls apart between a spreadsheet register and the systems it describes:
- Maps each risk to controls - the clauses of GDPR, ISO/IEC 27001, the EU AI Act, and your other frameworks that address it.
- Monitors it with policies - Policy Center policies check those controls against your data, systems, and AI, and you link them to the risk.
- Surfaces live issues - once a policy is linked, the risk is Monitored by Relyance and the policy's open issues show on the risk, scoped to what the risk applies to, each with remediation steps.
You find it under Risks & Issues → Risk Register, next to the Dashboard and Issues tabs.
| Link in the chain | Who owns it | What it is |
|---|---|---|
| Risk | Your team | A scenario - what could go wrong and what it would lead to - with scores, owner, treatment, and status |
| Control | Your frameworks | A clause of a regulation or standard that addresses the risk, marked as already in place or as planned treatment |
| Policy | Relyance | A check that runs against your environment and tests whether a control holds |
| Issue | Relyance | A live finding raised by a linked policy, with remediation steps, that can open a ticket in your tracker |
How the pieces fit together
Getting risks in. You rarely start from a blank page. There are five ways to add risks, and every one of them shows you a draft before anything is saved:
- From the risk library - about 90 common privacy, security, AI, and third-party risk scenarios, each already scored, mapped to controls, and given a suggested treatment. The Suggested view shows the ones that map to frameworks you have enabled.
- By importing your existing register - attach a CSV or Excel export from a spreadsheet or another GRC tool. Relyance maps its columns onto the register's fields and brings in every row.
- By describing them - type a sentence ("risks of storing customer support transcripts in a third-party LLM") or attach a policy, audit report, or assessment, and Relyance drafts the risk scenarios it names.
- From an assessment's answers - on a completed assessment, Relyance reads the answers and proposes the risks they raise.
- By hand - one risk at a time with the manual form.
Avoiding duplicates. When a drafted risk describes the same scenario as one already in your register, Relyance says so and offers to add the new source to the existing risk instead of recording it twice. A risk keeps every source that backs it - library, import, assessment, or manual.
Scoring. Each risk has an inherent score (the risk as it stands) and a residual score (what's left once treatment is in place). A score is likelihood × impact on a 5 × 5 scale, banded Low, Medium, High, or Critical. See the Scoring and Risk Library Reference.
Monitoring. On each risk, Relyance suggests the policies its controls map to. You can enable and link one in a click, link any other policy, or have Relyance create a new policy from the risk's description. A risk that no platform policy can check is tracked through its controls, treatment, and reviews instead.
Where risks appear elsewhere. Register risks also show up on the Risks section of a policy's detail drawer, on an AI use case's Risks & Issues card, and in an AI use case's compliance package export. That closes the loop from use case to assessment to risk and back.
The guided tour
The first time you open the Risk Register, an invitation card appears in the bottom-right corner: See how the Risk Register works. The tour takes about two minutes and walks through the whole chain on your own page:
- Your risks, monitored by Relyance - the risk → control → policy → issue chain and who owns each link.
- Start from the risk library - the Risk library button in the toolbar.
- Risks that fit your frameworks - the library's list of suggested risks.
- Each risk is mapped to controls - the framework clauses that come with a library risk.
- Controls are checked by policies - the policies for a risk, and how many issues they already find in your environment.
- Add them in bulk - adding every ticked library risk at once.
- A risk in your register - the risk drawer's header and details (shown when your register already has a risk).
- Relyance monitors the risk - the suggested policies on a risk, and creating one from its description.
- Issues, with steps to fix them - live issues on a monitored risk.
- Bring your own risks too - the Add risks button for imports and descriptions.
- Come back any time - the tour lives in the help menu.
The invitation stays until you finish the tour. You can restart it at any time from Help → Take a tour of this page while you're on the Risk Register.
Recommended rollout
Phase 1 - Seed the register
Owner: Risk owner or GRC lead. Open the Risk library, review the Suggested risks for your enabled frameworks, tick the ones that apply, and add them in bulk. If you already keep a register elsewhere, import it at the same time with Add risks. See the Admin Configuration Guide.
Phase 2 - Score, assign, and set treatment
Owner: Risk owners. Rescore library defaults to fit your organization, assign an owner to each risk, choose a treatment (Mitigate, Accept, Transfer, or Avoid), and record a residual score where treatment is in place. See Scoring and treatment.
Phase 3 - Turn on monitoring
Owner: Risk owners, with the policy owner where a policy needs enabling. On each risk, enable and link a suggested policy or create one from the risk. Work toward every open risk that can be checked on the platform being Monitored by Relyance. See Monitoring a risk.
Phase 4 - Connect assessments
Owner: Assessment owners. For completed DPIAs, vendor reviews, and AI assessments, use Assess risks… to pull the risks their answers raise into the register, so each risk records the assessment as a source.
Phase 5 - Review and report
Owner: Risk owners, ongoing. Use review status, grouping, and the per-risk audit log to run periodic risk reviews and to show an auditor what changed and when. See Audit Log and Reporting.
Who should read what
- New to the product or evaluating it? Start with this doc, then the FAQ.
- Building and running the register day to day? The Admin Configuration Guide is your reference.
- Legal, compliance, or audit? Read the Legal and Compliance Guide.
- Preparing for an audit or a risk review? Audit Log and Reporting.