TheArtOfService
Cross-Framework Mapping

Chile Personal Data Protection Law (Law No. 21.719)vsEMV 3-D Secure (3DS2) — Payment Authentication Protocol

See exactly how Chile Personal Data Protection Law (Law No. 21.719) controls map to EMV 3-D Secure (3DS2) — Payment Authentication Protocol. Pre-computed mappings, identified gaps, and coverage analysis.

19
Controls Mapped
10
Gaps Found
28%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

Chile Personal Data Protection Law (Law No. 21.719) maps to EMV 3-D Secure (3DS2) — Payment Authentication Protocol with 28% coverage across 8 directly mapped controls. Analysis of 29 Chile Personal Data Protection Law (Law No. 21.719) controls identifies 21 compliance gaps — primarily concentrated in Title IV - Obligations of Data Controllers and Processors.

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

Control Mappings

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

Title IV - Obligations of Data Controllers and Processors(5 mappings)

Art. 14 quinquiesSecurity Measures
→3DS-3.3Data Encryption
Art. 15 bisProcessor Obligations3 targets
→3DS-1.1Three-Domain Model
→3DS-2.1SDK Architecture
→3DS-4.3Split-SDK Specification
Art. 15 terData Protection Impact Assessment
→3DS-2.2Device Information Collection

Title V - Sensitive Data and Special Categories(3 mappings)

Art. 16 terBiometric Data3 targets
→3DS-1.2Authentication Request/Response
→3DS-1.3Challenge Flow
→3DS-2.1SDK Architecture

Title I - General Provisions and Definitions(4 mappings)

Art. 2Consent Definition4 targets
→3DS-1.1Three-Domain Model
→3DS-2.1SDK Architecture
→3DS-4.1Directory Server Interoperability
→3DS-4.3Split-SDK Specification

Title II - Rights of Data Subjects(7 mappings)

Art. 7Minimum Standards2 targets
→3DS-1.1Three-Domain Model
→3DS-4.1Directory Server Interoperability
Art. 8Data Categories3 targets
→3DS-1.1Three-Domain Model
→3DS-2.1SDK Architecture
→3DS-4.3Split-SDK Specification
Art. 9Free Data Sharing2 targets
→3DS-1.1Three-Domain Model
→3DS-4.1Directory Server Interoperability

Related Comparisons

Other Chile Personal Data Protection Law (Law No. 21.719) comparisons

Chile Personal Data Protection Law (Law No. 21.719) vs Serbia Law on Personal Data Protection (2018)14 mappingsChile Personal Data Protection Law (Law No. 21.719) vs Argentina PDPA14 mappingsChile Personal Data Protection Law (Law No. 21.719) vs APPI14 mappingsChile Personal Data Protection Law (Law No. 21.719) vs Pakistan Personal Data Protection Bill 202314 mappingsChile Personal Data Protection Law (Law No. 21.719) vs Privacy Act 1988 (Australia)14 mappingsChile Personal Data Protection Law (Law No. 21.719) vs ILO Nursing Personnel Convention C149 (1977)14 mappingsChile Personal Data Protection Law (Law No. 21.719) vs 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673)14 mappingsChile Personal Data Protection Law (Law No. 21.719) vs ISO 8000 — Data Quality14 mappings

Other EMV 3-D Secure (3DS2) — Payment Authentication Protocol comparisons

Connecticut Data Privacy Act (CTDPA) vs EMV 3-D Secure (3DS2) — Payment Authentication Protocol8 mappingsNIST SP 800-171A Rev 3 — Assessing CUI Security Requirements vs EMV 3-D Secure (3DS2) — Payment Authentication Protocol7 mappings3GPP Security Architecture (TS 33.501 — 5G Security) vs EMV 3-D Secure (3DS2) — Payment Authentication Protocol7 mappingsUK Open Banking Standard vs EMV 3-D Secure (3DS2) — Payment Authentication Protocol7 mappingsCSA STAR (Security, Trust, Assurance, and Risk) vs EMV 3-D Secure (3DS2) — Payment Authentication Protocol7 mappingsDigital Economy Partnership Agreement (DEPA) vs EMV 3-D Secure (3DS2) — Payment Authentication Protocol7 mappingsNIST SP 800-146 vs EMV 3-D Secure (3DS2) — Payment Authentication Protocol7 mappingsFTC GLBA Safeguards Rule (16 CFR Part 314) vs EMV 3-D Secure (3DS2) — Payment Authentication Protocol7 mappings

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 →

Popular framework comparisons

NIST CSF vs NIST 800-53ISO 27001 vs NIST CSFCMMC vs NIST 800-53FedRAMP vs NIST 800-53NIST CSF vs SOC 2HIPAA vs NIST 800-53ISO 27001 vs SOC 2ISO 27001 vs ISO 27701

What are the key differences between Chile Personal Data Protection Law (Law No. 21.719) and EMV 3-D Secure (3DS2) — Payment Authentication Protocol?

Chile Personal Data Protection Law (Law No. 21.719) has 29 controls across its framework, while EMV 3-D Secure (3DS2) — Payment Authentication Protocol covers 15 controls. Direct mapping analysis identifies 8 overlapping controls (28% coverage). The frameworks diverge most significantly in Title IV - Obligations of Data Controllers and Processors, where 4 Chile Personal Data Protection Law (Law No. 21.719) controls have no direct EMV 3-D Secure (3DS2) — Payment Authentication Protocol equivalent.

How many controls map between Chile Personal Data Protection Law (Law No. 21.719) and EMV 3-D Secure (3DS2) — Payment Authentication Protocol?

Of 29 total Chile Personal Data Protection Law (Law No. 21.719) controls, 8 map directly to EMV 3-D Secure (3DS2) — Payment Authentication Protocol controls — representing 28% coverage. The remaining 21 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping Chile Personal Data Protection Law (Law No. 21.719) to EMV 3-D Secure (3DS2) — Payment Authentication Protocol?

21 Chile Personal Data Protection Law (Law No. 21.719) controls have no direct equivalent in EMV 3-D Secure (3DS2) — Payment Authentication Protocol. The highest concentration of gaps is in Title IV - Obligations of Data Controllers and Processors 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 Chile Personal Data Protection Law (Law No. 21.719) and EMV 3-D Secure (3DS2) — Payment Authentication Protocol?

The domain with the highest gap count is Title IV - Obligations of Data Controllers and Processors (4 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.

Related Resources

How to Map Controls Across Frameworks|Multi-Framework Compliance Guide|Compliance Glossary

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.