Introduction to ZTNA

A new era in security and connectivity

In today's digital world, where information security is a priority, innovative technologies such as Zero Trust Network Access (ZTNA) have become indispensable by offering a more secure and efficient way of connecting users and devices to corporate networks.

This article aims to simplify the concept of ZTNA and demonstrate its practical applications, exemplifying how ZTNA technology can optimize the connectivity and security of your network.

What is ZTNA?

ZTNA is a security architecture based on the principle of “never trust, always verify”. This means that, unlike traditional models that rely on users or devices within the network, ZTNA requires constant authentication and authorization to access resources, regardless of their location.

It offers greater control, flexibility and protection, especially in cloud environments and distributed networks, making it ideal for companies that operate with critical data in multiple locations or that need to securely allow remote access.

The origin of ZTNA

The need for ZTNA has grown due to the limitations of VPNs, such as:

• Lateral movement: After joining a VPN, users can access different parts of the network, creating risks if their credentials are compromised.

• Latency: The centralization of traffic in VPNs can lead to significant delays.

• Scalability: Modern networks need solutions that meet the complexity of hybrid and distributed environments.

In addition, ZTNA meets more stringent security demands, such as identity-based authentication and policy-based access control.

Applications of ZTNA

ZTNA is ideal for companies that:

• Operate in hybrid or multi-cloud environments.

• Need rigorous security in sectors such as banking and healthcare.

• Want to improve remote access for employees in a secure and scalable way.

• Are looking to reduce the risk of cyber attacks, such as ransomware and credential hijacking.

Benefits of ZTNA

• Greater security: Lateral movement is eliminated, as access is segmented and based on identity. With robust access policies and continuous authentication, you can be sure that only authorized users can access your resources.

• Reduced latency: Distributed architectures optimize traffic by eliminating unnecessary network jumps. ZTNA's architecture minimizes latency, ensuring that communication between devices and resources is fast and efficient.

• Flexibility: It can be implemented in hybrid environments, with multiple clouds and data centers.

• Simplified management: There's no need to set up complex entry rules. Administration is done autonomously through the Digibee Integration Platform.

• High availability: With an SLA of 99.99%, ZTNA offers reliability for critical operations.

How does ZTNA work?

The ZTNA architecture integrates several components, creating a secure, scalable, and high-performance corporate network. These are:

Access Policies and App WANs

Access policies are rules that determine who can access what within the network, limiting access based on identity.

Practical example: If a user needs to access a financial system, the access policy will ensure that they only have access to the system if they are authenticated and authorized according to the defined rules.

Fabric

Fabric is the network infrastructure that connects all the devices and resources within the ZTNA architecture. It allows communication to take place securely and efficiently, managing traffic between different parts of the network dynamically.

Practical example: When a user accesses a resource or application, the Fabric will ensure that the data flows securely and optimally, choosing the best route for the traffic according to the network conditions.

Edge Routers

Edge Routers are a key component within the ZTNA architecture, acting as connection points between network resources. They ensure that only authorized sources can access network resources, and they do this by applying the access policies defined in the system.

Edge Routers not only guarantee security, but also help optimize traffic and minimize latency by dynamically adjusting communication according to the network situation.

Network Mappings

Network Mappings are the protected resources within the network environment, such as APIs, servers, or applications. The ZTNA architecture creates a private network for these services, ensuring that only authenticated users and devices can access them.

Practical example: If your company offers an API for consulting financial data, ZTNA architecture ensures that this API is only accessible to users with the right permissions, without exposing it to security risks.

First steps in ZTNA

Check below the steps that must be taken to migrate to ZTNA on the Digibee Integration Platform:

Step 1: Map the resources that need protection, such as APIs and critical applications

Before setting up ZTNA, it’s essential to identify and categorize the resources that need to be protected. This ensures that the scope is clear and that the security measures are adequate.

List critical resources

• Externally exposed APIs, such as: api.mycompany.com/v1/login.

• Internal applications, such as an ERP system or a financial database.

• Cloud services, such as CRM or project management platforms.

Sort resources by sensitivity

• High sensitivity: Financial data, authentication APIs.

• Medium sensitivity: Non-public internal documents.

• Low sensitivity: Training resources or public materials.

Identify users and systems that need access

• Internal teams, such as developers or financial analysts.

• Automated applications, such as bots that consume APIs.

• External partners who need access to specific systems.

Map the location of resources

• On-Premises: Local servers or data centers.

• Cloud: Amazon AWS, Microsoft Azure, Google Cloud.

• Hybrid: Resources distributed between cloud and on-premises.

Understand communication flows

• Which users access which resources?

• How do applications interact with each other?

Step 2: Configure Edge Routers in strategic locations to optimize traffic

The Edge Router is the central component for establishing secure communication in ZTNA. As we saw earlier, its configuration and positioning are crucial.

Choose the environment

• On-Premises:

  • Position the Edge Router inside the Data Center, close to the resource to be protected.

  • Example: Protecting a local database server.

• Cloud:

  • Use the AWS Marketplace to deploy the Edge Router directly in the API region.

  • Example: APIs hosted on AWS.

Plan for redundancy

• Always configure at least two Edge Routers to ensure high availability.

• Example: One in US East (AWS US-East) and another in US West (AWS US-West).

Register the Edge Router

1. Access the connectivity section for ZTNA in the Digibee Integration Platform.

2. Generate a key and register the Edge Router in the chosen environment. Example of a name: EdgeRouter-Prod-US-East.

Read the full documentation for step-by-step instructions on how to generate new keys.

Configure Outbound Rules

• No inbound rules are required in the firewall.

• Make sure to open required outbound ports, such as:

  • Port 443 (HTTPS): Secure communication.

  • Specific ports for the ZTNA controller.

Grant access

One of the most important premises of ZTNA is to grant access only to what is necessary, limiting excessive privileges.

1. Restrict ports and endpoints:

• Limit access to specific ports and endpoints.

• Example:

  • Internal users: Only port 22 (SSH) and 443 (HTTPS).

  • External partners: Only api.partner.myorganization.com.

1. Enable microsegmentation:

• Example: An Edge Router can allow only one application to interact with the financial database, for example a financial dashboard.

Migration can be done gradually, allowing existing infrastructure (such as VPNs) to coexist while ZTNA is implemented.

Integrated example

Scenario

A company operates a financial application that allows customer queries. This application is distributed between a local data center and an AWS cloud.

Solution with ZTNA

1. Map the api.financial.com API and the local database as critical resources.

2. Configure an Edge Router in AWS (for the API) and another in the local data center (for the database).

3. Create access policies to allow:

   • Only authenticated users query the API.

   • Only the API has access to the database.

4. Test communication with a simulated user and validate latency.

Final thoughts

ZTNA represents a significant advance in the security and connectivity of modern networks. Its model based on zero trust, continuous authentication and microsegmentation offers a robust solution to today's cybersecurity challenges.

For those starting out, ZTNA may seem complex, but its implementation brings benefits that far outweigh the initial efforts. Whether for small or large companies, ZTNA is a powerful tool for protecting data and ensuring secure operations in the digital environment.

If you're looking to transform your network security, ZTNA could be the next step in the evolution of your infrastructure, and Digibee is ready to support you.