Starting point
It began with a single tool for business impact analysis that we had built for the consultancy. Beside it, other applications existed or were being built: one for implementing NIS-2, a clickable prototype for the ISMS, a picture of the security situation worldwide. Each stood on its own. For the consultancy's clients, often groups made up of a holding company and several subsidiaries, that meant several accounts, a company structure maintained more than once, and no single place that showed who may use which product.
Then there was the rating itself. The BIA and the ISMS rated risks on matrices of their own, so "high" in one product could mean something different from "high" in the other. And a measure from the risk analysis counted as soon as it was entered; whether it had been carried out was tracked somewhere else. The consultancy wanted a shared foundation on which further products could be added quickly, without the existing ones losing their independence.
Solution
At the core is a platform for sign-in, the company tree and licences. One account works for every product; they sit under one address, with the same header, the same product switcher and the same account menu. The company tree models the holding company and its subsidiaries. You always work in exactly one company and switch between them as between workspaces. A member of the holding reaches the subsidiaries below it, never those beside or above it. Between sister companies the consultancy can grant read access: explicitly, in one direction, for the task tool only, and not extending to their subsidiaries.
In the console the consultancy records what has been sold: product, number of seats, term. Whether a licence is active, scheduled, in its grace period or suspended follows from its dates and is never maintained by hand. The client's administrator assigns the seats, and a licence held by the holding can cover its subsidiaries. The task tool and the situation picture are included in every organisation, the other products are assigned per seat; a seat in the BIA or the ISMS product includes the risk register, and the data protection product is switched on per organisation.
The products stay independent. Each has its own database schema and its own database user, which cannot read the other products' data. At sign-in the platform issues a short-lived, signed access ticket carrying the organisation, permissions and entitled products, and every product checks it itself, without asking the platform on each request. If the platform cannot be reached, nobody can sign in anew, but work in progress carries on. When a seat, a membership or a session is withdrawn, the products refuse the old ticket on the next request.
For rating there is one risk policy per company, versioned and held in the platform: likelihood levels with the company's own definitions, damage categories with thresholds per level, and a matrix. The BIA, the ISMS and the risk register rate against it. Where there used to be two matrices, a fixed rule decides which one is adopted: a signed-off one before one that was only saved, and within that the more recent. A report lists cell by cell what changes and which ratings change their acceptance as a result. The risk policy is switched on per company, not for everyone at once.
Measures run through the shared task tool. When a measure is saved in the BIA product, the ISMS or the risk register, exactly one task is created, even with retries, lost responses and simultaneous requests. In the BIA product's risk analysis the measure starts inactive and only counts towards the current residual risk once its task is done; if the task is reopened, it stops counting. Planned and current residual risk are shown side by side. In the ISMS a completed task leads to a review, not straight to effectiveness. The risk register mirrors the risks from the BIA and the ISMS, closes reporting periods with immutable snapshots and the version of the risk policy, and shows the holding a heat map across its subsidiaries.
- One account for seven products, with a shared header, product switcher and account menu
- A company tree for the holding and its subsidiaries; access only downwards, read access between sister companies only when granted
- Licences with seats per product; status follows from term and grace period, and the client assigns the seats
- A database schema of its own per product, and a signed, short-lived access ticket that every product checks itself
- One versioned risk policy per company, with a fixed selection rule and a report on the switch, switched on per company
- Exactly one task per measure; in the BIA product effective only once the task is done
- A risk register across the BIA and the ISMS, with closed reporting periods and a heat map for the holding
A look inside the product
Illustrative sample data; an anonymised product example that deliberately does not show the real product.
Result
The platform is in production use. The move from a single BIA tool to a platform began at the end of July 2026, and the seventh product joined at the beginning of November, about three months later. In between came the task tool, NIS-2, the ISMS, the situation picture, the risk register and finally data protection.
Three of the products were not built anew but brought into the platform: the NIS-2 application, which we had previously developed as a standalone application, the situation picture and the ISMS clickable prototype. They took over the platform's sign-in, company tree and licences and kept their own data. We present some of the products in case studies of their own.
One decision carried this: the platform is responsible only for what all products share, namely identity, companies, licences and the risk policy, and everything specialist stays in the products. That is how each further product could join without the existing ones giving up their data or their workflows.
- In production use
- Seven products on one platform, about three months from the platform's start
- NIS-2, the situation picture and the ISMS prototype brought in rather than rebuilt
- One meaning of "high" across the company, once the risk policy is switched on