What Is Confirmed About the Event
BrokerTech Connect Chicago 2026 is organized by BrokerTech Ventures and scheduled for Sept 1-2, 2026 in Chicago. The event has been announced publicly as a gathering of insurance and insurtech leaders, with the organizer's own materials describing it as a venue for connecting carriers, brokerages, and technology vendors. Publicly available announcements confirm the event name, dates, location, and organizer, but do not yet list a confirmed sponsor roster, exhibitor names, or session-level agenda. That absence of published detail is itself useful information for a security leader: it means the value of attendance will come less from pre-reading a program and more from how effectively each vendor conversation is structured on the floor. This article focuses on that structure rather than speculating about which specific companies or products will appear.
The Gap Between a Good Demo and a Deployable Product
Insurtech vendor demonstrations at industry events are built to show functional capability: an underwriting assistant that drafts a quote, a claims agent that triages a file, a broker copilot that answers coverage questions in seconds. None of that is evidence of security architecture. A live demo can look identical whether the underlying agent operates under a shared service account with broad standing access or under a scoped, individually revocable identity. The difference only becomes visible when someone asks about it directly. This matters because procurement conversations that start at a conference booth often move into contract negotiation without a security architect in the room, and by the time a CISO is looped in, commercial terms may already be set. Treating the event as a due-diligence opportunity means asking runtime security questions at the same table where the product is being pitched, not after a term sheet is drafted.
Turning Floor Conversations Into a Defensible Procurement Record
- Ask for a live demo of enforcement: Request an unscripted demonstration of permission boundaries rather than relying on a security slide in the pitch deck.
- Trace the full task lifecycle: Ask the vendor to show how agent access is provisioned, monitored, and de-provisioned from start to finish, not just at setup.
- Confirm log ownership: Establish whether audit logs can be exported to your own SIEM or GRC tooling instead of remaining only in a vendor dashboard.
- Bring security into the room: Ensure a CISO or security architect is part of post-event vendor conversations before any contractual commitment is made.
- Use one checklist for every vendor: Apply the same question set consistently across every booth meeting so responses can be compared like for like.
Governance Considerations Beyond the Event Floor
Carriers and brokerages operate under state insurance department expectations around data handling and third-party vendor oversight, and those expectations extend to any AI agent vendor that will touch policyholder or claims data. Vendor risk assessment processes should treat AI agent runtime permissions as their own review category, separate from standard data security and privacy questionnaires, since agent behavior involves multi-step actions that static questionnaires do not capture well. Any resulting contract should specify audit log retention periods, the buyer's right to access those logs on request, and incident notification timelines specific to agent-related security events. It is also worth documenting, in writing, exactly which security questions were asked at the event and how each vendor responded. That record becomes useful later, both for internal procurement governance and as a reference point if a vendor's answers on the floor do not match what is delivered in a signed agreement.