Since Active Directory is based on DNS and LDAP, it’s important to understand the namespace. The structure and schema for Active Directory is irrelevant for the functioning of Zscaler Private Access, however it is important to understand it to ensure Application Segmentation functions correctly. The security overlay could be a simple password, NTLM Authentication Blob, Kerberos authentication token, or Client Certificate, where these credentials are stored securely in the user object in Active Directory. It is a tree structure exposed via LDAP and DNS, with a security overlay. It can be utilised as a data structure to store configuration data for Active Directory objects and applications such as SCCM.

This document is NOT intended to be an exhaustive description of Active Directory, however it will describe the key services, and how Zscaler Private Access functions to utilise them.Īctive Directory is used to manage users, devices, and other objects in an organization. The document then covers how Zscaler Private Access should be configured to work transparently with it with these Microsoft Services. This document describes some of the workings of Microsoft Active Directory, Group Policy and SCCM. Even with the migration to Azure Active Directory, companies continue to utilise Active Directory in a Hybrid environment where workstations may be joined solely to AD, or both AD joined and WorkPlace joined to AAD.Ĭompanies deploying Zscaler Private Access should consider the connectivity workstations need to Active Directory to retrieve authentication tokens, connect to file shares, and to receive GPO updates. Microsoft Active Directory is used extensively across global enterprises.

Wireshark ip location map