CGSS — ACAMS Certified Global Sanctions Specialist Exam Blueprint
Independent CGSS exam blueprint for ACAMS Certified Global Sanctions Specialist candidates reviewing sanctions frameworks, screening, investigations, evasion, and compliance controls.
How to Use This Exam Blueprint
Use this independent Exam Blueprint as a practical readiness map for the ACAMS Certified Global Sanctions Specialist (CGSS) exam from ACAMS. It does not assign official weights or claim to reproduce the exam. Instead, it helps you check whether you can apply sanctions concepts to realistic compliance decisions.
Work through the checklist in three passes:
- Concept pass: Can you define the vocabulary and explain the purpose of each control?
- Scenario pass: Can you decide what to do when facts are incomplete, cross-border, or conflicting?
- Documentation pass: Can you support your decision with clear rationale, escalation, and evidence?
Exam identity
| Item | Details |
|---|---|
| Official provider | ACAMS |
| Official exam title | ACAMS Certified Global Sanctions Specialist (CGSS) |
| Official exam code | CGSS |
| Page purpose | Independent exam blueprint and final-review blueprint |
| Readiness target | Apply global sanctions concepts to customer, transaction, ownership, screening, investigation, and compliance-program scenarios |
Core topic-area readiness table
| Readiness area | What to review | Ready when you can… | Quick self-check |
|---|---|---|---|
| Sanctions purpose and policy goals | Why sanctions are imposed; foreign policy, national security, human rights, terrorism, proliferation, corruption, cyber, conflict, and other policy objectives | Explain the difference between a sanctions objective and an AML objective | “Is this risk about illicit finance generally, or about a prohibited/restricted party, place, sector, good, or activity?” |
| Sanctions authorities and regimes | Global, supranational, national, and regional sanctions sources; how institutions identify applicable regimes | Describe why one transaction may trigger multiple regimes | “Which jurisdictions, currencies, parties, branches, and touchpoints matter?” |
| Types of sanctions | List-based, territorial, sectoral, activity-based, trade, arms, travel, asset-freeze/blocking-style, investment, securities, and services restrictions | Classify a scenario by restriction type before deciding what to do | “Is the issue who, where, what, sector, ownership, service, or transaction type?” |
| Sanctions lists and identifiers | Names, aliases, dates of birth, addresses, nationalities, government IDs, vessels, aircraft, entities, crypto addresses, and other identifiers | Compare potential matches using more than name similarity | “What identifiers confirm, weaken, or leave unresolved the match?” |
| Ownership and control | Direct ownership, indirect ownership, aggregation, control rights, beneficial ownership, nominee structures, and management influence | Identify when a non-listed entity may still require sanctions review | “Who ultimately owns, controls, benefits, or directs the entity?” |
| Customer and counterparty due diligence | Customer profile, beneficial owners, controllers, counterparties, geography, expected activity, products, services, and risk changes | Identify missing facts that must be obtained before disposition | “What do I need to know before clearing or escalating?” |
| Payment and transaction screening | Originator, beneficiary, banks, intermediaries, remittance text, addresses, vessel or shipment data, and reference fields | Explain why transaction screening is not the same as onboarding screening | “Which transaction fields create sanctions exposure?” |
| Trade finance and maritime risk | Bills of lading, invoices, ports, vessels, flag states, cargo, end use, end users, insurers, shippers, freight forwarders, and transshipment | Spot sanctions red flags in trade documents | “Do the documents tell a consistent story?” |
| Sectoral and activity restrictions | Sector-based limits, securities or financing restrictions, energy, defense, technology, dual-use goods, and services restrictions where applicable | Avoid assuming that absence from a list means no sanctions risk | “Could the activity itself be restricted?” |
| Screening systems and alert logic | Exact matching, fuzzy matching, transliteration, aliases, threshold tuning, batch screening, real-time interdiction, and list updates | Explain false positives, potential matches, true matches, and unresolved alerts | “Why did the system generate this alert, and what evidence supports the disposition?” |
| Investigations and escalation | Alert triage, evidence gathering, legal/compliance escalation, disposition, hold/release decisions, and documentation | Write a defensible case note for a sanctions alert | “Would another reviewer understand my decision from the file?” |
| Licensing, exemptions, and exceptions | General authorizations, specific permissions, humanitarian considerations, wind-down-style concepts, and regime-specific conditions | Treat authorizations as conditional, not blanket permission | “What facts must be true for the authorization to apply?” |
| Reporting and recordkeeping | Internal escalation, regulator-facing reporting where applicable, audit trail, evidence retention, and management information | Identify when a matter may require more than routine alert closure | “Who must know, and what must be documented?” |
| Evasion and circumvention | Front companies, nominees, payment stripping, unusual routing, transshipment, ownership changes, maritime deception, and virtual asset typologies | Distinguish weak coincidence from meaningful red flag pattern | “What behavior suggests concealment or avoidance?” |
| Compliance program design | Governance, risk assessment, policies, controls, screening, training, testing, audit, remediation, and third-party oversight | Map a weakness to the control that should prevent or detect it | “Is this a policy gap, data gap, system gap, training gap, or governance gap?” |
| Ethics and professional judgment | Independence, escalation discipline, documentation quality, conflicts, pressure to process, and risk-based decisions | Choose a cautious, well-supported response when facts are incomplete | “Am I clearing because the evidence supports it, or because processing is urgent?” |
Sanctions framework and vocabulary checks
Can you explain these core concepts?
- The difference between sanctions, AML, counter-terrorist financing, anti-bribery/corruption, and export control objectives.
- Why sanctions compliance is often jurisdiction-specific and may depend on location, currency, nationality, incorporation, branch, ownership, or transaction touchpoints.
- The difference between a listed person/entity and a restricted activity.
- The difference between direct sanctions exposure and broader reputational, correspondent, or secondary-risk exposure.
- Why sanctions restrictions may apply to customers, beneficial owners, counterparties, vessels, goods, services, locations, securities, technology, and transactions.
- Why a sanctions program cannot rely only on annual customer reviews.
- Why “not on a list” is not the same as “not restricted.”
- Why “humanitarian” or “charitable” purpose may still require controls, documentation, and authorization analysis.
Sanctions source documents to recognize
| Source or artifact | What it tells you | Readiness prompt |
|---|---|---|
| Sanctions law, regulation, order, or measure | The legal basis and scope of restrictions | Can you identify who and what is restricted without overgeneralizing? |
| Sanctions list entry | Names, aliases, identifiers, program tags, and other reference data | Can you compare the list entry to the customer or transaction facts? |
| Guidance, FAQ, advisory, or interpretive note | How an authority explains application, risk, or compliance expectations | Can you use guidance without treating it as universal across regimes? |
| General authorization, exemption, or license-type document | Conditions under which otherwise restricted activity may be allowed | Can you identify the exact conditions that must be satisfied? |
| Specific permission or license | Approval tied to defined facts, parties, timing, or activity | Can you explain why it may not cover a different transaction? |
| Enforcement action or penalty notice | Examples of control failures, evasion, or governance weaknesses | Can you extract the compliance lesson without memorizing only facts? |
| Internal policy or procedure | Institution-specific operating rules | Can you distinguish internal risk appetite from legal requirements? |
| Screening alert record | System-generated potential match or rule hit | Can you document the disposition and evidence trail? |
Sanctions regime and restriction types
| Restriction type | What to know | Scenario cue |
|---|---|---|
| List-based sanctions | A person, entity, vessel, aircraft, wallet, or other identifier appears on a sanctions list | Name match, alias match, ID match, vessel match, wallet match |
| Territorial or geographic sanctions | Restrictions relate to a country, region, territory, or location | Address, port, origin, destination, IP, shipping route, place of incorporation |
| Sectoral sanctions | Restrictions target specific sectors, industries, financing, securities, services, or activity types | Energy, defense, finance, technology, mining, capital markets, or restricted services fact pattern |
| Activity-based sanctions | The prohibited conduct matters even if the party is not listed | Facilitation, circumvention, export, import, investment, brokering, financing, or services |
| Trade and goods restrictions | Goods, technology, end use, end user, or shipment route may be restricted | Invoice, commodity description, dual-use concern, transshipment, vague cargo |
| Asset-freeze/blocking-style restrictions | Dealing with property or interests in property may be restricted under applicable rules | Existing customer becomes listed; funds or securities are detected |
| Travel or immigration-related sanctions | Restrictions may affect entry, visas, or movement | Usually less operational for transaction processing but important conceptually |
| Arms embargo or defense restrictions | Military goods, services, training, brokering, or defense-related support may be restricted | Defense goods, security services, military end user |
| Secondary or extraterritorial risk | A party may face consequences for certain dealings even without a direct domestic nexus | Non-domestic transaction involving high-risk sanctioned activity |
Customer, counterparty, and ownership/control readiness
Parties and data points to evaluate
| Party or data element | Why it matters | Can you review it? |
|---|---|---|
| Customer or account holder | Primary onboarding and ongoing screening subject | Can you compare legal name, trade name, alias, address, IDs, and activity? |
| Beneficial owner | Listed or sanctioned ownership may affect an otherwise non-listed entity | Can you trace ownership through layers? |
| Controller or senior manager | Control can create sanctions concern even without majority economics | Can you identify veto rights, board control, signatory authority, or management direction? |
| Authorized signer or power of attorney | A listed person may operate through another account | Can you identify who can move value? |
| Counterparty | Sanctions exposure may arise from the other side of the transaction | Can you screen and assess counterparties, not just customers? |
| Intermediary bank or correspondent | Payment path can create jurisdictional and sanctions touchpoints | Can you analyze all banks in the payment chain? |
| Originator and beneficiary | Payment screening depends on both sides of the transfer | Can you identify incomplete or inconsistent payment fields? |
| Vessel, aircraft, or vehicle | Transportation assets may be listed, renamed, reflagged, or indirectly controlled | Can you validate unique identifiers where available? |
| Goods, technology, or services | The item or service may be restricted even if parties are not listed | Can you identify end use, end user, and route concerns? |
| Geographic touchpoints | Location drives territorial, sectoral, and evasion risk | Can you evaluate address, origin, destination, port, IP, branch, and routing facts? |
Ownership and control calculation checks
The CGSS exam is not best approached as a pure calculation exam, but sanctions scenarios often require basic ownership logic. Be ready to calculate simple direct and indirect ownership, then apply the relevant regime, guidance, and internal escalation standard.
\[ \text{Indirect ownership through a chain} = \text{Ownership}_1 \times \text{Ownership}_2 \times \cdots \]Checklist:
- Identify direct ownership versus indirect ownership.
- Trace ownership through each entity in the chain.
- Recognize that aggregation rules may vary by regime or policy.
- Recognize that control may exist through rights, influence, management, veto power, or contractual arrangements.
- Avoid clearing an entity solely because a percentage appears low.
- Escalate when ownership is opaque, recently changed, nominee-based, or inconsistent with the customer profile.
- Document assumptions, data sources, and unresolved ownership gaps.
Ownership/control scenario prompts
| Scenario cue | What to ask |
|---|---|
| A listed person owns a parent company that owns a customer | What is the indirect ownership percentage, and does control also exist? |
| Several sanctioned persons each own minority stakes | Does applicable guidance or internal policy require aggregation? |
| A non-listed relative manages the company | Is this a nominee, front, or legitimate independent manager? |
| Ownership changed shortly before onboarding | Was the change designed to avoid sanctions restrictions? |
| A shareholder has veto rights over major decisions | Could control exist even without majority ownership? |
| Corporate records are unavailable or inconsistent | Is enhanced due diligence or escalation required before processing? |
Screening and alert-handling readiness
Screening data fields to know
| Data field | Screening relevance | Common weakness |
|---|---|---|
| Legal name | Primary match field | Overreliance on exact spelling |
| Alias, former name, trade name | Captures known variations | Missing local-language or transliterated names |
| Date and place of birth | Helps distinguish individuals | Treating partial DOB conflicts as automatic clearance |
| Nationality or citizenship | Supports identification and risk context | Assuming nationality alone proves a match |
| Address and geography | Identifies location and territorial risk | Ignoring branch, port, or shipping address |
| Government ID, passport, tax ID | Strong identifier when available | Failing to compare document numbers carefully |
| Entity registration number | Distinguishes companies with similar names | Not validating current corporate records |
| Beneficial ownership data | Identifies hidden sanctions exposure | Not screening owners and controllers |
| Payment reference text | Detects restricted parties, vessels, goods, or locations | Ignoring free-text fields |
| Vessel name and IMO-style identifier | Helps detect maritime sanctions risk | Screening only vessel names, not unique identifiers |
| Crypto wallet or blockchain indicator | Relevant where virtual assets appear | Treating virtual assets as outside sanctions controls |
| List source and timestamp | Supports audit trail | Not preserving the basis for disposition |
Alert workflow to be comfortable with
flowchart TD
A[Sanctions alert or list update] --> B[Collect customer, counterparty, and transaction facts]
B --> C[Compare identifiers and context]
C --> D{Match resolved?}
D -->|False positive| E[Document rationale and close per procedure]
D -->|True or likely match| F[Hold or restrict activity per procedure]
D -->|Unresolved| G[Escalate and request more information]
F --> H[Assess ownership, control, activity, and jurisdiction]
G --> H
H --> I[Determine reporting, licensing, blocking/freezing, rejection, or other required action where applicable]
I --> J[Record evidence, approvals, and final disposition]
Can you handle screening questions?
- Explain exact matching, fuzzy matching, phonetic matching, and transliteration at a practical level.
- Distinguish a false positive from a potential match and a confirmed match.
- Identify why a name-only match is rarely enough for final disposition.
- Identify why missing identifiers may require escalation, not automatic clearance.
- Explain the risk of both overly loose matching and overly restrictive tuning.
- Describe batch screening, real-time transaction interdiction, and periodic rescreening.
- Explain why list updates can create risk for existing customers, pending transactions, and previously cleared relationships.
- Document a screening decision in a way that a reviewer, auditor, or regulator could follow.
Transaction, trade, maritime, and sectoral scenario checks
| Scenario type | Facts to identify | Decision focus |
|---|---|---|
| Cross-border wire payment | Originator, beneficiary, banks, currency, addresses, purpose, remittance text | Are any parties, locations, banks, or references restricted? |
| Correspondent banking transaction | Respondent bank, nested relationships, underlying customer, payment path | Is the institution exposed to indirect or nested sanctions risk? |
| Trade finance | Applicant, beneficiary, goods, invoice, bill of lading, ports, carrier, insurer, end user | Are goods, parties, route, or end use restricted or suspicious? |
| Maritime shipment | Vessel name, unique vessel identifier, flag, owner, operator, route, AIS behavior, ship-to-ship transfers | Is the vessel or route linked to sanctions evasion? |
| Securities or capital markets activity | Issuer, instrument type, maturity or terms where relevant, sector, exchange, beneficial owner | Is the instrument, issuer, or sector subject to restrictions? |
| Insurance or reinsurance | Insured, beneficiary, vessel, cargo, route, claim, covered activity | Is the institution supporting restricted activity? |
| Real estate or high-value asset purchase | Buyer, seller, beneficial owner, source of funds, nominee, property location | Is value being stored or moved for a sanctioned person? |
| Virtual asset transaction | Wallet, exchange, mixer, blockchain exposure, customer profile, geography | Is there exposure to a listed wallet, sanctioned service, or evasion pattern? |
| Charitable or humanitarian activity | Beneficiary, implementing partner, location, goods/services, authorization basis | Do the conditions for permissible activity actually apply? |
| Professional services | Client, service type, jurisdiction, beneficiaries, project purpose | Is the service itself restricted or facilitative? |
Investigation and disposition checklist
A sanctions investigation should answer: Who is involved, what is happening, where is it connected, which rules may apply, what evidence supports the decision, and who approved the outcome?
Case file contents to recognize
- Alert source, date, system, rule, and list reference where available.
- Customer or transaction snapshot at the time of review.
- Names and identifiers compared.
- Ownership and control analysis.
- Geographic and jurisdictional touchpoints.
- Product, service, goods, vessel, or sector analysis.
- External and internal data sources used.
- Missing facts and how they were resolved or escalated.
- Rationale for false positive, potential match, true match, or unresolved disposition.
- Legal, sanctions advisory, or senior compliance escalation where needed.
- Hold, release, reject, freeze/block, exit, license-review, or other action where applicable.
- Reporting or notification decision where applicable.
- Reviewer approval and audit trail.
- Remediation, tuning, training, or policy update if the case revealed a control weakness.
Disposition traps
| Trap | Why it is weak | Better approach |
|---|---|---|
| “Name is similar but not exact, so clear” | Sanctions lists often contain aliases, transliterations, and incomplete data | Compare all identifiers and context |
| “No list hit, so no sanctions issue” | Activity, sector, geography, or ownership may still be restricted | Analyze the full fact pattern |
| “Customer said it is humanitarian, so process” | Humanitarian activity may be conditional and documentation-dependent | Verify authorization basis and conditions |
| “The payment already processed, so no issue” | Post-transaction detection may still require investigation and escalation | Document timing, cause, and remediation |
| “Ownership is below a threshold, so no concern” | Control, aggregation, or regime-specific rules may still matter | Analyze ownership and control together |
| “A prior alert was cleared, so all future alerts are cleared” | Facts, lists, ownership, and activity can change | Reassess based on current data |
Evasion and circumvention readiness
Red flags to recognize
| Red flag pattern | Why it matters | Scenario cue |
|---|---|---|
| Use of shell or front companies | May obscure sanctioned ownership or control | Newly formed company with vague business purpose |
| Nominee directors or shareholders | May hide the true beneficiary | Directors with no clear commercial role |
| Recent ownership transfer | May be designed to avoid restrictions | Transfer shortly before sanctions, onboarding, or shipment |
| Payment stripping or altered information | Conceals sanctioned party, location, or purpose | Missing originator details or changed remittance text |
| Unusual intermediaries | May route around controls | Third-country broker with no economic rationale |
| Transshipment through nearby jurisdictions | May conceal origin or destination | Goods route through a neighboring or free-trade hub |
| Inconsistent trade documents | May indicate false end user, cargo, or route | Invoice, bill of lading, and packing list do not align |
| Maritime deception | May hide vessel identity or route | Name changes, flag changes, AIS gaps, ship-to-ship transfers |
| Use of family members or associates | May enable indirect access to funds or services | Relative controls account activity for a restricted person |
| Virtual asset obfuscation | May conceal value movement | Mixer, chain-hopping, high-risk exchange, or listed wallet exposure |
| Sudden business model shift | May indicate sanctions avoidance | Customer begins trading restricted-sector goods unexpectedly |
| Pressure for urgency or secrecy | May discourage proper review | “Process today; details will follow later” |
Can you apply red flags?
- Explain why a red flag is not proof, but does require inquiry.
- Combine multiple weak indicators into a stronger risk narrative.
- Identify when a pattern suggests sanctions evasion rather than ordinary operational complexity.
- Decide what information to request before processing.
- Escalate when a customer refuses to provide basic ownership, shipment, or counterparty information.
- Link evasion findings to control improvements, not just case closure.
Sanctions compliance program checklist
| Program component | Ready when you can explain… | Evidence or artifact |
|---|---|---|
| Governance and accountability | Who owns sanctions risk and how decisions are escalated | Board or committee reporting, roles and responsibilities |
| Sanctions risk assessment | How products, customers, geography, transactions, channels, and third parties create risk | Risk methodology, inherent risk, controls, residual risk |
| Policies and procedures | How staff identify, escalate, document, and resolve sanctions issues | Written standards, workflows, approval matrices |
| Customer due diligence | How onboarding and ongoing review capture sanctions-relevant facts | KYC files, beneficial ownership records, risk ratings |
| Screening controls | Who and what is screened, when, against which sources, and with what logic | Screening configuration, list management, test results |
| Transaction monitoring/interdiction | How payments, trade, and activity are reviewed before or after processing | Alert queues, interdiction rules, payment holds |
| Investigation procedures | How alerts are triaged, documented, escalated, and dispositioned | Case notes, evidence attachments, reviewer signoff |
| Licensing and authorization review | How exceptions, exemptions, and permissions are validated | Legal analysis, authorization conditions, approval records |
| Reporting and recordkeeping | How reportable matters are identified and preserved | Internal logs, regulator-facing records where applicable |
| Training and awareness | How staff learn relevant risks for their roles | Training materials, attendance, scenario exercises |
| Independent testing and audit | How control design and operating effectiveness are assessed | Testing plans, findings, remediation tracking |
| Data quality management | How names, addresses, ownership, and transaction fields remain usable | Data standards, exception reports, remediation actions |
| Third-party oversight | How vendors, agents, brokers, correspondents, and processors are controlled | Due diligence files, contracts, monitoring |
| Issue management | How failures are corrected and prevented from recurring | Root-cause analysis, action plans, validation evidence |
| Management information | How leaders see sanctions risk and control performance | Metrics, KRIs, trend reports, escalations |
Scenario decision-point matrix
| If the scenario says… | First question to ask | Avoid this mistake | Likely readiness action |
|---|---|---|---|
| Customer name resembles a listed person | Which identifiers match and which do not? | Clearing on spelling difference alone | Compare DOB, address, IDs, nationality, aliases, and context |
| Beneficial owner is linked to a listed party | Is there direct or indirect ownership or control? | Screening only the legal entity | Trace ownership and escalate unclear control facts |
| Payment references a sanctioned location | Is the location origin, destination, beneficiary address, port, or narrative text? | Ignoring free-text payment fields | Hold or escalate until location role is understood |
| Trade route includes a high-risk transshipment point | Is there a legitimate commercial reason? | Treating route complexity as normal without evidence | Review documents, counterparties, vessel, cargo, and end user |
| Customer claims activity is authorized | Which authorization applies and what conditions must be met? | Treating authorization as blanket approval | Verify facts, conditions, scope, and documentation |
| Existing customer appears on a new list update | What accounts, assets, pending transactions, and related parties are affected? | Focusing only on new onboarding | Review exposure, restrict activity if required, escalate |
| A securities transaction involves a restricted sector | Is the issuer, instrument, maturity/terms, or service restricted under applicable rules? | Looking only for name-list hits | Analyze sectoral and activity restrictions |
| A vessel was recently renamed | Is the unique vessel identifier, owner, operator, or route linked to sanctions risk? | Screening only the new name | Review vessel history and identifiers |
| A customer refuses ownership information | Is there a legitimate reason, or is this concealment? | Processing because no match exists | Escalate due diligence gap |
| Internal staff are pressured to process urgently | Are sanctions checks complete? | Letting business urgency override controls | Follow hold/escalation procedure and document pressure if relevant |
Common weak areas and exam traps
| Weak area | What candidates often miss | How to fix it |
|---|---|---|
| Treating sanctions as only list screening | Sanctions can also be activity-, sector-, territory-, and ownership-based | Classify every scenario by party, place, ownership, sector, and activity |
| Ignoring indirect exposure | Counterparties, intermediaries, vessels, and owners may create risk | Map all relevant parties and touchpoints |
| Overgeneralizing one regime’s rule | Sanctions terms and consequences vary | Use “under the applicable regime” thinking |
| Weak ownership analysis | Candidates stop at the immediate shareholder | Trace through layers and consider control |
| Poor documentation mindset | Correct conclusion may still be unsupported | Practice writing concise case rationales |
| Confusing AML and sanctions red flags | Some overlap exists, but sanctions risk turns on restricted parties, places, goods, sectors, and activity | State the sanctions-specific concern |
| Assuming humanitarian activity is automatically allowed | Conditions, parties, goods, and location still matter | Verify the authorization basis |
| Missing maritime identifiers | Vessel names can change | Look for unique identifiers, owners, operators, flags, and route behavior |
| Ignoring data quality | Bad screening data causes missed hits and excessive false positives | Review data completeness and normalization |
| Clearing unresolved alerts | Lack of evidence is not evidence of no risk | Escalate or obtain more facts |
| Not connecting case failures to controls | Exams may test program remediation logic | Identify whether the root cause is data, policy, system, staffing, or governance |
| Forgetting ongoing monitoring | Sanctions risk changes after onboarding | Include rescreening, list updates, and customer activity changes |
Final-week CGSS review checklist
Use this as a closing readiness test before moving into timed practice.
Sanctions concepts
- I can explain major sanctions objectives without confusing them with general AML objectives.
- I can distinguish list-based, territorial, sectoral, trade, activity, and ownership/control restrictions.
- I can explain why multiple regimes may be relevant to one transaction.
- I can identify when legal or senior sanctions escalation is needed.
Screening and investigations
- I can disposition a name-screening alert using identifiers and context.
- I can explain false positive, potential match, confirmed match, and unresolved alert logic.
- I can document an alert investigation clearly.
- I can identify when list updates affect existing customers or pending transactions.
- I can explain why tuning, data quality, and list management matter.
Ownership and customer due diligence
- I can trace direct and indirect ownership through a simple structure.
- I can explain why control can matter even when ownership is not obvious.
- I can identify missing beneficial ownership or controller information.
- I can recognize nominee, shell-company, and recent-transfer concerns.
Transaction, trade, and sectoral scenarios
- I can identify all parties in a payment chain.
- I can review trade documents for goods, route, vessel, port, end user, and insurer risk.
- I can identify maritime sanctions red flags.
- I can spot when a sector or activity restriction may matter even without a list hit.
- I can evaluate humanitarian or licensed activity cautiously.
Compliance program
- I can describe the components of a sanctions compliance program.
- I can map a failure to a root cause and remediation step.
- I can explain the role of governance, training, testing, audit, and management reporting.
- I can distinguish policy requirements, system controls, analyst judgment, and legal escalation.
- I can identify evidence an auditor or regulator would expect to see in a sanctions file.
Last readiness self-test
For any CGSS-style sanctions scenario, you should be able to answer these questions without guessing:
- Who are the parties, owners, controllers, intermediaries, and beneficiaries?
- Where are the geographic touchpoints?
- What product, service, good, vessel, security, or activity is involved?
- Which restriction type may apply: list, ownership/control, territory, sector, trade, activity, or authorization condition?
- What facts are missing before a decision can be made?
- What should happen next: clear, request information, hold, escalate, restrict, report, seek authorization review, or remediate?
- What documentation would support the decision?
Practical next step
Pick your two weakest rows from the topic-area readiness table. For each one, write three short scenarios and force yourself to identify the parties, restriction type, missing facts, escalation path, and documentation. Then move into mixed CGSS practice questions so you can test judgment under exam-style timing.