How Can We Help?
-
zWAN
-
-
-
-
-
-
- Articles coming soon
-
-
-
- Articles coming soon
-
-
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
-
-
-
-
-
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
-
-
-
-
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
-
-
-
-
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
-
-
- Articles coming soon
-
- IPsec Tunnel not Establishing
- SSL-VPN Tunnel not Establishing
- Mobile Network Issues
- Management Tunnel does not Establish
- DNS not Resolving from Local Network Appliance
- DNS Resolution Issues in Tunnel Configuration
- DHCP Server not Leasing IP to LAN PC
- Debugging EC Events - Unknown Status Issue
- Trusted-MAC Geofencing Issues
- DNS Issues from DC LAN PC
- Troubleshooting LAN Connectivity to Internet via WAN, Remote Branch LAN, or Local Branch LAN
- NetBalancer gateways displaying Faulty/Inactive
- Packet Drop Issues
-
-
zTC
-
- Articles coming soon
-
StorTrends
-
zAccess
-
- Articles coming soon
-
- Articles coming soon
-
zGuardian
You are here:
Print
Geo Fences
0 out Of 5 Stars
5 Stars | 0% | |
4 Stars | 0% | |
3 Stars | 0% | |
2 Stars | 0% | |
1 Stars | 0% |
Quick Overview
Geo Fences in zAccess allow administrators to define physical boundaries using geographic coordinates (latitude and longitude). Devices that move outside of the defined radius from a specified location can be automatically denied access to configured applications. This feature is crucial for enforcing location-aware access policies in sensitive or regulated environments.
How to Use This Feature in the UI
- Navigate to Policy Configuration > Geo Fences in the zAccess Director UI.
- Click ADD GEO FENCE.
- Provide a Group Name (e.g., “Headquarters Zone” or “Restricted Campus Area”).
- Enter the Latitude and Longitude coordinates of the target location.
- Specify the Radius (in meters) that defines the boundary around the location.
- Click Save to apply the geo fence. Ensure it is referenced in a ruleset for enforcement.
Concepts & Use Cases
- Location-Based Access Control: Allow or deny application access based on whether a device is inside a trusted geographic boundary.
- Security Enforcement: Prevent data access when devices connect from unknown or high-risk areas.
- Remote Work Governance: Ensure employees connect only from approved work zones (e.g., corporate office, approved co-working spaces).
- Compliance with Geo Restrictions: Enforce region-specific data access restrictions for regulated industries (e.g., healthcare, finance, defense).
Troubleshooting & FAQs
- Why is a device denied access even inside the geo fence?
Ensure the device’s reported location (via OS telemetry) is accurate and matches the coordinates and radius defined in the group. - Can I define multiple coordinates in one geo fence?
No. Each geo fence is based on a single coordinate pair and radius. Use multiple entries for complex coverage. - What happens if the device has no GPS data?
zAccess relies on the endpoint to report location. Devices without GPS may fall back on IP-based geolocation, which is less precise. - Can geo fences apply to wired devices?
Only if the wired device reports location via OS or agent-level configuration.
Was this article helpful?
0 out Of 5 Stars
5 Stars | 0% | |
4 Stars | 0% | |
3 Stars | 0% | |
2 Stars | 0% | |
1 Stars | 0% |
5
Table of Contents