Skip to content
Calcrivo

Identity Risk Calculator

Score identity risk across MFA gaps, privileged density, stale and shared accounts, breached credentials and service accounts.

Inputs

identities
identities
%
accounts
accounts
credentials
accounts

Identity Risk Score

22/ 100

Severity

Low

Largest Risk Driver

MFA coverage gap

MFA Gap

18.0%

Privileged Identity Density

2.00%

Identities Needing Immediate Attention

2,280

Step by step

  1. Values used

    Identities in scope = 12,000 identities; Privileged identities = 240 identities; Identities with MFA enforced = 82 %; Accounts unused for 90 days = 380 accounts; Shared or generic accounts = 45 accounts; Credentials found in breach data = 120 credentials; Service accounts with unrotated secrets = 60 accounts

  2. Identity Risk

    risk = 0.45 × MFA gap + 2.2 × privileged density + 1.6 × stale rate + 2.5 × shared account rate + 3 × breached credential rate + 1.8 × unrotated service account rate.

  3. Immediate remediation queue

    identities needing immediate attention = identities without MFA + credentials found in breach data.

  4. Identity Risk Score

    = 22 / 100

  5. Severity

    = Low

  6. Largest Risk Driver

    = MFA coverage gap

  7. MFA Gap

    = 18.0

  8. Privileged Identity Density

    = 2.00

  9. Identities Needing Immediate Attention

    = 2,280

How it works

Each factor is expressed as a rate so organisations of different sizes are comparable, then weighted by how directly it leads to account takeover. Breached credentials carry the heaviest weight because they need no attacker skill at all, and shared accounts follow because nothing about them can be attributed to a person. Ranking drivers matters more than the composite score: it tells you whether the next sprint should go to MFA enrolment, secret rotation or dismantling shared accounts.

Formulas

Identity Risk

risk = 0.45 × MFA gap + 2.2 × privileged density + 1.6 × stale rate + 2.5 × shared account rate + 3 × breached credential rate + 1.8 × unrotated service account rate.

MFA gap
100% minus MFA coverage
privileged density
Privileged identities ÷ all identities
breached credential rate
Credentials appearing in breach corpora ÷ all identities

Immediate remediation queue

identities needing immediate attention = identities without MFA + credentials found in breach data.

breach data
Public and commercial credential dumps, checked continuously rather than once

Frequently Asked Questions

How is Identity Risk calculated?

risk = 0.45 × MFA gap + 2.2 × privileged density + 1.6 × stale rate + 2.5 × shared account rate + 3 × breached credential rate + 1.8 × unrotated service account rate. Each factor is expressed as a rate so organisations of different sizes are comparable, then weighted by how directly it leads to account takeover. Breached credentials carry the heaviest weight because they need no attacker skill at all, and shared accounts follow because nothing about them can be attributed to a person.

Why does Identity Risk matter?

Ranking drivers matters more than the composite score: it tells you whether the next sprint should go to MFA enrolment, secret rotation or dismantling shared accounts.

What values do I need to enter?

This calculator takes 7 inputs: Identities in scope, Privileged identities, Identities with MFA enforced, Accounts unused for 90 days, Shared or generic accounts, Credentials found in breach data, Service accounts with unrotated secrets. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.

Why weight breached credentials so heavily?

Because credential stuffing needs no exploit and no skill — the attacker already has a working username and password and only has to find where it was reused. This is also why MFA coverage is the paired control: it is the difference between a breached credential being an incident and being a login failure.

What counts as a privileged identity?

Anything that can change security state: cloud administrators, domain and enterprise admins, database owners, CI/CD pipeline identities, and any account holding a privilege-escalation permission. Judging privilege by job title rather than by effective permissions is what makes the density figure look artificially low.

You might also need