Can Healthcare Device Security Improve Without Starting at the Network Traffic Layer?


In today's world of healthcare, thousands of connected devices rely on one another, such as infusion pumps, imaging equipment, badge readers, controllers of H/VAC, clinical stations and tele-health endpoints. A majority of these types of devices do not support security agents, can't be patched and were not designed with cybersecurity in mind; they were simply designed to provide safe reliable clinical care. 

Here are some real-world observations related to the above statement:

• There are substantial amounts of valuable traffic signals that are generated on connected medial and facility devices

• Many of the devices cannot be secured by the use of traditional endpoint controls

• Packet-level visibility can provide insight into device behaviour patterns, communications, and risk

• Optimized delivery of traffic helps improve the accuracy of asset discovery and monitoring tools

• Network evidence can support security compliance and incident investigation processes

There is a common myth with regard to connected device security - that it is a matter of just having an accurate asset inventory. This is not entirely correct; the asset inventory is only one aspect of the overall program. The healthcare team must also determine how the devices communicate, if the device is utilizing encryption properly, which external services the device is communicating with, and whether or not lateral communications are taking place on the network. 

The bottom line is that connected medical device security will be improved as the foundation for packet-level visibility. By capturing, enriching and intelligently delivering network traffic, a security team will have enhanced visibility of all medical devices (or assets) as well as other healthcare assets that operate on the healthcare network as well as cloud-based services.

Sharing the full breakdown below for anyone who wants to explore how packet-level visibility supports connected device security in healthcare: https://aviznetworks.com/guide/cisco-guide-to-hippa-compliance-in-healthcare/download

Comments

Post a Comment

Popular posts from this blog

Evolving Packet Brokering for Modern Network Observability

Image
  I recently reviewed a technical overview describing how packet brokering platforms are evolving to support large-scale observability in modern data centers and service provider networks. The discussion focused on scalability, automated deployment, and operational efficiency. Some practical observations: • Network visibility platforms are expanding support for 400G switching hardware used in modern data center fabrics • GRE encapsulation enables mirrored traffic to move across Layer-3 networks while preserving packet metadata • Zero-Touch Provisioning simplifies onboarding for new or factory-reset switches • Packet brokers aggregate traffic from TAPs and SPAN ports and apply filtering and distribution policies • CLI improvements help operators manage large monitoring environments more efficiently One notable element was how GRE tunneling extends observability beyond Layer-2 boundaries. By encapsulating mirrored traffic into GRE tunnels, monitoring systems can receive full packet c...
Read more

Scaling Deep Network Observability for 5G: Reflections from a Real Deployment

Image
  I recently went through a detailed implementation showing how deep network observability enhances 5G mobile user experience while reducing operational complexity. What stood out was how grounded the deployment was in real traffic and production-scale constraints. Some practical observations: • Fragmented systems increase cost and operational overhead • Frequent infrastructure upgrades create instability and repair expenses • Optimised filtering significantly reduces DPI hardware requirements • Real-time KPI computation improves SLA monitoring and service assurance • Standardised data export through streaming pipelines simplifies integration One misconception addressed during the walkthrough was that deeper observability automatically means more hardware. In reality, efficient filtering and intelligent packet processing reduce hardware footprint while improving performance. My biggest takeaway is that scalable observability in 5G environments requires architectural efficiency,...
Read more

How Network Copilot Uses Agentic AI to Correlate FortiGate and Splunk

Image
I recently went through a detailed implementation explaining how Network Copilot correlates FortiGate firewall telemetry with operational data indexed in Splunk . What stood out was how grounded the discussion was in real operational workflows rather than theoretical AI claims. Some practical observations: • Network and security logs are typically distributed across multiple platforms • Troubleshooting often requires manually correlating events between systems • Network Copilot ingests metrics, events, logs, and traces from firewall environments • Operators can interact with the system using natural language questions • Explainable root cause analysis improves operational confidence One misconception addressed during the walkthrough was that AI in operations means replacing engineers. In reality, the system augments teams by surfacing insights faster and correlating information across environments. Another interesting point was how the platform learns from real firewall deployments...
Read more