Difference between revisions of "Template:Network Architecture"

From IVS Wiki
Jump to: navigation, search
 
Line 1: Line 1:
 
{{Section | title = <h1>Network Architecture</h1> | content =
 
{{Section | title = <h1>Network Architecture</h1> | content =
 
 
Below is a diagram of a sensitive network environment, where in-transit encryption is a requirement.  This type of network architecture is typical of environments that are using the system to capture / observe actual patient interactions within clinical training environments.
 
Below is a diagram of a sensitive network environment, where in-transit encryption is a requirement.  This type of network architecture is typical of environments that are using the system to capture / observe actual patient interactions within clinical training environments.
  
 
+
{{img - resize| file = Network_testing_img.webp}}
{{img - no_click | file = specific-8.jpg}}
 
  
  
{{Aside | content = For SSL, we will need the customer to set up a DNS name for the server <em>(example ivs-valt.mysite.edu)</em>.  We will also need a wildcard or generated signed certificate that is compatible with nginx and can be applied by an IVS engineer. LetsEncrypt may also be utilized.}}
+
{{Aside - Helpful | content = Want to see more information about our [[Network Requirements]]?}}
 
}}
 
}}

Latest revision as of 15:38, 23 January 2026

Network Architecture

Below is a diagram of a sensitive network environment, where in-transit encryption is a requirement. This type of network architecture is typical of environments that are using the system to capture / observe actual patient interactions within clinical training environments.

Network testing img.webp


🕮
Want to see more information about our Network Requirements?