Read a sample: 1. Meet the Vendor Review
Maya Chen’s first vendor review begins with a calendar invitation marked urgent.
The customer operations team at Northstar Outfitters wants to use a cloud service called CaseBridge to organize customer support work. The team currently tracks issues across shared inboxes and spreadsheets. Its managers hope CaseBridge will give them one place to assign cases, see their status, and coordinate responses.
The business wants the service ready for a pilot in six weeks, before a planned increase in customer inquiries. The vendor has sent a proposal and a link to a page describing its security practices. Procurement is preparing to negotiate the agreement. Maya, a new third-party risk analyst, has been asked to “make sure the vendor is secure.”
That request sounds straightforward until she tries to decide what it means.
Does “secure” mean that CaseBridge has never experienced an incident? That every employee has appropriate access? That Northstar’s customer information will remain available when needed? That the service meets every requirement Northstar might later discover? Maya cannot establish any of those things simply by reading a security page, and a review cannot promise that nothing will go wrong.
Her job is narrower and more useful: help the people making the purchase understand the relevant risks, the evidence available, the questions that remain, and any conditions they should consider before proceeding.
This chapter opens the case file you will follow throughout the book. Northstar Outfitters and CaseBridge are fictional, but the work Maya encounters is familiar to people who review real vendors. Some facts are deliberately unknown at the outset. Recognizing those unknowns is part of the exercise.
A third party is an outside organization on which a business relies for a product or service. In this case, Northstar would rely on CaseBridge to provide and operate a cloud application. Depending on how the service is used, Northstar might also rely on CaseBridge to protect information, restrict access, maintain availability, respond to incidents, and support an orderly exit.
Third-party cyber risk arises when that outside relationship could contribute to a security or technology problem for the buyer. The concern is not limited to a vendor deliberately misusing information. An employee could make a mistake, an account could be compromised, a configuration could be incorrect, or a service interruption could affect Northstar’s operations. The circumstances matter more than the label.
A third-party risk review is a structured inquiry into that relationship. It connects the proposed use of a service to potential impacts, asks for relevant information, examines the support for important claims, and communicates findings to someone with authority to act.
The review is not an inspection of every system CaseBridge owns. Maya will not see every access log, interview every employee, or test every safeguard. She may receive documents prepared by the vendor, answers to questions, and perhaps independent assurance covering some activities. Each source can contribute to an assessment, but each also has boundaries.
A useful review therefore asks two questions at the same time:
- What can the available information reasonably support?
- What remains uncertain, and does that uncertainty matter to the decision?
The second question is not a sign that Maya has failed. It is often where her judgment is most valuable.
Northstar Outfitters sells outdoor equipment and operates a customer support team. Its support agents answer questions about orders, returns, and product issues. The team wants CaseBridge to collect and organize those conversations in a cloud application accessible through a web browser.
The proposed pilot is expected to involve a small group of support agents and their manager. The business sponsor is Elena Ruiz, Northstar’s head of customer operations. Elena believes the service could reduce time spent searching for prior conversations and help managers see which cases need attention.
At the first meeting, Elena tells Maya that the pilot will use “ordinary customer support information.” She expects agents to create cases and add notes. She also wants to explore whether customer emails can be brought into the service automatically.
That is enough to begin a review, but not enough to finish scoping one. “Ordinary customer support information” might include names, email addresses, order details, attachments, or unexpected material supplied by customers. Maya does not yet know which of those will actually enter CaseBridge. She also does not know whether the proposed email connection is part of the pilot, what permissions it would require, or whether a vendor support employee could view customer cases.
Those are not findings that CaseBridge handles data poorly. They are unanswered questions about the proposed relationship.
The distinction is important. If Maya writes, “CaseBridge exposes customer data to its support staff,” she has turned a possibility into a claim without evidence. If she writes, “It is not yet known whether CaseBridge support staff can access customer cases,” she preserves the question and gives the team something specific to investigate.
The business deadline is real within the case, too. Six weeks is not an unlimited period for gathering documents, reviewing them, asking follow-up questions, negotiating terms, and arranging a pilot. But a deadline does not turn missing information into evidence. It means Maya and the other stakeholders need to decide early which questions are necessary for the intended decision and who can help answer them.
Maya starts a case file before sending the vendor a questionnaire. It is a working record, not a polished verdict. She enters only what she can attribute to…