06.10 Vendor Overview, Reports and Control Coverage
Read the Vendor Overview and the vendors that need attention first, run the six vendor reports on the Reports page (vendor risk heat map, overdue reassessments, expiring evidence and contracts, fourth-party and asset concentration, framework coverage and the vendor register) and export the register, record the fourth parties each vendor relies on, and record and waive each vendor's required SCF controls on its Controls tab.
Requires: Vendor Risk Management Extra
The Vendor Risk Dashboard, the six vendor reports and a vendor's Dependencies tab come with the Vendor Risk Management Extra. Without it, the dashboard and the reports aren't offered at all, and the tab shows as locked. Control coverage, meaning a vendor's Controls tab, the controls each tier requires and the Vendor Control Coverage report, also needs the Secure Controls Framework (SCF) Extra to be active, because the controls come from the Secure Controls Framework.
Why this matters
Questions about a vendor program rarely come one vendor at a time. Your CISO wants to know which vendors are in trouble this week. The audit committee wants the critical vendors and when each was last reviewed. A regulator asks which suppliers your suppliers depend on, and an auditor asks for the register as a spreadsheet before the opening meeting. Every one of those answers already sits in the register, spread over a few hundred vendor pages.
The NIST Cybersecurity Framework (CSF) 2.0 puts supplier risk under its supply chain risk management category (GV.SC), which expects you to know your suppliers, their criticality and the requirements you hold them to, and to monitor them over the relationship. ISO/IEC 27001:2022 Annex A asks the same of supplier relationships and of the ICT supply chain behind them. Three parts of the Vendor Risk Management Extra cover the program-level view. The Vendor Risk Dashboard shows where to look first. The six vendor reports answer the standing questions and export the register. Fourth parties and control coverage record what the per-vendor pages couldn't: which vendors your vendors rely on, and whether each vendor meets the Secure Controls Framework (SCF) controls you require of its tier.
Most of it counts things you can check rather than scoring them. The tier says how much a vendor matters, findings and reviews say what you found, and the Overview ranks vendors by warning signs. For users who can read every part of it, there is also each vendor's computed risk score, a single figure on SimpleRisk's own risk scale that is built from those same facts and explains each change in the vendor's Risk tab (see Using the Vendor Register). It appears in the register, in the export and in one chart on the dashboard, and nowhere for anyone who can't read what it is built from.
Before you start
- The right permissions. Every part of this article needs Allow Access to "Vendor Risk" Menu and Able to View Vendors, or a permission that includes viewing (Able to Manage Vendors or Able to Configure Vendor Risk Management). That's enough to open both pages and the Dependencies tab. Everything else depends on what else you hold:
- Able to Manage Vendors adds, edits and deletes dependencies.
- Able to Run Vendor Due Diligence adds the review figures and reports, and, together with Allow Access to "Governance" Menu, the Controls tab and the coverage figures.
- Evidence, contract and findings permissions add their own figures and columns, and Allow Access to "Asset Management" Menu adds the asset figures.
- Linking an exception as a waiver also needs Able to View Exceptions.
- The Secure Controls Framework (SCF) Extra, for control coverage. Your administrator installs it and chooses, per tier, which SCF controls a vendor must meet. Until both have happened, the Controls tab says so.
Encryption availability. In this release, dependency notes and control assessment notes 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
1. Read the Vendor Risk Dashboard
Select Reporting, then Dashboards, then the Vendor Risk Dashboard card (use the Vendor Risk filter to find it). It appears only while the Vendor Risk Management Extra is active. The page opens with a row of tiles, a chart of Vendors by tier and status, and Vendors that need attention. A user who can read the computed risk score also gets a Vendors by risk level chart.
Each tile counts something specific, and most of them open the list behind the number:
Vendors
- What it counts: Every vendor you can see, in every status
- Selecting it opens: The Vendor Register report
In offboarding
- What it counts: Vendors in Offboarding
- Selecting it opens: The register filtered to Offboarding
Reviews overdue
- What it counts: Onboarding and Active vendors whose Next Review Date has passed
- Selecting it opens: Overdue Vendor Reassessments report
Evidence expiring soon
- What it counts: Evidence items that expire within the evidence lead time your administrator set (30 days unless they changed it)
- Selecting it opens: The evidence list under Expiring Vendor Evidence and Contracts, at that window
Contracts renewing or ending
- What it counts: Contracts showing Renewal due plus contracts showing Ending soon
- Selecting it opens: Each of its two figures opens Manage Contracts filtered to that status
Open findings
- What it counts: Findings that are Open or In Progress, at any risk level
- Selecting it opens: Manage Findings
Vendors with control gaps
- What it counts: Tiered vendors, other than Terminated ones, with at least one required control marked Not met
- Selecting it opens: No list. Its Framework coverage link opens the coverage report, and Vendor register opens the register sorted by Controls not met
The evidence, contract and findings tiles count every vendor you can see, Terminated ones included, so each figure matches the list it opens. The control-gaps tile is the odd one out: it counts vendors, while the Vendor Control Coverage report it links to counts each vendor's required controls under every framework they map to. Expect different numbers there, by design.
The chart stacks each tier's vendors by status, with Untiered last, and the same figures sit in a table under it.
Vendors by risk level is a pie chart of the vendors that have a score, one slice per risk level in the colors your risk levels use, with a slice for the vendors that are Unscored because they have no tier. It is offered only to users who can read the score; for everyone else it isn't in the picker or on the page. Like every widget on the dashboard, a widget you can't read is never offered to you: your dashboard shows only the tiles and charts you may see.
2. Work the Needs attention list
Vendors that need attention lists up to ten vendors, each with its Tier and the warning signs it shows. A vendor appears when it shows at least one warning sign you're allowed to see. The list puts the vendors with the most warning signs first, then the higher tier, then, for readers of findings, the vendor with more open critical and high findings, and then the name. Terminated vendors are left out.
When more than ten vendors show a warning sign, a line under the table, Showing top {n} of {total}, says how many there are in all, next to a Vendor Register link. The rest are in the register, where sorting by a column such as Controls not met or Overdue findings brings them up.
Top tier
- Raised when: The vendor is in your highest tier (the one with the highest minimum score)
- You see it with: Any view permission
Review overdue
- Raised when: An Onboarding or Active vendor's next review date has passed
- You see it with: Able to Run Vendor Due Diligence
Unsatisfactory review
- Raised when: The latest completed review's outcome was Unsatisfactory
- You see it with: Able to Run Vendor Due Diligence
Top-risk findings
- Raised when: It has at least one open finding at the highest risk level your scoring can produce
- You see it with: A permission that reads findings
Overdue findings
- Raised when: It has at least one overdue open finding
- You see it with: A permission that reads findings
Evidence gaps
- Raised when: Its tier requires an evidence type it doesn't have
- You see it with: A permission that reads evidence
Control gaps
- Raised when: A required control is marked Not met
- You see it with: The coverage permissions in "Before you start"
A warning sign you can't see is never worked out for you, so it can't move a vendor up or down your list. Two people with different permissions can therefore see different lists, and both are right. Linked risks and their scores play no part in the ranking.
Read the list as a to-do list. A Top tier vendor with an overdue review and a top-risk finding is the call to make today; a vendor whose only sign is Top tier is simply important, and it'll sit at the bottom of the list until something else goes wrong.
3. Run the reports
Select Reporting, then Reports, and use the Vendor Risk filter to find the vendor reports. There are six, each on its own page. They appear only while the Vendor Risk Management Extra is active, and a report you don't have the permission to read isn't offered to you: its card isn't there, and its address sends you back to the Reports page. The Vendor Risk menu has no reports entry of its own.
Vendor Risk Heat Map shows Tier and review outcome as a grid with your tiers across the top (Untiered last) and the latest completed review outcome down the side: Unsatisfactory, Conditional, Satisfactory and No completed review. Each cell counts the vendors in that tier whose latest completed review had that outcome. Select a count to list the vendors behind it. The list names up to 25 of them and ends with and {n} more when there are others. Terminated vendors aren't counted. The cell to watch is your top tier crossed with No completed review: important vendors nobody has looked at.
The vendors-by-tier chart isn't a report: it's a widget on the Vendor Risk Dashboard.
Overdue Vendor Reassessments lists the Onboarding and Active vendors whose review is overdue, with the Vendor, Tier and Next Review Date. The vendor's name opens its Assessments tab.
Expiring Vendor Evidence and Contracts has two lists, each with a Window (days) box from 0 to 365. The evidence list starts at your administrator's evidence lead time, and the contracts list at the contract lead time. The contracts list counts a contract whose end date or renewal date falls in the window. It ignores notice deadlines, and the page says so: a contract whose notice deadline is close but whose renewal is months away shows as Renewal due on the Overview and on Manage Contracts, but not here. When the notice deadline is what matters to you, work from Manage Contracts.
Fourth-Party Concentration lists the vendors your other vendors depend on most, up to 50 of them. For each it shows Vendors relying on it, Top-tier vendors relying on it, and the Services they rely on it for (up to 20). Vendors with the most top-tier dependents come first. Terminated vendors are left out at both ends. With Allow Access to "Asset Management" Menu, an Asset concentration table follows: the vendors linked to the most assets and asset groups, with how many vendors rely on each.
Vendor Control Coverage rolls the control coverage of step 7 up to every framework your required controls map to. Step 9 explains it.
Vendor Register is the register as one table, 25 rows to a page by default. A link from the dashboard, such as the one from In offboarding, opens it already filtered. Filter it with Search (on the vendor's name), Status and Tier (which also offers Untiered), and select any column heading to sort by it. The vendor's name opens its page. Users who can read the computed risk score also see Risk score and Risk level at the end of the table. Risk score is a number with one decimal, and Risk level shows the level name in its color. Sorting by either one orders the vendors by score, highest first on the first click, with unscored vendors always last.
4. Export the register
Export CSV and Export XLSX sit above the register once it has loaded. You get every vendor that matches the register's current filters, not only the page you're looking at, sorted by name; the sort you chose on screen isn't carried over. The file is named after the date, for example vendor_register_2026-10-30.csv.
If the export is refused, for example because it would cover more vendors than one report can, the message appears under the register's toolbar and the page stays as it was, filters and all. Narrow the register and export again.
The columns come in groups, and a group you can't read isn't in the file at all, with no header and no empty column:
Vendor
- Columns: Name, Legal name, Status, Category, Business Owner, Team(s), Tier, Tier source, Next Review Date, Depends on, Relied on by
- Included with: Any view permission
Due diligence
- Columns: Review due state, Last completed review, Outcome
- Included with: Able to Run Vendor Due Diligence
Evidence
- Columns: Evidence gaps, Evidence expiring
- Included with: A permission that reads evidence
Contracts
- Columns: Active contracts, Next contract date
- Included with: A permission that reads contracts
Findings
- Columns: Open critical findings, Open high findings, Open medium findings, Open low findings, Overdue findings
- Included with: A permission that reads findings
Risk score
- Columns: Risk score, Risk level
- Included with: The permissions that read every source of the computed score (see Using the Vendor Register)
Assets
- Columns: Linked assets, Linked asset groups
- Included with: Allow Access to "Asset Management" Menu
Control coverage
- Columns: Required controls, Controls met, Controls partially met, Controls not met, Controls waived, Controls not assessed
- Included with: The coverage permissions, while the SCF Extra is available
Some things are never exported, whatever you hold. Contract values are in mixed currencies, so contract readers get the count of active contracts and the next renewal or end date instead. Services, notes and every other free-text field stay out too, so the file never needs the encryption key and never carries an unreadable placeholder.
The headers and the status, review state, outcome and tier source cells are written in your own language, the way the page shows them, so a register exported by a colleague who uses SimpleRisk in German reads in German. In an XLSX file the counts are numbers you can add up. A CSV cell that would start with =, +, -, @, a tab or a carriage return gets a leading apostrophe, so a spreadsheet never runs a vendor called =HYPERLINK(...) as a formula. In XLSX the cell is stored as text and shows the name exactly as typed.
The Depends on and Relied on by columns count dependencies on vendors of every status. Fourth-Party Concentration leaves Terminated vendors out, so a fourth party can show more dependents in the export than in that report.
5. Record a vendor's fourth parties
A fourth party is a vendor your vendor depends on: the cloud host behind your payroll provider, the payment processor behind your e-commerce platform. Open the vendor and choose its Dependencies tab. It holds two lists, Vendors it depends on and Vendors that rely on it, each with the other vendor's Tier, Status, the Service involved and Notes.
With Able to Manage Vendors, select Add dependency, choose the Fourth party, describe the Service involved (required, up to 255 characters) and add Notes if you like (up to 5,000 characters). Select Add dependency in the dialog to save it.
The fourth party has to be a vendor already. If it isn't listed, add it on Manage Vendors first, which needs Able to Add Vendors; a new vendor starts as a Prospect. That's on purpose. A fourth party you track is a supplier in your chain, so it gets a vendor record like any other: it shows in the register and the vendor counts, and you can tier it, review it and record findings against it if it ever matters enough.
A few rules apply:
- A vendor can't depend on itself.
- One service, one row. A second dependency on the same vendor for the same service is refused with This vendor already depends on that vendor for this service. The comparison ignores letter case and accents, so "Café hosting" and "cafe hosting" count as the same service. It also treats every emoji as equal to every other emoji, so "Hosting 🚀" and "Hosting 🔥" are duplicates too.
- At most 200 per vendor. Past that, the add is refused with A vendor can have at most 200 fourth-party dependencies. Remove one before adding another. The count includes dependencies on vendors you can't see, so under team separation you can be refused while fewer show, and be unable to remove the ones you can't see. Ask someone who can see them.
- Cycles are fine. Two vendors that depend on each other happen in real supply chains, and SimpleRisk records both.
Edit and delete a dependency on the vendor that depends, from the Vendors it depends on list; the edit can change the service and the notes, not the vendors. Vendors that rely on it is read-only and shows up to 200 vendors, with Showing the first {n} of {total} dependencies on this vendor. when there are more. Each vendor's name opens that vendor on its own Dependencies tab. Deleting either vendor deletes the dependency from both.
The tab and the register count differently. The tab lists one row per service, so a vendor that relies on this one for hosting and for backups shows twice here. The register's Relied on by and Depends on columns, and fourth-party concentration, count vendors, so the same vendor counts once there.
Dependencies on a vendor you can't see under team separation aren't listed or counted anywhere you look, including the reports.
6. Know which controls a vendor must meet
Your administrator chooses, for each tier, the SCF controls its vendors must meet; usually a handful from the Third-Party Management family, such as third-party risk assessments, contract requirements and the review of third-party services. A vendor's required controls are the ones its current tier requires. Change the vendor's tier and its list changes with it. An untiered vendor has none, and its tab says Set a tier to see its required controls.
7. Record control coverage
Open the vendor and choose its Controls tab. It appears for users who hold Able to Run Vendor Due Diligence and Allow Access to "Governance" Menu together with a view permission. There's no locked version, so if you don't see the tab, one of those is missing.
The Controls card lists the required controls with their Coverage, the Status you recorded, Assessed on, Notes and Exception. A control's coverage is one of five:
- Met, Partially met or Not met: the status you recorded.
- Waived: an approved exception covers it (step 8). A waiver beats any recorded status.
- Not assessed: nothing is recorded and nothing waives it.
Use the pencil button to edit the assessment. Set the Status (choose Not assessed to clear it), the Assessed on date and Notes of up to 20,000 characters, and select Save. Dates show as YYYY-MM-DD, like the other vendor tabs. Write down what the vendor showed you: the SOC 2 section, the contract clause, the date of the call. Coverage here is your analyst's judgement, and a judgement with no notes is hard to defend. SimpleRisk doesn't work it out from questionnaire answers.
Below the main card, two more cards can appear:
- Removed controls lists assessments of a control that no longer exists in SimpleRisk, by Control ID, each marked Control removed. The control's name is gone with it, so the ID is all that's left to show. That happens when the SCF Extra is uninstalled and reinstalled, or a control is deleted. These count nowhere. Select Clear and confirm to delete one.
- Controls this tier no longer requires lists assessments recorded while the tier required the control, each named like the controls in the main card. These assessments were recorded while the vendor's tier required the control. They count nowhere now and come back if the tier requires the control again. Clear any you no longer need.
Clear asks Clear this assessment? Its status, date, notes and any linked exception are deleted., with the control's name (or its ID, for a removed control) above the question.
An assessment that no longer records anything isn't kept. Setting Not assessed and emptying the date and the notes, or unlinking the exception from a control you never assessed, deletes the assessment, and the audit trail shows it as cleared. So a control only lands under Controls this tier no longer requires when there's something there to keep.
8. Waive a control through an exception
Sometimes a vendor won't meet a control and you've decided to live with it. SimpleRisk doesn't keep a second exception register for vendors. A waiver is a link from the vendor's control to an exception in SimpleRisk's own exceptions, which you create under Governance, Define Exceptions as a control exception for that control, and approve there as usual. Exceptions Management covers that side.
With Able to View Exceptions as well, select the link button on the control's row, choose the exception and select Link exception. The list holds the exceptions for that control that are in the open state, each marked Approved or Unapproved. When there are none it says There are no open exceptions for this control. Create one under Governance first. An exception for another control is refused.
What the link does depends on the exception:
- Approved and open: the control shows Waived, with Waived by exception {name} for users who can view exceptions.
- Not yet approved: Waiver pending approval. The control keeps its recorded status until someone approves the exception.
- Closed, deleted, or changed to another control: Linked exception does not waive this control. The link stays until you unlink it.
Two things surprise people. A waiver is organization-wide for its control: an exception belongs to the control, not to a vendor, so one approved exception can waive that control for every vendor that links it. And it still waives after its review date for as long as it stays approved and open. SimpleRisk doesn't let a waiver lapse on its own, so put the exception's review on someone's calendar and close it when it no longer applies.
Unlink exception removes the link for this vendor only, after Unlink the exception from this control for this vendor? The control is then no longer waived for this vendor. Unlinking doesn't need Able to View Exceptions, because it reveals nothing. Without that permission you see Waived or Waiver pending approval but never the exception's name, and you can't link one.
9. Read the framework rollup
Coverage is recorded against SCF controls, but your auditors probably speak NIST CSF or ISO 27001. The SCF maps each of its controls to the other frameworks installed on your instance, and Vendor Control Coverage report uses that mapping. For each active framework it shows Required controls (all vendors) and how many of them are Met, Partially met, Not met, Waived and Not assessed. A tier filter narrows it to the vendors of one tier.
Each pair of a vendor and one of its required controls counts once under every framework that control maps to. Five vendors in a tier that requires a control mapped to NIST CSF add five to NIST CSF's figure. The report covers tiered vendors you can see, other than Terminated ones. The SCF releases themselves are frameworks on your instance, so they appear in the list next to NIST and ISO. Which other frameworks appear depends on the ones your administrator installed.
10. Know who sees what
Every figure, report and register row counts only the vendors you can see. A vendor in a team you're not in contributes nothing anywhere, not even as the far end of a dependency. A section you can't read is missing from the page, not shown as zero, so a missing tile means "not yours to see", never "nothing to report".
Nothing more
- Vendor Risk Dashboard: Vendors, In offboarding, the chart and the list (Top tier only)
- Vendor reports offered: Fourth-party concentration, the vendor register's vendor columns
- Dependencies tab: Read
- Controls tab: Not shown
Able to Manage Vendors
- Vendor Risk Dashboard: As above
- Vendor reports offered: As above
- Dependencies tab: Add, edit, delete
- Controls tab: Not shown
Able to Run Vendor Due Diligence
- Vendor Risk Dashboard: Adds Reviews overdue, Evidence expiring soon, Open findings and their warning signs
- Vendor reports offered: Adds the heat map, overdue reassessments, expiring evidence and contracts, and the due diligence, evidence and findings columns
- Dependencies tab: Read
- Controls tab: With Allow Access to "Governance" Menu: record and clear, unlink waivers
An evidence, contract or findings permission
- Vendor Risk Dashboard: Adds that domain's tile and any warning signs it has
- Vendor reports offered: Adds that domain's report (expiring evidence and contracts) and columns
- Dependencies tab: Read
- Controls tab: Not shown
Allow Access to "Asset Management" Menu
- Vendor Risk Dashboard: No change
- Vendor reports offered: Adds Asset concentration and the asset columns
- Dependencies tab: Read
- Controls tab: Not shown
Due diligence plus Allow Access to "Governance" Menu
- Vendor Risk Dashboard: Adds Vendors with control gaps and its warning sign
- Vendor reports offered: Adds Vendor Control Coverage and the coverage columns
- Dependencies tab: Read
- Controls tab: Record, clear and unlink; link waivers with Able to View Exceptions
The coverage parts also need the SCF Extra to be available. While it isn't, the Controls tab and the coverage report show a note instead, the Overview has no control-gaps tile, and the register has no coverage columns. Your stored assessments are kept.
Things to know
- The SCF Extra can be busy. While it's installing or updating its controls, the tab and the report say The Secure Controls Framework (SCF) Extra is updating its controls. Control coverage is available again when it finishes. Nothing is lost; try again later.
- Big instances have a ceiling. A page or export that would cover more than 20,000 vendors you can see, or that needs more memory than the server allows, is refused as a whole with a message rather than shown in part. Narrow the register by status, tier or name; the Overview can't be narrowed, so ask your administrator.
- Numbers on the two pages can differ for honest reasons. The register's dependency counts include Terminated vendors and concentration doesn't. The contracts report ignores notice deadlines and the Overview doesn't. The control-gaps tile counts vendors and the rollup counts controls.
- Audit entries name numbers, not names. Adding, changing and removing a dependency, recording or clearing an assessment, and linking or unlinking an exception all go to the audit trail, with the vendor, control and exception IDs only.
Common pitfalls
- Reading a missing tile as zero. A user without evidence permissions sees no evidence tile, not "0 expiring". Check what someone holds before you compare screenshots.
- Waiving a control for one vendor with an exception scoped to all. Linking an approved exception waives that control for every vendor you link it to, and the exception doesn't know which vendors those are. Write the exception's justification for the vendors that actually use it.
- Leaving waivers past their review date. They keep waiving. Close the exception when the reason goes away.
- Recording "Met" with no notes. Next year's analyst, and your auditor, will want to know how you knew.
- Adding a fourth party under a slightly different name. It becomes a second vendor. Search Manage Vendors first; vendor names are unique ignoring case, but "AWS" and "Amazon Web Services" aren't the same name.
- Exporting the register and sorting it in the spreadsheet as the truth. The export is a snapshot under your permissions. A colleague with different permissions exports different columns and possibly different vendors.
Related
- Using the Vendor Register
- Vendor Intake and Tiering
- Vendor Due Diligence and Reassessment
- Vendor Evidence and Contracts
- Vendor Findings and Offboarding
- Exceptions Management
- The Secure Controls Framework (SCF) Extra
- Mapping Controls Across Frameworks
- The Vendor Risk Management Extra in the Administrator Guide