06.06 Vendor Intake and Tiering
Score a vendor's inherent risk with the intake questionnaire, place it in a risk tier, and take it from Onboarding to Active. Covers the requester's side (submitting an intake) and the approver's side (approving, overriding the tier, or rejecting).
Requires: Vendor Risk Management Extra
The Onboard Vendors page and the tiers behind it come from the Vendor Risk Management Extra. Without it, Onboard Vendors shows in the menu as a locked page. The vendor list the intakes feed, Manage Vendors, is described in Managing Vendors in SimpleRisk and Using the Vendor Register.
Why this matters
Not every vendor deserves the same scrutiny. The company that prints your business cards and the company that hosts your customer database are both "vendors", and treating them alike either buries the small one in paperwork or waves the big one through. The usual answer is tiering: ask a few questions about what the vendor will touch, turn the answers into a rating of inherent risk, and let that rating decide how much diligence follows and how often you look again.
Inherent risk is the risk before anyone has checked the vendor's controls. It describes the relationship, not the vendor's quality: how sensitive the data is, how much of it there is, how deep the access goes, how much an outage would hurt. That's why the intake asks about your use of the vendor and never about the vendor's own security. The NIST Cybersecurity Framework (CSF) 2.0 expects you to understand the criticality of your suppliers before you manage their risk, and the supplier controls in ISO/IEC 27001:2022 Annex A assume you have a basis for treating suppliers differently. A recorded score, a tier and a decision are that basis.
In SimpleRisk the process has two roles. A requester describes the vendor and answers the questions. An approver reviews the proposed tier and either confirms it, changes it with a reason, or sends the intake back. Approving also makes the vendor Active. Keeping those roles apart is the point: the person who wants the vendor isn't the one who decides how risky it is.
Before you start
- The Onboard Vendors entry in the left menu. With the Extra active, Vendor Risk in the left menu holds Manage Vendors and Onboard Vendors, followed by the other pages your permissions open. The vendor dashboard and reports are under Reporting. Every user here also needs Allow Access to "Vendor Risk" Menu, without which there's no Vendor Risk menu at all. If you see Manage Vendors but not Onboard Vendors, you lack a permission to view the Extra's data.
- A requester needs Able to Manage Vendors. That permission shows the + New intake button and submits the intake. Adding a brand-new vendor through the intake also needs Able to Add Vendors.
- An approver needs Able to Approve Vendors, and a way to view vendors. Approve alone opens no page, so the approver also needs Able to View Vendors or a permission that includes it. Approving doesn't need Able to Edit Vendors. Your administrator sets this up.
- Tiers and questions that an administrator has set up. If there are none, the form tells you so. The administrator article, The Vendor Risk Management Extra, covers how they're defined.
Encryption availability. In this release, intake notes, rejection reasons and reasons for choosing another tier are stored as entered, not encrypted. They will be encrypted once SimpleRisk's built-in encryption is available; the Vendor Risk Management Extra does not use the Encrypted Database Extra. Until then, don't put secrets in these fields. After encryption arrives, saving or reading them also needs a working encryption key, and your administrator restores it if it goes missing.
Step-by-step
The requester
1. Open Onboard Vendors
Select Vendor Risk, then Onboard Vendors. The page lists Vendor intakes with the Vendor, Score, Proposed tier, Status and Requested date of each. The All statuses filter narrows the list to Submitted, Approved or Rejected intakes. A new installation says No intakes yet.
2. Start a new intake
Select + New intake. You can also reach the same form from a vendor's page with Start intake, in which case the vendor is already chosen.
Under Vendor, choose one of two options.
- Existing vendor lets you pick a vendor that's already in the register. Start typing the name and choose from the matches.
- New vendor name adds a vendor as part of the intake. Type the name, which has to be unique across the installation, and choose its Team(s) if your organization uses team separation. The new vendor starts as a Prospect. This option needs Able to Add Vendors. Without it the intake is refused with You do not have permission to add vendors. Choose an existing vendor, or ask an administrator for the Able to Add Vendors permission.
You can't do both at once, and you can't submit for a vendor that's Offboarding or Terminated. A vendor that already has an intake waiting for a decision can't have a second one: you'll see This vendor already has an intake waiting for a decision.
3. Answer the questions
Under Questions, choose one answer for each. Every question is required, and a missing answer stops the submit with Answer every question. The form shows the answers in plain words and never shows how many points each is worth. That's deliberate. A requester who can see the arithmetic can steer the result, and a tier that the requester picked isn't much of an assessment.
Answer for the relationship you actually plan, not the one you hope for. If the vendor will "only" see a test export of customer data, but the test export is the production table, the honest answer is the sensitive one. When you're torn between two answers, take the higher-risk one and explain in the notes.
Use Notes for context the approver should have: why you're engaging the vendor, which team owns the relationship, what you assumed. It's optional and holds up to 10,000 characters.
4. Submit and see what happens next
The form ends in an action bar with Cancel and Submit intake. Select Submit intake. SimpleRisk scores your answers and tells you the result: The intake was submitted. Proposed tier: High. Score: 71. Three buttons follow: View intake, Submit another intake and Back to intakes.
The proposed tier is a proposal. Nothing about the vendor's tier or status changes until an approver decides. What does change right away is the vendor's status: a Prospect moves to Onboarding as soon as an intake is submitted for it. A vendor that's already Onboarding or Active stays where it is.
You can follow the intake from Onboard Vendors. Its status reads Submitted until a decision, then Approved or Rejected. Open it to see the answers you gave, your notes and, once decided, the final tier and the approver's reason.
The approver
5. Find the intakes waiting for you
On Onboard Vendors, set the status filter to Submitted to see what's pending. Select a vendor's name to open its intake.
The intake page shows the summary (Vendor, Status, Score, Proposed tier, Requested), the Answers and the Notes. Unlike the requester, you see the Points behind each answer, written as points earned out of the best possible for that question. That makes it quick to see which answer pushed the vendor up a tier. Open vendor takes you to the vendor's page on Manage Vendors.
6. Approve
The Decision card at the bottom has a Tier list preselected to the proposed tier, a Reason box and the Reject and Approve buttons.
To accept the proposal, leave the tier alone and select Approve. The reason is optional here (Reason (optional)). Approving does three things in one step: it sets the vendor's tier, it moves an Onboarding vendor to Active, and it fills in the vendor's Next Review Date from the tier's review interval when that date is empty. An existing review date is never moved. The vendor's tier history records the change and links back to this intake.
To choose a different tier, change the Tier list. The reason becomes required (Reason (required)) and the form says A reason is required when you choose a tier other than the proposed one. Overriding is normal and nothing to apologize for. The questionnaire can't know that this vendor is the only one who can restore your payments file. Just write down why. The intake keeps the score the questionnaire computed, and the tier history shows the override. On the vendor's Tier panel the tier then reads Set by an analyst.
If an administrator deleted the proposed tier after the intake was submitted, the list starts on Choose a tier and you have to choose one and give a reason.
An intake can be approved only while the vendor is Onboarding or Active. If someone has moved the vendor on in the meantime, you'll see An intake can be approved only while the vendor is Onboarding or Active.
7. Reject
Select Reject to send the intake back. A reason is required (Enter a reason for rejecting this intake.), because the requester has to know what to fix. Rejecting changes only the intake. The vendor keeps its status, which for a new vendor means it stays in Onboarding with no tier, and its tier doesn't change. A rejection closes the intake, so the requester can submit a fresh one.
8. When two approvers act at once
If a colleague decides the same intake while you have it open, your decision is refused because the intake has already been approved or rejected, and the page refreshes to show the decision that was recorded. Nothing is overwritten, so there's nothing to repair.
From Onboarding to Active
Put together, the usual path for a vendor that isn't in the register yet is:
- The requester submits an intake with a New vendor name. The vendor is created as a Prospect and moves to Onboarding.
- SimpleRisk scores the answers and proposes a tier.
- An approver approves the proposal or picks another tier with a reason.
- The vendor becomes Active, holds a tier and, if its tier has a review interval, has a Next Review Date.
For a vendor that's already in the register, the path is the same from step 2. If it's already Active, approving an intake changes its tier and leaves it Active, which makes the intake the right way to reassess a vendor when its role changes.
Vendors that can't go through an intake, because they're Terminated, for instance, can't be given a tier either. An approver can also set a tier without an intake from the vendor's Tier panel, as described in Using the Vendor Register.
What else a tier decides
A tier is more than a label. It sets the review interval behind the Next Review Date, and your administrator can attach three more things to it: the questionnaire template due diligence sends, the evidence types a vendor must keep on file, and, when the Secure Controls Framework (SCF) Extra is in use, the Secure Controls Framework (SCF) controls the vendor must meet. Those required controls appear on the vendor's Controls tab, where analysts record whether the vendor meets each one.
All of them follow the vendor's current tier. Approve an intake into a higher tier and the vendor picks up that tier's required controls straight away, each starting as Not assessed. Move it to a lower tier and the controls that tier doesn't require drop out of its coverage figures, though any assessments already recorded are kept and come back if the tier requires those controls again. An untiered vendor has no required controls. Vendor Overview, Reports and Control Coverage covers recording them.
Who sees what
Overall score and proposed tier
- Requester (Manage): Yes
- Approver (Approve plus View): Yes
- Administrator: Yes
Answers given
- Requester (Manage): Yes
- Approver (Approve plus View): Yes
- Administrator: Yes
Points behind each answer
- Requester (Manage): No
- Approver (Approve plus View): Yes
- Administrator: Yes
Approve, reject, choose another tier
- Requester (Manage): No
- Approver (Approve plus View): Yes
- Administrator: Yes
Edit tiers and questions
- Requester (Manage): No
- Approver (Approve plus View): No
- Administrator: Yes
A user who can only view vendors can read the intake list and each intake, without the points. Visibility follows the vendor: where your administrator uses team separation, an intake for a vendor in a team you can't see doesn't exist as far as you're concerned.
Common pitfalls
- Answering to get a lower tier. It saves a week of diligence and costs you credibility with the first auditor who compares the answers with the vendor's actual access.
- Submitting a second intake while one waits. Only one can be open per vendor. Ask the approver to decide the first, or have it rejected.
- Expecting an old score to change when the rules change. The score and the answers are fixed when the intake is submitted. If your administrator tunes the questions or moves a threshold, only later intakes see it.
- Approving without checking the notes. The score doesn't read them. The answers decide the proposed tier, and the notes are where the requester says what the answers can't.
- Rejecting without a useful reason. The reason is stored with the intake and is the requester's only guide to what to fix.
- Forgetting the permissions. An approver who can't open Onboard Vendors usually has Able to Approve Vendors without Able to View Vendors, or lacks Allow Access to "Vendor Risk" Menu. A requester whose new vendor is refused is missing Able to Add Vendors.