Every Threshold Owned.
Every Change Logged.
Screening thresholds, risk weights, access policy, and retention periods — configured at the institution level, with every change traced back to who made it and when.
The Controls a Regulator
Expects to See.
Ownership, oversight, and a documented audit trail — the minimum governance elements the CBN Baseline Standards call out by name.
Sanctions List Configuration
Choose which lists screen every customer — OFAC, UN, EU, HMT — and set the match-confidence threshold your team investigates at.
PEP Data Sources
Toggle Global PEP, Local PEP, and RCA (Relatives & Close Associates) sources, with an independently configurable PEP match threshold.
Risk Scoring Weights
Tune how much KYC verification, transaction volume, geographic risk, PEP status, and sanctions screening each contribute to a customer's risk score.
Access Control
Enforce two-factor authentication, set session timeout, and cap failed login attempts before lockout — institution-wide.
IP Allowlisting
Restrict administrative access to named IP ranges, and set a password expiry policy your team can't bypass.
Data Retention Policy
Set retention periods for PII, transaction records, and audit logs independently — aligned to your regulator's record-keeping requirements.
Audit Trail
Every configuration change — who changed what, and when — is logged and immutable, ready for supervisory review.
Change Accountability
Configuration lives at the institution level, not a shared default — every threshold, weight, and policy is owned and traceable.
Governance Is a
Requirement, Not a Feature.
A detection engine with no ownership, no change control, and no documented oversight isn't defensible — regardless of how sophisticated it is. Governance is what turns a set of thresholds into a control environment a supervisor can actually assess.