Authors

Subscribe:.rss.atom.json.md

Publishes 1 feed

• Secure Networks: Endace Packet Forensics Files

  "Secure Networks: Endace Packet Forensics Files" features interviews with leading cybersecurity and networking experts from companies such as Cisco, Darktrace, Palo Alto Networks, and others. It focuses on the issues that Security, Network Operations and DevOps teams face in securing and managing their networks and applications and provides insights into best practices and future developments.

  10 posts · theirs

Lately

• Episode 67: Erik Dove, Security Sales Engineer and incident response expert, Cisco

  Secure Networks: Endace Packet Forensics Files · 2026-08-03

• Episode 65: Cody Spooner, Senior Sales Engineer and IR expert, Corelight

  Secure Networks: Endace Packet Forensics Files · 2026-05-28

• Episode 65: Andrew Cook, CTO Recon InfoSec

  Secure Networks: Endace Packet Forensics Files · 2026-03-03

• Episode 64: Steve Fink, CTO and CISO at Secure Yeti

  Secure Networks: Endace Packet Forensics Files · 2025-11-07

• Episode 63: Jack Chan, VP of Product and Field CTO at Fortinet

  Secure Networks: Endace Packet Forensics Files · 2025-10-01

• Episode 62: Jessica (Bair) Oppenheimer, Cisco's Director of Security Operations

  Secure Networks: Endace Packet Forensics Files · 2025-08-12

• Episode 61: Jean-Pierre Bergeaux - Federal CTO, GuidePoint Security

  Secure Networks: Endace Packet Forensics Files · 2025-06-11

• Episode 60: James Spiteri - Director of Product Management for Security Analytics at Elastic

  Secure Networks: Endace Packet Forensics Files · 2025-02-26

• Episode 59: Matt Bromiley - SANS Author and Instructor | Veteran Threat Hunting Expert

  Secure Networks: Endace Packet Forensics Files · 2024-11-07

• Episode 57: Ryan Chapman - SANS Author and Instructor | Veteran DFIR Expert

  Secure Networks: Endace Packet Forensics Files · 2024-08-26

Everything on this page was read from markup Michael Morris published — a rel="me" link, an h-card, or the feed’s own author element. Nothing was inferred from anywhere else. To correct or remove it, get in touch. Machine-readable: JSON