Feature - Where to document and track KRIs

Hello,

I do not see any place where I can document the Key Risk Indicators in the Risk Module in Eramba. Is this functionality available at all? In case not, do you have it on your development roadmap?

I am actually refering to the indicators used to measure risk levels in comparison to defined risk thresholds, so that the organization receives an alert when a risk level approaches an unacceptable level.

Examples:

  • Number of instances of service level agreements (SLAs) exceeding thresholds.
  • High average downtime due to operational incidents.
  • Average time to deploy new security patches to servers.
  • etc.

Thanks,
Ejona

1 Like

I don’t believe this feature exists in Eramba. While I think it would be cool, I think you may be able to do this with a workaround.

For example, you could create a new compliance package with the KRIs. Then, you would create controls for each… Then audit those controls. This can be done in the community version, but with Enterprise you’d be able.to create custom fields and store your KRI values there, then run reports on those.

Personally, I don’t know that I’d do this. I’d probably just create a dashboard in Excel. But, this would allow you to leverage Eramba as a reminder, immutable repository of the data, and a method for the collection (ie, email the owners).

Kyle

2 Likes

I’d love to see this as a feature in a future release, reverting to spreadsheets is exactly what we should not be doing, and custom fields don’t work as well with reporting.

Walt

2 Likes

Thank you for a feature request. I created an issue and it will go to our roadmap.

Int. ref: https://github.com/eramba/eramba_v2/issues/2899

2 Likes

Hi,

Maybe the best way to document KRIs (and other Indicators) it’s at the Goals section.

At this place you can:

  • Document basic attributes (name, desc, owner…)
  • Assign them to risks (KRIs), control (KCIs) or others (KPIs)
  • Define the metric and the criteria
  • Perform audits over the indicators.

In any case, I also think that It would be useful what you mean (thresholds, alerts…)

I hope that helps,
Jorge

The internal link https://github.com/eramba/eramba_v2/issues/2899 goes to a page 404.

Is this feature still on the roadmap?

Hello,

Yes, GitHub issues are just internal references. The issue was not implemented yet.

1 Like