A continuously updated view of risk.
Aletva uses AI to link your risks, controls and incidents, and updates your scores as things change, so you always see where risk stands today.
/Risk Assessment
All entities ▾
A risk score is only as current as its last review
Between reviews, the picture drifts. Three things cause it.
Scores go stale.
A score set at one point in time does not change when an incident closes or a KRI crosses its threshold.
Risk data sits apart.
Incidents, KRIs and audit findings live in different systems, so nobody sees them against the risk they affect.
Re-scoring is manual.
Teams update scores by hand, on a schedule rather than when something changes.
An out-of-date score sends attention to the wrong risks.
Everything that shapes a score, in one place.
From how risks are organized to how their scores change.
Structured risk taxonomy.
Risks are sorted into families, types and sub types, so every risk has a clear place.
KRIs and incident types.
Each risk has the indicators that measure it and the types of incident that signal it.
Entity exposure.
Each business unit or entity is linked to the risks it faces, so scores sit where the exposure is.
Inherent and residual scoring.
Each risk starts with an inherent score, the risk before any controls. The residual score shows where it stands now, after controls.
Continuous signal monitoring.
Incidents, indicator readings, audit findings and regulatory changes are picked up as they arrive.
AI links across your risk data.
Entities, risks, controls, incidents and indicators are connected, so an event reaches every risk it affects.
Scores that rise and fall.
Scores go up when events happen and come back down when things return to normal.
Human override.
A risk owner can review any score and adjust it when their judgment calls for it.
Connection to compliance.
Compliance results are connected with risk events, giving one view of risk and compliance.
How Aletva keeps your risk scores current
Aletva links your risks, controls and incidents, then watches for events that change them.
-
01
Link your risks
Each business unit is connected to the risks it faces, with the indicators and incident types that go with them.
-
02
Set the starting score
Every risk begins with an inherent score, the risk before any controls.
-
03
Watch for changes
Incidents, indicator readings, audit findings and regulatory changes are picked up as they arrive.
-
04
Update the score
When something happens, Aletva updates the score of every risk it affects.
Monitoring runs continuously on the signals your systems and teams send.
Request a demo →Automation does the updating. People make the call.
Aletva handles the routine work. Judgment stays with your team.
Add risk scoring without replacing anything
-
Events flow in automatically
Incidents, indicator readings and audit findings are sent to Aletva from where they are recorded today. Each one updates the scores of the risks it affects. The connection is set up for your organisation.
-
No double entry
Aletva uses the risks, business units and processes already in your GRC tool, so nothing is entered twice.
For the people who carry the risk
Different roles, one current position.
Chief risk officers and heads of risk.
A current position for leadership conversations, not last quarter's.
Compliance heads.
See how compliance results relate to the risks they affect.
Internal control and operational risk owners.
Scores stay current as incidents and KRI readings arrive. Adjust them when your judgment differs.
Technology leaders.
Connect through the APIs your systems already expose. Integrations are built for each organization.
Questions buyers ask
Risk assessment software helps organizations identify, score and monitor risk. Aletva does it with a connected model of entities, risks, controls, incidents and KRIs, and keeps residual scores current as signals arrive.
Scores adjust when an incident occurs, a KRI measurement arrives, audit findings come in or a regulatory amendment is implemented. They come down when the signal returns to normal. The person in charge can change any score.
Risk intelligence software usually monitors external threats. Aletva's scores come from signals inside your organization, such as incidents, KRIs and audit findings.
No. Aletva sits on top of your existing GRC tools and operational systems. It can also run on its own.
Any system that exposes RESTful APIs can connect. Integrations are built for each organization, based on its environment.
Aletva works on its own, so you don’t need one. You set up your risks and business units in Aletva and connect your incident and indicator data. Scores then update as events come in. If you add a GRC tool later, Aletva can use the risks and processes already in it.
See a risk score move
Bring a risk you track today. We will show how signals change its score, and where your team can step in.
Audit automation is coming soon.