G2

Alexander K.

Chief Information Security Officer

Mid-Market (51-1000 emp.)

9/30/2026

"SecDim Makes Shift-Left Security Training Practical for Engineers"

5/5

What do you like best about SecDim?

What I like most about SecDim is how effectively it shifts application security from being mainly a security-team responsibility to becoming a practical capability within engineering.

We used it as part of a broader DevSecOps program. The goal wasn’t just to have developers complete security training, but to help them recognize, understand, and prevent real vulnerabilities in their day-to-day work. The hands-on approach, realistic scenarios, and emphasis on learning by doing made a noticeable difference compared with traditional awareness training.

It also fit especially well with our Security Champions model and our broader shift-left initiatives. SecDim gave developers a practical environment to build security skills, while our security team could focus on enabling teams, improving controls, and embedding security into the development lifecycle - instead of repeatedly covering the same fundamentals.

For me, the biggest value is that it treats developers as engineers rather than compliance recipients. That makes security training much easier to integrate into an engineering culture. Review collected by and hosted on G2.com.

What do you dislike about SecDim?

The main area I would improve is the learning curve for developers who are newer to application security. Some of the challenges become technically demanding quite quickly, so more adaptive guidance, progressive hints, and clearer paths from beginner to advanced levels would make it easier to roll out across engineering teams with very different levels of security maturity.

There are also some areas of the user experience that could be streamlined. As the platform has grown, reducing unnecessary navigation and making the journey from assignment to hands-on exercise even more seamless would help.

Finally, real-world vulnerabilities are often architectural rather than isolated coding mistakes. I would love to see SecDim continue expanding scenarios that require developers to think beyond fixing a specific function and consider design-level security decisions as well. Review collected by and hosted on G2.com.

What problems is SecDim solving and how is that benefiting you?

SecDim helped us solve one of the most difficult parts of a DevSecOps program: turning security knowledge into practical developer capability at scale.

We already had automated security testing, vulnerability management and a Security Champions model in place. The missing part was making sure developers understood why vulnerabilities happened, how they could be exploited, and how to prevent the same type of issue in future code. SecDim helped close that gap through practical, hands-on exercises rather than traditional awareness training.

It also fitted well into the way we wanted to run security engineering. Training should not sit separately from development. It should connect naturally with repositories, CI/CD, IDEs and the tools engineers already use. That made SecDim much easier to position as part of the engineering workflow rather than another corporate training platform.

The benefit was also operational. It reduced the need for repeated manual coaching from the security team and gave developers a way to build skills independently. That meant security specialists could spend more time on engineering, automation and higher-risk issues.

For us, the real value was not training completion numbers. It was stronger developer ownership of security, better discussions between engineering and security teams, and a more scalable way to improve secure development practices. Review collected by and hosted on G2.com.