Application Discovery is part of the separately-licensable Optimizer feature that helps you migrate from a traditional network model to a ZTNA model. With a traditional VPN, it can be difficult to see which apps users access, which makes it harder to define the entitlements and policies that AppGate ZTNA requires. Application Discovery identifies the apps users access so you can create the right entitlements and policies.
This feature analyzes access patterns over time and produces insights you can use to refine entitlements and policies so that only authorized users can access the right resources.
In hosted or connected deployments, Application Discovery can help you respond to changing security needs while maintaining a smooth user experience.
Contact your AppGate representative about obtaining a feature license for Application Discovery. For information about how licensing works, see Licenses.
NOTE
The current version of Application Discovery does not detect public IP addresses. Each system supports up to 10,000 apps, 5,000 users, and 5,000 groups.
Prerequisites
A Collective that is ZTP-connected or ZTP-hosted.
A configured LogServer or LogForwarder that can connect to
logpusher.[region].appgate.neton port 443 andkafka.[region].appgate.neton ports 9192 through 9195.A feature license that includes Optimizer.
Broad host definitions in entitlements (TCP up actions only) for the Site where you want to discover applications.
An IdP attribute mapped to the
groupsclaim (for example, maproleor another attribute you use to group users).The DNS servers for the discovered apps must match the DNS servers configured on the Gateways. Gateways must also handle client DNS traffic. For best results, use zone transfer.
NOTE
Application Discovery does not work with secure DNS.
Operation of Application Discovery
Application Discovery runs when an entitlement action uses a broad host definition—for example, an IPv4/IPv6 subnet (192.168.0.0/24) and/or a full port range (1–65535) with the protocol set to TCP up. Using domain syntax (such as *.mycompany.com) is not considered a broad host definition.
NOTE
You can discover up to 5,000 applications, with up to 5,000 users per application. In version 6.5 and earlier, the limit is 5,000 user groups per application. In version 6.6 and later, the limit is 200 user groups.
Data collection and retention
Application Discovery exports data from the AppGate ZTNA environment to ZTP. This data contains the following audit log record types:
authentication_succeededauthorization_succeededip_access
For detailed content of these records, see Audit log detail.
Application Discovery also exports DNS request data from the Gateway.
Data is stored in the document database for 30 days after it is pushed, and then deleted.
If the Collective is disconnected from ZTP, the stored data is deleted at 00:00 UTC.
Keep in mind how AppGate ZTNA handles overlapping entitlements: The action with a smaller subnet has higher precedence. As a result, precisely defined actions—even when they fall within a broad host definition—are not forwarded to the LogPusher service.
Example (four entitlement actions):
TCP up to 192.168.0.0/24
TCP up to 192.168.0.1
TCP up to 192.168.1.1
TCP up to myserver.mycompany.com (resolves to 192.168.0.2)
In this example, only traffic for 192.168.0.3–192.168.0.254 is forwarded to LogPusher.
Application Discovery collects data that identifies this traffic and forwards it to the ZTP LogPusher service. The LogPusher stores the data in a document database organized by Collective. Other Collectives (even in the same account) cannot access the data.
Every hour, the ZTP Advisor service analyzes the database and generates a summary for administrators. The summary is stored until the Collective requests it. In the Discovered Apps page (Usage > Discovered Apps), each discovered app represents a hostname and port. From the list of Discovered Apps, you can create policies and entitlements for the corresponding traffic and user group.
NOTE
Discovered apps can take up to 15 minutes to appear.
After you create specific entitlements, traffic that matches those entitlements is excluded from discovery. Because the new entitlements have higher precedence, that traffic no longer uses the broad host definition (which you can keep).
As you add more specific entitlements, less traffic uses the broad host definition and the number of discovered apps decreases.
When no traffic uses the broad host definition, you can disable the related entitlement. If you want to keep monitoring for remaining traffic, change the broad host definition action to DENY. Discovery still records the traffic, but access is blocked until you create an entitlement that allows it.
Troubleshooting Application Discovery
To review the data sets used by Application Discovery:
In Discovered Apps (Usage > Discovered Apps), select Actions, Troubleshoot.
The Troubleshooting window shows when the system last received each data set: Access Data, Authentication Data, and DNS Data. These timestamps can take up to 15 minutes to update.
If Access Data Received is missing, check the following:
The LogForwarder or LogServer cannot connect to
logpusher.[region].appgate.net. See Prerequisites for Cloud Services in the ZTP User Guide.No LogForwarder or LogServer is configured for the Collective.
Traffic is not routed through AppGate ZTNA. If Authentication Data Received is also missing, the Controller may not be able to connect to
logpusher.[region].appgate.net.
If you expect traffic to appear but it does not, check for an existing narrow entitlement that matches the same traffic. Narrow entitlements take precedence over broad entitlements, so the traffic is excluded from discovery.
If Authentication Data Received is missing, the Controller may not be able to connect to
logpusher.[region].appgate.net.If DNS Data Received is missing, DNS requests may not be routed through AppGate ZTNA. See DNS and name resolution.
Select Download Data to download Application Discovery data in JSON format.
NOTE
Refresh the Discovered Apps page to see the latest troubleshooting data.