Vendors
Vendors are the third parties your organisation depends on: cloud providers, software suppliers, contractors. For each one you record how critical it is, keep its security documents, and run an AI assessment that scores its posture and raises the risks it finds.
Find them under Risk → Vendors.
The vendor list
Each row shows the vendor's name, its tier and status, a short description, its latest assessment score out of 100 (a dash if it has not been assessed), how many risks are attached to it, and when it was last assessed (or Not assessed). A Review Due flag appears on a vendor whose next review date has passed.
Search with Search vendors..., filter by tier or status, and sort by Recently Updated, Newest First, Name (A-Z) or Name (Z-A).
Tiers
The tier says how much you rely on the vendor: Critical, High, Medium or Low. The AI weighs a vendor's gaps more heavily the higher its tier.
Statuses
| Status | Meaning |
|---|---|
| Prospect | You are considering the vendor but are not using it yet. |
| Active | You are using the vendor. |
| Under Review | The relationship is being reassessed. |
| Offboarded | You no longer use the vendor. |
Statuses are a record you keep. Changing one does not trigger anything else.
Adding a vendor
People who can make changes (owners, admins and members) see Add Vendor at the top of the list. Viewers can read vendors but not change them. The form has two tabs.
Manual
Enter the Name (required), and optionally the Website (an https link), a Description, the Tier (starts as Medium), the Status (starts as Prospect), the Primary Contact, the Security Contact and the Review Frequency (Quarterly, Semi-Annual, Annual or Biennial; it starts as Annual). Choose Create Vendor.
From Catalog
The catalogue lists vendors QuantAssure already holds compliance documents for, such as certifications and audit reports. Search it, select a vendor, tick the Compliance Documents you want to link, and choose Create Vendor. A vendor added this way is created as Medium tier and Active; change either on the edit form afterwards. Its page then shows a Platform Compliance Documents section that lists the linked documents with a link to each source. The cross beside a document unlinks it (Unlink this document?), and you can re-link it later.
A vendor's page
Select a vendor to see its page. The main column holds:
- Documents: your own uploads. Choose Upload or drop a file on the drop zone. PDF, DOCX, MD and TXT files up to 10 MB are accepted. Hover a document to delete it. These are what the AI reads, so upload the vendor's SOC 2 report, ISO certificate, penetration test summary, security policies or questionnaire answers.
- Assessment History: each assessment's date, score, rating, number of risks, status and a short summary.
- Vendor Risks: the risks attached to this vendor, with code, title, risk level, status and treatment. Each code opens the risk in the risk register.
The side column has the Overview (tier, status, contacts, website, review frequency, next review due and created date) and Linked Systems, which links to each system the vendor has access to or serves.
Review dates
The Next Review Due date is set for you from the review frequency: that long after the vendor's last completed assessment, or after it was created if it has never been assessed. It is set when you create the vendor, when you change the frequency on the edit form, and each time an assessment completes. Vendors created before this existed show the calculated date too.
Editing a vendor
Edit Vendor opens the edit form, grouped into Vendor Details, Contacts, Review Schedule, Linked Systems and Subprocessor. Choose Save Changes when done.
Turn on Subprocessor to list the vendor on your Trust centre. You then give a Processing Purpose, a Data Location, a DPA Status (Not applicable, Signed, Pending or Not Required) and the Data Categories it handles. Which subprocessors are shown publicly is controlled from Settings → Trust centre.
Deleting a vendor
Delete Vendor, in the Danger Zone, removes the vendor with all its assessments and uploaded documents. Risks it raised are kept in the register but no longer tied to the vendor. This cannot be undone.
Running an assessment
Run Assessment, at the top of a vendor's page, asks the vendor risk analyst agent to review the vendor's documents. It reads everything you have uploaded and any linked catalogue documents, works out what kind each document is (SOC 2 report, ISO certificate, penetration test, policy, questionnaire, insurance), and checks them against each other and against your organisation's context. A progress indicator shows while it runs, and you can leave the page and come back. Only one assessment runs at a time per organisation; if one is already running you see An assessment is already in progress. Assessments count towards your organisation's AI usage.
An assessment is only as good as the documents behind it. A vendor with no uploaded documents gives the AI little to go on, so upload the evidence first.
The assessment produces:
- An overall score from 0 to 100, shown in green through red by grade, and an overall rating of Low, Medium, High or Critical risk. Roughly, 80 or more is Low, 60 to 79 Medium, 40 to 59 High and below 40 Critical. The recent presence of a SOC 2 Type II report, an ISO 27001 certificate and clean penetration test results weigh most.
- A written summary.
- A set of risks, each with a likelihood, consequence and treatment.
In the history, an assessment's status reads Pending, Analyzing while the AI works, Completed or Failed. A run that fails, times out or is cancelled moves its assessment to Failed rather than leaving it on Analyzing. If a run fails, start another with Run Assessment.
What happens to the risks
Each risk the AI raises is added to the risk register as a Draft in the Third-Party category, linked to the vendor. Nothing is counted in reports or on the risk matrix until you review a risk and make it Active. When you run a new assessment:
- Drafts left over from earlier assessments are marked Superseded and hidden, so the list does not fill with duplicates.
- Risks you have already moved to Active, Under Review or Closed are left alone.
Review schedule
The Review Frequency records how often you intend to reassess the vendor. It is a reminder for your team: running an assessment is always up to you, and nothing runs on its own.
How vendors connect to the rest of QuantAssure
- Risk register. Vendor risks live in the risk register and follow its statuses and reports.
- Trust centre. Vendors marked as subprocessors can be shown on your Trust centre.
- Systems. A vendor can be linked to the systems it touches.
- Findings and compliance. Vendors are not tied to individual findings or to framework controls.