Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Autonomous AI agents are no longer experimental—they’re writing code, executing commands, and making decisions in real time. But as AI coding agents become more powerful, they’re also introducing a new and often invisible attack surface. In this video, we break down: AI agents can install packages, run scripts, and modify systems instantly—often without traditional visibility. That means security teams need to rethink how they monitor and protect their environments.

A maximum-severity vulnerability is hitting React Server Components - and if you're running Next.js, you may be vulnerable by default. React disclosed CVE-2025-55182, nicknamed React2Shell, an unauthenticated remote code execution (CVSS 10.0) affecting React Server Components via the Flight protocol. Next.js tracks downstream exposure as CVE-2025-66478: That means internet-wide scanning is likely. Who’s affected?

84% of developers are using or planning to use AI tools in their workflow (Stack Overflow, 2025). AI coding assistants like Codex, GitHub Copilot, and CodeWhisperer are changing how we build software. But here’s the real question: Who secures AI-generated code? In this video, we break down: If you’re using AI to write code, you need: AI-generated code is still code. It must be reviewed, validated, and monitored.

What if you could analyze system calls, containers, and cloud workloads the same way you analyze packets in Wireshark? That’s exactly what Stratoshark does — deep visibility into hosts, containers, and cloud activity. Stratoshark is an open source analysis tool that brings the Wireshark-style workflow to system calls, containers, hosts, and cloud audit events.

Containers are supposed to be isolated — but what happens when that isolation breaks? In this video, we explain critical container escape vulnerabilities in runc, the default container runtime used by Docker and Kubernetes, and why they represent a serious container security risk. Recent disclosures known as the “Leaky Vessels” vulnerabilities show how a compromised container can escape its sandbox, access the host filesystem, and potentially take over the node.

It’s December, and Kubernetes 1.35 is almost here - with security changes that can break workloads or access paths if you upgrade unprepared. This video is a fast, practical security edition rundown for security and platform engineers: what changed, why it matters, and what to verify before you roll 1.35 into production. In this video (Kubernetes 1.35 security highlights): If you want a deeper dive, comment with what you’re running today (managed K8s vs self-managed, distro, container runtime, auth setup) and I’ll break down the safest upgrade path.