Ticket Discounts for Cyber Events

GET ALERTS!

Recommended Event: Gartner Security & Risk Management Summit | 22 - 24 Sep 2026

How Banking Sites Unknowingly Expose Customer Data to Third Parties

Solution Category Application Security
Type Webinar
Organization Jscrambler
Event Format Company Webinar

Webinar Description

Key Takeaways

  • Security research reveals widespread unintentional data leakage from banking websites to third-party advertising platforms
  • Browser-based tracking scripts can capture sensitive financial data before consent is granted or after it is explicitly rejected
  • Exposed data includes loan amounts, account details, and hashed email addresses
  • Designed for security professionals, compliance officers, and IT leaders in banking and financial services
  • Covers technical mechanisms behind client-side data exposure and runtime defence strategies

Introduction

Financial institutions invest heavily in perimeter security, encryption, and access controls, yet a significant vulnerability persists in an often-overlooked area: the browser. New security research indicates that numerous banking websites across the United States and Europe are inadvertently transmitting sensitive customer data to third-party advertising platforms through client-side scripts. This webinar, hosted by Jscrambler, examines documented cases of these data leaks and explores the technical realities that allow them to occur despite consent management frameworks.

About This Event

The Crack in the Vault: How Banking Sites Unknowingly Expose Customer Data to Third Parties is a live virtual webinar scheduled for August 2026. The session brings together security researchers and product specialists from Jscrambler to present findings from recent investigations into client-side data exposure within the financial sector. Attendees will receive a technical breakdown of how these leaks occur, along with practical guidance on implementing runtime controls to secure data flows at the browser level.

The Client-Side Security Gap in Financial Services

Traditional security architectures focus on protecting servers, databases, and network infrastructure. However, modern web applications rely extensively on third-party JavaScript for analytics, advertising, and functionality enhancements. These scripts execute directly in the user’s browser, operating outside the security perimeter that organisations typically monitor and control.

The research presented in this webinar demonstrates that tracking scripts embedded in banking websites can capture data including loan application amounts, account information, and hashed email addresses. More concerning is the timing of this data collection: scripts may execute before a user has provided consent or continue operating after consent has been explicitly denied. This behaviour undermines the fundamental assumptions of consent management platforms and creates compliance exposure under regulations such as GDPR and CCPA.

Technical Mechanisms Behind Data Exposure

The webinar will detail how browser-based scripts bypass traditional security controls. Third-party code loaded into a webpage typically has access to the same document object model as first-party code, enabling it to read form inputs, monitor user interactions, and transmit data to external servers. When financial institutions embed advertising or analytics scripts without granular runtime controls, they effectively grant these third parties access to sensitive customer information.

Financial intent data presents particular risks. Information about loan amounts, investment interests, or account balances can be valuable for targeted advertising but represents a serious privacy violation when collected without proper authorisation. The session will examine specific cases where such data has been observed flowing to ad-tech platforms.

Implementing Runtime Defence Strategies

Beyond identifying the problem, the webinar addresses practical remediation. Runtime controls offer a mechanism for monitoring and restricting script behaviour as it occurs in the browser. Unlike static code analysis, which examines scripts before deployment, runtime monitoring can detect and block unauthorised data access in real time.

Continuous client-side monitoring enables security teams to maintain visibility over third-party script behaviour, identify anomalous data collection patterns, and enforce policies that align with stated consent preferences. This approach addresses the gap between what organisations promise users about data handling and what actually occurs in the browser environment.

Who Should Attend

This webinar is relevant for professionals responsible for application security, data privacy, and regulatory compliance within financial institutions. Chief Information Security Officers, security analysts, compliance managers, IT directors, and product managers working in banking, fintech, and related sectors will find the content directly applicable to their operational challenges. The session assumes familiarity with web application architecture and privacy regulations but does not require deep technical expertise in JavaScript security.

Conclusion

As financial services organisations face increasing scrutiny over data handling practices, understanding client-side vulnerabilities becomes essential. This webinar provides security and compliance professionals with documented evidence of how data leakage occurs and actionable strategies for closing the gap between privacy commitments and technical reality.