Template:Network Architecture: Difference between revisions

From IVS Wiki
Jump to navigation Jump to search
← Older editNewer edit →
No edit summary
No edit summary
Line 1: Line 1:
{{Section | title = <h1>Network Architecture</h1> | content =
{{Section | title = <h1>Network Architecture</h1> | content =
<div class="floating_card">The network architecture for a VALT solution can look different for many of our customers.</div>
Below is a typical standard suggested network architecture diagram.  We see this architecture often used in Law Enforcement & Simulation, as well as other environments, where security is important and segmenting access to only the necessary ports / devices is desired but in transit encryption is not a requirement.
{{img - no_click | file = specific-6.jpg}}
<hr>
If LDAP is being used, the server will also need access to the authentication server(s) as shown below.  For LDAP integration using our software, we will also need a bind account and password with read-only access to LDAP.
{{img - no_click | file = specific-7.jpg}}
<hr>


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.


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.


{{img - no_click | file = specific-8.jpg}}
{{img - no_click | file = specific-8.jpg}}


<hr>
If LDAP is being used, the server will also need access to the authentication server(s) as shown below.  For LDAP integration within our software, we will also need a bind account and password with read-only access to LDAP.


{{img - no_click | file = specific-9.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.}}
}}
}}

Revision as of 20:57, 21 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.



✎
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.
Retrieved from "https://ivs.help/wiki/index.php?title=Template:Network_Architecture&oldid=16758"