AWS Builder Center
Everyone Is a Developer Now. So I Built a Cybersecurity Team.

Everyone Is a Developer Now. So I Built a Cybersecurity Team.

AI made building software ridiculously accessible. But there’s one problem nobody talks about enough: not everyone building software has a security team. So I decided to build one.

Let's start Building

Everyone Is Building. Who's Securing It?

I'm a cybersecurity researcher, I do bug bounties, I vibe-code a lot, and I love going to hackathons.
One day I was reading about a startup that got hit really badly because of security vulnerabilities in their product.
And I started thinking...
Everyone is building software now. But not everyone has a security team.
A solo developer probably isn't hiring a red team.
A small startup might not have the money for security researchers.
And now AI makes building products even easier.
So we're creating faster than ever.
But security still feels like something you bring in later.
That didn't make sense to me.
So I thought:
Why don't I try to build the security team instead?
And that's how Kryonsec started.


Kryonsec is my attempt to make cybersecurity more accessible to developers, startups and builders who can't just hire a whole security team.
I wanted something that could look at a product more like a security researcher would — find things, investigate them, and help figure out what actually matters.
But I also didn't want to just give an AI unlimited access and say:
“bro, go hack this.” 💀
I've tested enough AI systems to know they can be really smart and still make really stupid mistakes.
So I made Kryonsec with human approval in the workflow.
When it finds a possible attack, it asks me before doing anything risky.
That part matters to me a lot.
Because in cybersecurity, one wrong decision can become a very expensive problem.


The project also tries to follow the way I personally approach security research.
I've done a lot of bug bounty work, so I have my own way of thinking about recon, connecting clues and figuring out where to go next.
Kryonsec is basically me trying to turn some of those habits into something repeatable.
It's not just:
AI + security tools = done.
There's a whole workflow behind it.
And honestly, that's one of the parts I'm most proud of.


Then came First Commit.
And AWS decided to make me suffer a little. 😭
I spent a good amount of time getting Amazon Bedrock working inside Kryonsec.
Sometimes the model worked.
Sometimes it didn't.
Then the gateway had problems.
Then there were region issues.
Then I'd fix one thing and discover another.
At some point I was just looking at my terminal thinking:
“bro… wtf.”
But I actually learned a lot because I wasn't just reading about Bedrock.
I was trying to make it work inside something real.
And that was probably one of my favourite parts of the hackathon.


The other battle was Docker.
Kryonsec has a lot of security tooling, so getting the whole environment working together was... pain.
And I even had one of those amazing developer moments where I had fixed bugs in the new version, but I was still testing an older version.
So basically:
I fixed the bug. Then tested the wrong thing. Then wondered why the bug was still there.
💀


But that's honestly what I like about hackathons.
You build something.
It breaks.
You swear at it.
You fix it.
Then you break something else.
And somehow you're having fun the entire time.
I really enjoyed the First Commit venue polaris school of technology, I spent time talking with the volunteers, played in the retro game zone for a bit, and obviously had the important battle over the keyboard/keycap swag.
I lost that battle.
Got stickers instead. 😭
Fair enough.


The bigger idea behind Kryonsec is still really simple to me:
If everyone can build software now, everyone should have easier access to security too.
I don't know exactly how far I'll take Kryonsec yet.
But I know I want to keep building it.
Because somewhere between bug bounties, vibe coding, hackathons, broken Docker containers and Bedrock refusing to behave...
I ended up building something I actually want to use.
Kryonsec.
An attempt to give builders a security team before they have to learn the hard way why they needed one.
Gonchi Joshna Vardhan Reddy
team: Digital Priates
ho by the way kryonsec is live at kryonsec.in
@WeMakeDevs @polaris_code @awsdevelopers@kunalstwt @HiteshChudhary @BharatBuildTour
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article