Study guide
Data Privacy, Cybersecurity, and Other Risk Functions
CAMS Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: CAMS Orientation and Exam Facts
Current CAMS Exam Format Eligibility Credits and ACAMS Membership Package Pricing and Study Materials Pearson VUE Scheduling Window Passing Score and Result Reporting Exam Non-Disclosure and Practice Ethics
2 Chapter 2: Financial Crime Risks and Methods
AML, CFT, Sanctions, Fraud, ABC, and Tax Evasion Financial Systems and AFC Consequences Predicate Crimes and Financial Crime Exposure Sector, Product, Customer, Jurisdiction, and Channel Risk Banking Products and High-Risk Sectors Politically Exposed Persons and High-Risk Customers
3 Chapter 3: High-Risk Sectors and Structures
MSBs, PSPs, and E-commerce Platforms Insurance Product Risk VASPs, Cryptoassets, and Related Products Gaming, Gambling, and Real Estate Gatekeepers, Trusts, and Company Service Providers Accountants and Other High-Risk Structures
4 Chapter 4: Global AFC Frameworks
FATF Role and Recommendations United Nations Sanctions Regimes Regulators, Law Enforcement, and FIUs Public Sector, Private Sector, and NGO Objectives Cross-Border Cooperation Authority Reports, Trends, and Typologies
5 Chapter 5: Governance Regulations and Information Sharing
Risk-Based Regulatory Expectations Regulatory Examinations and Enforcement Public-Private Partnerships Information Sharing Mechanisms De-Risking and Financial Inclusion RFIs, Tipping Off, and Customer Communication
6 Chapter 6: AFC Compliance Program Design
Effective Program Pillars Three Lines of Defense and MLRO Role Risk Appetite Statement Enterprise Risk Assessment Risk-Based Controls Policies Standards and Procedures
7 Chapter 7: Program Governance and Operating Model
Horizon Scanning and Regulatory Guidance Governance Committees and Terms of Reference AFC Team Structure and Responsibilities Front Office Interaction Supporting Functions and Risk Partners Training, Awareness, and Staff Risk Culture
8 Chapter 8: Customer Lifecycle Controls
Control Tools Across the Customer Lifecycle Data Quality, Integrity, Access, and Taxonomy Customer Experience and Friction Digital Onboarding and Electronic KYC (e-KYC) External Data Sources and Beneficial Ownership Customer Screening and Sanctions Lists
9 Chapter 9: Ongoing Controls and Monitoring
Periodic Refresh and Perpetual KYC Adverse Media Screening Batch Screening and Fuzzy Logic Transaction and Payment Screening Rules-Based Transaction Monitoring Model Risk Management and Tuning
10 Chapter 10: Investigations and Case Support
Investigation Triggers and Case Triage Open Source Tools and Investigator Support Escalation and Suspicious Activity Decisions Documentation and Evidence Quality Law Enforcement and FIU Requests Post-Investigation Feedback Loops
11 Chapter 11: Technology and Emerging AFC Practice
AI and Machine Learning in AFC Controls Blockchain Transaction Screening Automation to Support Investigators Scenario Coverage and Threshold Setting Data Privacy, Cybersecurity, and Other Risk Functions Technology Governance for AFC Tools
12 Chapter 12: Final CAMS Review and Exam Day
Domain-Weighted Study Allocation Simulator Practice Without Actual Exam Claims Pearson VUE Identification and Test Rules Time Management and Guessing Strategy Retake Extension and Appeal Boundaries Recertification and Ongoing Membership
Data Privacy, Cybersecurity, and Other Risk Functions
Key Takeaways Explain This Topic AI
Data-privacy laws (e.g., the EU GDPR) restrict how customer data is used and shared, sometimes tensioning with AML data-sharing needs.
AML, fraud, cyber, and sanctions functions increasingly converge; cyber-enabled fraud and ransomware payments are reportable financial crime.
Information-sharing safe harbors (e.g., USA PATRIOT Act Section 314(b)) allow institutions to share AML information without violating privacy or tipping-off rules.
A privacy regime does not override AML reporting duties; SAR confidentiality and lawful AML processing generally coexist with data-protection law.
Last updated: June 2026
Where AML Meets Privacy and Cybersecurity
Modern financial-crime programs sit alongside several adjacent risk functions, and the CAMS exam tests the boundaries between them.
Data privacy. Laws such as the European Union's General Data Protection Regulation (GDPR) govern how personal data is collected, processed, retained, and transferred across borders. AML programs are inherently data-hungry (KYC, screening, monitoring), so tension arises: privacy law limits use, while AML law compels collection and retention. The reconciling principle is that AML processing is generally a lawful obligation , so institutions may process and retain data for AML purposes, but only what is necessary and for defined periods.
Privacy law does not excuse failing to file a SAR, and SAR confidentiality rules continue to apply.
Cybersecurity. Breaches, account takeovers, business email compromise (BEC), and ransomware are both security incidents and financial crimes . In the U.S., facilitating or processing ransomware payments can itself raise OFAC sanctions exposure, and related suspicious activity is reportable.
- Function Primary concern Overlap with AML
- Data privacy Lawful, limited use of personal data KYC/screening data; cross-border transfers; retention
- Cybersecurity Confidentiality, integrity, availability Account takeover, BEC, ransomware payments
- Fraud Loss from deception Mule accounts, scams, fraud proceeds laundered
- Sanctions Prohibited parties/jurisdictions Screening, ransomware payee, VA addresses
The practical takeaway is that these functions share data and signals. A privacy team's data-retention schedule, for instance, directly affects whether AML can keep the records it is legally required to retain (in the U.S., the Bank Secrecy Act generally requires retaining certain records for five years ). A cybersecurity team's breach detection may be the first indicator of an account takeover that the AML team must then report. Treating these as isolated silos is the failure mode the exam warns against; coordinated governance, with clear ownership and shared escalation paths, is the expected answer.
Convergence and Lawful Information Sharing
The industry trend is convergence : combining AML, fraud, and cyber into a single financial-crime view (sometimes called FRAML , fraud + AML). Convergence matters because the same data often reveals both a scam (fraud) and the laundering of its proceeds (AML), and a single cyber event can trigger reporting in multiple regimes.
A key enabler is the information-sharing safe harbor . In the U.S., USA PATRIOT Act Section 314(b) lets participating financial institutions share information with each other about suspected money laundering or terrorist financing, protected from liability, without breaching privacy law or tipping-off rules. Section 314(a) is the separate channel through which FinCEN relays law-enforcement requests to institutions. Knowing 314(a) (government-to-institution) versus 314(b) (institution-to-institution) is a classic exam point.
Worked scenario
A cyber team detects a BEC attack that diverted a customer wire to a mule account at another bank. The integrated response: the fraud team recovers what it can, the cyber team remediates, and the AML team files a SAR describing the cyber-enabled event (FinCEN expects cyber-event and cyber-enabled-crime SARs). The institution may use 314(b) to coordinate with the receiving bank. It must not disclose the SAR's existence to the customer or the counterparty.
Cross-border data flows add a further layer. A global institution running centralized monitoring may need to move customer data from a GDPR jurisdiction to a hub in another country. GDPR restricts such transfers unless an approved mechanism (such as standard contractual clauses or an adequacy decision) is in place.
The exam-correct posture is that the institution designs its AML data architecture to be compliant with both regimes simultaneously , rather than treating one as overriding the other: it processes the minimum necessary data for a clearly lawful AML purpose, retains it only for required periods, secures it, and documents the legal basis. Privacy and AML are reconciled by careful design, not by choosing a winner.
Exam reminders:
Privacy law restricts use , but AML reporting duties and SAR confidentiality still govern.
314(a) = government → institutions; 314(b) = institution to institution (voluntary, with safe harbor).
Cyber-enabled fraud and ransomware are reportable financial crime, not just IT problems.
BSA record-retention (generally five years ) coexists with privacy-law data-minimization through a documented lawful basis.
Convergence improves detection but never relaxes the duty of SAR secrecy or proportional data use.
The broader exam theme is that AFC is a team sport across risk functions . Sanctions screening protects against prohibited parties; fraud controls catch deception and identify mule networks; cybersecurity detects intrusions that enable both; data privacy keeps the institution lawful in how it uses the resulting information; and AML ties it together through monitoring and reporting. A weakness in any one function becomes a weakness in the others, because criminals exploit the seams between silos, for example using a stolen identity (cyber) to open an account, run a scam (fraud), and launder the proceeds (AML) all in one chain.
Candidates should be ready to identify, in a scenario, which functions a given fact pattern implicates and how they coordinate, while remembering that the AML reporting duty and SAR confidentiality remain non-negotiable regardless of how the work is shared.