The short version: A client risk register is one page that lists what is still wrong, who owns each item, what was decided and when it will be looked at again. Build it from the gaps you already know about, get the director to sign it each quarter, and you have an answer ready when an insurer, auditor or customer asks "what do you know about your own risks?"
What does a one-page risk register contain?
Seven columns. Anything more and the client stops reading.
| Column | What to write |
|---|---|
| Risk | One plain sentence: "Three staff have no MFA on email." |
| What it could cost | Downtime, data loss, a lost contract, a failed renewal. |
| Likelihood and impact | High, medium or low for each. No scoring maths. |
| Decision | Fix it, accept it, move it (insurance or contract), or monitor it. |
| Owner | A named person at the client, not "IT". |
| Date | When the decision was made and when you will look again. |
| Status | Open, in progress, closed. |
NIST's IR 8286 series on cybersecurity risk management describes registers that capture what the risk is, what it affects, how likely and severe it is, and how the organisation plans to respond. A small client needs the same thinking in a much smaller format.
Why do clients need one before renewal season?
Because insurers, auditors and customers now ask for evidence that you know your own gaps. Renewal season for many businesses runs from December to February, and the questionnaire asks what controls are in place. A dated register answers the follow-up question: "and what is not in place?"
It also protects you. If a client declines a fix and something later goes wrong, a signed entry shows the client was told and chose the risk. For the sign-off wording, see Client refuses MFA? How an MSP puts the risk in writing.
Where do the first rows come from?
From work you already do. Do not start with a blank page and a workshop.
- Failed or partial controls from your last scan or assessment.
- Anything the client declined or deferred in the past year.
- End-of-life systems still running. The Windows 10 end-of-support post covers how to write those up.
- Supplier risks: the one vendor that holds all their data, the contractor with admin access.
- Gaps the insurance questionnaire made you answer "no" or "partly" to.
Our insurance questionnaire walkthrough shows how those answers line up with controls.
How do you rank the rows without a scoring model?
Ask one question: "If this goes wrong, can the business keep trading?" Rows where the answer is no go to the top. Everything else is ordered by how cheap it is to fix.
This is where a scan with ranking helps. CYBERWHITE's CARS scoring puts a client's gaps in order, most important first, so the top three rows of the register come from the same ordered list you work from. You still decide the wording. A human should always write the "what it could cost" line, because only you know that this client's quoting system is the one thing that cannot go offline on a Monday.
What does it look like in practice?
Take a 20-person accounting firm. After a quarterly review the register has six rows.
- No MFA for two partners. Decision: accept until 31 January, partners signed. Owner: managing partner.
- One Windows 10 machine in reception. Decision: replace. Owner: office manager. Date: before renewal.
- Backups never test-restored. Decision: fix. Owner: MSP, with a restore test booked.
- Shared mailbox with full-company access. Decision: fix, 30 days.
- Payroll supplier has no security attestation. Decision: ask for one.
- No incident phone tree. Decision: fix, one hour with the MSP.
That is one page. The managing partner reads it in four minutes and signs it. At renewal, the broker gets the questionnaire and the register together.
If you are a small business owner
You do not need to build this yourself. Ask your IT provider for a one-page list of known risks, with your name beside each decision. If you are told everything is fine, ask what is not yet fixed. Every business has open items. A register that says "none" is not credible.
If you are an MSP
Treat the register as a service line, not a favour. It takes about an hour per client per quarter once the first version exists, and it gives you a reason to talk to the owner when nothing is on fire. Position it as part of your quarterly review. For how to package that, see the MSP compliance pricing guide. To see where the evidence behind each row comes from, book a free proof check and we will scan one tenant with you and show what an assessor would still ask for.
What should you avoid?
- Scoring models with decimals. False precision. High, medium, low is enough.
- Rows without owners. An unowned risk does not get fixed.
- Hiding the awkward rows. The register is only worth showing to an insurer if it is honest.
- Treating it as a one-off. An undated register is a stale register.
Monday checklist
- Pick your three most exposed clients.
- List their open gaps from the last scan or review.
- Write each as one plain sentence with a decision and an owner.
- Book a 15-minute sign-off with the director.
- Put the next review date on the page.
- Store the signed copy with the client's compliance evidence.
For the wider standards context, the Essential 8 pillar page and the SMB1001 guide show which controls each framework expects.
Sources
- NIST: Integrating Cybersecurity and Enterprise Risk Management, NISTIR 8286 series (csrc.nist.gov)
- Australian Signals Directorate, cyber.gov.au: Small business cyber security guide
- Australian Signals Directorate, cyber.gov.au: Cyber security priorities for boards of directors 2025-26
Keep reading: Client refuses MFA? How an MSP puts the risk in writing and The evidence problem: you did the security work, but can you prove it? and Raising MSP prices without churn: the clause and the letter