Study guide
4.3 Policies, Operating Procedures & Control Standards
CGSS Certified Global Sanctions Specialist Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Introduction to Sanctions & Global Frameworks
1.1 Nature, Purpose, and Types of Sanctions 1.2 Multilateral Regimes & UN Security Council Architecture 1.3 European Union Sanctions Framework & Implementation
2 Chapter 2: Key National Sanctions Regimes & Authorities
2.1 United States Sanctions Regime & OFAC Framework 2.2 UK Post-Brexit Sanctions Architecture & OFSI 2.3 Other Key Global Sanctions Regimes & Regional Authorities
3 Chapter 3: Jurisdictional Reach, Licensing & Enforcement
3.1 Extraterritoriality, Jurisdictional Nexus & Blocking Statutes 3.2 Sanctions Licensing, Authorizations & Exemptions 3.3 Enforcement Powers, Penalties & Legal Consequences
4 Chapter 4: Building a Sanctions Compliance Program
4.1 The Five Essential Components of an SCP 4.2 Governance Architecture & Three Lines of Defense 4.3 Policies, Operating Procedures & Control Standards
5 Chapter 5: Sanctions Due Diligence & Beneficial Ownership
5.1 Customer Due Diligence (CDD) & KYC for Sanctions 5.2 Beneficial Ownership & The 50 Percent Rule 5.3 Enhanced Due Diligence (EDD) for Complex Structures & PEPs
6 Chapter 6: Supply Chain & Third-Party Sanctions Due Diligence
6.1 Third-Party, Intermediary & Supply Chain Due Diligence 6.2 Independent Audit, Testing Methodologies & Staff Training
7 Chapter 7: Sanctions Risk Assessment Fundamentals
7.1 SRA Framework, Methodology & Governance 7.2 Customer & Industry Risk Factor Analysis 7.3 Geographic & Jurisdictional Sanctions Risk
8 Chapter 8: Risk Scoring, Residual Risk & Management Information
8.1 Product, Service & Delivery Channel Vulnerabilities 8.2 Inherent Risk Scoring, Control Effectiveness & Residual Risk 8.3 Management Information (MI), KRIs & Dynamic Reassessment
9 Chapter 9: Sanctions Screening Architecture & Matching Logic
9.1 Screening Systems Architecture & Data Integrity 9.2 Name Matching Logic & Fuzzy Matching Algorithms 9.3 Alert Adjudication Workflow & False Positive Management
10 Chapter 10: Payment & Trade Screening Technologies
10.1 Real-Time Payment Filtering & SWIFT/ISO 20022 10.2 Maritime & Trade Screening Technologies 10.3 System Validation, Calibration & Model Governance
11 Chapter 11: Sanctions Evasion Techniques & Typologies
11.1 Corporate & Ownership Evasion Typologies 11.2 Payment & Financial Channel Evasion 11.3 Trade, Shipping & Maritime Evasion Techniques
12 Chapter 12: Virtual Assets & Investigation Triggers
12.1 Virtual Assets, DeFi & Blockchain Evasion 12.2 Sanctions Investigation Triggers & Case Development
13 Chapter 13: Sanctions Investigations, Asset Control & Reporting
13.1 Asset Blocking, Freezing & Transaction Rejection 13.2 Voluntary Self-Disclosures (VSD), Reporting & Remediation
4.3 Policies, Operating Procedures & Control Standards
Key Takeaways Explain This Topic AI
A Sanctions Policy establishes board-approved principles and risk appetite, while Standard Operating Procedures (SOPs) define granular, day-to-day operational execution steps.
A formal Delegation of Authority (DOA) matrix must clearly delineate who has the legal and operational authority to adjudicate alerts, approve high-risk counterparties, and grant policy exceptions.
Escalation protocols must enforce strict timeframes and multi-tiered adjudication (Level 1 Triage, Level 2 Investigation, Level 3 Senior Sanctions/Legal Officer determination).
Policy exceptions must be strictly limited, time-bound, formally justified with documented legal/compliance sign-offs, and logged in a centralized Exception Register.
Sanctions policies and operating procedures require annual scheduled reviews and immediate out-of-cycle trigger-based reviews following material regulatory or geopolitical changes.
Last updated: August 2026
4.3 Policies, Operating Procedures & Control Standards
A high-performing Sanctions Compliance Program (SCP) translates legal requirements and board risk appetite into actionable, defensible operational standards. In regulatory audits and enforcement inquiries, enforcement agencies like OFAC, OFSI, and EU regulators closely inspect not only whether an institution has a high-level policy, but whether its Standard Operating Procedures (SOPs) provide clear, step-by-step guidance for front-line personnel and compliance analysts.
Policy vs. Operating Procedure: Hierarchy & Structure
Organizations frequently confuse policies with procedures, creating compliance ambiguity:
1. The Enterprise Sanctions Policy
Definition: A high-level, mandatory governance document approved by the Board of Directors that establishes the institution's commitment to compliance, jurisdictional scope, and sanctions risk appetite.
Audience: Enterprise-wide (all employees, business units, subsidiaries, and contractors).
Content: Core principles, definitions of prohibited activities, statutory authorities (OFAC, UN, EU, UK), governance roles (Board, SCO, 3LoD), and consequences of non-compliance.
Approval: Board of Directors or designated Board Risk Committee.
2. Standard Operating Procedures (SOPs)
Definition: Detailed, operational step-by-step manuals that explain how specific tasks must be executed to comply with the overarching Policy.
Audience: Specific operational teams (e.g., wire transfer screening teams, trade finance analysts, onboarding specialists, alert investigators).
Content: Screening system configurations, exact search string rules, fuzzy match thresholds, alert adjudication criteria, escalation pathways, and data retention requirements.
Approval: Sanctions Compliance Officer (SCO) and Operational Business Heads.
Attribute Sanctions Policy Standard Operating Procedures (SOPs)
Focus What we must do and Why (Principles & Governance) How we do it, Who does it, and When (Operational Execution)
Level of Detail Broad, strategic, principles-based Highly granular, procedural, technical
Approval Body Board of Directors / Executive Risk Committee Sanctions Compliance Officer / Compliance Management
Update Cadence Annual scheduled review Dynamic (updated upon system changes or regulatory shifts)
Mandatory Scope Enterprise-wide across all global operations Tailored to specific functional units and workflows
Defining the Sanctions Risk Appetite Statement
The Sanctions Risk Appetite Statement (SRAS) articulates the boundaries of acceptable risk:
Zero-Tolerance Baseline: Most global institutions maintain a zero-tolerance appetite for intentional, knowing, or willful violations of international sanctions laws.
Prohibited Jurisdictions (Hard Exclusions): Complete prohibition on establishing accounts, executing transactions, or financing activities involving comprehensively sanctioned countries (e.g., Cuba, Iran, North Korea, Syria, and occupied regions of Ukraine) absent express compliance approval and specific regulatory licenses.
High-Risk Corridors & Sensitive Sectors: Restricting business in countries neighboring conflict zones, transshipment hubs, free trade zones, defense industries, precious metals, and maritime shipping unless enhanced due diligence (EDD) is completed.
Currency & Nexus Restrictions: Explicit prohibitions on facilitating transactions denominated in U.S. Dollars (USD) or Euros (EUR) that involve secondary sanctions targets or indirect jurisdictional links.
Approval Hierarchies & Delegation of Authority (DOA)
A formal Delegation of Authority (DOA) Matrix establishes legal accountability for sanctions-sensitive decisions, preventing unauthorized or low-level clearance of high-risk matters.
Core Governance Principles of DOA
The Four-Eyes Principle: Any decision to clear a high-risk alert, approve an exception, or onboard a politically exposed person (PEP) from a high-risk jurisdiction requires review and sign-off by at least two authorized individuals .
Prohibition of Self-Approval: Front-line revenue generators cannot clear screening alerts or approve sanctions risk exceptions for their own clients.
Tiered Decision-Making: Escalation thresholds based on risk severity, transaction value, and entity type.
Multi-Tiered Alert Escalation Protocols
When automated filtering systems flag a transaction or customer name against a sanctions list, the alert must flow through a disciplined, time-sensitive escalation protocol: ┌─────────────────────────────────────────────────────────────────────────┐
- │ MULTI-TIERED ALERT ESCALATION PROTOCOL │
- │ │
- │ [ INCOMING TRANSACTION / ONBOARDING RECORD ] │
- │ │ │
- │ ▼ │
- │ ┌──────────────────────────────────────────────────────────────────┐ │
- │ │ LEVEL 1: Operational Triage (SLA: < 2 Hours) │ │
- │ │ • Front Line / Operations Screening Team │ │
- │ │ • Clear obvious false positives (e.g., distinct DOB, nationality) │ │
- │ │ • Document clear rationales using standardized disposition codes │ │
- │ └──────────────────────────────┬───────────────────────────────────┘ │
- │ │ Potential Match / Unclear Match │
- │ ▼ │
- │ ┌──────────────────────────────────────────────────────────────────┐ │
- │ │ LEVEL 2: Compliance Investigation (SLA: < 24 Hours) │ │
- │ │ • Specialized Sanctions Compliance Analysts │ │
- │ │ • Request for Information (RFI), UBO & SWIFT message analysis │ │
- │ │ • Clear false positives or confirm potential true match │ │
- │ └──────────────────────────────┬───────────────────────────────────┘ │
- │ │ True Match / Complex Nexus Identified │
- │ ▼ │
- │ ┌──────────────────────────────────────────────────────────────────┐ │
- │ │ LEVEL 3: Senior Adjudication & Legal Escalation (SLA: Immediate) │ │
- │ │ • Sanctions Compliance Officer (SCO) & Legal Counsel │ │
- │ │ • Final determination: Block, Reject, or License Derogation │ │
- │ │ • File Regulatory Report (OFAC 10-day block / OFSI reporting) │ │
- │ └──────────────────────────────────────────────────────────────────┘ │
- └─────────────────────────────────────────────────────────────────────────┘
- SLA and Escalation Framework
Escalation Tier Responsible Role Core Functions & Duties Standard SLA
Level 1: Triage Operations / Front-Line Screener Screen raw alerts against basic demographic data (DOB, passport, country). Clear obvious false positives. < 2 to 4 Hours
Level 2: Investigation Sanctions Compliance Analyst Conduct in-depth open-source intelligence (OSINT), verify 50% Rule ownership, issue RFIs to correspondent banks. < 24 Hours
Level 3: Senior Adjudication Sanctions Officer / Legal Counsel Authorize transaction blocking, asset freezing, rejection, or external regulatory filings. Immediate / Priority
Restricted Party Lists & Internal Registries
In addition to official government watchlists (OFAC SDN, UN Consolidated, EU Financial Sanctions, UK OFSI), robust compliance programs maintain internal watchlists:
Internal "Do Not Board" / Blacklist: Entities and individuals exited for sanctions concerns, suspected evasion, or adverse media.
Heightened Scrutiny / Gray List: Customers operating in border corridors, dual-use supply chains, or transshipment hubs requiring mandatory enhanced due diligence (EDD) and Level 2 pre-clearance for every transaction.
PEP and Sanctions Associates Registry: High-profile figures, family members, and known corporate associates of sanctioned persons.
Exception Handling, Policy Deviations & Audit Logging
No compliance program can eliminate all operational edge cases. However, uncontrolled policy exceptions represent a major regulatory vulnerability.
Mandatory Controls for Policy Exceptions
Formal Written Exception Request: Documenting the commercial necessity, full counterparty details, transaction rails, and legal analysis.
Sole Authorization by SCO & Legal: Only the Sanctions Compliance Officer (and Legal Counsel where necessary) may approve a policy deviation; business executives have zero authority to grant exceptions.
Time-Bound Validity: Exceptions must never be permanent. They must have a strict expiration date (e.g., 30 to 90 days) requiring re-evaluation upon renewal.
Centralized Exception Register: Every exception must be logged in an auditable register accessible to Internal Audit and regulatory examiners.
Audit Trail & Immutable Records: All alert dispositions, investigator notes, RFI responses, and clearance rationales must be retained for at least five years (complying with OFAC 31 CFR § 501.601).
Policy Review Schedules & Version Control
Sanctions policies and SOPs cannot remain static:
Annual Scheduled Review: The enterprise Sanctions Policy must undergo a formal, documented review by the compliance team and approval by the Board at least once every 12 months.
Out-of-Cycle (Trigger-Based) Reviews: Immediate updates are required following:
Major geopolitical events and emergency sanctions rollouts (e.g., new sectoral bans or embargoes).
Material changes in screening software, payment messaging formats (e.g., ISO 20022 migration), or core banking platforms.
Severe audit findings, regulatory enforcement actions, or significant internal true match incidents.
Strict Version Control: Every document must maintain an immutable revision history table documenting version number, author, approver, summary of changes, and effective date.
Exam Traps & Deficiencies Checklist
Trap 1: Informal Email Clearances. An analyst clearing a potential sanctions match via unrecorded verbal confirmation or an informal Slack/Teams chat violates audit trail standards. Every clearance must use standardized disposition codes with attached evidentiary documentation in the screening system.
Trap 2: Blanket Exceptions. Granting a permanent, indefinite policy exemption to a high-volume corporate customer to "reduce alert noise" is a critical compliance violation.
Trap 3: Vague Disposition Notes. Disposing of an alert with generic phrases like "False hit / Not my customer" without documenting specific distinguishing factors (e.g., "Beneficiary in Singapore confirmed distinct from designated target in Beirut via passport number and DOB" ) will result in adverse regulatory examination findings.