Shifting left on security while having fun
Shift-Left-on-Security is not only essential for preventing expensive and time-consuming problems later in the Software Development Lifecycle, but it can also be made attractive and motivating for developers. This whitepaper discusses how to make the transition a success.

Summary
Shift-Left-on-Security is not only essential for preventing expensive and time-consuming problems later in the Software Development Lifecycle, but it can also be made attractive and motivating for developers. This whitepaper discusses how to make the transition a success.
Key takeaways:
Reduce risks and save costs: Investing in security early in the process reduces the likelihood of incidents and speeds up releases.
Make security fun for developers: By adding game elements and challenges, security becomes part of their daily work enjoyment.
Overcome organizational and team challenges: Create ownership, facilitate knowledge development, and apply security best practices consistently.
Promote collaboration and innovation: Use informal discussions, hackathons, and security champions to connect teams and share knowledge.
Want to know how BBTG has successfully applied this approach and how your organization can benefit from it too? Read on and discover the possibilities.
Introduction
You have probably already heard of Shift-Left-on-Security and how important it is. You may have even looked into how to apply this within your organization or team. Have you offered security training to developers or taken training yourself? Yet, it often proves difficult to actually integrate security early in the process. Why is that? In this whitepaper, we discuss the obstacles and how you can overcome them. This is how we make security more fun for developers!
* The further you "shift right" (later in the process), the more frustrating and costly security becomes. More importantly, shifting left (earlier in the process) ultimately delivers greater business value by reducing the risk of security incidents and saving time. According to DORA, teams that integrate security early in the process spend up to 50% less time remediating security issues.
Shifting left on security pays off
Let's briefly revisit why Shift Left on Security is so important. As Wouter van Vegchel describes in his whitepaper 'Secure from the Start', it is a proactive approach where security is integrated early into the Software Development Lifecycle. This has become increasingly urgent, with one key takeaway: fixing security issues after the fact is expensive and complex. This is due to three main causes:
- It is harder to fix existing code.
- There is often a lot of pressure for quick fixes.
- Friction arises between security experts and developers.
Solving security issues is more difficult when you have to account for existing code. You have to find the problem and also check the surrounding code, which may have dependencies. If the code is already live, there is often pressure to fix it quickly. This increases the chance of errors. Even if the code is not yet live, friction and stress can arise if the responsibility for security lies outside the team. This is often seen in large organizations. This approach leads to two possible scenarios: the bar is lowered to meet deadlines, which frustrates experts and harms quality, or the release is blocked at the last minute, which causes frustration for the business and developers.
So why isn't it happening (everywhere)?
Although it is clear why we should apply security best practices early in the process (see Wouter van Vegchel's whitepaper), in practice, we are not shifting left enough. Sometimes it is attempted, but without success. This is not surprising, as it requires a change in the way both the organization and the developers work. And that is where obstacles arise.
The things you encounter as an organization
Organizations must first understand what non-functional requirements are: everything needed to keep software manageable and sustainable. Think of infrastructure, the build and release process, readable code, flexible architecture, and, of course, security. These requirements are often difficult to measure, so their value is not always visible. It sometimes feels like an upfront cost, even if it is logical that they are necessary.
This makes it difficult for the business to get a firm grip, often forcing them to rely on trust. If that trust hasn't been established yet, getting started can feel daunting. Fortunately, DORA research shows that investing in security early delivers positive outcomes. Stricter regulations, such as GDPR (AVG) and AML, are also compelling organizations to prioritize this. Ultimately, it comes down to building confidence across the business that this approach pays off.
… and what you encounter as a developer or team
If the organization provides the space and priority for security, developers can get to work. But why isn't that happening everywhere yet? There are three main reasons:
- Security lies outside the team.
- Knowledge is lacking within the team.
- Developers don't enjoy it, especially after the fact.
In large organizations, security often lies with a Chief Information Security Officer (CISO) and their team. This leads to less ownership within the development team and creates a knowledge gap. The solution is to place responsibility with the team and provide the right support to bridge that gap. The latter, in particular, is the challenge.
Training is crucial here. Ideally, developers choose their own training, but suggesting good training often helps get them started. Choose something that aligns with their learning style, such as self-paced online courses. For security, there are many platforms that convey knowledge through challenges and gamification. Once developers have gained knowledge, they also want to apply it, which strengthens ownership.
But what if developers have no interest in gaining that knowledge because they don't enjoy it? Developers often prefer to "crush features" and are less interested in dealing with non-functional requirements. That is because they are often perceived as "not fun." Ideally, the motivation comes from the developers themselves. Often that is the case, because they know they have to work on security to keep their software safe. But not everyone is always equally motivated. In that case, you have to find a way to make them realize that security is not only necessary, but can also be fun.
Make it fun!
Even with sufficient budget and knowledge, it remains a challenge if developers don't enjoy security. Fun is subjective, but it often means working on a challenging problem with a clear goal, variety, rewards, and an impact on the result. Even if you are lagging behind on security, you can make it fun.
How do you do that? These components can help:
- Awareness: Start with awareness of the importance of security.
- Security mindset: Don't let developers think only about features, but also about potential risks. This doesn't require technical skills, so you can start immediately.
- Keep it small: Large, tedious tasks are often put off. Break them down into small, manageable pieces and make them part of the daily workflow.
- Gamification: Add a game element to make it more fun.
- Knowledge sharing: Encourage teams to share knowledge.
- Knowledge development: Encourage continuous learning about security.
- Support from above: Ensure management sees security as an essential part of the work, not as a cost. Give teams recognition and appreciation.
Informal discussion
Awareness often starts with an informal discussion. For example, organize a lunch or pizza session to talk about security with different teams. You will notice that there are very different perspectives. This naturally makes it clear why security is important and what it means for everyone.
Use these sessions to discuss how you can contribute to security in an accessible way, simply by asking the right questions. This helps to develop that security mindset.
An added benefit: these conversations improve knowledge sharing between teams. "War stories"—experiences with security issues—often come up, which make the topic more vivid and get people excited. At BBTG, we have had great experiences with this!
Threat modelling
Threat modelling is a proactive approach to identifying and analyzing potential risks and vulnerabilities in software. Each risk is given a score so that the team can prioritize objectively.
Regularly add threat modelling sessions to your sprint. This can be boring, but it can also be fun. Try to get people excited with challenging questions. From experience, we know that the best sessions arise from questions like:
- “How can we as a team get filthy rich from this?”
- “How can we drag the organization's name through the mud?”
- “How would you take revenge if you were fired as a developer for a devious reason?”
- “Can we use our app to create chaos in the organization?”
Start with the team's own code, but also let colleagues from other teams take a look. A fresh perspective often helps. This way, you immediately share knowledge and experience (“We had a similar vulnerability and solved it this way”). This also strengthens the bond between teams and makes future requests for help easier.
Internal hackathon
Developers often know the software better than anyone else. They know exactly where the weak spots are. Take advantage of this by organizing an internal hackathon. Let teams try to hack or abuse each other's applications, possibly with a role-playing element based on threat modelling. Add a competitive element, such as a prize—like a team outing or a lunch—and turn it into a team-building activity.
An added benefit is that you get immediate feedback on your code. By collecting all the teams' findings, you can identify common problems and knowledge gaps. This offers opportunities for further knowledge development or for purchasing tools that address these issues systematically.
Hackathons are ideal for off-site locations and also work excellently as team-building events.
Bug bounty program
A step further than an internal hackathon is a bug bounty program. In this, you invite external experts to track down security bugs in your applications. Usually, a financial reward is given, depending on the severity of the vulnerability found.
You can also set up such a program internally. Just make sure to establish clear guidelines so everyone (developers, management, etc.) knows where they stand. This prevents pitfalls like the 'cobra effect' (intentionally introducing bugs).
Some companies give a portion of the reward to the employee who found the bug. The remaining amount can go to a charity or into a pot for a party once a certain amount has been collected.
Post-mortem
Despite good preparations, things can always go wrong. This is frustrating, but it also offers an opportunity to learn and improve. It is important not to point fingers, because then no one will want to take responsibility. Instead, you should learn from it by conducting a post-mortem.
In a post-mortem, you record what went wrong and how it happened. You document the impact of the incident and the steps taken to resolve it. The question of "how could this happen" (root cause) is answered as thoroughly as possible. In addition, you propose concrete actions to prevent recurrence. This is how you turn a negative event into something positive.
Have the team share these lessons with the rest of the developers and the organization as soon as the problem is resolved. This way, you disseminate knowledge widely and structurally improve the process.
Facilitating security champions
Not everyone has an affinity for security, and that is perfectly fine. But give those who are enthusiastic about it the space to grow. Perhaps they want to organize a workshop or propose a new security feature. These "security champions" often have more impact within their team than a notification during a company presentation or on a slide.
Give these people recognition and appreciation. This can be financial, but it doesn't have to be. Acknowledge their contribution during a company call or give them the opportunity to attend a conference or training. They will appreciate this and bring the knowledge they have gained back to their work.
Ensure that security champions can exchange knowledge with each other and, for example, compile a list of best practices and recommended training courses. By distributing them well across the organization, you prevent them from working in silos. This allows them to encourage others within the organization to think about security more often.
So, what now?
It is not easy to make security fun, and the approach can vary per organization or team. The most important thing is to just get started. Invite a group of developers for lunch or a pizza session and see what ideas they have. Is there motivation to gain knowledge? Then make sure you move forward with the right people.
At BBTG, we have also gone through this transformation. We now have a security community where knowledge is shared and cases are discussed. We continuously help our clients improve their security mindset. Do you want to take security at your organization to the next level? Contact us today, and together we will make security not just a necessity, but something your team gets excited about!
Featured posts
We don't do off-the-shelf job openings. We create your ultimate role based on your personal ambitions and expertise.

Shifting left on security while having fun
Shift-Left-on-Security is not only essential for preventing expensive and time-consuming problems later in the Software Development Lifecycle, but it can also be made attractive and motivating for developers. This whitepaper discusses how to make the transition a success.





