How to Lose Millions Without Getting Hacked

How to Lose Millions Without Getting Hacked

Title history
  • How to Lose Millions Without Getting Hacked — observed on 20261111-0311 UTC (YouTube)
🎙 Dino Pusulaki and Craig Duckworth 👥 223 📅 November 11, 2026 ⏱ 36 min 👁 1 📄 expert opinion 🧭 2026-11-11
Available in: English (current) Français

Keywords

ICSOT securityPLCasset inventoryincident response

Summary

This episode of Industrial Cybersecurity Insider features a conversation between Dino Pusulaki and Craig Duckworth about common mistakes in industrial control system (ICS) security that lead to significant financial losses without any external hacker involvement. They share several real-world incidents: a vending machine with a duplicate IP address taking down a $35 million wheel press, an IT technician accidentally wiping IP addresses from 30 Siemens PLCs, federal agents scanning a beverage plant’s control network, and a steel plant dealing with WannaCry and SMBv1 vulnerabilities. The discussion highlights the IT/OT collision, the air gap myth, and the lack of effective asset inventory and continuous monitoring. They propose five ICS critical controls: defensible architectures, vulnerability management, continuous monitoring, remote access control, and incident response. They emphasize the importance of a tabletop exercise and naming an OT security owner per site. The episode provides practical advice for manufacturers to prevent such costly mistakes.

150 words

Critical Evaluation

Value of the Information & Strength of the Argument

The video offers high practical value by presenting concrete failure scenarios that are often overlooked in cybersecurity discussions, such as accidental IT actions, duplicate IP addresses, and the impact of unpatched systems. The argumentation is grounded in real-world experience, making the cases credible and compelling. The speakers effectively argue that these incidents are more common than acknowledged and that a lack of monitoring and clear ownership exacerbates the risks. They advocate for a collaborative IT/OT approach and provide actionable steps, such as conducting a tabletop exercise and improving asset inventory. The logical flow from incident stories to solutions strengthens the overall argumentation.

Scientific Rigor, Source Quality, Title Accuracy

The content is presented as anecdotal evidence from the speakers’ professional experiences, without citing external sources or publications. The title accurately captures the theme of financial losses from non-hacker-related mistakes, and the discussion stays true to that theme. The rigor is moderate: while the stories are detailed and plausible, the lack of verifiable sources or references reduces scientific rigor. The title-content alignment is strong, and the video does not overpromise beyond what is presented.

191 words

Title / Content Match

The title accurately reflects the content: it discusses costly mistakes that are not hacker attacks, and provides prevention steps.

Quality & Reliability

8/10

The speakers are experienced OT security professionals sharing real incidents and actionable advice, but no external sources or citations are provided, relying on anecdotal evidence.

Key Moments

Contribution & Novelties

The episode provides valuable insight into non-malicious but costly OT security failures, emphasizing the importance of asset inventory and continuous monitoring. It offers a practical framework of five ICS critical controls. The discussion is particularly useful for bridging the IT/OT gap.

Pour aller plus loin :

  • Industrial control system — Overview of ICS and its security challenges.
  • SIMATIC S7 — Details on Siemens PLCs and the S7 protocol.
  • WannaCry ransomware attack — Context on the WannaCry incident and SMBv1 exploitation.
  • NIST SP 800-82 — Guide to Industrial Control Systems Security, relevant for defensive architecture guidance.

95 words

Radar Profile

The radar profile shows balanced scores across information quantity, quality, technical level, and reliability, with slightly lower reliability due to the lack of formal sources. The technical level indicates appropriate depth for a professional audience, and the high quality and quantity scores reflect the practical insights shared.

Reliability 7/10