Book traversal links for 4.1 Counter-Fraud Solutions and Controls for Elevated Risk
4.1 Counter-Fraud Solutions and Controls for Elevated Risk
| No: 106897184 | Date(g): 14/4/2025 | Date(h): 16/10/1446 | Status: In-Force |
| Control ID | Control requirement description | ||||||||||||||||||
4.1.1 | Member Organizations should implement real-time fraud detection and prevention solutions to identify anomalies in transactional and non-transactional data, and monitor systems and internal accounts for transactions or behaviours that may be indicative of fraud. | ||||||||||||||||||
4.1.2 | Fraud detection systems should operate 24/7 with appropriate resources in place to manage outputs on a timely basis. | ||||||||||||||||||
4.1.3 | Member Organizations should ensure that the solutions and rules are designed or can be customised to align to the products, services, and fraud risks of the organization. | ||||||||||||||||||
4.1.4 | Member Organizations should implement controls that allow real-time actions such as freezing of accounts and blocking of transactions in a timely manner if a customer or Member Organization suspects an account has been compromised. | ||||||||||||||||||
4.1.5 | Member Organizations should use data and intelligence to screen and block transactions or access from identified high risk accounts; GPS locations; IP addresses; email addresses; devices that are subject to jailbreaking or rooting; use of VPN services when accessing online or mobile services; and compromised devices or those that have previously been used for fraud. | ||||||||||||||||||
4.1.6 | Member Organizations should implement device registration controls which allow users to register trusted devices for access management. | ||||||||||||||||||
4.1.7 | Member Organizations should implement controls to protect customers from payments and product application fraud, including but not limited to:
| ||||||||||||||||||
4.1.8 | Member Organizations should conduct multi-factor authentication checks to verify:
| ||||||||||||||||||
4.1.9 | Multi-factor authentication conducted by Member Organizations for identification and transaction verification should not solely consist of One Time Passwords (OTPs) sent via SMS. Member Organizations should implement additional factors, e.g.,
| ||||||||||||||||||
4.1.10 | Where a Member Organization sends an OTP via SMS, the purpose, amount and merchant name should be clearly defined and in line with SAMA approved notification templates. OTPs sent via SMS should be in the language selected by the customer on the account (e.g., Arabic, English). | ||||||||||||||||||
4.1.11 | Member Organizations should implement controls to detect mule accounts (e.g., accounts set-up to receive fraudulently obtained funds and launder the proceeds of crime) and take action to prevent the outward flow and recovery of funds. | ||||||||||||||||||
4.1.12 | Member Organizations should update controls, rules and decision-making models in solutions to mitigate fraud risks resulting from new and emerging fraud typologies identified through intelligence monitoring or root cause analysis and take proactive action to prevent fraud. | ||||||||||||||||||
4.1.13 | Where a customer relationship is initiated on a remote basis (e.g., online), Member Organizations should assess the risk of impersonation and the set-up of mule accounts, implementing appropriate controls to mitigate the risk, including but not limited to:
|