Scoring

Understanding the 300–850 Cyber Risk Score

XR
Xcigence Research
Cyber Risk Intelligence Team
8 min read

A number only means something once you know the scale it sits on. The Xcigence cyber risk score runs from 300 to 850 across five defined bands — and each band carries specific consequences for underwriting, procurement and board reporting. This is how to read it.

Why 300–850

The range is borrowed deliberately. Consumer credit scoring settled on 300–850 decades ago, and as a result almost every business decision-maker already has a working intuition for what a number on that scale implies: the low 500s mean trouble, the high 700s mean strength.[1] Importing the scale imports the intuition — a CFO, an underwriter or a board member can act on a cyber score of 612 without being taught a new vocabulary first.

There is a second, subtler reason. A 0–100 scale invites false precision and percentage thinking ("we're 71% secure"), which is meaningless. A 300-point floor makes clear that the score is a position on a comparative scale, not a completion percentage.

The scale at a glance

300
← Higher Risk
Xcigence Cyber Risk Score
850
Lower Risk →
300 – 579
Critical Exposure
580 – 669
Elevated Risk
670 – 739
Moderate Risk
740 – 799
Strong Posture
800 – 850
Industry-Leading

The five bands

Each band describes a materially different risk posture, not merely a better or worse version of the same one. The practical consequence of a band is usually more important than the exact number inside it.

RangeBandWhat it signals
300 – 579Critical ExposureMultiple exploitable exposures on the external attack surface. Compromise likelihood is high and remediation is urgent.
580 – 669Elevated RiskMaterial weaknesses present across several assessed domains. Risk is concentrated enough to affect underwriting and vendor decisions.
670 – 739Moderate RiskCore controls are in place, with recurring gaps in configuration, patch cadence, or exposed services.
740 – 799Strong PostureConsistent control coverage with limited residual exposure. Typically acceptable for most commercial engagements.
800 – 850Industry-LeadingMinimal external exposure and mature, continuously validated controls. Meets thresholds for highly regulated sectors.
The five bands of the Xcigence 300–850 cyber risk score.

A useful way to hold these in mind: Critical Exposure and Elevated Risk describe organizations where an attacker's work is largely already done for them. Moderate Risk describes competent security with inconsistent execution. Strong Posture and Industry-Leading describe organizations where compromise requires the attacker to invest real effort and novel capability.

Reading score movement

A single score is a snapshot; the trend is the diagnosis. Three patterns recur:

  • Sharp drop, quick recovery — Usually a newly disclosed critical vulnerability in software the organization runs, patched within days. This is a healthy signature — it shows an operating patch process. CISA's KEV catalog is a good proxy for the events that cause these dips.[2]
  • Sharp drop, slow recovery — The same trigger without the operating process. Weeks of exposure to a known-exploited vulnerability is among the strongest predictors of a successful intrusion documented in breach research.[4]
  • Slow, steady decline — The most commonly missed pattern and often the most serious: no single event, just accumulating drift — expired certificates, forgotten subdomains, unpatched secondary systems. It typically indicates an under-resourced security function rather than a technical failure.
Rule of thumb
Treat any movement of 25 points or more within a single month as an event requiring explanation, in either direction. An unexplained improvement can indicate assets dropping out of scope rather than genuine remediation.

Sector thresholds

The same score does not carry the same verdict in every industry. Because impact scales with data sensitivity and regulatory exposure, Xcigence applies sector thresholds — the score a supplier or counterparty is generally expected to clear before it is considered acceptable in that sector. Regulated environments such as finance, healthcare and public services sit at the top of that range; the published thresholds and the reasoning behind them are set out in our scoring methodology.

This is why a 760 can be entirely adequate for a marketing SaaS vendor and inadequate for a clearing bank's core payment processor. NIST CSF 2.0 frames this as risk tolerance being a governance decision, not a technical one[3] — the score informs the threshold; it does not set it.

Four common misreadings

  • Treating the score as a grade — It is a risk position relative to observable evidence, not a report card on the security team. Teams inherit exposure they did not create.
  • Assuming 850 is achievable and permanent — The top band reflects minimal exposure at a point in time. Any organization with an internet presence can lose 40 points overnight to someone else's vulnerability disclosure.
  • Comparing across vendors' scales — A "780" from another provider on a different scale, weighting and evidence base is not comparable to a 780 here. Only scores from the same methodology can be ranked against each other — see score vs rating.
  • Ignoring the impact dimension — Two 700s are not equal risks if one holds patient records. The score reflects context, but your risk appetite must still weigh what the counterparty holds and how much you depend on them.

How to move your score

Because every point of the score traces to specific, timestamped evidence under our patented methodology[5], improvement is not guesswork. In practice, movement comes from a short and predictable list: remediating known-exploited vulnerabilities on internet-facing systems, retiring forgotten and end-of-life assets, correcting email authentication and TLS configuration, and closing exposed administrative services. These are the highest-yield actions precisely because they are the ones an attacker finds first.

Where the score sits matters less than whether you can explain it, defend it and move it. For the conceptual foundations, start with What Is a Cybersecurity Risk Score? — and to translate a band into expected loss, continue to cyber risk quantification.

Part of our guide to
Cyber Risk Scoring

How security evidence becomes a standardized, defensible 300–850 score.

References

  1. [1]myFICO. What is a FICO Score and credit score ranges
  2. [2]CISA. Known Exploited Vulnerabilities (KEV) Catalog
  3. [3]NIST. Cybersecurity Framework (CSF) 2.0
  4. [4]Verizon. Data Breach Investigations Report (DBIR)
  5. [5]USPTO. Granted patent US 11,418,531 (application US 16/822,691) — Global Dossier record

See your own cyber risk score

Xcigence computes a standardized 300–850 cyber risk score for your organization and every vendor in your ecosystem — no agents, no questionnaires.

We use cookies to improve your experience, analyze traffic, and support our marketing. See our Privacy Policy.