> 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-saas-security/onboard-a-supported-saas-application/onboard-harness.md). # Onboard Harness For SaaS Security to detect posture risks in your Harness instance, you must onboard your Harness instance to SaaS Security. Through the onboarding process, SaaS Security connects to a Harness API and, through the API, scans your Harness 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 Harness instance through an API key. During the onboarding process, SaaS Security prompts you for the API key. To onboard your Harness instance, complete the following actions: * Generate an API access key and personal access token * Connect SaaS Security to your Harness instance *** ### Step 1: Generate an API Access Key and Personal Access Token To access a Harness API, SaaS Security requires an API key that contains a personal access token of an administrator assigned to the Account Admin role. The API key inherits the permissions of the administrator who generates the key and token. 1. Open a web browser to the Harness site at [www.harness.io](https://www.harness.io) and log in as an administrator assigned to the Account Admin role. Required Permissions: You must log in as an administrator assigned to the Account Admin role. The account must also have permission to View and to Create/Edit authentication settings. 2. To open your profile, click the profile icon in the lower-left corner of the window. 3. On your profile, click + API Key. The New API Key dialog is displayed. 4. Enter a name for your key and click Save. The key appears in the My API Keys area. 5. For the new API key, click + Token. The New Token dialog is displayed. 6. Enter a name and expiration date for the token and click Generate Token. Harness generates and displays the personal access token. Copy and paste the token into a text file so you can provide it to SaaS Security during onboarding. **Note**: Do not continue to the next step unless you have copied the token. When SaaS Security prompts you for an API key during the onboarding process, enter this personal access token. *** ### Step 2: Connect SaaS Security to Your Harness Instance By adding a Harness app in Cortex, you enable SaaS Security to connect to your Harness 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 Harness tile. 4. Under **Capabilities**, enter a name for your application. 5. Select Security Posture under Default Capabilities and click Next. 6. Under **Connections**, enter the API key (personal access token) for accessing your Harness instance. 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-saas-security/onboard-a-supported-saas-application/onboard-harness.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.