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!
High Stress Levels Impacting CISOs Physically, Mentally
Jai Vijayan, Freelance writer,  2/14/2019
Valentine's Emails Laced with Gandcrab Ransomware
Kelly Sheridan, Staff Editor, Dark Reading,  2/14/2019
Making the Case for a Cybersecurity Moon Shot
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  2/19/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
How Enterprises Are Attacking the Cybersecurity Problem
How Enterprises Are Attacking the Cybersecurity Problem
Data breach fears and the need to comply with regulations such as GDPR are two major drivers increased spending on security products and technologies. But other factors are contributing to the trend as well. Find out more about how enterprises are attacking the cybersecurity problem by reading our report today.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-8980
PUBLISHED: 2019-02-21
A memory leak in the kernel_read_file function in fs/exec.c in the Linux kernel through 4.20.11 allows attackers to cause a denial of service (memory consumption) by triggering vfs_read failures.
CVE-2019-8979
PUBLISHED: 2019-02-21
Koseven through 3.3.9, and Kohana through 3.3.6, has SQL Injection when the order_by() parameter can be controlled.
CVE-2013-7469
PUBLISHED: 2019-02-21
Seafile through 6.2.11 always uses the same Initialization Vector (IV) with Cipher Block Chaining (CBC) Mode to encrypt private data, making it easier to conduct chosen-plaintext attacks or dictionary attacks.
CVE-2018-20146
PUBLISHED: 2019-02-21
An issue was discovered in Liquidware ProfileUnity before 6.8.0 with Liquidware FlexApp before 6.8.0. A local user could obtain administrator rights, as demonstrated by use of PowerShell.
CVE-2019-5727
PUBLISHED: 2019-02-21
Splunk Web in Splunk Enterprise 6.5.x before 6.5.5, 6.4.x before 6.4.9, 6.3.x before 6.3.12, 6.2.x before 6.2.14, 6.1.x before 6.1.14, and 6.0.x before 6.0.15 and Splunk Light before 6.6.0 has Persistent XSS, aka SPL-138827.