Difference between revisions of "Template talk:Network Architecture"

From IVS Wiki
Jump to: navigation, search
(Created page with "{{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...")
 
Line 1: Line 1:
{{Section | title = <h1>Network Architecture</h1> | content =
+
{{Article - Manual | title = Network Architecture| 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.

Revision as of 08:23, 22 January 2026

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


For SSL, we will need the customer to set up a DNS name for the server (example ivs-valt.mysite.edu). 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.