propose A TALK

submit a TALK
to devseccon EVENTS
You must login / register to submit.


Proposals – What you Should Know BEFORE SUBMITTING

We are always looking for proposals for our virtual events, meetups, and when they’ll be back our summits, in the following areas:

**Note – abstracts that are vague and do not include in-depth details will not be considered.**

  • DevSecOps, DevOps and Security experiences: the good, the bad and the ugly
  • Cultural changes in organizations: ways to challenge the status quo and implement a new approach to secure development and delivery
  • Applying DevSecOps and continuously secure delivery in an organization:
    • Development – integrating security into development practices, supply chain, SDLC…
    • Testing – testing, quality assurance and practices for releasing secure code
    • Public and private cloud – security of specific cloud services and managed services, integrations, policy management, access control and authentication, and cloud security best practices
    • Operations – infrastructure, platform and networking security, process, culture, transformation
    • Security – new research and exploits, best practices in all areas of security – information security, application security, mobile, cyber and whatever else
    • DevSecOps – includes: shift left, CI/CD, Infrastructure as Code
    • Cloud Native Security – security as it applies to emerging cloud native technologies, all clouds, containers, serverless and more.

Questions to consider when drafting your abstract:

  • Why you? Why this talk? What makes it a must see for those attending the audience?
  • Is this a technical or cultural talk? If technical, what are the prerequisites for the audience to make it as impactful as possible?

Please provide a detailed abstract. Abstracts that do not clearly define the talk or are less than a paragraph will not be considered.

We do not accept any product or vendor pitches.

Provide your top three (3) key takeaways for attendees.

Session formats

You can submit proposals for one of the following:

  • Talks (usually up to 40 mins)

    – Presentation with time for questions or a brief discussion

  • Short Talks (usually up to 20 mins)

    – A short presentation on specific and lean topic, with Q&A if there’s time

  • Workshops (at least 90 mins and can be up to half or full-day sessions)

    – Presentation, technical hands-on learning, with easy setup and resources (e.g. a public repo and cloneable environment), all with an interactive element for participants

  • Ignites (5 mins)

    – We’re not purists about the auto-advancing slides, but we do require that there be exactly 20, and that you not go over the 5 minute allocation (because that’s the fun!)

  • Other (You tell us!)

    – Hey, it’s a community – we’re open to new and out-of-the-box ideas, feel free to propose your idea, and we’ll let you know what we think. (Ideas can be panels, Tell Me Something I Don’t Know Sessions, Chess Timer Talks…whatever you think you can handle).

We welcome any feedback on our submission process and stay at your disposal for any queries, contact us on


DevSecCon does not pay speakers. The DevSecCon is a not-for-profit community, that is funded by sponsorship. In specific cases, when funding allows, we might be able to help with travel expenses but most of our speakers cover their own cost and make their own travel arrangements. Other benefits include pre-conference coaching, special speaker get-togethers for networking, conference goodies and the possibility to stay for the whole conference (for free of course) to soak up the other sessions and connect with attendees. We are committed to creating an experience that’s fulfilling and beneficial on all sides.

Sessions will be assigned a time, date and location based on the moderation team’s discretion, and you will be notified once all assignments have been determined. Please do let us know if you have a special preference for the date or time of your session and we will do our best to accommodate.

DevSecCon cannot guarantee a specific number of attendees. You can help increase attendance by promoting your session to your network using emails, tweets, and other social media channels.

We recommend that the speaker arrives at the conference venue at least 1-2 hours before the assigned speaking slots and makes yourself known to the conference organizers. Speakers should arrive in the presentation room 15-30 minutes early for a sound and device check.

Code of conduct

All speakers must adhere to the DevSecCon code of conduct.

DevSecCon is dedicated to providing a harassment-free conference experience for everyone regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.

Any form of written, social media, or verbal communication that can be offensive or harassing to any attendee, speaker or staff is not allowed at DevSecCon. Please inform a DevSecCon staff member if you feel a violation has taken place and the management team will address the situation. Conference staff can be identified by t-shirts and/or special badges. Participants asked to stop any harassing behavior are expected to comply immediately. We expect participants to follow these rules at all conference venues and conference-related social events.

Recent episodes
get in touch
Visit us on social networks
Privacy Preferences
When you visit our website, it may store information through your browser from specific services, usually in form of cookies. Here you can change your privacy preferences. Please note that blocking some types of cookies may impact your experience on our website and the services we offer.