> For the complete documentation index, see [llms.txt](https://docs.compliance.phalcon.blocksec.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.compliance.phalcon.blocksec.com/manual/configure/risk-engines.md).

# Risk Engine

Risk Engine is the core risk detection module of Phalcon Compliance. It provides configurable rules for detecting exposure risk and behavioral risk across addresses and transactions.

Although we provide default rules, we recommend reviewing and adjusting them based on your specific business needs and user profiles, and continuously optimizing them to address emerging risks.

The module is organized into four tabs:

* **Overview** — A read-only dashboard of your rule coverage and overlap warnings. See [Overview](https://docs.compliance.phalcon.blocksec.com/manual/configure/risk-engines/overview.md).
* **Rules** — View, create, and manage all risk rules. See below.
* **Lists** — Blacklists, Whitelists, and Rule Whitelists. See [Lists](https://docs.compliance.phalcon.blocksec.com/manual/configure/risk-engines/lists.md).
* **Settings** — Default Rule Set version and cross-chain tracking. See [Settings](https://docs.compliance.phalcon.blocksec.com/manual/configure/risk-engines/settings.md).

We provide two types of risk detection:

* **Exposure Risk**: Detects interactions with high-risk entities (such as sanctioned addresses and mixers).
* **Behavioral Risk**: Identifies abnormal fund flow patterns (such as rapid transfers and layering).

📌 Learn more:

{% content-ref url="/pages/hY4aEuFLGON8eMBl4NAw" %}
[Risk Exposure Engine](https://docs.compliance.phalcon.blocksec.com/manual/configure/risk-engines/exposure.md)
{% endcontent-ref %}

{% content-ref url="/pages/d65aytWGmRD4yOOQBMSk" %}
[Behavioral Risk Engine](https://docs.compliance.phalcon.blocksec.com/manual/configure/risk-engines/behavior.md)
{% endcontent-ref %}

## Rules

### Default Rules and Custom Rules

Rules come in two types, with different levels of control:

| Action                                                    | Default Rules | Custom Rules |
| --------------------------------------------------------- | ------------- | ------------ |
| View details                                              | ✅             | ✅            |
| Enable / Disable                                          | ✅             | ✅            |
| Clone                                                     | ✅             | ✅            |
| Edit notification channels and Rule Whitelists            | ✅             | ✅            |
| Edit detection logic (risk level, indicators, thresholds) | —             | ✅            |
| Delete                                                    | —             | ✅            |

**Default Rules** are provided by BlockSec based on FATF guidelines and industry best practices, and are managed as a versioned set. See [Default Rules](https://docs.compliance.phalcon.blocksec.com/manual/configure/risk-engines/default-engines.md).

**Custom Rules** are created by your team with full control over all settings. Your plan determines how many you can have.

### Rule List

The Rules tab lists every rule in a single table.

<figure><img src="https://1419887533-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPfx6yOSRmp0GCnHv5rhy%2Fuploads%2Fgit-blob-c12c3bb2fc125190de652538cfb4ae127de2595d%2Frisk-engine-rules-tab.png?alt=media" alt="Rules tab with filter bar and rule table"><figcaption></figcaption></figure>

You can filter by target type, template, and risk level, and open **More Filters** for source, status, risk indicator, whether a rule has overlaps, and whether it has never triggered in the past 30 days. You can also search by rule name, sort the table, choose which columns to show, and export the matching rules to CSV.

Rules can be enabled, disabled, cloned, or deleted individually or in bulk, and you can map notification channels to several rules at once. Deletion applies to Custom Rules only.

### Create a Rule

Click **Create Rule**, then:

1. **Select a template** — Pick the target type (Address or Transaction) and what you want to detect. Templates are grouped into Exposure Risk and Behavioral Risk, and the options depend on the target type.
2. **Configure the rule** — Set its name, risk level, and status; the detection target and trigger thresholds for that template; an optional Rule Whitelist; and the [notification channels](https://docs.compliance.phalcon.blocksec.com/manual/configure/notification-channels.md) that should receive its alerts.

<figure><img src="https://1419887533-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPfx6yOSRmp0GCnHv5rhy%2Fuploads%2Fgit-blob-b06d8e5974c87c43d9c74e654337c693790e4a87%2Frisk-engine-select-template.png?alt=media" alt="Select Template dialog for an address rule"><figcaption></figcaption></figure>

If the new rule overlaps with an existing one, Phalcon tells you once it is created. The rule is still saved — overlap is a warning, not a blocker.

### Rule Detail

The Rule Detail page shows a rule's full configuration and how it has performed.

<figure><img src="https://1419887533-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPfx6yOSRmp0GCnHv5rhy%2Fuploads%2Fgit-blob-408bf2f2faa1fc8b10bc4867ffa5798ba944e75d%2Frisk-engine-rule-detail.png?alt=media" alt="Rule Detail page for a Default rule"><figcaption></figcaption></figure>

* **Detection Target** — Which risk indicators and screen directions this rule detects.
* **Trigger Thresholds** — The conditions that make it fire.
* **Rule Whitelist** — Lists that exempt subjects from this rule.
* **Notification Channels** — Linked alert channels.

A sidebar shows the alerts this rule has triggered along with its trigger rate, and an audit log of every change made to the rule.

For Custom Rules, you can edit any of this in place. For Default Rules, you can change the status, notification channels, and Rule Whitelist associations, but not the detection logic.

### Overlap Warning

If a rule overlaps with others, a banner on its detail page links to a breakdown of which rules overlap and exactly which conditions coincide.

<figure><img src="https://1419887533-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPfx6yOSRmp0GCnHv5rhy%2Fuploads%2Fgit-blob-2c0760218ec9679599139f69fb920b51a21c9ab1%2Frisk-engine-overlap-detail.png?alt=media" alt="Overlap Detected dialog"><figcaption></figcaption></figure>

Overlapping rules may both fire on the same target. This is sometimes intentional — for example, different risk levels for different thresholds. See [Rule Overlap](https://docs.compliance.phalcon.blocksec.com/manual/concepts.md#rule-overlap).

### Export a Report

From a rule's detail page you can download a report summarizing its settings, triggered alerts, and audit logs, as a PDF or CSV. It can be used as compliance documentation.
