WorkflowIT & Data

Vendor Security Assessment

Vendor security assessment that shows where the answers and the evidence disagree

A cited vendor risk rating with gaps and controls, ready to sign

See one case, screen by screen ↓
demo640answers and testsmapped to the control framework for one Tier-1 vendor — 611 answers and 112 SOC 2 pages read
demo2contradictionsfound in the sample vendor's evidence, each with the questionnaire answer and the auditor's finding side by side
target6.6hof analyst time per Tier-1 vendor assessment, against about 20 h by hand
target9daysmedian from complete evidence to a signed decision, against a 15-day goal
In short

What is Vendor Security Assessment?

Software that takes a supplier from its evidence pack — security questionnaire, SOC 2 report, pen test, policies and agreements — to a rated, signed decision. Vendor Security Assessment adds six agents that read the whole pack, score ten security domains from each source, flag every answer the independent evidence contradicts and explain residual risk, for the third-party risk analyst to decide and sign.

How to choose AI solutions for life sciences →

Updated

The problem

Why a Tier-1 vendor review takes days — and still misses the gap that matters

Drug makers hand patient data, GxP trial data and admin access to hundreds of suppliers. Before each contract or renewal, IT risk reads the vendor's SIG questionnaire, its SOC 2 Type II report, its pen-test summary, its policies, certificates, BAA and DPA, and decides whether the residual risk is acceptable. A Tier-1 review is a questionnaire of more than 600 questions and an 80–120-page audit report, read side by side by hand — about 20 analyst hours.

The dangerous gaps are contradictions. The questionnaire says MFA is enforced for 100% of privileged accounts, and Section 4 of the SOC 2 records an exception. The two statements sit in different documents, written by different people, and are found only if someone compares them line by line. Miss one and a signed approval rests on a false answer; find it late and the renewal slips, the business owner escalates and the review gets rushed.

demo627questionsin one vendor's SIG Core questionnaire
demo112pagesin the same vendor's SOC 2 Type II report
estimated20hof analyst time for a Tier-1 review read by hand
Where a Tier-1 assessment's analyst hours goestimated
By hand20 days
With the solution6.6 days
  • Reading the questionnaire, SOC 2 and pen test, and mapping them to our controls12 → 1 d
  • Comparing answers with tests and reviewing findings4 → 2.8 d
  • Vendor follow-up — requests, bridge letters, evidence2.5 → 1.9 d
  • Decision, co-signature and sign-off1.5 → 0.9 d

Estimated by-hand split of about 20 hours; the hours with the solution are the ones its dashboard shows on the sample portfolio.

How it works

How an assessment moves

Six agents read the questionnaire, SOC 2 and pen test, find contradictions and rate the risk; the third-party risk analyst decides.

What comes in
Evidence inVendor evidence pack · questionnaires, audit reports, tests, policies
Agents at work
Evidence classifierfiles + gaps
Then
Questionnaire readeranswers + comments
SOC report readerexceptions + pen tests
Then
Control mapper & contradiction finderanswers vs evidence
Then
Risk raterinherent → residual
Then
Request & clause writerrequests + next review
A person decides
Third-party risk analystdecides; high risk gets a second signature
What comes out
Signed risk rating
Requests to the vendor
Next review booked
One case, step by step

One Tier-1 renewal, from evidence pack to signed decision

Velunda Trial Cloud runs clinical data capture and patient diaries for 14 studies — about 38,000 participants — and its renewal is due on Nov 15, 2026. The decision is due Oct 9. Here is what happens, screen by screen, in the working solution.

  1. 01Oct 7

    Five assessments need her

    Priya Raman · Third-party risk analyst

    Priya's assessments list shows 14 vendors with recent activity, 5 of them needing her. Velunda Trial Cloud is Tier 1, in analysis: inherent Critical 88, residual High 64, 9 of 10 documents in and 1 missing, decision due Oct 9 — two days away.

    “Showing 14 of 14 with recent activity · 472 more vendors in monitoring, all quiet”

  2. 02Already read

    Every source scored, domain by domain

    The agents

    The agents have read 611 of 627 answers from SIG Core 2026 and 112 SOC 2 pages, and mapped 640 answers and tests to the control framework. The security radar plots ten domains: blue is what the vendor says, green what the independent evidence shows, the dashed ring is the Tier-1 bar of 75. Encryption & keys reads “98 said · 52 shown”.

    “The questionnaire says every backup is encrypted — the auditor found backups that were not”

  3. 03One click

    The auditor's exception on page 52

    SOC report reader

    SIG G.1.2 says all client data at rest, including backups in both hosting regions, is encrypted with AES-256. The SOC 2 test of CC6.7 found 2 of 10 sampled backup sets from the secondary region without encryption at rest before September 4, 2025. Management says earlier backups were re-encrypted by November 2025, with no evidence to the auditor — and the pen test still finds TLS 1.0 and 1.1 accepted on the SFTP gateway.

    The SOC report reader quotes exceptions word for word and never treats a management response as evidence.

  4. 04The second one

    MFA for every privileged account — except 3 of 25

    Control mapper & contradiction finder

    Questionnaire answer H.4.2 says MFA is enforced for 100% of privileged accounts. The SOC 2 test of CC6.1, on page 48, found 3 of 25 sampled privileged accounts without it. The finding asks for an identity-provider MFA policy export dated after February 2026, covering every privileged account.

    “A contradiction needs both passages.”

  5. 05Claims nobody tested

    What the SOC 2 never looked at

    Control mapper & contradiction finder

    The compliance statement says the audit trail is always on and cannot be disabled — but no validation summary or Part 11 assessment was supplied, and the SOC 2 does not test audit-trail controls. Privacy is not in the SOC 2 scope either, though patient data is processed. Both are listed as claims no independent test covers.

    “Ask for: The vendor validation summary and Part 11 / Annex 11 assessment for the current release.”

  6. 06Our side

    Seven controls the auditor assumed we run

    SOC report reader

    Velunda's auditor assumed Northwind runs 7 complementary user entity controls. Five are in place. Two need action: the access review for this system runs once a year, not quarterly — Dana Okafor's — and the audit-trail review runs in 9 of 14 studies — Dr. Maya Chen's.

  7. 07The rating

    High 64 today, Moderate 34 with conditions

    Risk rater

    Inherent risk is Critical 88: protected health information in US patient diaries, GxP trial data supporting submissions, 14 live studies and 9–12 months to replace. Vendor controls bring the base to 34; seven findings add 30 — MFA +9, the open pen-test highs +8, backup encryption +4, no bridge letter +3, and +2 each for incident notice, validation and privacy.

    Scores are explained, never bare — every point has its reason.

  8. 08Drafted

    Seven requests to the vendor, clauses to procurement

    Request & clause writer

    One request per finding, each with its due date and the passage it relates to — from the MFA export within 14 days to the HIPAA risk-analysis summary within 30. Contract clauses for the renewal come from the approved library, such as a 24-hour initial incident notice.

    The writer sends nothing to a vendor without the analyst.

  9. 09The decision

    Approve with seven conditions

    Priya Raman · Third-party risk analyst

    The recommended decision is “Approve with conditions”: 7 conditions, tracked to closure. Full reassessment Oct 2027 for a Tier-1 vendor, every 12 months, and a triggered check on Dec 15, 2026 for the pen-test retest letter. Residual is High, so Omar Haddad co-signs after her.

  10. 10Signed · same day

    Signed, co-signed, sent, booked

    Priya Raman and Omar Haddad

    Priya signs, and Omar Haddad, Head of IT Risk & Compliance, co-signs for the High residual. The requests go to Marta Lindqvist, Velunda's CISO, and the clauses to Sam Patel in procurement. The reassessment is booked for Oct 2027, with the triggered check on Dec 15.

    “Approved with conditions — co-signed by Omar Haddad, vendor and procurement told”

Who it’s for

Built for everyone who signs off a vendor.

The same renewal, seen by the four people who carry it — what their review looked like, and what it looks like now.

PR
Priya RamanThird-party risk analyst · 8 assessments open
Third-party risk analyst
Before
“The answer says yes. I need to know where the auditor says no.” Reads 600-plus answers and an 80–120-page audit report side by side for each Tier-1 vendor.
Now
Opens a radar already scored per domain, with each contradiction and both passages one click away; spends her time on the decision.
OH
Omar HaddadHead of IT Risk & Compliance · co-signs High residual
Head of IT Risk & Compliance
Before
“If I sign it, show me the page behind every point.” Co-signs every High residual and accepts Tier-1 risk.
Now
Sees residual explained point by point, each finding with its passage, before adding the second signature.
MC
Dr. Maya ChenClinical operations · business owner for the trial platform
Clinical operations
Before
“Tell me what to fix, not just no.” Needs the trial platform renewed by Nov 15.
Now
Gets a decision with conditions instead of a hold, and sees the controls on her side — the audit-trail review in 5 more studies.
SP
Sam PatelProcurement category manager · renewal paper
Procurement category manager
Before
“Give me the clause wording.” Puts the security terms into the renewal paper.
Now
Receives the clauses from the approved library, one per domain with a finding, when the decision is signed.
Built on the engine

6 agents. Each with one job, and hard limits.

Six agents read the questionnaire, SOC 2 and pen test, find contradictions and rate the risk; the third-party risk analyst decides.

Evidence classifier

Files each document a vendor sends — questionnaire, SOC 2, bridge letter, pen-test summary, certificate, policy, BAA — into the right assessment and flags what is missing.

  • Never opens password-protected files without the vendor's key
  • Vendor documents stay in the vendor's assessment
Questionnaire reader

Reads SIG Core, SIG Lite and CAIQ answers with their comments, keeping each answer's reference and cell. Blank or “N/A” answers count as unanswered unless a reason is given.

  • Cites the questionnaire reference for every answer it uses
SOC report reader

Reads SOC 2 reports in the order reviewers use — opinion, scope and criteria, carve-outs, controls on our side, Section 4 exceptions and management responses — and also pen-test summaries and policies.

  • Quotes exceptions word for word
  • Never treats a management response as evidence
Control mapper & contradiction finder

Maps answers and tests to the Northwind Control Framework and finds contradictions, missing evidence, stale periods, missing criteria and carved-out fourth parties — reusing reports already on file.

  • Every finding cites at least one passage
  • A contradiction needs both passages
Risk rater

Scores inherent risk from the tiering form and residual risk from controls and findings, with the reason for every point and the score if the conditions are met.

  • Scores are explained, never bare
  • High or Critical residual routes to the co-signer
Request & clause writer

Drafts the remediation request to the vendor and contract clauses for procurement from the findings, and books reassessments by tier.

  • Sends nothing to a vendor without the analyst
  • Uses approved clause wording only
Third-party risk analyst

Decides; high risk signed twice. The agents propose; a named person decides.

Ask in plain words

Ask about any vendor, finding or rule

Ask in plain words — every answer points to the page it came from.

Where do Velunda's answers and evidence disagree?

Two answers are contradicted. Encryption: SIG G.1.2 says every backup is AES-256, but the auditor found 2 of 10 backup sets unencrypted before September 2025, and the pen test still sees TLS 1.0 on file transfer. Access: MFA “100%” against 3 of 25 admin accounts without it.

Why is Velunda rated High?

Velunda is Critical inherent (88) — patient data for 14 studies, GxP trial data, 9–12 months to replace. Its controls bring the base to 34; seven findings add 30. The biggest driver: the auditor found 3 of 25 admin accounts without MFA while the questionnaire says 100%. With the conditions met it drops to Moderate (34).

What do we have to run on our side for Velunda?

Velunda's auditor assumed we run 7 controls. Five are in place. Two need action: quarterly access review (yearly today — Dana Okafor) and audit-trail review running in 9 of 14 studies (Dr. Maya Chen).

Which pen-test findings are open?

Velunda has 2 high findings open from the July test: object-level access on the patient-diary API and legacy TLS on file transfer. The retest is booked for November — after the Nov 15 renewal — so the decision carries a retest-letter condition by Dec 15.

Every screen

The working solution, as it ships.

13 screens from the working solution, on its sample data. Pick one to see it large.

Security radarWhat the vendor says against what the evidence shows, in ten domains, with the contradiction finder open on Encryption & keys.
AssessmentsEvery vendor with an open assessment — tier, stage, inherent and residual risk, evidence received and the decision clock.
Claims no test coversThe GxP audit-trail claim with no validation evidence, and the request that would close it.
Findings, side by sideThe domain strip, each contradiction with both statements, and the questionnaire answer highlighted in its cell.
The auditor's exceptionThe SOC 2 report opened beside the findings, with the auditor's exceptions highlighted — backup encryption on page 52, change approval on page 61.
Controls on our sideThe complementary user entity controls the auditor assumed, matched to our controls with a named owner and status.
Inherent and residual riskWhy inherent risk is Critical, what moves residual point by point, and a what-if for each condition.
Requests and clausesThe remediation request to the vendor, one item per finding with its due date, and the contract clauses for the renewal.
The decisionThe recommended decision, its conditions, the reassessment and triggered check, and the co-signature rule.
Signed and co-signedSigned by the analyst, co-signed by the Head of IT Risk, requests and clauses sent, reassessment booked.
MonitoringReassessments booked by tier, the next 90 days, and the signals that open a review early.
DashboardAssessments completed, median days to decision, analyst hours, residual risk by tier and evidence freshness.
Your rulesTiering, evidence rules, reassessment cadence, approvals, framework mappings and people — all settings, versioned.
Governance

Built for third-party risk: cited, signed, on the record.

No citation, no findingEvery score and finding cites the passage behind it — questionnaire cell, SOC 2 page, pen-test finding — and a contradiction is raised only with both passages.
Evidence, not assurancesExceptions are quoted word for word, and a management response is never treated as evidence: a fix the vendor reports without proof becomes a request.
A named person decidesThe agents recommend; the third-party risk analyst decides and signs. High or Critical residual needs a second signature from the Head of IT Risk, who also confirms risk acceptance on Tier-1 high findings.
Nothing leaves without the analystRequests go to the vendor only when the analyst sends them, and contract clauses use the approved clause wording only.
Vendor documents stay containedEach vendor's documents stay in its own assessment, visible to the assessment team and the business owner, and the agents never train on vendor documents.
Every step on the recordEach agent step, request, signature and co-signature is on the activity trail, which cannot be changed. Decisions and rule changes are versioned and kept seven years.
Configuration

Your standard, not ours

The rules the agents apply, who decides and how often vendors are reassessed are settings. Changes apply to open assessments and are versioned.

SettingDefaultChoose from
Patient or health dataTier 1Tier 1 · Tier 2
Ask for a bridge letter when a SOC 2 period ended more than3 months3 months · 6 months · 9 months
High pen-test findings fixed and retested within30 days30 days · 45 days · 60 days
Accept ISO 27001 in place of SOC 2 for Tier 2 and 3OnWhen the certificate scope names the service we buy
Reuse fourth-party reports already on fileOnA carved-out host's report is reused across every vendor that runs on it
Flag questionnaire answers the evidence contradictsAlways on for Tier 1Always on for Tier 1
Tier 1 full reassessmentEvery 12 monthsEvery 12 months · Every 18 months · Every 6 months
Residual High or Critical — co-signs after the analystOmar HaddadOmar Haddad · Priya Raman
Connections

Works with the evidence a vendor review already runs on

Security questionnairesSIG Core, SIG Lite and CAIQ, with the vendor's comments
SOC 2 reportsType II and Type I reports and bridge letters, including a carved-out host's report already on file
Pen-test summariesfindings by severity, status and retest dates
Policies and agreementsincident response plans, ISO 27001 certificates, compliance statements, BAA and DPA
Tiering formprocurement's intake: data handled, GxP use, access and replaceability
Supplier portal and mailboxwhere vendors send their evidence, filed into the right assessment
What it changes

The difference, in numbers.

Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.

target
6.6h
of analyst time per Tier-1 vendor assessment
By hand≈ 20 h
With agents6.6 h
target
9days
median from complete evidence to a signed decision
Decided on day 9
target is 15 days
target
2contradictions
caught in one vendor's evidence, each with both passages side by side

“demo” = seen in the working solution, on its sample vendor data · “target” = the design goal, measured in the live solution · “estimated” = our estimate, including the about-20-hour by-hand review (a 600-question questionnaire plus an 80–120-page audit report per vendor). Northwind Bio, its vendors, and the people named on this page are fictional — characters and sample data in the working solution.

Questions

What IT risk teams ask us.

What is vendor security assessment software?

Software that takes a supplier from its evidence pack — security questionnaire, SOC 2 report, pen test, policies and agreements — to a rated, signed decision. Vendor Security Assessment adds six agents that read the whole pack, score ten security domains from each source, flag every answer the independent evidence contradicts and explain residual risk, for the third-party risk analyst to decide and sign.

How does it review a SOC 2 report?

The SOC report reader works in the order reviewers use: opinion, scope and criteria, carve-outs, complementary user entity controls, Section 4 exceptions and management responses. It quotes each exception word for word, never treats a management response as evidence, and reuses a carved-out host's report already on file instead of asking for it again.

How does it find contradictions between the questionnaire and the evidence?

The control mapper and contradiction finder scores each domain from the questionnaire and from the independent tests, and flags any answer a test contradicts — for example “MFA is enforced for 100% of privileged accounts” against a SOC 2 exception for 3 of 25. Both passages are shown side by side, each cited to its page. It also lists claims no independent test covers.

Does it handle SIG and CAIQ questionnaires?

Yes. The questionnaire reader reads SIG Core, SIG Lite and CAIQ answers with their comments and keeps the reference and cell of every answer it uses. The framework mappings in Settings cover SIG Core 2026, SIG Lite 2026, CAIQ v4, ISO 27001:2022 Annex A, NIST CSF 2.0, NIS2 Art. 21 and the SOC 2 criteria.

How is residual risk calculated?

The risk rater scores inherent risk from procurement's tiering form — data handled, GxP use, access, scale and replaceability — then a base after the vendor's controls, plus points for each open finding, each with its reason. It also shows the score if the conditions are met; on the sample vendor that is High 64 today and Moderate 34 with conditions.

Do people stay in control of the decision?

Yes. The agents recommend; the third-party risk analyst decides and signs, and High or Critical residual is co-signed by the Head of IT Risk. Nothing is sent to a vendor without the analyst, and clauses use approved wording only.

Can we set our own tiering, evidence rules and reassessment cadence?

Yes. Tiering rules, bridge-letter age, the pen-test fix window, ISO 27001 in place of SOC 2, reuse of fourth-party reports, the reassessment cadence by tier, the triggers that open a review early and who approves are all settings, versioned when they change.

How long does it take to go live?

The Agentic Solution Engine builds and deploys it from your requirements and documents — your control framework, tiering rules, clause library and a sample of past vendor evidence packs — and it goes live once every quality gate has passed. We will walk you through it on your own vendors first.

See it on
your vendors.

We'll run Vendor Security Assessment on the evidence pack from one of your own Tier-1 vendors.