Product

Cyber Risk Management

Assess cyber risks, put security controls into practice and review the exposure that remains. Connect risks to your systems, information and suppliers, then track control implementation, review outcomes and residual risk with clear ownership.

Simplified risk management illustration showing example risks, inherent and residual scores, ownership and treatment progress

The outcome

Know which controls are implemented, whether they are working and whether residual cyber risk needs further treatment or an accountable acceptance decision.

How it helps

How Cyber Risk Management works

This product connects with the wider Apollo platform, so information can support action, evidence and reporting without being entered again.

Feature 1

Connect cyber risks to what is at stake

Bring the affected information, systems and suppliers into the risk record. A data breach risk, for example, becomes easier to assess when the relevant records, cloud supplier and access controls are connected.

  • Link assets, suppliers and controls
  • Compare inherent and residual exposure
  • Assign a risk owner and review date
Illustration of an example data breach risk connected to an access review control, student records asset and cloud supplier

Feature 2

Implement the controls that reduce exposure

Select relevant controls from the library or your existing register, link them to the risk and assign responsibility for implementation. Track what is planned, underway or implemented, with treatment tasks to close the gaps.

  • Link controls to the risks they address
  • Assign control owners and track implementation
  • Follow up outstanding treatment work
Simplified illustrative control register workflow with fictional sample data

Feature 3

Review controls and reassess residual risk

Review whether implemented controls are operating as intended, then reassess the likelihood and impact of the risk. Record the remaining exposure and the next decision: further treatment, continued monitoring or acceptance by the accountable risk owner. Planned controls should not be treated as if they are already reducing risk.

  • Review control effectiveness and supporting evidence
  • Reassess and record residual risk
  • Assign the next review or treatment action
Illustrative risk score history: inherent risk 20 Critical, earlier assessment 16 High after adding access controls, current residual risk 12 Medium after enabling MFA, and a separate target of 9 Low that has not yet been reached

What is included

One product, connected to the wider platform

Use the product you need now while keeping its records, work and evidence ready for related products across Apollo.

Included features

  • Cyber risk registers
  • Control implementation and ownership
  • Control reviews
  • Inherent and residual risk scoring
  • Treatment and review tasks
  • Residual risk reporting

Customer proof

Cyber Risk Management in practice

See how customers use this product as part of a broader security, governance or compliance outcome.

Questions and answers

Questions about Cyber Risk Management

Practical answers to common questions about managing this responsibility well.

What should a cyber risk register contain?

Record the risk scenario, affected systems or information, likely consequences, owner, existing controls and assessed exposure. Include the treatment decision and review date so the register supports action rather than becoming a list of threats.

How are inherent and residual cyber risk different?

Inherent risk describes exposure before considering the controls in the assessment. Residual risk describes the exposure that remains after those controls are considered. Record the assumptions behind both ratings so reviewers can understand the judgement.

How should control implementation affect residual risk?

Base the residual risk assessment on controls that are implemented and operating, with evidence to support the judgement. A planned control is a treatment action, not an existing reduction in exposure. Review control effectiveness, reassess likelihood and impact, and record whether the remaining risk needs further treatment or an accountable acceptance decision.

Who should own a cyber risk?

Assign the risk to someone who can make or escalate decisions about the affected activity. Technology staff may operate the controls, while the accountable risk owner decides whether treatment and remaining exposure are appropriate within the organisation's governance process.

What should leaders see in cyber risk reporting?

Show material exposure, significant changes, treatment progress and decisions requiring attention. Keep the connection to business impact clear, and identify overdue reviews or actions so leaders can see where intervention is needed.

See Cyber Risk Management in Apollo

Book a focused demonstration and we will show how the product fits your current responsibilities, existing information and next practical priorities.