Private AI for vendor risk assessment
A vendor risk assessment lists every third party with access to your systems or data, what each one can reach, and where your controls around them are weakest. Draft it with a public AI chat service and you hand that list to one more unvetted third party. Running the drafting model yourself, on hardware whose host you have assessed like any other processor, avoids that.
What this work actually involves
Security and procurement teams write vendor questionnaires for two audiences: vendors filling them out, and internal reviewers reading the responses. Both directions are drafting-heavy. A new vendor questionnaire needs to be tailored to what the vendor actually does (a payment processor gets different questions than a marketing analytics tool), and a completed questionnaire needs to be read against an internal risk checklist to flag gaps, contradictions, or answers that don't match what the vendor's own documentation says elsewhere. Doing this by hand for every vendor in a company's stack is slow, which is why teams reach for an AI assistant.
The risk decision itself, whether a given vendor's answers are good enough to proceed, should stay with a person who understands the company's actual risk tolerance. What a model helps with is getting from a blank questionnaire to a complete draft, and from a completed questionnaire to a structured summary of what to look at closely.
Why the vendor list itself is sensitive
The list of vendors a company relies on, and what each one can access, is close to a map of where a breach would start. Adding "and here's where I think our own controls are weak" (which is the point of a risk assessment) turns that list into a document that would help an attacker planning a supply-chain compromise. Paste it into a cloud AI tool's chat window and it now sits in that vendor's infrastructure and chat history.
One version of this problem deserves its own mention: assessing whether to trust a cloud AI vendor is itself a common reason to write a vendor risk assessment. Running that evaluation through a different cloud AI vendor's public tool means describing the first vendor's weaknesses to a second, equally unvetted party, which defeats much of the point. For the compliance angle, GDPR and the EU AI Act on dedicated hardware covers where regulatory obligations meet vendor and processor choices, and the private ChatGPT page covers the broader pattern of internal teams routing sensitive work through unsanctioned tools.
How to set this up privately
A general-purpose model with retrieval over your existing risk framework (past assessments, your standard questionnaire template, internal policy docs) can draft a tailored questionnaire for a new vendor and summarize a completed one against your criteria, using the retrieval-augmented pattern described in the guide to on-premise RAG for internal documents. The task doesn't need a specialized model; a mid-sized open-weight model handles structured document generation and summarization well. The value is in keeping the vendor list and the risk findings out of shared AI services.
If the model runs on rented hardware, the host belongs in the assessment too. On GPUwerk that is one dedicated machine under an Article 28 DPA, with GPUwerk keeping infrastructure admin access but not accessing workload content; assess it with the same questionnaire you use for everyone else.
The workload is low-volume and bursty: active during vendor onboarding or an annual review cycle, idle otherwise, which suits on-demand pricing. A single Spark at $0.79/hour covers it, and the private LLM hosting page covers running one machine across several internal use cases instead of separate infrastructure for each.
FAQ
What exactly is sensitive about a vendor risk assessment?
The full list of who you rely on, what each vendor can access, and where your own security gaps are, since a risk assessment exists specifically to identify weak points. That combination is close to a roadmap of where an attacker would look first, which is not something most companies want sitting in a third party's chat history.
Can an AI model actually assess vendor risk, or just fill out forms?
It's stronger at the drafting side: generating a questionnaire tailored to a vendor's role, summarizing a vendor's response against your internal checklist, or flagging when an answer contradicts something said elsewhere in the same document. It shouldn't be the sole basis for a risk decision; a security or procurement lead still makes the call.
Does this apply to assessing AI vendors specifically?
Yes, and there's a specific irony worth naming: if you're evaluating whether to trust a cloud AI vendor with sensitive workloads, running that evaluation through a different cloud AI vendor's chat tool means trusting a second unvetted party with the details of the first assessment.