More Breaches, More Problems: The Cost of Trust in Third-Party Apps
It's no secret that our main mission is to make software and its development safe; crafted with security in mind from the very beginning of production. Our vision sets a new benchmark for software creation, where developers are empowered with the skills and knowledge detect vulnerable code during the writing process and fix it before it even becomes an issue.
So, with that in mind, you may think we're delighted to hear of new data breaches, cyber attacks and exploited code affecting companies all over the world - those incidents certainly highlight the need for our service in multiple verticals. The truth is, it's quite frustrating. It's clear that as an industry we are making the same mistakes time and time again, because most security education just isn't robust enough to minimise risk and stop these breaches.
The latest data breach victim is Ticketmaster. If you were among the thousands of affected customers, you'd have received an email notifying you of the incident and to change your password. No-one expects to have their personal data violated simply for buying tickets to a concert or sporting event, yet here we are.
It's an awful situation for everyone; detrimental to Ticketmaster's reputation and a downright rotten customer experience. There's one problem, though: it wasn't entirely their fault.
You see, the company utilised the services of a third-party customer support application from Inbenta Technologies. Ticketmaster UK discovered that the product contained malicious code, leading to five percent of their global customer data being compromised.
And how exactly did hackers manage to exploit this system? They manipulated a single line of JavaScript code, customized by Inbenta Technologies for Ticketmaster's requirements. According to Inbenta, the code was used on a page it was not built to accommodate, and had they known, would have identified it as a security vulnerability.
The vulnerability itself is essentially a file upload/storage library security issue, wherein just one breach can affect every site on which the same code is loaded. The code can be modified to collect and reroute personal data to the attackers, just for starters. This is a simple exploit with far-reaching damage potential, and it is something we are working on defending against with a range of in-platform training exercises for developers.
Of course, it's virtually impossible to run a business without relying on some third-party applications. However, you have no control over how they build their software, and essentially zero visibility on the security strength of their code. It becomes a trust exercise. If your third-party partner is lax in their secure coding practices, you may be opening the door to a breach in yourcompany.
So, what's the solution? Put simply: we all must do better. We must stop thinking of security as an irritating obstacle on the path of company innovation.
It is easier than you think to empower your dev team with the right tools and knowledge to embrace security, stopping bad code in its tracks. We have been pleased to see so many of the worlds largest and most well-known financial, telecommunications, retail and tech companies adopt this new approach, but it shouldnt be the sole domain of Fortune 100 companies to take steps in security education. Every company that counts developers among their staff needs to implement training to help teams code securely.
The recently released white paper I wrote in conjunction with our CTO Matias Madou, showcases the benefits of building a security culture in your organisation. We detail why it is the key to unlocking innovation, staying agile and reducing the financial impact of insecure code.
You'll find tips including:
* How to make security training relevant and engaging for developers
* How to teach developers to identify and fix their own issues
* How to help developers securely construct their own code.
I invite you to download this resource and use it to champion security in your organisation, build the skills of your team and be at the forefront of setting a higher standard of code.
We must stop thinking of security as an irritating obstacle on the path of company innovation.
We must stop thinking of security as an irritating obstacle on the path of company innovation.
Chief Executive Officer, Chairman, and Co-Founder
Secure Code Warrior is here for your organization to help you secure code across the entire software development lifecycle and create a culture in which cybersecurity is top of mind. Whether you’re an AppSec Manager, Developer, CISO, or anyone involved in security, we can help your organization reduce risks associated with insecure code.
Book a demo
Chief Executive Officer, Chairman, and Co-Founder
Pieter Danhieux is a globally recognized security expert, with over 12 years experience as a security consultant and 8 years as a Principal Instructor for SANS teaching offensive techniques on how to target and assess organizations, systems and individuals for security weaknesses. In 2016, he was recognized as one of the Coolest Tech people in Australia (Business Insider), awarded Cyber Security Professional of the Year (AISA - Australian Information Security Association) and holds GSE, CISSP, GCIH, GCFA, GSEC, GPEN, GWAPT, GCIA certifications.
It's no secret that our main mission is to make software and its development safe; crafted with security in mind from the very beginning of production. Our vision sets a new benchmark for software creation, where developers are empowered with the skills and knowledge detect vulnerable code during the writing process and fix it before it even becomes an issue.
So, with that in mind, you may think we're delighted to hear of new data breaches, cyber attacks and exploited code affecting companies all over the world - those incidents certainly highlight the need for our service in multiple verticals. The truth is, it's quite frustrating. It's clear that as an industry we are making the same mistakes time and time again, because most security education just isn't robust enough to minimise risk and stop these breaches.
The latest data breach victim is Ticketmaster. If you were among the thousands of affected customers, you'd have received an email notifying you of the incident and to change your password. No-one expects to have their personal data violated simply for buying tickets to a concert or sporting event, yet here we are.
It's an awful situation for everyone; detrimental to Ticketmaster's reputation and a downright rotten customer experience. There's one problem, though: it wasn't entirely their fault.
You see, the company utilised the services of a third-party customer support application from Inbenta Technologies. Ticketmaster UK discovered that the product contained malicious code, leading to five percent of their global customer data being compromised.
And how exactly did hackers manage to exploit this system? They manipulated a single line of JavaScript code, customized by Inbenta Technologies for Ticketmaster's requirements. According to Inbenta, the code was used on a page it was not built to accommodate, and had they known, would have identified it as a security vulnerability.
The vulnerability itself is essentially a file upload/storage library security issue, wherein just one breach can affect every site on which the same code is loaded. The code can be modified to collect and reroute personal data to the attackers, just for starters. This is a simple exploit with far-reaching damage potential, and it is something we are working on defending against with a range of in-platform training exercises for developers.
Of course, it's virtually impossible to run a business without relying on some third-party applications. However, you have no control over how they build their software, and essentially zero visibility on the security strength of their code. It becomes a trust exercise. If your third-party partner is lax in their secure coding practices, you may be opening the door to a breach in yourcompany.
So, what's the solution? Put simply: we all must do better. We must stop thinking of security as an irritating obstacle on the path of company innovation.
It is easier than you think to empower your dev team with the right tools and knowledge to embrace security, stopping bad code in its tracks. We have been pleased to see so many of the worlds largest and most well-known financial, telecommunications, retail and tech companies adopt this new approach, but it shouldnt be the sole domain of Fortune 100 companies to take steps in security education. Every company that counts developers among their staff needs to implement training to help teams code securely.
The recently released white paper I wrote in conjunction with our CTO Matias Madou, showcases the benefits of building a security culture in your organisation. We detail why it is the key to unlocking innovation, staying agile and reducing the financial impact of insecure code.
You'll find tips including:
* How to make security training relevant and engaging for developers
* How to teach developers to identify and fix their own issues
* How to help developers securely construct their own code.
I invite you to download this resource and use it to champion security in your organisation, build the skills of your team and be at the forefront of setting a higher standard of code.
We must stop thinking of security as an irritating obstacle on the path of company innovation.
It's no secret that our main mission is to make software and its development safe; crafted with security in mind from the very beginning of production. Our vision sets a new benchmark for software creation, where developers are empowered with the skills and knowledge detect vulnerable code during the writing process and fix it before it even becomes an issue.
So, with that in mind, you may think we're delighted to hear of new data breaches, cyber attacks and exploited code affecting companies all over the world - those incidents certainly highlight the need for our service in multiple verticals. The truth is, it's quite frustrating. It's clear that as an industry we are making the same mistakes time and time again, because most security education just isn't robust enough to minimise risk and stop these breaches.
The latest data breach victim is Ticketmaster. If you were among the thousands of affected customers, you'd have received an email notifying you of the incident and to change your password. No-one expects to have their personal data violated simply for buying tickets to a concert or sporting event, yet here we are.
It's an awful situation for everyone; detrimental to Ticketmaster's reputation and a downright rotten customer experience. There's one problem, though: it wasn't entirely their fault.
You see, the company utilised the services of a third-party customer support application from Inbenta Technologies. Ticketmaster UK discovered that the product contained malicious code, leading to five percent of their global customer data being compromised.
And how exactly did hackers manage to exploit this system? They manipulated a single line of JavaScript code, customized by Inbenta Technologies for Ticketmaster's requirements. According to Inbenta, the code was used on a page it was not built to accommodate, and had they known, would have identified it as a security vulnerability.
The vulnerability itself is essentially a file upload/storage library security issue, wherein just one breach can affect every site on which the same code is loaded. The code can be modified to collect and reroute personal data to the attackers, just for starters. This is a simple exploit with far-reaching damage potential, and it is something we are working on defending against with a range of in-platform training exercises for developers.
Of course, it's virtually impossible to run a business without relying on some third-party applications. However, you have no control over how they build their software, and essentially zero visibility on the security strength of their code. It becomes a trust exercise. If your third-party partner is lax in their secure coding practices, you may be opening the door to a breach in yourcompany.
So, what's the solution? Put simply: we all must do better. We must stop thinking of security as an irritating obstacle on the path of company innovation.
It is easier than you think to empower your dev team with the right tools and knowledge to embrace security, stopping bad code in its tracks. We have been pleased to see so many of the worlds largest and most well-known financial, telecommunications, retail and tech companies adopt this new approach, but it shouldnt be the sole domain of Fortune 100 companies to take steps in security education. Every company that counts developers among their staff needs to implement training to help teams code securely.
The recently released white paper I wrote in conjunction with our CTO Matias Madou, showcases the benefits of building a security culture in your organisation. We detail why it is the key to unlocking innovation, staying agile and reducing the financial impact of insecure code.
You'll find tips including:
* How to make security training relevant and engaging for developers
* How to teach developers to identify and fix their own issues
* How to help developers securely construct their own code.
I invite you to download this resource and use it to champion security in your organisation, build the skills of your team and be at the forefront of setting a higher standard of code.
We must stop thinking of security as an irritating obstacle on the path of company innovation.
Click on the link below and download the PDF of this resource.
Secure Code Warrior is here for your organization to help you secure code across the entire software development lifecycle and create a culture in which cybersecurity is top of mind. Whether you’re an AppSec Manager, Developer, CISO, or anyone involved in security, we can help your organization reduce risks associated with insecure code.
View reportBook a demo
Chief Executive Officer, Chairman, and Co-Founder
Pieter Danhieux is a globally recognized security expert, with over 12 years experience as a security consultant and 8 years as a Principal Instructor for SANS teaching offensive techniques on how to target and assess organizations, systems and individuals for security weaknesses. In 2016, he was recognized as one of the Coolest Tech people in Australia (Business Insider), awarded Cyber Security Professional of the Year (AISA - Australian Information Security Association) and holds GSE, CISSP, GCIH, GCFA, GSEC, GPEN, GWAPT, GCIA certifications.
It's no secret that our main mission is to make software and its development safe; crafted with security in mind from the very beginning of production. Our vision sets a new benchmark for software creation, where developers are empowered with the skills and knowledge detect vulnerable code during the writing process and fix it before it even becomes an issue.
So, with that in mind, you may think we're delighted to hear of new data breaches, cyber attacks and exploited code affecting companies all over the world - those incidents certainly highlight the need for our service in multiple verticals. The truth is, it's quite frustrating. It's clear that as an industry we are making the same mistakes time and time again, because most security education just isn't robust enough to minimise risk and stop these breaches.
The latest data breach victim is Ticketmaster. If you were among the thousands of affected customers, you'd have received an email notifying you of the incident and to change your password. No-one expects to have their personal data violated simply for buying tickets to a concert or sporting event, yet here we are.
It's an awful situation for everyone; detrimental to Ticketmaster's reputation and a downright rotten customer experience. There's one problem, though: it wasn't entirely their fault.
You see, the company utilised the services of a third-party customer support application from Inbenta Technologies. Ticketmaster UK discovered that the product contained malicious code, leading to five percent of their global customer data being compromised.
And how exactly did hackers manage to exploit this system? They manipulated a single line of JavaScript code, customized by Inbenta Technologies for Ticketmaster's requirements. According to Inbenta, the code was used on a page it was not built to accommodate, and had they known, would have identified it as a security vulnerability.
The vulnerability itself is essentially a file upload/storage library security issue, wherein just one breach can affect every site on which the same code is loaded. The code can be modified to collect and reroute personal data to the attackers, just for starters. This is a simple exploit with far-reaching damage potential, and it is something we are working on defending against with a range of in-platform training exercises for developers.
Of course, it's virtually impossible to run a business without relying on some third-party applications. However, you have no control over how they build their software, and essentially zero visibility on the security strength of their code. It becomes a trust exercise. If your third-party partner is lax in their secure coding practices, you may be opening the door to a breach in yourcompany.
So, what's the solution? Put simply: we all must do better. We must stop thinking of security as an irritating obstacle on the path of company innovation.
It is easier than you think to empower your dev team with the right tools and knowledge to embrace security, stopping bad code in its tracks. We have been pleased to see so many of the worlds largest and most well-known financial, telecommunications, retail and tech companies adopt this new approach, but it shouldnt be the sole domain of Fortune 100 companies to take steps in security education. Every company that counts developers among their staff needs to implement training to help teams code securely.
The recently released white paper I wrote in conjunction with our CTO Matias Madou, showcases the benefits of building a security culture in your organisation. We detail why it is the key to unlocking innovation, staying agile and reducing the financial impact of insecure code.
You'll find tips including:
* How to make security training relevant and engaging for developers
* How to teach developers to identify and fix their own issues
* How to help developers securely construct their own code.
I invite you to download this resource and use it to champion security in your organisation, build the skills of your team and be at the forefront of setting a higher standard of code.
We must stop thinking of security as an irritating obstacle on the path of company innovation.
Table of contents
Chief Executive Officer, Chairman, and Co-Founder
Secure Code Warrior is here for your organization to help you secure code across the entire software development lifecycle and create a culture in which cybersecurity is top of mind. Whether you’re an AppSec Manager, Developer, CISO, or anyone involved in security, we can help your organization reduce risks associated with insecure code.
Book a demoDownloadResources to get you started
Resources to get you started
10 Key Predictions: Secure Code Warrior on AI & Secure-by-Design’s Influence in 2025
Organizations are facing tough decisions on AI usage to support long-term productivity, sustainability, and security ROI. It’s become clear to us over the last few years that AI will never fully replace the role of the developer. From AI + developer partnerships to the increasing pressures (and confusion) around Secure-by-Design expectations, let’s take a closer look at what we can expect over the next year.
OWASP Top 10 For LLM Applications: What’s New, Changed, and How to Stay Secure
Stay ahead in securing LLM applications with the latest OWASP Top 10 updates. Discover what's new, what’s changed, and how Secure Code Warrior equips you with up-to-date learning resources to mitigate risks in Generative AI.
Trust Score Reveals the Value of Secure-by-Design Upskilling Initiatives
Our research has shown that secure code training works. Trust Score, using an algorithm drawing on more than 20 million learning data points from work by more than 250,000 learners at over 600 organizations, reveals its effectiveness in driving down vulnerabilities and how to make the initiative even more effective.
.png)
Reactive Versus Preventive Security: Prevention Is a Better Cure
The idea of bringing preventive security to legacy code and systems at the same time as newer applications can seem daunting, but a Secure-by-Design approach, enforced by upskilling developers, can apply security best practices to those systems. It’s the best chance many organizations have of improving their security postures.
Developer-driven coding.
Securely.
Contact us today and make software security an intrinsic part of your development process.
