Search a title or topic

Over 20 million podcasts, powered by 

Player FM logo
Artwork

Content provided by Chatcyberside. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Chatcyberside or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://podcastplayer.com/legal.
Player FM - Podcast App
Go offline with the Player FM app!

Vibe Hacking: The Dark Side of AI Coding

27:47
 
Share
 

Manage episode 508043767 series 3625301
Content provided by Chatcyberside. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Chatcyberside or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://podcastplayer.com/legal.

What happens when the same AI tools that make coding easier also give cybercriminals new powers? In this episode of Cyberside Chats Live, we explore the rise of “vibe coding” and its darker twin, “vibe hacking.” You’ll learn how AI is reshaping software development, how attackers are turning those vibes into cybercrime, and what it means for the future of security.

Key Takeaways

  1. Establish ground rules for AI use
    • Even if you don’t have developers, employees may experiment with AI tools. Set a policy for how (or if) AI can be used for coding, automation, or day-to-day tasks.
    • Make sure staff understand not to paste sensitive data (like credentials or customer info) into AI tools.
  2. Strengthen your software supply chain
    • If you rely on vendors or contractors, ask them whether they use AI in their development process and how they vet the resulting code.
    • Request (or create) an inventory of software components and dependencies (SBOMs) so you know what’s inside the software you buy.
    • Stay alert to supply chain risks from open-source code or third-party add-ons.
  3. Treat your endpoints like crown jewels
    • Limit what software employees can install, especially IT staff.
    • Provide a safe “sandbox” machine for testing unfamiliar tools instead of using production systems.
    • Apply strong endpoint protection and restrict administrative privileges.
  4. Prepare for AI-related incidents
    • Include scenarios where AI is part of the attack, such as compromised development tools, malicious packages, or data fed into rogue AI systems.
    • Plan for vendor incidents, since third-party software providers may be the first link in a compromise.
    • Test these scenarios through tabletop exercises so your team knows how to respond.

References

#AIhacking #AIcoding #vibehacking #vibecoding #cyberattack #cybersecurity #infosec #informationsecurity #datasecurity

  continue reading

49 episodes

Artwork
iconShare
 
Manage episode 508043767 series 3625301
Content provided by Chatcyberside. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Chatcyberside or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://podcastplayer.com/legal.

What happens when the same AI tools that make coding easier also give cybercriminals new powers? In this episode of Cyberside Chats Live, we explore the rise of “vibe coding” and its darker twin, “vibe hacking.” You’ll learn how AI is reshaping software development, how attackers are turning those vibes into cybercrime, and what it means for the future of security.

Key Takeaways

  1. Establish ground rules for AI use
    • Even if you don’t have developers, employees may experiment with AI tools. Set a policy for how (or if) AI can be used for coding, automation, or day-to-day tasks.
    • Make sure staff understand not to paste sensitive data (like credentials or customer info) into AI tools.
  2. Strengthen your software supply chain
    • If you rely on vendors or contractors, ask them whether they use AI in their development process and how they vet the resulting code.
    • Request (or create) an inventory of software components and dependencies (SBOMs) so you know what’s inside the software you buy.
    • Stay alert to supply chain risks from open-source code or third-party add-ons.
  3. Treat your endpoints like crown jewels
    • Limit what software employees can install, especially IT staff.
    • Provide a safe “sandbox” machine for testing unfamiliar tools instead of using production systems.
    • Apply strong endpoint protection and restrict administrative privileges.
  4. Prepare for AI-related incidents
    • Include scenarios where AI is part of the attack, such as compromised development tools, malicious packages, or data fed into rogue AI systems.
    • Plan for vendor incidents, since third-party software providers may be the first link in a compromise.
    • Test these scenarios through tabletop exercises so your team knows how to respond.

References

#AIhacking #AIcoding #vibehacking #vibecoding #cyberattack #cybersecurity #infosec #informationsecurity #datasecurity

  continue reading

49 episodes

所有剧集

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Copyright 2025 | Privacy Policy | Terms of Service | | Copyright
Listen to this show while you explore
Play