POPULARITY
164 episodes with security operations
59 episodes with security operations
39 episodes with security operations
51 episodes with security operations
16 episodes with security operations
14 episodes with security operations
13 episodes with security operations
13 episodes with security operations
8 episodes with security operations
10 episodes with security operations
9 episodes with security operations
7 episodes with security operations
8 episodes with security operations
11 episodes with security operations
6 episodes with security operations
6 episodes with security operations
10 episodes with security operations
7 episodes with security operations
4 episodes with security operations
5 episodes with security operations
4 episodes with security operations
7 episodes with security operations
7 episodes with security operations
5 episodes with security operations
12 episodes with security operations
6 episodes with security operations
3 episodes with security operations
The dominant structural shift highlighted is margin pressure and business model viability for MSPs due to workforce reduction driven by AI automation. This is exemplified by Microsoft's introduction of Agent365—an enterprise product licensing AI agents rather than human users—and industry reports forecasting that 30–50% of white-collar jobs may be replaced by AI technologies, according to publication summaries referenced during discussion. The shift fundamentally threatens the per-seat managed services pricing model that has anchored MSP revenue. Evidence of mounting financial risk is provided by the scenario where clients may halve their seat counts within a two-to-three-year window. As stated, this adjustment would immediately cut monthly recurring revenue (MMR) for MSPs. The discussion connects this trend to Microsoft's evolving licensing model and notes an industry-wide consensus reflected in a Capterra survey, which found all surveyed MSPs in 2024 facing significant increases in local competition. The implication is that margin pressure from both automation and intensifying competition is occurring simultaneously. Additional developments reinforce the risks to stability. Security complexity and associated liability are increasing, as non-specialist teams—originally tasked with legacy IT functions—are now expected to take responsibility for security operations without adequate expertise. This burden is heightened by the emergence of unmanaged AI adoption at client organizations, creating new avenues for data exposure and regulatory risk. Surveyed business owners are considering exit or consolidation, citing inability or unwillingness to restructure business models to accommodate these changes. Peer group participation is recognized as widespread but not a direct countermeasure to these structural challenges. For MSPs and IT service providers, the practical implications are clear: reliance on the per-seat model is a growing contract risk, with revenue volatility linked to workforce automation outpacing both the speed of traditional service adaptation and client technology adoption. Accountabilities around AI risk, security governance, and compliance are expanding—often without a corresponding increase in compensable scope or staff capability. Operators must assess vendor dependency (especially in rapidly shifting software licensing models), realign service portfolios towards advisory, compliance, and security, and prepare for sustained market turbulence marked by shrinking margins and rising operational complexity. Supported by: Small Biz Thoughts Community Sign up for the SMB Online Conference: www.smbonlineconference.com
Shane Tews — Non-Resident Senior Fellow at AEI and the person who explained the internet to Capitol Hill No Password Required Season 7: Episode 7 – Shane Tews Shane Tews is a Non-Resident Senior Fellow at the American Enterprise Institute, where she focuses on cybersecurity, privacy, artificial intelligence, and internet governance. She is also President of Logan Circle Strategies, a strategic advisory firm working at the intersection of technology and policy. Before her think tank work, Shane helped introduce modems to the George H.W. Bush White House, walked the halls of Capitol Hill explaining the internet to blank-staring legislators, and spent years at VeriSign helping shape the foundational frameworks of how the internet would be governed. In this episode, Shane traces her unlikely path from the Bush administration to becoming one of Washington's most trusted voices on tech policy. She breaks down why regulating outcomes rather than inputs is the only sensible approach to technology governance, why the US and EU are operating from fundamentally different innovation philosophies, and why a national privacy bill is long overdue. She also explains why most organizations and individuals are far less protected than they think and why nobody knows who to call when something goes wrong. Jack Clabby and co-host Kayley Melton talk with Shane about legacy system vulnerabilities, the cybersecurity implications of agentic AI, and what policymakers absolutely must get right over the next decade. She also reflects on what the CISA reauthorization limbo means for companies that don't even know they've lost liability protection. In the Lifestyle Polygraph, Shane reveals she has 20,000 emails across eight accounts, admits she fakes laughs at bad jokes out of Midwestern politeness, shares her obsession with The Bear and Peaky Blinders, and tells us about her children's book project using Google Omni called "Shane on a Train." Follow Shane on LinkedIn and on X at @ShaneTews. Find her work at AEI.org and TechPolicyDaily.com. No Password Required is presented by ThreatLocker In this episode: Shane's path from the George H.W. Bush White House to becoming Capitol Hill's go-to internet explainer (00:34 - 02:22) Why the Clinton-era multi-stakeholder model got internet governance right and what that means for policy today (04:40 - 06:13) The case for a national privacy bill and why 50 state standards aren't working (07:24 - 09:27) What AEI covers and how Shane thinks about riding the top of the wave across the entire tech policy stack (09:35 - 11:23) Legacy systems, vendor debt, and why outdated software is the easiest entry point for bad actors (11:30 - 13:34) The gap between how protected people think they are and how exposed they actually are, including a generational perspective on MFA (14:07 - 16:25) The biggest disconnect between everyday cyber reality and the policy world (16:59 - 20:35) Government readiness for a major cyber attack and why most people don't have a plan (20:54 - 22:32) How the US and EU innovation philosophies differ and why Europe's banking system is the real tech problem (22:41 - 25:38) The DeepSeek false narrative and where the US is leading vs. reacting on AI (25:45 - 29:21) The shift from AI features to AI coordination and what agentic AI means for cybersecurity permissions (29:28 - 32:16) What policymakers must get right on AI over the next 10 years (32:25 - 34:11) The Lifestyle Polygraph: inbox chaos, fake laughs, The Bear, and Shane on a Train (00:04 - 12:48) Timestamp Highlights: (00:34) Shane's origin story: modems at the White House and blank stares on the Hill (04:40) Why the internet got policy right early on and what we can learn from it (07:24) The case for harmonizing breach standards with a national framework (11:30) Legacy systems and vendor debt as the easiest attack vectors (14:07) The real gap between how protected people think they are and how exposed they actually are (20:54) Government cyber readiness: do you know who to call when something goes wrong? (22:41) US vs. EU innovation: why Europe's banking system is the real tech problem (29:28) Agentic AI and the cybersecurity risks of permissions you forgot you gave (32:25) What policymakers must get right on AI over the next decade (06:44) Shane on a Train: using Google Omni to write a children's book series Resources & Links: AEI.org — Shane's think tank home base TechPolicyDaily.com — Daily tech policy coverage ThreatLocker — Supporter of this podcast Cyber Florida — The Mother Ship
At Infosecurity Europe 2026 in London, Bill Peterson, Senior Director of Product Marketing at Sumo Logic, joins us to unpack a tension every regulated security team knows well. When an incident hits, the business has to keep running. At the same time, regulators expect sensitive data to stay in region. For a long time, those two demands have pulled in opposite directions. Sumo Logic has spent 15 years as a SaaS platform on AWS, processing roughly four exabytes of data a day for around 2,000 customers. The core promise is speed, driving mean time to resolve as low as possible. Peterson frames it in business terms, because the person signing the check wants to know the return, not the bits and bytes. The news from the show is Sumo Logic availability on the AWS European Sovereign Cloud. EU organizations can keep their data in region, handled by EU staff, while still running the full platform for incident response. That turns a painful either/or into a checklist a regulated buyer can complete. Genesys is the first customer live in the sovereign cloud, with payment processor OpenPay preparing to follow. How does this play out for highly regulated industries? Sumo Logic is focused on finance, healthcare, telco, and government, the verticals feeling the most pressure. The path Peterson describes is simple: let Sumo Logic handle incident management, let AWS move and grow the data in region, and check the sovereignty box without giving up operational readiness. Underneath sits a full-featured SIEM and Dojo AI, the agentic approach Sumo Logic launched earlier this year. The goal is not to replace analysts but to keep a human in the loop while handing proven, repetitive work to an agent. Fix one server, confirm the solution, then let an agent patch the other 599 under oversight. A SOC Analyst Agent reaches general availability at Black Hat later this year, alongside an MCP server. On observability, the differentiator is reading both structured and unstructured data without normalizing it first. A zip code is structured; a cryptic web hook error is not. Sumo Logic reads both, which feeds directly into faster time to identify and faster time to resolve. For any leader weighing sovereignty against uptime, Bill Peterson makes a clear case that they can finally live in the same plan. This is a Brand Spotlight. A Brand Spotlight is a ~15 minute conversation designed to explore the guest, their company, and what makes their approach unique. Learn more: https://www.studioc60.com/creation#spotlight GUEST Bill Peterson, Senior Director of Product Marketing, Sumo Logic LinkedIn: https://www.linkedin.com/in/williampetersonjr/ RESOURCES Learn more about Sumo Logic: https://www.sumologic.com/ Sumo Logic on the AWS European Sovereign Cloud (announced at Infosecurity Europe 2026): https://www.sumologic.com/newsroom Infosecurity Europe 2026 event coverage: https://www.itspmagazine.com/infosecurity-europe-2026-infosec-london-cybersecurity-event-coverage Are you interested in telling your story? ▶︎ Full Length Brand Story: https://www.studioc60.com/content-creation#full ▶︎ Brand Spotlight Story: https://www.studioc60.com/content-creation#spotlight ▶︎ Brand Highlight Story: https://www.studioc60.com/content-creation#highlight ▶︎ Get your own Brand Briefing at an upcoming event: https://www.studioc60.com/buy-brand-briefings KEYWORDS Bill Peterson, Sumo Logic, Sean Martin, brand story, brand marketing, marketing podcast, brand spotlight, AWS European Sovereign Cloud, data sovereignty, incident response, mean time to resolve, SIEM, security operations, Dojo AI, agentic AI, SOC analyst agent, observability, log analytics, Infosecurity Europe 2026 Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
At Infosecurity Europe 2026, Matt Middleton-Leal, Regional Vice President for Qualys across Northern Europe, joins Sean Martin inside the Risk Operations Center built into the Qualys booth. The premise is blunt: cybersecurity has spent years getting good at measuring risk and almost no time getting good at fixing it. The Risk Operations Center, or ROC, is the Qualys answer to that imbalance. So what is a ROC? It is not a product. Middleton-Leal describes it as an operating model that pulls scattered risk signals together, ranks them by business context and financial impact, and drives them toward remediation. If a SOC looks in the rearview mirror at what already happened, the ROC looks through the windshield at the risk ahead. Why now? Because risk moves at machine speed. In an AI-driven world of frontier models and autonomous agents, Middleton-Leal argues that remediation tied to service desk tickets is already too slow. He shares what happens when a client prepares to deploy tens of thousands of new agents before anyone knows what those agents touch or where their data goes. The example that lands hardest is a number: 62 million risk findings across one client's combined tooling. Middleton-Leal walks through how threat intelligence, business context, and safe exploitability testing collapse that figure to under one percent of fixes that genuinely reduce loss. It is a concrete look at how to prioritize remediation instead of drowning in dashboards. There is a quieter shift underneath it all: financial risk quantification, long reserved for the largest banks, reaching companies that never had the analysts to build it. Working with Richard Seiersen, Chief Risk Technology Officer at Qualys, the company is building ways to answer questions like what a ransomware event would likely cost a business in your sector and region. Middleton-Leal closes with the one place every organization should start, whether they use Qualys or not. This is a Brand Spotlight. A Brand Spotlight is a ~15 minute conversation designed to explore the guest, their company, and what makes their approach unique. Learn more: https://www.studioc60.com/creation#spotlight GUESTMatt Middleton-Leal, Regional Vice President, Northern Europe, Qualys LinkedIn: https://www.linkedin.com/in/matt-middleton-leal-a56557/ RESOURCES Qualys: https://www.qualys.com ITSPmagazine Infosecurity Europe 2026 coverage: https://www.itspmagazine.com/infosecurity-europe-2026-infosec-london-cybersecurity-event-coverage Richard Seiersen, Chief Risk Technology Officer at Qualys, co-author of "How to Measure Anything in Cybersecurity Risk" Connect with Matt Middleton-Leal on LinkedIn: https://www.linkedin.com/in/matt-middleton-leal-a56557/ Are you interested in telling your story? ▶︎ Full Length Brand Story: https://www.studioc60.com/content-creation#full ▶︎ Brand Spotlight Story: https://www.studioc60.com/content-creation#spotlight ▶︎ Brand Highlight Story: https://www.studioc60.com/content-creation#highlight ▶︎ Get your own Brand Briefing at an upcoming event: https://www.studioc60.com/buy-brand-briefings KEYWORDS Matt Middleton-Leal, Qualys, Sean Martin, brand story, brand marketing, marketing podcast, brand spotlight, Risk Operations Center, ROC, risk remediation, cyber risk quantification, exposure management, vulnerability management, Richard Seiersen, AI security risk, Infosecurity Europe 2026, machine speed remediation, security operations Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
Interview with Filip Stojkovski on the State of AI in SecOps Filip joins us to talk through the 2+ year rollercoaster that Security Operations tooling has been on since AI entered the chat. We discuss the AI SecOps market, which Filip closely tracks through his SecOps Unpacked project. We also discuss how most of the market has traditionally been focused on the "middle" of the process, which is effectively alert management. Where the conversation really gets interesting is shifting left to discuss building better quality detections. Segment Resources: Be sure to check out SecOps Unpacked - it has more than just vendor information: there are articles, frameworks, podcast episodes, research, and articles/thought leadership Topic: The Unintended Consequences of Vulnmaxxing We discuss my latest blog post where I share a theory that perhaps Project Glasswing is a clever exclusive freemium tier, where Anthropic is hoping to ensnare the world's largest producers of software into using its most expensive model to fix their code for the foreseeable future, creating a much needed new revenue stream for the AI giant with a Trillion dollar valuation. There are some potential unintended consequences that come along with an expensive vulnerability discovery/remediation process that threatens to raise the security poverty line and leave less wealthy companies behind. The Weekly Enterprise News Finally, in the enterprise security news, If you were starting a cybersecurity company today, which category would you pick? layoffs funding the White House AI executive order OpenAI's frontier governance framework Anthropic's Zero Trust for AI agents guide IBM's vulnmaxxing efforts RICO as a service for job seekers Instagram had possibly the most embarrassing hack ever All that and more, on this episode of Enterprise Security Weekly. Visit https://www.securityweekly.com/esw for all the latest episodes! Show Notes: https://securityweekly.com/esw-462
Interview with Filip Stojkovski on the State of AI in SecOps Filip joins us to talk through the 2+ year rollercoaster that Security Operations tooling has been on since AI entered the chat. We discuss the AI SecOps market, which Filip closely tracks through his SecOps Unpacked project. We also discuss how most of the market has traditionally been focused on the "middle" of the process, which is effectively alert management. Where the conversation really gets interesting is shifting left to discuss building better quality detections. Segment Resources: Be sure to check out SecOps Unpacked - it has more than just vendor information: there are articles, frameworks, podcast episodes, research, and articles/thought leadership Topic: The Unintended Consequences of Vulnmaxxing We discuss my latest blog post where I share a theory that perhaps Project Glasswing is a clever exclusive freemium tier, where Anthropic is hoping to ensnare the world's largest producers of software into using its most expensive model to fix their code for the foreseeable future, creating a much needed new revenue stream for the AI giant with a Trillion dollar valuation. There are some potential unintended consequences that come along with an expensive vulnerability discovery/remediation process that threatens to raise the security poverty line and leave less wealthy companies behind. The Weekly Enterprise News Finally, in the enterprise security news, If you were starting a cybersecurity company today, which category would you pick? layoffs funding the White House AI executive order OpenAI's frontier governance framework Anthropic's Zero Trust for AI agents guide IBM's vulnmaxxing efforts RICO as a service for job seekers Instagram had possibly the most embarrassing hack ever All that and more, on this episode of Enterprise Security Weekly. Visit https://www.securityweekly.com/esw for all the latest episodes! Show Notes: https://securityweekly.com/esw-462
Interview with Filip Stojkovski on the State of AI in SecOps Filip joins us to talk through the 2+ year rollercoaster that Security Operations tooling has been on since AI entered the chat. We discuss the AI SecOps market, which Filip closely tracks through his SecOps Unpacked project. We also discuss how most of the market has traditionally been focused on the "middle" of the process, which is effectively alert management. Where the conversation really gets interesting is shifting left to discuss building better quality detections. Segment Resources: Be sure to check out SecOps Unpacked - it has more than just vendor information: there are articles, frameworks, podcast episodes, research, and articles/thought leadership Topic: The Unintended Consequences of Vulnmaxxing We discuss my latest blog post where I share a theory that perhaps Project Glasswing is a clever exclusive freemium tier, where Anthropic is hoping to ensnare the world's largest producers of software into using its most expensive model to fix their code for the foreseeable future, creating a much needed new revenue stream for the AI giant with a Trillion dollar valuation. There are some potential unintended consequences that come along with an expensive vulnerability discovery/remediation process that threatens to raise the security poverty line and leave less wealthy companies behind. The Weekly Enterprise News Finally, in the enterprise security news, If you were starting a cybersecurity company today, which category would you pick? layoffs funding the White House AI executive order OpenAI's frontier governance framework Anthropic's Zero Trust for AI agents guide IBM's vulnmaxxing efforts RICO as a service for job seekers Instagram had possibly the most embarrassing hack ever All that and more, on this episode of Enterprise Security Weekly. Show Notes: https://securityweekly.com/esw-462
Interview with Filip Stojkovski on the State of AI in SecOps Filip joins us to talk through the 2+ year rollercoaster that Security Operations tooling has been on since AI entered the chat. We discuss the AI SecOps market, which Filip closely tracks through his SecOps Unpacked project. We also discuss how most of the market has traditionally been focused on the "middle" of the process, which is effectively alert management. Where the conversation really gets interesting is shifting left to discuss building better quality detections. Segment Resources: Be sure to check out SecOps Unpacked - it has more than just vendor information: there are articles, frameworks, podcast episodes, research, and articles/thought leadership Topic: The Unintended Consequences of Vulnmaxxing We discuss my latest blog post where I share a theory that perhaps Project Glasswing is a clever exclusive freemium tier, where Anthropic is hoping to ensnare the world's largest producers of software into using its most expensive model to fix their code for the foreseeable future, creating a much needed new revenue stream for the AI giant with a Trillion dollar valuation. There are some potential unintended consequences that come along with an expensive vulnerability discovery/remediation process that threatens to raise the security poverty line and leave less wealthy companies behind. The Weekly Enterprise News Finally, in the enterprise security news, If you were starting a cybersecurity company today, which category would you pick? layoffs funding the White House AI executive order OpenAI's frontier governance framework Anthropic's Zero Trust for AI agents guide IBM's vulnmaxxing efforts RICO as a service for job seekers Instagram had possibly the most embarrassing hack ever All that and more, on this episode of Enterprise Security Weekly. Show Notes: https://securityweekly.com/esw-462
The document is a sworn OIG interview transcript from June 15, 2021, involving the Bureau of Prisons captain who oversaw security operations at MCC New York during the period surrounding Jeffrey Epstein's death. The captain described the command structure inside the jail, including his role supervising lieutenants and reporting up to associate wardens or the warden, while investigators walked him through staffing, rosters, post assignments, suicide-watch procedures, SHU operations, and the chain of responsibility on August 9–10, 2019. The transcript is important because it does not present Epstein's death as a clean, orderly institutional event; instead, it shows a jail struggling with bad staffing, confusing handoffs, unfilled posts, questionable paperwork, and a command structure where critical responsibilities appear to have been either missed, misunderstood, or passed around.The most serious value of the interview is in the irregularities it surfaces. The captain reportedly discussed inaccurate rosters or logs, acknowledged questions around skipped SHU rounds, addressed the fact that Epstein had previously been on suicide watch, and said he would not necessarily have known in real time if officers were failing to conduct required checks. Even more troubling, he expressed concern that certain documents may have been deliberately removed from files that should have been reviewed or audited, and investigators also raised an inmate-count issue involving an inmate named Reyes, whose release may not have been properly reflected in the institution's count — something the captain treated as a protocol violation. Taken together, the transcript adds another layer to the larger Epstein death record: not a single clean explanation, but a bureaucratic mess of missing or questionable documentation, staffing failures, broken supervision, and institutional chaos at precisely the moment when the most high-profile federal inmate in America was supposed to be under careful control.to contact me:bobbycapucci@protonmail.comsource:EFTA00111830.pdfBecome a supporter of this podcast: https://www.spreaker.com/podcast/the-epstein-chronicles--5003294/support.
The document is a sworn OIG interview transcript from June 15, 2021, involving the Bureau of Prisons captain who oversaw security operations at MCC New York during the period surrounding Jeffrey Epstein's death. The captain described the command structure inside the jail, including his role supervising lieutenants and reporting up to associate wardens or the warden, while investigators walked him through staffing, rosters, post assignments, suicide-watch procedures, SHU operations, and the chain of responsibility on August 9–10, 2019. The transcript is important because it does not present Epstein's death as a clean, orderly institutional event; instead, it shows a jail struggling with bad staffing, confusing handoffs, unfilled posts, questionable paperwork, and a command structure where critical responsibilities appear to have been either missed, misunderstood, or passed around.The most serious value of the interview is in the irregularities it surfaces. The captain reportedly discussed inaccurate rosters or logs, acknowledged questions around skipped SHU rounds, addressed the fact that Epstein had previously been on suicide watch, and said he would not necessarily have known in real time if officers were failing to conduct required checks. Even more troubling, he expressed concern that certain documents may have been deliberately removed from files that should have been reviewed or audited, and investigators also raised an inmate-count issue involving an inmate named Reyes, whose release may not have been properly reflected in the institution's count — something the captain treated as a protocol violation. Taken together, the transcript adds another layer to the larger Epstein death record: not a single clean explanation, but a bureaucratic mess of missing or questionable documentation, staffing failures, broken supervision, and institutional chaos at precisely the moment when the most high-profile federal inmate in America was supposed to be under careful control.to contact me:bobbycapucci@protonmail.comsource:EFTA00111830.pdfBecome a supporter of this podcast: https://www.spreaker.com/podcast/the-moscow-murders-and-more--5852883/support.
The document is a sworn OIG interview transcript from June 15, 2021, involving the Bureau of Prisons captain who oversaw security operations at MCC New York during the period surrounding Jeffrey Epstein's death. The captain described the command structure inside the jail, including his role supervising lieutenants and reporting up to associate wardens or the warden, while investigators walked him through staffing, rosters, post assignments, suicide-watch procedures, SHU operations, and the chain of responsibility on August 9–10, 2019. The transcript is important because it does not present Epstein's death as a clean, orderly institutional event; instead, it shows a jail struggling with bad staffing, confusing handoffs, unfilled posts, questionable paperwork, and a command structure where critical responsibilities appear to have been either missed, misunderstood, or passed around.The most serious value of the interview is in the irregularities it surfaces. The captain reportedly discussed inaccurate rosters or logs, acknowledged questions around skipped SHU rounds, addressed the fact that Epstein had previously been on suicide watch, and said he would not necessarily have known in real time if officers were failing to conduct required checks. Even more troubling, he expressed concern that certain documents may have been deliberately removed from files that should have been reviewed or audited, and investigators also raised an inmate-count issue involving an inmate named Reyes, whose release may not have been properly reflected in the institution's count — something the captain treated as a protocol violation. Taken together, the transcript adds another layer to the larger Epstein death record: not a single clean explanation, but a bureaucratic mess of missing or questionable documentation, staffing failures, broken supervision, and institutional chaos at precisely the moment when the most high-profile federal inmate in America was supposed to be under careful control.to contact me:bobbycapucci@protonmail.comsource:EFTA00111830.pdf
The document is a sworn OIG interview transcript from June 15, 2021, involving the Bureau of Prisons captain who oversaw security operations at MCC New York during the period surrounding Jeffrey Epstein's death. The captain described the command structure inside the jail, including his role supervising lieutenants and reporting up to associate wardens or the warden, while investigators walked him through staffing, rosters, post assignments, suicide-watch procedures, SHU operations, and the chain of responsibility on August 9–10, 2019. The transcript is important because it does not present Epstein's death as a clean, orderly institutional event; instead, it shows a jail struggling with bad staffing, confusing handoffs, unfilled posts, questionable paperwork, and a command structure where critical responsibilities appear to have been either missed, misunderstood, or passed around.The most serious value of the interview is in the irregularities it surfaces. The captain reportedly discussed inaccurate rosters or logs, acknowledged questions around skipped SHU rounds, addressed the fact that Epstein had previously been on suicide watch, and said he would not necessarily have known in real time if officers were failing to conduct required checks. Even more troubling, he expressed concern that certain documents may have been deliberately removed from files that should have been reviewed or audited, and investigators also raised an inmate-count issue involving an inmate named Reyes, whose release may not have been properly reflected in the institution's count — something the captain treated as a protocol violation. Taken together, the transcript adds another layer to the larger Epstein death record: not a single clean explanation, but a bureaucratic mess of missing or questionable documentation, staffing failures, broken supervision, and institutional chaos at precisely the moment when the most high-profile federal inmate in America was supposed to be under careful control.to contact me:bobbycapucci@protonmail.comsource:EFTA00111830.pdfBecome a supporter of this podcast: https://www.spreaker.com/podcast/the-epstein-chronicles--5003294/support.
The document is a sworn OIG interview transcript from June 15, 2021, involving the Bureau of Prisons captain who oversaw security operations at MCC New York during the period surrounding Jeffrey Epstein's death. The captain described the command structure inside the jail, including his role supervising lieutenants and reporting up to associate wardens or the warden, while investigators walked him through staffing, rosters, post assignments, suicide-watch procedures, SHU operations, and the chain of responsibility on August 9–10, 2019. The transcript is important because it does not present Epstein's death as a clean, orderly institutional event; instead, it shows a jail struggling with bad staffing, confusing handoffs, unfilled posts, questionable paperwork, and a command structure where critical responsibilities appear to have been either missed, misunderstood, or passed around.The most serious value of the interview is in the irregularities it surfaces. The captain reportedly discussed inaccurate rosters or logs, acknowledged questions around skipped SHU rounds, addressed the fact that Epstein had previously been on suicide watch, and said he would not necessarily have known in real time if officers were failing to conduct required checks. Even more troubling, he expressed concern that certain documents may have been deliberately removed from files that should have been reviewed or audited, and investigators also raised an inmate-count issue involving an inmate named Reyes, whose release may not have been properly reflected in the institution's count — something the captain treated as a protocol violation. Taken together, the transcript adds another layer to the larger Epstein death record: not a single clean explanation, but a bureaucratic mess of missing or questionable documentation, staffing failures, broken supervision, and institutional chaos at precisely the moment when the most high-profile federal inmate in America was supposed to be under careful control.to contact me:bobbycapucci@protonmail.comsource:EFTA00111830.pdfBecome a supporter of this podcast: https://www.spreaker.com/podcast/the-moscow-murders-and-more--5852883/support.
The document is a sworn OIG interview transcript from June 15, 2021, involving the Bureau of Prisons captain who oversaw security operations at MCC New York during the period surrounding Jeffrey Epstein's death. The captain described the command structure inside the jail, including his role supervising lieutenants and reporting up to associate wardens or the warden, while investigators walked him through staffing, rosters, post assignments, suicide-watch procedures, SHU operations, and the chain of responsibility on August 9–10, 2019. The transcript is important because it does not present Epstein's death as a clean, orderly institutional event; instead, it shows a jail struggling with bad staffing, confusing handoffs, unfilled posts, questionable paperwork, and a command structure where critical responsibilities appear to have been either missed, misunderstood, or passed around.The most serious value of the interview is in the irregularities it surfaces. The captain reportedly discussed inaccurate rosters or logs, acknowledged questions around skipped SHU rounds, addressed the fact that Epstein had previously been on suicide watch, and said he would not necessarily have known in real time if officers were failing to conduct required checks. Even more troubling, he expressed concern that certain documents may have been deliberately removed from files that should have been reviewed or audited, and investigators also raised an inmate-count issue involving an inmate named Reyes, whose release may not have been properly reflected in the institution's count — something the captain treated as a protocol violation. Taken together, the transcript adds another layer to the larger Epstein death record: not a single clean explanation, but a bureaucratic mess of missing or questionable documentation, staffing failures, broken supervision, and institutional chaos at precisely the moment when the most high-profile federal inmate in America was supposed to be under careful control.to contact me:bobbycapucci@protonmail.comsource:EFTA00111830.pdf
The document is a sworn OIG interview transcript from June 15, 2021, involving the Bureau of Prisons captain who oversaw security operations at MCC New York during the period surrounding Jeffrey Epstein's death. The captain described the command structure inside the jail, including his role supervising lieutenants and reporting up to associate wardens or the warden, while investigators walked him through staffing, rosters, post assignments, suicide-watch procedures, SHU operations, and the chain of responsibility on August 9–10, 2019. The transcript is important because it does not present Epstein's death as a clean, orderly institutional event; instead, it shows a jail struggling with bad staffing, confusing handoffs, unfilled posts, questionable paperwork, and a command structure where critical responsibilities appear to have been either missed, misunderstood, or passed around.The most serious value of the interview is in the irregularities it surfaces. The captain reportedly discussed inaccurate rosters or logs, acknowledged questions around skipped SHU rounds, addressed the fact that Epstein had previously been on suicide watch, and said he would not necessarily have known in real time if officers were failing to conduct required checks. Even more troubling, he expressed concern that certain documents may have been deliberately removed from files that should have been reviewed or audited, and investigators also raised an inmate-count issue involving an inmate named Reyes, whose release may not have been properly reflected in the institution's count — something the captain treated as a protocol violation. Taken together, the transcript adds another layer to the larger Epstein death record: not a single clean explanation, but a bureaucratic mess of missing or questionable documentation, staffing failures, broken supervision, and institutional chaos at precisely the moment when the most high-profile federal inmate in America was supposed to be under careful control.to contact me:bobbycapucci@protonmail.comsource:EFTA00111830.pdfBecome a supporter of this podcast: https://www.spreaker.com/podcast/the-epstein-chronicles--5003294/support.
The document is a sworn OIG interview transcript from June 15, 2021, involving the Bureau of Prisons captain who oversaw security operations at MCC New York during the period surrounding Jeffrey Epstein's death. The captain described the command structure inside the jail, including his role supervising lieutenants and reporting up to associate wardens or the warden, while investigators walked him through staffing, rosters, post assignments, suicide-watch procedures, SHU operations, and the chain of responsibility on August 9–10, 2019. The transcript is important because it does not present Epstein's death as a clean, orderly institutional event; instead, it shows a jail struggling with bad staffing, confusing handoffs, unfilled posts, questionable paperwork, and a command structure where critical responsibilities appear to have been either missed, misunderstood, or passed around.The most serious value of the interview is in the irregularities it surfaces. The captain reportedly discussed inaccurate rosters or logs, acknowledged questions around skipped SHU rounds, addressed the fact that Epstein had previously been on suicide watch, and said he would not necessarily have known in real time if officers were failing to conduct required checks. Even more troubling, he expressed concern that certain documents may have been deliberately removed from files that should have been reviewed or audited, and investigators also raised an inmate-count issue involving an inmate named Reyes, whose release may not have been properly reflected in the institution's count — something the captain treated as a protocol violation. Taken together, the transcript adds another layer to the larger Epstein death record: not a single clean explanation, but a bureaucratic mess of missing or questionable documentation, staffing failures, broken supervision, and institutional chaos at precisely the moment when the most high-profile federal inmate in America was supposed to be under careful control.to contact me:bobbycapucci@protonmail.comsource:EFTA00111830.pdfBecome a supporter of this podcast: https://www.spreaker.com/podcast/the-moscow-murders-and-more--5852883/support.
The document is a sworn OIG interview transcript from June 15, 2021, involving the Bureau of Prisons captain who oversaw security operations at MCC New York during the period surrounding Jeffrey Epstein's death. The captain described the command structure inside the jail, including his role supervising lieutenants and reporting up to associate wardens or the warden, while investigators walked him through staffing, rosters, post assignments, suicide-watch procedures, SHU operations, and the chain of responsibility on August 9–10, 2019. The transcript is important because it does not present Epstein's death as a clean, orderly institutional event; instead, it shows a jail struggling with bad staffing, confusing handoffs, unfilled posts, questionable paperwork, and a command structure where critical responsibilities appear to have been either missed, misunderstood, or passed around.The most serious value of the interview is in the irregularities it surfaces. The captain reportedly discussed inaccurate rosters or logs, acknowledged questions around skipped SHU rounds, addressed the fact that Epstein had previously been on suicide watch, and said he would not necessarily have known in real time if officers were failing to conduct required checks. Even more troubling, he expressed concern that certain documents may have been deliberately removed from files that should have been reviewed or audited, and investigators also raised an inmate-count issue involving an inmate named Reyes, whose release may not have been properly reflected in the institution's count — something the captain treated as a protocol violation. Taken together, the transcript adds another layer to the larger Epstein death record: not a single clean explanation, but a bureaucratic mess of missing or questionable documentation, staffing failures, broken supervision, and institutional chaos at precisely the moment when the most high-profile federal inmate in America was supposed to be under careful control.to contact me:bobbycapucci@protonmail.comsource:EFTA00111830.pdf
The document is a sworn OIG interview transcript from June 15, 2021, involving the Bureau of Prisons captain who oversaw security operations at MCC New York during the period surrounding Jeffrey Epstein's death. The captain described the command structure inside the jail, including his role supervising lieutenants and reporting up to associate wardens or the warden, while investigators walked him through staffing, rosters, post assignments, suicide-watch procedures, SHU operations, and the chain of responsibility on August 9–10, 2019. The transcript is important because it does not present Epstein's death as a clean, orderly institutional event; instead, it shows a jail struggling with bad staffing, confusing handoffs, unfilled posts, questionable paperwork, and a command structure where critical responsibilities appear to have been either missed, misunderstood, or passed around.The most serious value of the interview is in the irregularities it surfaces. The captain reportedly discussed inaccurate rosters or logs, acknowledged questions around skipped SHU rounds, addressed the fact that Epstein had previously been on suicide watch, and said he would not necessarily have known in real time if officers were failing to conduct required checks. Even more troubling, he expressed concern that certain documents may have been deliberately removed from files that should have been reviewed or audited, and investigators also raised an inmate-count issue involving an inmate named Reyes, whose release may not have been properly reflected in the institution's count — something the captain treated as a protocol violation. Taken together, the transcript adds another layer to the larger Epstein death record: not a single clean explanation, but a bureaucratic mess of missing or questionable documentation, staffing failures, broken supervision, and institutional chaos at precisely the moment when the most high-profile federal inmate in America was supposed to be under careful control.to contact me:bobbycapucci@protonmail.comsource:EFTA00111830.pdfBecome a supporter of this podcast: https://www.spreaker.com/podcast/the-epstein-chronicles--5003294/support.
The document is a sworn OIG interview transcript from June 15, 2021, involving the Bureau of Prisons captain who oversaw security operations at MCC New York during the period surrounding Jeffrey Epstein's death. The captain described the command structure inside the jail, including his role supervising lieutenants and reporting up to associate wardens or the warden, while investigators walked him through staffing, rosters, post assignments, suicide-watch procedures, SHU operations, and the chain of responsibility on August 9–10, 2019. The transcript is important because it does not present Epstein's death as a clean, orderly institutional event; instead, it shows a jail struggling with bad staffing, confusing handoffs, unfilled posts, questionable paperwork, and a command structure where critical responsibilities appear to have been either missed, misunderstood, or passed around.The most serious value of the interview is in the irregularities it surfaces. The captain reportedly discussed inaccurate rosters or logs, acknowledged questions around skipped SHU rounds, addressed the fact that Epstein had previously been on suicide watch, and said he would not necessarily have known in real time if officers were failing to conduct required checks. Even more troubling, he expressed concern that certain documents may have been deliberately removed from files that should have been reviewed or audited, and investigators also raised an inmate-count issue involving an inmate named Reyes, whose release may not have been properly reflected in the institution's count — something the captain treated as a protocol violation. Taken together, the transcript adds another layer to the larger Epstein death record: not a single clean explanation, but a bureaucratic mess of missing or questionable documentation, staffing failures, broken supervision, and institutional chaos at precisely the moment when the most high-profile federal inmate in America was supposed to be under careful control.to contact me:bobbycapucci@protonmail.comsource:EFTA00111830.pdfBecome a supporter of this podcast: https://www.spreaker.com/podcast/the-moscow-murders-and-more--5852883/support.
The document is a sworn OIG interview transcript from June 15, 2021, involving the Bureau of Prisons captain who oversaw security operations at MCC New York during the period surrounding Jeffrey Epstein's death. The captain described the command structure inside the jail, including his role supervising lieutenants and reporting up to associate wardens or the warden, while investigators walked him through staffing, rosters, post assignments, suicide-watch procedures, SHU operations, and the chain of responsibility on August 9–10, 2019. The transcript is important because it does not present Epstein's death as a clean, orderly institutional event; instead, it shows a jail struggling with bad staffing, confusing handoffs, unfilled posts, questionable paperwork, and a command structure where critical responsibilities appear to have been either missed, misunderstood, or passed around.The most serious value of the interview is in the irregularities it surfaces. The captain reportedly discussed inaccurate rosters or logs, acknowledged questions around skipped SHU rounds, addressed the fact that Epstein had previously been on suicide watch, and said he would not necessarily have known in real time if officers were failing to conduct required checks. Even more troubling, he expressed concern that certain documents may have been deliberately removed from files that should have been reviewed or audited, and investigators also raised an inmate-count issue involving an inmate named Reyes, whose release may not have been properly reflected in the institution's count — something the captain treated as a protocol violation. Taken together, the transcript adds another layer to the larger Epstein death record: not a single clean explanation, but a bureaucratic mess of missing or questionable documentation, staffing failures, broken supervision, and institutional chaos at precisely the moment when the most high-profile federal inmate in America was supposed to be under careful control.to contact me:bobbycapucci@protonmail.comsource:EFTA00111830.pdfBecome a supporter of this podcast: https://www.spreaker.com/podcast/the-epstein-chronicles--5003294/support.
The document is a sworn OIG interview transcript from June 15, 2021, involving the Bureau of Prisons captain who oversaw security operations at MCC New York during the period surrounding Jeffrey Epstein's death. The captain described the command structure inside the jail, including his role supervising lieutenants and reporting up to associate wardens or the warden, while investigators walked him through staffing, rosters, post assignments, suicide-watch procedures, SHU operations, and the chain of responsibility on August 9–10, 2019. The transcript is important because it does not present Epstein's death as a clean, orderly institutional event; instead, it shows a jail struggling with bad staffing, confusing handoffs, unfilled posts, questionable paperwork, and a command structure where critical responsibilities appear to have been either missed, misunderstood, or passed around.The most serious value of the interview is in the irregularities it surfaces. The captain reportedly discussed inaccurate rosters or logs, acknowledged questions around skipped SHU rounds, addressed the fact that Epstein had previously been on suicide watch, and said he would not necessarily have known in real time if officers were failing to conduct required checks. Even more troubling, he expressed concern that certain documents may have been deliberately removed from files that should have been reviewed or audited, and investigators also raised an inmate-count issue involving an inmate named Reyes, whose release may not have been properly reflected in the institution's count — something the captain treated as a protocol violation. Taken together, the transcript adds another layer to the larger Epstein death record: not a single clean explanation, but a bureaucratic mess of missing or questionable documentation, staffing failures, broken supervision, and institutional chaos at precisely the moment when the most high-profile federal inmate in America was supposed to be under careful control.to contact me:bobbycapucci@protonmail.comsource:EFTA00111830.pdf
The document is a sworn OIG interview transcript from June 15, 2021, involving the Bureau of Prisons captain who oversaw security operations at MCC New York during the period surrounding Jeffrey Epstein's death. The captain described the command structure inside the jail, including his role supervising lieutenants and reporting up to associate wardens or the warden, while investigators walked him through staffing, rosters, post assignments, suicide-watch procedures, SHU operations, and the chain of responsibility on August 9–10, 2019. The transcript is important because it does not present Epstein's death as a clean, orderly institutional event; instead, it shows a jail struggling with bad staffing, confusing handoffs, unfilled posts, questionable paperwork, and a command structure where critical responsibilities appear to have been either missed, misunderstood, or passed around.The most serious value of the interview is in the irregularities it surfaces. The captain reportedly discussed inaccurate rosters or logs, acknowledged questions around skipped SHU rounds, addressed the fact that Epstein had previously been on suicide watch, and said he would not necessarily have known in real time if officers were failing to conduct required checks. Even more troubling, he expressed concern that certain documents may have been deliberately removed from files that should have been reviewed or audited, and investigators also raised an inmate-count issue involving an inmate named Reyes, whose release may not have been properly reflected in the institution's count — something the captain treated as a protocol violation. Taken together, the transcript adds another layer to the larger Epstein death record: not a single clean explanation, but a bureaucratic mess of missing or questionable documentation, staffing failures, broken supervision, and institutional chaos at precisely the moment when the most high-profile federal inmate in America was supposed to be under careful control.to contact me:bobbycapucci@protonmail.comsource:EFTA00111830.pdf
The document is a sworn OIG interview transcript from June 15, 2021, involving the Bureau of Prisons captain who oversaw security operations at MCC New York during the period surrounding Jeffrey Epstein's death. The captain described the command structure inside the jail, including his role supervising lieutenants and reporting up to associate wardens or the warden, while investigators walked him through staffing, rosters, post assignments, suicide-watch procedures, SHU operations, and the chain of responsibility on August 9–10, 2019. The transcript is important because it does not present Epstein's death as a clean, orderly institutional event; instead, it shows a jail struggling with bad staffing, confusing handoffs, unfilled posts, questionable paperwork, and a command structure where critical responsibilities appear to have been either missed, misunderstood, or passed around.The most serious value of the interview is in the irregularities it surfaces. The captain reportedly discussed inaccurate rosters or logs, acknowledged questions around skipped SHU rounds, addressed the fact that Epstein had previously been on suicide watch, and said he would not necessarily have known in real time if officers were failing to conduct required checks. Even more troubling, he expressed concern that certain documents may have been deliberately removed from files that should have been reviewed or audited, and investigators also raised an inmate-count issue involving an inmate named Reyes, whose release may not have been properly reflected in the institution's count — something the captain treated as a protocol violation. Taken together, the transcript adds another layer to the larger Epstein death record: not a single clean explanation, but a bureaucratic mess of missing or questionable documentation, staffing failures, broken supervision, and institutional chaos at precisely the moment when the most high-profile federal inmate in America was supposed to be under careful control.to contact me:bobbycapucci@protonmail.comsource:EFTA00111830.pdf
The document is a sworn OIG interview transcript from June 15, 2021, involving the Bureau of Prisons captain who oversaw security operations at MCC New York during the period surrounding Jeffrey Epstein's death. The captain described the command structure inside the jail, including his role supervising lieutenants and reporting up to associate wardens or the warden, while investigators walked him through staffing, rosters, post assignments, suicide-watch procedures, SHU operations, and the chain of responsibility on August 9–10, 2019. The transcript is important because it does not present Epstein's death as a clean, orderly institutional event; instead, it shows a jail struggling with bad staffing, confusing handoffs, unfilled posts, questionable paperwork, and a command structure where critical responsibilities appear to have been either missed, misunderstood, or passed around.The most serious value of the interview is in the irregularities it surfaces. The captain reportedly discussed inaccurate rosters or logs, acknowledged questions around skipped SHU rounds, addressed the fact that Epstein had previously been on suicide watch, and said he would not necessarily have known in real time if officers were failing to conduct required checks. Even more troubling, he expressed concern that certain documents may have been deliberately removed from files that should have been reviewed or audited, and investigators also raised an inmate-count issue involving an inmate named Reyes, whose release may not have been properly reflected in the institution's count — something the captain treated as a protocol violation. Taken together, the transcript adds another layer to the larger Epstein death record: not a single clean explanation, but a bureaucratic mess of missing or questionable documentation, staffing failures, broken supervision, and institutional chaos at precisely the moment when the most high-profile federal inmate in America was supposed to be under careful control.to contact me:bobbycapucci@protonmail.comsource:EFTA00111830.pdfBecome a supporter of this podcast: https://www.spreaker.com/podcast/the-epstein-chronicles--5003294/support.
The document is a sworn OIG interview transcript from June 15, 2021, involving the Bureau of Prisons captain who oversaw security operations at MCC New York during the period surrounding Jeffrey Epstein's death. The captain described the command structure inside the jail, including his role supervising lieutenants and reporting up to associate wardens or the warden, while investigators walked him through staffing, rosters, post assignments, suicide-watch procedures, SHU operations, and the chain of responsibility on August 9–10, 2019. The transcript is important because it does not present Epstein's death as a clean, orderly institutional event; instead, it shows a jail struggling with bad staffing, confusing handoffs, unfilled posts, questionable paperwork, and a command structure where critical responsibilities appear to have been either missed, misunderstood, or passed around.The most serious value of the interview is in the irregularities it surfaces. The captain reportedly discussed inaccurate rosters or logs, acknowledged questions around skipped SHU rounds, addressed the fact that Epstein had previously been on suicide watch, and said he would not necessarily have known in real time if officers were failing to conduct required checks. Even more troubling, he expressed concern that certain documents may have been deliberately removed from files that should have been reviewed or audited, and investigators also raised an inmate-count issue involving an inmate named Reyes, whose release may not have been properly reflected in the institution's count — something the captain treated as a protocol violation. Taken together, the transcript adds another layer to the larger Epstein death record: not a single clean explanation, but a bureaucratic mess of missing or questionable documentation, staffing failures, broken supervision, and institutional chaos at precisely the moment when the most high-profile federal inmate in America was supposed to be under careful control.to contact me:bobbycapucci@protonmail.comsource:EFTA00111830.pdfBecome a supporter of this podcast: https://www.spreaker.com/podcast/the-epstein-chronicles--5003294/support.
The document is a sworn OIG interview transcript from June 15, 2021, involving the Bureau of Prisons captain who oversaw security operations at MCC New York during the period surrounding Jeffrey Epstein's death. The captain described the command structure inside the jail, including his role supervising lieutenants and reporting up to associate wardens or the warden, while investigators walked him through staffing, rosters, post assignments, suicide-watch procedures, SHU operations, and the chain of responsibility on August 9–10, 2019. The transcript is important because it does not present Epstein's death as a clean, orderly institutional event; instead, it shows a jail struggling with bad staffing, confusing handoffs, unfilled posts, questionable paperwork, and a command structure where critical responsibilities appear to have been either missed, misunderstood, or passed around.The most serious value of the interview is in the irregularities it surfaces. The captain reportedly discussed inaccurate rosters or logs, acknowledged questions around skipped SHU rounds, addressed the fact that Epstein had previously been on suicide watch, and said he would not necessarily have known in real time if officers were failing to conduct required checks. Even more troubling, he expressed concern that certain documents may have been deliberately removed from files that should have been reviewed or audited, and investigators also raised an inmate-count issue involving an inmate named Reyes, whose release may not have been properly reflected in the institution's count — something the captain treated as a protocol violation. Taken together, the transcript adds another layer to the larger Epstein death record: not a single clean explanation, but a bureaucratic mess of missing or questionable documentation, staffing failures, broken supervision, and institutional chaos at precisely the moment when the most high-profile federal inmate in America was supposed to be under careful control.to contact me:bobbycapucci@protonmail.comsource:EFTA00111830.pdfBecome a supporter of this podcast: https://www.spreaker.com/podcast/the-moscow-murders-and-more--5852883/support.
The document is a sworn OIG interview transcript from June 15, 2021, involving the Bureau of Prisons captain who oversaw security operations at MCC New York during the period surrounding Jeffrey Epstein's death. The captain described the command structure inside the jail, including his role supervising lieutenants and reporting up to associate wardens or the warden, while investigators walked him through staffing, rosters, post assignments, suicide-watch procedures, SHU operations, and the chain of responsibility on August 9–10, 2019. The transcript is important because it does not present Epstein's death as a clean, orderly institutional event; instead, it shows a jail struggling with bad staffing, confusing handoffs, unfilled posts, questionable paperwork, and a command structure where critical responsibilities appear to have been either missed, misunderstood, or passed around.The most serious value of the interview is in the irregularities it surfaces. The captain reportedly discussed inaccurate rosters or logs, acknowledged questions around skipped SHU rounds, addressed the fact that Epstein had previously been on suicide watch, and said he would not necessarily have known in real time if officers were failing to conduct required checks. Even more troubling, he expressed concern that certain documents may have been deliberately removed from files that should have been reviewed or audited, and investigators also raised an inmate-count issue involving an inmate named Reyes, whose release may not have been properly reflected in the institution's count — something the captain treated as a protocol violation. Taken together, the transcript adds another layer to the larger Epstein death record: not a single clean explanation, but a bureaucratic mess of missing or questionable documentation, staffing failures, broken supervision, and institutional chaos at precisely the moment when the most high-profile federal inmate in America was supposed to be under careful control.to contact me:bobbycapucci@protonmail.comsource:EFTA00111830.pdf
The document is a sworn OIG interview transcript from June 15, 2021, involving the Bureau of Prisons captain who oversaw security operations at MCC New York during the period surrounding Jeffrey Epstein's death. The captain described the command structure inside the jail, including his role supervising lieutenants and reporting up to associate wardens or the warden, while investigators walked him through staffing, rosters, post assignments, suicide-watch procedures, SHU operations, and the chain of responsibility on August 9–10, 2019. The transcript is important because it does not present Epstein's death as a clean, orderly institutional event; instead, it shows a jail struggling with bad staffing, confusing handoffs, unfilled posts, questionable paperwork, and a command structure where critical responsibilities appear to have been either missed, misunderstood, or passed around.The most serious value of the interview is in the irregularities it surfaces. The captain reportedly discussed inaccurate rosters or logs, acknowledged questions around skipped SHU rounds, addressed the fact that Epstein had previously been on suicide watch, and said he would not necessarily have known in real time if officers were failing to conduct required checks. Even more troubling, he expressed concern that certain documents may have been deliberately removed from files that should have been reviewed or audited, and investigators also raised an inmate-count issue involving an inmate named Reyes, whose release may not have been properly reflected in the institution's count — something the captain treated as a protocol violation. Taken together, the transcript adds another layer to the larger Epstein death record: not a single clean explanation, but a bureaucratic mess of missing or questionable documentation, staffing failures, broken supervision, and institutional chaos at precisely the moment when the most high-profile federal inmate in America was supposed to be under careful control.to contact me:bobbycapucci@protonmail.comsource:EFTA00111830.pdfBecome a supporter of this podcast: https://www.spreaker.com/podcast/the-epstein-chronicles--5003294/support.
The document is a sworn OIG interview transcript from June 15, 2021, involving the Bureau of Prisons captain who oversaw security operations at MCC New York during the period surrounding Jeffrey Epstein's death. The captain described the command structure inside the jail, including his role supervising lieutenants and reporting up to associate wardens or the warden, while investigators walked him through staffing, rosters, post assignments, suicide-watch procedures, SHU operations, and the chain of responsibility on August 9–10, 2019. The transcript is important because it does not present Epstein's death as a clean, orderly institutional event; instead, it shows a jail struggling with bad staffing, confusing handoffs, unfilled posts, questionable paperwork, and a command structure where critical responsibilities appear to have been either missed, misunderstood, or passed around.The most serious value of the interview is in the irregularities it surfaces. The captain reportedly discussed inaccurate rosters or logs, acknowledged questions around skipped SHU rounds, addressed the fact that Epstein had previously been on suicide watch, and said he would not necessarily have known in real time if officers were failing to conduct required checks. Even more troubling, he expressed concern that certain documents may have been deliberately removed from files that should have been reviewed or audited, and investigators also raised an inmate-count issue involving an inmate named Reyes, whose release may not have been properly reflected in the institution's count — something the captain treated as a protocol violation. Taken together, the transcript adds another layer to the larger Epstein death record: not a single clean explanation, but a bureaucratic mess of missing or questionable documentation, staffing failures, broken supervision, and institutional chaos at precisely the moment when the most high-profile federal inmate in America was supposed to be under careful control.to contact me:bobbycapucci@protonmail.comsource:EFTA00111830.pdfBecome a supporter of this podcast: https://www.spreaker.com/podcast/the-epstein-chronicles--5003294/support.
The document is a sworn OIG interview transcript from June 15, 2021, involving the Bureau of Prisons captain who oversaw security operations at MCC New York during the period surrounding Jeffrey Epstein's death. The captain described the command structure inside the jail, including his role supervising lieutenants and reporting up to associate wardens or the warden, while investigators walked him through staffing, rosters, post assignments, suicide-watch procedures, SHU operations, and the chain of responsibility on August 9–10, 2019. The transcript is important because it does not present Epstein's death as a clean, orderly institutional event; instead, it shows a jail struggling with bad staffing, confusing handoffs, unfilled posts, questionable paperwork, and a command structure where critical responsibilities appear to have been either missed, misunderstood, or passed around.The most serious value of the interview is in the irregularities it surfaces. The captain reportedly discussed inaccurate rosters or logs, acknowledged questions around skipped SHU rounds, addressed the fact that Epstein had previously been on suicide watch, and said he would not necessarily have known in real time if officers were failing to conduct required checks. Even more troubling, he expressed concern that certain documents may have been deliberately removed from files that should have been reviewed or audited, and investigators also raised an inmate-count issue involving an inmate named Reyes, whose release may not have been properly reflected in the institution's count — something the captain treated as a protocol violation. Taken together, the transcript adds another layer to the larger Epstein death record: not a single clean explanation, but a bureaucratic mess of missing or questionable documentation, staffing failures, broken supervision, and institutional chaos at precisely the moment when the most high-profile federal inmate in America was supposed to be under careful control.to contact me:bobbycapucci@protonmail.comsource:EFTA00111830.pdfBecome a supporter of this podcast: https://www.spreaker.com/podcast/the-moscow-murders-and-more--5852883/support.
The document is a sworn OIG interview transcript from June 15, 2021, involving the Bureau of Prisons captain who oversaw security operations at MCC New York during the period surrounding Jeffrey Epstein's death. The captain described the command structure inside the jail, including his role supervising lieutenants and reporting up to associate wardens or the warden, while investigators walked him through staffing, rosters, post assignments, suicide-watch procedures, SHU operations, and the chain of responsibility on August 9–10, 2019. The transcript is important because it does not present Epstein's death as a clean, orderly institutional event; instead, it shows a jail struggling with bad staffing, confusing handoffs, unfilled posts, questionable paperwork, and a command structure where critical responsibilities appear to have been either missed, misunderstood, or passed around.The most serious value of the interview is in the irregularities it surfaces. The captain reportedly discussed inaccurate rosters or logs, acknowledged questions around skipped SHU rounds, addressed the fact that Epstein had previously been on suicide watch, and said he would not necessarily have known in real time if officers were failing to conduct required checks. Even more troubling, he expressed concern that certain documents may have been deliberately removed from files that should have been reviewed or audited, and investigators also raised an inmate-count issue involving an inmate named Reyes, whose release may not have been properly reflected in the institution's count — something the captain treated as a protocol violation. Taken together, the transcript adds another layer to the larger Epstein death record: not a single clean explanation, but a bureaucratic mess of missing or questionable documentation, staffing failures, broken supervision, and institutional chaos at precisely the moment when the most high-profile federal inmate in America was supposed to be under careful control.to contact me:bobbycapucci@protonmail.comsource:EFTA00111830.pdfBecome a supporter of this podcast: https://www.spreaker.com/podcast/the-moscow-murders-and-more--5852883/support.
The document is a sworn OIG interview transcript from June 15, 2021, involving the Bureau of Prisons captain who oversaw security operations at MCC New York during the period surrounding Jeffrey Epstein's death. The captain described the command structure inside the jail, including his role supervising lieutenants and reporting up to associate wardens or the warden, while investigators walked him through staffing, rosters, post assignments, suicide-watch procedures, SHU operations, and the chain of responsibility on August 9–10, 2019. The transcript is important because it does not present Epstein's death as a clean, orderly institutional event; instead, it shows a jail struggling with bad staffing, confusing handoffs, unfilled posts, questionable paperwork, and a command structure where critical responsibilities appear to have been either missed, misunderstood, or passed around.The most serious value of the interview is in the irregularities it surfaces. The captain reportedly discussed inaccurate rosters or logs, acknowledged questions around skipped SHU rounds, addressed the fact that Epstein had previously been on suicide watch, and said he would not necessarily have known in real time if officers were failing to conduct required checks. Even more troubling, he expressed concern that certain documents may have been deliberately removed from files that should have been reviewed or audited, and investigators also raised an inmate-count issue involving an inmate named Reyes, whose release may not have been properly reflected in the institution's count — something the captain treated as a protocol violation. Taken together, the transcript adds another layer to the larger Epstein death record: not a single clean explanation, but a bureaucratic mess of missing or questionable documentation, staffing failures, broken supervision, and institutional chaos at precisely the moment when the most high-profile federal inmate in America was supposed to be under careful control.to contact me:bobbycapucci@protonmail.comsource:EFTA00111830.pdf
The document is a sworn OIG interview transcript from June 15, 2021, involving the Bureau of Prisons captain who oversaw security operations at MCC New York during the period surrounding Jeffrey Epstein's death. The captain described the command structure inside the jail, including his role supervising lieutenants and reporting up to associate wardens or the warden, while investigators walked him through staffing, rosters, post assignments, suicide-watch procedures, SHU operations, and the chain of responsibility on August 9–10, 2019. The transcript is important because it does not present Epstein's death as a clean, orderly institutional event; instead, it shows a jail struggling with bad staffing, confusing handoffs, unfilled posts, questionable paperwork, and a command structure where critical responsibilities appear to have been either missed, misunderstood, or passed around.The most serious value of the interview is in the irregularities it surfaces. The captain reportedly discussed inaccurate rosters or logs, acknowledged questions around skipped SHU rounds, addressed the fact that Epstein had previously been on suicide watch, and said he would not necessarily have known in real time if officers were failing to conduct required checks. Even more troubling, he expressed concern that certain documents may have been deliberately removed from files that should have been reviewed or audited, and investigators also raised an inmate-count issue involving an inmate named Reyes, whose release may not have been properly reflected in the institution's count — something the captain treated as a protocol violation. Taken together, the transcript adds another layer to the larger Epstein death record: not a single clean explanation, but a bureaucratic mess of missing or questionable documentation, staffing failures, broken supervision, and institutional chaos at precisely the moment when the most high-profile federal inmate in America was supposed to be under careful control.to contact me:bobbycapucci@protonmail.comsource:EFTA00111830.pdfBecome a supporter of this podcast: https://www.spreaker.com/podcast/the-epstein-chronicles--5003294/support.
Surface every AI agent in your tenant and expose the ones throwing security signals — across both the IT and SOC view. Triage high-severity alerts as IT in the Microsoft 365 admin center, then pivot into the full incident graph as a SOC analyst in Microsoft Defender. Block malicious tool invocations the instant they fire and catch jailbreak attempts on Copilot Studio agents before they take hold. Trace a compromised user back to suspicious agent activity, then trigger Microsoft Entra conditional access to revoke the session and force a password reset straight from the incident. Hunt overpermissioned agents with pre-built advanced hunting templates — including one that exposes every agent running MCP tools on the maker's standing credentials — and pull risky builds from the Agent Store using the Agent Registry. Spencer Berg, AI & Security Product Manager, shares how to turn agent risk signals into coordinated remediation across Defender, Entra, and the Microsoft 365 admin center. ► QUICK LINKS: 00:00 - Stay in control with Agent 365 00:40 - Gain visibility with unified control plane 01:48 - Unified IT & SOC agent view 02:54 - Real-time blocking and jailbreak detection 04:08 - Auto-revoke via Entra conditional access 04:32 - Prevent future incidents 05:28 - Advanced hunting for AI agents 06:43 - Block risky agents 07:15 - Wrap up ► Link References Check out https://aka.ms/Agent365SecOps ► Unfamiliar with Microsoft Mechanics? As Microsoft's official video series for IT, you can watch and share valuable content and demos of current and upcoming tech from the people who build it at Microsoft. • Subscribe to our YouTube: https://www.youtube.com/c/MicrosoftMechanicsSeries • Talk with other IT Pros, join us on the Microsoft Tech Community: https://techcommunity.microsoft.com/t5/microsoft-mechanics-blog/bg-p/MicrosoftMechanicsBlog • Watch or listen from anywhere, subscribe to our podcast: https://microsoftmechanics.libsyn.com/podcast ► Keep getting this insider knowledge, join us on social: • Follow us on Twitter: https://twitter.com/MSFTMechanics • Share knowledge on LinkedIn: https://www.linkedin.com/company/microsoft-mechanics/ • Enjoy us on Instagram: https://www.instagram.com/msftmechanics/ • Loosen up with us on TikTok: https://www.tiktok.com/@msftmechanics
The document is a sworn OIG interview transcript from June 15, 2021, involving the Bureau of Prisons captain who oversaw security operations at MCC New York during the period surrounding Jeffrey Epstein's death. The captain described the command structure inside the jail, including his role supervising lieutenants and reporting up to associate wardens or the warden, while investigators walked him through staffing, rosters, post assignments, suicide-watch procedures, SHU operations, and the chain of responsibility on August 9–10, 2019. The transcript is important because it does not present Epstein's death as a clean, orderly institutional event; instead, it shows a jail struggling with bad staffing, confusing handoffs, unfilled posts, questionable paperwork, and a command structure where critical responsibilities appear to have been either missed, misunderstood, or passed around.The most serious value of the interview is in the irregularities it surfaces. The captain reportedly discussed inaccurate rosters or logs, acknowledged questions around skipped SHU rounds, addressed the fact that Epstein had previously been on suicide watch, and said he would not necessarily have known in real time if officers were failing to conduct required checks. Even more troubling, he expressed concern that certain documents may have been deliberately removed from files that should have been reviewed or audited, and investigators also raised an inmate-count issue involving an inmate named Reyes, whose release may not have been properly reflected in the institution's count — something the captain treated as a protocol violation. Taken together, the transcript adds another layer to the larger Epstein death record: not a single clean explanation, but a bureaucratic mess of missing or questionable documentation, staffing failures, broken supervision, and institutional chaos at precisely the moment when the most high-profile federal inmate in America was supposed to be under careful control.to contact me:bobbycapucci@protonmail.comsource:EFTA00111830.pdfBecome a supporter of this podcast: https://www.spreaker.com/podcast/the-moscow-murders-and-more--5852883/support.
The document is a sworn OIG interview transcript from June 15, 2021, involving the Bureau of Prisons captain who oversaw security operations at MCC New York during the period surrounding Jeffrey Epstein's death. The captain described the command structure inside the jail, including his role supervising lieutenants and reporting up to associate wardens or the warden, while investigators walked him through staffing, rosters, post assignments, suicide-watch procedures, SHU operations, and the chain of responsibility on August 9–10, 2019. The transcript is important because it does not present Epstein's death as a clean, orderly institutional event; instead, it shows a jail struggling with bad staffing, confusing handoffs, unfilled posts, questionable paperwork, and a command structure where critical responsibilities appear to have been either missed, misunderstood, or passed around.The most serious value of the interview is in the irregularities it surfaces. The captain reportedly discussed inaccurate rosters or logs, acknowledged questions around skipped SHU rounds, addressed the fact that Epstein had previously been on suicide watch, and said he would not necessarily have known in real time if officers were failing to conduct required checks. Even more troubling, he expressed concern that certain documents may have been deliberately removed from files that should have been reviewed or audited, and investigators also raised an inmate-count issue involving an inmate named Reyes, whose release may not have been properly reflected in the institution's count — something the captain treated as a protocol violation. Taken together, the transcript adds another layer to the larger Epstein death record: not a single clean explanation, but a bureaucratic mess of missing or questionable documentation, staffing failures, broken supervision, and institutional chaos at precisely the moment when the most high-profile federal inmate in America was supposed to be under careful control.to contact me:bobbycapucci@protonmail.comsource:EFTA00111830.pdf
The document is a sworn OIG interview transcript from June 15, 2021, involving the Bureau of Prisons captain who oversaw security operations at MCC New York during the period surrounding Jeffrey Epstein's death. The captain described the command structure inside the jail, including his role supervising lieutenants and reporting up to associate wardens or the warden, while investigators walked him through staffing, rosters, post assignments, suicide-watch procedures, SHU operations, and the chain of responsibility on August 9–10, 2019. The transcript is important because it does not present Epstein's death as a clean, orderly institutional event; instead, it shows a jail struggling with bad staffing, confusing handoffs, unfilled posts, questionable paperwork, and a command structure where critical responsibilities appear to have been either missed, misunderstood, or passed around.The most serious value of the interview is in the irregularities it surfaces. The captain reportedly discussed inaccurate rosters or logs, acknowledged questions around skipped SHU rounds, addressed the fact that Epstein had previously been on suicide watch, and said he would not necessarily have known in real time if officers were failing to conduct required checks. Even more troubling, he expressed concern that certain documents may have been deliberately removed from files that should have been reviewed or audited, and investigators also raised an inmate-count issue involving an inmate named Reyes, whose release may not have been properly reflected in the institution's count — something the captain treated as a protocol violation. Taken together, the transcript adds another layer to the larger Epstein death record: not a single clean explanation, but a bureaucratic mess of missing or questionable documentation, staffing failures, broken supervision, and institutional chaos at precisely the moment when the most high-profile federal inmate in America was supposed to be under careful control.to contact me:bobbycapucci@protonmail.comsource:EFTA00111830.pdfBecome a supporter of this podcast: https://www.spreaker.com/podcast/the-epstein-chronicles--5003294/support.
The document is a sworn OIG interview transcript from June 15, 2021, involving the Bureau of Prisons captain who oversaw security operations at MCC New York during the period surrounding Jeffrey Epstein's death. The captain described the command structure inside the jail, including his role supervising lieutenants and reporting up to associate wardens or the warden, while investigators walked him through staffing, rosters, post assignments, suicide-watch procedures, SHU operations, and the chain of responsibility on August 9–10, 2019. The transcript is important because it does not present Epstein's death as a clean, orderly institutional event; instead, it shows a jail struggling with bad staffing, confusing handoffs, unfilled posts, questionable paperwork, and a command structure where critical responsibilities appear to have been either missed, misunderstood, or passed around.The most serious value of the interview is in the irregularities it surfaces. The captain reportedly discussed inaccurate rosters or logs, acknowledged questions around skipped SHU rounds, addressed the fact that Epstein had previously been on suicide watch, and said he would not necessarily have known in real time if officers were failing to conduct required checks. Even more troubling, he expressed concern that certain documents may have been deliberately removed from files that should have been reviewed or audited, and investigators also raised an inmate-count issue involving an inmate named Reyes, whose release may not have been properly reflected in the institution's count — something the captain treated as a protocol violation. Taken together, the transcript adds another layer to the larger Epstein death record: not a single clean explanation, but a bureaucratic mess of missing or questionable documentation, staffing failures, broken supervision, and institutional chaos at precisely the moment when the most high-profile federal inmate in America was supposed to be under careful control.to contact me:bobbycapucci@protonmail.comsource:EFTA00111830.pdfBecome a supporter of this podcast: https://www.spreaker.com/podcast/the-moscow-murders-and-more--5852883/support.
The document is a sworn OIG interview transcript from June 15, 2021, involving the Bureau of Prisons captain who oversaw security operations at MCC New York during the period surrounding Jeffrey Epstein's death. The captain described the command structure inside the jail, including his role supervising lieutenants and reporting up to associate wardens or the warden, while investigators walked him through staffing, rosters, post assignments, suicide-watch procedures, SHU operations, and the chain of responsibility on August 9–10, 2019. The transcript is important because it does not present Epstein's death as a clean, orderly institutional event; instead, it shows a jail struggling with bad staffing, confusing handoffs, unfilled posts, questionable paperwork, and a command structure where critical responsibilities appear to have been either missed, misunderstood, or passed around.The most serious value of the interview is in the irregularities it surfaces. The captain reportedly discussed inaccurate rosters or logs, acknowledged questions around skipped SHU rounds, addressed the fact that Epstein had previously been on suicide watch, and said he would not necessarily have known in real time if officers were failing to conduct required checks. Even more troubling, he expressed concern that certain documents may have been deliberately removed from files that should have been reviewed or audited, and investigators also raised an inmate-count issue involving an inmate named Reyes, whose release may not have been properly reflected in the institution's count — something the captain treated as a protocol violation. Taken together, the transcript adds another layer to the larger Epstein death record: not a single clean explanation, but a bureaucratic mess of missing or questionable documentation, staffing failures, broken supervision, and institutional chaos at precisely the moment when the most high-profile federal inmate in America was supposed to be under careful control.to contact me:bobbycapucci@protonmail.comsource:EFTA00111830.pdfBecome a supporter of this podcast: https://www.spreaker.com/podcast/the-epstein-chronicles--5003294/support.
Send us Fan MailEight terabytes of stolen schematics is not just a scary number, it is a reminder that cyber risk becomes business risk fast. We start with the Wired report on the Foxconn ransomware attack and unpack what a claim like that could mean in the real world: intellectual property exposure, supply chain disruption, customer impact, and the uncomfortable truth that recovery is only one part of the story when data walks out the door.From there, we switch into CISSP Domain 7 Security Operations mode and work through practical exam-style questions with the “how would this hold up at work” mindset. We break down why live forensics imaging can be the right call during an insider threat investigation, using the order of volatility and the kinds of RAM artifacts that disappear the moment you shut a machine down. We also tackle a Patch Tuesday nightmare scenario where a CVSS 9.8 vulnerability is already being exploited but the change advisory board will not meet for ten days, and we explain why an emergency change process plus compensating controls is the mature security operations answer.We also cover a common privileged access failure where a domain admin uses an elevated account for email and browsing, and how least privilege plus a privileged access workstation (PAW) architecture can prevent a single phish from becoming domain compromise. Finally, we sharpen the fundamentals with an RTO/RPO recovery timeline question and a SIEM brute force threshold miss that illustrates false negatives and the need for better tuning and behavioural baselines.Subscribe for weekly CISSP training, share this with a study partner, and leave a review so more security pros can find the show. What topic do you want me to turn into practice questions next?Gain exclusive access to 360 FREE CISSP Practice Questions at FreeCISSPQuestions.com and have them delivered directly to your inbox! Don't miss this valuable opportunity to strengthen your CISSP exam preparation and boost your chances of certification success. Join now and start your journey toward CISSP mastery today!
In this episode, host Kim Coombes is joined by security experts John Chirillo and Rob Di Girolamo, along with Microsoft Security expert Robin Camirand, to unpack the most important insights from the RSAC 2026 Conference. The discussion covers the rapid rise of Agentic AI security, the need to defend at machine speed, and the industry's shift toward active defense as traditional response models struggle to keep up. The team also explores the growing importance of post-quantum cryptography as organizations prepare for the next phase of cryptographic risk. Throughout the conversation, the panel reflects on RSAC's defining theme, the “power of community,” and why collective defense is essential as threats become faster, more automated, and more complex. Whether you're tracking AI-driven risks, planning for quantum readiness, or looking for clear takeaways from RSAC 2026, this episode delivers practical insights from experienced security leaders. Moderator: Kimberlee Coombes, Security Solution Architect, Connection Guest: John Chirillo, Principal Security Architect, Connection Guest: Rob Di Girolamo, Senior Security Architect, Connection Guest: Robin Camirand, Inside Solution Architect and Microsoft Security SME, Connection Show Notes 00:00 Introduction to RSAC 2026 Trends 02:43 AI as a Tool and Threat in Cybersecurity 05:22 Microsoft's Perspective on Identity and Security 08:27 AI as a New Attack Surface 10:58 The Future of Security Operations and SOC 13:31 AI-Driven Attacks and Vulnerability Management 16:17 Quantum Security: A Growing Concern 18:51 Final Thoughts and Future Considerations
RSAC Conference 2026 made one thing impossible to miss: AI is on every sticker, every slide, and every booth. Sorting signal from marketing has never been harder. Lisa Liu, Corporate Marketing and Communications Manager at Stellar Cyber, joins this Brand Highlight to continue a conversation that started on the show floor in San Francisco and was worth picking up again once the noise settled. Stellar Cyber has been incorporating machine learning into every layer of its security platform since 2015, well before AI became the marketing default. The position Lisa Liu brings is direct: AI is not a one-size-fits-all solution. A large language model is not the most efficient way to parse log data, and slapping an AI label on existing functionality is not the same as designing for the analyst pain points at every stage of detection, investigation, and response. The conversation closes on the autonomous SOC question, where Stellar Cyber argues for a human-augmented approach. Promises of complete autonomy deserve healthy skepticism; guardrails matter, and keeping a human analyst in the loop is what allows AI mistakes to be caught and contained before they cascade. It is a Brand Highlight worth a few minutes for anyone trying to separate AI substance from AI theater in security operations. This is a Brand Highlight. A Brand Highlight is a ~5 minute introductory conversation designed to put a spotlight on the guest and their company. Learn more: https://www.studioc60.com/creation#highlight GUEST Lisa Liu, Corporate Marketing and Communications Manager, Stellar Cyber | On LinkedIn: https://www.linkedin.com/in/lisaaliu/ RESOURCES Learn more about Stellar Cyber: https://stellarcyber.ai/ View all of our RSAC Conference 2026 coverage: https://www.itspmagazine.com/rsac26 Are you interested in telling your story? ▶︎ Full Length Brand Story: https://www.studioc60.com/content-creation#full ▶︎ Brand Spotlight Story: https://www.studioc60.com/content-creation#spotlight ▶︎ Brand Highlight Story: https://www.studioc60.com/content-creation#highlight KEYWORDS Lisa Liu, Stellar Cyber, Sean Martin, brand story, brand marketing, marketing podcast, brand highlight, RSAC Conference 2026, Multi-Layer AI, human-augmented autonomous SOC, machine learning, Open XDR, NG-SIEM, security operations, AI in cybersecurity, agentic AI, SOC analyst, security platform Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
Guests: Eric Foster, CEO, Tenex.AI Bashar Abouseido, President, Tenex.AI Topics: "10X SOC" sounds great. But for an organization stuck in "SIEM 1.0" with poor data quality and manual workflows, is "AI-native MDR" a "leapfrog" opportunity or a recipe for disaster? We've seen the rise of "Decoupled SIEM" and security data lakes. Does a "Modern SIEM" even need to exist if an MDR platform has an agentic layer doing the heavy lifting? You've argued for AI-native over AI-bolted-on. For an end user, what are the tangible differences of using "AI inside a legacy SIEM" versus using an "AI-native separate product"? What is the one task you thought AI would handle by now that still requires a senior human analyst to step in? If a CISO is using an AI MDR, "Mean Time to Detect" (MTTD) starts to look like a vanity metric because the machine is instant. What is the new golden metric for an AI-powered SOC? Is it "Time to Context," "Reduction in Human Toil," or something else? How do you help a skeptical SOC Manager—who has been burned by false positives for a decade—trust an autonomous agent to perform a "containment" action at 3:00 AM? Resources: EP227 AI-Native MDR: Betting on the Future of Security Operations? EP10 SIEM Modernization? Is That a Thing? The original "10X" paper "Autonomic Security Operations: 10X Transformation of the Security Operations Center"
In today's Cloud Wars Minute, I explain how ServiceNow is enabling secure, scalable adoption of AI agents across the enterprise. Highlights 00:03 — ServiceNow is joining forces with Zenity, the first security and governance platform that's been purpose-built for AI agents. Zenity is becoming a ServiceNow build partner, bringing with it a range of capabilities to ServiceNow Security Operations, including agent security, posture management, and vulnerability assessment. 00:25 — Deepak Kolingivadi, VP of Product Management and Head of Security Products at ServiceNow, said the following about this new partnership: “AI agents are transforming how work gets done across the enterprise, including Security Operations. Our partnership with Zenity strengthens the ServiceNow AI control tower and Security Operations solutions.” 01:01 — Now, collectively, these new capabilities bring to ServiceNow customers a greater ability to scale the use of AI agents safely and with full confidence as part of their existing SecOps processes. And what we're seeing here is ultimately a new category, AI Security Operations, or AI SecOps. 01:26 — It's also important to note that by embedding this governance layer through its build partnership, ServiceNow is demonstrating that it's truly ahead of the curve here. All new products delivered by software vendors need integrated security and governance, and agentic AI is no exception. 01:58 — The key word here is scale. ServiceNow has the tools to drive AI across the breadth of a business, and now through Zenity, it's delivering the ability to do this at scale. Visit Cloud Wars for more.
The security industry has spent years debating which tools to buy. Impetum is asking a different question: are the tools you already have actually working? Founded by incident responders who saw the same failures across hundreds of breaches, Impetum built the Persistent Purple Team platform to simulate advanced threat actors inside customer environments on a continuous monthly basis -- not as a one-time engagement, but as an ongoing relationship built around real data, custom TTPs, and a measurable Threat Resilience Score. Matt Stewart and Alex Grohmann spoke with Sean Martin and Marco Ciappelli at RSAC Conference 2026 about what they are hearing on the show floor: agentic AI is accelerating the speed of compromise and exposing vulnerabilities in legacy systems that have been dormant for decades. Against that backdrop, the value of knowing -- not assuming -- that your detection and response capabilities hold up becomes critical. The platform builds that knowledge through live-fire exercises using an organization's own data, validating patch management, XDR, SIEM tuning, and post-compromise detection in a way no annual pen test can. The conversation also touched on the structural talent problem agentic AI is creating inside SOCs. As AI fills the level one analyst role, the pipeline for developing level two analysts and incident responders is narrowing. Impetum sees persistent purple teaming as the training ground that closes that gap -- giving existing teams the repeated, realistic practice they need to respond with confidence when an actual breach begins. Impetum targets mid-size organizations that have the right security tools but lack the budget, bandwidth, and access to industry events to keep those tools continuously validated against evolving attack paths. For those teams, the platform delivers something an annual report cannot: a documented, ongoing record of what works, what does not, and where the program is heading. This is a Brand Spotlight. A Brand Spotlight is a ~15 minute conversation designed to explore the guest, their company, and what makes their approach unique. Learn more: https://www.studioc60.com/creation#spotlight GUEST Matt Stewart, Co-Founder, Impetum Alex Grohmann, Co-Founder, Impetum LinkedIn: https://www.linkedin.com/in/alexandergrohmann/ RESOURCES Impetum / Persistent Purple Team: https://www.persistentpurpleteam.com ITSPmagazine RSAC Conference 2026 coverage: https://www.itspmagazine.com/rsac-2026-conference-san-francisco-usa-cybersecurity-event-infosec-conference-coverage Are you interested in telling your story? ▶︎ Full Length Brand Story: https://www.studioc60.com/content-creation#full ▶︎ Brand Spotlight Story: https://www.studioc60.com/content-creation#spotlight ▶︎ Brand Highlight Story: https://www.studioc60.com/content-creation#highlight KEYWORDS Matt Stewart, Alex Grohmann, Impetum, Persistent Purple Team, Remedium Security, Sean Martin, RSAC Conference 2026, brand spotlight, brand story, brand marketing, marketing podcast, purple teaming, continuous security validation, threat resilience, CISO, security operations, SOC, red team, blue team, incident response, agentic AI, MITRE ATT&CK, penetration testing, cybersecurity Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
In the middle of a major incident, security teams face a brutal paradox: the faster things move, the harder it becomes to capture what's actually happening. Cydarm Technologies was built to solve exactly that. Vaughan Shanks, Co-Founder and CEO, describes the platform as a system of record for the SOC -- a purpose-built case management tool that captures who knew what, when, and why, in real time, throughout the lifecycle of an incident. Most of Cydarm's customers sit in government, defense, and critical infrastructure -- organizations where the pressure of regulatory compliance, legal accountability, and board-level reporting is highest. But the value extends well beyond compliance. Shanks draws a direct line from his time in Australian federal government to the philosophy behind Cydarm: good record keeping is good governance. When a capital-I incident is declared, legal, HR, communications, the C-Suite, and the board all need a view in. Cydarm's fine-grained, attribute-based access control makes it possible to give each stakeholder exactly the access they need -- and no more. What sets Cydarm apart from the ticketing systems most teams already have? Shanks puts it plainly: ITSM was built for IT service management, not adversarial cyber threats. The volume, velocity, and variety of SecOps are simply different. Cydarm is designed to feel more like WhatsApp and less like ITSM -- rich data format support, Easy Connect integrations, and a collaborative experience built specifically for high-frequency security operations. Teams that have built workarounds in existing tools know the maintenance burden that comes with it. Cydarm eliminates that mess. The post-incident dimension is where the system of record pays compounding dividends. Shanks outlines three paths: individual incident reports with adjustable significance levels for different audiences; longitudinal metrics capture that reveals the threat environment your controls aren't blocking; and resource justification data that gives security leaders the evidence to defend headcount and budgets. One customer -- a security leader at a major household brand -- had never experienced a breach, and had long struggled to justify the size of their team. With Cydarm's metrics, they finally had the data to make the argument. This is a Brand Spotlight. A Brand Spotlight is a ~15 minute conversation designed to explore the guest, their company, and what makes their approach unique. Learn more: https://www.studioc60.com/creation#spotlight GUEST Vaughan Shanks, Co-Founder and CEO, Cydarm Technologieshttps://www.linkedin.com/in/vaughan-shanks/ RESOURCES Cydarm Technologies: https://www.cydarm.com KEYWORDS Vaughan Shanks, Cydarm Technologies, Sean Martin, brand spotlight, brand story, brand marketing, marketing podcast, cyber incident response, SOC case management, security operations, incident management platform, system of record, RSAC Conference 2026, NIST incident response, playbook management, SecOps, ITSM alternatives, post-incident review, threat metrics, CISO accountability Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
Madhav Nakar — AI Security Researcher and Documentarian of Spirituality and Play No Password Required Season 7: Episode 3 - Madhav Nakar Madhav Nakar is a Security Researcher at BeyondTrust specializing in identity threats, endpoint security, and cloud attack paths. With a background in theoretical mathematics, his current research focuses on analyzing attacker behavior to build practical systems of detection. In this episode, Madhav shares the pivotal moments that shaped his career, including his first experience witnessing a nation-state attack unfold in real time from his seat in a SOC. He explains how mathematical thinking sharpens security strategy and why strong research is rooted in exploration, not predetermined outcomes. Jack Clabby of Carlton Fields, joined by co-host Kayley Melton of the Cognitive Security Institute, welcomes Madhav for a conversation on modern cyber defense. From AI-driven attacks and agentic systems to privilege escalation risks in role-based access environments, Madhav breaks down what teams are getting wrong about AI and why defending against AI increasingly requires AI-powered tools. The conversation turns to Madhav's philosophy of “serious play,” where curiosity, experimentation, and failure fuel better research and resilience. He also shares insights from his spiritual and philosophy project, The Fire of Knowing, exploring consciousness and belief through a neutral lens. In the Lifestyle Polygraph, Madhav pitches a cybersecurity documentary, debates growth versus comfort, and reflects public dancing experiments. Follow Madhav Nakar here: https://www.linkedin.com/in/madhav-nakar/ Follow "The Fire of Knowing" on Instagram and Youtube! CHAPTERS: 00:00 Introduction with Kayley and Jack 08:08 Transition from Theoretical Math to Cybersecurity 16:13 Exploring Spiritual Traditions and Madhav's Documentary 19:48 The Intersection of Art and Science in Content Creation 25:20 The Lifestyle Polygraph: Challenging Perspectives on Security
Security teams are under more pressure than ever, reacting at human speed while systems, identities, and AI agents operate at machine speed. In this episode of Security Matters, host David Puner sits down with cybersecurity leader and former FBI executive MK Palmore to explore why defenders struggle to keep pace and what it takes to regain control.From AI agents that overshare sensitive data to cloud misconfigurations that never seem to disappear to the persistent success of ransomware, MK explains how complexity, vendor sprawl, and overloaded teams create gaps that attackers continue to exploit. The conversation highlights how identity across human, machine, and emerging agent types has become the center of modern security and why fundamentals, prioritization, and platform thinking matter more than ever.Listeners will hear insight on: • Identity at machine speed and the rise of autonomous access • Why attackers still win more than 51 percent of the time • How ransomware continues to succeed despite industry progress • Why SMBs face “mission impossible” expectations • The true cost of vendor sprawl and operational overload • What effective security leadership looks like in the current threat environmentIf you work in identity, security operations, strategy, or leadership, this discussion cuts through hype and focuses on the realities defenders face and how to push back against the constant pressure of the tyranny of the now.
⬥EPISODE NOTES⬥ The security operations center has always been a battleground of volume, velocity, and human endurance. Analysts have long faced the impossible math of too many alerts, too few hours, and too much at stake. For years, the industry promised automation would change that equation -- but the technology was never quite ready to deliver. That moment, according to Richard Stiennon, has now arrived. Stiennon, Chief Research Analyst at IT-Harvest, has spent two decades tracking every corner of the cybersecurity vendor landscape. His data now shows more than 61 net-new SOC automation vendors -- companies that did not exist a few years ago -- built from the ground up to replace the work of tier-one, tier-two, and tier-three analysts. Some of these vendors launched in January 2024 and reached $1 million in ARR by April. By the end of 2025, several were reporting $3 million ARR. These are not incremental improvements. They represent a structural shift in how security operations can be run. What makes this generation of SOC automation different from earlier SIEM and SOAR tooling is scope and autonomy. The value proposition is blunt: 100% alert triage, 24 hours a day, 7 days a week -- with automated case building, threat investigation, and response actions including machine isolation and reimaging. Stiennon points to a CISO he met, speaking under Chatham House rules, who disclosed that a large enterprise had already eliminated its entire human SOC team. He predicts that disclosure will go public before long. The conversation also explores the business context question that security leaders frequently wrestle with: are these AI-driven SOC tools operating with a narrow cyber mandate, potentially optimizing for security metrics at the expense of business continuity? Stiennon pushes back on that concern, arguing that large language models are already trained on the full breadth of human knowledge -- they understand business context at a level that exceeds most organizations' internal documentation. The more pressing risk, he suggests, is not that AI will act outside business intent, but that organizations will move too slowly to benefit. Waiting six months for a proof-of-concept report while spending a million dollars on human SOC operations is not due diligence -- it is opportunity cost. The conversation also touches on data privacy in AI-driven security, the role of federated learning and fully homomorphic encryption for compliance-sensitive environments, and what security leaders can do today to evaluate and accelerate their own adoption timeline. Stiennon will be at RSA Conference 2026 with his new book, Guardians of the Machine Age: Why AI Security Will Define Digital Defense, continuing to make the case for a field that is moving faster than most organizations are prepared to acknowledge. ⬥GUEST⬥ Richard Stiennon, Chief Research Analyst at IT-Harvest | Website: https://it-harvest.com/ On LinkedIn: https://www.linkedin.com/in/stiennon/ ⬥HOST⬥ Sean Martin, Co-Founder at ITSPmagazine, Studio C60, and Host of Redefining CyberSecurity Podcast & Music Evolves Podcast | Website: https://www.seanmartin.com/ ⬥RESOURCES⬥ IT-Harvest | https://it-harvest.com/ Richard Stiennon on LinkedIn | https://www.linkedin.com/in/stiennon/ Guardians of the Machine Age: Why AI Security Will Define Digital Defense (Richard Stiennon) | Available via IT-Harvest and major booksellers RSAC Conference 2026 Coverage on ITSPmagazine | https://www.itspmagazine.com/rsac-2026-conference-san-francisco-usa-cybersecurity-event-infosec-conference-coverage The Future of Cybersecurity Newsletter | https://www.linkedin.com/newsletters/7108625890296614912/ More Redefining CyberSecurity Podcast episodes | https://www.seanmartin.com/redefining-cybersecurity-podcast Redefining CyberSecurity Podcast on YouTube | https://www.youtube.com/playlist?list=PLnYu0psdcllS9aVGdiakVss9u7xgYDKYq ⬥ADDITIONAL INFORMATION⬥ On Podcast: https://www.seanmartin.com/redefining-cybersecurity-podcast On YouTube: https://www.youtube.com/playlist?list=PLnYu0psdcllS9aVGdiakVss9u7xgYDKYq Newsletter: https://itspm.ag/future-of-cybersecurity Contact Sean: https://www.seanmartin.com/ ⬥KEYWORDS⬥ richard stiennon, it-harvest, sean martin, soc automation, ai security, security operations center, threat detection, autonomous response, alert triage, security operations, cybersecurity vendors, ai agents, large language models, federated learning, siem, soar, redefining cybersecurity, cybersecurity podcast, redefining cybersecurity podcast Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
What does it take to turn the dream of an autonomous SOC into something organizations can actually deploy? Subo Guha, Senior Vice President of Product Management at Stellar Cyber, joins Sean Martin to share how the company's AI-driven security operations platform is making that vision a reality. Stellar Cyber serves SOC teams across more than 50 countries, with a primary focus on MSPs and MSSPs supporting the underserved mid-market, though marquee enterprise customers like Canon are also part of the portfolio.How can agentic AI change the way SOC teams handle alert overload? Guha describes what he calls a "digital army" of AI agents that work around the clock to automate alert triage and catch phishing attacks. The system filters 70 to 80 percent of incoming alerts, allowing analysts to focus on the 20 percent that matter most. With attackers using AI to launch faster and more frequent campaigns, Stellar Cyber takes a human-augmented approach, meaning the AI learns from analyst interactions and continuously guides the SOC team toward faster, more accurate remediation.Why does this matter for MSPs operating on thin margins? Guha explains that the autonomous SOC capability layered on top of Stellar Cyber's XDR platform allows MSSPs to serve more customers, reduce mean time to repair, and grow their tenant base without proportionally increasing staff. When MSSPs grow revenue, Stellar Cyber grows alongside them, creating a mutually beneficial model that ultimately means more organizations get protected.This is a Brand Highlight. A Brand Highlight is a ~5 minute introductory conversation designed to put a spotlight on the guest and their company. Learn more: https://www.studioc60.com/creation#highlightGUESTSubo Guha, Senior Vice President of Product Management, Stellar Cyber @LinkedInRESOURCESLearn more about Stellar Cyber: https://stellarcyber.aiAre you interested in telling your story?▶︎ Full Length Brand Story: https://www.studioc60.com/content-creation#full▶︎ Brand Spotlight Story: https://www.studioc60.com/content-creation#spotlight▶︎ Brand Highlight Story: https://www.studioc60.com/content-creation#highlightKEYWORDSSubo Guha, Stellar Cyber, Sean Martin, brand story, brand marketing, marketing podcast, brand highlight, autonomous SOC, agentic AI, security operations, XDR, NDR, MSSP, MSP, alert triage, AI-driven security, Open XDR, Gartner Magic Quadrant, phishing detection, SOC automation Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
© 2020-2026 Ivy Podcast Discovery LLC
