The security event landscape
- Large security conferences (e.g. RSA Conference): broad vendor expos and practitioner audiences
- Technical and research events: highly technical audiences, low tolerance for sales pitches
- Regional and sector events: financial services, healthcare, public sector security
- Ecosystem events: cloud and platform conferences with security tracks
Defining a security event ICP
| Attribute | Example criteria |
|---|---|
| Security category | Identity, cloud, data, network, application |
| Buyer maturity | Has a dedicated security team or CISO |
| Regulatory context | Operates in regulated industries |
| Ecosystem role | Buyer vs vendor partner vs MSSP vs competitor |
Roles to consider
- CISOs and security leaders
- Security architects and engineers
- Security operations managers
- Partner and alliance managers at vendors
- Procurement for larger organizations
Pre-show workflow
- Step 1
Choose
Select events where your buyers or partners concentrate.
- Step 2
Prioritize
Separate buyers, partners, and competitors; tier by fit.
- Step 3
Validate
Confirm roles and review the source of each record.
- Step 4
Prepare
Offer technical, specific meeting reasons and keep messages short.
Security professionals are sensitive to how their data is used. Never imply you know someone is attending unless they told you, and follow applicable privacy rules.
Tools that can help
See how to qualify exhibitors against your ICP for a manual process.