The story of how we got started — and why we believe security culture is built by engineers, not checklists.
For many years, we did lots of penetration testing across medium-sized startups to Fortune 500 enterprises. We realised our pen-test reports often did not solve these firms' security problems. The root cause wasn't the design or implementation of their programs — it was something else.
We listened to everyone from product owners to software testers, and found a big gap between what security people push for and what engineers care about. A wrong culture and approach to security meant bug reports felt like a burden, not an opportunity.
We turned real pen-test findings into a course built from developers' own programs. Not another course to turn every developer into a hacker — one that teaches defensive design patterns and security principles in the developer's language.
Developers used their learnings in day-to-day work and loved that security was implicitly taken care of by better-designed software. ❤️After almost every course, internal security teams heard about security bugs discovered and patched by their own engineers.
I built SecDim for one reason: I was tired of seeing smart developers become dependent on tools to catch their mistakes. Scanners, AI assistants, security reviews — none of that makes you better. Practice does.
SecDim is here to make you genuinely stronger.
We want more companies to have similar success stories.
Our mission is to change the wrong approach (i.e. Whack-a-mole security patching) and culture (e.g. security is pain) to application security.
We've created a dedicated company to achieve our mission!
Looking for a quote? Interested to know more about our enterprise offering? We're here to assist you with any type of question.
[email protected]Need help with your account, subscription, billing issues or have a technical question? Submit a support request
Support TicketLet's discuss your specific needs and requirements
