Cross-Framework Mapping

3GPP 5G Security Architecture (TS 33.501)vsFATF Recommendation 16 — Virtual Asset Travel Rule

See exactly how 3GPP 5G Security Architecture (TS 33.501) controls map to FATF Recommendation 16 — Virtual Asset Travel Rule. Pre-computed mappings, identified gaps, and coverage analysis.

6
Controls Mapped
22
Gaps Found
14%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

3GPP 5G Security Architecture (TS 33.501) maps to FATF Recommendation 16 — Virtual Asset Travel Rule with 14% coverage across 4 directly mapped controls. Analysis of 28 3GPP 5G Security Architecture (TS 33.501) controls identifies 24 compliance gaps — primarily concentrated in Security for Specific Services.

Source: TheArtOfService Knowledge Graph | 28 controls analysed | 693 frameworks | 819K+ cross-framework mappings

Control Mappings

Showing 6 of 6 mapped controls across 3 domains. Sign up to explore all 819K+ mappings across 693 frameworks.

Authentication and Key Management(4 mappings)

6.3SUPI and SUCI Privacy2 targets
FATF-TR-IMP-03VASP AML/CFT
FATF-TR-RQ-03Unhosted Wallets
6.5AUSF and SEAF Functions2 targets
FATF-TR-IMP-03VASP AML/CFT
FATF-TR-RQ-03Unhosted Wallets

Service Based Architecture Security(1 mappings)

TS33.501-13.2Service Based Interface Security
PBD-IMP-01GDPR Article 25

Security for NAS and AS Protocols(1 mappings)

TS33.501-6.6AS Security
PBD-IMP-01GDPR Article 25

Related Comparisons

Other 3GPP 5G Security Architecture (TS 33.501) comparisons

Other FATF Recommendation 16 — Virtual Asset Travel Rule comparisons

Stop Paying Consultants to Read Spreadsheets

AI-powered compliance intelligence across 693 frameworks — at a fraction of consulting costs.

$0/forever

Free

  • 693 framework browser
  • Cross-framework mappings (819K+)
  • 824 compliance assessments
  • 3 AI queries & searches per day
Get Started Free
Recommended
$49/month

Professional

  • Unlimited AI Compliance Advisory
  • Unlimited full-text search
  • Framework self-assessment
  • PDF, Excel & CSV exports
Start 7-Day Free Trial →

What are the key differences between 3GPP 5G Security Architecture (TS 33.501) and FATF Recommendation 16 — Virtual Asset Travel Rule?

3GPP 5G Security Architecture (TS 33.501) has 28 controls across its framework, while FATF Recommendation 16 — Virtual Asset Travel Rule covers 22 controls. Direct mapping analysis identifies 4 overlapping controls (14% coverage). The frameworks diverge most significantly in Security for Specific Services, where 4 3GPP 5G Security Architecture (TS 33.501) controls have no direct FATF Recommendation 16 — Virtual Asset Travel Rule equivalent.

How many controls map between 3GPP 5G Security Architecture (TS 33.501) and FATF Recommendation 16 — Virtual Asset Travel Rule?

Of 28 total 3GPP 5G Security Architecture (TS 33.501) controls, 4 map directly to FATF Recommendation 16 — Virtual Asset Travel Rule controls — representing 14% coverage. The remaining 24 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping 3GPP 5G Security Architecture (TS 33.501) to FATF Recommendation 16 — Virtual Asset Travel Rule?

24 3GPP 5G Security Architecture (TS 33.501) controls have no direct equivalent in FATF Recommendation 16 — Virtual Asset Travel Rule. The highest concentration of gaps is in Security for Specific Services with 4 unmapped controls. These gaps represent areas where additional controls, policies, or documentation must be created to achieve compliance with both frameworks.

Which control domains have the most gaps between 3GPP 5G Security Architecture (TS 33.501) and FATF Recommendation 16 — Virtual Asset Travel Rule?

The domain with the highest gap count is Security for Specific Services (4 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.

This platform provides educational compliance tools, not legal, regulatory, or professional compliance advice. Cross-framework mappings are AI-assisted interpretations and do not reproduce or replace official standards. Framework names and trademarks belong to their respective owners. Consult qualified professionals for your specific compliance requirements. See our Terms of Service.