A skill shortage is a culture problem first.
Most of what keeps people out of security in India isn't difficulty. It's that the field looks closed, or suspicious, or like something other people do. The community work exists to change that, and it is not a marketing channel.
“Hacker” shouldn't be an accusation.
In a lot of Indian households, saying you want to work in security lands somewhere between confusing and alarming. The word carries an association with crime rather than with one of the more employable skills available today.
Why that costs everyone something
Programmes in development.
Nothing here has run yet. We would rather list four things honestly marked as planned than imply a calendar that doesn't exist.
Workshops
PlannedPractical sessions on the things people actually get stuck on: reading logs, understanding auth, thinking about a system the way an attacker does.
Live investigations
PlannedWorking through a scenario in the open, including the wrong turns. Watching somebody debug their own reasoning is more useful than a polished talk.
Capture the flag
PlannedCompetitions built from the same mission format as Suraksha Labs, so practice and competition reinforce each other rather than being separate worlds.
Research in the open
In developmentPublishing our own findings and analysis, with methodology attached, so it can be checked rather than just cited.
The community is the ecosystem's first layer.
Suraksha Labs is where practice happens. Suraksha VDP is where findings go once there are researchers to make them. The community is what turns one into the other.
Free, hands-on practice.
Where legitimate findings go.
Want to help build it?
If you run a student group, teach, organise events, or just want to be in the room early, say hello.