RiskLense
Risk and regulatory context. Layer 2 of the Strise platform.
RiskLense is the layer that encodes regulation, jurisdictional logic, and your internal risk policy into the platform — so every agent, module, and analyst operates within the same guardrails.
Why It Exists
Agents that reason freely on compliance data are unsafe. The difference between “AI assisting compliance” and “AI doing compliance” is the guardrails it operates within. RiskLense is those guardrails, rendered in code.
Regulation is the architecture, not a feature.
What’s Encoded
| Layer | What’s in it |
|---|---|
| EU regulation | AMLR, AMLA, 6AMLD, DORA |
| Jurisdictional logic | Country-specific rules — German GwG §15, French UBO restrictions post-CJEU 2022, UK PSC thresholds, Nordic beneficial-ownership rules, and many more |
| Your risk policy | Your team’s rules layered on top: which sectors auto-approve, which sanctions-adjacent links escalate, which thresholds trigger enhanced due diligence |
The platform keeps the regulation layer up to date. Your team controls the policy layer — rules, thresholds, and actions — without a data-science team.
What RiskLense Does
- Auto-classifies cases. Routine entities in low-risk sectors with resolved UBOs under the exposure threshold clear automatically.
- Escalates on rule match. Any sanctions-indirect link suspends the case, escalates to the MLRO queue, and notifies within the configured SLA.
- Routes by jurisdiction. German entities go through GwG §15 enhanced due diligence triggered by Anlage 2 risk factors; French entities pick up the post-CJEU collection flow; and so on.
- Drives the calculated-risk engine. Risk signals (PEPs, sanctions, high-risk countries, industries, legal forms, custom fields) feed into a single risk class per entity. See Calculated Risk.
- Feeds review triggers. Rule matches can open a review or complete one automatically, depending on the entity’s risk class. See Review Triggers.
Policy as Configuration
RiskLense rules are configured through the Settings UI, not a policy file. Each surface owns one slice of the policy:
| Surface | What it controls |
|---|---|
| Calculated Risk Settings | Which signals (sanctions, PEPs, countries, industries, legal forms, custom fields) contribute points, and the class thresholds. |
| Review Triggers | Which events open a review, auto-complete one, or stay silent — per risk class. |
| Risk Flag Settings | Which flags are actionable per jurisdiction, with severity and direction gates. |
| PEP Settings / Sanctions Settings | Which providers, lists, and match thresholds apply to screening. |
Changes take effect on the next evaluation — no data-pipeline work, no re-deploy. The Connect API exposes the same rules programmatically.
Built-In, Controllable, Auditable
- Built-in. AMLR, AMLA, 6AMLD, DORA, and country-specific rules ship with the platform.
- Controllable. Rules become guardrails through the Settings UI — no data-science team required.
- Auditable. Every policy evaluation is logged with its inputs, the rule that matched, and the action taken.
Related
- SuperData — what feeds RiskLense.
- Compliance Memory — what RiskLense writes to.
- Calculated Risk — the scoring model RiskLense drives.
- Review Triggers — how RiskLense actions open reviews.
- Risk Flag Settings — per-country flag configuration.