Privacy Please

Send us Fan Mail Jacob Coxon spent three years doing pretraining research at OpenAI and then Anthropic. This week he resigned and posted a seven-part thread claiming neither company is acting responsibly with how fast they're racing toward self-improving AI. It hit 100 million views in a day. This episode covers what he actually said, how Anthropic's own alignment science lead responded (and the important nuance buried in that response), the questions worth asking about Coxon's timing and incentives, a fair skeptic's rebuttal, and the AI safety legislation already moving in Congress as a result. One thing on the title: it's a real quote, but it's Hubinger's general belief statement, not his assessment of present-day risk — he separately said present-model risk is low. Your own episode makes that distinction carefully. Worth a one-line callout in your pinned comment or community post after it's live, so the title doesn't end up being the thing people push back on in the comments before they've actually watched. Support the show

Send us Fan Mail Flock Safety's automated license plate readers are in over 5,000 communities and used by more than 40,000 cameras nationwide — sold to cities as a tool to catch car thieves and find missing people. But a Washington Post investigation found at least 50 officers accused of misusing the system, most of them to track romantic partners. This episode covers: The scale of Flock's network and how warrantless searches are legally justified Individual abuse cases in Wichita, Milwaukee, and New Bedford The Texas sheriff's office case tied to reproductive-related searches 404 Media's reporting on ICE's informal access to Flock data despite no official contract Flock's "Freeform" search feature and the race/ethnicity flagging controversy CEO Garrett Langley's August 13 apology and the new audit reforms The historical parallel: NSA's "LOVEINT" scandal from the Snowden leaks What's actually working: 39+ contracts canceled by cities in 2026 3 concrete steps if your town has these cameras flock safety, flock cameras, license plate reader, ALPR, police surveillance, data privacy, police stalking, automated license plate reader, mass surveillance, privacy please podcast, cybersecurity, ICE surveillance, police misconduct, LOVEINT Support the show

Send us Fan Mail Jonathan Sander is back on Privacy Please — and he's brought two blog posts worth arguing about. Sander (42 Notions, now in an operational role at Myota) joins Cam and Gabe to dig into why ransomware resilience should work like New York City's storm surge infrastructure — building something that pays off before disaster strikes, not just a wall you wait behind. Then the conversation turns to AI agents: why Sander tried and failed to build a clean taxonomy for them, the six dimensions he landed on instead (authority, execution location, trigger, persistence, delegation, tool reach), and why the "hybrid agent" — switching between acting on your behalf and acting with power you never had — might be the hardest identity problem in security right now. Also covered: why "back to basics" (secrets, resilience, identity) is Sander's answer for teams panicking about AI, and a real story about an AI agent that deleted a Postgres database and just... apologized. Articles referenced: Ransomware Doesn't Have to Hit Like a Hurricane (Myota): https://www.myota.io/articles/ransomware-doesnt-have-to-hit-like-a-hurricane Why We Need an AI Agent Taxonomy Right Now But We Can't Have One (42 Notions): https://blog.42notions.com/why-we-need-an-ai-agent-taxonomy-right-now-but-we-cant-have-one/ Chapters: 00:00 – Catch-up with Sander 14:30 – The hurricane analogy: why Myota built resilience instead of a wall 20:30 – What actually makes Myota different from standard backup/cyberstorage 22:15 – Why you can't build a clean AI agent taxonomy (and the six dimensions Sander landed on instead) 28:50 – The hybrid agent problem: acting "on behalf of" vs. "for the benefit of" 45:10 – Sander's one takeaway: get the basics right before chasing the AI hype Support the show

Send us Fan Mail Full Show Notes This week on Privacy Please, Cam breaks down four stories that all come back to one theme: choice. GigaWiper — Microsoft researchers uncovered a new backdoor malware built from pieces of older malware families, giving attackers the ability to decide after they're already inside a network how they want to cause damage — from low-level disk wipes to fake ransomware with encryption keys that are never even saved. Multiple security firms are independently tracking it, with no group attribution yet. Connecticut's new AI disclosure law — As of July 1st, companies covered by Connecticut's privacy law must clearly disclose whether their data is used to train large language models like ChatGPT, Gemini, DeepSeek, or Grok. Cam digs into why "disclosure" doesn't always mean "clarity," and what to actually look for in a privacy policy update. California's Delete Act (DROP) — A correction and a deep dive: DROP has been live since January 1st, not launching in August as previously stated. What actually changes on August 1st is enforcement — the date data brokers become legally required to act on deletion requests. Cam walks through exactly how to submit one at privacy.ca.gov. The Phantom Hacker gold bar scam — A 78-year-old Phoenix woman nearly lost $600,000 in gold bars to a scammer posing as a federal official — until she turned the tables and called the FBI herself. Cam covers the arrest, the courier-for-hire business model behind it, and the billion-dollar scale of phantom hacker scams since 2024. Tips for this episode: Back up your data offline — wipers don't negotiate, there's no ransom to pay your way out Search privacy policy updates for "train," "AI," or "language model" before skimming past them California residents: submit a DROP request now at privacy.ca.gov so it's queued before enforcement begins on August 1st No real government agency will ever tell you to convert your money to gold, crypto, or gift cards — hang up and call the agency back yourself Sources referenced: Microsoft Security research on GigaWiper Connecticut Data Privacy Act (CTDPA) amendment, effective July 1, 2026 California Delete Act / DROP platform, cppa.ca.gov FBI IC3 reporting on Phantom Hacker and gold bar scams AZFamily coverage of the Gary Christopher arrest, Phoenix Sky Harbor Airport Chapter Timestamps 00:00 – Cold Open 01:30 – GigaWiper: Choose-Your-Own-Destruction Malware 04:00 – Connecticut's LLM Data Disclosure Law 06:15 – California's Delete Act & DROP Platform 08:30 – The Phantom Hacker Gold Bar Scam 11:30 – Recap & Close Support the show

Send us Fan Mail Last year, every major outlet ran the same story: 16 billion passwords exposed. Apple. Google. Facebook. The largest breach in history. It was overblown. Security experts tore it apart within 48 hours. But here's the thing: the real story underneath that headline is actually scarier. And nobody covered it. It's called infostealer malware. It's been quietly running on millions of devices — stealing passwords, bypassing MFA, and feeding an underground credential economy that's behind nearly every major breach of the last two years. Ticketmaster. AT&T. Coinbase. All of it traces back here. In this episode, I dig back into that story and break down: Why the 16 billion number was a "fearset, not a dataset" What infostealer malware actually is and how it gets on your device Why MFA doesn't fully protect you from this (and what does) The underground marketplace where your stolen credentials are sold within 48 hours The stat that should genuinely keep you up at night: 67 seconds Six things you can do right now to protect yourself SHOW NOTES Episode: Your Password Is Already For Sale Last year, the 16 billion password story dominated headlines. The headline was overblown — but the real threat underneath it, infostealer malware, is what nobody talked about. It's an industrial-scale credential theft economy running quietly in the background, and it's the engine behind almost every major data breach of the last two years. We dug back into it because it's only gotten worse. Resources mentioned: Check if your email has been breached: haveibeenpwned.com Free password manager: bitwarden.com Premium password manager: 1password.com Key sources: Cybernews — original 16 billion credential report (June 2025) CyberScoop — "The 16 billion password breach story is a farce" Flashpoint / DeepStrike — 1.8 billion credentials stolen in 2025 report Microsoft Security Blog — Lumma Stealer breakdown IBM X-Force Threat Intelligence Index 2025 Verizon Data Breach Investigations Report 2025 SANS Institute commentary Connect: 🌐 theproblemlounge.com 📺 YouTube: The Problem Lounge Network Support the show

Send us Fan Mail Gabe and I dig into Shiny Hunters and why the scariest cyberattacks now look like ordinary logins instead of dramatic break-ins. We map how credential theft, social engineering, and SaaS data exports turn basic security hygiene into the difference between a close call and a headline. • Shiny Hunters’ scale, loose structure, and why takedowns rarely stick • Why ransomware and extortion keep growing as a business model • How the tactics evolve from Microsoft 365 and developer creds to SaaS platforms like Salesforce • Credential stuffing, vishing, and smishing as “low-friction” intrusion paths • The Snowflake-style failure mode of missing MFA and weak password practices • Password reuse and how consumer breaches can cascade into enterprise access • Data retention and why old records increase privacy risk • Vendor risk and the shared responsibility model for identity and data • Practical steps that improve security without relying on perfect users If you guys have not been to our website, theproblemlounge.com, check it out. Got some new blogs up there. Sign up for the newsletter. Support us, follow us. Let’s get this out to more people. Support the show

Send us Fan Mail SHOW NOTES The Pornhub breach is being reported as a data story. It's actually a story about shame as a weapon. In December 2025, a hacker group called ShinyHunters claimed to have stolen 200 million records from Pornhub Premium users — including email addresses, locations, and intimate watch and search history. They sent extortion demands. The data was verified as real. In this episode of Privacy Please, Cameron Ivey breaks down: ✅ What was actually stolen — and why it's worse than most breaches ✅ The three-way blame game between Pornhub, Mixpanel, and a mysterious 2023 employee access ✅ Why ShinyHunters is one of the most dangerous and active hacker groups operating right now ✅ The bigger question nobody's asking: why does this data still exist? ✅ Five things you can do right now to protect yourself 🔗 RESOURCES MENTIONED: Check your email in breaches: haveibeenpwned.com Freeze your credit: annualcreditreport.com (links to all three bureaus) Data removal: DeleteMe — joindeleteme.com Follow the reporting: bleepingcomputer.com | malwarebytes.com/blog 📰 SOURCE REPORTING: BleepingComputer — ShinyHunters extortion demand (December 2025) Malwarebytes — Pornhub/Mixpanel/SoundCloud breach roundup Euronews — Pornhub investigation coverage Reuters — user data verification Panda Security — breach overview 🎙️ Privacy Please is part of the Problem Lounge Network 🌐 theproblemlounge.com 📺 YouTube: The Problem Lounge Network If this one hit different — share it. Support the show

Send us Fan Mail In this episode of Privacy Please, Cameron Ivey investigates Palantir Technologies — a data analytics company founded in 2003 with CIA backing that has quietly become embedded across nearly every major arm of the U.S. federal government. This week's investigation covers: The USDA Deal On April 22nd, the Department of Agriculture signed a $300 million blanket purchase agreement with Palantir to build "One Farmer, One File" — a unified digital profile for every American farmer. The deal was awarded without competitive bidding. The IRS Bombshell The same week, The Intercept revealed — based on documents obtained by watchdog group American Oversight — that Palantir has been running financial crime surveillance operations inside the IRS since 2018. The IRS has paid Palantir over $130 million for access to a platform that cross-references bank records, tax filings, transaction histories, and more across millions of Americans. The Immigration Enforcement Machine Palantir's ICE contracts — now over $145 million — power the agency's case management, deportation targeting, and real-time location tracking of immigrants. A tool called ELITE creates individual dossiers on deportation targets by pulling data from the Department of Health and Human Services. The Pushback That's Working New York City's public hospital network canceled its Palantir contract after community organizing and City Council pressure. In the UK, 229,000 people have signed petitions to remove Palantir from the National Health Service. Public pressure is moving the needle. Five Things You Can Do Right Now Cameron closes with specific, actionable steps every listener can take — from requesting your IRS transcript to freezing your credit to contacting your representative about sole-source contracting. Privacy Please is part of the Problem Lounge Network. New episodes weekly. theproblemlounge.com Chapter Markers 00:00 — Cold Open 01:30 — Intro & Show Welcome 02:45 — Act One: The USDA Deal 06:00 — Act Two: Who Is Palantir? 11:30 — Act Three: The Empire Expands (ICE, Policing) 17:00 — Act Four: Your Tax Returns Are In There Too 24:00 — Act Five: The Layer Nobody's Talking About 30:00 — Act Six: The Part That Gives Me Hope 34:30 — What You Can Actually Do (5 Tips) 39:00 — Closing Reflection (Adjust timestamps after editing) Support the show

Send us Fan Mail A normal data breach steals names and passwords. This one may have stolen the recipe for building the world’s most powerful AI models, and it happened through software most people will never notice until it breaks. We follow the Mercor breach from the first warning signs to the moment poisoned Python packages hit PyPI and spread in minutes across systems that were set to auto-update. We walk through what Mercor actually does in the AI economy, especially RLHF (Reinforcement Learning from Human Feedback), and why that behind-the-scenes work shapes how tools from OpenAI, Anthropic, Meta, and Google behave. Then we unpack Lite LLM, the open source “plumbing” that connects apps to multiple AI services, and how a supply chain attack can bypass the company you’re targeting by compromising the dependencies everyone trusts. From there, the focus shifts to the fallout: contractors whose Social Security numbers and identity documents may be exposed, companies scrambling to assess backdoors and credential theft, and the bigger fear that proprietary AI training data sets and labeling strategies are being auctioned on the dark web. We also dig into the compliance controversy around SOC2 and ISO 27001 style certifications and what happens when security audits become performance instead of protection. If you care about cybersecurity, data privacy, AI governance, and open source risk, listen through to the end for concrete steps you can take right now. Subscribe, share this with a friend who uses AI tools, and leave a review with your take on who should be held accountable. Support the show

Send us Fan Mail You already knew you were the product. But did you know you're also the teacher? Companies are quietly feeding your emails, your work decisions, your customer interactions, and your daily patterns into AI systems — systems designed to automate exactly what you do. And most people have no idea it's happening. In this episode of Privacy Please, we break down how it works, who's doing it, why your right to delete your own data is functionally broken in the AI era, and what you can actually do about it. What we cover: How "function creep" turns your data into AI training fuel without new consent The GitHub policy change that's happening right now — and how to opt out Why employees at Amazon, Google, and JPMorgan described training AI as "building your own coffin." The deletion problem — why you can't remove yourself from a trained model Practical steps to audit your tools and protect yourself today Links: GitHub opt-out: github.com/settings/copilot/features Khan v. Figma lawsuit: rainintelligence.com FTC on AI data practices: ftc.gov Check your state privacy rights: iapp.org/resources/article/us-state-privacy-legislation-tracker Delete old posts: redact.dev Privacy Please is part of The Problem Lounge network. 🌐 theproblemlounge.com 🎙️ Subscribe on Apple Podcasts, Spotify, or wherever you listen Support the show

Send us Fan Mail Your anonymous account isn't anonymous anymore. Researchers just proved it costs $4 to find out who you are. In February 2026, a team from ETH Zurich and Anthropic published a paper that quietly ended the era of practical online anonymity. Their AI pipeline, using nothing but your posts, comments, and forum activity, correctly identified 67% of pseudonymous users from a pool of 89,000 candidates. No name. No photo. No metadata. Just your words. This episode breaks down exactly how it works, why it's different from every deanonymization scare before it, who's most at risk, and what you can actually do about it. In this episode: How the ESRC pipeline (Extract, Search, Reason, Calibrate) works Why previous anonymity attacks required structured data, and this one doesn't Why commercial AI safety guardrails didn't stop it What "practical obscurity" meant, and why it's gone Concrete steps to reduce your exposure today Links: Research paper: arxiv.org/abs/2602.16800 Delete your Reddit history: redact.dev Tor Project: torproject.org Signal: signal.org Privacy Please is part of The Problem Lounge network. 🌐 theproblemlounge.com 🎙️ Subscribe on Apple Podcasts, Spotify, or wherever you listen Support the show

Send us Fan Mail Cameron and Gabe sit down with Girish Redekar, co-founder and CEO of Sprinto, to pull back the curtain on one of the most misunderstood areas of security: compliance. Girish built his first startup, RecruiterBox, to 3,500 customers before selling it, and it was the painful, expensive, duct-taped compliance process he experienced firsthand that sparked the idea for Sprinto. Today, Sprinto helps companies move beyond point-in-time audits into something far more valuable: continuous, autonomous trust. In this episode, we dig into: Why passing a SOC 2 or ISO 27001 audit doesn't mean you're actually secure The three stages of compliance maturity — and how to climb them What "compliance debt" is and why it's quietly eating your business How smart CISOs use their security posture as a revenue driver , not a back-office cost center The "$100/month" challenge: what actually moves the needle for startups How AI is reshaping compliance programs — for better or worse Why Girish spent over a year talking to customers before writing a single line of code Plus: the "sell more jeans" framework every CISO should know, Rich Hickey, The Mom Test, and the toilet paper question. 🔗 Find Sprinto at sprinto.com Support the show

Send us Fan Mail How a Super Bowl dog commercial accidentally revealed America's surveillance infrastructure A family loses their dog. Ring runs a Super Bowl ad. America collectively goes "wait… what?" This week, we're digging into Ring's "Search Party" feature, the AI-powered doorbell camera tool that lit up millions of living rooms during the big game and immediately made privacy experts lose their minds. Because what looked like a heartwarming story about finding your lost lab was actually a live demonstration of a nationwide networked surveillance system most people didn't know they were part of. We follow the trail from the commercial to the backlash, from a secret police surveillance partnership that quietly got canceled mid-chaos, to an 84-year-old woman's "deleted" doorbell footage that the FBI recovered anyway. There's a lost dog. There's Amazon. There's a company called Flock Safety that you need to know about. And there's a question worth asking before you go home and look at your front door. They sold you a puppy. They built a network. Support the show

Send us Fan Mail Autonomy sounds like progress until the system turns your choices against you. We dive into how AI agents change the risk equation, why “don’t trust, verify” now beats “trust but verify,” and what to do when the update button itself becomes the attack vector. We start with the Ivy League leak tied to Harvard and UPenn, where attackers exposed admissions hold notes that map influence rather than credit cards. That context turns routine records into leverage for extortion, social pressure, and geopolitical targeting. From there, we trace the surge of agentic AI in the workplace as employees paste code, legal docs, and sensitive files into chat interfaces. The real accelerant is MCP, the model context protocol that standardizes connections across Google Drive, Slack, databases, and more. Like USB for AI, MCP makes integration simple and powerful, but a single prompt injection can pivot across everything the agent can reach. Security gets messier with supply chain compromise. A China‑nexus campaign allegedly hijacked the Notepad++ update mechanism, handing a bespoke backdoor to developers who did the right thing. We unpack how to keep patching while reducing risk: signed updates, independent checksum checks, tight egress policies for updaters, and strong monitoring around update flows. On the policy front, Rhode Island’s vendor transparency rule forces companies to name who buys data. It is a nutrition label for privacy, and it lets users and watchdogs finally connect the dots between friendly interfaces and aggressive brokers. We close with concrete defenses that raise the floor. Move high‑value accounts to FIDO2 hardware keys or platform passkeys to block phishing at the protocol level. Scope agent permissions narrowly, isolate MCP connectors by function, and require explicit approvals for sensitive actions. Log everything an agent touches and review those trails. Autonomy should be earned, minimal, and observable. If AI is going to act on your behalf, it must prove itself at every step. If this conversation helps you think differently about agents, influence mapping, and how to lock down your stack, subscribe, share with a teammate, and leave a quick review telling us the one control you plan to implement this week. Support the show

Send us Fan Mail We kick off season seven with a tour of the year’s early privacy & security news: neighborhood watchtowers from Ring, a rival-led hack of Breach Forums, a massive stitched leak in France, a heavy Microsoft patch drop, AI agents on the rise, and new state privacy laws. We share practical steps: self-host cameras, freeze your credit, harden identity portals, and keep humans in the loop when AI handles sensitive data. • CES unveils Ring’s neighborhood watchtower and its surveillance tradeoffs • Why self‑hosted DVR systems beat cloud video for privacy • Breach Forums doxxed by rivals and lessons in OPSEC • France’s 45 million record “combo” leak and re‑identification risks • Credit freezes, hard vs soft inquiries, and portal security • Microsoft’s 114 patches and sane patch management • AI agents escalating breach risk and human‑in‑the‑loop controls • New privacy laws in Indiana, Kentucky, and Rhode Island and actionable rights Please go to theproblemlounge.com and sign up for the newsletter If you have guests or topics or anything, please reach out to us! Support the show

Send us Fan Mail We look back at 2025’s privacy and security reality: useful AI where data was ready, repeating breach patterns, and infrastructure limits that slowed the hype. We call out backdoors, weak 2FA, and the shift toward passkeys, decentralization, and owning more of our stack. • AI succeeds when data, process and governance are mature • Power, chips and cost constraints limit AI growth • SALT Typhoon shows backdoor risk and patching failures • SMS 2FA remains weak while passkeys gain ground • Data hoarding expands breach blast radius • Streaming consolidation drives algorithm control and piracy’s return • Decentralization and self‑hosting rebuild trust with users • 2026 outlook: AI contraction, ML pragmatism, fewer but stronger tools Check out our website: the problemlounge.com If you have episode guest ideas or topics you want us to talk about, please send them our way Go check out YouTube channel, Privacy Please Podcast In 2026, would you like to see us do live streams? Support the show

Send us Fan Mail It is Monday, December 15th, and the battle for Hollywood has officially gone nuclear. What started as an $82 billion acquisition by Netflix has morphed into a $108 billion hostile takeover battle with Paramount Skydance. As of this morning, stocks are volatile, the government has frozen the deal, and a massive Class Action Lawsuit has just been filed to burn it all down. In this Special Report from Privacy Please, we break down the chaos of the last 72 hours. We uncover the "National Security" weapon Netflix is using to kill the deal, the foreign money backing Paramount, and the leaked memos that reveal why executives are selling you out. No matter who wins—the Algorithm or the Oligarchs—your privacy is the casualty. Time Stamps / Key Moments: 0:00 - Monday Morning Chaos: Stocks Halted & The $108B Counter-Bid 2:15 - Future A vs. Future B: The Algorithm Era vs. The Oligarch Era 5:30 - BREAKING: The "National Security" Argument & Class Action Lawsuit 8:45 - Leaked Memos: The "Golden Parachute" Betrayal 11:20 - The Fallout: Why Streaming Prices Will Hit $35/Month What you'll uncover in this deep dive: The Weekend of Chaos: A complete timeline of how Netflix lost control of the deal over the weekend. The "Foreign Money" Threat: Why Paramount's backing by sovereign wealth funds has regulators panicked. Netflix's Hypocrisy: How the surveillance giant is weaponizing "privacy" to stop their competitors. The Consumer Cost: Why the era of cheap streaming is officially dead. Join the Community: We are building a community dedicated to navigating these complex digital issues. Website & Newsletter: https://www.theproblemlounge.com Support the Show: http://buzzsprout.com/622234/support Don't forget to Like, Comment, and Subscribe! Your support helps us uncover the stories Big Tech wants to hide. #WarnerBros #Netflix #Paramount #StreamingWars #PrivacyPlease #Antitrust #FTC #DataPrivacy #Hollywood #BreakingNews #ClassAction #StockMarket Support the show

Send us Fan Mail A week where the lawful intercept backdoor became the front door, a supply chain hop hit 200+ companies, a bargain app faced a malware lawsuit, and a university breach turned into a donor-targeting roadmap. We share simple moves to lower risk fast and set guardrails that actually hold. • Salt Typhoon abusing CALEA at major US telecoms • Negligence, unpatched routers and weak passwords • Why SMS is transparent and how to switch to Signal • Kill SMS 2FA and use authenticators or YubiKey • Gainsight-to-Salesforce island hopping at scale • Audit connected apps and revoke stale API keys • Arizona AG lawsuit calling Timu malware • Shop via browser sandbox and use masked payments • UPenn donor data leak and Oracle exploit • Whaling protections with voice verification and data scrubbing • Practical recap: trust nothing, verify everything Please follow us or subscribe on your podcast app, and watch the video on our YouTube or at theproblemlounge.com. If you have topics or guest ideas, we would love to hear from you Support the show

Send us Fan Mail A sleepless night, a soft prompt, and a flood of relief—the rise of AI therapy and companion apps is rewriting how we seek comfort when it matters most. We explore why these tools feel so human and so helpful, and what actually happens to the raw, intimate data shared in moments of vulnerability. From CBT-style exercises to memory-rich chat histories, the promise is powerful: instant support, lower cost, and zero visible judgment. The tradeoff is less visible but just as real—monetization models that thrive on sensitive inputs, “anonymized” data that can often be re-identified, and breach risks that turn private confessions into attack surfaces. We dig into the ethical edge: can a language model provide mental health care, or does it simulate empathy without the duty of care? We look at misinformation, hallucinated advice, and the way overreliance on AI can delay genuine human connection and professional help. The legal landscape lags behind the technology, with HIPAA often out of scope and accountability unclear when harm occurs. Still, there are practical ways to reduce exposure without forfeiting every benefit. We walk through privacy policies worth reading, data controls worth using, and signs that an app takes security seriously, from encryption to third‑party audits. Most of all, we focus on agency. Use AI for structure, journaling, and small reframes; lean on people for crisis, nuance, and real relationship. Create boundaries for what you share, separate identities when possible, and revisit whether a tool is helping you act or just keeping you company. If you’ve ever confided in a bot at 2 a.m., this conversation gives you the context and steps to stay safer while still finding support. If it resonates, subscribe, share with a friend who might need it, and leave a review to help others find the show. Support the show

Send us Fan Mail In this episode of Privacy Please, host Cameron Ivey discusses significant security threats, including a critical vulnerability in Microsoft's WSUS, a major data breach at the University of Pennsylvania, and the emergence of sophisticated malware known as Glassworm. The conversation highlights the importance of cybersecurity measures and the potential consequences of negligence in IT security. Support the show