# Harmony SASE **Harmony Secure Access Service Edge** (SASE) provides cloud-delivered network security, allowing organizations to streamline secure remote access with precision. Integrating Harmony SASE with Apono allows you to automate just-in-time access by temporarily adding users to specific Harmony SASE groups. This ensures the right users get access only when needed and are automatically removed when access expires, which is ideal for short-term projects or incident response. This approach strengthens security, reduces operational overhead, and supports least-privilege access practices. *** ### Prerequisites

Item	Description
Harmony account access	Harmony SASE user account hosted by Perimeter 81 or Check Point
Apono connector	On-prem connection serving as a bridge between an SSH server and Apono: AWS Azure GCP Kubernetes Learn how to update an existing AWS, Azure, GCP, or Kubernetes connector.
Harmony API key	Unique key generated in Harmony platform to authenticate connection with Apono Learn how to generate an API key with Harmony. NOTE: When creating the key, select all Key Permissions under the following categories for Apono to access your Harmony instance: Members Groups
Apono secret	Value generated with the credentials of the user you create Create your secret based on your Redis Cloud API account key and user key: `"api_key": <ACCOUNT_KEY>` `"secret_key": <USER_KEY>` Apono does not store credentials. The Apono Connector uses the secret to communicate with services in your environment and separate the Apono web app from the environment for maximal security.

*** ### Integrate Harmony SASE

{% hint style="success" %} You can also use the steps below to integrate with Apono using Terraform. In step **10**, instead of clicking **Confirm**, follow the **Are you integrating with Apono using Terraform?** guidance. {% endhint %} Follow these steps to complete the integration: 1. On the [**Catalog**](https://app.apono.io/catalog?search=harmony) tab, click **Harmony**. The **Connect Integration** page appears. 2. Under **Discovery**, click **Next**. The **Apono connector** section expands. 3. From the dropdown menu, select a connector. Choosing a connector links Apono to all the services available on the account where the connector is located. {% hint style="info" %} If the desired connector is not listed, click **+ Add new connector** and follow the instructions for creating a connector ([AWS](/docs/aws-environment/apono-connector-for-aws.md), [Azure](/docs/azure-environment/apono-connector-for-azure.md), [GCP](/docs/gcp-environment/apono-connector-for-gcp.md), [Kubernetes](/docs/kubernetes-environment/apono-connector-for-kubernetes.md)). {% endhint %} 4. Click **Next**. The **Integration Config** page appears. 5. Enter a unique, alphanumeric, user-friendly **Integration Name** to identify the integration when constructing an access flow. 6. From the dropdown menu, select a **Region** for the config’s activity. 7. Click **Next**. The **Secret Store** section expands. 8. [Associate the secret or credentials](/docs/connectors-and-secrets/apono-integration-secret.md). {% hint style="info" %} If you select the Apono secret manager, enter the value of your [**Harmony SASE workspace API Key**](#prerequisites). {% endhint %} 9. Click **Next**. The **Get more with Apono** section expands. 10. Define the **Get more with Apono** settings.

Setting	Description
Custom Access Details	(Optional) Instructions explaining how to access this integration's resources Upon accessing an integration, a message with these instructions will be displayed to end users in the User Portal. The message may include up to 400 characters. To view the message as it appears to end users, click Preview.
Integration Owner	(Optional) Fallback approver if no resource owner is found Follow these steps to define one or several integration owners: From the Attribute dropdown menu, select User or Group under the relevant identity provider (IdP) platform. From the Value dropdown menu, select one or multiple users or groups. NOTE: When Resource Owner is defined, an Integration Owner must be defined.
Resource Owner	(Optional) Group or role responsible for managing access approvals or rejections for the resource Follow these steps to define one or several resource owners: Enter a Key name. This value is the name of the tag created in your cloud environment. From the Attribute dropdown menu, select an attribute under the IdP platform to which the key name is associated. Apono will use the value associated with the key (tag) to identify the resource owner. When you update the membership of the group or role in your IdP platform, this change is also reflected in Apono. NOTE: When this setting is defined, an Integration Owner must also be defined.

Setting

Description

Custom Access Details

(Optional) Instructions explaining how to access this integration's resources

Upon accessing an integration, a message with these instructions will be displayed to end users in the User Portal. The message may include up to 400 characters.

To view the message as it appears to end users, click Preview.

Integration Owner

(Optional) Fallback approver if no resource owner is found

Follow these steps to define one or several integration owners:

From the Attribute dropdown menu, select User or Group under the relevant identity provider (IdP) platform.
From the Value dropdown menu, select one or multiple users or groups.

NOTE: When Resource Owner is defined, an Integration Owner must be defined.

Resource Owner

(Optional) Group or role responsible for managing access approvals or rejections for the resource

Follow these steps to define one or several resource owners:

Enter a Key name. This value is the name of the tag created in your cloud environment.
From the Attribute dropdown menu, select an attribute under the IdP platform to which the key name is associated.

Apono will use the value associated with the key (tag) to identify the resource owner. When you update the membership of the group or role in your IdP platform, this change is also reflected in Apono.

NOTE: When this setting is defined, an Integration Owner must also be defined.

10. Click **Confirm**.

💡Are you integrating with Apono using Terraform?

If you want to integrate with Apono using Terraform, follow these steps instead of clicking **Confirm**: 1. At the top of the screen, click **View as Code**. A modal appears with the completed Terraform configuration code. 2. Click to copy the code. 3. Make any additional edits. 4. Deploy the code in your Terraform. Refer to [Integration Config Metadata](https://docs.apono.io/metadata-for-integration-config/integration-metadata/ssh) for more details about the schema definition.

#### Usage Now that the integration is complete, you can add Harmony SASE to define the grantees or resources in an access flow. This allows only the correct requesters to securely access your Harmony-synced groups, based on the access flow’s approval and provisioning rules. Follow the guidance in these articles to define the resource using Harmony SASE.

Access flow type	Resources
Self Serve	Define permitted requesters Define the resource
Automatic	Define permitted requesters Define the resource

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.apono.io/docs/additional-integrations/network-management/harmony-sase.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.