Video Collection: Configure DIVE To Add Access Policy Based On Device Identity
This video collection introduces DIVE and how it strengthens ZTNA. Starting with an introduction video, the other two videos demonstrate the two modes of DIVE.
This video collection introduces DIVE and how it strengthens ZTNA. Starting with an introduction video, the other two videos demonstrate the two modes of DIVE.
Introduction
This video introduces DIVE and how it strengthens ZTNA. It goes on to show how to find the UUID of the device, explains the different modes of DIVE, and the minimum versions of Connect Client needed for DIVE to work.
Date published: | 04/20/2023 |
Functionality covered: | DIVE |
Description | This video introduces DIVE and how it strengthens ZTNA. It goes on to show how to find the UUID of the device, explains the different modes of DIVE, and the minimum versions of Connect Client needed for DIVE to work. |
Length | 06:29 |
Learn & Enforce
This video demonstrates the 'learn and enforce' mode of DIVE.
Date published: | 04/20/2023 |
Functionality covered: | DIVE Learn & Enforce Mode |
Description | This video demonstrates the use of DIVE 'learn and enforce mode.' CloudConnexa learns the device ID on the first successful connection and then locks the digital certificate in the device's configuration profile to that Device ID (UUID). Now, even if the configuration profile is transferred to another device, it cannot connect. Connections are only allowed from the device with which the connection profile was mapped. |
Length | 06:21 |
Enforce
This video demonstrates the 'enforce' mode of DIVE.
Date published: | 04/20/2023 |
Functionality covered: | DIVE Enforce Mode, Create User, Create Device, User Portal sign in with a temporary password, import connection profile, and connect with authentication. |
Description | This video demonstrates the use of DIVE 'enforce mode' to lock the digital certificate in the configuration profile to the device that has been authorized to use it based on the provisioned UUID. The video demonstrates that an unauthorized device cannot import a profile or connect; even if it is transferred to another device, it cannot connect. |
Length | 08:51 |