Zero Trust Network Access (ZTNA) is a security approach where users are not trusted by default — Their access is automatically denied, even if they are already inside the network.
All access requests must be authenticated, authorized, and continuously validated based on their identity, registration, roles and permissions.
How Zero Trust Network Access (ZTNA) works
1. Endpoint Authentication
Before any network access is allowed, the ZTNA systems need to verify the identity of the user. This ensures that only a legitimate user can start a session.
In SC//Connect™, we utilize the OAuth 2.0 method to verify the user's identity. This method includes:
- Username/Password
- MFA — Multi-factor authentication (one-time code)
Only the successfully authenticated users/devices (endpoints) can start a session.
Example:
After entering the correct username/password, the user receives an MFA one-time code request to log in to the SC//Connect™ Orchestrator.
Entering the correct one-time code → the user proves their identity to the system → Access is granted.
2. Network Registration
Network Registration is a process by which users identify themselves to a network to obtain authorized access. It creates a binding between the User’s identity and Network Identity. Once registration is successful, the user’s identity is bound to a specific private IP on their pre-assigned network, enabling controlled access.
Example :
A user with the email address user@example.com provides a signed authentication token and is assigned a private IP address 10.10.10.22.
3. Role Look-up via Gateway RBAC
After Network registration, the gateway checks which roles are assigned to the user in its Role-Based Access Control (RBAC) database.
Roles define what resources the user is allowed to access
Example :
IP address 10.10.10.22 belongs to user@example.com.
This user has the following roles:
- Role X = Access to the internal trading systems
- Role Y = Access to the Cloud services (such as Google Workspace)
With this role combination, the authenticated user@example.com with the IP = 10.10.10.22 can access both the internal trading systems and Google Workspace.
4. Permission Verification via Gateway RBAC
Permission Verification via Gateway RBAC is the final step in the access control process. In this process, the gateway checks whether users' access is permitted by their role(s) or not. When users try to reach a resource, the gateway compares the permission (tied to users' role) with the resources (network or application features) users are trying to access. If the role permits, access is allowed; if not, access is denied.
Example :
Following the previous example, after the Endpoint Authentication, Network Registration and Role Look-up via Gateway RBAC are completed successfully. Then the gateway checks:
- Role X has permission to access the network 10.10.0.0/16
- Result: Permission Verification successful → the gateway allows access.
If the user tried to access 192.168.0.0/16 and Role X does not have permission for that network → the gateway would deny access.
Benefits of Zero Trust Network Access (ZTNA)
- Enhanced Security and Reduced Risk — Access is denied by default; only authorized users can see it → minimizes the attack surface.
- Identity-Based Access — Users only access the specific resources that match their identity and assigned roles — no broad network access.
- Better User Experience — Users get direct, secure access to the resources they need without navigating the entire internal network → reduce the latency