Operations

9/22/2016
11:30 AM
Steve Zurier
Steve Zurier
Slideshows
Connect Directly
Twitter
RSS
E-Mail
50%
50%

10 Ways To Lock Down Third-Party Risk

Experts share ideas for closing potential security holes that leave organizations open to attack.
Previous
1 of 11
Next

Image Source: Pixabay

Image Source: Pixabay

Ever since the Target breach in December 2013 and the resulting fallout, many companies have been paying closer attention to third-party security.

After all, it was one of its HVAC contractors that was the weak link in that incident, not Target itself.

And even with all the stories and conference seminars around third-party security, there’s evidence that there’s still much work ahead to plug the potential holes with third parties.

A Ponemon Institute study released earlier this year found that 67 percent of companies surveyed say they do not have or are unsure if their company has an inventory of third parties. Sixty-three percent say their organizations have no centralized control over third parties and 50 percent say third-party management is simply not a priority.

T.R. Kane, cybersecurity and privacy partner at PwC, says while it will take time for companies to put their third-party programs in place, there has been some progress during 2016.

“We’re seeing third party risk management show up as one of the top three board agenda items,” Kane says. “Companies are realizing that when a breach takes place it has a negative impact on the bottom line and share price so it makes more sense to focus on third-party management as opposed to the hundreds of millions it would cost to fix a problem.”

Here is a 10-point plan for managing third-party risk based on interviews with PwC’s Kane and input from James Christiansen, vice president for information risk management at Optiv and Fred Kneip, CEO of CyberGRX. 

 

Steve Zurier has more than 30 years of journalism and publishing experience, most of the last 24 of which were spent covering networking and security technology. Steve is based in Columbia, Md. View Full Bio

Previous
1 of 11
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Shantaram
50%
50%
Shantaram,
User Rank: Ninja
9/27/2016 | 2:01:32 PM
192.168.0.1
Thanks, it was really intresting article!
Election Websites, Back-End Systems Most at Risk of Cyberattack in Midterms
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/14/2018
Intel Reveals New Spectre-Like Vulnerability
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/15/2018
Australian Teen Hacked Apple Network
Dark Reading Staff 8/17/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
The State of IT and Cybersecurity
The State of IT and Cybersecurity
IT and security are often viewed as different disciplines - and different departments. Find out what our survey data revealed, read the report today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-15504
PUBLISHED: 2018-08-18
An issue was discovered in Embedthis GoAhead before 4.0.1 and Appweb before 7.0.2. The server mishandles some HTTP request fields associated with time, which results in a NULL pointer dereference, as demonstrated by If-Modified-Since or If-Unmodified-Since with a month greater than 11.
CVE-2018-15505
PUBLISHED: 2018-08-18
An issue was discovered in Embedthis GoAhead before 4.0.1 and Appweb before 7.0.2. An HTTP POST request with a specially crafted "Host" header field may cause a NULL pointer dereference and thus cause a denial of service, as demonstrated by the lack of a trailing ']' character in an IPv6 a...
CVE-2018-15492
PUBLISHED: 2018-08-18
A vulnerability in the lservnt.exe component of Sentinel License Manager version 8.5.3.35 (fixed in 8.5.3.2403) causes UDP amplification.
CVE-2018-15494
PUBLISHED: 2018-08-18
In Dojo Toolkit before 1.14, there is unescaped string injection in dojox/Grid/DataGrid.
CVE-2018-15495
PUBLISHED: 2018-08-18
/filemanager/upload.php in Responsive FileManager before 9.13.3 allows Directory Traversal and SSRF because the url parameter is used directly in a curl_exec call, as demonstrated by a file:///etc/passwd value.