Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Attacks/Breaches

Verizon Study Links External Hacks to Internal Mistakes

Most breaches come from outside the company, but they are often triggered by unfound errors on the inside

Does your company's greatest security risk come from inside or outside the organization? After years of debate, experts may have finally found an answer: It's a deadly combination of both.

A study published yesterday by Verizon Business offers a new look at one of security's oldest problems and arrives at a new conclusion: While most breaches are executed by external attackers, the attacks are usually facilitated by security failures that were overlooked by internal staff, often for a long period of time.

In the study, which was generated by analyzing data from more than 500 forensic investigations conducted between 2004 and 2007, Verizon reports that 73 percent of data breaches resulted from external sources. This includes breaches caused by business partners, a source of vulnerability that increased fivefold during the study. Only 18 percent of breaches were caused by insiders.

But that doesn't mean internal parties don't contribute to the problem, Verizon asserts. In fact, the study also reveals that 62 percent of data breaches can be attributed to a significant error in internal behavior. Sixty-six percent of the breaches involved data that the victim organization did not know was on the system, and 75 percent of breaches are discovered by a third party, rather than someone inside the organization.

These seemingly contradictory bits of evidence -- that most breaches are perpetrated by outsiders but facilitated by errors inside -- indicate that most security breaches are crimes of opportunity, in which a door is left open and attackers simply walk in, Verizon suggests.

In fact, the study states specifically that 83 percent of attacks resulting in breaches are "not highly difficult" for the attacker. Eighty-five percent are the result of "opportunistic attacks," rather than targeted schemes, and 87 percent of the breaches probably could have been avoided through the proper enforcement of security controls, Verizon says.

"This report clearly shows it’s not about clever or complex security protection measures," says Peter Tippett, vice president of research and intelligence for Verizon Business Security Solutions. "It really boils down to doing the basics, from planning to implementation to monitoring of the data."

The most common "errors" identified in the study are errors of omission, which account for 79 percent of the mistakes identified. "This often entailed standard security procedures or configurations which were believed to have been implemented, but in actuality were not," the study says.

A lack of knowledge about corporate data, and where it is stored, is another common element in data breaches, according to the study. In fact. 90 percent of the breaches could be attributed to one of four causes: a system that was operating without the organization's knowledge; a set of data that was stored on a particular system without the organization's knowledge; a system that had unknown access or network connections; or a system that had unknown accounts or user privileges.

"We refer to these recurring situations as 'unknown unknowns,' and they appear to be the Achilles heel in the data protection efforts of every organization -- regardless of industry, size, location, or overall security posture." The scenario in which sensitive data is stored on an unknown or unauthorized system is by far the most common, according to the report.

To mitigate these internal problems -- which often lead to external attacks -- Verizon recommends some common-sense strategies, including frequent checks to ensure that policies are carried out, securing business partner connections, and creating a data retention plan.

"Investigators concluded that nearly all breaches would likely have been prevented if basic security controls had been in place at the time of attack," the report states.

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message.

  • Verizon Business

    Tim Wilson is Editor in Chief and co-founder of Dark Reading.com, UBM Tech's online community for information security professionals. He is responsible for managing the site, assigning and editing content, and writing breaking news stories. Wilson has been recognized as one ... View Full Bio

    Comment  | 
    Print  | 
    More Insights
  • Comments
    Newest First  |  Oldest First  |  Threaded View
    Edge-DRsplash-10-edge-articles
    7 Old IT Things Every New InfoSec Pro Should Know
    Joan Goodchild, Staff Editor,  4/20/2021
    News
    Cloud-Native Businesses Struggle With Security
    Robert Lemos, Contributing Writer,  5/6/2021
    Commentary
    Defending Against Web Scraping Attacks
    Rob Simon, Principal Security Consultant at TrustedSec,  5/7/2021
    Register for Dark Reading Newsletters
    White Papers
    Video
    Cartoon
    Current Issue
    2021 Top Enterprise IT Trends
    We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
    Flash Poll
    How Enterprises are Developing Secure Applications
    How Enterprises are Developing Secure Applications
    Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
    Twitter Feed
    Dark Reading - Bug Report
    Bug Report
    Enterprise Vulnerabilities
    From DHS/US-CERT's National Vulnerability Database
    CVE-2021-31922
    PUBLISHED: 2021-05-14
    An HTTP Request Smuggling vulnerability in Pulse Secure Virtual Traffic Manager before 21.1 could allow an attacker to smuggle an HTTP request through an HTTP/2 Header. This vulnerability is resolved in 21.1, 20.3R1, 20.2R1, 20.1R2, 19.2R4, and 18.2R3.
    CVE-2021-32051
    PUBLISHED: 2021-05-14
    Hexagon G!nius Auskunftsportal before 5.0.0.0 allows SQL injection via the GiPWorkflow/Service/DownloadPublicFile id parameter.
    CVE-2021-32615
    PUBLISHED: 2021-05-13
    Piwigo 11.4.0 allows admin/user_list_backend.php order[0][dir] SQL Injection.
    CVE-2021-33026
    PUBLISHED: 2021-05-13
    The Flask-Caching extension through 1.10.1 for Flask relies on Pickle for serialization, which may lead to remote code execution or local privilege escalation. If an attacker gains access to cache storage (e.g., filesystem, Memcached, Redis, etc.), they can construct a crafted payload, poison the ca...
    CVE-2021-31876
    PUBLISHED: 2021-05-13
    Bitcoin Core 0.12.0 through 0.21.1 does not properly implement the replacement policy specified in BIP125, which makes it easier for attackers to trigger a loss of funds, or a denial of service attack against downstream projects such as Lightning network nodes. An unconfirmed child transaction with ...