Contatti
Info
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...
mostra di più
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. The focus is on operational reality, decision making under pressure, and the controls that truly reduce risk in production environments.
mostra meno
Cybersecurity Under Pressure. Real Attacks, Real Lessons
Cybersecurity Under Pressure. Real Attacks, Real Lessons
Antonio GonzalezEpisodi & Post
Episodi
Post
28 SET 2026 · Secure Boot is often represented as a simple security property: enabled or disabled. But a configuration flag does not tell us whether the complete chain used to establish trust at boot actually behaves as intended.
In this episode of Cybersecurity Under Pressure: Real Attacks, Real Lessons, we examine Espressif security advisory AR2026-006, affecting ECDSA-based Secure Boot on specific revisions of the ESP32-H2, ESP32-C5, ESP32-C61, ESP32-P4 and ESP32-S31. The issue sits inside ROM-based ECDSA signature verification, where invalid signatures can under certain conditions be accepted as valid.
The Technical Breakdown looks at what that actually means. The affected verification workflow does not sufficiently validate whether the ECDSA signature components fall within their required range. ESP32-C5 also contains an initialization issue affecting the ECDSA peripheral during the ROM verification process. If an attacker can replace the signed firmware image and manipulate its signature in external flash, the device can accept attacker-controlled firmware during boot.
But the vulnerability does not eliminate the attack preconditions. Exploitation requires a path to modify external flash. That can mean supply-chain access or physical access combined with flash-write capability. Packaging, Secure UART configuration, disabled download paths and Flash Encryption can therefore materially change attack feasibility even though they do not repair the underlying ROM defect.
The Operational Decisions become especially difficult because this is not simply a software patching problem. The affected behaviour exists in immutable ROM on currently affected devices. Product teams therefore need to know the exact SoC and hardware revision deployed, which Secure Boot scheme is configured, how flash is protected, which programming and service interfaces remain available, and which additional security controls surround the boot process. For new production, Espressif recommends RSA-based Secure Boot where supported. Migration of already-deployed devices depends on their existing eFuse configuration and available Secure Boot digest blocks.
Another important distinction is scope. The advisory states that application-layer ECDSA verification is not affected, and the ECDSA verification path used for OTA updates is therefore separate from the vulnerable ROM-based boot verification. That distinction matters because “ECDSA is vulnerable” would be a much broader claim than the evidence supports.
In The Pressure Test, imagine managing a global population of connected devices built across different hardware revisions and configurations. A Secure Boot vulnerability is disclosed, but there is no universal software fix for the affected ROM. Some devices have Flash Encryption and tightly controlled programming interfaces. Others may have different manufacturing or service paths. The decision is no longer simply whether Secure Boot is enabled. It is which deployed configurations actually expose a viable attack chain and what evidence proves that the remaining barriers still hold.
The key lesson is that a security feature is not an assurance argument. Secure Boot depends on the verification implementation, key and eFuse configuration, flash integrity, programming interfaces, hardware revision and the lifecycle processes surrounding the device.
“Secure Boot enabled” is configuration data.
Knowing whether the complete boot chain can still be trusted is security evidence.
Thanks for listening to Cybersecurity Under Pressure. Follow the show for more real attacks, technical breakdowns and practical lessons for cybersecurity leaders.
Explore all episodes and resources:https://cybersecurityunderpressure.com/episodes
27 SET 2026 · A public vehicle identifier became the starting point for a remote attack chain. This CUP Micro Brief connects the Kia API flaw, the disappearance of the traditional vehicle perimeter and the need for blind exploit validation.
Listen to the full episode:https://podcasters.spotify.com/pod/show/toni-gonzalez-burgueo/episodes/Your-License-Plate-Is-the-Password-What-the-Kia-API-Hack-Revealed-e3lumpt
25 SET 2026 · Knowing who your suppliers are is useful. Collecting SBOMs is useful. Neither, by itself, proves where a component came from, what happened to it during its lifecycle or whether the evidence describing it can still be trusted.
In this episode of Cybersecurity Under Pressure: Real Attacks, Real Lessons, we examine NIST IR 8536, Supply Chain Traceability: Manufacturing Meta-Framework, and the problem it is trying to solve: how organizations can build verifiable provenance across increasingly complex, multi-tier supply chains without forcing every participant into the same internal system.
The Technical Breakdown explores the difference between having supply-chain data and having an actual traceability chain. A supplier register, an SBOM, a certificate or a component record may each contain valuable information, but isolated artifacts do not automatically establish provenance. Traceability requires those records to be connected into a temporally ordered history in which products, components, events and transformations can be related to one another and independently verified.
NIST IR 8536 approaches this through interoperable structures, linked traceability events and cryptographically verifiable relationships. The objective is not to create one enormous centralized database containing every supplier’s proprietary information. The framework supports selective disclosure, allowing organizations to provide the evidence necessary to establish provenance and integrity while protecting sensitive manufacturing and commercial data.
The Operational Decisions examine what this means for organizations already collecting SBOMs, supplier declarations, certificates, manufacturing records and cybersecurity evidence. The challenge is no longer simply obtaining more documents. Teams need to determine which artifacts belong to which product configuration, which supplier or sub-tier produced them, when they were valid, what changed afterwards and whether the relationships between those records can still be demonstrated.
In The Pressure Test, a critical component has passed through several suppliers, software and hardware revisions and manufacturing stages before reaching the final product. A security issue appears months later. You have supplier records, SBOMs and individual pieces of assurance evidence, but no reliable way to reconstruct the complete provenance chain. The question becomes whether you can identify the affected population, determine which evidence remains valid and prove which products actually contain the affected component or configuration.
The key lesson is that supply-chain assurance depends on relationships, not inventories. A list tells you who participated. An SBOM tells you what components were declared. Traceability connects those facts to provenance, chronology, configuration and evidence throughout the lifecycle.
Because a folder full of evidence is not yet a trust chain.
The value appears when you can prove how the evidence connects.
Thanks for listening to Cybersecurity Under Pressure. Follow the show for more real attacks, technical breakdowns and practical lessons for cybersecurity leaders.
Explore all episodes and resources:https://cybersecurityunderpressure.com/episodes
23 SET 2026 · A vulnerability with a local attack vector can have serious consequences. But “local” does not automatically mean remote vehicle compromise, and it certainly does not prove that an attacker can reach safety-relevant vehicle functions.
In this episode of Cybersecurity Under Pressure: Real Attacks, Real Lessons, we examine CVE-2026-24083, a memory-corruption vulnerability affecting Qualcomm Snapdragon Auto platforms including QAM8295P, QCA6696 and SA8295P. The vulnerability occurs while processing IOCTL device-driver requests with invalid arguments and carries a CVSS 3.1 score of 7.8, with a local attack vector, low privileges required and no user interaction.
The Technical Breakdown focuses on what “local” actually tells us. It describes where exploitation begins, not how the attacker reached that position. The initial foothold could result from physical access, a compromised application, another vulnerability, a maintenance interface or an already-established execution context. Those paths have very different levels of attack feasibility and should not be collapsed into a single vulnerability score.
The next question is privilege propagation. Successful exploitation of the vulnerable component does not automatically imply control of the vehicle. The relevant engineering question is what authority that component provides and which security boundaries remain between it and vehicle-relevant assets. Can an attacker reach a more privileged service? Escape an application or virtualization boundary? Cross a hypervisor? Reach a gateway? Move toward Ethernet or CAN? Or influence an asset whose compromise could affect vehicle behaviour?
The Operational Decisions translate that reasoning into automotive vulnerability management. Identifying “Snapdragon Auto” in a vehicle is not enough. The vulnerable SoC has to be mapped to the actual BSP or firmware baseline, ECU implementation, vehicle architecture and deployed population. The vulnerability then becomes an input to the ISO/SAE 21434 TARA, where each step in the attack path must be supported by explicit preconditions, controls and evidence.
In The Pressure Test, the security team must decide what to do when a high-severity local vulnerability exists inside a complex vehicle architecture but the complete path to a vehicle-relevant consequence has not been demonstrated. Treating the CVSS score as proof of vehicle compromise exaggerates the evidence. Treating “local” as automatically low risk can underestimate it. The defensible decision depends on the actual attack chain and the containment mechanisms implemented in the deployed system.
The key lesson is that vulnerability management cannot stop at the CVE entry. Automotive cybersecurity has to connect the initial foothold, privilege transition, architectural boundaries and vehicle consequences into one evidence-based attack path.
Because “local” tells us where exploitation starts.
The vehicle architecture determines how far the attacker can go.
Thanks for listening to Cybersecurity Under Pressure. Follow the show for more real attacks, technical breakdowns and practical lessons for cybersecurity leaders.
Explore all episodes and resources:https://cybersecurityunderpressure.com/episodes
21 SET 2026 · An industrial asset may appear as a single box in an inventory, but that does not mean everything inside it follows the same cybersecurity lifecycle.
In this episode of Cybersecurity Under Pressure: Real Attacks, Real Lessons, we examine vulnerabilities affecting the additional GNU/Linux subsystem of the Siemens SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP and use them to challenge one of the most persistent simplifications in OT asset management: the assumption that one physical device represents one software stack, one vulnerability profile and one maintenance lifecycle.
The Technical Breakdown explores what changes when a traditional PLC platform also contains a general-purpose Linux environment. The control functionality and the Linux subsystem may coexist inside the same industrial device, but their security characteristics are very different. Linux brings its own kernel, libraries, packages and vulnerability stream, creating dependencies and remediation requirements that may evolve independently from the automation functions operators normally associate with the PLC.
The Operational Decisions examine why this matters in a real plant. An asset inventory may tell you that a particular S7-1500 is installed, while still failing to identify the version and exposure of the subsystem running inside it. Vulnerability management therefore has to move beyond device-level identification toward component-level understanding. Teams need to know which software environments are present, who owns their maintenance, which updates apply to each layer and whether remediation can be performed without affecting deterministic control, validated configurations or production availability.
In The Pressure Test, you are responsible for securing a factory where PLCs control high-consequence physical processes. A vulnerability disclosure affects the Linux environment inside devices that production teams regard simply as PLCs. Stopping the process is expensive, patching introduces operational uncertainty and leaving the subsystem untouched preserves known exposure. You must determine which lifecycle takes precedence, how to validate the update and what evidence is necessary before returning the system to normal operation.
The key lesson is that modern industrial assets increasingly contain several security domains inside the same physical product. Firmware, operating systems, applications, containers and control logic may each evolve at different speeds and may require different vulnerability monitoring, patching and support strategies. Asset management therefore has to represent not only what the device is, but also what is running inside it and how each component is maintained throughout its life.
Because in modern OT, one asset no longer necessarily means one cybersecurity lifecycle.
Thanks for listening to Cybersecurity Under Pressure. Follow the show for more real attacks, technical breakdowns and practical lessons for cybersecurity leaders.
Explore all episodes and resources:https://cybersecurityunderpressure.com/episodes
18 SET 2026 · Semiconductor development already has formal gates for functionality, timing, power and physical implementation. Security is increasingly becoming another condition that must be demonstrated before a design can be considered ready.
In this episode of Cybersecurity Under Pressure: Real Attacks, Real Lessons, we examine the emerging concept of security sign-off in semiconductor development and what it means for an industry building increasingly complex, heterogeneous and software-dependent hardware. The challenge is no longer simply to add security features to a chip. It is to establish evidence that the architecture, implementation and surrounding system preserve the intended security properties before the design reaches production.
The Technical Breakdown explores why conventional software and IT security checks cannot provide that assurance alone. An application can pass vulnerability scanning, firmware can be tightly controlled and traditional network protections can operate correctly while weaknesses remain inside the hardware architecture itself. Security therefore has to move earlier into specification, RTL, verification and physical implementation, where issues such as unauthorized data paths, information leakage, fault behavior, roots of trust and implementation weaknesses can still be identified before they become expensive silicon.
The Operational Decisions examine what happens when this principle reaches real engineering programmes. Security verification cannot simply become an unlimited additional checklist imposed at the end of development. Teams need explicit security requirements, measurable coverage, clear ownership between architecture, hardware, firmware and system engineering, and acceptance criteria that fit into existing development gates without making delivery impossible.
In The Pressure Test, you are operating in a high-consequence cyber-physical environment built around heavy industrial robotics and complex embedded electronics. A component may satisfy its functional requirements while uncertainty remains about the security assumptions embedded below the software layer. You must decide what evidence is sufficient, whether production can proceed and where the boundary should be drawn between acceptable residual risk and a security issue serious enough to stop deployment.
The key lesson is that semiconductor security cannot remain an informal confidence statement. If security properties matter to the system, they need requirements, verification evidence and an explicit decision point before release. That does not mean one universal test can certify every chip. It means security must become part of the same engineering discipline already used to prove that the rest of the design is ready.
Because a chip should not be considered finished simply because it works. Increasingly, it will also have to demonstrate why it can be trusted.
Thanks for listening to Cybersecurity Under Pressure. Follow the show for more real attacks, technical breakdowns and practical lessons for cybersecurity leaders.
Explore all episodes and resources:https://cybersecurityunderpressure.com/episodes
16 SET 2026 · A hardcoded cryptographic key can look like a relatively simple implementation mistake. In an embedded or industrial system, however, that single decision can undermine an entire security architecture.
In this episode of Cybersecurity Under Pressure: Real Attacks, Real Lessons, we examine CVE-2026-64887 affecting Johnson Controls Airwall and use it to explore a broader problem in embedded cybersecurity: what happens when a secret intended to establish trust is permanently built into the product itself. Airwall versions before 4.1 contain a hardcoded cryptographic key that can enable a cryptanalytic attack, exposing a weakness in a platform designed to provide identity-based, zero-trust protection for connected operational assets.
The Technical Breakdown looks beyond the vulnerability label to examine why hardcoded secrets are fundamentally different from ordinary credentials. A password can be changed and a certificate can be replaced, but a cryptographic key embedded across deployed products may be shared by many installations and deeply coupled to firmware, configuration data or authentication mechanisms. Once that secret is discovered, the problem is no longer confined to a single device. The trust model built around it must be reassessed.
The Operational Decisions explore what remediation really means in an industrial environment. Updating software may remove the vulnerable implementation, but organisations still need to determine where affected versions are deployed, what information may have been exposed, whether the same secret existed across multiple installations and whether systems that previously relied on that key can still be trusted. Asset visibility, supplier coordination, maintenance windows and operational continuity quickly become part of what initially looked like a cryptographic problem.
In The Pressure Test, you are responsible for cybersecurity in a large automotive manufacturing environment where embedded systems support high-speed robotic processes. A hardcoded-key vulnerability is disclosed in technology connected to the operational environment, but production cannot simply stop while every dependency is investigated. You must decide what to isolate, what can continue operating, how to establish the affected population and what evidence is necessary before declaring the environment trustworthy again.
The key lesson is that cryptographic strength means very little if key management is weak. Secure algorithms cannot compensate for secrets that are identical across deployments, impossible to rotate or permanently embedded in software. Effective product and OT cybersecurity therefore requires unique secrets, protected provisioning, controlled key lifecycle management, revocation and rotation mechanisms, and clear evidence that compromise of one device cannot automatically undermine every other deployment.
Because the most sophisticated security architecture can still depend on one very simple question: who else knows the key?
Thanks for listening to Cybersecurity Under Pressure. Follow the show for more real attacks, technical breakdowns and practical lessons for cybersecurity leaders.
Explore all episodes and resources:https://cybersecurityunderpressure.com/episodes
14 SET 2026 · When cybersecurity teams discuss supply-chain risk, the conversation usually starts with software. But some of the most consequential trust decisions are made much deeper in the stack — inside the hardware itself.
In this episode of Cybersecurity Under Pressure: Real Attacks, Real Lessons, we examine the NSA’s latest guidance for Application Specific Integrated Circuits, or ASICs, and what its Level of Assurance 1 framework tells us about securing custom microelectronics throughout design and manufacturing. An organisation may spend years and billions of dollars engineering a critical chip, yet still depend on external design tools, third-party intellectual property, manufacturing facilities and suppliers that sit outside its direct security boundary.
The Technical Breakdown explores why hardware assurance is fundamentally different from conventional vulnerability management. The objective is not simply to find a known flaw after deployment, but to establish evidence-supported confidence that the component has not acquired unexpected characteristics or unintended behaviour somewhere along its lifecycle. That requires looking beyond the finished silicon to the engineering environments, EDA tooling, third-party IP, design data, manufacturing processes and organisations involved in producing it.
The Operational Decisions translate that problem into risk, procurement and governance. Not every component requires the same degree of assurance, and maximum assurance is neither practical nor economically sustainable for every product. The challenge is determining how critical a component is to the system, what the consequence of subversion would be, which parts of the supply chain can actually be trusted and what evidence is sufficient to justify that trust.
In The Pressure Test, the problem becomes immediate: you are responsible for a high-value hardware design destined for a critical system, but fabrication and parts of the engineering chain depend on external organisations. You must decide what information suppliers genuinely need, which controls reduce exposure without making production impossible, and how much residual uncertainty the programme can accept before the chip becomes part of the final system.
The key lesson is that hardware supply-chain security cannot be reduced to choosing a trusted supplier. Assurance must be engineered across the lifecycle and supported by evidence proportional to the consequence of failure or malicious modification. The deeper a component sits inside a critical system, the harder it may be to replace — and the more important it becomes to understand exactly why it deserves to be trusted.
Thanks for listening to Cybersecurity Under Pressure. Follow the show for more real attacks, technical breakdowns and practical lessons for cybersecurity leaders.
Explore all episodes and resources:https://cybersecurityunderpressure.com/episodes
11 SET 2026 · A vehicle can leave the factory with a carefully designed cybersecurity architecture and acquire a new attack surface before the owner even drives it home.
In this episode of Cybersecurity Under Pressure: Real Attacks, Real Lessons, we examine the BLE Theft Auto research into aftermarket Bluetooth Low Energy remote-control and anti-theft systems. Installed by dealerships or vehicle owners, these products can connect smartphone applications to door locks, alarms, lights, immobilizers, ignition systems and other sensitive vehicle functions. Their installation changes the vehicle’s security baseline outside the original development and release process of the manufacturer.
The Technical Breakdown explores how proprietary application-layer protocols, weak pairing mechanisms and inadequate key management can turn a security product into an access path. Vulnerable devices may broadcast identifiers that can be detected locally or located through crowdsourced Bluetooth databases, allowing an attacker to identify and target specific vehicles. Depending on the affected system, unauthorised access may enable doors to be unlocked, alarms to be disabled, engines to be immobilised or remote-control functions to be activated.
The Operational Decisions examine the fragmented responsibility behind the problem. The OEM may not have designed or approved the device, the dealership may have installed it, the aftermarket supplier controls the firmware and application, and the owner may be expected to perform the update. For dealerships and fleet operators, the immediate challenge is determining which vehicles contain the component, whether the firmware has been updated and what compensating controls are possible when removing the device requires invasive work on the vehicle wiring.
In The Pressure Test, you are responsible for product security across a dealership network or vehicle fleet. A serious vulnerability has been disclosed, affected vehicles are already in customer hands and the installed-device inventory is incomplete. You must decide how to identify exposed vehicles, notify customers, verify remediation and manage the residual risk while ownership remains distributed across manufacturers, dealers, suppliers and drivers.
The key lesson is that automotive cybersecurity cannot stop at factory release. The vehicle security baseline must account for dealer-installed equipment, aftermarket modifications, software updates, resale and decommissioning. Effective lifecycle governance requires configuration visibility, explicit supplier responsibilities, secure update mechanisms and evidence that every component connected to sensitive vehicle functions remains authorised and supportable.
Because a secure vehicle can become vulnerable when someone adds a component that was never part of its original cybersecurity architecture.
Thanks for listening to Cybersecurity Under Pressure. Follow the show for more real attacks, technical breakdowns and practical lessons for cybersecurity leaders.
Explore all episodes and resources:https://cybersecurityunderpressure.com/episodes
9 SET 2026 · An industrial security router is supposed to protect the factory floor. But when that router is vulnerable, the security boundary itself can become the attacker’s path into production.
In this episode of Cybersecurity Under Pressure: Real Attacks, Real Lessons, we examine vulnerabilities affecting Weidmüller industrial security routers and the wider operational problem they expose. These devices may provide firewalling, network segmentation, VPN connectivity and remote access between industrial machines, production cells and external support environments. That defensive role also gives them a privileged position within the architecture.
The Technical Breakdown explores what happens when vulnerabilities affect the device responsible for enforcing trust between networks. A compromised router may expose its configuration, interfere with communications or provide a pivot point toward systems that were assumed to be protected behind it. The risk is therefore larger than the individual vulnerability: placing extensive trust in one security appliance also creates a concentration of operational risk.
In The Pressure Test, you are responsible for a large, high-speed factory floor built around industrial robotics. The routers protecting the production networks are vulnerable, but taking them offline could interrupt operations, remote maintenance and critical communications. You must decide whether to patch, isolate, replace or continue operating under compensating controls while production, safety and recovery requirements leave little room for error.
The Operational Decisions examine the practical constraints behind that choice, including incomplete asset inventories, restricted maintenance windows, legacy dependencies, supplier access and the challenge of proving that segmentation still works after the device enforcing it can no longer be fully trusted.
The key lesson is that a security control must also be managed as a potentially vulnerable operational asset. Industrial resilience requires verified firmware baselines, restricted management access, independent monitoring, tested recovery procedures and an architecture that does not place unlimited trust in a single protective device.
Because when the security boundary becomes the attack path, everything behind it must be reassessed.
Thanks for listening to Cybersecurity Under Pressure. Follow the show for more real attacks, technical breakdowns and practical lessons for cybersecurity leaders.
Explore all episodes and resources:https://cybersecurityunderpressure.com/episodes
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...
mostra di più
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. The focus is on operational reality, decision making under pressure, and the controls that truly reduce risk in production environments.
mostra meno
Informazioni
| Autore | Antonio Gonzalez |
| Organizzazione | Antonio Gonzalez |
| Categorie | Tecnologia |
| Sito | www.spreaker.com |
| - |
Copyright 2026 - Spreaker Inc. an iHeartMedia Company
