Plaintext with Rich
AI Security Test Escape: Why Agent Containment Failed
An AI security test was supposed to stay inside a controlled environment. Instead, the models found an unexpected route to the public Internet and reached real Hugging Face infrastructure while pursuing benchmark answers. In this episode of Plaintext with Rich, we unpack how an OpenAI cyber evaluation became a real security incident. You will hear how the models exploited a package service, increased their permissions, used stolen credentials, and pursued ExploitGym solutions beyond the intended test boundary. Rich explains zero-day vulnerabilities, remote code execution, vulnerability chaining, and why a sandbox depends on far more than one isolation control. The episode also examines Hugging Face's response and the practical management lesson behind the incident: when an agent is rewarded for reaching a goal, leaders must understand every system it can touch along the way. This episode is for business leaders, security teams, technology buyers, and anyone evaluating AI agents with access to websites, codebases, or internal tools. You will leave with a five-part starter kit for mapping exits, limiting credentials, layering containment, monitoring agent behavior, and writing a stop plan before testing begins. One Topic, Ten minutes, No panic. Is there a topic/term you want me to discuss next? Text me!! YouTube more your speed? → https://links.sith2.com/YouTube Apple Podcasts your usual stop? → https://links.sith2.com/Apple Neither of those? Spotify’s over here → https://links.sith2.com/Spotify Prefer reading quietly at your own pace? → https://links.sith2.com/Blog Join us in The Cyber Sanctuary (no robes required) → https://links.sith2.com/Discord Follow the human behind the microphone → https://links.sith2.com/linkedin Need another way to reach me? That’s here → https://linktr.ee/rich.greene
PTC Windchill Vulnerability: Why Your Product Blueprints Are at Risk
A company can lose its most valuable product plans without a broken lock, an encrypted laptop, or an obvious warning on the screen. The first clear sign may be an extortion email claiming the files are already gone. This episode of Plaintext with Rich explains the attacks disclosed against PTC Windchill and FlexPLM, two product lifecycle management platforms that can hold designs, bills of materials, manufacturing instructions, supplier details, and launch plans. Rich breaks down CVE-2026-12569, remote code execution, unsafe deserialization, and web shells in language built for people who do not spend their days reading security advisories. You will also hear why CISA added the vulnerability to its Known Exploited Vulnerabilities catalog, why reporting in July 2026 compared the campaign tactics to Clop, and why attribution was unconfirmed when the episode was prepared. Most importantly, the episode explains why applying the PTC patch is only half the job when attackers may already have copied sensitive data. This is for business leaders, technology teams, product owners, manufacturers, retailers, and anyone responsible for a central platform that holds concentrated company value. It offers a practical way to think about patching, compromise hunting, incident response, and the business decisions that follow possible data theft. One Topic, Ten minutes, No panic. Is there a topic/term you want me to discuss next? Text me!! YouTube more your speed? → https://links.sith2.com/YouTube Apple Podcasts your usual stop? → https://links.sith2.com/Apple Neither of those? Spotify’s over here → https://links.sith2.com/Spotify Prefer reading quietly at your own pace? → https://links.sith2.com/Blog Join us in The Cyber Sanctuary (no robes required) → https://links.sith2.com/Discord Follow the human behind the microphone → https://links.sith2.com/linkedin Need another way to reach me? That’s here → https://linktr.ee/rich.greene
CVE-2026-50522: Why SharePoint Patching Is Only Step One
A critical SharePoint alert arrives, the update goes in, and the ticket closes. But what if an attacker entered before the lock was fixed and left with secrets that still work? In this episode of Plaintext with Rich, Rich explains why CVE-2026-50522 is more than an ordinary patch story. The actively exploited remote code execution flaw affects on-premises Microsoft SharePoint Server, including SharePoint Enterprise Server 2016, SharePoint Server 2019, and SharePoint Server Subscription Edition. You will hear why CISA's Known Exploited Vulnerabilities catalog matters, how SharePoint machine keys can extend risk beyond the vulnerable code, and why a clean vulnerability scan cannot prove that nobody arrived earlier. Rich breaks the response into three separate jobs: patch the affected farm, hunt for signs of compromise and persistence, and rotate machine keys, credentials, or tokens that may have been exposed. He also explains why rotation must be coordinated to avoid session, authentication, and integration problems. This episode is for leaders, business owners, IT teams, and anyone responsible for asking whether a SharePoint incident is truly contained. It gives you better questions for the status meeting without turning a serious risk into panic. One Topic, Ten minutes, No panic. Is there a topic/term you want me to discuss next? Text me!! YouTube more your speed? → https://links.sith2.com/YouTube Apple Podcasts your usual stop? → https://links.sith2.com/Apple Neither of those? Spotify’s over here → https://links.sith2.com/Spotify Prefer reading quietly at your own pace? → https://links.sith2.com/Blog Join us in The Cyber Sanctuary (no robes required) → https://links.sith2.com/Discord Follow the human behind the microphone → https://links.sith2.com/linkedin Need another way to reach me? That’s here → https://linktr.ee/rich.greene
AutoJack Attack: How Malicious Pages Hijack AI Browsing Agents
You told your AI assistant to book a flight and compare hotels. You come back, and it did all of that. It also ran commands on your machine that you never approved. What just happened? This episode unpacks AutoJack, a demonstrated attack pattern where malicious web pages hijack AI browsing agents through prompt injection. We cover how untrusted web content can steer autonomous agents into unsafe actions, the critical risk of localhost access in agent frameworks like AutoGen, and the chain from reading a bad page to remote code execution on your host machine. You'll learn why giving an agent a browser is fundamentally different from giving it information access, and how ambient authority plus autonomous actions creates a blast radius most teams haven't planned for. This is for security teams adopting AI agents, engineering leads building agentic tools, and anyone who needs to understand the new attack surface before deploying browsing automation at work. One Topic, Ten minutes, No panic. Is there a topic/term you want me to discuss next? Text me!! YouTube more your speed? → https://links.sith2.com/YouTube Apple Podcasts your usual stop? → https://links.sith2.com/Apple Neither of those? Spotify’s over here → https://links.sith2.com/Spotify Prefer reading quietly at your own pace? → https://links.sith2.com/Blog Join us in The Cyber Sanctuary (no robes required) → https://links.sith2.com/Discord Follow the human behind the microphone → https://links.sith2.com/linkedin Need another way to reach me? That’s here → https://linktr.ee/rich.greene
North Korea Mastra NPM Supply Chain Attack: How It Works
You installed a dependency before lunch. Tests passed, app booted, nothing looked wrong. By dinner, your machine had quietly run someone else's code. This episode covers the Mastra npm supply chain compromise Microsoft attributed to North Korea linked threat actors. We break down how postinstall scripts became the attack vector, why an 88 minute exposure window still matters, and what remote access trojans do on developer endpoints. You will learn how AI framework supply chains expand your attack surface, the difference between package takedown and forensic cleanup, and why lockfiles are history snapshots not security verdicts. We walk through the controls that protect teams most: deterministic builds with pinned versions and provenance attestations for verified package origins. The episode includes timeline thinking for exposure windows, hunting for execution artifacts beyond package names, and the specific steps for rotating secrets and rebuilding compromised environments. This is for developers, security teams, and engineering leaders managing open source dependencies in fast moving stacks. One Topic, Ten minutes, No panic. Is there a topic/term you want me to discuss next? Text me!! YouTube more your speed? → https://links.sith2.com/YouTube Apple Podcasts your usual stop? → https://links.sith2.com/Apple Neither of those? Spotify’s over here → https://links.sith2.com/Spotify Prefer reading quietly at your own pace? → https://links.sith2.com/Blog Join us in The Cyber Sanctuary (no robes required) → https://links.sith2.com/Discord Follow the human behind the microphone → https://links.sith2.com/linkedin Need another way to reach me? That’s here → https://linktr.ee/rich.greene
Patch Tuesday 206 Vulnerabilities: AI Discovery vs Remediation Speed
Your update dashboard keeps climbing. Not ten fixes, not fifty. Two hundred and six security patches waiting for approval, and everyone is asking if work stops now. That was June 2026, the largest Patch Tuesday on record. This episode covers why record patch volumes are becoming normal, what AI-assisted vulnerability discovery has to do with the bug pipeline, how to prioritize under pressure with a four-lens triage framework (exploitability, exposure, impact, compensating controls), and why the real problem is not volume but the speed mismatch between finding bugs and fixing them. We walk through CVE-2026-45657, the wormable kernel issue rated CVSS 9.8, and what that severity score actually means for your risk timeline. You will also get a practical approach to building a 24-hour critical patch lane, classifying assets before the next wave, and using temporary containment when patching must wait. This is for IT leaders managing emergency change windows, security teams ranking exploit paths, and business leaders deciding when downtime is justified. One Topic, Ten minutes, No panic. Is there a topic/term you want me to discuss next? Text me!! YouTube more your speed? → https://links.sith2.com/YouTube Apple Podcasts your usual stop? → https://links.sith2.com/Apple Neither of those? Spotify’s over here → https://links.sith2.com/Spotify Prefer reading quietly at your own pace? → https://links.sith2.com/Blog Join us in The Cyber Sanctuary (no robes required) → https://links.sith2.com/Discord Follow the human behind the microphone → https://links.sith2.com/linkedin Need another way to reach me? That’s here → https://linktr.ee/rich.greene
Instagram AI Takeover: How Attackers Exploited Meta Support Bots
Your profile photo vanishes. Your email is changed. A password reset you never requested lands in someone else's inbox. You're locked out of your own Instagram account, and you didn't click a single suspicious link. In early 2026, attackers manipulated Meta's AI support chatbot to approve password resets on roughly 20,225 Instagram accounts over seven weeks. This episode breaks down how social engineering evolved from targeting human support reps to exploiting AI-powered customer service systems. We cover identity verification failures, how chatbots became part of the security boundary, the policy response led by California Attorney General Rob Bonta and 40 state attorneys general, and the difference between traditional phishing and trust-layer manipulation. You'll hear why separating chat from authority matters, what phishing-resistant multi-factor authentication means, and how to apply throttling, anomaly detection, and tabletop exercises for bot abuse. This is for anyone managing Instagram accounts, security teams integrating AI support tools, and developers building customer service automation who need to understand where convenience meets risk. One Topic, Ten minutes, No panic. Is there a topic/term you want me to discuss next? Text me!! YouTube more your speed? → https://links.sith2.com/YouTube Apple Podcasts your usual stop? → https://links.sith2.com/Apple Neither of those? Spotify’s over here → https://links.sith2.com/Spotify Prefer reading quietly at your own pace? → https://links.sith2.com/Blog Join us in The Cyber Sanctuary (no robes required) → https://links.sith2.com/Discord Follow the human behind the microphone → https://links.sith2.com/linkedin Need another way to reach me? That’s here → https://linktr.ee/rich.greene
FortiBleed: When Your Firewall Becomes the Front Door
Your firewall is supposed to be the thing that keeps attackers out. FortiBleed is the story of what happens when it becomes the way in. In June 2026, roughly 86,644 sets of working Fortinet credentials turned up circulating among attackers across 194 countries. On June 18th, CISA issued an emergency advisory telling anyone running internet-facing Fortinet gear to terminate active sessions, rotate every credential, and turn on phishing-resistant multi-factor authentication immediately. This episode of Plaintext with Rich explains what FortiBleed actually is, why patching alone does not solve a credential-exposure incident, and what the difference between "patch" and "rotate" means for the people responsible for keeping a network safe. It also covers why a firewall breach lands differently than almost any other kind of breach, and what to check if you are worried someone already walked through the door before you changed the locks. If you manage a team, own a business, or sit anywhere near a decision about network security gear, this one is directly relevant to your week. If you have no idea what a firewall does, that is fine too; the episode starts from the beginning. One Topic, Ten minutes, No panic. Is there a topic/term you want me to discuss next? Text me!! YouTube more your speed? → https://links.sith2.com/YouTube Apple Podcasts your usual stop? → https://links.sith2.com/Apple Neither of those? Spotify’s over here → https://links.sith2.com/Spotify Prefer reading quietly at your own pace? → https://links.sith2.com/Blog Join us in The Cyber Sanctuary (no robes required) → https://links.sith2.com/Discord Follow the human behind the microphone → https://links.sith2.com/linkedin Need another way to reach me? That’s here → https://linktr.ee/rich.greene
Post-Quantum Cryptography: Start the Inventory Before Q-Day
You don't inventory your house the morning of the move. You start months before. So why are most organizations still treating post-quantum cryptography as a 2035 problem? Episode 31 of Plaintext with Rich treats the post-quantum crypto migration as what it actually is. A logistics problem, not a science one. We walk through the news peg that moved the timeline. Google's March 2026 announcement of a 2029 internal deadline, years ahead of federal targets, anchored by Craig Gidney's research at Google Quantum AI showing that one million noisy qubits could break a 2,048-bit RSA key in under a week. We explain harvest-now-decrypt-later in plain language, the threat that doesn't wait for Q-Day. We cover the three new NIST standards (FIPS 203, FIPS 204, FIPS 205), the NSA's January 2027 CNSA 2.0 procurement gate, and the design principle that matters more than any single algorithm. Crypto-agility. The episode closes with a Plaintext Starter Kit for the leader who needs to know what to ask the security team this quarter. If you've ever wondered what "quantum breaks encryption" actually means for your environment, or whether you should be doing anything about it before 2030, this one is for you. Ten minutes. One topic. No panic. Is there a topic/term you want me to discuss next? Text me!! YouTube more your speed? → https://links.sith2.com/YouTube Apple Podcasts your usual stop? → https://links.sith2.com/Apple Neither of those? Spotify’s over here → https://links.sith2.com/Spotify Prefer reading quietly at your own pace? → https://links.sith2.com/Blog Join us in The Cyber Sanctuary (no robes required) → https://links.sith2.com/Discord Follow the human behind the microphone → https://links.sith2.com/linkedin Need another way to reach me? That’s here → https://linktr.ee/rich.greene
Cybersecurity Careers and AI: The Squeeze and the Opening
Someone pulled Rich aside at a conference recently. Six years in IT, ready to break into security, and asking the question more people ask every week. Should I even bother right now? Here's what the data actually shows. Episode 30 of Plaintext with Rich unpacks the cybersecurity career paradox of 2026. The bottom rung is getting squeezed as AI automates SOC analyst, threat intelligence, and incident response work. At the same time, demand for AI security engineers, prompt injection specialists, and model risk leads is climbing fast. The episode walks through what prompt injection actually looks like in plain language, why the 2025 ISC2 Cybersecurity Workforce Study calls AI the field's top critical skill for the second year running, what BLS projects through 2034, and how the Pentagon's new Cyber Registered Apprenticeship Program is becoming a skills-based hiring blueprint other employers will copy. If you're trying to break into cybersecurity right now, or you're already in the field and watching AI requirements sprout on every posting, this one is for you. It addresses the anxiety honestly. No doom. No false comfort. Ten minutes. One topic. No panic. Is there a topic/term you want me to discuss next? Text me!! YouTube more your speed? → https://links.sith2.com/YouTube Apple Podcasts your usual stop? → https://links.sith2.com/Apple Neither of those? Spotify’s over here → https://links.sith2.com/Spotify Prefer reading quietly at your own pace? → https://links.sith2.com/Blog Join us in The Cyber Sanctuary (no robes required) → https://links.sith2.com/Discord Follow the human behind the microphone → https://links.sith2.com/linkedin Need another way to reach me? That’s here → https://linktr.ee/rich.greene
Supply Chain Attacks: How One Update Hit OpenAI
A routine software update. No phishing. No sketchy download. Then a security team finds the unthinkable: trusted code has been hijacked, and the breach rode in through the exact channels engineers rely on every day. I walk through the supply chain attacks that piled up across April and May 2026, including poisoned open source packages tied to TanStack and trojanized Daemon Tools installers, plus the rapid-fire abuse of major software registries like NPM, PyPI, and Docker Hub. The most important twist is what the malware is hunting. These campaigns aren’t primarily chasing customer data. They’re after the assets sitting on developer laptops and flowing through build servers: developer credentials, API keys, cloud tokens, SSH keys, and the permissions that turn “one compromised machine” into “access everywhere.” I explain why this shift is happening now through two lenses: trust (software is assembled, not written from scratch) and leverage (compromise one popular dependency and you reach everyone who installs it). Then we get practical about software supply chain security and CI/CD security. I break down how a poisoned pipeline can still output packages that look legitimate, complete with valid signatures, and why that makes detection so hard. Finally, I lay out five moves you can take right now: build an SBOM, treat CI/CD like production, watch for suspicious dependency changes and too-fresh releases, rotate to short-lived scoped secrets, and patch known-bad tool versions quickly. Subscribe, share this with a developer or leader who approves tooling, and leave a review so more teams stop trusting updates on autopilot. Is there a topic/term you want me to discuss next? Text me!! YouTube more your speed? → https://links.sith2.com/YouTube Apple Podcasts your usual stop? → https://links.sith2.com/Apple Neither of those? Spotify’s over here → https://links.sith2.com/Spotify Prefer reading quietly at your own pace? → https://links.sith2.com/Blog Join us in The Cyber Sanctuary (no robes required) → https://links.sith2.com/Discord Follow the human behind the microphone → https://links.sith2.com/linkedin Need another way to reach me? That’s here → https://linktr.ee/rich.greene
Microsoft Exchange Zero-Day Under Attack: One Email Hijacks OWA
It's Monday morning. You open the third email of the day. Nothing visible happens, but in the background, an attacker just borrowed the proof you were logged in. Episode 28 of Plaintext with Rich is a hot take on CVE-2026-42897, the Microsoft Exchange Server zero-day under active exploitation right now. We break down what cross-site scripting actually does inside Outlook Web Access, why session hijacking is more dangerous than the underlying bug, and how a single crafted email becomes business email compromise. We look at the on-premises versus Exchange Online divide, why ProxyLogon and ProxyShell aren't ancient history yet, and what CISA's Known Exploited Vulnerabilities catalog listing and the May 29 federal deadline mean for everyone else. The episode closes with a Plaintext Starter Kit of four moves any on-prem Exchange team should make this week. If you run on-prem Exchange, support someone who does, or you've been putting off the migration conversation, this one is for you. Ten minutes. One topic. No panic. Is there a topic/term you want me to discuss next? Text me!! YouTube more your speed? → https://links.sith2.com/YouTube Apple Podcasts your usual stop? → https://links.sith2.com/Apple Neither of those? Spotify’s over here → https://links.sith2.com/Spotify Prefer reading quietly at your own pace? → https://links.sith2.com/Blog Join us in The Cyber Sanctuary (no robes required) → https://links.sith2.com/Discord Follow the human behind the microphone → https://links.sith2.com/linkedin Need another way to reach me? That’s here → https://linktr.ee/rich.greene
Work-Life Balance in Cybersecurity: The Structural Fix
You finish at 6:00pm. At 6:47 you reopen the laptop, 'just to check something.' By 9:00 the evening is gone. The boundary didn't fail tonight. It was never there. Episode 27 of Plaintext with Rich closes the Month of Mindfulness, a five-week series on self-care for people working in security and tech. This week we're talking about work-life balance, but not as willpower or time management. As protective infrastructure. We pull the arc together, mental, spiritual, physical, and burnout, and land on the idea that balance is what keeps the first three from collapsing into the fourth. We borrow briefly from Cal Newport's concept of deep work and Jocko Willink's framing of discipline as freedom, neither as sermon, both as shorthand. The episode closes with a Plaintext Starter Kit of structural defaults, not resolutions, designed to protect a sustainable career in a job that otherwise won't let you have one. If you've made it to the end of this series and you're asking 'okay, but how do I actually live this on a Tuesday,' this one is for you. Ten minutes or less. One topic. No panic. Cal Newports "Deep Work: Rules for Focused Success in a Distracted World" Jocko Willink Is there a topic/term you want me to discuss next? Text me!! YouTube more your speed? → https://links.sith2.com/YouTube Apple Podcasts your usual stop? → https://links.sith2.com/Apple Neither of those? Spotify’s over here → https://links.sith2.com/Spotify Prefer reading quietly at your own pace? → https://links.sith2.com/Blog Join us in The Cyber Sanctuary (no robes required) → https://links.sith2.com/Discord Follow the human behind the microphone → https://links.sith2.com/linkedin Need another way to reach me? That’s here → https://linktr.ee/rich.greene
Cybersecurity Burnout: Not a Character Flaw, a System Problem
You're reading a breach report. Third one this month. Last year a story like this would have lit something in you. Today you scroll past it. That's not you. That's the bill. Episode 26 of Plaintext with Rich is the fourth installment of the Month of Mindfulness, a five-week series on self-care for people working in security and tech. This week we're talking about burnout, what it actually is and why the cybersecurity industry produces it reliably. We use the World Health Organization's classification of burnout as an occupational phenomenon and Christina Maslach's three dimensions (exhaustion, cynicism, reduced efficacy) to name what most of us feel but can't label. We get into the systemic causes specific to our field: always-on culture, headcount lag, and job designs that treat recovery as a perk instead of infrastructure. The episode lands with a Plaintext Starter Kit split between what the individual can do and what only leadership can fix. If you've ever caught yourself scrolling past a breach report that used to light a fire and realized you don't feel anything, this one is for you. Whether you're the one carrying the load or the one supposed to be protecting the people who are. Ten minutes or less. One topic. No panic. Christina Maslach -> https://www.linkedin.com/in/christinamaslach/ World Health Organization -> https://www.linkedin.com/company/world-health-organization/ Is there a topic/term you want me to discuss next? Text me!! YouTube more your speed? → https://links.sith2.com/YouTube Apple Podcasts your usual stop? → https://links.sith2.com/Apple Neither of those? Spotify’s over here → https://links.sith2.com/Spotify Prefer reading quietly at your own pace? → https://links.sith2.com/Blog Join us in The Cyber Sanctuary (no robes required) → https://links.sith2.com/Discord Follow the human behind the microphone → https://links.sith2.com/linkedin Need another way to reach me? That’s here → https://linktr.ee/rich.greene
Physical Health in Cybersecurity: The Body Keeps the Receipts
It's Friday morning. You stand up to refill your water and your back doesn’t move the way it used to. The systems are up and running smoothly. Your body hasn’t gotten the same memo. Episode 25 of Plaintext with Rich is the third installment of the Month of Mindfulness, a five-week series on self-care for people working in security and tech. This week we’re talking about physical health, the silent receipt your body keeps for the cumulative load of this job. We get into the specific body costs of security work: long incident response shifts, screen time, the cortisol of on-call, sleep disruption from pages, and the war-room conditions that turn your spine into a slow-motion lawsuit. The episode lands with a Plaintext Starter Kit of habits you can start this week, no programs to join and no protocols to memorize. If you’ve ever come off a long incident and felt every hour you spent at the keyboard in your shoulders, this one is for you. Whether you’re an analyst, an engineer, or the one person doing security at a 40-person company, the body keeps the bill. For community around this conversation, find Rich’s LinkedIn group, Desk to Deadlifts. The name is catchy, but it’s not a powerlifting group. It’s a space for professionals trying to fit physical health into busy lives. Ten minutes or less. One topic. No panic. Desk to Deadlift (LinkedIn Group) https://www.linkedin.com/groups/13248033/ Is there a topic/term you want me to discuss next? Text me!! YouTube more your speed? → https://links.sith2.com/YouTube Apple Podcasts your usual stop? → https://links.sith2.com/Apple Neither of those? Spotify’s over here → https://links.sith2.com/Spotify Prefer reading quietly at your own pace? → https://links.sith2.com/Blog Join us in The Cyber Sanctuary (no robes required) → https://links.sith2.com/Discord Follow the human behind the microphone → https://links.sith2.com/linkedin Need another way to reach me? That’s here → https://linktr.ee/rich.greene
All-In with Chamath, Jason, Sacks & Friedberg
Tomorrow, Today
Acquired
Hard Fork
AI Business Daily
The Room Podcast