Study guide

6.3 Controlling Internal Threats: Insider Fraud, Collusion, and Data Misuse

ACAMS Certified AML FinTech Compliance Associate CAFCA

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: CAFCA Exam Overview and Study Strategy

1.1 CAFCA Exam Format, Official Domains, and Study Strategy

2 Chapter 2: Domain 1: FinTech Business Models and Their Vulnerabilities

2.1 Neobanks, Challenger Banks, and Digital Banking Models 2.2 Payment Processors, Gateways, and Merchant Acquirers 2.3 Buy Now, Pay Later (BNPL) and Alternative Credit 2.4 BaaS Architecture, Embedded Finance, and Program Structures

3 Chapter 3: Domain 1: Financial Crime Types and the Regulatory Perimeter

3.1 Types of Financial Crime and Predicate Offences 3.2 Licensing, Registration, Charters, and Regulatory Sandboxes 3.3 Virtual Asset Service Provider (VASP) Framework & FinCEN MSB Rules

4 Chapter 4: Domain 1: Global AML Frameworks and Sources of Guidance

4.1 U.S. Regulatory Architecture: BSA, PATRIOT Act, and AMLA 2020 4.2 European Union Regulatory Framework: AMLD6, the AML Package, and MiCA 4.3 International Standards: UK FCA, Singapore MAS, and Hong Kong HKMA 4.4 Sources of Guidance for Building Anti-Financial Crime Processes

5 Chapter 5: Domain 1: Risk Management Framework, Risk-Based Approach, and Data Protection

5.1 Risk Management Framework: Lines of Defence, Policies, Assurance, and the MLRO 5.2 Risk-Based Approach, Risk Assessment, Risk Appetite, and Types of Risk 5.3 Handling Sensitive Information: PII, SPII, Privacy Laws, and Breach Reporting

6 Chapter 6: Domain 1: Bank Partners and Internal Threats

6.1 Regulatory Expectations and Enforcement on Sponsor Banks 6.2 How Banks Risk-Rate FinTechs: Onboarding, Ongoing Oversight, and De-Risking 6.3 Controlling Internal Threats: Insider Fraud, Collusion, and Data Misuse

7 Chapter 7: Domain 2: CIP, KYC, CDD, and EDD

7.1 Customer Identification Program (CIP) Under USA PATRIOT Act §326 7.2 The FinCEN CDD Rule & Beneficial Ownership Standards 7.3 KYC to EDD: Applying CDD and Enhanced Due Diligence Across Customer Types

8 Chapter 8: Domain 2: Identity Verification, Data Sources, and Device Data

8.1 Digital Onboarding & Electronic KYC (eKYC) Foundations 8.2 Biometric Face Matching and Liveness Detection 8.3 Verification Data Sources and How to Judge Their Reliability 8.4 Device Fingerprinting, Geolocation, and Behavioral Biometrics

9 Chapter 9: Domain 2: Onboarding Screening, Risk Ratings, and Fraud Red Flags

9.1 Screening at Onboarding: Sanctions Lists, PEPs, and Known Fraudsters 9.2 Customer Risk Ratings: Factors, Data Sources, and How Scoring Models Work 9.3 Detecting Synthetic Identity Fraud and Ineligible Applicants 9.4 Deepfakes, Generative AI Threats, and Scam Typologies

10 Chapter 10: Domain 3: Payment Screening

10.1 OFAC Sanctions Regimes & the 50 Percent Rule 10.2 Real-Time vs. Batch Screening Architecture in High-Velocity Rails 10.3 Screening Logic: Fuzzy Matching, Phonetics, and PEP Controls

11 Chapter 11: Domain 3: Transaction Monitoring Systems and Red Flags

11.1 Hybrid Transaction Monitoring: Rules Engines vs. Machine Learning 11.2 FinTech Typologies: Mule Networks, Funnel Accounts, and Rapid Pass-Through 11.3 Fraud-AML Convergence: BIN Attacks, ATO, and Credential Stuffing 11.4 Model Risk Management Under SR 11-7 & System Optimization

12 Chapter 12: Domain 3: Payment Methods and Transaction Risk Characteristics

12.1 Common Payment Methods, Crypto, and High-Risk Transactions Such as Aggregation 12.2 Transaction Risk Characteristics: Reversibility, Convertibility, Fund Integrity, and Privacy Coins 12.3 Wallet Types, Custody Architectures, and Counterparty Risks 12.4 Stablecoins, On/Off Ramps, and Asset-Referenced Tokens

13 Chapter 13: Domain 3: Monitoring Crypto Transactions

13.1 Blockchain Analytics & Transaction Tracing 13.2 The FATF Travel Rule for Virtual Assets 13.3 DeFi, Mixers, and Smart Contract Sanctions

14 Chapter 14: Domain 3: Alert Investigation, Audit Trails, and Monitoring MI

14.1 The Alert Investigation Process: From Unusual to Suspicious and When to Escalate 14.2 Building an Audit Trail for Suspicious Activity Reviews 14.3 Communicating Monitoring Results: KPIs, KRIs, OKRs, and Management Information

15 Chapter 15: Domain 4: Investigations and Customer Communication

15.1 Talking to Customers During Investigations and Offboarding: Financial Crime Risk vs Policy Breach 15.2 Reviewing KYC, Transactions, Open Sources, and Documents to Build an Investigation 15.3 Analytical Principles in Investigations: Avoiding Confirmation Bias and Other Traps

16 Chapter 16: Domain 4: SARs and STRs

16.1 SARs and STRs: What They Are, When and Where to File, and Why They Matter 16.2 Writing Effective SAR and STR Narratives

17 Chapter 17: Domain 4: Law Enforcement, Regulators, and Banking Partners

17.1 Operational AML Governance and Third-Party Risk Management 17.2 Working With Law Enforcement, Banking Partners, Regulators, and Other Third Parties 17.3 Types of Law Enforcement Requests: Subpoenas, Court Orders, 314(a), and International Requests 17.4 How Banking Partners' Terms of Service Relate to the FinTech's Own Terms

18 Chapter 18: Domain 5: Scaling Anti-Financial Crime Strategies

18.1 Assessing New Products and Features Before Launch 18.2 Refreshing the Financial Crime Risk Assessment as the Business Scales 18.3 Changes That Should Trigger a Financial Crime Risk Assessment Review 18.4 Record Retention Rules and Secure Data Storage 18.5 Outsourcing Controls: Surge Capacity, RegTech, and Independent Testing

6.3 Controlling Internal Threats: Insider Fraud, Collusion, and Data Misuse

Key Takeaways Explain This Topic AI

Insider threats include internal fraud, collusion with external criminals, data theft and misuse of privileged access by staff, contractors or outsourced agents.

The UK Money Laundering Regulations require screening of relevant employees where appropriate to the firm's size and nature.

US banks must file a SAR for insider abuse involving any amount, without the usual dollar thresholds.

Maker-checker approval for whitelist changes, limit overrides and account recovery is a core control against insider-enabled fraud.

Last updated: October 2026

CAFCA sub-topic 1.9 asks for a control framework to mitigate internal threat . FinTechs give many people powerful access. Customer support agents can change phone numbers and reset two-factor authentication, engineers can query production databases, analysts can close alerts or whitelist names, and outsourced teams handle queues around the clock. Criminals know this and recruit insiders.

What insider threat looks like

Insider risk How it happens in a FinTech Damage

Collusion with fraud rings Support agent changes contact details on target accounts for a bribe, enabling account takeover Customer losses, reimbursement costs, reputational harm

Mule account facilitation Onboarding staff approve accounts with known-bad documents or override verification failures Laundering through the platform

Alert suppression Analyst closes alerts without review, or whitelists a counterparty linked to a criminal network Missed SARs; regulatory breach

Data theft and sale Employee exports customer data or sells credentials Privacy breach, fraud against customers

Tipping off Staff member warns a customer about an investigation Criminal offence; failed investigation

Rule or code tampering Engineer changes a monitoring rule or screening threshold without approval Silent control failure

Unwitting insiders Staff fall for phishing or social engineering that gives criminals access Same damage as a malicious insider

The control framework

Think in four layers: prevent, detect, respond and culture .

Prevent

Pre-employment screening in proportion to the role: identity, right to work, references and, where lawful, criminal record and credit checks. Repeat screening for sensitive roles. The UK Money Laundering Regulations require screening of relevant employees where appropriate to the firm's size and nature.

Least privilege and role-based access : staff get only the permissions their role needs. Remove access promptly when people move roles or leave.

Segregation of duties : the person who requests a change is not the person who approves or releases it. For example, the engineer who writes a monitoring rule change is not the one who deploys it.

Maker-checker (four-eyes) approvals for high-risk actions: whitelist additions, limit overrides, manual releases of held payments, account recovery and contact changes, and fee refunds above thresholds.

Privileged access management for production systems: just-in-time access, session recording and break-glass procedures.

Change management for rules, models and screening lists, with versioning and audit trails (Chapter 11).

Detect

User activity monitoring : log every sensitive action and review the logs. Look for unusual patterns, such as one agent handling an outsized number of contact changes on accounts later hit by fraud.

Staff account monitoring : review employees' own accounts on the platform where the law permits.

Data loss prevention tools: alerts on bulk exports, personal email use and unusual downloads.

Mandatory leave or job rotation for roles with powerful access. Some schemes only work when the insider is present every day.

QC and second-line sampling that deliberately includes high-risk overrides.

Respond

A documented insider investigation protocol involving compliance, security, HR and legal, with evidence preserved.

Immediate access revocation when misconduct is suspected.

Reporting : US banks must file a SAR for insider abuse involving any amount. Other regimes treat insider involvement as an aggravating factor for STRs. Notify the partner bank where the contract requires it.

Root-cause fixes : which control failed, and is the same weakness present elsewhere?

Culture

Training that explains insider red flags and how criminals approach staff, especially in support and operations centres.

Conflict-of-interest declarations and a gifts and hospitality register.

Whistleblowing and speak-up channels that protect reporters.

A tone from the top : leaders who reward escalation rather than speed at any cost.

Outsourced and offshore teams

Outsourcing does not move insider risk outside the firm. Contracts should require screening standards, access restrictions, monitoring rights, incident notification and audit access. The firm should test them in practice, for example by reviewing the vendor's access logs for its own queues.

Realistic exam scenario

Fraud analytics finds that 70% of account takeovers this quarter followed a phone-number change made by one of three outsourced support agents. All three work the same night shift. The firm should suspend the agents' access to sensitive functions at once and preserve the logs. It should notify the vendor under the contract, investigate jointly, and assess SAR obligations for both the takeovers and the suspected insider involvement. It should then add maker-checker approval and step-up verification for contact changes. Retraining alone would leave the control gap open.

Common exam traps

"Senior or long-serving staff are low risk." Insider cases often involve trusted people with wide access.

Logs that nobody reviews. Logging is not a control unless someone acts on it.

One-time background checks for powerful roles.

Leaving offboarded staff with live access.