Governance, Risk & Compliance

Running a Risk Assessment and Keeping a Risk Register

a repeatable way to turn worries into ranked, owned decisions

2 min readupdated by Syed Khaleel Ahmed

A risk assessment answers: what could go wrong, how likely is it, how bad would it be, and what should we do about it? Doing it the same way each time lets you compare risks, track progress and justify spending.[1]

A practical process

  1. Set the scope and criteria. What is being assessed (a system, a project, the whole company)? Agree the likelihood and impact scales and what level of risk the organization will accept.
  2. Identify assets. Information, systems, people and services that matter, and who owns them.
  3. Identify threats and vulnerabilities. Who or what might cause harm, and what weaknesses exist? Use incident history, vulnerability scans, audit findings and brainstorming with the people who run the system.
  4. Identify existing controls. What already reduces the risk?
  5. Analyze: rate likelihood and impact for each scenario, usually Low to High or 1 to 5. Write scenarios as sentences: "An attacker uses stolen credentials to access the customer database, exposing personal data."
  6. Evaluate: compare each rating with the acceptance criteria and rank the results.
  7. Treat: choose to mitigate, transfer, avoid or accept, and plan the actions.
  8. Record and communicate results to decision makers.
  9. Monitor and review regularly and whenever something significant changes.[2]

The risk register

The register is the living record of the risks. Typical fields:

  • ID and a clear description of the risk scenario
  • Affected asset or process
  • Risk owner (the person accountable for it)
  • Inherent rating, existing controls and residual rating
  • Treatment decision and planned actions, with owners and due dates
  • Status and the date of the last review

Keep it current: a stale register is worse than none because it gives false comfort.

Tips for useful results

  • Involve the people who know the systems, not just security.
  • Be specific. "Hacking" is not a risk; a concrete scenario is.
  • Avoid false precision. A 3 out of 5 is a judgment, so write down the reasoning.
  • Make sure every risk has a named owner, and that acceptance decisions are made by someone with the authority to accept them.
  • Link the register to the rest of governance: audits, incidents, vendor reviews and projects.

Common traps

Treating it as a one-off annual exercise, listing hundreds of low-value risks, no link to action, and rating everything "medium" to avoid a hard conversation.

Sources

  1. NIST SP 800-30 Rev. 1: Guide for Conducting Risk Assessments
  2. ISO/IEC 27005: Guidance on managing information security risks

Test yourself

My notes

Private — saved only on this device, never sent anywhere.