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

1/18/2017
01:45 PM
Kelly Sheridan
Kelly Sheridan
Slideshows
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail

7 Common Reasons Companies Get Hacked

Many breaches stem from the same root causes. What are the most common security problems leaving companies vulnerable?
2 of 8

Failure to check code before it's deployed
Certain risks will stay strong unless businesses change their behavior, says Kelley. Injections, which she explains is a popular vector of attack, have been a known vulnerability type for fifteen years. They will continue to pose a threat to businesses in 2017.
With injections, the problem isn't coding, she explains, but a lack of understanding among developers on how to validate input. They need to understand what the vulnerabilities are, code robust software, and test it before deployment.
By testing code, businesses can remove vulnerabilities before deploying apps and software, says Kelley. IT and security pros can help developers by providing education and giving them tools to establish apps before they're launched.
(Image: ESB Professional via Shutterstock)

Failure to check code before it's deployed

Certain risks will stay strong unless businesses change their behavior, says Kelley. Injections, which she explains is a popular vector of attack, have been a known vulnerability type for fifteen years. They will continue to pose a threat to businesses in 2017.

With injections, the problem isn't coding, she explains, but a lack of understanding among developers on how to validate input. They need to understand what the vulnerabilities are, code robust software, and test it before deployment.

By testing code, businesses can remove vulnerabilities before deploying apps and software, says Kelley. IT and security pros can help developers by providing education and giving them tools to establish apps before they're launched.

(Image: ESB Professional via Shutterstock)

2 of 8
Comment  | 
Print  | 
Comments
Newest First  |  Oldest First  |  Threaded View
VesnaE29
50%
50%
VesnaE29,
User Rank: Apprentice
1/28/2017 | 10:10:34 PM
Reasons why companies get hacked
Here is an admission of guilt - I used to hack when i was in my 20s and when I thought it was fun slipping trojans into peoples emails, running port scans and checking for open telnet ports.  It was kind of, well, fun and exhilareting to do something others didn't know how to do.  What that makes you realise is that people are well, lazy when it comes to securing their data.  People fail to realise what their data is worth to someone else, period.  And to be honest here, social engineering never, ever seems to fail.  You can have 10 firewalls sitting around your data and have a DMZ inside the DMZ, but all it takes is for a person to off handedly mention an IP address you can use, or a password for a device that allows you to get onto another advice and then get to that dbase that holds the information you want to access.  The way I see it, educating people is the ONLY way to go.  Teach people how to write good codes. Teach them how to recognise corrupt codes. Teach them to keep their egos in check and not just broadcast information about secure data to others, because that exposes them to social engineering risks.  Education and more education is the key.  I don't think it will ever stop hacking and cyber attacks because there are a lot of curious people out there, but at least it will minimise the damage when data security breaches and thefts occur.   
Redhat62!
0%
100%
Redhat62!,
User Rank: Apprentice
1/27/2017 | 12:45:19 PM
Password? Really?
What evidence exists that default non-unique, or weak passwords are a common reason?
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
1/26/2017 | 11:23:04 AM
Re: Company Hack
@kbannan: Interesting point, considering that German and Russian government entities have reportedly gone back to typewriters in some instances to increase data security on particularly sensitive matters.

What this comes down to is M&M security (hard on the outside, soft in the middle) vs. holistic security throughout.  The locks on my office door are probably easy to bypass for someone wilful enough.  But the lock on my office safe presents a new and harder challenge.  If I don't have that safe or don't use that safe, however, then a bad guy just needs to get past my office door.

The same principle applies equally among both physical security and cyber security, of course.
Navrit
50%
50%
Navrit,
User Rank: Apprentice
1/25/2017 | 6:02:08 AM
Re: Missing #8: Being a target
This article is d 'Une grande importance Parce Que pour moi la sécurité de nos Données is a première et essentielle commentaire réussir in the sauvegarde de nos informations et d' eviter tout tracas et perte de Données.  
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
1/24/2017 | 8:30:40 AM
Missing #8: Being a target
While these are great examples of *how* a company can get hacked, one of the biggest *whys* in my experience -- and perhaps a more powerful "security" flaw than any of those listed here -- is being a big target in the first place.

Consider Sony, which sued a 13-year-old hacker for modifying his PlayStation.  In the wake of the PR disaster that followed, the company and its PlayStation Network suffered countless mega-hacks.  In choosing to listen to the legal department without properly taking into account any counterbalancing viewpoints erring on the side of risk management, Sony may as well have painted a big red target on its back and announced to the world, "Open for hacking!"

Less notoriously, consider the University of Virginia hack a couple years ago that was traced back to Chinese operatives.  The only information, apparently, that the hackers wanted was in relation to two particular employees.  Employing these two high-interest individuals was enough to bring U-Va. within the crosshairs of nation-state hackers.

Flaws are flaws.  Everybody has security flaws.  But there is something to the idea of security by obscurity.
kbannan100
50%
50%
kbannan100,
User Rank: Moderator
1/23/2017 | 11:45:00 PM
Re: Company Hack
Agree! And when people do something silly like not changing passwords, leaving ports open or not setting expectations of users the problem is only compounded. There was a recent Ponemon study, for instance, that found 62 percent of respondents were pessimistic about their ability to prevent the loss of data contained in printer mass storage and/or printed hard copy documents. They gave reasons for their feelings. You can read the rest of the blog here. It's a bitly: /2cFfLM2

--Karen Bannan for IDG and HP
kevinmn
50%
50%
kevinmn,
User Rank: Apprentice
1/18/2017 | 8:58:57 PM
Company Hack
well! in my point of view, there are many reasons that a company may be hacked. It's a long war between companies and hackers. When you look at why people are still getting hacked or breached, I think a big contributor to that is either not knowing if you were patched or if you were patched and you were secure at one point, but something happened in operations that caused you not to be patched again
97% of Americans Can't Ace a Basic Security Test
Steve Zurier, Contributing Writer,  5/20/2019
How Security Vendors Can Address the Cybersecurity Talent Shortage
Rob Rashotte, VP of Global Training and Technical Field Enablement at Fortinet,  5/24/2019
TeamViewer Admits Breach from 2016
Dark Reading Staff 5/20/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Building and Managing an IT Security Operations Program
As cyber threats grow, many organizations are building security operations centers (SOCs) to improve their defenses. In this Tech Digest you will learn tips on how to get the most out of a SOC in your organization - and what to do if you can't afford to build one.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-7068
PUBLISHED: 2019-05-24
Adobe Acrobat and Reader versions 2019.010.20069 and earlier, 2019.010.20069 and earlier, 2017.011.30113 and earlier version, and 2015.006.30464 and earlier have an use after free vulnerability. Successful exploitation could lead to arbitrary code execution .
CVE-2019-7069
PUBLISHED: 2019-05-24
Adobe Acrobat and Reader versions 2019.010.20069 and earlier, 2019.010.20069 and earlier, 2017.011.30113 and earlier version, and 2015.006.30464 and earlier have a type confusion vulnerability. Successful exploitation could lead to arbitrary code execution .
CVE-2019-7070
PUBLISHED: 2019-05-24
Adobe Acrobat and Reader versions 2019.010.20069 and earlier, 2019.010.20069 and earlier, 2017.011.30113 and earlier version, and 2015.006.30464 and earlier have an use after free vulnerability. Successful exploitation could lead to arbitrary code execution .
CVE-2019-7071
PUBLISHED: 2019-05-24
Adobe Acrobat and Reader versions 2019.010.20069 and earlier, 2019.010.20069 and earlier, 2017.011.30113 and earlier version, and 2015.006.30464 and earlier have an out-of-bounds read vulnerability. Successful exploitation could lead to information disclosure.
CVE-2019-7072
PUBLISHED: 2019-05-24
Adobe Acrobat and Reader versions 2019.010.20069 and earlier, 2019.010.20069 and earlier, 2017.011.30113 and earlier version, and 2015.006.30464 and earlier have an use after free vulnerability. Successful exploitation could lead to arbitrary code execution .