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.

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 and has covered networking, security, and IT as a writer and editor since 1992. Steve is based in Columbia, Md. View Full Bio
 

Recommended Reading:

Previous
1 of 11
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/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-2015-20001
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.2.0, BinaryHeap is not panic-safe. The binary heap is left in an inconsistent state when the comparison of generic elements inside sift_up or sift_down_range panics. This bug leads to a drop of zeroed memory as an arbitrary type, which can result in a memory ...
CVE-2020-36317
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, String::retain() function has a panic safety problem. It allows creation of a non-UTF-8 Rust string when the provided closure panics. This bug could result in a memory safety violation when other string APIs assume that UTF-8 encoding is used on the sam...
CVE-2020-36318
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, VecDeque::make_contiguous has a bug that pops the same element more than once under certain condition. This bug could result in a use-after-free or double free.
CVE-2021-28875
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.50.0, read_to_end() does not validate the return value from Read in an unsafe context. This bug could lead to a buffer overflow.
CVE-2021-28876
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.52.0, the Zip implementation has a panic safety issue. It calls __iterator_get_unchecked() more than once for the same index when the underlying iterator panics (in certain conditions). This bug could lead to a memory safety violation due to an unmet safety r...