Vendor Security Check: Match Checks, Contract Terms, and Incident Contacts to Data Sensitivity

Business & Strategy

Vendor Security Check: Match Checks, Contract Terms, and Incident Contacts to Data Sensitivity

Intermediate | 4 whiteboard pages · Task board: 5 columns (4 parent tasks, 12 subtasks)

Intermediate: Method names appear, but the whiteboard explains the key points. Use the examples as a guide and fill it in, thinking it through for your own situation.

Vendor security checks stay manageable when checking depth follows data sensitivity and the contract terms and contact chain are set in advance. It suits admin or IT staff unsure how far to verify firms or cloud services that handle payroll, customer management, or website updates. List vendors from payment records with work, data, and owner, then prepare questions on access control, backups, incident reporting, subcontracting, and end-of-contract handling. Ask about subcontracting so unknown subcontractors surface, get a deletion record and stop accounts on the end date so nothing lingers, and review your own sharing settings and user list yearly instead of trusting a big name. MoSCoW sorts the items, and a yearly review keeps checks from ending at signing. Confirm contract wording and notification duties with legal staff, experts, or current official guidance. The 4-page board runs from vendors to contacts; the task board has 5 columns, 4 parent tasks, and 12 subtasks.

0 Likes 0 Copies Author: WeProcess
vendor management security checks contracts cloud services information security
Sign up free and use this template

Once you have a free account, you can copy this template from the marketplace

Whiteboard preview

Read the whiteboard text as plain text

Vendor Security Check Board

How to use (4 pages): ① List vendors and the data you hand over (boards①–⑤) → ② Line up questions and check the pitfalls (boards⑥–⑨) → ③ Sort vendors by data sensitivity and link depth, set check depth (boards⑩–⑭) → ④ Set contract terms, yearly review, contacts (boards⑮–⑰)

1/4 List your vendors

① Purpose and Scope of the Check (start here)

  • Why you are checking e.g. Finish checking the firms that hold our customer list within this fiscal year
  • What is in scope e.g. Work handed to outside firms and the cloud services the company has contracted
  • Owner and time frame e.g. Admin Rivera leads. Write up to page 4 in one month

② Vendor List (work handed over, data handed over, owner)

Vendor name Work handed over Data handed over Internal owner
Vendor A e.g. A payroll service e.g. Monthly payroll and payslips e.g. Employee names, bank accounts, pay amounts e.g. Admin Rivera
Vendor B e.g. A customer management cloud service e.g. Customer contacts and deal records e.g. Customer names, phone numbers, emails e.g. Sales Lee
Vendor C e.g. A website production firm e.g. Site updates and the contact form e.g. Inquiry contents and the site admin account e.g. PR Patel
Vendor D e.g. An accounting cloud service e.g. Books and invoices e.g. Client names and sales records e.g. Accounting Brooks

③ Vendors (firms you hand work to)

  • People do the work. You pass them your information so they can do the job
  • e.g. A payroll service or a website production firm
  • You check with their contact person and the contract

④ Cloud services (you contract and use)

  • You borrow a system. Managing users and settings is often your side's job
  • e.g. Customer management, accounting, or email cloud services
  • You check public documents and the settings in your own admin screen

⑤ Subcontractors (firms your vendor uses)

  • No direct contract with you, so they are hard to see
  • e.g. The server company a production firm rents to host your site
  • To check, ask the vendor for a list of the firms it hands work to

2/4 Pull out items to check

⑥ Five Items to Ask the Vendors in ② (sample questions and how to check)

Sample question How to check What a good answer looks like
Access control e.g. Who can see our data, and how many people? e.g. Get the list of people with access and ask how they remove access for people who leave e.g. Only the people in charge can see it, and login needs an extra check such as an authenticator app
Backups e.g. Where are copies kept, and how often are they made? e.g. Ask for the frequency and for a record of testing a restore from a copy e.g. Copies are made daily and a restore is tested at least once a year
Incident reporting e.g. When you notice a possible leak, by when and to whom do you tell us? e.g. Check the contract clause and the vendor's contact point in writing e.g. The deadline is set in hours and the contact point is in writing
Subcontracting e.g. Do you hand our information on to other companies? e.g. Get the list of subcontractors and ask how they tell us when one is added e.g. A list exists and they tell us before adding one
End-of-contract handling e.g. What happens to the data and accounts when the contract ends? e.g. Ask the form of return, the deletion deadline, and how they report the deletion e.g. The form of return and deletion deadline are set and a deletion report is issued (for a cloud service, the public guide says when data is deleted after cancellation)

⑦ Pitfall: not knowing the subcontractors

  • What happens: e.g. A server company the vendor rents from has an incident, and no notice reaches us
  • How to check: e.g. Get the subcontractor list from the vendor in writing and set it beside the table in ②
  • How to prevent: e.g. Put 'tell us before subcontracting' in the contract (to board ⑮)
  • Our check: e.g. Vendor A has a list. Vendor C has not been asked yet

⑧ Pitfall: data and accounts remain after the end

  • What happens: e.g. A dropped cloud service still holds the customer list and an admin account
  • How to check: e.g. List the contracts ended in the past year and look in each admin screen to see whether accounts are stopped
  • How to prevent: e.g. In the end month, ask for return, deletion, and account shutdown together and get a report. For a cloud service, export the data yourself before cancelling and check in the service guide when it is deleted
  • Our check: e.g. The account of a past accounting service was still usable

⑨ Pitfall: assuming big means safe

  • What happens: e.g. A big service feels safe, so nobody checks your side's settings, such as sharing scope and permissions of people who left
  • How to check: e.g. Open the sharing settings and the user list in the service's admin screen
  • How to prevent: e.g. Write one line each for what the service protects and what you protect
  • Our check: e.g. In the customer management cloud, two people who left were still users

3/4 Sort by sensitivity

⑩ Sort the Vendors in ② by Data Sensitivity and Depth of Connection

Vertical axis: Data sensitivity (higher = more sensitive) / Horizontal axis: Depth of connection (how far they reach into your systems and accounts; right = deeper)

  • Sensitive data, shallow connection e.g. A payroll service. It receives pay data but does not enter your systems. Check the items in ⑥ in writing
  • Sensitive data, deep connection e.g. A customer management cloud service, or a production firm trusted with the site admin screen. Check deepest and always run the yearly review
  • Less sensitive data, shallow connection e.g. A print shop that gets only public material. Narrow the items and check at signing
  • Less sensitive data, deep connection e.g. A firm that maintains your equipment. The data is light, but it gets inside your company, so check access control and end-of-contract handling

⑪ Choose Among the Five Items in ⑥ with MoSCoW (sets the scope for ⑫–⑭)

Must Essential
  • e.g. The incident reporting deadline, return and deletion at the end, and removing access for people who left
Should Should do
  • e.g. The subcontractor list and advance notice when one is added
Could If possible
  • e.g. A record of testing a restore from a copy
Won't Skip this time
  • e.g. Visiting their office to check. Think about it at the next review

⑫ Sensitive data, deep connection: depth of checking

  • e.g. Ask all five items in ⑥ and get the answers in writing
  • e.g. Put all four rows of board ⑮ into the contract
  • e.g. Review once a year with the flow in board ⑯

⑬ Sensitive or deep, not both: depth of checking

  • e.g. Ask the Must and Should items in ⑪
  • e.g. Check from public documents what they can show
  • e.g. Review when you renew the contract

⑭ Less sensitive data, shallow connection: depth of checking

  • e.g. Ask only the Must items in ⑪
  • e.g. Check once at signing
  • e.g. If the data you hand over grows, sort again in ⑩

4/4 Set contracts and contacts

⑮ Contract Terms from the Items Chosen in ⑪ (sample wording, owner, how to check)

Sample wording Internal owner How to check
Incident reporting deadline e.g. When the vendor notices a possible leak, it tells our contact within a set number of hours (write the hours as a number) e.g. Admin Rivera e.g. Is the deadline written as a number and is the contact point in an attachment?
Subcontracting e.g. Before subcontracting, the vendor tells us in writing and asks the subcontractor for the same level of protection e.g. Admin Rivera e.g. Get the subcontractor list once a year
Return and deletion e.g. When the contract ends, the vendor returns the data by a set deadline, deletes its copies, and issues a report e.g. IT Nguyen e.g. Receive the report and check in the admin screen that accounts are stopped
Cooperation with reviews e.g. When we ask, the vendor answers the items in ⑥ e.g. Admin Rivera e.g. Keep the date you got the answers in the record of ⑯

⑯ Yearly Review (pitfall: checked once at signing and never again)

  1. Fix the list Bring the table in ② up to date e.g. Add the cloud service you started using and mark the firms you dropped
  2. Re-sort Review weight and connection in ⑩ e.g. The production firm now also handles the site admin screen, so move it toward deeper connection
  3. Ask again Ask the items in ⑥ at the depth set in ⑫–⑭ e.g. For firms with sensitive data and deep connection, get the answers in writing
  4. Record and fix Keep the answers and what you will fix e.g. Stop the account that was not stopped and add it to the task board

⑰ Incident Contact Chain (when a vendor notifies you)

  • Who receives the notice first e.g. Admin Rivera (Accounting Brooks if out). Keep each vendor's contact phone number from ②
  • Order of internal notice e.g. The person who got it → the president → the owner of that work. Meet within 30 minutes and hear the situation
  • Who to notify outside e.g. How to tell customers and partners, and whether a report is required, are checked in the latest official guidance. Also write the contacts of your lawyer and insurer

Task board contents

Not started 16 items

List your vendors

On page 1, write the purpose of the check and put outside firms and cloud services into one table. That table is the base for every question, sort, and contract term on later pages. Press Ctrl+F (⌘F on Mac) and type "3/4" to jump to page 3.

Scan payments

Open the accounting payment list or the bank and company card statements (last 3 months, plus contracts for annual payments) and copy the names of outside firms and cloud services into the vendor name column of board ②. You are done when the names are listed in about 15 minutes. Work and data come later.

Fill in the gaps

Fill in the rest of board ② by asking the people who deal with each firm. You are done when each row has at most one blank. Write the purpose for board ① here too.

Sort into 3 types

Read boards ③–⑤ and note beside each row in ② whether it is a vendor, a cloud service, or a subcontractor. For rows where the subcontractors are unknown, ask in the subcontracting question on board ⑥ and write the result in ⑦.

List what to check

On page 2, line up the questions and the way to verify the five items you ask vendors about, then check whether your company falls into the common pitfalls. Whatever the check finds, add it as a task.

Tailor 5 questions

Rewrite the sample questions on board ⑥ in your own words and make them a question sheet for the vendors in ②. You are done when each of the five items has at least one question.

Check the pitfalls

Write the result for each vendor in ② under "our check" on boards ⑦–⑨. For cloud services, open the user list in the admin screen and look for people who left or accounts nobody uses.

Gather answers

Stick the answers from vendors next to the table on board ⑥ as notes. For a firm that does not answer, write the contact person's name and the date you asked.

Sort by sensitivity

On page 3, sort vendors by how sensitive the data is and how deeply they connect, and decide how deep to check. The point is to spend time on the heavy ones instead of giving every vendor the same effort.

Plot on the matrix

On board ⑩, place the vendors from ② one by one as notes. If you are unsure about a vendor's data sensitivity, place it higher; if unsure about its connection, place it further right (the side that needs deeper checks).

Rank with MoSCoW

On board ⑪, sort the five items of ⑥ into Must, Should, Could, and Won't. You are done when each of the five items sits in a column and Must holds incident reporting and end-of-contract handling.

Set the depth

On boards ⑫–⑭, write what to check, in what form, and how often for each weight. You are done when the four zones of ⑩ each fall under one of the frames.

Contract & contacts

On page 4, decide what goes into contracts and turn the yearly review and the incident contact chain into something concrete. When this is done, wait in the Reviewed column of the task board until the next review.

Draft clauses

Use the sample wording on board ⑮ as material to discuss with vendors from the next contract renewal. Have legal staff or a professional check the wording before you use it.

Set review month

Decide to run the four steps of board ⑯ in the same month every year. You are done when next year's tasks are added to the task board.

Share contact list

On board ⑰, write who receives the notice, the order of internal notice, and outside contacts, then share it with everyone involved. You are done when a backup person for absences is named.

Listing 0 items

Asking vendors 0 items

Into contracts 0 items

Reviewed 0 items

← Back to templates

Preview mode Vendor Security Check: Match Checks, Contract Terms, and Incident Contacts to Data Sensitivity

Whiteboard preview

① Purpose and Scope of the Check (sta... ② Vendor List (work handed over, data... ③ Vendors (firms you hand work to) ④ Cloud services (you contract and use) ⑤ Subcontractors (firms your vendor u... ⑥ Five Items to Ask the Vendors in ② ... ⑦ Pitfall: not knowing the subcontrac... ⑧ Pitfall: data and accounts remain a... ⑨ Pitfall: assuming big means safe ⑩ Sort the Vendors in ② by Data Sensi... Sensitive data, shallow connection Sensitive data, deep connection Less sensitive data, shallow connection Less sensitive data, deep connection ⑫ Sensitive data, deep connection: de... ⑬ Sensitive or deep, not both: depth ... ⑭ Less sensitive data, shallow connec... ⑮ Contract Terms from the Items Chose... ⑯ Yearly Review (pitfall: checked onc... ⑰ Incident Contact Chain (when a vend... Vendor Security C... How to use (4 pag... Purpose and data ... How to check and ... Pitfalls and worries Findings and next... 1/4 List your vendors Ctrl+F / ⌘F : 2/4... → 2/4 2/4 Pull out items to... ↙ 3/4 Why you are checkinge.g. Finish checking the firms that hold our customer list within this fiscal year What is in scopee.g. Work handed to outside firms and the cloud services the company has contracted Owner and time framee.g. Admin Rivera leads. Write up to page 4 in one month Vendor name Work handed over Data handed over Internal owner Vendor A e.g. A payroll service e.g. Monthly payroll and payslips e.g. Employee names, bank accounts, pay amounts e.g. Admin Rivera Vendor B e.g. A customer management cloud service e.g. Customer contacts and deal records e.g. Customer names, phone numbers, emails e.g. Sales Lee Vendor C e.g. A website production firm e.g. Site updates and the contact form e.g. Inquiry contents and the site admin account e.g. PR Patel Vendor D e.g. An accounting cloud service e.g. Books and invoices e.g. Client names and sales records e.g. Accounting Brooks People do the work. You pass them your information so they can do the job e.g. A payroll service or a website production firm You check with their contact person and the contract You borrow a system. Managing users and settings is often your side's job e.g. Customer management, accounting, or email cloud services You check public documents and the settings in your own admin screen No direct contract with you, so they are hard to see e.g. The server company a production firm rents to host your site To check, ask the vendor for a list of the firms it hands work to Sample question How to check What a good answe... Access control e.g. Who can see our data, and how many people? e.g. Get the list of people with access and ask how they remove access for people who leave e.g. Only the people in charge can see it, and login needs an extra check such as an authenticator app Backups e.g. Where are copies kept, and how often are they made? e.g. Ask for the frequency and for a record of testing a restore from a copy e.g. Copies are made daily and a restore is tested at least once a year Incident reporting e.g. When you notice a possible leak, by when and to whom do you tell us? e.g. Check the contract clause and the vendor's contact point in writing e.g. The deadline is set in hours and the contact point is in writing Subcontracting e.g. Do you hand our information on to other companies? e.g. Get the list of subcontractors and ask how they tell us when one is added e.g. A list exists and they tell us before adding one End-of-contract h... e.g. What happens to the data and accounts when the contract ends? e.g. Ask the form of return, the deletion deadline, and how they report the deletion e.g. The form of return and deletion deadline are set and a deletion report is issued (for a cloud service, the public guide says when data is deleted after cancellation) What happens: e.g. A server company the vendor rents from has an incident, and no notice reaches us How to check: e.g. Get the subcontractor list from the vendor in writing and set it beside the table in ② How to prevent: e.g. Put 'tell us before subcontracting' in the contract (to board ⑮) Our check: e.g. Vendor A has a list. Vendor C has not been asked yet What happens: e.g. A dropped cloud service still holds the customer list and an admin account How to check: e.g. List the contracts ended in the past year and look in each admin screen to see whether accounts are stopped How to prevent: e.g. In the end month, ask for return, deletion, and account shutdown together and get a report. For a cloud service, export the data yourself before cancelling and check Our check: e.g. The account of a past accounting service was still usable What happens: e.g. A big service feels safe, so nobody checks your side's settings, such as sharing scope and permissions of people who left How to check: e.g. Open the sharing settings and the user list in the service's admin screen How to prevent: e.g. Write one line each for what the service protects and what you protect Our check: e.g. In the customer management cloud, two people who left were still users 3/4 Sort by sensitivity → 4/4 4/4 Set contracts and... Vertical axis: Da... e.g. A payroll service. It receives pay data but does not enter your systems. Check the items in ⑥ in writing e.g. A customer management cloud service, or a production firm trusted with the site admin screen. Check deepest and always run the yearly review e.g. A print shop that gets only public material. Narrow the items and check at signing e.g. A firm that maintains your equipment. The data is light, but it gets inside your company, so check access control and end-of-contract handling ⑪ Choose Among th... MustEssential e.g. The incident reporting deadline, return and deletion at the end, and removing access for people who left ShouldShould do e.g. The subcontractor list and advance notice when one is added CouldIf possible e.g. A record of testing a restore from a copy Won'tSkip this time e.g. Visiting their office to check. Think about it at the next review e.g. Ask all five items in ⑥ and get the answers in writing e.g. Put all four rows of board ⑮ into the contract e.g. Review once a year with the flow in board ⑯ e.g. Ask the Must and Should items in ⑪ e.g. Check from public documents what they can show e.g. Review when you renew the contract e.g. Ask only the Must items in ⑪ e.g. Check once at signing e.g. If the data you hand over grows, sort again in ⑩ Sample wording Internal owner How to check Incident reportin... e.g. When the vendor notices a possible leak, it tells our contact within a set number of hours (write the hours as a number) e.g. Admin Rivera e.g. Is the deadline written as a number and is the contact point in an attachment? Subcontracting e.g. Before subcontracting, the vendor tells us in writing and asks the subcontractor for the same level of protection e.g. Admin Rivera e.g. Get the subcontractor list once a year Return and deletion e.g. When the contract ends, the vendor returns the data by a set deadline, deletes its copies, and issues a report e.g. IT Nguyen e.g. Receive the report and check in the admin screen that accounts are stopped Cooperation with ... e.g. When we ask, the vendor answers the items in ⑥ e.g. Admin Rivera e.g. Keep the date you got the answers in the record of ⑯ Fix the listBring the table in ② up to datee.g. Add the cloud service you started using and mark the firms you dropped Re-sortReview weight and connection in ⑩e.g. The production firm now also handles the site admin screen, so move it toward deeper connection Ask againAsk the items in ⑥ at the depth set in ⑫–⑭e.g. For firms with sensitive data and deep connection, get the answers in writing Record and fixKeep the answers and what you will fixe.g. Stop the account that was not stopped and add it to the task board Who receives the notice firste.g. Admin Rivera (Accounting Brooks if out). Keep each vendor's contact phone number from ② Order of internal noticee.g. The person who got it → the president → the owner of that work. Meet within 30 minutes and hear the situation Who to notify outsidee.g. How to tell customers and partners, and whether a report is required, are checked in the latest official guidance. Also write the contacts of your lawyer and insurer → 2/4 Pull out items to... ↙ 3/4 Sort by sensitivity → 4/4 Set contracts and...
100%

Drag to move, scroll to zoom