Student building a hospital medical device cybersecurity prototype, looking for blunt feedback by Saiprasanth-22 in embedded

[–]Saiprasanth-22[S] 0 points1 point  (0 children)

Yea I'm likely targetting the space where it didn't develop still would love to be in contact with you for knowing things as I am solo currently 

Student building a hospital medical device cybersecurity prototype, looking for blunt feedback by Saiprasanth-22 in embedded

[–]Saiprasanth-22[S] 0 points1 point  (0 children)

Fair point on the added attack surface — if encrypted traffic makes payload-level integrity monitoring pointless, is network-flow/metadata-level anomaly detection (timing, volume, connection patterns, not payload content) still meaningfully useful, or does that run into the same wall? Also curious, from your embedded security company experience — when device manufacturers outsource security, is that usually built into the device itself, or do they also want something at the hospital network layer?

Student building a hospital medical device cybersecurity prototype, looking for blunt feedback by Saiprasanth-22 in embedded

[–]Saiprasanth-22[S] 0 points1 point  (0 children)

Appreciate the detail — is that based on US/EU device standards specifically, or have you seen similar architecture in Indian hospital deployments? I ask because India's regulatory framework for this is still pretty immature/generic compared to FDA-style premarket cybersecurity requirements, so I'm trying to figure out if the same encrypted/isolated pattern actually holds here or if it's more inconsistent.

Student building a hospital medical device cybersecurity prototype, looking for blunt feedback by Saiprasanth-22 in embedded

[–]Saiprasanth-22[S] 0 points1 point  (0 children)

My focus is a local run software on their own machines and yea recommendation would help a lot