INTRODUCTION 

Application Security leaders, software engineers, and researchers from all over the world gather at Global AppSec conferences to drive visibility and evolution in the safety and security of the world’s software, as well as to network, collaborate, and share the newest innovations in the field. The training will take place on June 22-24, 2026, at the Austria Center Vienna. 

CALL FOR TRAINERS (CfT) & SUBMISSION  

The Program Team is formally issuing a call for Trainers, opening October 1, 2025. 

As with previous Global AppSec events, we would like to run a number of different training courses of varying lengths over several days surrounding the conference. 

Trainers can apply to give 1, 2 or 3-day classes. Trainers are allowed to make multiple applications, one application per class. The training audience will include developers interested in security as well as security professionals. We will select only the best submission. 

We are looking for training courses at all levels, from someone new to the application security field to advanced topics for experienced professionals. However, all training submissions should focus on practical skills which are immediately applicable to an attendee’s job and have a significant hands-on element with tasks and exercises for attendees to attempt during the training. Our main priority for selecting trainings for this event is useful, practical information that will be valuable for our target audience. Even if this training has been offered before, as long as there is fresh and up to date content. 

REVIEW PROCESS

IMPORTANT DATES: 

CfT Opens: October 1, 2025

CfT Closes: December 12, 2025 at 11:59pm EST

Notification of submitters: Week of January 12, 2026

Program announced: the week of Week of January 19, 2026

REVIEW CONSIDERATIONS

The Program Team will review your submission based on a descriptive abstract and detailed outline of your class. Including additional classroom materials will be helpful in our evaluation. 

Please review your proposal thoroughly, as all accepted abstracts and bios will be published on our site as submitted.

Examples of topics include, but are not limited to the following. We encourage innovation!

• Secure development: frameworks, best practices, secure coding, methods, processes, SDLC
  
• Integrating Security into DevOps or SRE
  
• Vulnerability analysis: code review, pentest, static analysis
  
• Threat modeling
  
• Mobile security
  
• Cloud and serverless security
  
• Kubernetes and Container security
  
• OWASP tools or projects in practice
  
• New technologies, paradigms, tools
  
• Operations and software security
  
• Other topics but with an emphasis on Application Security: Business Risks, Outsourcing/Offshoring, Awareness Programs, Project Management
  

Training should: 

• Be Aimed at a Specific Audience - OWASP has a diverse audience that consists of novice to advanced level practitioners in different fields. Your content should be developed to clearly connect with a specific audience.
• Not be a Marketing Pitch - Submissions that double as marketing or include sales pitches within the training will not be accepted.
  
• Have a Clearly Written Abstract - Your Abstract is the only long-form marketing for your specific talk to our audience. It should be written so attendees can clearly understand what you will be discussing and what they will get out of your class.
  
• Have a Detailed Outline - Detailed description of how you are structuring the course. Walk the reviewer through the training. Please try to be as detailed as possible, including timing and learning objectives for each module.
  
• Be Clearly Applicable - Classes that prioritize content that attendees will be able to immediately implement preferred.
  
• Include Hands-on training - Hands-on labs which allow attendees to connect meaningfully with content are preferred.
  
• Demonstrate the Expertise of Trainer(s) - The submission should highlight the experience of the trainer(s) in the subject of training and in delivering professional training.
  

Terms

All trainers will be required to submit a trainer agreement. The following conditions apply to those who want to provide conference training. 

Trainer provides:

• Class syllabus/training materials.
• Covers travel for the instructor(s) and all course materials for students.
• Promotion of training on all available media eg. Twitter, Linkedin

OWASP provides: 

• Venue
• Catering 
  
• Registration logistics 
  
• Basic wireless internet access (if you need additional technical arrangements, it is important to let us know)
  
• Five (5) power strips for training room
  
• Three (3) flip charts, upon request.
  

Trainer profit-share:

In-person Trainers For Global AppSec events, I am eligible to share 40% of net revenue up to $10,000 USD and 50% of net revenues above $10,000 USD. I may ask to be included in the OWASP Foundation’s discounted hotel block booking, subject to availability and at my own cost. I will be granted a complimentary pass to the Global AppSec. I must provide appropriate taxing authority documentation as needed for final payment, such as a W-9 in the United States. I understand that I will not be reimbursed for any travel expenses such as airfare, accommodation, or any other daily expenses incurred while attending the Company’s Event for which I am a Presenter. For other events, I am eligible according to the terms in the Call for Trainers.

Should in-person or hybrid training take place, OWASP will revise training agreements for selected trainers and address compensation based on the needs of the program. 

All personal data collected during the submission process will be only for contacting submitters regarding their submission and will not be used for marketing or commercial purposes. All data collected will be deleted once the selection process is completed.