---
title: "Interface schematic"
slug: "interface-schematic-v6-5"
description: "Learn how to set up a Collective with Appgate SDP, manage connections, and ensure secure access through detailed guides and troubleshooting tips."
updated: 2025-10-31T18:25:57Z
published: 2025-10-31T18:25:57Z
canonical: "support.appgate.com/interface-schematic-v6-5"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.appgate.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Interface schematic

Full details of the requirements for setting up an Appgate SDP Collective are covered in the topic [System Connections](/v1/docs/system-connections). Some step-by-step connectivity trouble shooting guides are also available in [Troubleshooting user/device access](/v1/docs/troubleshooting-user-and-device-access).

![Diagram illustrating network traffic flow between AWS and Azure components with various controllers and gateways.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/hmfile_hash_a7b1647f.png?sv=2026-02-06&spr=https&st=2026-10-26T23%3A24%3A03Z&se=2026-10-27T00%3A24%3A03Z&sr=c&sp=r&sig=pPmcKkfiIG9h39NhLDA%2FU1DnibLy5ENGjPwFXUCNzxA%3D)

** The LogServer can be interchanged with the LogForwarder.*

Most of the communications within the Collective uses TCP port 443. (UDP Port 443 and 53 are required when [SPA is used in UDP-TCP mode](/v1/docs/configure-client-profiles).)

Port 443 is used:

- for Clients (including the Connector/Portal) to make connections TO Controllers/Gateways.
- by appliances to make connections TO Controllers. This communication is only very limited and network capacity should not be a cause for concern even in larger-scale environments. This connection is used:

1. for healthchecks - the Controller requests each Appliance to provide the latest statistics so it can be displayed to the user or feed external monitoring via SNMP or Prometheus.
2. .when tokens are revoked by an admin - the Controller will push a Token revocation list to each Gateway, so that it can immediately force the Clients to re-establish their connection, ensuring that the Gateway is enforcing the latest Policies.
3. to send configuration updates when an appliance's configuration is changed by the Admin.
4. by each appliance when it queries the Controller for its current configuration at start up, and also does so periodically (no more frequently than once every 15 minutes) to make sure it’s up to date. This is designed to cover the scenario where an appliance is offline at the moment a configuration change is made in the admin UI.

- by appliances to send audit logs TO the LogServer/LogForwarder

1. Appliances will be sending audit log records to the LogServer/LogForwarder. These are typically quite small but the frequency/volume depends on the size of the system. Budget for 1 log record/user/second within the entire Collective. Log records are about 1.5KB each. So with 1000 users on a Gateway this might result in 1.5MB/s. With a 1Gbe NIC this would represent just over 1%.

- by appliances to send metrics TO the Metrics Aggregator

- Appliances will be sending metrics to the Metrics Aggregator. These are typically quite small but the volume depends on the size of the system.

Appgate SDP (Software Defined Perimeter) is a security solution that provides secure access to resources based on user identity and context, leveraging a zero trust security model.

A component that extends connectivity to remote sites and unmanaged resources without requiring the use of a standalone Client.

A web-based interface that allows users to access resources without requiring a standalone Client. It serves as a reverse proxy for user traffic.

The Controller is the central management appliance in the Appgate ZTNA system, responsible for user authentication, policy distribution, and overall system administration.

The virtual or physical instance on which the system is running. Each appliance is a stateless, configurable machine that can operate as a single function or a combination of functions.

A digital key used to authenticate and authorize users or devices, enabling secure access to resources.

An appliance that acts as an enforcement point, controlling user access to protected resources.