ACAMS CGSS Quick Review

Quick review for CGSS candidates: sanctions frameworks, governance, compliance programs, screening, ownership and control, investigations, evasion typologies, and 756-question Finance Prep practice.

Quick Review for CGSS Candidates

This quick review is for candidates preparing for the ACAMS Certified Global Sanctions Specialist (CGSS) exam. Use it to refresh high-yield sanctions concepts before moving into topic drills, mock exams, and detailed explanations in Finance Prep.

This page is independent review support. It is not affiliated with ACAMS and does not replace the official exam materials, current candidate guidance, or applicable laws and regulations in your jurisdiction.

Finance Prep currently has 756 original CGSS practice questions for sanctions practice. Use this page as a fast consolidation tool, then use topic drills and mixed practice to test whether you can choose the defensible sanctions-control step in a scenario.

How to Use This Quick Review

If you have…Best use of this pageThen practice
10 minutesReview the decision rules, alert handling table, and final checklistMixed CGSS questions in Finance Prep
30 minutesWork through governance, screening, ownership/control, and evasion sectionsOne topic drill from your weakest area
One study sessionRead the tables, write a short error log, then answer sample exam questionsFree CGSS Practice Exam
A weak mock scoreMatch each missed question to the topic map belowThe matching focused topic page

Best use: read one section, then answer original practice questions on that topic. CGSS questions usually test sequence and judgment: identify the sanctions risk signal, decide what evidence matters, choose the correct escalation or disposition step, and document the rationale.

High-Yield CGSS Review Map

AreaWhat to know coldCommon exam trap
Sanctions frameworksSanctions can target countries, sectors, persons, entities, vessels, goods, services, and ownership interestsTreating every sanctions issue as a simple name-list match
GovernanceSenior oversight, risk appetite, documented accountability, independent testing, and control ownership matterAssuming screening software alone is the sanctions program
Risk assessmentCustomer, geography, product, channel, transaction, ownership, and third-party exposure shape control strengthApplying the same screening and review depth to every relationship
ScreeningName, payment, customer, vendor, vessel, geography, and goods screening require match disposition and documentationClearing alerts only because the name is common
Ownership and controlSanctioned-party interests can flow through ownership, control, voting rights, or indirect benefitStopping at the direct customer name and ignoring beneficial ownership
EscalationPotential true matches, high-risk ambiguity, blocked/rejected activity, and evasion indicators need escalationLetting front-line staff resolve sanctions ambiguity without review
InvestigationsBuild the facts before deciding: parties, identifiers, routing, goods, documents, purpose, and historyJumping to a report or clearance without enough evidence
Evasion typologiesFront companies, transshipment, dual-use goods, altered documents, ownership opacity, and routing changes are key red flagsTreating one clean document as proof that the transaction is safe
Reporting and post-decision controlsBlocking, rejection, reporting, account restrictions, and senior/legal escalation depend on facts and jurisdictionChoosing a generic report or account closure without first classifying the issue

The Core CGSS Decision Model

Most sanctions scenarios reduce to a practical chain:

  1. Identify all parties and interests. Customer, beneficial owner, controller, vessel, aircraft, wallet, intermediary, bank, vendor, consignee, end user, and beneficiary.
  2. Identify the restriction type. List-based, ownership/control, sectoral, geographic, goods/end-use, service, financing, facilitation, or evasion concern.
  3. Assess the evidence. Names, aliases, identifiers, ownership documents, trade documents, payment messages, shipment route, goods description, and customer history.
  4. Choose the control response. Clear, continue review, escalate, block, reject, restrict, report, or decline depending on facts and law/policy.
  5. Document the rationale. The file should show the facts reviewed, decision-maker, date, conclusion, and follow-up.
    flowchart TD
	    A[Customer, payment, trade, vendor, or counterparty activity] --> B[Identify parties, owners, controllers, goods, route, and purpose]
	    B --> C[Screen lists and review sanctions risk indicators]
	    C --> D{Possible match, prohibited exposure, or evasion signal?}
	    D -- No --> E[Document rationale and proceed under policy]
	    D -- Yes --> F[Pause or hold action under policy]
	    F --> G[Gather identifiers, ownership, trade, payment, and context evidence]
	    G --> H{Facts resolve the issue?}
	    H -- False positive --> I[Document clearance and monitor if needed]
	    H -- Possible or true issue --> J[Escalate to sanctions/legal/compliance]
	    J --> K{Required action?}
	    K -- Block/reject/report/restrict --> L[Execute required action and preserve records]
	    K -- More review --> M[Request documentation and continue investigation]

Exam point: The best answer is usually the next defensible control step. Avoid answers that ignore evidence, skip escalation, or treat every concern as either harmless or automatically criminal.

Sanctions Frameworks and Governance: Fast Distinctions

Sanctions questions often test whether you can separate the legal restriction from the operational control.

Types of Sanctions Exposure

Exposure typeWhat to identifyCommon exam angle
List-based sanctionsWhether a person, entity, vessel, aircraft, wallet, or beneficial owner appears on a sanctions listMatch quality, identifiers, aliases, and false-positive documentation
Ownership/controlWhether a listed party owns, controls, directs, or benefits from a non-listed partyDirect customer looks clean, but ownership or benefit is unresolved
Sectoral restrictionsWhether activity involves restricted sectors, debt/equity, services, technology, or financingParty is not blocked, but the activity may still be restricted
Country or region measuresWhether geography, origin, destination, routing, or beneficiary creates exposureShipment or payment touches a restricted location
Trade and export controlsWhether goods, software, technology, end use, or end user create restrictionsDual-use goods, military end user, altered documents, or suspicious routing
Facilitation riskWhether the firm or employee helps another party do what the firm cannot do directlyAdvice, routing changes, payment rewriting, or indirect support
Evasion riskWhether facts suggest a person is trying to avoid sanctions controlsFront companies, new intermediaries, vague goods, or sudden ownership changes

Governance Roles

ParticipantCore responsibilityExam trap
Board or senior managementSet risk appetite, support resources, oversee program effectivenessAssuming senior leaders do daily alert disposition
First line businessOwn sanctions risk in customers, products, payments, trade, and vendorsTreating compliance as the only risk owner
Sanctions compliance functionSet standards, advise, review escalations, monitor controls, support decisionsTreating policy writing as the whole program
LegalInterpret legal obligations and advise on complex restrictions or reportingAsking frontline staff to resolve legal ambiguity alone
OperationsApply screening, holds, payment processing, and documentation proceduresReleasing a transaction before review is complete
Internal audit or independent testingTest design and operating effectivenessLetting the same team test its own work without independence

Exam point: CGSS practice is rarely about memorizing one list. It is usually about applying sanctions risk logic to a messy customer, payment, trade, or ownership fact pattern.

Building a Sanctions Compliance Program

A sanctions compliance program should be risk-based, documented, tested, and connected to actual business activity.

Program Elements

Program elementWhat strong practice should make you decideWeak answer pattern
Risk assessmentWhich customers, products, geographies, intermediaries, goods, and transaction types need stronger controls?Same screening depth for every business line
Policies and proceduresWhat must staff do when screening produces a possible match, true match, or evasion red flag?Policy says “screen” but does not define escalation or holds
Screening controlsWhich data fields, lists, thresholds, timing points, and rescreening events matter?One-time onboarding screening only
Alert handlingIs the alert a false positive, possible match, true match, or prohibited activity?Clearing by name similarity alone
Trade and payment reviewDo goods, route, parties, ownership, payment messages, or documents create sanctions risk?Treating trade documents as automatically reliable
TrainingWhich employees need role-based sanctions training based on exposure?Generic annual training with no operational relevance
Independent testingAre controls designed well, operating as intended, and remediated after failures?No test of alert quality, overrides, or backlog aging
Management informationAre risk, alert, backlog, escalation, and issue trends visible to governance?Senior management sees only volume, not control quality
DocumentationCan the firm explain why it cleared, escalated, blocked, rejected, or continued review?Decision field says “OK” with no rationale

Trap: A policy that exists on paper is not enough. The question often asks whether the control is actually applied, documented, monitored, and escalated.

Risk Assessment Review

Risk factorHigher-risk indicatorsStrong control response
CustomerShell companies, nominees, PEPs, state-owned entities, complex ownership, money services businesses, high-risk trade customersEnhanced ownership review, source of funds/purpose checks, closer monitoring
GeographySanctioned jurisdictions, border regions, weak controls, transshipment hubs, conflict zonesCountry risk scoring, routing review, restrictions, escalation
Product/serviceTrade finance, correspondent banking, virtual assets, shipping, insurance, securities, commodity financeProduct-specific screening and document review
TransactionVague payment messages, round-dollar wires, third-party payments, unusual route, altered instructionsPayment hold, context review, escalation
Vendor/third partyAgents, brokers, freight forwarders, distributors, resellers, consultantsThird-party due diligence and sanctions clauses
Data qualityMissing date of birth, incomplete addresses, poor transliteration, stale ownership dataData remediation, manual review, rescreening

Control Quality Questions

Before you choose an answer, ask:

  • Is the control preventive, detective, or corrective?
  • Does the control happen before the firm creates prohibited exposure?
  • Does the reviewer have enough information to clear the issue?
  • Is a legal or sanctions specialist needed?
  • Is the decision documented well enough for a later examiner?
  • Does the program learn from failures, backlogs, overrides, and false positives?

Screening and Alert Handling

Screening is a decision workflow, not a button press.

Screening Lifecycle

StepPractical questionEvidence to review
Collect usable dataAre names, aliases, dates, addresses, ownership, vessels, goods, and identifiers complete enough?Customer files, KYC, trade docs, payment fields, vendor records
Normalize and screenAre aliases, transliteration, abbreviations, spelling variants, and local naming conventions handled?Screening configuration, fuzzy logic, list sources, data quality
Compare identifiersDo identifiers support a true match, false positive, or unresolved possible match?DOB, incorporation date, address, passport, national ID, registration number
Check ownership/controlIs a non-listed customer owned or controlled by a sanctioned party?Ownership chart, registries, corporate documents, voting/control rights
Review transaction contextDo routing, goods, jurisdictions, counterparties, or payment purpose change the risk?SWIFT/payment message, invoice, bill of lading, contract, end-user certificate
DispositionIs the right action clear, or does it require escalation?Policy, legal guidance, sanctions procedure, escalation notes
Document and monitorWould another reviewer understand the decision from the record?Rationale, evidence, approver, date, follow-up actions

Trap: A false-positive process is not a shortcut. Weak documentation can make even a reasonable decision look indefensible.

Alert Disposition Table

Alert outcomeWhat it meansBetter response
Clear false positiveIdentifiers show the party is not the sanctioned partyDocument facts and rationale; proceed under policy
Possible matchEvidence is incomplete or conflictingHold or pause action as policy requires, gather facts, escalate
True matchParty, owner, vessel, or relevant interest matches a sanctions targetFollow blocking, rejection, reporting, and escalation requirements
Ownership/control concernDirect party is not listed but listed party may own/control/benefitEscalate and review ownership/control before proceeding
Sectoral or activity restrictionParty is not blocked but activity may be restrictedLegal/sanctions review; assess restrictions and permitted activity
Evasion red flagFacts suggest avoidance of sanctions controlsEscalate, investigate, document, and consider reporting/restriction
Data-quality failureScreening cannot be reliable because inputs are weakRemediate data before clearing; do not treat “no hit” as proof

AML Monitoring vs. Sanctions Screening

TopicAML suspicious activity monitoringSanctions screening
Main questionIs activity suspicious or inconsistent with profile?Is there a prohibited, restricted, or sanctioned party/activity?
TimingOften ongoing and post-activity, depending on productOften before onboarding, before transactions, and when lists/data change
EvidenceCustomer profile, behavior, typologies, source of fundsList match, ownership/control, goods, route, identifiers, restrictions
OutputInvestigate, escalate, report if suspicion threshold is metClear, hold, escalate, block, reject, report, or restrict
Common trapFiling solely because an alert firedClearing solely because the direct customer is not listed

Ownership, Control, and Indirect Exposure

CGSS scenarios often turn on what the candidate does after the direct party looks clean.

High-Yield Ownership and Control Cues

  • A listed person owns or controls part of the customer, vendor, vessel, trust, or intermediary.
  • The direct party is new, thinly capitalized, or recently changed ownership.
  • A payment or shipment benefits a sanctioned party even if that party is not named as the customer.
  • A corporate structure has nominees, layered entities, or unexplained offshore ownership.
  • A customer changes routing, counterparty, documents, or goods descriptions after a sanctions concern appears.

Exam point: Do not assume a clean first-level name screen ends the analysis when beneficial ownership, control, or benefit is unresolved.

Ownership/Control Review Table

Fact patternWhy it mattersBetter exam response
Listed person owns a minority interest but has veto rightsControl may exist without majority ownershipEscalate for ownership/control analysis
Customer is owned by several companies in different jurisdictionsLayering may obscure a sanctioned beneficial ownerBuild ownership chart and verify controllers
Trust has sanctioned settlor or protector influenceControl or benefit may not sit with legal ownerReview trust roles and escalation requirements
New intermediary appears after a sanctions concernCould be an attempt to reroute through a frontTreat as evasion signal and investigate
Payment benefits a listed party indirectlySanctions exposure can arise through benefit, not just named partyEscalate before processing
Ownership documents are stale or inconsistentScreening result may be unreliableRefresh information and document rationale

Direct, Indirect, and Beneficial Exposure

ExposurePractical question
Direct partyIs the customer, vendor, bank, vessel, or counterparty listed or restricted?
Beneficial ownerDoes a listed person ultimately own or benefit from the party?
ControllerDoes a listed person direct decisions through voting, management, contract, or influence?
IntermediaryIs a broker, agent, freight forwarder, distributor, or bank creating sanctions exposure?
Goods/end userAre the goods, technology, destination, or end user restricted?
Payment pathDoes the payment route, bank, message, or beneficiary indicate prohibited exposure?

Detecting and Investigating Evasion

Sanctions evasion questions reward careful fact gathering before final disposition.

Red flagReview focus
Transshipment through unusual routesCompare goods, ports, counterparties, and economic rationale.
Dual-use or restricted goodsReview end user, end use, licensing, documentation, and routing.
Altered or inconsistent documentsCompare invoices, bills of lading, certificates, contracts, and payment instructions.
Front or shell companiesReview ownership, business purpose, transaction history, and adverse media.
Sudden counterparty changesAsk why the customer changed the party, routing, vessel, or payment path.
Payments just below thresholdsReview whether structuring or control avoidance is plausible.
Clean customer but sanctioned beneficiaryReview indirect benefit, ownership/control, and facilitation risk.
Vague payment referencesCompare payment message to contract, invoice, goods, and counterparties.
Use of new agents or brokersReview commercial rationale, due diligence, and sanctions exposure.

Trap: The best answer is often not immediate closure or immediate clearance. It may be escalation, additional documentation, enhanced review, blocking, rejection, or reporting depending on the facts and local requirements.

Trade and Payment Evasion Patterns

PatternHow it appears in a questionWhat to do first
TransshipmentShipment routes through a third country with no commercial reasonCompare route, goods, end user, and documents
MisdescriptionGoods are described generically or inconsistentlyRequest detail, review end use, and escalate if unresolved
Dual-use goodsItem can have civilian and military/restricted useReview end user, end use, licensing, and sanctions/export controls
Third-party paymentUnrelated party pays or receives fundsEstablish relationship and commercial rationale
Document alterationInvoice, bill of lading, or certificate conflicts with other recordsDo not rely on one document; compare all evidence
Shipping switchVessel, carrier, consignee, or port changes after review beginsTreat as a potential evasion indicator
Message strippingPayment references remove obvious sanctioned informationEscalate because concealment may indicate facilitation/evasion

Investigation Workflow

StepWhat good looks like
Define the issueIs the concern a list match, ownership/control concern, restricted activity, or evasion signal?
Preserve the activityHold, pause, or restrict action according to policy while review is pending.
Gather factsParties, owners, controllers, goods, end user, route, purpose, documents, payment path, and history.
Compare evidenceCheck whether documents, messages, routes, and parties tell the same story.
Seek explanation carefullyUse approved procedures and avoid tipping off or helping evade controls.
EscalateBring unresolved or high-risk matters to sanctions/legal/compliance specialists.
DecideClear, block, reject, report, restrict, decline, or continue review based on facts and law/policy.
DocumentRecord facts, rationale, decision-maker, date, and follow-up actions.

Quality Documentation

Good sanctions documentation answers:

  • What triggered the alert or investigation?
  • Which parties, owners, controllers, goods, jurisdictions, and payment paths were reviewed?
  • Which sanctions lists, restrictions, or policies were relevant?
  • Which identifiers or documents supported the decision?
  • Why was the issue cleared, escalated, blocked, rejected, or kept under review?
  • Who made or approved the decision?
  • What follow-up monitoring, remediation, or reporting is required?

Trap: “No sanctions issue found” is not enough if the file does not show why the match, ownership concern, route, or evasion signal was resolved.

Proliferation Financing and Dual-Use Goods

CGSS questions may blend sanctions, export controls, and proliferation financing. The key is to look beyond the customer name and test whether the transaction supports restricted procurement or restricted end users.

Common Proliferation-Financing Indicators

IndicatorWhy it matters
Dual-use goods, software, or technologyCivilian items may support military, nuclear, missile, or restricted programs
Unusual procurement chainMultiple brokers or front companies may hide the true end user
Inconsistent end-user certificateDocumentation may be altered or incomplete
Shipment through transshipment hubsRoute may be designed to conceal destination
Customer lacks technical capacityThe buyer does not appear able to use the goods legitimately
Payment from unrelated third partyMay hide sponsor, beneficial owner, or restricted beneficiary
Goods inconsistent with business modelProduct does not fit customer profile or prior activity

What to Review

  • End user and end use.
  • Goods description and technical specifications.
  • Licensing or authorization requirements where relevant.
  • Shipping route, ports, freight forwarders, and vessel history.
  • Counterparties, brokers, distributors, and payment parties.
  • Public adverse information and sanctions proximity.

Virtual Assets, Securities, and Nonbank Exposure

Sanctions risk is not limited to bank wires. CGSS candidates should be ready for scenarios involving virtual assets, securities, insurance, fintech platforms, trade finance, charities, and third-party service providers.

ChannelSanctions risk angleControl focus
Virtual assetsWallet exposure, mixers, sanctioned wallets, ransomware, chain hoppingBlockchain analytics, wallet screening, VASP due diligence
SecuritiesIssuer, investor, broker, custodian, beneficial owner, market restrictionCustomer and issuer screening, ownership/control review
InsurancePolicyholder, beneficiary, insured asset, vessel, cargo, claims paymentParty, asset, and claims screening
Trade financeGoods, route, vessel, end user, invoice, financing bankDocument comparison and goods/end-use review
Charities and nonprofitsDiversion to sanctioned regions or entitiesPurpose, beneficiaries, partners, geography, monitoring
Third-party agentsDistributor, consultant, broker, freight forwarder, resellerThird-party due diligence and contract controls

Quick Decision Map

If the scenario shows…Better first response
Weak fuzzy-name match with inconsistent identifiersDocument false-positive rationale if policy supports clearance.
Possible true match with unresolved identifiersEscalate and pause action pending specialist review.
Listed party or sanctioned ownership/controlFollow blocking, rejection, reporting, and escalation requirements.
Clean party name but high-risk trade route or goodsReview end use, documents, counterparties, and evasion indicators.
Customer asks how to avoid screening or change routing after a hitTreat as an evasion red flag and escalate.
Program audit finds alert backlogs and undocumented clearancesRemediate control failure, document decisions, and strengthen oversight/testing.
Frontline staff want to release funds while review is pendingHold or restrict action under policy until sanctions review is complete.
Senior manager wants to override an alert for a valuable customerFollow escalation, legal review, and governance controls; do not clear without rationale.
Data is too incomplete to screen reliablyObtain or remediate data before relying on the result.
High false-positive volume creates backlogTune rules carefully, improve data quality, and monitor control effectiveness.

Common CGSS Candidate Mistakes

MistakeBetter approach
Treating sanctions as only name matchingReview ownership/control, sectoral restrictions, geography, goods, services, and evasion signals
Clearing a match because one identifier differsCompare all relevant identifiers and document the conclusion
Ignoring indirect benefitAsk who owns, controls, receives, benefits, or directs the activity
Choosing account closure too quicklyFirst classify the issue, escalate, and follow legal/policy requirements
Assuming software makes the decisionScreening tools create alerts; people and policy disposition them
Treating every red flag as proofRed flags require investigation, evidence, and escalation where needed
Forgetting data qualityBad data can make screening ineffective
Overlooking trade documentsSanctions risk often appears in goods, route, vessel, consignee, or end user facts
Missing facilitation riskAdvising a customer how to route around controls can create exposure
Writing weak notesA defensible decision needs facts, reasoning, approver, and follow-up

“Best Next Step” Exam Strategy

When two answers seem plausible, choose the one that best reflects:

  1. Legal and policy compliance.
  2. Risk-based evidence gathering.
  3. Proper escalation.
  4. Holds or restrictions where required.
  5. Clear documentation.
  6. No facilitation or tipping-off behavior.

Words That Often Signal a Wrong Answer

Be cautious when an answer says:

  • “Ignore” a hit because the customer is profitable.
  • “Process first and review later.”
  • “Tell the customer how to avoid the restriction.”
  • “Clear because only the direct customer is screened.”
  • “No need to document.”
  • “Use a different bank to complete the payment.”
  • “Delete the sanctioned country reference.”
  • “Assume the intermediary checked everything.”
  • “Close the alert because the name is common” without identifiers.
  • “Skip legal/compliance because timing is urgent.”

Words That Often Signal a Better Answer

Look for actions such as:

  • Verify identifiers.
  • Review ownership and control.
  • Hold or pause under policy.
  • Gather trade/payment documents.
  • Escalate to sanctions, legal, or compliance.
  • Block, reject, report, or restrict where required.
  • Remediate data or control weakness.
  • Document rationale.
  • Continue monitoring.
  • Refuse facilitation.

Rapid Final Review Checklist

Before CGSS practice questions, make sure you can explain:

  • Why sanctions exposure can exist even when the direct customer is not listed.
  • The difference between list-based, sectoral, geographic, trade, and ownership/control restrictions.
  • Why governance requires oversight, risk assessment, policies, training, testing, and remediation.
  • What makes a screening alert a false positive, possible match, or true match.
  • Which identifiers matter when reviewing a name match.
  • Why ownership, control, indirect benefit, and facilitation matter.
  • How trade documents can reveal transshipment, dual-use goods, or restricted end users.
  • Why a payment message change can be an evasion signal.
  • How sanctions screening differs from AML suspicious activity monitoring.
  • When to escalate to sanctions/legal/compliance specialists.
  • Why independent testing should evaluate control quality, not just alert volume.
  • What a defensible clearance note should include.

Rapid Review: If You Have 30 Minutes

10-Minute Framework Review

Focus on:

  • List-based sanctions are only one part of the analysis.
  • Country, sector, goods, service, ownership, and benefit restrictions can matter.
  • Governance sets accountability; operations apply controls; compliance/legal review ambiguity.
  • Risk assessment drives screening, due diligence, escalation, and monitoring strength.

10-Minute Scenario Review

Practice spotting:

  • Possible true matches.
  • Beneficial ownership issues.
  • Front or shell companies.
  • Transshipment and unusual routing.
  • Dual-use goods and restricted end users.
  • Vague or altered trade documents.
  • Payment-message stripping.
  • High-risk intermediaries.
  • Backlogs, overrides, and weak documentation.

10-Minute Question-Bank Review

Use original practice questions to test:

  • “What should the analyst do next?”
  • “Which fact is most important?”
  • “Which control failed?”
  • “Which issue requires escalation?”
  • “Which evidence best resolves the alert?”
  • “Which response avoids facilitation?”

Review the detailed explanations for both correct and incorrect options. The tempting wrong answers often reveal the exam’s favorite traps: fast clearance, missing ownership/control, weak documentation, and failure to escalate.

Practice Next

After this review, use CGSS topic drills to test whether you can apply sanctions rules under time pressure. Finance Prep’s CGSS bank has 756 original practice questions with topic drills, timed mock exams, and detailed explanations.

Need to sharpen…Use
Sanctions regimes, governance, risk appetite, and oversightSanctions Frameworks and Governance
Program design, screening controls, procedures, training, and testingBuilding a Sanctions Compliance Program
Alert review, investigations, ownership/control, and evasion typologiesDetecting and Investigating Sanctions Evasion Techniques
Mixed exam-style practiceFree CGSS Practice Exam

For each missed practice question, write down:

  • The sanctions issue tested.
  • The fact that should have changed your answer.
  • The control or escalation rule you missed.
  • Why the correct answer is more defensible than the tempting answer.

Your next step: practice scenario-based questions until you can consistently identify the sanctions exposure, the evidence needed, the right escalation or disposition, and the documentation that makes the decision defensible.