Knowledge Base
Browse Docs
  • Introduction
    1. DefensX
    2. DNS & Web Filtering
    3. Zero Trust Files
    4. Zero Trust Credentials
    5. ADWare Protection
    6. Remote Browser Isolation
    7. Secure Browser Extension
    8. Secure Mobile Browser
    9. System & Browser Requirements
  • Management
    1. Role-Based Access Control
    2. Message Templates
  • Deployment
    1. Deployment via RMM
    2. Operating System Agent
    3. Deployment via GPO
    4. Deployment via Intune
    5. VDI and Terminal Servers
    6. Windows Manual Deployment
    7. Mac MDM Deployment
    8. Mac Manual Deployment
    9. Network Deployment
    10. Secure Mobile Browser
    11. Bypass Option
    12. AI Protections
    13. SaaS Restrictions
    14. Bookmark Manager
  • Integrations
    1. Azure AD
    2. Identity Providers
    3. SIEM
  • Policy Management
    1. Configuring Policies
    2. Configuring Consents
    3. PII Protection
  • Secure Access (ZTNA)
    1. Introduction to ZTNA
    2. Configuration
  • Nexi AI
    1. Nexi AI
    2. Nexi AI for MSPs
    3. Nexi AI for End Users
  • Training Videos
    1. Onboarding Videos
    2. Attack Scenarios
    3. MSP Admin Training Series
  • Questions & Answers
    1. Licensing
    2. Incognito Mode
    3. Onboarding
    4. Active Directory
    5. Group Synchronization
    6. Agent
    7. Conflicting Softwares
    8. Reporting
    9. Virtual Desktops
    10. Using the Backend
    11. DNS & Web Filtering
  • MSP Automation
    1. Overview
    2. External Notifications
    3. Integrations
    4. Partner API
ONLINE DOCUMENTATION

Configuring ZTNA in DefensX

In this document
  • Preparing the Deployment for ZTNA
  • Creating Secure Access Policies
  • Creating Secure Access Services
  • Linking Service and User Group to a Secure Access Policy
  • Using DefensX ZTNA with Active Directory

Preparing the Deployment for ZTNA

Before configuring ZTNA services, the deployment environment must be prepared. For ZTNA environments, it is strongly recommended to place Connector Agents in a separate deployment where LOGON User is disabled. This approach ensures that the connector always operates with the required subscription and is not affected by users logging in to the machine.

Start by creating a dedicated deployment for connectors. Navigate to Policy Groups and click +New Deployment in the Deployment table. Create a new deployment named Connectors and ensure that Create a Local Group is enabled during the creation process.

Screenshot%202026 03 16%20at%2023.03.23
Screenshot%202026 03 16%20at%2023.03.50

After the deployment is created, open the Advanced Options for the new deployment and configure the following settings:

  • Set Enable LOGON User to Disabled

  • Set ZTNA Connection Mode to Automatic (Always-On)

Screenshot%202026 03 16%20at%2023.05.39
Screenshot%202026 03 16%20at%2023.06.33

Next, navigate to Settings → Subscriptions and add the deployment group created for the Connectors deployment to the Auto Provisioning Groups of the Premium+ subscription.

With this configuration, Connector Agents deployed through this deployment will automatically receive the Premium+ subscription and will not be affected by Windows users logging in to the machine.

Screenshot%202026 03 16%20at%2023.08.55
Screenshot%202026 03 16%20at%2023.09.21
Screenshot%202026 03 16%20at%2023.10.31

Once these configurations are completed, proceed with deploying the agents.

For detailed deployment instructions, see the Deployment guide.

If users connect from within an office network that already hosts a DefensX Connector, Office IPs can be defined for that connector.

These IPs should correspond to the public IP address used by the connector when accessing the DefensX ZTNA Cloud Network.

When a ZTNA client connects from an IP address matching the defined Office IPs, all ZTNA services provided by that connector are disabled locally. This allows the client to access services directly over the local network, bypassing the ZTNA tunnel.

After the agent installation is completed, navigate to the Deployment table and click the number under Deployed Agents for the relevant deployment. This will open the list of agents deployed under that deployment.

Screenshot%202026 03 16%20at%2023.12.52

From there, select the connector agent and click the Configure button for ZTNA Office IPs, where you can enter the organization’s external (public) office IP addresses.

Screenshot%202026 03 16%20at%2023.13.40
Screenshot%202026 03 16%20at%2023.14.53
Screenshot%202026 03 16%20at%2023.15.27
Screenshot%202026 03 16%20at%2023.15.51

After completing these steps, the connector will be ready to operate with ZTNA connectivity.

Creating Secure Access Policies

To create Secure Access Policies, navigate to the Configuration page.

Click + New Secure Access Policy, provide a name for the policy, and ensure that the Status is set to Active. After completing the required fields, save the configuration to create the policy.

Screenshot%202026 03 15%20at%2019.48.13
Screenshot%202026 03 15%20at%2019.50.27
Screenshot%202026 03 15%20at%2019.49.48

Creating Secure Access Services

Navigate to the Configuration page and click + New Secure Access Service.

Enter a Name that clearly identifies the service. Select the appropriate Connector (Agent) that will provide access to the service. Under Application Restrictions, you can select which browser or available process can use the service or choose No Restriction to let any process to use the secure tunnel to access the service and ensure that Status is set to Active.

In DNS Hostname or IP Address, define the hostname(s) or IP address(es) through which the service will be accessible. Set the Protocol to what is needed for that service, then specify the Target Service IP or Hostname by entering the IP address or hostname of the target service.

Finally, enter the required Port(s) that the service listens on and save the configuration to complete the Secure Access Service setup.

Use Case 1 - Remote Desktop Protocol

Screenshot%202026 03 15%20at%2020.14.23
Screenshot%202026 03 15%20at%2020.14.51

Use Case 2 - File Sharing

Screenshot%202026 03 15%20at%2020.17.09
Screenshot%202026 03 15%20at%2020.17.48
Screenshot%202026 03 15%20at%2020.18.17

Linking Service and User Group to a Secure Access Policy

In the Secure Access Policies table, click the Linked Services cell for the relevant policy and set the required Secure Access Service to Active.

Screenshot%202026 03 15%20at%2020.18.47
Screenshot%202026 03 15%20at%2020.19.12
Screenshot%202026 03 15%20at%2020.28.07

Next, click the Linked User Groups cell for the same policy and add the desired User Group as a membership.

Screenshot%202026 03 16%20at%2023.20.44
Screenshot%202026 03 18%20at%2013.56.17

Once these steps are completed, the selected services and user groups will be linked to the Secure Access Policy.

Screenshot%202026 03 18%20at%2013.58.22

If a Secure Access Policy has no group assignment, it applies to all DefensX ZTNA clients, granting them access to the defined services.

Using DefensX ZTNA with Active Directory

You can securely expose your Active Directory services through a DefensX Connector, without installing the DefensX Agent directly on your Primary Domain Controller (PDC).

It is best practice to use a separate machine (not the PDC) as the connector for Active Directory access. This simplifies configuration and avoids complexities related to Microsoft DNS Server settings.

After configuring all required ports in a Secure Access Service, you can:

  • Perform Group Policy updates

  • Access file servers

  • Join or remove computers from the domain

all securely over the ZTNA network.

For detailed configuration steps, see the Active Directory Services Configuration guide.

www.defensx.com
Secure Industries, Inc 101 Avenue of The Americas, Floor 9 New York, NY 10013