The 3 worst software security breaches of 2016 (and how to avoid them in your company)

| 2 min. (340 words)

If 2016 taught us anything about technology, it was about the damage software security breaches can cause. And it’s not just a company’s reputation that suffers. We can measure the losses of the worst software security breaches in billions of dollars.

Industries across the board from finance to government came under scrutiny from the press amid claims of fraud, leaked data and compromised private information.

What happened?

Is it that companies were just lax? Could the worst of 2016’s biggest security breaches have been prevented by more rigorous security measures? After all, it only takes one breach to bring down a company’s reputation and cause dollar values to plummet. Luckily, we can live and learn from the mistakes of others.

We can learn a lot from large companies like Sage and FACC (both of which we will cover). We’ll also take a look at Yahoo which fell victim to one of the largest software security breaches. Luckily, there are a few preventative measures that will allow your company to avoid the same pitfalls.

The largest software security breach in history (so far): Yahoo

The fake president incident: FACC

**Insider threat: Sage **


The worst software security breaches are preventable. Ensure you have solid business and security procedures in place which are followed rigorously, and make it easy for your employees to report suspicions. If the worst does happen, follow Sage’s lead and let everyone know what steps they need to take to stay protected – even after a security issue!

As mentioned in this article, an error and crash reporting software like Raygun is beneficial as an early warning system. The Raygun platform detects software errors and broken scripts that can be a sign of a security breach in your software. If you’d like to see how Raygun can make your software safer, take a free trial here.

How Raygun keeps big data safe

Mobile application development trends from 2016

Maintain visibility through the entire software build process

Rails security: dropping your code into shark infested waters!