Compliance Gap Analysis
Structured assessment of an organization's compliance posture against one or more regulatory frameworks, producing a gap register with severity ratings, remediation priorities, and estimated effort. Used as input to compliance program design, external audit preparation, board reporting, and regulatory examination preparation.
When to use this
- An organization is entering a new jurisdiction and needs to understand the compliance build required
- A compliance programme is being refreshed after a regulatory change
- An M&A transaction requires compliance due diligence on the target
- A regulator has issued a finding or information request and the organization needs to understand its exposure
- Internal audit is scoping a compliance review and needs a framework
Inputs
| Input |
Why it matters |
Default |
| Organization description (sector, size, geographic footprint) |
Determines which frameworks apply and at what level |
Required |
| Frameworks to assess |
Specify: AML, sanctions, data protection, anti-bribery, ESG, sector-specific, or "all applicable" |
Required or infer from sector + jurisdiction |
| Current-state documentation (policies, procedures, controls, audit reports) |
Enables gap assessment vs a baseline; without it, assessment is hypothetical |
Provide if available |
| Regulatory correspondences or prior findings |
Indicates known gaps already identified by a regulator |
Provide if available |
| Risk appetite / materiality threshold |
Determines what counts as a "blocker" vs a "polish" item |
Default: any regulatory breach = blocker; best-practice gaps = improvement |
Framework coverage
AML / KYC (FATF 40 Recommendations)
Core requirements:
- Customer Due Diligence (CDD): identification, verification, beneficial ownership identification (≥ 25% UBO threshold, per [[research-beneficial-ownership-lookup]])
- Enhanced Due Diligence (EDD): for high-risk customers (PEPs, high-risk jurisdictions, complex structures)
- Ongoing monitoring: transaction monitoring, periodic KYC refresh
- Suspicious Transaction Reporting (STR): to financial intelligence unit (UAEFIU, SAMA/SAFIU, BDL-SIC)
- Record keeping: 5 years minimum (most MENA jurisdictions) from end of relationship
- FATF Travel Rule: for virtual asset transfers ≥ threshold (USD/EUR/AED 1,000 equivalent), originator and beneficiary information must travel with the transfer
MENA-specific AML gaps commonly found:
- Failure to identify/verify beneficial owners beyond the direct account holder
- Inadequate PEP screening (often limited to international lists; missing local PEPs)
- No documented risk appetite for customer types and jurisdictions
- Transaction monitoring rules not calibrated to the customer's expected behavior
- DNFBP (real estate, legal, accounting) obligations often not implemented — UAE Cabinet Decision No. 10 of 2019 extended AML obligations to DNFBPs
Sanctions
Core requirements:
- Screen customers, counterparties, and UBOs against all applicable lists (per [[research-sanctions-screening]])
- Freeze assets of designated parties; file Suspicious Transaction Report
- Maintain a documented screening process, screening frequency, and match-disposition workflow
- Re-screen at meaningful events (transaction trigger, periodic refresh, news alert)
Gap patterns:
- Screening only the direct party, not UBOs
- Using a sanctions screening tool not configured for Arabic-script name matching
- No documented process for handling near-matches (screening produces false positives; the process for clearing them must be documented)
- Not re-screening existing customers when lists are updated (daily updates to OFAC SDN are common)
Data Protection
Multiple overlapping regimes may apply simultaneously:
| Framework |
Trigger |
Key requirements |
| GDPR |
EU personal data processed |
Lawful basis per processing activity; privacy notice; records of processing; DPIAs for high-risk; 72-hour breach notification; DSR handling |
| UAE PDPL (Federal Decree-Law No. 45 of 2021) |
UAE personal data |
Consent or legitimate interest; privacy policy; data controller obligations; 72-hour breach notification |
| KSA PDPL (Royal Decree M/19 of 2021) |
KSA personal data |
Consent required for most processing; cross-border transfer restrictions; NDMO registration |
| Bahrain PDPL |
Bahrain personal data |
Broadly similar to GDPR |
| Egypt PDPL (Law No. 151 of 2020) |
Egypt personal data |
ITIDA registration; consent; 72-hour breach notification |
For a full GDPR-specific review, see [[review-gdpr-readiness]].
Cross-border transfer gap (MENA): Many MENA companies use US-hosted cloud services; cross-border transfer mechanisms under KSA PDPL and UAE PDPL are still developing. Standard Contractual Clauses (SCCs) used for GDPR compliance may not satisfy KSA PDPL Article 29 requirements.
Anti-Bribery
| Framework |
Jurisdictional reach |
Key requirements |
| FCPA (US) |
US persons, US-listed companies, anything in US commerce |
Prohibits bribery of foreign government officials; accounting provisions require accurate books |
| UK Bribery Act 2010 |
UK-incorporated entities, persons carrying on business in UK |
Broadest reach: strict liability for commercial organisations that fail to prevent bribery; extends to private-to-private bribery |
| KSA Anti-Bribery Law (Royal Decree M/36 of 2017) |
KSA entities and persons |
Prohibits both offering and receiving bribes; applies to public sector officials and private sector |
| UAE Federal Law No. 31 of 2021 (Penal Code) |
UAE entities and persons |
Anti-bribery provisions covering public officials; gift policies required for regulated entities |
Common gaps in MENA anti-bribery programs:
- Facilitation payments: illegal under UK Bribery Act (no exception); FCPA has a narrow exception (being narrowed by enforcement); illegal under MENA laws
- Third-party agent diligence: many MENA transactions use intermediaries; inadequate due diligence on agents is the most common FCPA/UKBA enforcement trigger
- No written anti-bribery policy; no training; no speak-up mechanism
ESG / Disclosure
| Framework |
Scope |
Key requirements |
| CSRD (EU Corporate Sustainability Reporting Directive) |
EU companies + non-EU companies with EU operations above threshold |
Mandatory sustainability reporting against ESRS standards; third-party assurance |
| SEC Climate Disclosure Rule (US) |
SEC registrants |
Mandatory disclosure of climate risks, GHG emissions (Scopes 1 and 2) |
| Saudi Green Initiative / ESG |
KSA-listed and large private companies |
Increasing expectation of ESG disclosure aligned with Saudi Vision 2030 |
| Abu Dhabi Net Zero 2050 / Dubai 2040 |
UAE entities |
Voluntary targets; increasingly expected for regulated entities |
Sector-specific frameworks
| Sector |
Additional frameworks |
| Banking |
BCBS Basel III/IV; CRD VI (EU); CBUAE CAR; SAMA Capital Adequacy |
| Insurance |
Solvency II (EU); CBUAE Insurance Authority regulations; SAMA insurance circulars |
| Fintech |
DFSA Innovation Testing Licence; FSRA RegLab; SAMA/CMA sandbox; EU MiCA for crypto assets |
| Healthcare |
HIPAA (US); NMC/DOH/DHA clinical governance standards (UAE); HAAD standards |
| Telecoms |
TRA UAE; CITC KSA; SMEX Lebanon |
Review methodology
Step 1 — Framework scoping
Confirm which frameworks apply based on:
- Sectors in which the organization operates
- Jurisdictions in which it is licensed or operates
- Nature of its customer base (retail, professional, government)
- Whether it handles EU personal data (triggers GDPR)
- Whether it has US or UK operations (triggers FCPA / UK Bribery Act)
Step 2 — Current-state assessment
For each requirement within each framework, assess:
- Is there a documented policy or procedure?
- Are controls implemented in practice (not just on paper)?
- Is there evidence of training and awareness?
- Are there audit results confirming effectiveness?
Step 3 — Gap identification
For each gap, record:
- The specific requirement not met (with framework citation)
- The nature of the gap: complete absence vs partial implementation vs documentation gap vs effectiveness gap
- Evidence reviewed (or absence of evidence)
Step 4 — Severity rating
| Severity |
Definition |
Typical remediation timeline |
| Blocker (Critical) |
Active regulatory breach; regulatory enforcement risk; immediate professional-liability exposure |
Fix within 30 days |
| Material (High) |
Significant gap that would be cited in a regulatory examination; reputational risk if exploited |
60–90 day remediation plan |
| Moderate |
Best-practice gap; unlikely to trigger enforcement but would be noted in audit |
90–180 day improvement plan |
| Minor |
Documentation gap or process improvement; no current regulatory risk |
Next annual cycle |
Materiality principle: distinguish "blockers" (a compliance program that is entirely absent for a mandatory framework) from "polish" (a program that exists but has minor documentation gaps). A regulator assessing a CBUAE examination will weight these very differently.
Output format
{
"organizationProfile": "string",
"frameworksAssessed": ["list"],
"assessmentDate": "ISO date",
"gaps": [
{
"framework": "AML | Sanctions | GDPR | UAE-PDPL | KSA-PDPL | Anti-Bribery | ESG | Sector-specific",
"requirement": "specific requirement description with regulatory citation",
"currentState": "description of what currently exists",
"requiredState": "description of what is required",
"gap": "description of the delta",
"severity": "Blocker | Material | Moderate | Minor",
"remediationAction": "specific action to close the gap",
"owner": "function responsible (Legal | Compliance | IT | HR | Finance)",
"targetDate": "ISO date",
"estimatedEffort": "small (days) | medium (weeks) | large (months)"
}
],
"summary": {
"totalGaps": number,
"blockers": number,
"material": number,
"moderate": number,
"minor": number
},
"prioritizedRoadmap": "Ordered list of top 10 remediation actions by severity + effort"
}
Limits and escalation
- This skill produces a gap register as a starting point, not a completed audit. A formal compliance audit requires on-site testing, document review, and interviews.
- For GDPR, [[review-gdpr-readiness]] provides a more detailed 10-area review.
- For sanctions, [[research-sanctions-screening]] is required for transaction-level screening.
- For AML, [[research-beneficial-ownership-lookup]] is required to complete UBO identification.
- Regulatory enforcement risk assessments require jurisdiction-qualified legal counsel.
Related skills
- [[research-regulator-guidance-lookup]]
- [[research-regulation-lookup]]
- [[research-sanctions-screening]]
- [[research-beneficial-ownership-lookup]]
- [[review-gdpr-readiness]]
1---2name: review-compliance-gap-analysis3description: Use when a compliance officer, legal team, or external adviser needs to map an organization's current compliance posture against applicable regulatory frameworks — identifying gaps, quantifying severity, and recommending remediation. Covers AML/KYC (FATF 40 Recommendations + Travel Rule), sanctions (OFAC, UN, EU, MENA national lists), data protection (GDPR, KSA PDPL, UAE PDPL, Bahrain, Egypt), anti-bribery (FCPA, UK Bribery Act, MENA laws), ESG/disclosure, and sector-specific frameworks (banking, fintech, insurance, healthcare). Outputs a structured gap register with severity tiers.4license: MIT5metadata:6 id: review.compliance-gap-analysis7 category: review8 practice_area: regulatory9 jurisdictions: [UAE, KSA, LB, EG, UK, EU, US]10 priority: P111 intent: [review, compliance, gap-analysis, aml, gdpr, sanctions, anti-bribery, regulatory]12 related: [research-regulator-guidance-lookup, research-regulation-lookup, research-sanctions-screening, research-beneficial-ownership-lookup, review-gdpr-readiness]13 source: https://skillmd.com/skills/sboghossian-mini-claude-for-legal/review-compliance-gap-analysis14 upstream: Louis — HAQQ Legal AI (github.com/sboghossian/mini-claude-for-legal)15 version: "1.0"16---1718# Compliance Gap Analysis1920Structured assessment of an organization's compliance posture against one or more regulatory frameworks, producing a gap register with severity ratings, remediation priorities, and estimated effort. Used as input to compliance program design, external audit preparation, board reporting, and regulatory examination preparation.2122## When to use this2324- An organization is entering a new jurisdiction and needs to understand the compliance build required25- A compliance programme is being refreshed after a regulatory change26- An M&A transaction requires compliance due diligence on the target27- A regulator has issued a finding or information request and the organization needs to understand its exposure28- Internal audit is scoping a compliance review and needs a framework2930## Inputs3132| Input | Why it matters | Default |33|-------|---------------|---------|34| Organization description (sector, size, geographic footprint) | Determines which frameworks apply and at what level | Required |35| Frameworks to assess | Specify: AML, sanctions, data protection, anti-bribery, ESG, sector-specific, or "all applicable" | Required or infer from sector + jurisdiction |36| Current-state documentation (policies, procedures, controls, audit reports) | Enables gap assessment vs a baseline; without it, assessment is hypothetical | Provide if available |37| Regulatory correspondences or prior findings | Indicates known gaps already identified by a regulator | Provide if available |38| Risk appetite / materiality threshold | Determines what counts as a "blocker" vs a "polish" item | Default: any regulatory breach = blocker; best-practice gaps = improvement |3940## Framework coverage4142### AML / KYC (FATF 40 Recommendations)4344**Core requirements**:45- Customer Due Diligence (CDD): identification, verification, beneficial ownership identification (≥ 25% UBO threshold, per [[research-beneficial-ownership-lookup]])46- Enhanced Due Diligence (EDD): for high-risk customers (PEPs, high-risk jurisdictions, complex structures)47- Ongoing monitoring: transaction monitoring, periodic KYC refresh48- Suspicious Transaction Reporting (STR): to financial intelligence unit (UAEFIU, SAMA/SAFIU, BDL-SIC)49- Record keeping: 5 years minimum (most MENA jurisdictions) from end of relationship50- FATF Travel Rule: for virtual asset transfers ≥ threshold (USD/EUR/AED 1,000 equivalent), originator and beneficiary information must travel with the transfer5152**MENA-specific AML gaps commonly found**:53- Failure to identify/verify beneficial owners beyond the direct account holder54- Inadequate PEP screening (often limited to international lists; missing local PEPs)55- No documented risk appetite for customer types and jurisdictions56- Transaction monitoring rules not calibrated to the customer's expected behavior57- DNFBP (real estate, legal, accounting) obligations often not implemented — UAE Cabinet Decision No. 10 of 2019 extended AML obligations to DNFBPs5859### Sanctions6061**Core requirements**:62- Screen customers, counterparties, and UBOs against all applicable lists (per [[research-sanctions-screening]])63- Freeze assets of designated parties; file Suspicious Transaction Report64- Maintain a documented screening process, screening frequency, and match-disposition workflow65- Re-screen at meaningful events (transaction trigger, periodic refresh, news alert)6667**Gap patterns**:68- Screening only the direct party, not UBOs69- Using a sanctions screening tool not configured for Arabic-script name matching70- No documented process for handling near-matches (screening produces false positives; the process for clearing them must be documented)71- Not re-screening existing customers when lists are updated (daily updates to OFAC SDN are common)7273### Data Protection7475Multiple overlapping regimes may apply simultaneously:7677| Framework | Trigger | Key requirements |78|-----------|---------|-----------------|79| GDPR | EU personal data processed | Lawful basis per processing activity; privacy notice; records of processing; DPIAs for high-risk; 72-hour breach notification; DSR handling |80| UAE PDPL (Federal Decree-Law No. 45 of 2021) | UAE personal data | Consent or legitimate interest; privacy policy; data controller obligations; 72-hour breach notification |81| KSA PDPL (Royal Decree M/19 of 2021) | KSA personal data | Consent required for most processing; cross-border transfer restrictions; NDMO registration |82| Bahrain PDPL | Bahrain personal data | Broadly similar to GDPR |83| Egypt PDPL (Law No. 151 of 2020) | Egypt personal data | ITIDA registration; consent; 72-hour breach notification |8485For a full GDPR-specific review, see [[review-gdpr-readiness]].8687**Cross-border transfer gap (MENA)**: Many MENA companies use US-hosted cloud services; cross-border transfer mechanisms under KSA PDPL and UAE PDPL are still developing. Standard Contractual Clauses (SCCs) used for GDPR compliance may not satisfy KSA PDPL Article 29 requirements.8889### Anti-Bribery9091| Framework | Jurisdictional reach | Key requirements |92|-----------|---------------------|-----------------|93| FCPA (US) | US persons, US-listed companies, anything in US commerce | Prohibits bribery of foreign government officials; accounting provisions require accurate books |94| UK Bribery Act 2010 | UK-incorporated entities, persons carrying on business in UK | Broadest reach: strict liability for commercial organisations that fail to prevent bribery; extends to private-to-private bribery |95| KSA Anti-Bribery Law (Royal Decree M/36 of 2017) | KSA entities and persons | Prohibits both offering and receiving bribes; applies to public sector officials and private sector |96| UAE Federal Law No. 31 of 2021 (Penal Code) | UAE entities and persons | Anti-bribery provisions covering public officials; gift policies required for regulated entities |9798**Common gaps in MENA anti-bribery programs**:99- Facilitation payments: illegal under UK Bribery Act (no exception); FCPA has a narrow exception (being narrowed by enforcement); illegal under MENA laws100- Third-party agent diligence: many MENA transactions use intermediaries; inadequate due diligence on agents is the most common FCPA/UKBA enforcement trigger101- No written anti-bribery policy; no training; no speak-up mechanism102103### ESG / Disclosure104105| Framework | Scope | Key requirements |106|-----------|-------|-----------------|107| CSRD (EU Corporate Sustainability Reporting Directive) | EU companies + non-EU companies with EU operations above threshold | Mandatory sustainability reporting against ESRS standards; third-party assurance |108| SEC Climate Disclosure Rule (US) | SEC registrants | Mandatory disclosure of climate risks, GHG emissions (Scopes 1 and 2) |109| Saudi Green Initiative / ESG | KSA-listed and large private companies | Increasing expectation of ESG disclosure aligned with Saudi Vision 2030 |110| Abu Dhabi Net Zero 2050 / Dubai 2040 | UAE entities | Voluntary targets; increasingly expected for regulated entities |111112### Sector-specific frameworks113114| Sector | Additional frameworks |115|--------|----------------------|116| Banking | BCBS Basel III/IV; CRD VI (EU); CBUAE CAR; SAMA Capital Adequacy |117| Insurance | Solvency II (EU); CBUAE Insurance Authority regulations; SAMA insurance circulars |118| Fintech | DFSA Innovation Testing Licence; FSRA RegLab; SAMA/CMA sandbox; EU MiCA for crypto assets |119| Healthcare | HIPAA (US); NMC/DOH/DHA clinical governance standards (UAE); HAAD standards |120| Telecoms | TRA UAE; CITC KSA; SMEX Lebanon |121122## Review methodology123124### Step 1 — Framework scoping125126Confirm which frameworks apply based on:127- Sectors in which the organization operates128- Jurisdictions in which it is licensed or operates129- Nature of its customer base (retail, professional, government)130- Whether it handles EU personal data (triggers GDPR)131- Whether it has US or UK operations (triggers FCPA / UK Bribery Act)132133### Step 2 — Current-state assessment134135For each requirement within each framework, assess:136- Is there a documented policy or procedure?137- Are controls implemented in practice (not just on paper)?138- Is there evidence of training and awareness?139- Are there audit results confirming effectiveness?140141### Step 3 — Gap identification142143For each gap, record:144- The specific requirement not met (with framework citation)145- The nature of the gap: complete absence vs partial implementation vs documentation gap vs effectiveness gap146- Evidence reviewed (or absence of evidence)147148### Step 4 — Severity rating149150| Severity | Definition | Typical remediation timeline |151|----------|-----------|------------------------------|152| **Blocker (Critical)** | Active regulatory breach; regulatory enforcement risk; immediate professional-liability exposure | Fix within 30 days |153| **Material (High)** | Significant gap that would be cited in a regulatory examination; reputational risk if exploited | 60–90 day remediation plan |154| **Moderate** | Best-practice gap; unlikely to trigger enforcement but would be noted in audit | 90–180 day improvement plan |155| **Minor** | Documentation gap or process improvement; no current regulatory risk | Next annual cycle |156157**Materiality principle**: distinguish "blockers" (a compliance program that is entirely absent for a mandatory framework) from "polish" (a program that exists but has minor documentation gaps). A regulator assessing a CBUAE examination will weight these very differently.158159## Output format160161```json162{163 "organizationProfile": "string",164 "frameworksAssessed": ["list"],165 "assessmentDate": "ISO date",166 "gaps": [167 {168 "framework": "AML | Sanctions | GDPR | UAE-PDPL | KSA-PDPL | Anti-Bribery | ESG | Sector-specific",169 "requirement": "specific requirement description with regulatory citation",170 "currentState": "description of what currently exists",171 "requiredState": "description of what is required",172 "gap": "description of the delta",173 "severity": "Blocker | Material | Moderate | Minor",174 "remediationAction": "specific action to close the gap",175 "owner": "function responsible (Legal | Compliance | IT | HR | Finance)",176 "targetDate": "ISO date",177 "estimatedEffort": "small (days) | medium (weeks) | large (months)"178 }179 ],180 "summary": {181 "totalGaps": number,182 "blockers": number,183 "material": number,184 "moderate": number,185 "minor": number186 },187 "prioritizedRoadmap": "Ordered list of top 10 remediation actions by severity + effort"188}189```190191## Limits and escalation192193- This skill produces a gap register as a starting point, not a completed audit. A formal compliance audit requires on-site testing, document review, and interviews.194- For GDPR, [[review-gdpr-readiness]] provides a more detailed 10-area review.195- For sanctions, [[research-sanctions-screening]] is required for transaction-level screening.196- For AML, [[research-beneficial-ownership-lookup]] is required to complete UBO identification.197- Regulatory enforcement risk assessments require jurisdiction-qualified legal counsel.198199## Related skills200201- [[research-regulator-guidance-lookup]]202- [[research-regulation-lookup]]203- [[research-sanctions-screening]]204- [[research-beneficial-ownership-lookup]]205- [[review-gdpr-readiness]]