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

1. Navigate to Policy Configuration > Geo Fences in the zAccess Director UI.
2. Click ADD GEO FENCE.
3. Provide a Group Name (e.g., “Headquarters Zone” or “Restricted Campus Area”).
4. Enter the Latitude and Longitude coordinates of the target location.
5. Specify the Radius (in meters) that defines the boundary around the location.
6. 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.