The RSAC 2026 Conference in San Francisco drew more than 43,500 attendees and more than 600 exhibitors (RSAC, closing release, 2026). A security leader who walked that expo floor did not lack vendors. She already runs too many. In a study by the IBM Institute for Business Value and Palo Alto Networks, organisations reported an average of 83 security solutions from 29 vendors (IBM, January 2025).
That is the starting position for anyone who plans one-to-one meetings between security vendors and chief information security officers (CISOs). The vendors will gladly pay for the meetings. The CISOs have every reason to decline them.
This guide is for organisers of cybersecurity conferences and summits who want to add a pre-booked meeting programme, or repair one that buyers avoid. Its argument is simple. The programme works only when the CISO controls it: her problem comes first, the vendor second, and nothing leaves the room without her consent.
Why security buyers are harder to host than other tech buyers
The commercial model is the same as at any executive summit: the buyer attends as a guest, and the vendor pays for pre-arranged meetings. We explain it, with published prices and buyer contracts, in hosted buyer summits in B2B tech. Security adds three conditions that change how you have to run it.
Three figures that shape a security buyer's diary
The first condition is saturation. A leader with 29 vendors is usually trying to reduce that number, not to add to it. Every meeting request competes with a consolidation plan. A thirtieth vendor needs a reason.
The second is trust. In a 2026 survey of 320 enterprise security decision-makers, peer recommendations ranked highest for discovering vendors, at 55 per cent (Ponemon Institute and NOLA Marketing, The State of Cybersecurity Marketing Influence on Buyers 2026). For you, that means the peer sessions are not the wrapping around the vendor meetings. They are the reason a CISO travels at all.
The third is confidentiality. A useful vendor meeting requires the buyer to say what is not working in her own defences. Picture the CISO of a mid-sized insurer who admits in a 25-minute meeting that her team cannot see what its suppliers can access. If she expects that sentence to appear in a sales database the next morning, she will speak in generalities or not come.
Her diary is the product. Treat it accordingly.
Start with her problem list, not your vendor list
Those three conditions point to the same first step. Most programmes sell vendor packages first and then look for buyers to fill the slots. A security programme should begin on the other side, with what each CISO is working on in the next 12 months.
Ask for it at registration, with fixed categories that match how vendors describe themselves, so the two lists can be compared later.
| Question | Ask the CISO | Ask the vendor |
|---|---|---|
| Topic | Up to three priorities from a fixed list, for example identity, cloud security, third-party risk | The one or two categories the product belongs to, from the same list |
| Timing | Is there a project, and when: within 6 months, within 12 months, exploring | Which customer size and sector the product has references for |
| Limits | Categories she has just bought or does not want to discuss | Who will attend: sales lead, solutions engineer, or both |
The third row matters more in security than elsewhere. A CISO who signed a three-year contract for endpoint protection in spring gains nothing from four endpoint vendors in autumn. Let her say so, and respect it in the schedule. Keep the form short, though: which fields earn their place is the subject of our article on registration questions for matchmaking. Role and budget still need vetting, as described in how to qualify hosted buyers.
With that data, an invitation to a meeting can say why it exists. “You listed third-party risk as a priority for the next six months” is a reason. “Our platform is trusted by leading enterprises” is not.
Let her choose, and cap every category
A problem list tells you which meetings could make sense. The CISO still decides which ones happen. The Richmond Cyber Security Forum brings together 80 cyber security decision-makers and 35 solution providers, and delegates choose the pre-scheduled meetings they want (Richmond Events, accessed November 2026).
The ratio shows what you can sell. Take an illustrative calculation, not a benchmark. If each of 80 delegates accepts six meetings, there are 480 meetings to share among 35 vendors, about 14 each on average.
The average hides the real problem, which is the category. Suppose nine of the 35 vendors sell identity products, but only 20 delegates listed identity as a priority, and nobody wants more than two meetings on the same topic. That leaves 40 identity meetings for nine vendors, between four and five each. Sell those nine vendors a package of “up to 15 meetings” and you have promised something your buyers never offered.
So cap the number of vendors per category before sales open, based on how many buyers named that category. The Information Security Forum, a member organisation that hosts an annual congress, states the principle in its sponsorship brochure: “We strictly limit the number of vendors at each event” (ISF, Sponsorship Brochure 2026). A cap costs you a package or two in a popular category. It protects the renewal of every other vendor in it.
The ceiling for all of this is the number of meetings one buyer can hold in a day, which we calculate in how many meetings each hosted buyer should get. How the two sides stay in balance is the subject of our guide to buyer-to-seller ratios. Choice is the quality control.
Protect the room: rules for confidentiality
Choice brings the CISO to the table. Confidentiality decides how openly she talks once she sits there. The large security conferences treat this as a rule, not a courtesy. Black Hat describes its CISO Summit as invitation-only, reviews every application and holds the day under the Chatham House Rule. Attendees from solution providers, vendors and media are not permitted, with the exception of event sponsors (Black Hat, CISO and Executive Summit pages, accessed November 2026).
The Chatham House Rule itself is short. Participants “are free to use the information received, but neither the identity nor the affiliation of the speaker(s), nor that of any other participant, may be revealed” (Chatham House).
A meeting programme needs its own version of these rules, written down and sent to both sides:
- Peer sessions stay closed: vendors join the meetings and the meals they sponsor, not the peer discussions. If a sponsor hosts a table, delegates set the topic, and the host follows the rules of a roundtable discussion.
- No scanning in the meeting area: a badge scan turns a conversation into a lead record without anyone agreeing to it. Scanning on the expo floor is a separate decision, which we discuss in lead retrieval for event organisers.
- Profiles before names: show vendors role, sector and stated priorities when they select buyers. The name and contact details follow once the CISO has accepted the meeting.
- Follow-up by consent: at the end of each meeting, the buyer says whether she wants a follow-up and through which channel. Only that answer goes into the vendor’s report.
Think of the alternative. An account executive leaves the table, stands in the corridor and types the insurer’s weak spots into a customer database, tagged with her name. She will not see it happen, but she will assume it. What she said stays hers.
Put an engineer at the vendor’s side of the table
Rules protect the conversation. They do not make it worth having. The same 2026 survey shows what security buyers miss: 52 per cent cited insufficient technical depth in vendor marketing, and technical workshops were among the most valued event formats, at 43 per cent (Ponemon Institute and NOLA Marketing, 2026). A CISO who has chosen a meeting on third-party risk wants to ask how the product works in an environment like hers. A sales lead with a slide deck cannot answer that.
You can shape this as the organiser. Make a named technical person, such as a solutions engineer, a condition of every package. Send both sides a short briefing two or three days before, with the topic the buyer chose and the question she wants answered. Keep the slot at 25 to 30 minutes, and ask vendors to open with questions, not with a presentation.
Depth earns the second meeting. Nothing else does.
Hosting without pressure
Depth is what the CISO gets from the vendor. What she gets from you is the hosting, and here security needs a lighter hand than other sectors. Many security leaders work in banks, insurers, utilities or public bodies, where internal rules on gifts and hospitality tend to be strict. Publish exactly what the hosting includes, and let delegates decline single parts or pay for them themselves.
Obligations should be equally plain. Ask delegates to attend the meetings they chose, and to release a slot a day ahead if plans change. People keep that promise more reliably than a quota pressed on them. How to count booked against held meetings is explained in our article on event meeting no-show rates.
From problem list to delivery report
Put together, the programme runs in a fixed order. The weeks are a working plan for a two-day conference with travel, not a rule.
A vendor meeting programme at a cybersecurity conference in seven steps
- 16 weeks Collect buyer priorities Invited security leaders name up to three priorities, their timing and the categories they do not want to discuss.
- 14 weeks Set category caps Count the buyers per category and fix how many vendor packages each category can carry.
- 12 weeks Sell within the caps Offer packages as capacity, and require a named technical contact from every vendor.
- 5 weeks Open selection Buyers choose vendors first; vendors then request buyers by role, sector and priority.
- 2 weeks Publish schedules Confirm mutual matches, send draft diaries and allow swaps and declines.
- On site Hold and rebook Record which meetings took place and offer free slots when one falls through.
- After Report by consent Each vendor receives scheduled, held and missed meetings, plus the follow-ups buyers agreed to.
The order carries the argument. Buyers state their problems before packages are sold, and buyers choose before vendors request. Reverse either step and you are back at a programme the CISO avoids.
What vendors get afterwards, and what they do not
The last step is where two promises meet. The vendor paid for meetings and wants proof of delivery. The CISO spoke openly and wants discretion.
Both are possible if the report counts meetings and leaves their content out. Each vendor sees how many meetings were scheduled, held and missed, and which buyers agreed to a follow-up. It contains no notes about a buyer’s gaps and no contact details beyond those she released. A vendor who held eleven meetings and left with six agreed follow-ups does not need a brochure to renew.
Solution: Converve’s matchmaking runs on a rule-based meeting matrix. You define which participant groups may meet and on which criteria, for example the solution category on the vendor side and the stated priority on the buyer side. Both sides send and accept requests within those rules, and requests, acceptances, slots, tables and attendance are recorded for each meeting. You can see how this is set up for hosted formats on our hosted buyer solution page and on the B2B matchmaking page.
Conclusion: the CISO’s diary is the product
A meeting programme at a cybersecurity conference lives on the number of security leaders who accept a meeting and speak openly in it. That happens when the CISO controls the programme: her priorities set the topics, her choice sets the schedule, and her consent decides what the vendor takes home. Category caps, a technical counterpart and a report that counts meetings do the rest.
When the CISO of that mid-sized insurer tells a peer the meetings were worth her time, you have won next year’s buyer and vendor at once. If you want to set up meeting rules, selection rounds and delivery reports for your security event, get in touch with Converve.
Frequently Asked Questions
How do you get CISOs to attend vendor meetings at a cybersecurity conference?
Give them control. Ask each CISO for her priorities before you sell vendor packages, let her choose whom she meets and keep the conversation confidential. Peer content matters too: in a 2026 survey of 320 security decision-makers, peer recommendations ranked highest for discovering vendors, at 55 per cent (Ponemon Institute and NOLA Marketing).
How many vendors should a CISO meeting programme admit?
As many as your buyers’ stated priorities can carry, counted per category. The Richmond Cyber Security Forum, for example, invites 80 decision-makers and 35 solution providers (Richmond Events, accessed November 2026). If only 20 buyers name identity as a priority, nine identity vendors are too many, whatever the overall ratio says.
Should vendors receive the attendee list?
Not as a list of names. Show vendors role, sector and stated priorities for selection, and release name and contact details only when the buyer has accepted a meeting. After the event, each vendor’s report lists held meetings and the follow-ups buyers agreed to.
What is the Chatham House Rule at a security event?
Under the Chatham House Rule, participants may use the information they receive, but may not reveal the identity or affiliation of the speakers or of any other participant (Chatham House). Black Hat holds its invitation-only CISO and Executive Summits under this rule (Black Hat, accessed November 2026).