> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/cloud-security/cortex-cloud-ai-security/cortex-cloud-saas-security/onboard-a-supported-saas-application/onboard-kustomer.md). # Onboard Kustomer For SaaS Security to detect posture risks in your Kustomer instance, you must onboard your Kustomer instance to SaaS Security. Through the onboarding process, SaaS Security connects to a Kustomer API and, through the API, scans your Kustomer instance for misconfigured settings. If there are misconfigured settings, SaaS Security suggests a remediation action based on best practices. SaaS Security gets access to your Kustomer instance through an API access key. During the onboarding process, SaaS Security prompts you for the API access key and related information for your Kustomer instance. To onboard your Kustomer instance, complete the following actions: * Collect information for accessing your Kustomer instance * Connect SaaS Security to your Kustomer instance *** ### Step 1: Collect Information for Accessing Your Kustomer Instance To access your Kustomer instance, SaaS Security requires the following information, which you specify during the onboarding process. | Item | Description | | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | API Key | A generated character string that uniquely identifies your organization to the Kustomer API. SaaS Security requires this API key to authenticate to the Kustomer API. Required permissions: The API key must be generated by an administrator and configured with the org.permission role. | | Region | The region (US or EU) where your organization deployed Kustomer. | As you complete the following steps, make note of the values of the items described in the preceding table. You will need to enter these values during onboarding to access your Kustomer instance from SaaS Security. 1. Log in to Kustomer as an administrator. 1. Open a web browser and go to the Kustomer login page at [www.kustomerapp.com/domain](https://www.kustomerapp.com/domain). Enter your organization name and click Continue. 2. Log in using administrator credentials. 3. Generate an API key for your organization. 1. Click the settings icon (gear icon) in the lower-left corner of the window and select SECURITY > API Keys. 2. Click + Add API Key. 3. Fill in the fields of the ADD API KEY dialog: 1. Enter a name for the new API key. 2. In the Roles field, specify org.permission. Required permissions: The key must be configured with the org.permission role. 3. Specify an expiration date for the key. 4. Click Create. Kustomer generates and displays your new key. 5. Copy the API key and paste it into a text file. **Note**: Do not continue to the next step unless you have copied the API key. You must provide this key to SaaS Security during the onboarding process. 4. Identify the region (United States or European Union) where your organization instance was deployed. Because API calls are region-specific, you must provide this information to SaaS Security during the onboarding process. *** ### Step 2: Connect SaaS Security to Your Kustomer Instance By adding a Kustomer app in Cortex, you enable SaaS Security to connect to your Kustomer instance. 1. Log in to Cortex. 2. Select **Settings > Data Sources and Integrations > Add New**. You can use the Search bar to find the app you want to connect to. 3. Click the Kustomer tile. 4. Under **Capabilities**, enter a name for your application. 5. Select Security Posture under Default Capabilities and click Next. 6. Under **Connections**, enter your API Key and Region. 7. Under **Configurations**, select a **Sync Interval**. Choose a meaningful **Tag** to distinguish between various applications in different environments. 8. Click **Next** to complete the onboarding validation process. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://cortex-docs.paloaltonetworks.com/cortex-xsiam/cloud-security/cortex-cloud-ai-security/cortex-cloud-saas-security/onboard-a-supported-saas-application/onboard-kustomer.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.