I recently did some research on the source of data breaches and in this article, I’m going to talk a bit about my current favorite source for breach information, and what I learned.
Verizon publishes the Data Breach Investigations Report annually and the latest report is the 11th edition, so they’ve had some practice. The free reports are extremely well detailed and, shockingly, they’re even entertaining to read.
The reports don’t claim to discover all data breaches. After all, not all data breaches are discovered, and those that are discovered aren’t necessarily reported.
The 2018 report covers 53,000 incidents, defined as: A security event that compromises the integrity, confidentiality or availability of an information asset.
It also covers 2,216 breaches, which are defined as: An incident that results in the confirmed disclosure — not just potential exposure — of data to an unauthorized party.
These numbers (and the screenshots I’m sharing below), do NOT include breaches involving botnets. Instead, the 43,000 successful accesses via stolen credentials associated with botnets are handled in a special insights section of the report.
Are data breaches caused mainly by insiders or outsiders?
A colleague of mine mentioned that he’d recently seen some numbers suggesting that data breaches were mainly perpetuated by insiders to an organization — but he hadn’t been able to track down the source of those figures or substantiating data. With the number of data breaches we see these days, that’s a pretty dark view of employee-employer relationships!
Here’s what the Verizon report shows in terms of who is behind the breaches:
2018 Data Breach Investigations Report, 11th Edition, Verizon, page 5
These figures are regarding those confirmed data breaches, not all security incidents. While 28% involve internal actors, the bulk of data breaches are coming from people outside the organization, finding their way in by using malware or social attacks, or by exploiting vulnerabilities created due to errors.
Who can a database administrator trust?
For those internal actors involved in data breaches, my first thought was, Well, so WHO WAS IT?
That’s answered a couple pages later. While the exact internal actors weren’t found for all of the reported data breaches, analysis was done for 277 data breaches:
2018 Data Breach Investigations Report, 11th Edition, Verizon, page 9
As much as database administrators like to focus on denying permissions to developers for production, developers were much less likely to be involved in data breaches than system admins. And who exactly are system admins? Well, I’m guessing that includes … the DBAs.
This is remarkable given that you don’t need production access to cause a data breach. It’s pretty normal practice in an enterprise to make copies of production data for use by analysts, developers, product managers, marketing professionals, and others.
Redgate’s 2018 State of Database DevOps Report, for example, found that 67% of respondents use production data in development, test, or QA Environments, and that 58% of respondents reported that production data should be masked when in use in these environments:
The 2018 State of Database DevOps, Redgate, page 12
There are good reasons that production data is spread around like this: performance is extremely difficult to predict when testing with data that doesn’t have a very similar distribution and similar size to production data, for example.
But after many years of working in IT, I know that most often this data is not modified or masked after being duplicated. These environments tend to be far less secure than production environments, and they are a very rich target for data breaches — even if it’s not the developers themselves intentionally causing the data breach.
That’s worrying, given that the rise of malware and social attacks means that all environments in an enterprise can be the source of a data breach. And perhaps a sign that more attention should be given to introducing measures to prevent such breaches.
Kendra Little is a Microsoft Certified Master, a Microsoft Data Platform MVP, and a Redgate DevOps Evangelist. You can find her online at littlekendra.com.
Also in Audit & Compliance
SQL Server 2008 and SQL Server 2008 R2 are out of extended support as of July 2019, but the end of bug fixes, security updates and ongoing support has far-reaching data privacy implications, as James ...
Also in Blog
Ahead of our attendance at IDC’s DevOps Conference in September 2019, we approached Jen Thomson, IDC’s Senior Research Director & Lead for Accelerated App Delivery Practice, to help us articul...