- Sector
- Retail
- Company size
- International group with teams in several countries
- Business lines
- GRC and ESG
- Solutions
- GRC platforms
Three areas, three different ways of handling risk
The group's cybersecurity team already worked with eramba, with its own taxonomy and configuration. Then two other areas asked for the tool: corporate risk, which was setting up a new function with its own methodology and users in several countries, and internal audit, with its annual plan and the follow-up of its findings.
The client's question was direct: what really stood in the way of having everything in a single instance.
- Cybersecurity in production, with its own configuration
- Corporate risk with a new methodology and users in each country
- Internal audit, which needs a workflow eramba doesn't offer out of the box
- A committee that wants to follow all three areas at once
Separate instances, and the answer in writing
A reasoned recommendation
eramba supports several risk models in one instance if they share a methodology, fields, risk levels and an administration team. Here they didn't, so we proposed three.
What's missing, said up front
We explained that eramba has no internal audit module as such, how it is covered with the general modules and which other platforms do include one.
Corporate risk kick-off
An implementation plan with the client's team: the date the environment is available, the administrator, sign-in with their corporate accounts and workshops.
Workshops to load and run it
The workshops are for loading their risk matrix and learning to administer the tool. Access is prepared separately, with their security team.
A combined view, later
The consolidated view of the instances for the committee will be built with connectors, as an enhancement, once more than one area is up and running.
First the awkward question, then the instance
Before setting anything up, the client wanted to understand the architecture. They sent us a long questionnaire: one instance or three, and what happens with internal audit. We answered point by point, and the answer opened another round: how the data is consolidated and what the source of truth is if the same risk appears in two instances.
Separation by permissions within one instance exists, but separating by roles is not separating the data or the administration. With three areas that measure risk differently, putting them in one instance meant cutting back the configuration of at least one of them.
On internal audit we were clear. eramba is designed for the second line of defence: risk management and compliance. It can be adapted with projects for the annual plan, control reviews as working papers, findings with their action plans and questionnaires to request evidence, but it has limits compared with an audit tool. The client thanked us in writing for being that clear.
For corporate risk, the client issued its purchase order in August and we prepared with their team what the environment needs. They already had their risk matrix, and asked for the upload format before the workshops so they could arrive with it ready.
Area by area
We tell it as it is. The cybersecurity instance is still in production. The corporate risk instance is now up and running, with its workshops done.
The internal audit one has not been decided. For that requirement, the client is weighing eramba against other platforms, which we suggested ourselves when explaining the limits of each one.
The consolidated view for the committee will come once more than one area is up and running.
Several instances take more maintenance work than one. In return, each team works with its own method without cutting back the one next to it, and the decision to bring the data together is taken later, with the areas up and running.
How we choose a platform with each client, in GRC platforms. The product, at eramba. What we do in risk and compliance, in GRC and ESG.
Do several areas want the same tool?
Tell us how each one handles risk. We'll tell you whether they fit in one instance or each needs its own, and why.