Cross-Framework Mapping

PSD2 SCAvsGLBA

See exactly how PSD2 SCA controls map to GLBA. Pre-computed mappings, identified gaps, and coverage analysis.

59
Controls Mapped
0
Gaps Found
34%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

PSD2 SCA maps to GLBA with 34% coverage across 16 directly mapped controls. Analysis of 47 PSD2 SCA controls identifies 31 compliance gaps — primarily concentrated in Exemption.

Source: TheArtOfService Knowledge Graph | 47 controls analysed | 726 frameworks | 463K+ cross-framework mappings

Control Mappings

Showing 20 of 59 mapped controls across 5 domains. Sign up to explore all 463K+ mappings across 726 frameworks.

PSD2 SCA: Information Security Governance(7 mappings)

PSD2-03Risk appetite and tolerance for IT risk6 targets
GLBA-16Service Provider Oversight
GLBA-16Service Provider Oversight
GLBA-18Incident Response Plan
GLBA-18Incident Response Plan
GLBA-19Notification of Security Event (FTC)
GLBA-19Notification of Security Event (FTC)
PSD2-05Roles and responsibilities definition
GLBA-05Roles and responsibilities definition

PSD2 SCA: Cybersecurity Controls(6 mappings)

PSD2-06Network security and segmentation
GLBA-06Network security and segmentation
PSD2-07Endpoint protection and detection
GLBA-07Endpoint protection and detection
PSD2-08Application security controls
GLBA-08Application security controls
PSD2-09Encryption and key management
GLBA-09Encryption and key management
PSD2-10Secure configuration standards2 targets
GLBA-10Access Controls and MFA
GLBA-10Access Controls and MFA

PSD2 SCA: Operational Resilience(7 mappings)

PSD2-11Business continuity planning and testing6 targets
GLBA-11Asset Inventory and Data Mapping
GLBA-11Asset Inventory and Data Mapping
GLBA-12Encryption at Rest and in Transit
GLBA-12Encryption at Rest and in Transit
GLBA-15Security Awareness Training
GLBA-15Security Awareness Training
PSD2-12Disaster recovery procedures
GLBA-11Asset Inventory and Data Mapping

+39 more mappings

Plus AI-powered gap analysis, compliance advisory, PDF exports, and cross-mapping for all 726 frameworks.

Create Free Account →

Free forever — no credit card required

Stop Paying Consultants to Read Spreadsheets

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

$0/forever

Free

  • 726 framework browser
  • Cross-framework mappings (463K+)
  • 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 PSD2 SCA and GLBA?

PSD2 SCA has 47 controls across its framework, while GLBA covers 34 controls. Direct mapping analysis identifies 16 overlapping controls (34% coverage). The frameworks diverge most significantly in Exemption, where 7 PSD2 SCA controls have no direct GLBA equivalent.

How many controls map between PSD2 SCA and GLBA?

Of 47 total PSD2 SCA controls, 16 map directly to GLBA controls — representing 34% coverage. The remaining 31 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping PSD2 SCA to GLBA?

31 PSD2 SCA controls have no direct equivalent in GLBA. The highest concentration of gaps is in Exemption with 7 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 PSD2 SCA and GLBA?

The domain with the highest gap count is Exemption (7 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.