Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

If an employee wishes to raise a potential risk, use this form to do so. The review/implementation process from here will follow the below steps:

  1. Vertic management (Jan Tenenberg, Stephen Kent, Matt Romeo) to review the risk

  2. Several actions are possible from here, including:

    1. Rejecting the risk with an appropriate justification

    2. Capturing the risk including:

      1. Risk Details

      2. Severity

      3. Mitigation/Treatment

      4. Post-Treatment Assessment

  3. Vertic management to provide evidence to the employee raising the risk of what the actions and outcomes were by compiling email containing the following information:

    1. Original Risk Details

    2. Review Process Outcome

    3. Action Decision

    4. Decision Outcome

Any actions resulting from the risk management process will be managed using this JIRA workspace.

Vertic’s Risk Register

Risk

Nbr

#

Risk Name

Description/Risk Outcome

Annex A Controls

Likelihood

Impact Level

Severity

Mitigation/Treatment

Post-Treatment Likelihood

Post-Treatment Severity

Post-Treatment Assessment

1

Client Data Breach

A data breach may occur in one of our client’s software environments which may result in exposure of critical information.

  • A.9.1.1

  • A.5.1.1

  • A.9.3.1

  • A.9.4.1

  • A.9.4.2

  • A.9.4.3

  • A.10.1.1

  • A.10.1.2

Status
colourPurple
titlelow

Status
colourRed
titleHigh

Status
colourRed
titleHigh

Status
colourPurple
titlelow

Status
colourPurple
titlelow

2

Staff Breach

A staff member may expose critical data from a client’s software environment which could then be published.

  • A.7.1.1

  • A.7.2.2

  • A.7.2.3

  • A.9.1.1

  • A.9.1.2

  • A.9.2.2

  • A.9.2.3

  • A.9.2.4

  • A.9.2.5

  • A.9.2.6

  • A.9.4.4

Status
colourPurple
titlelow

Status
colourRed
titlehigh

Status
colourYellow
titlemedium

Status
colourYellow
titlemedium

Status
colourYellow
titlemedium

3

Hardware Loss

We may experience the failure of our hardware (primarily work laptops) which could result in loss of critical information to perform our duties.

  • A.8.1.3

  • A.8.1.4

  • A.8.3.2

  • A.8.3.1

Status
colourYellow
titlemedium

Status
colourYellow
titlemedium

Status
colourPurple
titlelow

Information Continuity

Status
colourPurple
titlelow

Status
colourPurple
titlelow

4

Software Failures

Software we use might fail; this could include either Salesforce or other key services.

  • A.9.1.1

  • A.9.1.2

Status
colourYellow
titlemedium

Status
colourRed
titlehigh

Status
colourRed
titleHigh

Status
colourPurple
titlelow

Status
colourPurple
titlelow

5

Employee Fraud

An employee might defraud Vertic but stealing critical information.

  • A.7.1.1

  • A.7.1.2

  • A.8.1.3

  • A.8.2.2

  • A.8.3.2

  • A.9.1.1

  • A.9.2.1

  • A.9.2.5

  • A.9.2.6

  • A.9.4.5

  • A.11.2.5

  • A.11.2.6

Status
colourPurple
titlelow

Status
colourRed
titlehigh

Status
colourYellow
titlemedium

Status
colourYellow
titlemedium

Status
colourRed
titlehigh

6

Employee Injury

An employee might get injured whilst performing their duties for Vertic.

  • A.11.2.4

  • A.12.1.1

Status
colourPurple
titlelow

Status
colourYellow
titlemedium

Status
colourPurple
titlelow

Status
colourPurple
titlelow

Status
colourPurple
titlelow

7

Natural Disaster

A natural disaster might strike impacting our geographic area.

  • A.8.1.3

Status
colourPurple
titlelow

Status
colourYellow
titlemedium

Status
colourPurple
titlelow

Status
colourPurple
titlelow

Status
colourPurple
titlelow

8

Software Development Standard Breach

An employee or contractor might breach our development standards.

  • A.9.1.1

  • A.9.1.2

Status
colourYellow
titlemedium

Status
colourYellow
titlemedium

Status
colourYellow
titlemedium

Status
colourYellow
titlemedium

Status
colourPurple
titlelow

9

Physical Security Breach

An employee or contractor might breach physical security policies, such as leaving laptops unattended.

  • A.6.2.2

  • A.8.1.3

  • A.8.1.4

  • A.8.2.3

  • A.8.3.1

  • A.8.3.2

  • A.8.3.3

  • A.11.1.4

  • A.11.1.5

  • A.11.1.6

  • A.11.2.1

Status
colourPurple
titlelow

Status
colourYellow
titlemedium

Status
colourPurple
titlelow

Status
colourPurple
titlelow

Status
colourPurple
titlelow

10

Contractural Relations Breach

A supplier might breach their contractural obligations with Vertic.

  • A.8.2.1

  • A.8.2.2

Status
colourPurple
titlelow

Status
colourYellow
titlemedium

Status
colourYellow
titlemedium

Status
colourPurple
titlelow

Status
colourYellow
titlemedium

11

Damage caused by Third Party

A third party, such as visitors, might cause physical or virtual damage to critical Vertic assets.

  • A.6.1.3

  • A.6.1.4

  • A.8.1.3

  • A.8.1.4

Status
colourPurple
titlelow

Status
colourYellow
titlemedium

Status
colourPurple
titlelow

Status
colourPurple
titlelow

Status
colourYellow
titlemedium

12

Malicious Code

An employee or contractor might deliberately produce malicious code.

Status
colourPurple
titlelow

Status
colourRed
titlehigh

Status
colourRed
titleHigh

Status
colourPurple
titlelow

Status
colourYellow
titlemedium

13

Equipment Theft

An employee might defraud Vertic but stealing critical hardware infrastructure or laptops.

  • A.6.2.1

  • A.8.1.1

  • A.8.1.2

  • A.8.1.3

  • A.8.1.4

  • A.8.2.3

  • A.8.3.1

  • A.8.3.2

  • A.11.1.1

  • A.11.1.2

  • A.11.2.1

Status
colourPurple
titlelow

Status
colourYellow
titlemedium

Status
colourPurple
titlelow

Status
colourPurple
titlelow

Status
colourPurple
titlelow

14

Sensitive Data Threat

Sensitive data might be under threat outside of Vertic’s control.

  • A.6.2.1

  • A.8.2.1

  • A.8.2.2

  • A.8.3.1

  • A.8.3.3

  • A.11.1.3

  • A.11.1.4

  • A.11.1.5

  • A.11.2.2

  • A.11.2.3

Status
colourYellow
titlemedium

Status
colourRed
titlehigh

Status
colourRed
titleHigh

Status
colourPurple
titlelow

Status
colourRed
titlehigh

15

Security Information System Failure

Our VQMS processes might fail resulting in critical data exposure and/or loss.

  • A.5.1.1

  • A.5.1.2

  • A.6.1.1

  • A.6.1.2

  • A.6.1.5

  • A.7.2.1

  • A.11.2.2

Status
colourPurple
titlelow

Status
colourYellow
titlemedium

Status
colourYellow
titlemedium

Status
colourPurple
titlelow

Status
colourPurple
titlelow

16

Production Data Loss

Whilst performing our duties, we might experience production data loss.

  • A.8.2.1

  • A.8.2.2

  • A.8.3.2

  • A.8.3.3

  • A.8.3.1

  • A.8.3.3

Status
colourRed
titlehigh

Status
colourRed
titlehigh

Status
colourRed
titlehigh

Status
colour

Red

Yellow
title

high

medium

Status
colourRed
titlehigh

We

...

We have used the following matrix to determine the severity of a stated risk:

Risk Likelihood

Risk Impact Level

Risk Severity

Status
colourRed
titlehigh

Status
colourRed
titlehigh

Status
colourRed
titlehigh

Status
colourRed
titlehigh

Status
colour

Purple

Yellow
titlemedium

Status
colour

Purple

Yellow
titlemedium

Status
colour

Purple

Yellow
titlemedium

Status
colourRed
titlehigh

Status
colourRed
titlehigh

Status
colour

Purple

Yellow
titlemedium

Status
colour

Purple

Yellow
titlemedium

Status
colour

Purple

Yellow
titlemedium

Status
colour

Blue

Purple
titlelow

Status
colourRed
titlehigh

Status
colour

Purple

Yellow
titlemedium

Status
colour

Blue

Purple
titlelow

Status
colour

Purple

Yellow
titlemedium

Status
colour

Blue

Purple
titlelow