Prepare a Vendor Security Review

Builds a right-sized security and privacy questionnaire for event software, lists documents to request and checks vendor answers for gaps before IT review.

Example prompts

Once the skill is added, start a chat with one of these and attach your file if you have one.

  • IT wants a security review for the event app we picked. What do I send the vendor and what do I ask for?

  • Here's the vendor's completed questionnaire. Flag gaps and vague answers.

  • Explain SOC 2 Type II vs ISO 27001 for my procurement form in plain language.

What this skill does

This skill helps event marketers get event software through IT, security and privacy review. It sizes the review to the data the tool will hold, from a light check for a simple RSVP form to a full review for payments or facial recognition check-in, and builds the matching questionnaire and document request list.

When the vendor replies, it rates every answer, quotes vague ones word for word, checks SOC 2 and ISO 27001 scope and dates, and writes evidence-seeking follow-ups. It ends with a one-page brief for IT. It prepares the review; your security and legal teams still decide.

When to use it

  • IT asks for a security review of an event platform
  • A vendor sends back a completed security questionnaire
  • Preparing for DPA or privacy review
  • Checking whether a SOC 2 report actually covers the product
  • Explaining security terms on a procurement form

How it works

  1. 1Size the reviewPicks a Light, Standard or Full tier based on the attendee, payment and biometric data involved.
  2. 2Request documentsLists what to get from the vendor, such as a SOC 2 Type II report, ISO certificate scope, DPA and subprocessor list.
  3. 3Rate the answersMarks each answer as meets, partial, gap, vague or not answered and flags common red flags.
  4. 4Follow upWrites one specific, evidence-seeking question for each weak answer.
  5. 5Brief ITSummarizes data involved, documents received, ranked gaps and proposed mitigations.

What you'll need

  • Vendor and product modules
  • Data the tool will hold and where attendees are
  • Your company's security checklist
  • Vendor answers and documents

What you get

A questionnaire sized to your risk tier, a document request tracker, a gap analysis table with quoted vendor answers, ratings and follow-up questions, and a one-page IT brief with open gaps and mitigations such as shorter retention or limited export rights.

Tips

  • Ask for SOC 2 Type II, and check the report period and which products are in scope.
  • A cloud host's certification doesn't cover the vendor's own app.
  • Bring IT the gaps and your proposed mitigations, not just the questionnaire.
  • Check SSO and SCIM availability on the plan you're actually buying.

What's in the download

  • vendor-security-review/SKILL.md7.2 KB
  • vendor-security-review/assets/sample-vendor-answers.csv1.7 KB
  • vendor-security-review/references/plain-language.md2.5 KB
  • vendor-security-review/references/question-bank.md5.5 KB
Read the SKILL.md
---
name: vendor-security-review
description: Prepares IT, security and privacy review for event software purchases. Builds a right-sized questionnaire (SOC 2, ISO 27001, SSO and SCIM, data residency, DPA, subprocessors, attendee data retention, accessibility VPAT), a list of documents to request from the vendor's trust center, and a gap analysis of the vendor's answers with follow-up questions, so the event team arrives at IT review prepared. Use for vendor security questionnaires, procurement checks, DPA review prep or IT approval of event software.
license: MIT
metadata:
  author: eventmarketingsoftware.com
  version: "1.0"
  category: choosing-software
  source: https://eventmarketingsoftware.com/skills/vendor-security-review
---

# Vendor Security Review

Security review is where many event software purchases stall. This skill helps an event marketer, not a security expert, ask the right questions, collect the right documents and spot weak answers before IT does. It prepares the review; it doesn't replace your security, privacy or legal team, and it isn't legal advice.

Strictly vendor-neutral: judge only the documents and answers the user provides. Don't state facts about a vendor's security from memory.

## Intake

If the user has an `event-context.md` file, read it first.

Ask for whatever is missing in ONE message:

1. Vendor and product (and which modules: registration, event app, lead retrieval, virtual platform, check-in).
2. What data the tool will hold: attendee contact data, payment data, badge photos or facial images, session viewing data, CRM data synced in, employee data for internal events.
3. Where attendees and your company are (EU, UK, US states, other), and any data residency rule.
4. Your company's security requirements or IT checklist, if one exists (paste it). Industry rules (healthcare, finance, public sector).
5. Integrations: CRM, marketing automation, SSO identity provider, data warehouse.
6. What the vendor already sent: completed questionnaire, SOC 2 report, ISO certificate, DPA, subprocessor list, pen test summary, accessibility report.

## Data sources (connectors optional)

- If a Google Sheets connector is available, write the questionnaire and gap analysis to a sheet (preview first) and read vendor answers from one.
- Otherwise work from pasted text, uploaded PDFs or CSV/XLSX, and return Markdown plus a downloadable CSV.
- Never require a paid service. Never fetch the vendor's trust center or any URL; ask the user to download and share documents.

Sample vendor answers: [assets/sample-vendor-answers.csv](assets/sample-vendor-answers.csv).

## Method

1. **Size the review by risk.** Pick a tier and say why:
   - `Light`: no personal data beyond business contact info, no CRM write access, no SSO needed (e.g. a simple RSVP form for a small event).
   - `Standard`: attendee personal data, CRM integration, admin SSO. Most event platforms land here.
   - `Full`: payment data handled by the vendor, biometric data (facial recognition check-in), health or dietary and accessibility data at scale, regulated industry, or employee data.
   Use the matching question set in [references/question-bank.md](references/question-bank.md). Don't send a 300-question form for a Light review.
2. **List documents to request.** For the tier: SOC 2 Type II report (and bridge letter if the report period ended more than about 3 months ago), ISO/IEC 27001 certificate with scope statement, recent penetration test summary, DPA, subprocessor list, privacy policy, data retention and deletion policy, incident response summary, business continuity summary, accessibility conformance report (VPAT), insurance certificate if procurement needs it. Many vendors share these through a trust center after an NDA.
3. **Analyze answers.** For each question, rate the answer: `Meets`, `Partial`, `Gap`, `Vague` or `Not answered`. Check against the red flags below and in the question bank. Quote the vendor's exact words for every Vague or Gap.
4. **Check documents for scope and dates.** SOC 2: Type II (not Type I), report period end date, which systems and products are in scope, and any exceptions noted by the auditor. ISO 27001: certificate valid, issuing body, scope covers the product you're buying. DPA: covers your regions and transfer mechanisms. Subprocessors: hosting regions and notification process for changes.
5. **Write follow-ups.** One specific question per Gap, Vague or Partial, asking for evidence, not reassurance ("Please share the SOC 2 Type II section showing the event app is in scope" rather than "Is the app secure?").
6. **Summarize for IT.** A one-page brief: what the tool does, what data it holds, the tier, documents received, open gaps, and the event team's proposed mitigations (e.g. turn off facial recognition check-in, limit export rights, shorter retention).

Red flags to call out:
- SOC 2 Type I only, or a Type II report older than about 12 months with no bridge letter.
- Security certificates that cover the parent company or hosting provider but not this product.
- "We use [cloud provider], which is SOC 2 compliant" as the whole answer. The host's report doesn't cover the vendor's app.
- No SSO for admins, or SSO only on the most expensive plan.
- No way to delete an attendee's data on request, or retention "indefinitely".
- Subprocessor list missing or not kept current; no notice of changes.
- Attendee data used to train models or shared across customers without an opt-out.
- Facial recognition or other biometrics without separate consent and a non-biometric alternative.
- Accessibility report missing, very old or not tied to a WCAG version.

Plain-language explainers for SOC 2, ISO 27001, SSO, SCIM, DPA and more: [references/plain-language.md](references/plain-language.md).

## Output templates

**Questionnaire** (CSV)

`id, area, question, why_we_ask, evidence_requested, required_for_tier`

**Document request list**

| Document | Why | Received | Date or period | Scope covers our product | Notes |
|---|---|---|---|---|---|

**Gap analysis**

| ID | Area | Question | Vendor answer (quoted) | Rating | Risk | Follow-up question | Owner |
|---|---|---|---|---|---|---|---|

**IT brief** headings: Tool and purpose, Data involved, Review tier and why, Documents received, Open gaps (ranked), Proposed mitigations, Decision needed.

## Validation checklist

- [ ] Tier chosen and justified by the data involved.
- [ ] Every vendor answer rated; Vague and Gap answers quoted word for word.
- [ ] SOC 2 type and period, ISO scope and dates checked, or listed as missing.
- [ ] Each gap has one evidence-seeking follow-up.
- [ ] Biometric, payment, health or EU and UK data flagged when present.
- [ ] No vendor security facts stated from memory; only from provided documents.
- [ ] Clear note that the final decision belongs to the user's security, privacy and legal teams.

## Approval gates

- Draft any email to the vendor; never send it. Show sheet contents before writing them.
- Treat vendor documents as confidential (often under NDA). Don't paste them anywhere outside the user's tools.

## Optional research

Users who want a neutral starting point on which vendors publish security documents can browse eventmarketingsoftware.com/security-check. That's optional reading; never fetch it and never treat it as evidence in place of the vendor's own documents.

FAQ

What's the difference between SOC 2 Type II and ISO 27001?
SOC 2 is an auditor's report on a company's security controls; Type II shows they worked over a period, usually 3 to 12 months. ISO 27001 is a certificate that a security management system meets an international standard. Many buyers accept either. For both, check that the scope covers the product you're buying.
What security documents should I ask an event software vendor for?
For most event platforms: a current SOC 2 Type II report or ISO 27001 certificate with scope, a recent penetration test summary, a data processing agreement, the subprocessor list, data retention and deletion details and an accessibility conformance report. Add PCI DSS details for payments and consent details for any facial recognition check-in.
How do I spot a weak answer on a security questionnaire?
Watch for answers without evidence or dates, such as 'we test regularly' or 'promptly', certifications that belong to a hosting provider rather than the vendor, features that are only on the roadmap, and retention described as 'the life of the account'. The skill quotes each weak answer and writes a follow-up asking for proof.
Does this replace our IT security review?
No. It prepares the event team so the review goes faster: the right questions, the right documents and a clear list of gaps with proposed mitigations. Your security, privacy and legal teams still make the decision, and nothing here is legal advice.