You've launched your Security Champions programme. You've recruited enthusiastic developers, introduced them to the security team and perhaps sent them on a training course. Now what?
How do you keep your champions engaged? More importantly, how do you help them get their development teams actively involved in security?
The challenge isn't necessarily a lack of enthusiasm. It's finding practical activities that make security part of everyday development without adding another significant burden to already busy engineers.
Here are seven activities that can help.
1. Run a security-focused team discussion
Time: 15–20 minutes
Give your Security Champions a topic they can bring to their next team meeting.
It might be a recent vulnerability, a security incident affecting a familiar technology or a common weakness such as broken access control.
Rather than delivering a presentation, ask a few simple questions:
- Could something similar happen in our applications?
- What controls do we already have?
- What could we do differently?
The objective isn't to turn developers into security experts. It's to get them comfortable asking security questions and recognising risks in their own work.
Why it works: It creates a regular opportunity to discuss security without requiring a separate training session.
2. Introduce a short, game-based security challenge
Time: 30–40 minutes
Sometimes the best way to engage developers is to stop talking about security and give them something to do.
A collaborative cybersecurity card game can turn a routine team meeting into an opportunity to explore security concepts, make decisions and discuss potential threats.
For example, CyberSec Games' Security Architects can be used as a short group activity to introduce security architecture and threat-related concepts.
Allow time for an introduction, gameplay and a brief discussion afterwards.
Ask participants what surprised them, which decisions were difficult and what lessons might apply to the systems they build.
Why it works: Developers practise thinking about security together, without sitting through another presentation.
3. Make threat modelling a manageable team activity
Time: 45-60 minutes initially, depending on scope
Threat modelling is often seen as something requiring specialist expertise, extensive training and a formal workshop. But not every discussion about security threats needs to be a large exercise.
A Security Champion can help their team explore potential threats when designing a feature, introducing a new integration or changing an existing architecture.
Game-based approaches such as Elevation of Privilege use the STRIDE threat categories to prompt teams to consider threats they might otherwise overlook.
Start with a clearly defined system or feature, work through relevant threat scenarios and record anything that needs further investigation. Not every question needs to be resolved in the session. More complex risks can be escalated to the application security team.
Why it works: It gives developers a structured way to contribute to threat identification without requiring them to become specialist threat modellers.
4. Review a real vulnerability together
Time: 20-30 minutes
Choose a vulnerability from your application security backlog, a resolved issue or an appropriate public example. Ask the team to explore how the weakness might arise and how it could have been prevented.
The Security Champion can guide the discussion around the root cause, possible exploitation paths and potential mitigations.
The aim is not to blame whoever introduced the issue. It's to help the team recognise similar problems in future.
Why it works: It connects security learning directly to the software developers work on.
5. Introduce security questions into design discussions
Time: 10-15 minutes per relevant design review
Security shouldn't only become a topic when an application reaches a formal assessment. Encourage Security Champions to bring a small number of security questions into relevant planning or design discussions.
For example:
- What are we trying to protect?
- Who or what can access this feature?
- Where are the trust boundaries?
- What could go wrong?
- Are there assumptions we should validate?
These questions aren't a substitute for a full security assessment where one is needed. They create an opportunity to recognise potential risks earlier.
Why it works: Security becomes part of existing development conversations rather than an entirely separate process.
6. Run an AI/ML security exploration
Time: 45-60 minutes
If your development teams are building or integrating AI/ML systems, give them an opportunity to explore the security challenges those systems introduce.
Use a relevant example architecture to discuss how data, models, integrations and external inputs might create security risks.
Games such as Elevation of MLSec can provide structured prompts for exploring AI and machine-learning threats.
This is particularly useful when teams are beginning to adopt unfamiliar technologies and need a shared vocabulary for discussing risk.
Why it works: It introduces structured security conversations around emerging technologies without requiring every developer to become an AI security specialist.
7. Give champions an activity they can repeat
Time: Ongoing
One of the biggest challenges in a Security Champions programme is maintaining momentum. A launch event can generate enthusiasm. A training course can develop knowledge. But what happens afterwards? Give champions an activity they can repeat with different teams and new colleagues.
This might be a short security game, a guided threat modelling exercise or a regular discussion of real-world vulnerabilities. Provide a simple format, clear instructions and enough support for champions to facilitate the activity confidently.
The objective is to create something that doesn't depend on your central security team organising and leading every session.
Why it works: Security engagement becomes a repeatable team activity rather than an occasional event.
Why not just send everyone on a threat modelling course?
Formal training has an important role, particularly for Security Champions who need deeper knowledge and confidence. But developers already have a job.
You don't necessarily need every developer to become a trained threat modeller. You need them to recognise potential threats, contribute to security discussions and know when to involve a specialist. That's where small, structured and repeatable activities can make a difference.
Rather than expecting developers to master an entire methodology before they can contribute, give them a manageable starting point. A focused exercise, a clear set of prompts, a predictable amount of time and most importantly, a practical outcome.
Done consistently, these activities can help make security thinking a normal part of software development.
Give your Security Champions the tools to get started
At CyberSec Games, we believe security is easier to engage with when people can learn by doing.
Our cybersecurity card games and Play to Learn workshop kits provide practical ways to introduce security concepts, facilitate threat modelling discussions and get development teams working together.
Whether you're running a short team activity with Security Architects, introducing application threat modelling with Elevation of Privilege, or exploring AI/ML threats with Elevation of MLSec, our games provide a structured starting point.
We also offer workshop materials and branded decks that can support a consistent Security Champions programme across your organisation.
Explore CyberSec Games for Security Champions.