--- title: Risk Register description: Read about what Risk Registers are, why they matter and how to file them in Copla Registry. --- [Skip to content](https://support.copla.com/risk-register#main-content) English Show submenu for translations [![main-black-pinkglasses](https://support.copla.com/hubfs/main-black-pinkglasses.svg)](https://support.copla.com/?hsLang=en) Open main navigation Close main navigation - English Show submenu for translations - [Contact us](mailto:support@copla.com) [Contact us](mailto:support@copla.com) How can we help you? - There are no suggestions because the search field is empty. 1. [Copla Help Center](https://support.copla.com/?hsLang=en) 2. [Core Guardian](https://support.copla.com/core-guardian?hsLang=en) 3. [General Instructions](https://support.copla.com/core-guardian?hsLang=en#general-instructions) # Risk Register ## Read about what Risk Registers are, why they matter and how to file them in Copla Registry. **Topics covered on this page:** - [Overview](https://support.copla.com/risk-register#RR1) - [How To Access It](https://support.copla.com/risk-register#RR2) - [Where Data Comes From](https://support.copla.com/risk-register#RR3) - [How To Find It](https://support.copla.com/risk-register#RR4) - [Register Asset Types](https://support.copla.com/risk-register#RR5) - [Creating a New Risk](https://support.copla.com/risk-register#RR6) - [Risk Table](https://support.copla.com/risk-register#RR7) - [Risk Table Column Descriptions](https://support.copla.com/risk-register#RR8) --- #### **Overview** A **Risk Register** is a simple, practical way to keep track of the main risks an organization faces, especially those that could affect compliance, day-to-day operations, or trust with customers. It helps teams understand what could go wrong, how serious it would be, and what is being done about it, so risks are managed intentionally rather than compliance being treated as a box-ticking exercise. --- #### **How To Access It** To view and manage the Risk Register, your user role needs to have the appropriate **Risk Register permissions**. Once those permissions are in place, you’ll be able to access and work with it normally. --- #### **Where Data Comes From** Assets from the Asset Register are **automatically included** in the Risk Register, so there’s no need to enter or duplicate the same information again. --- #### **How To Find It** You can access the Risk Register directly from the menu bar by selecting **Risks** on the left hand side.   ![2026-10-22 11\_57\_09-Chat \_ Justas Šukevičius (You) \_ Cyber upgrade UAB \_ justas.sukevicius@cyberupgr](https://support.copla.com/hs-fs/hubfs/2026-10-22%2011_57_09-Chat%20_%20Justas%20%C5%A0ukevi%C4%8Dius%20(You)%20_%20Cyber%20upgrade%20UAB%20_%20justas.sukevicius@cyberupgr.png?width=227&height=548&name=2026-10-22%2011_57_09-Chat%20_%20Justas%20%C5%A0ukevi%C4%8Dius%20(You)%20_%20Cyber%20upgrade%20UAB%20_%20justas.sukevicius@cyberupgr.png) --- #### **Risk Register Sections** There are 6 sections in the **Risk Register page** that help you understand the risks your company has and their impact: 1. **Count** - a breakdown by category of how many risks your company has 2. **Treatment** -  the status of how many risks are in a specific handling category **![2026-10-22 12\_01\_31-Chat \_ Justas Šukevičius (You) \_ Cyber upgrade UAB \_ justas.sukevicius@cyberupgr](https://support.copla.com/hs-fs/hubfs/2026-10-22%2012_01_31-Chat%20_%20Justas%20%C5%A0ukevi%C4%8Dius%20(You)%20_%20Cyber%20upgrade%20UAB%20_%20justas.sukevicius@cyberupgr.png?width=670&height=194&name=2026-10-22%2012_01_31-Chat%20_%20Justas%20%C5%A0ukevi%C4%8Dius%20(You)%20_%20Cyber%20upgrade%20UAB%20_%20justas.sukevicius@cyberupgr.png)** 3. **Trends** - an overview of your risk count throughout a selected time period 4. **Financial Potential Loss** - what loss could the risks cause to your company **![2026-10-22 12\_01\_44-Chat \_ Justas Šukevičius (You) \_ Cyber upgrade UAB \_ justas.sukevicius@cyberupgr](https://support.copla.com/hs-fs/hubfs/2026-10-22%2012_01_44-Chat%20_%20Justas%20%C5%A0ukevi%C4%8Dius%20(You)%20_%20Cyber%20upgrade%20UAB%20_%20justas.sukevicius@cyberupgr.png?width=670&height=256&name=2026-10-22%2012_01_44-Chat%20_%20Justas%20%C5%A0ukevi%C4%8Dius%20(You)%20_%20Cyber%20upgrade%20UAB%20_%20justas.sukevicius@cyberupgr.png)** 5. **Heat Map** - an overview of your risks in an easy to understand format![2026-10-22 12\_01\_52-Chat \_ Justas Šukevičius (You) \_ Cyber upgrade UAB \_ justas.sukevicius@cyberupgr](https://support.copla.com/hs-fs/hubfs/2026-10-22%2012_01_52-Chat%20_%20Justas%20%C5%A0ukevi%C4%8Dius%20(You)%20_%20Cyber%20upgrade%20UAB%20_%20justas.sukevicius@cyberupgr.png?width=670&height=261&name=2026-10-22%2012_01_52-Chat%20_%20Justas%20%C5%A0ukevi%C4%8Dius%20(You)%20_%20Cyber%20upgrade%20UAB%20_%20justas.sukevicius@cyberupgr.png) 6. **Table** -  a list of all the risks that have been entered/generated **![2026-10-22 12\_02\_44-Chat \_ Justas Šukevičius (You) \_ Cyber upgrade UAB \_ justas.sukevicius@cyberupgr](https://support.copla.com/hs-fs/hubfs/2026-10-22%2012_02_44-Chat%20_%20Justas%20%C5%A0ukevi%C4%8Dius%20(You)%20_%20Cyber%20upgrade%20UAB%20_%20justas.sukevicius@cyberupgr.png?width=670&height=369&name=2026-10-22%2012_02_44-Chat%20_%20Justas%20%C5%A0ukevi%C4%8Dius%20(You)%20_%20Cyber%20upgrade%20UAB%20_%20justas.sukevicius@cyberupgr.png)** --- #### **Creating a New Risk** Users can create **Risks** by: - Manually entering them one by one - Generate them with Copla AI from the assets that the company has uploaded ![2026-10-22 12\_16\_01-Chat \_ Justas Šukevičius (You) \_ Cyber upgrade UAB \_ justas.sukevicius@cyberupgr](https://support.copla.com/hs-fs/hubfs/2026-10-22%2012_16_01-Chat%20_%20Justas%20%C5%A0ukevi%C4%8Dius%20(You)%20_%20Cyber%20upgrade%20UAB%20_%20justas.sukevicius@cyberupgr.png?width=328&height=62&name=2026-10-22%2012_16_01-Chat%20_%20Justas%20%C5%A0ukevi%C4%8Dius%20(You)%20_%20Cyber%20upgrade%20UAB%20_%20justas.sukevicius@cyberupgr.png) --- #### **Risk Table** In the **Risk Table**, the risks are **displayed by the date they were added/generated**, and you can scroll to the side to see all the **details about the risks that have been entered/generated**.   By selecting **the 3 purple dots** to the left of the risk, you can **edit** the risk, **delete** it, **check** its history or **copy** it. ![2026-10-22 12\_11\_45-Chat \_ Justas Šukevičius (You) \_ Cyber upgrade UAB \_ justas.sukevicius@cyberupgr](https://support.copla.com/hs-fs/hubfs/2026-10-22%2012_11_45-Chat%20_%20Justas%20%C5%A0ukevi%C4%8Dius%20(You)%20_%20Cyber%20upgrade%20UAB%20_%20justas.sukevicius@cyberupgr.png?width=66&height=52&name=2026-10-22%2012_11_45-Chat%20_%20Justas%20%C5%A0ukevi%C4%8Dius%20(You)%20_%20Cyber%20upgrade%20UAB%20_%20justas.sukevicius@cyberupgr.png) --- #### **Risk Table Column Descriptions** | **ID** | **Column Name** | **Type** | **Logic description** | **Tooltip text** | | --- | --- | --- | --- | --- | | C-1 | Risk Date | • date• read-only | • The column is **pinned by default**. • The system sets the date when the risk record is created (format *yyyy-mm-dd*).• The value is not editable. | *Date when this risk was created.* | | C-2 | Risk Description | • text field | • The column is **pinned by default.**• A **required field** (marked with '\*' on UI; the system shows the error message if empty, the risk record can not be saved without a value).• Field limitation: 700 characters | *What could go wrong, written in clear business terms.* | | “*Risk*” **group** | | | | | | C-3 | Threat Description | • dropdown• single select | • A **dropdown component** displaying a list of potential threat descriptions.• The user can use search to find the relevant option• values are provided below the main table | *What could cause the risk to happen.* | | C-4 | Vulnerability Description | • dropdown• single select | • A **dropdown component** displaying a list of potential vulnerability descriptions.• The user can use search to find the relevant option• values are provided below the main table | *The weakness that makes this risk possible.* | | C-5 | Impact Description | • dropdown• single select | • A **dropdown component** displaying a list of potential impact descriptions.• The user can use search to find the relevant option• values are provided below the main table | *What would happen if the risk occurs.* | | “*Asset Criticality*” **group** | | | | | | C-7 | Confidentiality | • referenced field• read-only | • **Value options:** ◦ 3 (High) ◦ 2 (Medium) ◦ 1 (Low)• **Data source:** The value is populated from the *“Confidentiality”* **field** in the **Asset Dynamic Register**. ◦ For assets of **type 2 and/or type 3**, the system directly uses the asset’s confidentiality value. ◦ For assets of **type 1** (assets that belong to a subcategory and are not displayed individually in the Risk Register), the system assigns the **maximum** confidentiality value among all assets within the corresponding subcategory. | *How sensitive the affected information is.* | | C-8 | Integrity | • referenced field• read-only | • **Value options:** ◦ 3 (High) ◦ 2 (Medium) ◦ 1 (Low)• **Data source:** The value is populated from the *“Integrity”* **field** in the **Asset Dynamic Register**. ◦ For assets of **type 2 and/or type 3**, the system directly uses the asset’s integrity value. ◦ For assets of **type 1** (assets that belong to a subcategory and are not displayed individually in the Risk Register), the system assigns the **maximum** integrity value among all assets within the corresponding subcategory. | *How important it is that the information stays accurate and unchanged.* | | C-9 | Availability | • referenced field• read-only | • **Value options:** ◦ 3 (High) ◦ 2 (Medium) ◦ 1 (Low)• **Data source:** The value is populated from the *“Availability”* **field** in the **Asset Dynamic Register**. ◦ For assets of **type 2 and/or type 3**, the system directly uses the asset’s availability value. ◦ For assets of **type 1** (assets that belong to a subcategory and are not displayed individually in the Risk Register), the system assigns the **maximum** availability value among all assets within the corresponding subcategory. | *How important it is that the system or service is available when needed.* | | C-10 | Total | • calculated field • read-only | • Automatic calculation• Calculation Formula: **C-7 + C-8 + C-9**• The field automatically **recalculates** whenever any of the source fields (C-7, C-8, C-9) are updated.• If any of the source fields are empty or missing, the calculated field remains **empty**. | *Overall importance of the affected asset or process.* | | “*Impact and Likelihood*” **group** | | | | | | C-11 | Financial Impact | • dropdown• single select | • **Value options:** ◦ 3 (High) ◦ 2 (Medium) ◦ 1 (Low) | *Potential financial loss if the risk occurs.* | | C-12 | Regulatory/Legal/Compliance Impact | • dropdown• single select | • **Value options:** ◦ 3 (High) ◦ 2 (Medium) ◦ 1 (Low) | *Possible regulatory, legal, or compliance consequences.* | | C-13 | Reputational Impact | • dropdown• single select | • **Value options:** ◦ 3 (High) ◦ 2 (Medium) ◦ 1 (Low) | *Possible damage to trust or reputation.* | | C-14 | Operational Impact | • dropdown• single select | • **Value options:** ◦ 3 (High) ◦ 2 (Medium) ◦ 1 (Low) | *Disruption to daily operations or service delivery.* | | C-15 | Customer Impact | • dropdown• single select | • **Value options:** ◦ 3 (High) ◦ 2 (Medium) ◦ 1 (Low) | *Impact on customers or end users.* | | C-16 | Total Impact | • calculated field • read-only | • Automatic calculation. • Calculation Formula: **C-11 + C-12 + C-13+ C-14 + C-15**• The field automatically **recalculates** whenever any of the source fields (C-11 + C-12 + C-13+ C-14 + C-15) are updated.• If any of the source fields are empty or missing, the calculated field remains **empty**. | *Overall severity of the impact if the risk occurs.* | | C-17 | Likelihood | • dropdown• single select | • **Value options:** ◦ 3 (High) ◦ 2 (Medium) ◦ 1 (Low) | *How likely it is that this risk will happen.* | | “*Inherit Risk Level*” **group** | | | | | | C-18 | Risk Score | • calculated field • read-only | • Automatic calculation. • Calculation Formula: **C-17 x C-16 x C-10**• The field automatically **recalculates** whenever any of the source fields (C-17 x C-16 x C-10) are updated.• If any of the source fields are empty or missing, the calculated field remains **empty**. | *Overall risk score based on impact and likelihood.* | | C-19 | Risk Level | • calculated field • read-only | • Automatic calculation. • Mapping: ◦ If **C-18** value is between 15 and 180 → assign 1 (Low); ◦ If **C-18** value is between 181 and 360 → assign 2 (Medium); ◦ If **C-18** value is greater than 360 → assign 3 (High). • The value updates dynamically whenever the **C-18** value changes. | *Risk level shown as Low, Medium, or High.* | | “*Risk Treatment*” **group** | | | | | | C-20 | Risk Treatment Action (Decision) | • dropdown• single select | • **Value options**: ◦ Accept ◦ Mitigate ◦ Transfer ◦ Avoid (Stop the activity) | *How you plan to handle this risk.* | | C-21 | Existing Controls | text field | • Field limitation: 700 characters (MVP concept) | *What is already in place to reduce this risk.* | | C-22 | Proposed Treatment / Control | text field | • Field limitation: 700 characters (MVP concept) | *What you plan to implement to reduce the risk further.* | | C-23 | Responsible Team/function | text field | • Field limitation: 700 characters (MVP concept) | *Team responsible for managing this risk.* | | C-24 | Due Date | • date• date picker | • Users can pick the date from the date picker or insert it manually.• Format (*yyyy-mm-dd*).• The date should not be before the **C-1** date. | *When the planned actions should be completed.* | | “*Residual Risk (after Treatment)*” **group** | | | | | | C-25 | Financial Impact | • dropdown• single select | • **Value options:** ◦ 3 (High) ◦ 2 (Medium) ◦ 1 (Low) | *Financial impact after planned actions are applied.* | | C-26 | Regulatory/Legal Impact | • dropdown• single select | • **Value options:** ◦ 3 (High) ◦ 2 (Medium) ◦ 1 (Low) | *Regulatory or legal impact after planned actions are applied.* | | C-27 | Reputational Impact | • dropdown• single select | • **Value options:** ◦ 3 (High) ◦ 2 (Medium) ◦ 1 (Low) | *Reputational impact after planned actions are applied.* | | C-28 | Operational Impact | • dropdown• single select | • **Value options:** ◦ 3 (High) ◦ 2 (Medium) ◦ 1 (Low) | *Operational impact after planned actions are applied.* | | C-29 | Customer Impact | • dropdown• single select | • **Value options:** ◦ 3 (High)Overall remaining impact after treatment. ◦ 2 (Medium) ◦ 1 (Low) | *Customer impact after planned actions are applied.* | | C-30 | Total Impact | • calculated field • read-only | • Automatic calculation. • Calculation Formula: **C-25 + C-26 + C-27 + C-28 + C-29**• The field automatically **recalculates** whenever any of the source fields (C-25 + C-26 + C-27 + C-28 + C-29) are updated.• If any of the source fields are empty or missing, the calculated field remains **empty**. | *Overall remaining impact after treatment.* | | C-31 | Likelihood | • dropdown• single select | • **Value options:** ◦ 3 (High) ◦ 2 (Medium) ◦ 1 (Low) | *How likely the risk is after treatment.* | | C-32 | Risk Score | • calculated field • read-only | • Automatic calculation. • Calculation Formula: **C-31 x C-30 x C-10**• The field automatically **recalculates** whenever any of the source fields (C-31 x C-30 x C-10) are updated.• If any of the source fields are empty or missing, the calculated field remains **empty**. | *Overall remaining risk score.* | | C-33 | Risk Level | • calculated field • read-only | • Automatic calculation. • Mapping: ◦ If **С-32** value is between 15 and 180 → assign 1 (Low); ◦ If **С-32** value is between 181 and 360 → assign 2 (Medium); ◦ If **С-32** value is greater than 360 → assign 3 (High). • The value updates dynamically whenever the **С-32** value changes. | *Remaining risk level after treatment.* | | C-34 | Report to Board | text field | • Field limitation: 700 characters (MVP concept) | *Key information suitable for board-level reporting.* | | C-35 | Responsible Function | text field | • Field limitation: 700 characters | *Function accountable for long-term ownership of the risk.* | - [Core Guardian](https://support.copla.com/core-guardian?hsLang=en#main-content) - [General Instructions](https://support.copla.com/core-guardian?hsLang=en#general-instructions) - [Additional Information](https://support.copla.com/core-guardian?hsLang=en#additional-information) - [Demo Platform](https://support.copla.com/core-guardian?hsLang=en#demo-platform) - [Integration Setups](https://support.copla.com/core-guardian?hsLang=en#integration-setups) - [Copla Registry](https://support.copla.com/copla-registry?hsLang=en#main-content) - [Getting started](https://support.copla.com/copla-registry?hsLang=en#getting-started) - [Completing the Register](https://support.copla.com/copla-registry?hsLang=en#completing-the-register) - [Troubleshooting](https://support.copla.com/copla-registry?hsLang=en#troubleshooting) - [FAQ](https://support.copla.com/copla-registry?hsLang=en#faq) - [VendrIQ](https://support.copla.com/vendriq?hsLang=en#main-content) - [Trial](https://support.copla.com/vendriq?hsLang=en#trial) - [Overview](https://support.copla.com/vendriq?hsLang=en#overview) [![main-black-pinkglasses](https://support.copla.com/hubfs/main-black-pinkglasses.svg "main-black-pinkglasses")](http://copla.com) [support@copla.com](mailto:support@copla.com) [mailto:support@copla.com](mailto:support@copla.com) Copyright © 2026, Copla