How to Run a Security Review for Event Software
The short answer: Run an event software security review in five steps: classify the data the tool will hold (attendee PII, payments, lead data), collect the vendor's evidence (SOC 2 Type II report or ISO 27001 certificate, pen test summary, subprocessor list), check access controls (SAML SSO, SCIM, MFA), sign a GDPR Article 28 data processing agreement with breach and deletion terms, and record any gaps with owners. In our October 2026 check of about 700 event tech vendors' public pages, only 113 documented SOC 2 Type II and 137 documented SAML SSO, so plan for questionnaires with smaller vendors.
Checked 2026-10-19. By EventMarketingSoftware.com.
What data does event software hold that needs a review?
Event software usually holds attendee personal data (names, emails, employers, titles, sometimes dietary or accessibility needs), payment data for paid tickets, session and engagement behavior, and lead data passed to sales. That makes most registration, app, webinar and lead retrieval tools in-scope for a security review.
Classify each tool by data and access: does it store PII, take card payments, connect to your CRM with write access, or let staff log in with company accounts? A badge QR generator with no stored data needs a light review; a registration platform syncing to Salesforce needs a full one.
Watch for sensitive fields. Accessibility needs, dietary requirements tied to religion or health, and passport details for visa letters can be special category or high-risk data under GDPR.
Which security certifications and reports should you ask for?
Ask for a SOC 2 Type II report or an ISO/IEC 27001 certificate first, because they're independent evidence that controls exist and, for Type II, that they operated over a period.
SOC 2 is the AICPA's examination of a service organization's controls relevant to security, availability, processing integrity, confidentiality or privacy, using the 2017 Trust Services Criteria. A Type I report covers control design at a point in time; a Type II report also tests operating effectiveness over a review period. Read the scope, the period, the exceptions and the complementary user entity controls you're expected to run.
ISO 27001 certifies an information security management system. Check the certificate's scope covers the product you're buying and that it's current.
In our October 2026 procurement data covering about 700 event tech vendors, 113 publicly documented SOC 2 Type II, 10 SOC 2 Type I, and 140 ISO 27001. Look up vendors at /security-check, and see /glossary/soc-2-type-ii and /glossary/iso-27001.
What access controls should event software support?
Event software used by more than a few staff should support SAML single sign-on, ideally SCIM provisioning, role-based permissions and MFA, so access ends when someone leaves.
SSO matters because event teams often share logins with agencies and contractors. SCIM automates adding and removing users from your identity provider. In our October 2026 data, 137 of about 700 vendors documented SAML SSO and only 28 documented SCIM, and SSO is often on higher tiers (Stova lists SSO from its Pro package, for example).
Also ask about audit logs, granular roles (for example agency users who can't export attendee lists), API key management and session timeouts. See /glossary/sso and /glossary/scim.
What should the data processing agreement cover?
If the vendor processes personal data of people in the EU or UK on your behalf, you need a written contract meeting GDPR Article 28, usually called a DPA. Article 28(3) lists what it must include.
Required terms: process data only on your documented instructions; staff confidentiality; Article 32 security measures; rules for engaging subprocessors; help with data subject requests; help with security, breach notification and impact assessments; deletion or return of data at the end of the service; and information and audits to demonstrate compliance.
Breach timing: under Article 33, the processor must tell you without undue delay, and you as controller generally have 72 hours to notify the supervisory authority. Ask the vendor for a specific contractual notice window.
In our October 2026 data, 246 of about 700 event tech vendors published or offered a GDPR DPA. See /glossary/data-processing-agreement.
How do you review subprocessors and data location?
Get the vendor's current subprocessor list, check where each one hosts or accesses data, and make sure you'll be notified of changes, because Article 28(2) requires your authorization and a chance to object.
Event platforms often rely on cloud hosting, email delivery, streaming, payment and analytics providers. Check that each one's role and region are listed, that international transfers have a valid mechanism (such as standard contractual clauses), and whether EU data hosting is available if you need it.
In our October 2026 data, 211 of about 700 vendors published a subprocessor list and 167 documented EU data hosting. See /glossary/subprocessor and /glossary/data-residency.
How do you run the review step by step?
Run the review as a short, repeatable process so it doesn't stall the purchase: scope, collect evidence, assess gaps, contract, then monitor.
1) Scope: record data types, users, integrations and whether payments are taken. 2) Collect: SOC 2 report or ISO certificate (often under NDA through a trust center), pen test summary, subprocessor list, DPA, SSO documentation, accessibility conformance report if needed. 3) Assess: map evidence to your control list and send a questionnaire only for gaps. 4) Contract: DPA, breach notice window, deletion on exit, security exhibit. 5) Monitor: calendar the next SOC report date and subprocessor notices.
Start early; reviews can take weeks for vendors without a trust center. Put security questions into your RFP with /tools/event-software-rfp and read /guides/how-to-write-an-event-software-rfp.