Protecting Hospital and Healthcare Internet Applications
See details of electronic records such as bandwidth and speed
Quick response times on electronic medical records is crucial. Latencies when accessing a patient's electronic medical records can quickly reduce productivity for medical and nursing staff. Any delays with accessing electronic records will quickly increase the time it takes to see multiple patients.
In this example we can see that the eRecords app has large delays (round trip times or RTT). Anything higher than 200ms slows down medical and nursing staff response times.
Reduce delays on electronic medical records with Quality of Service (QoS)
By implementing NetScope's Quality of Service (QoS) algorithms on electronic medical records you can reduce the response times (delays or RTT) to a minimum. It is not limited to electronic medical records of course, any application can be protected in this way. You can read more about QoS here.
Notice the delays are greatly reduced, highest noted delay is 100ms down from 500ms above.
Monitoring users and groups using electronic medical records
Through NetScope's Active Directory support, users and groups can be monitored and controlled directly over the Internet & WAN. What does this mean? You can see which Microsoft Domains are accessing electronic medical records (or any application or website). You can also drill-down on any Microsoft Domain and see individual users and their usage information.
Click on any segment to drill down and see group users
This chart shows what displays when we drill down on a particular Windows Domain. Here we are seeing all the users in the Urology group. Each user is show with their percentage usage as a total of the group. With NetScope you can further drill down and see what applications and websites each user is currently using over the Internet. This includes their specific usage statistics on electronic medical records.
Block unauthorized applications and websites
Some applications can be difficult to detect and block with traditional firewalls that use IP and port based rules. NetScope, however, can detect application and websites using deep packet inspection (as well as IP and port based rules).
Some applications such as TOR (used for the Dark Web) that hide behind SSL or HTTPS (used for secure web browsing) won't be reliably detected by firewalls that use IP and port based rules. Deep packet inspection on the other hand can detect the TOR application as it initiates it's startup sequence. In this way NetScope can detect the Dark Web.
Further more, some of the larger social media and video streaming sites can't be blocked purely by domain based rules. This is because the large distributed nature of these websites mean that the content is often delivered via content delivery networks that don't contain domain information (reverse DNS) that can be easily linked to the originating site. Again, this is where deep packet inspection comes in. Deep packet inspection looks into the IP traffic and detects which website the traffic is for.
What is this pie chart showing?
This application activity chart shows all application bandwidth activity for the selected time period. In this example we have set up an alert to fire if NetScope detects Dark Web traffic, which we can see 'pulled out' in the chart.
Use NetScope to alert on or block unwanted traffic
Once you have detected the unwanted application or website type you can use NetScope to block the traffic. It is also reasonable to allow unwanted application or website types but use the alerts to notify the network administrators of their use. That way the users can be contacted and notified that this practice is not acceptable.