How to Use Vendor Analysis (AI)

How to Use Vendor Analysis (AI)

Overview

Vendor Analysis is an AI-generated briefing on a vendor, built by ZIN from publicly available information about the vendor's domain. It is background research — useful before onboarding, or as context when reading a questionnaire. It is not drawn from the vendor's own answers and it does not change the vendor's risk score.


Prerequisites

  • A cloud (SaaS) deployment. The tab is not available on on-premises installations.
  • The vendor:add permission, which is what the analysis checks. View-only access to vendors is not enough.
  • A vendor with a company domain. The analysis is keyed on the domain.

Opening Vendor Analysis

Navigation: Sidebar → Vendors → [select a vendor] → Vendor Analysis

  1. Click Vendors in the sidebar.
  2. Click the vendor you want to research.
  3. Open the Vendor Analysis tab. It is marked with the ZIN icon.

The analysis starts as soon as the tab opens. There is nothing to click.


While It Is Running

An AI Analysis in Progress card steps through what it is doing:

  1. Analyzing vendor financial stability and business continuity.
  2. Evaluating security posture and incident history.
  3. Assessing data privacy compliance and third-party dependencies.
  4. Identifying key strengths, risks, and market position.
  5. Analyzing technology stack and generating recommendations.
  6. Compiling comprehensive vendor analysis report.

Leave the tab open until the report appears. A first-time analysis is allowed up to five minutes before it gives up.

How fresh the report is

A finished analysis is kept for 30 days per domain. Opening the tab again within that time shows the stored report almost immediately instead of researching the vendor again. After 30 days the next visit generates a new one.

There is no refresh or re-run button. You cannot force a new analysis from this tab.


What the Report Contains

The report opens with a note: The following content has been generated using ZIN. Please independently verify the information before making any decisions based on it. Take that seriously — this is research material, not an audited finding.

Each section below appears only if the analysis returned something for it, so a low-profile vendor shows fewer of them.

Business and risk sections

SectionWhat it covers
Financial StabilityThe vendor's financial standing
Business ContinuityTheir resilience and continuity position
Incident HistoryA summary of past incidents affecting the vendor
Cyber Attacks & IncidentsIndividual incidents, each with a date, a description, an Impact note and a View Source link to the original reporting
Data Privacy ComplianceTheir data privacy and regulatory position
Third Party DependenciesWho the vendor themselves depends on
Key StrengthsWhat the vendor does well
Key RisksWhat to be cautious about
Market PositionWhere they sit in their market
Security PostureTheir overall security maturity
RecommendationsSuggested next steps

Technical cards

When the analysis also returns technical observations about the vendor's domain, a row of cards appears above the business sections. Any of these may be missing.

CardWhat it shows
Security ScoreAn overall grade for the domain
SSL RatingThe grade of the domain's SSL configuration
Exposed ServicesServices found reachable from the internet
Security HeadersThe status of the site's security headers, with Security Headers Details listing missing and present headers
VulnerabilitiesKnown vulnerabilities, each with a severity
Exposed EndpointsEndpoints found exposed
DNS SecuritySPF, DMARC and DKIM status, with the records where found
SSL CertificateRating, Issuer, Subject, Valid From, Valid Until, Days Until Expiry, Status and Cipher Suite
Domain InformationIP address, DNS records and domain age

These cards are a quick outside-in snapshot. For continuous external monitoring with findings you can turn into risks, use the Digital Risk tab. See How to Monitor Digital Risk (DRM).


How to Use It

  • Before onboarding — read Key Risks and Incident History alongside the vendor's questionnaire response.
  • During assessment review — if the analysis reports an incident the vendor did not disclose, raise it as a comment on the relevant question.
  • For risk context — Third Party Dependencies is a useful prompt for fourth-party risk questions.

Vendor Analysis is read-only. It does not create risks, it cannot be edited, and there is no export or download button. Anything you decide to track should be added as a risk on the vendor's Manage Risk tab. See How to Manage the Vendor Risk Lifecycle.


Troubleshooting

The Vendor Analysis tab shows an access-denied screen → Vendor Analysis is not available on on-premises installations.

The tab stays blank and the analysis never starts → The analysis runs against the vendor's company domain. Check on the Profile tab that the vendor has one.

The analysis fails or a colleague cannot run it → Running it needs the vendor:add permission. Someone with view-only access to vendors cannot run it.

The analysis is taking a long time → A first-time analysis can take up to five minutes. If it ends without a report, reload the page and open the tab again; a report that finished in the meantime is shown straight away.

The report is very thin or only shows the note at the top → The AI works from public information. Small or privately held vendors, and vendors with little web presence, produce less material, and sections with nothing to say are hidden.

The technical cards are missing → They only appear when the analysis returned technical observations for the domain. Their absence does not mean the vendor has no exposure; check the Digital Risk tab.

The report looks out of date → Reports are reused for 30 days and cannot be regenerated on demand. A new one is produced the first time the tab is opened after that.

Something in the report looks wrong → Follow the View Source link where one is given, and verify independently before making a decision.


Need more help? Contact support@zeron.one

    • Related Articles

    • Vendor Pulse: Roles & Permissions Reference

      Overview Access to Vendor Pulse is controlled by permission scopes — strings such as vendor:view. Each section of the product checks for its own scope, and a user who lacks it sees an "Unauthorized" screen instead of the page. This page covers Vendor ...
    • Getting Started with Vendor Pulse

      Overview Vendor Pulse is Zeron's third-party risk management product. You add the vendors you work with, send them assessment questionnaires, review what comes back, and track the risks you find through to closure. This guide takes you from your ...
    • How to Review Vendor Risk Scores

      Overview Vendor Pulse shows vendor risk in four places, each answering a different question: Where Question it answers Vendors list Which of my vendors score highest? Profile tab on a vendor How risky is this vendor overall? Manage Risk tab on a ...
    • Troubleshooting Common Issues in Vendor Pulse

      Overview Most "I can't see this" or "this won't save" problems in Vendor Pulse come down to one of four things: a missing permission scope, a field that has not been filled in on the vendor, a file that does not match its template, or a vendor-side ...
    • Vendor Pulse: Frequently Asked Questions (FAQ)

      Overview Answers to the questions we hear most often about Vendor Pulse, Zeron's third-party risk management (TPRM) product. Prerequisites A Vendor Pulse account For anything involving permissions, an administrator who can change your group Getting ...