Application Security in Banking
May 10th, 2022 | By Jscrambler | 3 min read
In the case of banking specifically, we have seen the industry continuously shift towards a digital-centric approach. Nowadays, you can pretty much perform any financial operation through a mobile or web app without any hassle, all while having a great user experience.
Despite all the benefits that come from this digital transformation, which has stimulated a highly competitive banking industry, there are still some security considerations to keep in mind. For instance, the emphasis on development speed often makes companies put security as an afterthought rather than a priority. And in the case of the financial industry, this is especially concerning, since there is a large volume of sensitive data put at risk.
If left unprotected, due to the nature of data they handle, banking apps are susceptible to data leakage and fraud attempts. Attackers can leverage web supply chain attacks, relying on the lack of visibility companies have over their third-party code, to inject malicious code into their websites and tamper with transactions and personal data.
In turn, those attacks also result in a breach of compliance with regulations and standards, such as GDPR, which ends up bringing in 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.
Today, the vast majority of banking institutions have gone through a stage of digital transformation. So, have these institutions given enough attention to the client-side security of their web and mobile applications?
To answer this question, the Jscrambler research team has looked deeper into some regions around the globe to see what the state of application security in banking actually looks like. The results show some interesting patterns.
In the LatAm region, we had previously found that around 63% of banking applications don’t use any obfuscation techniques in their code. The same thing is true for Brazilian banking apps, 65% of which leave their code unprotected. This means that the vast majority of 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, seeking to understand if banking apps in this region are equally lagging behind in terms of security. You can get first-hand access to these insights by watching this webinar.
In order to adequately protect banking apps from attacks, it's crucial that organizations adopt application shielding and third-party management techniques. This includes making sure that the client-side source code is protected using a multi-layered approach (obfuscation, environment checks, and runtime protection), while also gaining full visibility of all third-party code running on the banking website, through a website inventory.
Both of these dimensions are essential to ensure secure data management practices and the mitigation of client-side threats in real-time before they even become a problem.
To learn more on the subject of application security in banking apps, please refer to the following resources:
Webinar: State of Application Security of Banking apps in LatAm (Spanish)
Webinar: State of Application Security of Banking apps in Brazil (Portuguese)
Webinar: State of Application Security of Banking apps in the UK (English)