Join us for the 2025 OWASP AppSec Days Bangalore. Designed for private and public sector infosec professionals, OWASP conference equips developers, defenders, and advocates to build a more secure web. We are offering the conference and exhibition on 18 October. Join us for leading application security technologies, speakers, prospects, and community in a unique event that will build on everything you already know to expect from an OWASP Conference. With amazing speakers and networking opportunities, this is an event you will not want to miss.

 CALL FOR PRESENTATIONS (CFP) & SUBMISSION 

The AppSec Days Bangalore Program Team is formally issuing a call for presentations, opening April 1, 2025 and closing July 31, 2025, at 11:59 IST. 

What topics should you submit about?

 This year’s tracks are based on traditional OWASP tracks, but slightly changed and clarified. Speakers should focus on the following guidelines for each of the tracks below. Sessions will be scheduled for 45 minutes, and 20 minutes with an additional expected 5-10 minute Q&A period. 

BUILDER / DEVELOPER - Show the community how to build more secure apps, how to securely use technology in our code, and how to secure our systems at scale.

BREAKER / TESTER - Show the community how to test apps for security, and how to break secure systems, how to be a better bounty hunter, and how to integrate penetration testing in the SDLC

DEFENDER / OPS - Show the community world-class application operational defense, tools and techniques enabling detection and response to attacks, automating processes and pipelines, working with bounty hunters and running a production security program. 

MANAGER / CULTURE - Show the community how to run security teams effectively, create an effective security culture, selling security to executives, or balancing the risk tradeoffs.

We’ve provided a few topic suggestions below, but feel free to innovate!

• Web application security
• AI
• Mobile, Cloud, and Serverless security
• Blockchain & Internet of Things for security use
• Penetration testing & Application-level attacks
• Threat modeling, Application, and system architecture
• Security for DevOps engineers
• Privacy controls
• Planning and implementing an application security program
• Creating an AppSec team & culture
• Techniques to communicate risk and AppSec value to management - sharing what works and what doesn’t!
• How you failed. Things you did and didn’t work. Share pitfalls and failures so we all can learn from them. 

 REVIEW TIMELINES - CfP IMPORTANT DATES: 

CfP Opens: April 1, 2025

 CfP Closes: July 31, 2025

 Notification of submitters: Week of August 1, 2025

 Program announced: Week of August 15, 2025

Keep in mind: the better your description is, the better our review will be. Please review your proposal thoroughly, as your accepted abstract and bio will be published publicly as submitted on our site. 

******************************************************

REVIEW CONSIDERATIONS

The Program Team will review your submission and give it a rating which will be used to compare it to the other submissions in your chosen track. 

Your submission *will be disqualified* if: 

Your submission was submitted by someone who is not one of the speakers such as the marketing team or a marketing agency.

The top scored submissions:

-Have a clear abstract that describes an interesting and relevant talk which we would choose to attend. This is primarily to market to attendees but obviously it needs to impress the reviewers as well.

-Have an outline that leaves no doubts about the structure of the talk and the timings 

-Tell the reviewer exactly what you will be covering. Don’t just say “we will provide our top 5 techniques for avoiding this issue. Instead, clearly set out for the reviewer what those 5 techniques will be. Don’t keep secrets from the reviewer or try to keep the reviewer in suspense, that is what the conference abstract is for!

-Discuss a new or novel topic that attendees couldn’t see in the recordings of previous conferences or in existing resources.

-Describe a real-life story of how you solved a problem in a real-world environment.

-Are clearly aligned with the audience in the track to which the talk is being submitted and clearly demonstrates why the submission it is relevant for the stated skill level. 

-Demonstrate clear takeaways that attendees can immediately implement at their workplaces.

Top reasons submissions get marked down or rejected:

-No clear link to the topics listed above.

-Poorly formatted or structured submission or significant spelling and grammatical mistakes. Get someone else to review your submission or use an online tool to proofread it.

-Your submission sounds like it was created by an AI.

-Your submission makes it sounds like the answer to the challenge you raise in the talk is to buy your product. Alternatively, the submission sounds like a direct sales pitch. If you work for a vendor, we will be looking for a clear explanation of what value the submission brings, separate to your product or service.

-Your submission is full of buzzwords without clarity on what tangible value the talk brings to the attendee.

-The shorter the submission, the less time the reviewer will spend on your submission before they mark it down, due to a lack of details..

-Your submission has self-identifying details