Quickstart Guide

Prev Next

This guide will help you configure a simple AppGate environment that allows secure remote access to protected applications and resources.

NOTE

Use these steps only for a demo or lab system. Do not apply them to a production system. Before you prepare a system for production, work with your AppGate representative to confirm the correct configuration.


AppGate Concepts and Terminology

AppGate ZTNA enables organizations to implement granular, context-aware access control in distributed environments. It operates without a traditional network perimeter and does not require specific hardware, functioning across cloud and hybrid environments through software virtualization.

The following lists concepts and terminology that you will encounter when setting up your AppGate environment:

  • Admin role. Defines an administrator’s privileges, such as the ability to create, edit, or delete appliances, policies, tags, and conditions. Admin roles are assigned using policies.

  • Appliance. The virtual 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.

  • Client. The application used to connect to the AppGate ZTNA system, providing secure access to resources.

  • Client profile. Includes information required for a client to connect to an AppGate Controller.

  • Collective. A group of appliances configured and managed together.

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

  • Entitlement. A defined access right or permission granted to users or devices, allowing them to access specific resources or functionalities within the AppGate ZTNA system.

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

  • Local user. Users added to the local database that are not listed in an external identity provider.

  • Policy. Assigns rights to users or devices after successful login.

  • Site. A group of networks or resources reachable from a Gateway.


Prerequisites

Before you begin, you must:

  • Have sufficient resources and permissions to install AppGate virtual appliances and the AppGate client. You will need:

    • A physical, virtual, or cloud-based environment on which to deploy AppGate

    • Permission to make an appliance directly accessible to the internet

    • Permission to install the full AppGate client onto a laptop or desktop

  • Decide if you will deploy AppGate virtual appliances on-premises or in a public cloud

  • Know which application or target resource you want protect, such as:

    • Access to a subnet

    • Access to a web application


Summary of Steps

The following sections will get your AppGate ZTNA environment up and running:

  1. Deploy virtual appliances by configuring the initial Controller appliance and enabling the Gateway functionality.

  2. Configure access rules in your AppGate environment by creating entitlements and configuring an access policy.

  3. Enable your end users by installing the client and generating client profiles.


Next steps: preparing your system for production

This section provides the basic steps for standing up an AppGate environment. For more information about preparing your system for production, refer to the following sections: