Latest Stories

Stay up-to-date with everything at Approach

Publication

Who is the security champion in your developers’ team?

Publication date

25.11.2021

Cover for article "who is the security champion in your developers' team"
Identify a volunteer within your developers team willing to support the integration of security earlier in the development lifecycle and avoid delays due to vulnerabilities.

If your business develops applications, albeit internally or with third party providers, you have most likely already faced delays in your software releases due to security issues.

Why? Because security checks are performed at the end of the development process and if any vulnerabilities are discovered at that stage, your teams will need time to fix them.

And based on our experience pentesting applications, vulnerabilities are highly likely to be found in your code. That’s why we advise you to implement the shift-left principle and introduce security earlier into your development lifecycle. This will reduce the time and resources you will need to invest in order to address any issues.

However, this means a change in mindset which can be met with resistance from your teams. Nominating a security champion can help ease the transition and facilitate the integration of security from the start of the process.

Who can be the security champion?

The security champion should be a member of your dev team who is highly motivated about security and willing to support the team. Ideally, your security champion should volunteer and not be nominated to ensure they’re truly passionate and will serve as an ambassador for security.

To ease interaction and collaboration with teams, your security champion has to be a good communicator. But most importantly – to succeed in his mission – he will need to have continuous support from the management.

What will your benefits be?

Security:

  • Create a security culture within your organisation
  • Promote the shift left mindset
  • Reduce your exposure and vulnerabilities

Business:

  • Optimise your costs
  • Be compliant with laws and regulations
  • Reduce your time to market

How to start with your security champion?

Firstly, to find your security champion, you need to ensure management buy-in to support them. You should also highlight the benefits of being a security champion (career paths, self-improvement, …) and clearly define his/her role and responsibilities. Once you have identified your champion, you will need to:

  • Create clear communication channels between the champion and the rest of the team
  • Develop a shared knowledge base about security by creating a single source of information
  • Define security KPIs that allow you to measure your success and return on investment
  • Maintain interest and ensure the security champion doesn’t become a hindrance.

Want to improve the security of your applications?

Our experts are ready to support you through:

  • Training and coaching of your developers
  • External security champions: our experts can serve as your champion until you are ready to set-up the process internally
  • Implementation of a secure SDLC (through your security champion)
  • And much more

OTHER STORIES

While Belgian organizations have been navigating the complexities of NIS2 compliance, a new regulatory wave is already on the horizon. The European Union’s Cyber Resilience Act (CRA) entered into force on December 10, 2024, and will fundamentally reshape how businesses approach cyber security for products with digital elements. Unlike NIS2, which focuses on organizational security measures, the CRA targets the products themselves – from smart home devices to industrial IoT systems.
In 2025, the secure development landscape is at a turning point. Critical regulations like the EU’s Cyber Resilience Act are forcing organisations to shift from optional best practices to mandatory secure-by-design strategies. But are organisations truly ready? Drawing from OWASP SAMM benchmark data, this paper assesses where different industries stand, the influence of organisational size on maturity, and what it takes to build security programs that are both effective and compliant.
Threat modeling isn’t just a technical step, it’s a mindset. It empowers development teams to think like attackers, ask the right questions early, and embed security from the start. By making security collaborative, practical, and developer-friendly, it lays the foundation for resilient, trusted software delivery.

Contact us to learn more about our services and solutions

Our team will help you start your journey towards cyber serenity

Do you prefer to send us an email?