When the government shut down, the Cybersecurity Information Sharing Act of 2015 expired with it. That law provided liability protections for cyber threat information sharing and underpinned DHS’s Automated Indicator Sharing (AIS) program, which costs about $1M a month to run. Is it worth the cost? In this episode of Cyberside Chats, Sherri Davidoff and Matt Durrin dig into the value of public-private information sharing, the uncertain future of AIS, and how cybersecurity leaders should adapt as visibility gaps emerge. Along the way, they share a real-world story of how information sharing stopped a ransomware attack in its tracks — and what could happen if those pipelines dry up.

Key Takeaways:

• Strengthen threat intelligence pipelines: Don’t rely solely on AIS or your vendor. Ask providers how they source threat intel and diversify feeds.

• Review liability exposure: With CISA expired, safe harbors are gone — consult counsel before sharing.

• Plan for reduced visibility: Run tabletop exercises simulating loss of upstream intel.

• Get proactive about information exchange: Join ISACs, ISAOs, or local peer groups — and contribute, not just consume.

Resources:

• Reuters: Industry groups worry about cyber info-sharing as key U.S. law set to expire

• U.S. Chamber of Commerce: Letter to Congress on CISA 2015

• Baker McKenzie: CISA Liability Protections Terminate — What Legal & Infosec Need to Know

• Cyberside Chats: Executive Order Shockwave: The Future of Cybersecurity Unveiled

#CybersideChats #CISA #CISO #cybersecurity #infosec

Scattered Spider is back in the headlines, with two recent arrests — Thalha Jubair in the UK and a teenager in Nevada — bringing fresh attention to one of the most disruptive cybercriminal crews today. But the real story is in the indictments: they offer a rare inside look at the group’s structure, their victims, and the mistakes that led law enforcement to track them down. In this episode, Sherri Davidoff and Matt Durrin break down what the indictments reveal about Scattered Spider’s tactics, roles, and evolution, and what defenders can learn from these cases.

Key Takeaways:

• Lock down your help desk. Require strong, multi-step verification before resetting accounts, and monitor for suspicious or unusual requests.

• Prepare for ransom decisions. Develop playbooks that model both paying and refusing, so leadership understands the financial and operational tradeoffs before an incident hits.

• Get proactive on insider risk. Teens and early-career workers are being recruited in open forums like Telegram and Discord — build awareness and detection into your insider risk program.

• Pressure-test your MFA. Don’t just roll it out — simulate how attackers might bypass or trick staff into resetting it.

• Educate your team on voice social engineering. Scattered Spider relied on phone-based tactics; training staff to recognize and resist them is critical. (LMG Security offers targeted social engineering training to help your team prepare.)

Resources:

• BleepingComputer: “US charges UK teen over Scattered Spider hacks including US Courts” https://www.bleepingcomputer.com/news/security/uk-arrests-scattered-spider-teens-linked-to-transport-for-london-hack/

• “The Rabbit Hole Beneath the Crypto Couple is Endless” https://www.vice.com/en/article/the-rabbithole-beneath-the-crypto-couple-is-endless

• MGM Breach: A Wake-up Call for Better Social Engineering Training for Employees https://www.lmgsecurity.com/2023-mgm-breach-a-wake-up-call-for-better-social-engineering-training-for-employees/

• DOJ press release on the indictment of five Scattered Spider members (Nov 2024) – https://www.justice.gov/usao-cdca/pr/5-defendants-charged-federally-running-scheme-targeted-victim-companies-phishing-text

• DOJ press release on UK national Thalha Jubair charged in multiple attacks (Sept 2025) – https://www.justice.gov/opa/pr/united-kingdom-national-charged-connection-multiple-cyber-attacks-including-critical

#cyberattack #cybersecurity #cybercrime #informationsecurity #infosec #databreach #databreaches #ScatteredSpider

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

• Malwarebytes — Claude AI chatbot abused to launch cybercrime spree (Aug 2025): https://www.malwarebytes.com/blog/news/2025/08/claude-ai-chatbot-abused-to-launch-cybercrime-spree

• Trend Micro / Industrial Cyber — EvilAI malware campaign exploits AI-generated code to breach global critical sectors (Aug 2025): https://industrialcyber.co/ransomware/evilai-malware-campaign-exploits-ai-generated-code-to-breach-global-critical-sectors/

• The Hacker News — Cursor AI code editor flaw enables silent code execution on developer systems (Sept 2025): https://thehackernews.com/2025/09/cursor-ai-code-editor-flaw-enables.html

• PCWorld — I saw how an “evil” AI chatbot finds vulnerabilities. It’s as scary as you think (May 2025): https://www.pcworld.com/article/2424205/i-saw-how-an-evil-ai-chatbot-finds-vulnerabilities-its-as-scary-as-you-think.html

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

When we first covered the Salesforce–Drift breach, we knew it was bad. Now it’s clear the impact is even bigger. Hundreds of organizations — including Cloudflare, Palo Alto Networks, Zscaler, Proofpoint, Rubrik, and even financial firms like Wealthsimple — have confirmed they were affected. The root cause? A compromised GitHub account that opened the door to Drift’s AWS environment and gave attackers access to Salesforce and other cloud integrations.

In Part 2, Sherri Davidoff and Matt Durrin dig into the latest updates: what’s new in the investigation, why more victim disclosures are coming, and how the GitHub compromise ties into a wider trend of supply chain attacks like GhostAction. They also share practical advice for what to do if you’ve been impacted by Drift — or if you want to prepare for the next third-party SaaS compromise.

Tips for SaaS Incident Response:

1. Treat this as an incident: don’t wait for vendor confirmation before acting. There may be delays in vendor disclosure, so act quickly.
2. Notify your cyber insurance provider:
   • Provide notice as soon as possible.
   • Insurers may share early IOCs, coordinate with vendors, and advocate for your org alongside other affected clients.
   • They can also connect you with funded IR and legal resources.
3. Engage external support:
   • Bring in your IR firm to investigate and document.
   • Work with legal counsel to determine if notification obligations are triggered.
4. Revoke and rotate credentials:
   • Cycle API keys, OAuth tokens, and active sessions.
   • Rotate credentials for connected service accounts.
5. Inventory your data:
   • Identify what sensitive Salesforce (or other SaaS) data is stored.
   • Check whether support tickets, logs, or credentials were included.
6. Search for attacker activity:
   • Review advisories for malicious IPs, user agents, and behaviors.
   • Don’t rely solely on vendor-published IOCs — they may be incomplete.

References:

• Google Cloud Threat Intelligence Blog – Data theft in Salesforce instances via Salesloft Drift

• BleepingComputer – Salesloft March GitHub repo breach led to Salesforce data theft attacks

• Dark Reading – Salesloft breached GitHub account compromise

• BleepingComputer – Hackers steal 3,325 secrets in GhostAction GitHub supply chain attack

• LMG Security Blog – Third-Party Risk Management Lessons

#salesforcehack #salesforce #SalesforceDrift #cybersecurity #cyberattack #databreaches #datasecurity #infosec #informationsecurity

A single weak app integration opened the door for attackers to raid data from some of the world’s largest companies. Salesforce environments were hit hardest—with victims like Cloudflare, Palo Alto Networks, and Zscaler—but the blast radius also reached other SaaS platforms, including Google Workspace. In this episode of Cyberside Chats, Sherri Davidoff and Matt Durrin break down the Salesforce–Drift breach: how OAuth tokens became skeleton keys, why media headlines about billions of Gmail users were wrong, and what organizations need to do to protect themselves from similar supply chain attacks.

Key Takeaways

• Ensure Vendors Conduct Rigorous Technical Security Testing – Require penetration tests and attestations from third- and fourth-party SaaS providers.

• Limit App Permissions to “Least Privilege” – Scope connected apps only to the fields and objects they truly need.

• Implement Regular Key Rotation – Automate key rotation with vendor tools (e.g., AWS recommends every 60–90 days) to reduce the risk of leaked or stolen keys.

• Monitor for Data Exfiltration – Watch for unusual queries, spikes in API usage, or large Bulk API jobs.

• Limit Data Exfiltration Destinations – Restrict where exports and API jobs can go (approved IPs or managed locations).

• Integrate SaaS Risks into Your Incident Response Plan – Include guidance on rapidly revoking or rotating OAuth tokens and keys after a compromise.

References

1. Google Threat Intelligence Group advisory on UNC6395 / Drift OAuth compromise
2. Cloudflare disclosure on the Drift incident
3. Zscaler security advisory on Drift-related Salesforce breach
4. LMG Security Blog – Third-Party Risk Management Lessons

#Salesforcehack #SalesforceDrift #cybersecurity #cyberattack #cyberaware

Hackers aren’t untouchable—and sometimes, they become the victims. From North Korean operatives getting exposed at DEF CON, to ransomware gangs like Conti and LockBit crumbling under betrayal and rival leaks, the underground is full of double-crosses and takedowns. Now, Congress is even debating whether to bring back “letters of marque” to authorize cyber privateers to hack back on behalf of the United States. Join LMG Security’s Sherri Davidoff and Matt Durrin for a fast-paced discussion of headline cases, the lessons defenders can learn from these leaks, and what the future of hacker-on-hacker warfare could mean for your organization.

Key Takeaways  

1. Don’t mythologize adversaries. State actors and ransomware gangs are fallible; design defenses to exploit their mistakes. 
2. Invest in visibility. Many hacker exposures happened because attackers reused credentials, tools, or infrastructure — the same patterns defenders can detect if monitoring is strong. 
3. Watch for insider threats. Disgruntled employees or partners can dismantle even powerful groups — monitor for early warning signs. 
4. Use leaks for training and education. Incorporate hacker chat logs, playbooks, and leaked toolkits into exercises to build staff skills and awareness. 
5. Adapt your IR playbooks. Align response plans with real-world attacker tactics revealed in leaks — and be ready to update as new intelligence emerges. 

Resources

• TechCrunch: Hackers Breach and Expose a Major North Korean Spying Operation
• TheRegister: Congressman proposes bringing back letters of marque for cyber privateers
• LMG Security: Our Q3 2024 Top Control is Third-Party Risk Management

#Cybersecurity #Cybercrime #CybersideChats #Cyberattack #Hackers #Hacker

On the eve of the Trump–Putin summit, sensitive U.S. State Department documents were left sitting in a hotel printer in Anchorage. Guests stumbled on pages detailing schedules, contacts, and even a gift list—sparking international headlines and White House mockery.

But the real story isn’t just about geopolitics. It’s about how unmanaged printers—at hotels, in home offices, and everywhere in between—remain one of the most overlooked backdoors for data leaks. In this episode of Cyberside Chats, Sherri and Matt unpack the Alaska incident, explore why printers are still a weak spot in the age of remote and traveling workforces, and share practical steps to secure them.

Key Takeaways for Security & IT Leaders

1. Reduce reliance on unmanaged printers by promoting secure digital workflows. Encourage employees to use e-signatures and encrypted file sharing instead of printing.
2. Update remote work policies to cover home and travel printing. Most organizations don’t monitor printing outside the office—explicit rules reduce blind spots.
3. Require secure wiping or destruction of printer hard drives before disposal. Printers retain sensitive files and credentials, which can walk out the door if not properly handled.
4. Implement secure enterprise printing with authenticated release and HDD encryption. Treat printers as endpoints and apply the same safeguards you would for laptops.
5. Train employees to recognize that printers are data risks, not just office equipment. Awareness helps prevent careless mistakes like walk-away leaks or using hotel printers.

Resources

• NPR: Trump–Putin Summit Documents Left Behind in Anchorage Hotel Printer (2025)

• Dark Reading: “Printers’ Cybersecurity Threats Too Often Ignored”

• LMG Security: “Work from Home Cybersecurity Checklist”

A wave of coordinated cyberattacks has hit Salesforce customers across industries and continents, compromising millions of records from some of the world’s most recognized brands — including Google, Allianz Life, Qantas, LVMH, and even government agencies.

In this episode of Cyberside Chats, Sherri Davidoff and Matt Durrin break down how the attackers pulled off one of the most sweeping cloud compromise campaigns in recent memory — using no zero-day exploits, just convincing phone calls, malicious connected apps, and gaps in cloud supply chain security.

We’ll explore the attack timeline, parallels to the Snowflake breaches, ties to the Scattered Spider crew, and the lessons security leaders need to act on right now.

Key Takeaways

1. Use phishing-resistant MFA — FIDO2 keys, passkeys.

1. Train for vishing resistance — simulate phone-based social engineering.

1. Monitor for abnormal data exports from SaaS platforms.

1. Lockdown your Salesforce platform — vet and limit connected apps.

1. Rehearse rapid containment — revoke OAuth tokens, disable accounts fast.

References

• Google - The Cost of a Call: From Voice Phishing to Data Extortion

• Salesforce – Protect Your Salesforce Environment from Social Engineering Threats

• BleepingComputer – ShinyHunters behind Salesforce data theft at Qantas, Allianz Life, LVMH

• TechRadar – Google says hackers stole some of its data following Salesforce breach

• LMG Security Blog – Our Q3 2024 Top Control is Third Party Risk Management: Lessons from the CrowdStrike Outage