Cybersecurity Under Pressure. Real Attacks, Real Lessons

Cybersecurity Under Pressure. Real Attacks, Real Lessons

Antonio González
Country USA
Genres Technology
Language EN
Episodes 67
Latest 20.11.2026

This podcast breaks down real cybersecurity incidents to understand what actually went wrong, not in theory, but in practice. Each episode analyzes a recent attack, explains the technical mechanics in clear language, and translates them into concrete lessons for security, engineering, and business teams. Topics covered include OT security, ICS cybersecurity, industrial control systems, critical infrastructure protection, NIS2 compliance, Zero Trust architecture, operational technology resilience, railway cybersecurity, automotive security, and cyber-physical systems.

Episodes

  • The Patch Is Deferred. Is the Compensating Firewall Rule Still There?
    The Patch Is Deferred. Is the Compensating Firewall Rule Still There? 20.11.2026 46m
    An OT patch is deferred because production cannot stop. The risk register says a firewall rule compensates for the exposure. But after maintenance, troubleshooting or a loss of connectivity with the SOC, what evidence shows that the rule still blocks the intended path?This technical decision analysis uses a hypothetical plant scenario to compare configuration change alerts, baseline checks and tests of actual traffic reachability. It also examines what evidence the plant can preserve locally when central logging is unavailable, who owns escalation, and what should trigger a review of the patch...
  • The UDS Routine Works. Does It Refuse the Wrong Vehicle State?
    The UDS Routine Works. Does It Refuse the Wrong Vehicle State? 18.11.2026 41m
    A valid diagnostic session can still issue a request the vehicle should refuse. This episode opens with a hypothetical remote-attack scenario, not a report of a documented incident. It asks when an ECU should reject a UDS RoutineControl (0x31) request because the vehicle state is unsafe, stale or cannot be verified.We compare state checks at the gateway and at the target ECU, distinguish a diagnostic response from what the routine actually does, and discuss how hardware-in-the-loop fault injection can test those assumptions. The hardest question comes after the routine starts: what should happ...
  • Shared Railway Maintenance Credentials: What Does the Safety Case Allow?
    Shared Railway Maintenance Credentials: What Does the Safety Case Allow? 16.11.2026 33m
    A shared maintenance password on a legacy train is a security risk. Replacing it can also affect diagnostic compatibility, supplier support and the evidence behind the Safety Case. What can the operator change now, and what needs a planned engineering change?This technical decision analysis weighs individual access at the gateway, controls on maintenance sessions and a phased move away from shared credentials. It examines what those measures leave exposed at a local diagnostic port, what evidence the operator and supplier need before making changes, and how to compare the cost of keeping compe...
  • Validating Automotive Supplier VEX Claims
    Validating Automotive Supplier VEX Claims 13.11.2026 31m
    A supplier declares an automotive ECU not affected by a vulnerability identified in a software component. What evidence should the manufacturer request before relying on that assessment?This Friday episode explores a hypothetical supplier-assurance scenario involving closed-source firmware, a safety-related ECU and production constraints. The discussion contrasts component absence with code reachability, examines build-specific evidence and considers the trade-offs between accepting an assessment, requesting further investigation, applying containment and updating software.Editorial clarificat...
  • PLC Logic Changes During Live Production: An OT Pressure Test
    PLC Logic Changes During Live Production: An OT Pressure Test 11.11.2026 32m
    What if a PLC program change is flagged while a factory remains in production and process indicators appear normal? This Wednesday episode uses a hypothetical engineering scenario to examine the gap between apparent process stability and confidence in controller logic.We compare possible change paths, engineering access, network visibility, controller state and the safety consequences of an unverified response. An online edit, a compromised engineering workstation and manipulation of operator views are hypotheses discussed in the dialogue, not established findings from a documented intrusion....
  • Who Can End a Supplier Session When the Line Is Down?
    Who Can End a Supplier Session When the Line Is Down? 09.11.2026 32m
    A production line is stopped, and a supplier needs an engineering connection to diagnose the fault. In this explicitly hypothetical CUP scenario, the same legacy session can also download a PLC program. The question is who can constrain and end its authority when recovery is urgent.We trace the path from supplier identity through remote access, a plant-controlled workstation, the engineering tool and the controller. A broker disconnect, account disable and controller-side termination do not necessarily have the same effect; none can undo a program already downloaded. MFA, recording and a jump...
  • How Attackers Weaponized Evernote Against SCADA
    How Attackers Weaponized Evernote Against SCADA 06.11.2026 42m
    What happens when a trusted note-taking workflow becomes a route into an industrial control environment? This episode examines an Evernote-to-SCADA attack path and the boundary between ordinary collaboration tools and operational access.We consider how attackers can use familiar cloud content, links or shared documents to influence users and systems that support industrial operations. The practical questions are where trust is established, what privilege is needed to reach an engineering workstation or SCADA component, and which actions the available evidence actually supports. A suspicious do...
  • How Incomplete SBOMs Hide Critical Vulnerabilities
    How Incomplete SBOMs Hide Critical Vulnerabilities 04.11.2026 42m
    An SBOM is only as useful as the components and relationships it captures. This episode examines how incomplete software bills of materials can hide critical vulnerabilities when transitive dependencies, embedded packages, firmware or build artifacts are missed.We discuss the difference between generating an SBOM and accepting it as evidence: checking scope against the delivered build, reconciling package and version identifiers, testing dependency depth and validating the tool configuration. A clean vulnerability scan cannot establish absence of risk if the underlying inventory is incomplete....
  • VMS Privilege Escalation: When Edit Rights Become Server Control | CUP Micro Brief
    VMS Privilege Escalation: When Edit Rights Become Server Control | CUP Micro Brief 03.11.2026 2m
    Application edit rights and operating-system administration are not the same security boundary. This CUP Micro Brief shows how an over-privileged video-management service can turn a limited application role into control of the underlying server. Related CUP episodes:Siemens Siveillance: When Edit Access Enables Code ExecutionJohnson Controls Airwall: The Risk Behind a Hardcoded KeyIndustrial Identity Security: The Risk in Software-Defined Factories
  • Stopping Fake Emergency Braking in Connected Cars
    Stopping Fake Emergency Braking in Connected Cars 02.11.2026 41m
    Can a connected vehicle reject a forged emergency-braking warning without suppressing a legitimate safety message?This episode examines false emergency electronic brake light warnings in connected-car and V2X environments. We break down the trust boundary between a valid sender credential, a plausible road event and the vehicle response that follows. Cryptographic validity can authenticate a source, but it does not automatically prove that the reported event is true.The discussion covers message authentication, plausibility checks, certificate and credential revocation, duplicate and anomalous...
  • OT Maintenance Windows: Monitoring Temporary Access | CUP Focus
    OT Maintenance Windows: Monitoring Temporary Access | CUP Focus 31.10.2026 4m
    Planned downtime concentrates contractors, temporary access, firmware changes and disabled alerts in the same period. This CUP Focus explains why maintenance windows require tighter monitoring and evidence, not relaxed controls.Format: CUP Focus, a self-contained section from the Cybersecurity Under Pressure archive.Related CUP episodes:Kinetic AI and Critical Infrastructure: Connecting Cyber and Physical RiskOT Remote Access: Closing the Path When the Work EndsOT Session Hijacking: Revoking Trusted Engineering AccessLegacy VPNs in OT: Remote Access and the Cost of Disruption
  • Oldsmar Revisited: Remote Access and the Limits of the Evidence
    Oldsmar Revisited: Remote Access and the Limits of the Evidence 30.10.2026 38m
    Editorial context: The February 2021 Oldsmar incident was initially reported as an unauthorized remote-access attempt to alter water-treatment dosing. In 2023, the FBI said it could not confirm that a targeted cyber intrusion had initiated the incident. Treat the reported attack sequence discussed in this episode as an account with unresolved evidentiary limits, rather than a proven intrusion. Authorities reported no significant effect on treated water and no danger to the public.Revisit the Oldsmar case through the operational questions it raises for water utilities: who can reach an operator...
  • Industrial 5G Security: Protecting the Wireless Conduit | CUP Focus
    Industrial 5G Security: Protecting the Wireless Conduit | CUP Focus 29.10.2026 5m
    A wireless conduit cannot be protected like a copper port. This CUP Focus connects 5G device identity, subscriber credentials, edge routing and passive application monitoring without adding latency to deterministic industrial traffic.Format: CUP Focus, a self-contained section from the Cybersecurity Under Pressure archive.Related CUP episodes:Industrial 5G Jamming: Protecting Control When the Radio FailsIndustrial 5G Security: Designing for Lost ConnectivityWhen 40 Milliseconds Become an OT Incident | CUP Micro BriefFRMCS Security: Why a Mobile Network SLA Is Not a Safety Case
  • Railway Diagnostic Security: Protecting Privileged Access | CUP Micro Brief
    Railway Diagnostic Security: Protecting Privileged Access | CUP Micro Brief 29.10.2026 2m
    A railway diagnostic platform may not execute the safety function, but it can expose topology, privileged sessions and a pivot path toward operational assets. This CUP Micro Brief explains why monitoring systems still belong inside the security boundary. Related CUP episodes:Frauscher FDS102: Securing Railway Diagnostic AccessLegacy Railway Security: Patching and Validation ConstraintsRailway OT Segmentation: Protecting the Certified CoreRailway Cybersecurity: Service Risk Beyond the SIL Boundary
  • How Volt Typhoon Weaponizes Active Directory
    How Volt Typhoon Weaponizes Active Directory 28.10.2026 40m
    Volt Typhoon turns trusted administration into a path toward critical infrastructure. This episode examines how stolen credentials, Active Directory compromise and living-off-the-land activity can undermine confidence in the systems operators depend on.We explore the identity boundary between enterprise IT and operational technology, the evidence defenders need to distinguish legitimate administration from an intrusion, and the recovery decisions that follow a suspected domain compromise.Sources and further reading:Joint CISA advisory AA24-038A: https://www.cisa.gov/news-events/cybersecurity-a...
  • SBOM and VEX: Proving Vulnerability Reachability | CUP Focus
    SBOM and VEX: Proving Vulnerability Reachability | CUP Focus 27.10.2026 4m
    Component presence and practical exposure are different facts. This CUP Focus explains how static and dynamic reachability analysis support VEX decisions, reduce false positives and create defensible evidence when an actively exploited vulnerability appears.Format: CUP Focus, a self-contained section from the Cybersecurity Under Pressure archive.Related CUP episodes:Cyber Resilience Act: Evidence and the 24-Hour Reporting ClockSBOM and VEX: Turning Vulnerability Data into OT Risk DecisionsSBOM and VEX: Challenging Supplier Vulnerability ClaimsNIST IR 8536: Verifying the Software Supply Chain
  • Industrial Router Security: When SMS Authentication Fails Open | CUP Micro Brief
    Industrial Router Security: When SMS Authentication Fails Open | CUP Micro Brief 27.10.2026 2m
    An industrial router disables SMS password checks after five failed attempts. This CUP Micro Brief examines the availability logic behind the fail-open design and why it becomes dangerous on a cellular attack surface. Related CUP episodes:Weidmüller Router Security: When Segmentation Becomes an Attack PathIndustrial Network Security: Designing for Operational ResilienceLegacy VPNs in OT: Remote Access and the Cost of DisruptionOT Remote Access: Closing the Path When the Work Ends
  • A Trusted Engineering Workstation Can Still Deploy a Malicious Flow
    A Trusted Engineering Workstation Can Still Deploy a Malicious Flow 26.10.2026 36m
    An unauthenticated flow editor can turn an industrial gateway into a code-execution platform. This episode examines the Siemens SIMATIC IoT2050 Advanced case and the operational choices around patching, access restrictions and containment.Siemens advisory SSA-834709 documents CVE-2026-58115 in affected devices running Industrial OS with Node-RED installed before V4.3.4.1. An unauthenticated attacker who can reach the vulnerable HTTP interface may create malicious flows and execute code with maximum privileges. Siemens recommends updating to V4.3.4.1 or later.Editorial clarificationThe factory...
  • Connected Vehicle Security: From Cloud API to In-Vehicle Control | CUP Focus
    Connected Vehicle Security: From Cloud API to In-Vehicle Control | CUP Focus 24.10.2026 3m
    The API gateway may validate a remote command while the internal vehicle network accepts it without equivalent checks. This CUP Focus explains why cloud authorization, telematics and in-vehicle trust must be assessed as one attack path.Format: CUP Focus, a self-contained section from the Cybersecurity Under Pressure archive.Related CUP episodes:Your License Plate Is the Password: What the Kia API Hack RevealedWhen a License Plate Becomes a Password | CUP Micro BriefJeep Hack Lessons: Testing Vehicle Gateway Trust BoundariesAutomotive Extortion: Protecting Cloud, APIs and the Update Chain
  • A Station Identifier Is Not Proof of Station Identity
    A Station Identifier Is Not Proof of Station Identity 23.10.2026 52m
    What happens when an EV charging backend accepts a station identifier without proving which station is actually connecting?This episode examines the Monta OCPP authentication weakness described in CVE-2026-95102 and CISA ICSA-26-274-02. We break down how identifier-based trust can enable station impersonation, why possession of an ID is not authentication, and what operators should enforce at the WebSocket and deployment layers.We also separate demonstrated impact from broader speculation: the issue supports unauthorized station identity claims, but it does not by itself prove widespread explo...

Popular in

The podcast also appears in the podcast charts of these countries.