Running the risk register for a small security program: a spreadsheet, SimpleRisk, eramba and CISO Assistant reviewed
What a small organization's risk register has to do, and how a spreadsheet compares with three free or open-source GRC tools: SimpleRisk Core, eramba Community and CISO Assistant.
The question the register has to answer
An owner of a 40-person firm is asked by the bank’s underwriter, the cyber insurer and a large customer, in the same quarter, some version of one question: what are your top security risks, and what are you doing about them? The honest answer exists. It is spread across an MSP’s ticket queue, a policy binder, two spreadsheets and the office manager’s memory.
A risk register is where that answer lives. It is a list of the things that could hurt the business, how likely and how bad each one is, who owns it, and what the plan is. NIST describes the same idea at enterprise scale in IR 8286A Rev. 1, published December 2025: record risk scenarios, estimate their likelihood and impact in a cybersecurity risk register, and roll that up into the enterprise risk picture so leadership can prioritize and track the response.
The tool matters less than the habit. Still, the tool decides whether the habit survives the first busy month, so it is worth choosing deliberately.
What the register has to do
For a small program, five things:
- One row per risk, written as a scenario: “ransomware encrypts the file server and the backups”, not “ransomware”.
- Likelihood and impact on a scale everyone uses the same way, and a resulting rating.
- An owner and a decision for each risk: reduce, accept, transfer or avoid, with a date.
- Links to the controls and tasks that reduce it, so progress is visible.
- A record of acceptance: when leadership accepts a risk, who did it, when, and until when.
Anything beyond that is useful later, not on day one.
Option 1: a spreadsheet
A shared spreadsheet does all five if someone keeps it. It costs nothing, everyone can open it, and it fits on one screen in a board meeting. NIST’s IR 8286A Rev. 1 even publishes a risk register schema (as JSON) that shows which fields an enterprise register carries, which is a useful checklist for your columns.
Where it breaks: there is no workflow, so reviews depend on memory; there is no audit trail of who changed a rating; and linking risks to controls and evidence turns into a second and third tab that drift out of date. It works well for 10 to 30 risks and one person keeping it. It struggles once several people edit it or an auditor asks for history.
Option 2: SimpleRisk Core
SimpleRisk describes its Core edition as free and open source, with unlimited users, at no cost to self-host. Its pricing page lists governance, risk and compliance features in Core, including asset management, self-assessments against frameworks such as CIS, HIPAA, NIST SP 800-171 and PCI DSS, and dashboards and custom reports. Paid packages add optional extras, support and a hosted option; the pricing page listed the Starter Package at $5,000 a year in November 2026. Releases are published in SimpleRisk’s GitHub repository, most recently in October 2026.
Good fit: an organization that wants a register first and a compliance tool second, and has someone who can run a small web application or will pay for hosting.
Watch for: some features you may want later are paid extras, so check the list before you build your process around one.
Option 3: eramba Community
eramba offers a Community edition on-premises, which its site describes as free with no user or time limit, alongside paid Enterprise editions on-premises and as a hosted service. eramba publishes Docker helper files for running the software on GitHub. Its site lists risk management, compliance management, incident management, awareness training, data privacy, online assessments and account reviews among its use cases, with templates for policies and internal controls; in Community, awareness training, online assessments and account reviews are left out, along with automation and support from eramba’s team. That is a broader platform than a register alone, built around documented workflows and reviews.
Good fit: an organization that already knows it will be audited and wants reviews, exceptions and evidence tracked in one place.
Watch for: eramba’s Community page links a comparison with Enterprise. Read it before you commit, and plan for the time it takes to configure a platform this broad. eramba also sells implementation workshops.
Option 4: CISO Assistant (Community edition)
CISO Assistant, from intuitem, is released under the AGPL v3 in its Community edition, with commercially licensed Pro and Enterprise editions. Its repository lists risk assessments and registers, risk acceptance workflows, business impact analysis, cyber risk quantification and third-party risk features, and says it includes more than 200 frameworks with automatic mapping between them, among them ISO 27001, NIST CSF, SOC 2, PCI DSS, NIS2, DORA, GDPR and HIPAA. The quickest deployment is Docker. The project is active: version 4.2.1 was released on November 1, 2026.
Good fit: an organization that wants its register tied to more than one framework, for example a customer asking for ISO 27001 alignment while the board tracks NIST CSF 2.0.
Watch for: the AGPL license matters if you plan to modify the software and offer it to others as a service; for internal use it is rarely an issue, but read it. A tool with hundreds of frameworks makes it easy to load too many. Start with one.
Side by side
| Spreadsheet | SimpleRisk Core | eramba Community | CISO Assistant Community | |
|---|---|---|---|---|
| Cost to start | None | Free to self-host | Free on-premises | Free to self-host |
| Paid tiers | Not applicable | Yes, with extras and hosting | Yes, Enterprise on-premises or hosted | Yes, Pro and Enterprise |
| Hosting | Your file share | Self-host or vendor SaaS | Self-host; Enterprise also hosted | Self-host (Docker, Helm) |
| Strength | Simplicity | Risk-first, easy entry | Workflow and review discipline | Framework mapping |
How to choose
Ask three questions.
- Who will keep it? If the answer is one person with an hour a month, start with a spreadsheet and the five fields above. A tool nobody opens is worse than a spreadsheet someone does.
- Will an auditor or customer ask for history? If yes, move to a tool with an audit trail. SimpleRisk is the lightest step; eramba suits a heavier review process.
- How many frameworks are you answering to? One: any option works. Two or more: CISO Assistant’s mappings save repeated work.
Whatever you pick, a self-hosted GRC tool becomes a system that holds a list of your weaknesses. Put it behind single sign-on with MFA, back it up, and patch it like anything else exposed to your network.
A first month that works
- Week 1: list 10 to 15 risks as scenarios, with the owner and MSP in the room.
- Week 2: rate them on one agreed scale; do not debate decimals.
- Week 3: for the top five, write the decision and the next task with a date.
- Week 4: show the top five to leadership on one page and record any acceptance.
Then repeat the review quarterly, and after any incident or big change.
When to get help
If the register keeps stalling at “we should really write this down,” an outside facilitator can run the first workshop and leave you with a register, a scale and a review schedule.
Want to talk it through? Book a free 30-minute call with Security Medic Consulting.
Sources
- NIST, IR 8286A Rev. 1, Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management, December 2025 (accessed 2026-11-05). Includes the Risk Register Schema supplemental material.
- SimpleRisk, Pricing (read 2026-11-05).
- SimpleRisk, simplerisk/simplerisk releases on GitHub, release 20261020-001 published October 21, 2026 (accessed 2026-11-05).
- eramba, eramba.org (accessed 2026-11-05).
- eramba, Community (accessed 2026-11-06).
- eramba, eramba/docker on GitHub (accessed 2026-11-05).
- intuitem, ciso-assistant-community on GitHub, release v4.2.1 published November 1, 2026 (accessed 2026-11-05).