Announcing the Winners of May Secure Coding Challenge

✍️ 05/25/2021: Developer leaderboard update - we found an issue with the reporting that led to an error in the developer leaderboard published on Monday. The fix is in place now and the new leaderboard attached below reflects the accurate ranking, with @snieguu (Community Member)​ being the first-place winner in the developer division.

 

Last week, over 50 Community members from 17 countries participated in the May Secure Coding Challenge, working their ways through Cross-Site Scripting (OWASP A7) challenges in the Veracode Security Labs. Here are the winners that have solved the most challenges the fastest: 

 

Developer Division 

 

Security Engineer Division

 

🎁 Winners will receive the OWASP A7 Secure Coder badge and 50 community reputation points. Secure Code MVP will each take home a Google Nest Audio (+ 50 additional points), Secure Code Rising Star will each get a pair of Secure Coder socks. Our team will be in touch with you over the next few days with information on how to redeem the prizes.

 

🚀 What’s next? The next challenge will be on June 10-11 and where you will be solving the security risks of Insecure Deserialization (OWASP A8) - one of the common flaws found in open source libraries. Join the challenge to see if you have what it takes to take down the risk. 

 

----------------------------------------------------------------------

[Scores and Completion Time of the May Challenge Winners]

 

Developer Division (updated on 05/25/2021)

May_SCC_Winners_Dev_Update 

Security Engineer Division

May_SCC_Winners_Secutity Engineer


C-Rod likes this.
    • Thank you @snieguu (Community Member)​ for reaching out! We've fixed the issue in the leaderboard this morning and confirmed that you are the champion in the developer division this month. My team will be in touch with you later today regarding the prizes and benefits. Congratulations 👏

Topics (4)

No articles found
Loading

Ask the Community

Get answers, share a use case, discuss your favorite features, or get input from the community.