> ## Documentation Index
> Fetch the complete documentation index at: https://docs.webacy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Severity Levels

> Reference for Webacy severity levels that translate numerical risk scores into low, medium, high, and critical actions for policies, alerts, and workflows.

While Webacy calculates precise numerical risk scores, many products and workflows require a simpler way to interpret those scores. Severity levels group similar scores into standardized ranges that make it easier to trigger alerts, enforce policies, and prioritize investigations.

Depending on the entity type and product, severity levels may also incorporate additional contextual information beyond the overall score, such as real-time events, confidence, or critical risk factors.

## Severity Levels Are Contextual

While every Webacy analysis begins with a standardized risk score, the way that score is presented may vary depending on the entity being evaluated and the product consuming the intelligence.

Different blockchain assets exhibit different types of risk, and different workflows require different ways of communicating that risk. As a result, Webacy may expose specialized severity frameworks that are tailored to a particular domain while remaining grounded in the same underlying risk intelligence.

## Standard Severity Levels

Webacy generally categorizes risk into four severity levels.

<Info>
  ***Note:***\_ Some entity types may define additional severity bands or specialized classifications depending on the scoring methodology being used.\_
</Info>

<Frame>
  <img src="https://mintcdn.com/webacy/WOwccSluwNfjURJB/images/Screenshot-2026-08-06-at-3.52.38-PM.png?fit=max&auto=format&n=WOwccSluwNfjURJB&q=85&s=aba0b9e362d86c18394ef36e7836fe64" alt="Screenshot 2026 08 06 At 3 52 38 PM" width="1266" height="126" data-path="images/Screenshot-2026-08-06-at-3.52.38-PM.png" />
</Frame>

| Severity    | Score Range | General Interpretation                                                                                         |
| ----------- | ----------- | -------------------------------------------------------------------------------------------------------------- |
| 🟢 Low      | 0-24        | Minimal observed risk. No significant indicators requiring action                                              |
| 🟡 Medium   | 25–49       | Elevated risk signals are present and may warrant additional review or monitoring.                             |
| 🟠 High     | 50-74       | Significant risk indicators have been identified. Increased scrutiny or automated controls may be appropriate. |
| 🔴 Critical | 75-100      | Severe risk requiring immediate attention or automated response.                                               |

## Asset Monitoring Severity

Used for products such as stablecoin monitoring, where the emphasis is on operational response.

<Frame>
  <img src="https://mintcdn.com/webacy/WOwccSluwNfjURJB/images/Screenshot-2026-08-06-at-4.04.07-PM.png?fit=max&auto=format&n=WOwccSluwNfjURJB&q=85&s=605897c58b3781bbbb20abcdc8e9d7fd" alt="Screenshot 2026 08 06 At 4 04 07 PM" width="1271" height="124" data-path="images/Screenshot-2026-08-06-at-4.04.07-PM.png" />
</Frame>

| Tier     | Score Range | Typical Meaning                   |
| -------- | ----------- | --------------------------------- |
| OK       | \< 40       | Operating normally                |
| Watch    | 40-59       | Monitor closely                   |
| Warning  | 60-79       | Elevated risk requiring attention |
| Critical | 80+         | Immediate action recommended      |

## Why Severity Exists

Severity levels provide a common language for risk across the Webacy platform.

Rather than requiring every application to interpret raw numerical scores differently, developers can build consistent user experiences and automated workflows using standardized severity levels.

Common uses include:

* Alert prioritization
* Policy enforcement
* Transaction approval workflows
* Asset listing decisions
* Treasury monitoring
* Case management
* AI agent decision making

## Severity is Contextual

Severity should be interpreted within the context of the entity being analyzed.

A **High** severity wallet, transaction, stablecoin, or vault may represent very different underlying risks, even if their numerical scores fall within the same range. Severity communicates the urgency of the situation, not the specific cause of the risk.

To understand *why* an entity received its severity, developers should examine the underlying risk factors, detection engines, and supporting intelligence included in the analysis.

## Built for Automation

Severity levels are designed to make automated decision making straightforward.

Many integrations use severity as the primary input for configurable policies, such as:

* Block transactions above **High**
* Generate alerts for **Critical** events
* Escalate **High** findings for manual review
* Notify AI agents when severity changes
* Pause treasury operations when monitored assets become **Critical**

Because severity levels are standardized across the platform, the same policy framework can be applied consistently to many different blockchain entities.

## What's Next

<Card title="Data Quality and Confidence" icon="arrow-alt-circle-up" horizontal href="/data-quality-and-confidence">
  Understand how Webacy measures confidence, validates data quality, and builds explainable, high-precision risk intelligence.
</Card>
