Risk controls

Sentinel — risk controls

Sentinel is where the institution runs risk cases. If identity or permission cannot be confirmed, the sensitive step does not go through.

For your technology team. Sentinel runs the institution’s risk controls and the risk workflows that rely on evidence. Other platforms send it risk events; Sentinel owns each risk case from start to finish. It does not keep the customer record (CIF) or the ledger.

What it does

  • Receives risk events from channels and from money platforms.
  • Scores the events the institution has configured it to watch.
  • Makes a real-time decision on those events.
  • Opens a case when something must be reviewed by a person.
  • Supports screening and a look at behavior over time.
  • Tracks what was enforced after a decision.
  • Keeps the evidence of the case, with Scribe when documents are part of it.
  • If identity or permission cannot be confirmed, the sensitive step does not go through.

Who uses it

Fraud, risk, and investigation teams.

Detail for your technology team

  • Risk and fraud cases, and a workspace for risk decisions
  • Stops if Aegis or Atlas cannot confirm sign-in and permission
  • Evidence kept through a document platform, where set up

How it connects

Sentinel CONNECTS TO Aegis / Atlas Required sign-in and permissions Scribe Evidence Channels and money platforms Send risk events (Pulse and others, as set up)
Connections named on this page, with the platform marks. The diagram does not show balances or a live screen.
  • Aegis / AtlasRequired sign-in and permissions
  • ScribeEvidence
  • Channels and money platformsSend risk events (Pulse and others, as set up)

What it is not

The customer master file (CIF); the ledger; payment rails; the institution’s official document store.