Understanding 6clicks risk library content

Risk libraries in 6clicks are designed in 6clicks to be used as part of a risk review process using our mobile app, 6clicks Risk Review for Teams. To ensure risk libraries are easy to use and well structured, we use a sophisticated and contemporary graph database solution to ensure relationships between risks, risk domains, risk libraries, common causes and likely impacts are managed effectively. As such, the process of importing risks into the 6clicks platform is a task reserved for the 6clicks engineering team. As a content provider however, we need your content to be structured in a particular format to ensure the integrity of your content once imported into 6clicks (see more about preparing your data for import here).

Risk library data elements and type

Risk library data is structured into data elements as indicated:

Data Type


Risk Library

The name of the risk library as shown in the mobile app - e.g. "Board Top Risks"

Risk Library Description

The description of the risk library as shown under the risk library name in the mobile app - e.g. "Our digest of the top risks for businesses"

Risk Library Icon

Icon representing the risk library (typically the square logo of the publisher)

Risk Name

The name of the risk - e.g. "Targeted cyber attack"

Risk Description

The description of the risk - .e.g. "A targeted cyberattack or malware infection. Major concerns are denial-of-service attacks, phishing and viruses. The fear is that data and systems will be damaged, corrupted or destroyed, or that access to the data will be denied (ransomware)." 

Risk Domain

The risk domain that the risk belongs to.  These are fixed and defined in 6clicks and defined here. 

Common Cause(s)

A common cause of the risk - e.g. "Unauthorised access to systems" 

Likely Impact(s)

A likely impact of the risk - e.g. "Data breach"

For importing content into 6clicks Risk Review for Teams click here.

Risk library data relationships

The following diagram illustrates the relationship between the data elements that make up a risk library.  You can see: 

  • a Risk library has many risks; 
  • each Risk can have a number of common causes and potential impacts
  • each Risk belongs to a risk domain - i.e. "Cyber Security" or "Technological" - these exist across all risks in any domain