Cybersecurity requirements should be established immediately after the prototype/MVP concept is proven
starting directly in the product design phase.
Treating cybersecurity as a point-in-time penetration test 60 days before regulatory submission...
Treating cybersecurity as a point-in-time penetration test 60 days before regulatory submission delays market entry 90% of the time and can trigger massive rework.
Medical device manufacturers must design for hostile hospital network environments rather than...
Medical device manufacturers must design for hostile hospital network environments rather than assuming healthcare delivery organizations will provide perimeter security.
Hardware selections like microcontrollers must be vetted early to ensure support for critical...
Hardware selections like microcontrollers must be vetted early to ensure support for critical controls like Secure Boot and code integrity.
The FDA expects continuous security across the Total Product Life Cycle (TPLC) under a Secure...
The FDA expects continuous security across the Total Product Life Cycle (TPLC) under a Secure Product Development Framework (SPDF), spanning development, patching, and end-of-life decommissioning.
Proactive threat surface reduction—such as disabling unused wireless interfaces and validating...
Proactive threat surface reduction—such as disabling unused wireless interfaces and validating them via negative testing—substantially lowers device risk and compliance burden.
Episode Summary
In this episode of the Med Device Cyber Podcast, host Christian Espinosa addresses the critical question medical device manufacturers and MedTech innovators face: when should cybersecurity actually begin? Drawing from experience across hundreds of regulatory submissions, Christian debunks the pervasive misconception that cybersecurity is merely a late-stage, point-in-time penetration test conducted 60 days prior to an FDA 510(k) or EU MDR submission.
Instead, Espinosa outlines how waiting until the eleventh hour routinely results in costly redesigns, stripped device features, multi-month submission delays, or total project abandonment. While early prototyping and proof-of-concept stages do not require security overhead, cybersecurity requirements must be established the moment commercial product development begins.
The episode details the FDA's expectations surrounding the Secure Product Development Framework (SPDF) and Total Product Life Cycle (TPLC). Listeners will learn how to architect hardware and software requirements—such as Secure Boot and full disk encryption—reduce attack surfaces, implement secure CI/CD pipelines with SAST and SBOM management, and plan for postmarket vulnerability tracking and secure patch distribution. Christian explains why spending modestly on upfront security design saves manufacturers hundreds of thousands of dollars in downstream rework.
Frequently Asked Questions
Quick answers drawn from this episode.
In this episode of the Med Device Cyber Podcast, host Christian Espinosa addresses the critical question medical device manufacturers and MedTech innovators face: when should cybersecurity actually begin?
Cybersecurity requirements should be established immediately after the prototype/MVP concept is proven, starting directly in the product design phase. Treating cybersecurity as a point-in-time penetration test 60 days before regulatory submission delays market entry 90% of the time and can trigger massive rework. Medical device manufacturers must design...
This episode covers FDA Premarket Cybersecurity, Penetration Testing, Threat Modeling, and SBOM Management. It's part of The Med Device Cyber Podcast, hosted by Blue Goat Cyber, focused on practical medical device cybersecurity guidance for MedTech teams.
Instead, Espinosa outlines how waiting until the eleventh hour routinely results in costly redesigns, stripped device features, multi-month submission delays, or total project abandonment. It's most useful for medical device manufacturers, cybersecurity engineers, regulatory affairs professionals, and MedTech founders preparing for FDA...
Cybersecurity requirements should be established immediately after the prototype/MVP concept is proven, starting directly in the product design phase.
Listeners also asked
Quick answers pulled from related episodes.
What does Episode 26 cover about "How to Measure Exploitability in Medical Device Cybersecurity"?
How do you calculate cybersecurity risk when the thing you are measuring has an attacker making decisions on the other side? Probability works when there is historical data to lean on. Elevator cables wear out. Steel fatigues. Tornadoes follow patterns. A motivated attacker...
What does Episode 25 cover about "How to Make Your MedTech Startup Investable with Gavin Leonard"?
What actually makes a MedTech startup investable? Is it the technology, the clinical need, the founder, the pitch, or whether the company has simply done enough homework before walking into the room? Christian Espinosa speaks with Gavin Leonard of MedTech Syndicates about what...
What does Episode 24 cover about "Why Medical Device Penetration Testing Is Different"?
What makes medical device penetration testing different from a traditional cybersecurity penetration test? In this solo episode, Christian Espinosa explains why medical device penetration testing has to be approached through the lens of patient safety rather than simply data...
Pre-fills with: "Cybersecurity requirements should be established immediately after the prototype/MVP concept is proven, starting directly in the product design phase."
When is the right time to start cybersecurity for a medical device? For many manufacturers, the answer still seems to be somewhere close to submission. In this solo episode, Christian Espinosa explains why that approach can create major delays, expensive redesigns and even force companies to abandon products they have spent years developing. Christian breaks down where cybersecurity should enter the product lifecycle, why requirements and hardware decisions matter, and how frameworks like the SPDF and Total Product Lifecycle change the way manufacturers should think about security. He also covers penetration testing, secure updates, decommissioning, attack surface reduction and post-market monitoring, showing why cybersecurity has to extend from design through disposal. In This Episode: * 00:07 Why manufacturers say they’re “not ready” for cybersecurity * 02:08 When cybersecurity should actually begin * 04:19 How early design decisions create security problems * 06:28 Cybersecurity from cradle to grave * 10:32 Why hospital networks should be treated as hostile * 12:41 Secure updates and device decommissioning * 15:54 Building cybersecurity into development * 17:07 Post-market monitoring and why waiting costs more The Med Device Cyber Podcast is brought to you by Blue Goat Cyber, cybersecurity experts providing essential security solutions for the medical device industry. Learn more about Blue Goat Cyber: https://bluegoatcyber.com Schedule a Discovery Session: https://go.bluegoatcyber.com/meetings/blue-goat-cyber/discovery-session Christian Espinosa on LinkedIn: https://www.linkedin.com/in/christianespinosa/ Blue Goat Cyber on LinkedIn: https://www.linkedin.com/company/blue-goat-cyber/ Blue Goat Cyber on Instagram: https://www.instagram.com/bluegoatcyber/ Blue Goat Cyber on Facebook: https://www.facebook.com/bluegoatcyber/ Blue Goat Cyber on YouTube: https://www.youtube.com/@BlueGoatCyber/?sub_confirmation=1 Download MP3 — full interview
Hello and welcome back to the Med Device Cyber Podcast. Today we're going to be talking about an important topic: timing. When is the right time to consider cybersecurity for your medical device? And when is the wrong time? Most people get this wrong. So the whole idea is does it really matter when we consider cybersecurity? And this is something that I am trying to raise the awareness on and BlueGoat Cyber is trying to raise the awareness on. Pretty much at every event, I talk to medical device manufacturers. I talk to medtech innovators. Some of them developed a product several years ago. Some of them, it's their first product. When I talk to them about cybersecurity, it's very interesting. Most of them will say, "We're not ready for cybersecurity yet." And I find that a very interesting point of view because naturally I think, "Well, when are you going to be ready for cybersecurity?" And it's something like, when people say that, it's kind of hard to counter the argument. I've tried a few times, but often this idea that cybersecurity is some sort of point-in-time study that comes later on, is ingrained in the person that I'm trying to have the conversation with. So it's almost a losing battle. And I keep thinking, do I need to raise the awareness? Am I not communicating clearly? Is there still a fundamental misunderstanding of how cybersecurity works? I try to identify the root cause because I would say out of 10 medical device of the 100 innovators that I talked to, probably 5 of them, 50%, will say they're not ready for cybersecurity yet. And I know, and they know, their device has software and a way to connect to it. So it falls under the definition of a cyber device, which means it needs cybersecurity. So the right answer of when you need cybersecurity is now, if not yesterday. Cybersecurity needs to be designed into the product. If it's designed into the product, the cybersecurity controls can be developed into the product. If it's not part of the requirements or the design, it's not going to be developed into the product, which means we'll have to bolt it on later, which is very costly causes some features to be removed and causes a lot of rework. So we need to do it early on. And I don't think people are intentionally being careless with this. I think they just weren't asking the right questions, like when should we consider cybersecurity? And in some medical device manufacturers' defense, they've been developing this product for maybe 4 or 5 years before the FDA and other regulatory authorities really started cracking down on cybersecurity. So now they're, they're pretty far along and they have to consider cybersecurity. And it wasn't a thing maybe 5 years ago. To me, it's always been a thing because I've been involved with cybersecurity, but it, each industry takes a while to mature from a cybersecurity point of view. So by the end of this episode, you should understand some of the activities that are required for cybersecurity and where they should be considered in the product lifecycle. Unfortunately, a lot of teams will say, we're going to do cybersecurity before we submit to EU MDR. That's when we'll consider cybersecurity. It's treated like a point-in-time exercise, like a test. We'll do the penetration test 60 days before our submission. That's the wrong time to do it. That may feel logical because you want to test something before you submit it, but the problem is if you've never done penetration testing as part of your development, if you've never considered cybersecurity before, The penetration test is going to find many, many things wrong that have to be fixed before your submission will get cleared or approved by the FDA. Any risk that can affect a patient, that can cause harm to the patient, needs to be fixed. So if you've chosen things early on, made, made design decisions about a specific piece of hardware, that doesn't support cybersecurity requirements. The test will validate that, and now you may have to remove features from your device. We've had clients that have made design decisions without having the cybersecurity requirements. They chose microcontrollers that did not support the proper cybersecurity requirements, such as Secure Boot. Secure Boot provides code integrity, which means when the firmware boots up, we know it hasn't been tampered with. One of our clients that came to us before submission made that decision before they talked to us, and they had to remove features from their device to make sure the risk was acceptable to a patient. Again, cybersecurity should be considered in the requirements stage and the design phase so it can be developed into the product. This, this includes like requirements for hardware. A lot of people neglect the hardware part of it. Hardware affects cybersecurity as well as software. Another question we get quite often is, do I need to consider cybersecurity when I'm still developing my prototype? My answer is no. If you haven't figured out what you're going to develop because you're still testing it with a prototype, with your minimum viable product, You're proving market fit. That is not the right time for cybersecurity. You're going to waste time on cybersecurity. You're still trying to figure out what your concept is going to look like and how people are going to use it. But once you've figured that out and are starting to develop the actual product, that's when you should start considering the cybersecurity. In the requirements phase, not just the development phase. The requirements feed the design. Which feed the development. A couple of things the FDA wants to see. They want to see this thing called the SPDF, the Secure Product Development Framework. The whole idea is we have a process in place to develop secure software and secure products. So this means we have a lifecycle that where we look at the requirements, the design, the development, the release, the support, so how we deploy a patch, and the decommission, we have to have methods that are secure from cradle to grave, or design to disposal of our product. That's the requirement. It's not 60 days before submission, it's from cradle to grave. And what happens is when people wait to the 60 days before the submission, 90% of the time, from our experience of doing 260 or 270 submissions, it delays the submission. If you haven't considered cybersecurity and you're 60 days before the submission and your regulatory affairs person says, "Hey, we need to do cybersecurity. We need to get a penetration test done," and you've never done anything about cybersecurity, as I mentioned, the penetration test is going to find things wrong The longest part of that process is how long it takes you to fix what was identified. We've had clients that have been able to fix things very quickly and still submit within the 60 days. We've had clients that took 8 months to fix what we identified. So imagine you've told everybody you're going to submit in 60 days and you've budgeted appropriately, but now it's going to take you 8 more months to fix everything. Now you have to keep staff on your your team. You have to keep the software development team that maybe you outsource to employed for longer. You may have to go back to your investors and ask for more money because you didn't anticipate this. You may have to remove some features because there's no easy way to fix it. And you may have to tell your shareholders, if you're a publicly traded company, that you're not going to meet the deadline. And this frustrates everybody. And we, we would like to see this prevented, which is You know why we're doing things like this podcast, why we do a lot of advocacy about raising the awareness, because it can become very costly. We've had other clients that came to us 60 days before submission. Some of them come 45, some of them 30. I'm just using 60 days as an average. And we identified so many things wrong, they simply decided to abandon their product because they exhausted all the resources, they were tired from developing it already, and they thought, this is too costly to fix, we're just gonna like let the product go. Imagine that, that is a very frustrating scenario. I can't imagine being in their shoes, spending 4 to 5 years developing something, forgetting about cybersecurity, and then I look at what needs to be done, and it's such a massive cost and burden and level of effort that I simply decide I'm not going to do it. That my 4 to 5 years of effort culminated in me making a decision to not move forward because I forgot about cybersecurity or nobody told me I needed to do cybersecurity early on. So I mentioned the Secure Product Development Framework. Another term the FDA likes to throw around is the TPLC. Another acronym, we always have to have lots of acronyms, the SPDF, Secure Product Development Framework. So I have a framework to securely develop my product. This is similar to the Secure Software Development Lifecycle, or the SSDLC. The total product lifecycle means I need to have cybersecurity in my product from cradle to grave, from design to decommissioning, the entire way. And this has to be thought out ahead of time. This means what are the cybersecurity requirements because my device is going into a hostile environment. A lot of our clients make the assumption that their product is going to go into a secure environment and that they can inherit cybersecurity from the hospital. That is super far from the truth. As you may have noticed, if you pay attention to the news, pretty much every day a major healthcare conglomerate is compromised, often with ransomware, which means these healthcare delivery organizations or these hospitals are not secure. So your device is going into a hostile environment and it needs to be designed for that environment. It needs to survive under constant attack, which is why penetration testing is extremely important because the penetration testing uses the same tactics as the enemy, the same tactics, techniques, and procedures. So cybersecurity needs to be designed into the product and it needs to be tested. As well. This is where the whole traceability comes into play. We have our design, our cybersecurity requirements, our control. We have to validate that with software validation and verification, and then we have to also test it with a penetration test, typically a third party. So the Secure Product Development Framework, cradle to grave, total product lifecycle. And I talked about the design a little bit. The development, but also we have to think about, there's going to be some point in time where I'm going to have to deploy an update or security patch to my medical device. So how do I do that? And how do I do that securely? And how do I develop that patch securely? These are all questions that need to be asked because we've had attacks before, like SolarWinds, where the update infrastructure was compromised and somebody, or the attacker, deploy malicious software over the update patch mechanism for SolarWinds. So because of these things, we have to look at how can I prove I can develop a patch securely, and how can I prove I can deploy it securely? And if somebody tampers with it on the way, does my medical device have a means to make sure that patch is legitimate. So am I doing digital signatures and all the other things required? And then that's part of the support for the total product lifecycle, but the decommissioning is the next part. And we have to assume hospitals or healthcare delivery organizations are not going to follow our decommissioning instructions. We've had clients where the hospitals have just basically sold their used medical devices and put them on eBay for sale. People have bought the devices off of eBay, taken the hard drives off. The hard drives were not encrypted and were able to extract patient data and specific proprietary information about the algorithms that, that manufacturer had used. So we have to think about the decommissioning as well and make the assumption, as I mentioned, that the client is not going to follow your instructions. So what's the worst case scenario like the one I just gave, the hospital just puts them up for sale, gives them away, throws them in the trash, somebody else tries to sell them, somebody takes a hard drive out, um, somebody tries to repurpose it and resell it, you know, how am I making sure this is not a risk with my device? And what are my controls around that? In the case I just gave you, full disk encryption would have prevented someone from extracting the data off of that. Hard drive. A few things to look at. We talked about design to disposal. So when we look at the concept, I talked about after you've proven your prototype, now you should consider cybersecurity. We have to look at the hazard analysis— what can go wrong to a patient if the integrity and availability are compromised? And what design controls do we put in place for that? And how do we validate those design controls? If we don't need specific communication mechanisms on our device, let's take them off. Those are entry points. Those are entry points that may serve a purpose, but also are another way an attacker could get into your device. So if you don't need Wi-Fi, disable it. If you don't need NFC, disable that and validate it's disabled because we're, we're shrinking the attack surface. The more ways we have enabled, or the more connectivity mechanisms, the larger the attack surface, the more threats on our threat model, and the more cybersecurity controls we have to put in place. Sometimes the easiest control is just to turn something off and validate it's turned off. We have to also do negative testing from a cybersecurity point of view to make sure when someone says Wi-Fi is turned off, we have to validate it's turned off. A lot of our clients have said, Oh yeah, Bluetooth is turned off on our device. We look at Bluetooth, it's actually on. So when you turn it off, make sure you remove the drivers, you remove the chip if possible, and it's actually turned off, and that's validated. When you're developing the product, you can do things such as a secure software development lifecycle. You can have gates in there. This is often called a secure CI/CD, continuous integration, continuous development or deployment. Mechanism where you periodically, once something is developed, you run it through static application security testing. You look at the software bill of materials, but you do this as part of your development process so you can identify bugs and vulnerabilities as you're doing the development, not later on when you have a penetration test performed. This should be part of your development. And once your device is deployed, there's something called post-market management. We focused a lot on pre-market submissions. Pre-market simply means the product is not on the market yet. It's not up for sale. This is typically what most people focus on, getting through the FDA, getting FDA clearance or FDA approval. But once your device is on the market and you're able to sell it and healthcare delivery organizations purchase it, The things I talked about earlier with patch management and rolling out patches, there has to be a mechanism to do that. So you have to know where all your devices are. You may have to send a field technician to update them via USB drive, or you can do it remotely. But you also have to have a mechanism to monitor for new threats that evolve. An existing vulnerability, its exploitability may change because when you sold the product, a vulnerability in your SBOM, as an example, in one of the third-party components, may not be that big a deal. But 5 days later, after you've sold this device, some 12-year-old could come up with an exploit and publish it on the internet where anybody can download it, and they just have to put it on their computer and press a button and put your device to the target, and then they fully compromise your device. Before, that was a vulnerability where there was no way to exploit it. It was super difficult. But that can change overnight, which is why it's important to monitor, and it's required to monitor your software bill of materials. So cybersecurity, as I mentioned, is from cradle to grave, or design to decommission. Pre-market is part of it, but post-market is important as well. So how do we deploy a patch? How do we monitor for new vulnerabilities? How do we monitor for vulnerabilities that may have become more exploitable today than they were yesterday? And then how do we allow people to report something they discover with our device to us? And what do we do about it? There has to be entire infrastructure that supports this. So the right time to do cybersecurity is at your requirements phase after you've proven your concept. With an MVP or prototype. If you haven't done it, then the second best time to do it is now. Don't be like a lot of the people I talk to and say, we're not ready for cybersecurity yet. That's setting yourself up for frustration and failure, a lot of cost, a lot of rework. You may lose investors. You're going to delay your time to market, uh, which means you're going to delay your revenue. A competitor may get to market ahead of you. And I'm not saying things to scare you. These are, these are things that actually happen daily in our life. At Blue Coat Cyber, we see our clients unfortunately do nothing about cybersecurity until about 60 days before the submission. And the reality is, if you talk to us early on with design consulting, and we can help you with requirements, most of the time that costs less than $5,000. So it's not a lot of money, especially in comparison with what the cost is if you wait to the end. That 60 days before submission, that typically costs about $500,000 in rework and keeping the staff on and removing the features. It is very expensive. So it's much better to think about this sooner than later and spend $5,000 now and avoid the $500,000 bill later and a lot of frustration. I hope you found value in this episode. The moral of the story is to be proactive, consider cybersecurity early on. And I think the tide is shifting a little bit here. And I'm hoping like the next events I go to this year, that number of 50% of the people that say they're not ready for cybersecurity will shift. Hopefully it'll be down to 40%, uh, and we'll continue to raise the awareness. Uh, I know we sell cybersecurity services at Blue Goat Cyber, but I'm also an entrepreneur and I want to help entrepreneurs avoid the landmines in the minefield. Cybersecurity is one of the biggest ones today. It is one of the main reasons a lot of submissions are getting rejected. It is a major concern today because there are nation-state actors that are attacking some of our strategic companies out there. They're constantly attacking our healthcare infrastructure. So the bar has been upped quite a bit, and I want to help the entrepreneurs bring these products to market and get them to market because these are products that help humanity. I mean, some of the products we work with can help blind people see, can help reduce seizures in someone with epilepsy, can help Children Walk with multiple sclerosis. I mean, these are great products and it's very frustrating for me to see them delayed to market because of cybersecurity. So best of luck to you. Do cybersecurity early on. Contact us at Blue Goat Cyber if you have any questions. We're happy to just jump on a call and answer those questions. 'Cause as I mentioned, you know, part of my mission is to help entrepreneurs in this space succeed. Thanks, and I hope to see you on the next episode.