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.


01:52 AM
Connect Directly

Marrying IT Risk Management With Enterprise Procurement

Third parties represent a big chunk of data breaches, and experts say the only way to address the risk is to get IT risk managers working with vendor management executives

Enterprises have increasingly found that their vendors and other third parties are putting shared information at risk, but the disconnect between procurement professionals and IT risk managers has made it difficult to address information security risks during the vendor contract process.

What's more, the volume of vendor contracts in the enterprise would make it prohibitively expensive to simply put all vendors on the hook for the same information security requirements. That is why many IT risk management professionals advocate for better integrating supply-chain information risk management into the vendor management process.

"The challenge for those very large organizations is in dealing with very large numbers of suppliers who can't be dealt with individually, and where, for cost reasons, you can't apply the same rigorous requirements on every contract," says Michael de Crespigny, CEO of the Information Security Forum (ISF). "Otherwise you end up imposing a lot of costs to acquire because those costs ultimately get passed back to the acquirer by the supplier."

Last week, the ISF released a new report on this challenge experienced by its members, "Securing the Supply Chain," alongside a new process called the Supply Chain Information Risk Assurance Process (SCIRAP). SCIRAP is meant to help organizations better prioritize information risks within the supply chain in a way that makes sense for business stakeholders. The development of the process was driven by mounting statistics and anecdotal evidence within individual organizations of the consequences that stem from ignoring supply-chain information risk management.

For example, the Ponemon Institute reported in 2012 that 42 percent of breaches are the result of third-party mistakes. According to Larry Ponemon, founder of Ponemon Institute, the cyberunderworld has definitely taken notice of the deficiencies in security at the third-party vendors that service high-value enterprises being targeted by cybercriminals.

[How well do you normalize data for risk management? See Does Your Security Data Mesh With Risk Metrics?.]

"A lot of the bad guys have realized that sometimes the easiest way to get inside of a big company, like a large bank or pharmaceutical agency, is to basically identify subcontractors and vendors that have a link to the IT infrastructure or information," Ponemon says. "It's a lot easier to hack and break into the vendor than it is to break into the more sophisticated company with a better security posture."

However, Ponemon echoed de Crespigny's observations about the sheer problems of scale in managing vendors at large enterprises. As a point of example, he related a case study he did with a large pharmaceutical company that worked with 14,000 vendors, 11,000 of which captured data owned by the firm that was considered sensitive or confidential. And those are just numbers: Each one of them represents complex interactions, some of them governed with only loose relationships between the vendor and the contact within the enterprise.

"When a lot of organizations enter into an agreement, it's a handshake, and maybe it's legal because you've actually signed a contract, but there's really no testing or vetting in place that's meaningful," Ponemon says.

According to de Crespigny, ISF worked with its members to codify a process by which acquirers could implement mechanisms to identify the most risky suppliers and address risks by a rational prioritization. At its foundation, the process identifies a number of factors about the information handled by suppliers that organizations should take into account, such as whether the organization is handling personally identifiable information, intellectual property, or key information about how the business runs.

"Around those we came up with a method that helps them think about how they follow the information on a contract-by-contract basis and identifying individual contracts they should be focusing on to impose particular information security requirements," he says, explaining that it boils down to establishing within the supply chain the risk management fundamentals of assessing risks so that it's easiest to address the biggest risks first. "What you need to do is to do it according to where the risk lies so you get really deep assurance where you need it, and you impose very light requirements where the risk and the consequence is not so great." According to Ponemon, not only is it important to flag riskier vendors by the type of shared information they are entrusted with, but also by their geographic location.

"Culturally, there are different countries with different sensibilities about security and privacy and you need to take that into account," he warns. "Also important is the ability to use the ability to use the in-country legal system in the event that you do have an issue."

Equally important to identifying the risky vendors, though, is working with procurement to mitigate the risks before purchases are made, de Crespigny says.

"What enterprises are finding is that it's very difficult to agree on security requirements and purchase contracts -- they're looking for a way to make that easier," he says, explaining the key is in "integrating that in the vendor management or procurement processes that are already in place. Information security needs to work with procurement. They can't come and bolt this on after the event." Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Ericka Chickowski specializes in coverage of information technology and business innovation. She has focused on information security for the better part of a decade and regularly writes about the security industry as a contributor to Dark Reading.  View Full Bio

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
What the FedEx Logo Taught Me About Cybersecurity
Matt Shea, Head of Federal @ MixMode,  6/4/2021
A View From Inside a Deception
Sara Peters, Senior Editor at Dark Reading,  6/2/2021
Register for Dark Reading Newsletters
White Papers
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
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
PUBLISHED: 2021-06-13
The package studio-42/elfinder before 2.1.58 are vulnerable to Remote Code Execution (RCE) via execution of PHP code in a .phar file. NOTE: This only applies if the server parses .phar files as PHP.
PUBLISHED: 2021-06-12
Receita Federal IRPF 2021 1.7 allows a man-in-the-middle attack against the update feature.
PUBLISHED: 2021-06-12
In Apache PDFBox, a carefully crafted PDF file can trigger an OutOfMemory-Exception while loading the file. This issue affects Apache PDFBox version 2.0.23 and prior 2.0.x versions.
PUBLISHED: 2021-06-12
In Apache PDFBox, a carefully crafted PDF file can trigger an infinite loop while loading the file. This issue affects Apache PDFBox version 2.0.23 and prior 2.0.x versions.
PUBLISHED: 2021-06-12
It was discovered that read_file() in apport/hookutils.py would follow symbolic links or open FIFOs. When this function is used by the openjdk-16 package apport hooks, it could expose private data to other local users.