VibeDefend by CybeDefend

The one command line to secure your Cursor and Claude Code

Developer Tools

Security

Vibe coding

Visit WebsiteSee on Product Hunt

A request for securing Cursor and Claude Code is a good sell but how about its ability to work in a repo that has a tangled history? Does it need a clean history to extract relevant patterns or works from Day 1?

It pleases me that it happens before the command runs and not afterwards. Catching an errant rm -rf before it goes off is precisely what I want my coding agent to do.

@julien_zammit @florentin_ledy and @axel_paulin good start and it says something about your confidence in the product when all of you are responding to comments with actual facts rather than talking points. The line I found compelling was "the rule you never wrote down" as this is the true failure case for most teams, not the vulnerability that is scanned for.

As I went through the review posted by Olivier, what caught my attention was the fact that his criticism about how UI still requires many clicks for manual resolution is actually far more valuable than all the fluff written in the review; this is because he actually uses the software on a daily basis.

The Florentin point on the cross-user data leak vulnerability is indeed the true point. Injections will always be detected by all the scanners. No context will ever have "user A should not see user B data" unless someone adds it.

The "88%" figure used by Axel in his discussion post is difficult to comprehend but it seems accurate, as agents act quickly and ignore laws that have not been formally documented.

From reading the origin story to the "all the apps I scanned were hackable in five minutes" quote, I was left thinking about how this is probably true of many repositories that I have worked with myself. Since there is no card required, this would be my first place to try it out, without the purchase discussion.

The rm -rf and secrets guard is what really sealed the deal for me. All other tools scan after the problem happens; this stops it in its tracks. Today’s product would really enable us to reach the right people.

the 88% to 89% jump is the number I'd want more detail on, not because it's small, but because it implies 11% of cases still slip through even with the agent governed at write-time. what does that residual 11% look like in practice, is it mostly novel command patterns your ruleset hasn't seen yet, or edge cases where the agent works around the guard through a legitimate-looking path (like writing to a file that gets executed later instead of running the command directly)?

Being on the AWS marketplace makes procurement so much easier, smart move 🙃

Mining rules from the repo worries me a bit on older codebases. I audited one last month where four different places decided who counts as an admin, and they disagreed: two lower cased the email, two didn't. "Most consistent convention" there is a two against two tie, and either winner is a bug.

Does the miner flag contradictions like that for a human, or pick one? I'd rather get the list of disagreements than the rules.

What if there is a conflict between the security directive and the instruction from the developer to the agent?
Btw, Congratulations Team VibeDefend by CybeDefend ✌️

Hey! Solid launch! I wonder how can I integrate this application into my current setup

great to have new security products in the devtools space. I love that you have dedicated comparison pages for existing tools - really easy to differentiate. kudos on the launch!

Quick update for the community! 📣

Seeing all the great discussions today in the comments about the risks of AI coding agents (like data leakage and compliance rules), I thought this would be the perfect place to share an upcoming event we are super excited about.

We’re hosting a live webinar with Jason Lee (former CISO at Zoom, Splunk, and F5) entirely dedicated to the security of AI coding agents. We'll be diving deep into how engineering teams can actually scale these autonomous tools safely without giving the security team a heart attack.

If today's launch caught your interest and you want to dig deeper into the topic with a top-tier cybersecurity expert, we'd love to have you join the conversation.

You can grab your spot right here: https://www.cybedefend.com/en/webinar

Would love to see some of you there! Let me know if there are specific questions you'd like us to ask him. 👇

Does the secrets scanner also check files that are generated or modified indirectly by the coding agent?

Can teams define their own blocked commands based on their internal security policies?