The banking and financial services industries must address the application security risks associated with JavaScript code in banking applications.
Secure applications mitigate risk and reduce vulnerabilities by protecting against digital fraud and data leakage, while also improving compliance with industry regulations, standards, and laws.
In recent years, web development technologies have evolved rapidly, and JavaScript has become the predominant language of the Web. It powers 97% of modern websites, and every Fortune 500 company uses it.
Client-side JavaScript: Security Considerations
JavaScript is an interpreted language, so client-side JavaScript requires a browser interpreter to read, digest, and run it. This also means anyone can use a browser debugger to inspect the JS code and read or modify it.
With such easy access to client-side JavaScript code, an attacker can easily exploit this weakness and target unprotected code.
Since virtually every company uses JavaScript to develop its apps, it must consider the security risks, especially for apps that handle sensitive user data, such as mobile banking, e-commerce, and streaming services.
The Rise of Mobile Apps in Banking
In banking, the industry has continuously shifted toward a digital-centric approach. Today, you can perform any financial operation through a mobile or web app with minimal hassle and a great user experience.
Despite the benefits of this digital transformation, which has made the banking industry highly competitive, there are security considerations to highlight.
For instance, the emphasis on development speed often leads companies to treat security as an afterthought rather than a priority. In the financial industry, this is especially concerning because a large volume of sensitive data is at risk.
Consequences of Unprotected Source Code in Banking Applications
If left unprotected, banking apps are susceptible to data leakage and fraud attempts because of the sensitive data they handle.
Attackers can leverage web supply chain attacks, exploiting companies’ limited visibility into third-party code, to inject malicious code into websites and tamper with transactions and personal data.
In turn, those attacks can also breach compliance with regulations and standards such as PCI DSS and GDPR, which can bring heavy fines for organizations.
Given the high degree of exposure of sensitive data in these applications, it’s no surprise to see security standards such as PCI DSS now requiring compliant companies to keep an updated inventory of all of their website’s scripts and monitor in real time for the addition of any malicious code, such as payment card skimming code.
The State of Application Security in Banking Applications
Most banking institutions have gone through a stage of digital transformation.
Have these institutions given enough attention to the client-side security of their web and mobile applications?
Jscrambler’s research team has looked more deeply into several regions around the globe to assess the state of application security in banking. The results show some interesting patterns.
63% of banking apps in the LatAm region don’t use obfuscation techniques
In the LatAm region, we had previously found that around 63% of banking applications don’t use obfuscation techniques in their code. The same holds for Brazilian banking apps: 65% leave their code unprotected.
This means most banking apps in these regions are vulnerable to various client-side attacks, as outlined in standards like ISO 27001, OWASP, and NIST.
“Program source code can be vulnerable to attack if not adequately protected and can provide an attacker with a good means to compromise systems in an often covert manner.”
ISO 27001 Standard
Now, the Jscrambler research team has delved into the UK banking industry to see whether banking apps in this region are equally lagging in security. Get first-hand access to these insights by reading the free report on the state of application security in UK banking.
Protecting Banking Applications and Keeping User Data Secure
To protect banking apps from attacks, organizations must adopt application shielding and third-party management techniques.
This includes protecting the client-side source code through a multi-layered approach (obfuscation, environment checks, and runtime protection) while gaining visibility of all third-party code running on the banking website.
Both dimensions are essential to ensuring secure data management practices and mitigating client-side threats in real time before they become a problem.