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

10/26/2015
10:30 AM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail vvv
100%
0%

New Approaches to Vendor Risk Management

The key to managing partner security risk is having truly verifiable evidence.

In the legend of Troy, Greek warriors spent a significant amount of time trying to break into huge walls surrounding the city until Odysseus had a clever idea: leave a wooden Trojan horse outside and hide the soldiers inside. Today, the city of Troy is your company and the modern equivalent to the Trojan horse are your third party systems.

Organizations spend inordinate amounts of money protecting their fortresses, but they neglect the immediate risks posed by unfortunate partners. Today, organizations attempt to rein in third-party risk through on-site visits, security questionnaires, and intrusive, one-time audits. These security measures are an exercise in trust, but difficult to fully verify.  As a result, forward-leaning organizations are looking for a fresh approach to manage their security-risk environment.

If you have hundreds of vendors today, there is almost no way to know all of the security-risk issues they have. You send a questionnaire, jump on the phone, incorporate legal provisions into the contract, and pray that vendor responses are correct. The key to managing partner risk is having truly verifiable evidence. In business, the faster you are able to make an informed decision the more business value you can extract.

Source: Dr. Aleksandr Yampolskiy
Source: Dr. Aleksandr Yampolskiy

You also need to know which vendors pose less risk to your company and deserve fast-tracked assessments. As facts about third-party security risk become more readily apparent, proactive management will be needed. How do you get there? You can start by following these seven steps:

  1. Get your executive team to buy in and the general counsel to participate
  2. Separate your vendors into groups of low, medium, and high criticality.
  3. Ask for objective evidence, supporting answers that third parties presented in the questionnaire.
  4. Work with, not against your partners.
  5. Evaluate and measure vendor performance as a continuous process.
  6. Establish regular touch points and personal relations with vendors to review common risk threats
  7. Reserve the right to audit vendors.

Make the case with information

The independent security risk evidence that is now available via technologies that span big data, threat intelligence, and governance, risk, and compliance systems can help organizations make smarter decisions. When this information is accurately placed in a comparative business context, companies can begin to prioritize vendor management resources and speed up the time to remediation. With this intelligence, we can improve the maturity of our risk management and vendor management programs. But this intelligence must be in a business-friendly context. 

The bottom line: technical metrics alone will not suffice. We need to stop pretending the paperwork we are pushing around is protecting our organizations and our customers. We need stronger levels of trust based on rapid, factual, and accurate information that is completely independent from our partner relationships. 

Black Hat Europe returns to the beautiful city of Amsterdam, Netherlands November 12 & 13, 2015. Click here for more information and to register.

Dr. Aleksandr Yampolskiy is the CEO and Founder of SecurityScorecard, the leading security risk benchmarking service. In the past, he has been the head of security and compliance at Gilt Groupe, and has held lead technologist and security roles at Goldman Sachs, Oracle, and ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Microsoft Patches Wormable RCE Vulns in Remote Desktop Services
Kelly Sheridan, Staff Editor, Dark Reading,  8/13/2019
The Mainframe Is Seeing a Resurgence. Is Security Keeping Pace?
Ray Overby, Co-Founder & President at Key Resources, Inc.,  8/15/2019
GitHub Named in Capital One Breach Lawsuit
Dark Reading Staff 8/14/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-15224
PUBLISHED: 2019-08-19
The rest-client gem 1.6.13 for Ruby, as distributed on RubyGems.org, included a code-execution backdoor inserted by a third party.
CVE-2019-15225
PUBLISHED: 2019-08-19
In Envoy through 1.11.1, users may configure a route to match incoming path headers via the libstdc++ regular expression implementation. A remote attacker may send a request with a very long URI to result in a denial of service (memory consumption). This is a related issue to CVE-2019-14993.
CVE-2019-15223
PUBLISHED: 2019-08-19
An issue was discovered in the Linux kernel before 5.1.8. There is a NULL pointer dereference caused by a malicious USB device in the sound/usb/line6/driver.c driver.
CVE-2019-15211
PUBLISHED: 2019-08-19
An issue was discovered in the Linux kernel before 5.2.6. There is a use-after-free caused by a malicious USB device in the drivers/media/v4l2-core/v4l2-dev.c driver because drivers/media/radio/radio-raremono.c does not properly allocate memory.
CVE-2019-15212
PUBLISHED: 2019-08-19
An issue was discovered in the Linux kernel before 5.1.8. There is a double-free caused by a malicious USB device in the drivers/usb/misc/rio500.c driver.