15 Nov 2026 By CISO Consulting team 25 views 4 min read

SAMA CFF Digital Banking Fraud Controls Review Method

Most fraud reviews end in a long findings list that nobody can act on. This article walks through the phases of our review of digital banking fraud controls and what the client holds at the end of each one.

A fraud prevention team in a Riyadh office reviewing a customer journey map on a wall display.
In this article
  1. What the review covers
  2. Phase 1: Map customer journeys and their controls
  3. Phase 2: Threat-model fraud scenarios for each step
  4. Phase 3: Test controls and walk through scenarios
  5. Phase 4: Recommend a prioritized roadmap
  6. Full list of deliverables
  7. Related work
  8. Planning your review

Fraud teams in Saudi banks and fintechs rarely lack observations. They lack a sequence: what to fix first, what depends on what, and what each fix does to the customer experience. This article describes our SAMA CFF digital banking fraud controls review method, phase by phase, so that you can plan one with clear expectations of who is involved and what you will hold at the end.

The SAMA Cyber... rather, the SAMA Counter-Fraud Framework (CFF) is the reference point for the review, alongside SAMA CSF and PCI DSS where they apply to the channel under review.

What the review covers

Our Digital Banking and Payment Fraud Controls Review is an end-to-end review of fraud controls in mobile and internet banking, eKYC onboarding (Nafath), device binding, transaction signing and customer notifications. The aim is to secure every customer journey, from onboarding to payment.

The assessment runs 4–8 weeks depending on scope. The method below follows four phases, and a four-week engagement fits a focused scope of channels and journeys.

Phase 1: Map customer journeys and their controls

The first phase establishes what actually exists. We map each customer journey, such as onboarding, device binding, login, payment initiation and transaction signing, and place every control on it: where identity is checked, where a device is trusted, where the customer is asked to confirm, and where they are notified.

Who takes part on the client side: the owner of the digital channel, the fraud-prevention lead, and representatives from authentication, onboarding and customer notification. Their role is to confirm how journeys work in practice, which often differs from the design documents.

What the client holds at the end: an agreed map of journeys and control points, which becomes the common reference for every later phase.

Phase 2: Threat-model fraud scenarios for each step

With the map agreed, we threat-model fraud scenarios for each step. Typical scenarios include account takeover through a stolen credential, onboarding with misused identity, a new device bound under social pressure, a customer coached into approving a payment, and mule accounts receiving the proceeds.

This is where customer journey threat modeling is done in detail. We also look at social-engineering and mule-account controls, because many losses in digital channels begin with a persuaded customer rather than a technical break.

Who takes part on the client side: fraud analysts, investigators and the channel owner. Their case experience tells us which scenarios deserve the most attention.

What the client holds at the end: a scenario list tied to specific journey steps, agreed before any testing begins.

Phase 3: Test controls and walk through scenarios

Here we test each control against the scenarios from phase 2, through control testing and scenario walkthroughs. The review includes authentication and device trust, and a review of customer awareness and notifications: whether a customer would actually notice and understand a warning at the moment it matters.

Two questions come up consistently.

  • Do you test the live app? With your approval we test in a pre-production environment; live testing is limited to agreed, safe scenarios.
  • Does this include penetration testing? No, it focuses on fraud controls. It pairs well with our penetration testing service.

Who takes part on the client side: the technical team that provides the pre-production environment, the channel owner who approves any live scenario, and fraud operations who explain how alerts and interventions are handled.

What the client holds at the end: fraud scenario test results showing, for each scenario, whether the control held, partly held or failed.

Phase 4: Recommend a prioritized roadmap

The last phase turns results into decisions. We recommend a prioritized roadmap with experience impact, so that each remediation is considered for its effect on the customer as well as on fraud exposure. Stronger friction at the wrong step can push customers toward less safe behavior, and the roadmap should show that trade-off openly.

In sequencing, we consider dependencies between actions, the SAMA CFF expectations that bear on each gap, and the effort each fix is likely to need. Where a regulatory reference is relevant, we name SAMA and the framework and describe the expectation plainly.

Who takes part on the client side: the CISO, the head of fraud prevention, the channel owner and, where decisions on customer experience are needed, product leadership. A working session to challenge the sequence is more useful than a review of a finished document.

What the client holds at the end: a remediation roadmap that the team can take into planning and budgeting, and that a board or committee can follow.

Full list of deliverables

  • Journey-by-journey control assessment
  • Fraud scenario test results
  • Remediation roadmap

Related work

A review identifies what to fix. Two neighboring services address what follows. Our Fraud Detection and Transaction Monitoring Optimization service reviews and tunes the rules, scores and workflows of a fraud monitoring system across cards, mada, SARIE, instant payments and digital channels. Our Fraud Management Solution service covers vendor-independent selection and implementation of a fraud management system.

Planning your review

If you are preparing a digital-channel fraud review, start by listing the journeys in scope and naming a client-side owner for each. That alone shortens the first phase. To discuss scope and timing for a Digital Banking and Payment Fraud Controls Review, contact CISO Consulting and we will outline how the phases would apply to your channels.

Tags: SAMA CFF digital banking fraud fraud controls review eKYC Nafath device binding remediation roadmap
Readiness self-check

How ready are you? Find out in two minutes

Answer a few questions for your framework. You get a score, your biggest gaps and — if you want it — a detailed assessment from our team.

Ready to talk about your compliance?

Tell us where you stand. We will show you the shortest path to what your regulator expects.

Regulatory updates in your inbox

SAMA, NCA and SDAIA changes and what they mean for your institution — once a month.

E-mails in

We confirm by e-mail; unsubscribe any time. Manage your subscription · Past issues

Schedule a Free Assessment