All activity
Anastarted a discussion
How are you dealing with vibe coding security risks in AI-generated code?
I’ve been using a lot of AI-generated code lately, and while it definitely speeds things up, security feels like a weak spot. I’ve run into issues like missing auth, exposed endpoints, and weak configs stuff that AI doesn’t really flag unless you explicitly ask. Curious how others are handling this: Do you rely more on manual reviews or tools? Any workflows that consistently catch...
Analeft a comment
Totally relatable. AI speeds things up, but security is where it falls short I’ve seen issues like exposed endpoints, weak auth, and misconfigured services way too often. What works for me is treating AI code as a draft, then doing manual security reviews + running basic scans (SAST, dependency checks). Also relying on standard security practices instead of AI suggestions. Your Elastic example...
How do you make sure your products are secure after vibecoding it entirely or partially?
ConstantineJoin the discussion