Welcome to “FAQ Central”, a central area where we’ve consolidated questions throughout the our website into one area. If you can’t find what you’re looking for, you can submit your own at the bottom of the page.
Speaking Fees & Policies (9)
Yes. Conferences, keynotes, briefings, user groups, and trainings. Ranging from security conferences to HackerCons, vendor events or private association events, and training law enforcement agencies. Fees vary, but generally, if its a private event, you must cover travel and fees. If its a public agency, and we willing to do it, then we generally contribute at no charge (law enforcement events, training, public university, public utility, etc.). Contact us for more information.
Fees range from $2,500 USD to $8,500 USD. Lower end if its something we already have prepared and increases depending on needing to create new content or presenting for extended lengths (beyond 2 hours). We don’t change for some public agencies, particularly law enforcement trainings and conferences.
Unless otherwise agreed, we maintain ownership and copyright of the content. Don’t worry, we don’t want to own any of yours either. Also, we need to agree ahead of time on filming and copies of the presentation. We are open to it, but sometimes we need to be careful about what makes it out to distribution.
For the most part, we’re pretty flexible. If it’s regarding some of our published research content, then you might be interested in a vendor version report that provides you with redistribution licenses to much of that content. You can check out the “CRLTU” Agreement in Policy Central for more details. Or put us in touch, and we’ll get your marketing liaison whatever they need.
Generally yes, However, being security, there are times when we may be discussing information that is not in the public domain. This can be specific exploits, unpublished research, and other sensitive issues that greatly benefit the audience, but can be drawbacks of greater disclosure. This is covered during the planning phases to ensure expectations are met and boundaries are respected.
This requires our consent. In general we don’t have issues if we aren’t making disclosures not intended for public consumption and if there isn’t research content that otherwise requires a license. If it does, we can discuss working that out (we can agree on redactions, omissions, etc.). Some basic ground rules are 1) let us know your intentions up front so we can plan the content to be conducive toward your goals, 2) always attribute the source, and 3) don’t change the context of our statements.