Template:Network Architecture - Revision history

IVSWikiBlue at 21:38, 23 January 2026

2026-01-23T21:38:10Z

IVSWikiBlue at 20:57, 21 January 2026

2026-01-21T20:57:46Z

IVSWikiBlue at 22:45, 29 April 2025

2025-04-29T22:45:19Z

IVSWikiBlue at 22:04, 29 April 2025

2025-04-29T22:04:59Z

IVSWikiBlue: Created page with "{{Section | title =

Network Architecture

| content =

The network architecture for a VALT solution can look different for many of our custo..."

2023-05-10T20:54:56Z

Created page with "{{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 custo..."

New page

{{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.

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 apache and can be applied by an IVS engineer.

{{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}}
}}

@@ Line 1: / Line 1: @@
 {{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.
+{{img - resize| file = Network_testing_img.webp}}
-{{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]]?}}
 }}

@@ Line 17: / Line 17: @@
 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 apache and can be applied by an IVS engineer. LetsEncrypt may also be utilized.
+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}}