One score should lead to one better decision

The Digital Asset Health Score measures readiness across the systems a business depends on. It does not reward a long policy nobody has tested. It rewards ownership, monitoring, recovery, and proof.

The eight score areas

Each area receives zero to three points. The total becomes a score out of 100.

Score areaWhat earns the strongest resultUseful next page
AvailabilityWorking monitors and a tested alertMonitoring tools
Backup and recoveryA recent backup and a successful restoreContinuity checklist
Access controlProtected accounts and reviewed admin accessRansomware guide
Domain and platform controlDocumented ownership, renewal, and recovery accessWebsite risk
Data exposureA current map of sensitive data and response dutiesData breaches
Vendor dependencyKnown dependencies with tested fallbacksSystem outages
Search and AI visibilityMonitoring by priority page, topic, and business dependencyAI visibility risk
Incident response and insuranceTested first actions, contacts, and notice rulesResponse plan

What the score means

Health scoreMeaningNext move
0 to 39ExposedFix the control that could stop recovery or hide an incident.
40 to 69UnstableTurn documented controls into tested controls.
70 to 84Protected but not provenClose the weakest area and test the handoff.
85 to 100ResilientKeep the evidence current and watch for new dependencies.

Worked example: a business that has tools but has not tested recovery

Score areaCurrent pointsTarget pointsWhat changes
Availability33Keep the tested alert.
Backup and recovery13Complete a real restore test.
Access control23Remove old admin access.
Domain and platform control33Keep renewal and recovery records current.
Data exposure12Map sensitive data and retention.
Vendor dependency22Test the most important fallback.
Search and AI visibility22Track priority-page dependency.
Incident response and insurance13Run the first-hour response drill.
Total health score6388Move from unstable to resilient.

The useful part is not the final number. It is seeing that three tested actions can change the business from hoping it can recover to proving it can.

Availability

Know when a revenue or customer system fails. A tool earns credit only when the alert reaches the right person.

Backup and recovery

A backup becomes protection after a successful restore. Record how long the restore took and what the business had to do while it waited.

Access control

Protect admin accounts, remove old access, and know who can change the system now.

Domain and platform control

Keep ownership, renewal, recovery access, and vendor contacts where the business can reach them during an incident.

Data exposure

Know which systems hold sensitive data, who can reach it, and what notice or recovery duty begins after exposure.

Vendor dependency

Identify the outside service that would stop the most work. Test a fallback before that vendor becomes the incident.

Search and AI visibility

Track the pages and topics that create discovery. A business should know when one source carries too much of the lead flow.

Incident response and insurance

Document the first call, first action, evidence owner, approved vendors, and insurance notice rule. Then test the handoff.

Exposed

Start with the control that affects recovery. Unknown ownership, missing backups, or no incident contact can turn a manageable problem into a business interruption.

Unstable

The business has pieces of protection, but too much still depends on an assumption. Test the restore, alert, or response handoff.

Protected but not proven

Most controls exist. Close the weakest area and collect the evidence that proves it works.

Resilient

The business can detect, respond, and recover with tested controls. Review the score when the vendor stack, revenue dependency, team, or threat changes.

Get your score

Use the digital risk assessment to answer the eight questions now. Use the Risk Score method when you need to rank one threat or forecast how a planned control changes it.

Risk Topics