Documentation — August 28, 2026
5 files changed, 58 insertions, 76 deletions — view the commit on the mirror.
Onboard Aha.io deleted and rewritten onto the Aha! connector page; 12 SaaS app links un-broken
- Onboard Aha.io was deleted from Cortex Cloud SaaS Security and its instructions rewritten onto the Aha! vendor connector page — a bookmark break.
- The SaaS app connection table swapped
broken-referencefor real links on its first twelve rows, Aha.io through Coveo. - The relocated text drops the SaaS Security / SSPM framing for Cortex and the data connector configuration wizard.
- The XSIAM book is one page smaller, 2,218 to 2,217.
Highlights
-
Onboard Aha.io is gone; its setup steps now live on the Aha! data connector page
The page under Connect a SaaS Application was deleted outright and its 55 lines reappear, reworded, as a Prerequisites section on the vendor connector page — the same instructions at a different URL.
-
Twelve entries in the SaaS app connection table stopped pointing at broken-reference
Aha.io now targets the vendor connector page while Asana, Atlassian, Automox, BusinessMap, Celonis, Cisco Duo, Cisco Meraki, Clickup, Contentful, Couchbase and Coveo target their sibling onboarding pages; Databricks onward are still broken-reference.
-
The Aha! prerequisites name Tenant ID, Client ID and Client Secret as the connection inputs
The new Configure Aha! section routes the reader to the data connector configuration wizard and lists those three values, alongside the existing Okta subdomain and Okta or Azure 2FA secret requirements.
Changes
5 files listed, 4 written up and shaded below.
-
▸ ▾ README modified +1 −1
READMEGenerated by the mirror — not a documentation page, so no diff is kept. The counts above still say how much moved.
-
▸ ▾ Navigation manifest (xsiam) modified +1 −7 Navigation drops the Onboard Aha.io node, taking the Cortex XSIAM Documentation book from 2,218 pages to 2,217.
.meta/xsiamThe book's page tree and ordering — not a documentation page, so no diff is kept. The counts above still say how much moved.
-
▸ ▾ Connect a SaaS application modified +12 −12 Twelve rows from Aha.io to Coveo now link to real onboarding pages rather than broken-reference; the rows from Databricks onward are unchanged.
xsiam/cloud-security/cortex-cloud-saas-security/connect-a-saas-applicationRead it on the Cortex docs portal ↗ Read it here → This file's diff on GitHub ↗
Before After@@ -9,28 +9,28 @@ description: >-To detect posture risks, applications must first be connected to Cortex SaaS Security and have the necessary permissions to scan SaaS application settings. During data connection, Cortex SaaS Security prompts you for the configuration information required to establish a connection with the SaaS app. The configuration information that SaaS Security requires differs from app to app, and you might need to collect configuration information prior to onboarding.To detect posture risks, applications must first be connected to Cortex SaaS Security and have the necessary permissions to scan SaaS application settings. During data connection, Cortex SaaS Security prompts you for the configuration information required to establish a connection with the SaaS app. The configuration information that SaaS Security requires differs from app to app, and you might need to collect configuration information prior to onboarding.When you connect an application you may also be prompted to provide required for application connection, such as administrator credentials for a service account. The required information varies, and in many cases you must first take some actions on the SaaS app, such as creating an API key.When you connect an application you may also be prompted to provide required for application connection, such as administrator credentials for a service account. The required information varies, and in many cases you must first take some actions on the SaaS app, such as creating an API key.The following table provides links to detailed connection instructions for most applications. Where detailed instructions are not available for a particular SaaS application, the table includes the relevant onboarding steps.The following table provides links to detailed connection instructions for most applications. Where detailed instructions are not available for a particular SaaS application, the table includes the relevant onboarding steps.SaaS app connection stepsSaaS app connection steps| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- || ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |Aha.ioAha.ioAsanaAsanaAtlassianAtlassianAutomoxAutomoxBusinessMapBusinessMapCelonisCelonisCisco DuoCisco DuoCisco MerakiCisco MerakiClickupClickupContentfulContentfulCouchbaseCouchbaseCoveoCoveoDatabricksDatabricksDataDogDataDogGainsightGainsightGrammarlyGrammarlyHarnessHarnessIntercomIntercomJamf ProJamf ProJumpcloudJumpcloudShow markdown source
@@ -9,28 +9,28 @@ description: >- To detect posture risks, applications must first be connected to Cortex SaaS Security and have the necessary permissions to scan SaaS application settings. During data connection, Cortex SaaS Security prompts you for the configuration information required to establish a connection with the SaaS app. The configuration information that SaaS Security requires differs from app to app, and you might need to collect configuration information prior to onboarding. When you connect an application you may also be prompted to provide required for application connection, such as administrator credentials for a service account. The required information varies, and in many cases you must first take some actions on the SaaS app, such as creating an API key. The following table provides links to detailed connection instructions for most applications. Where detailed instructions are not available for a particular SaaS application, the table includes the relevant onboarding steps. | **SaaS app connection steps** | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| [Aha.io](broken-reference) | -| [Asana](broken-reference) | -| [Atlassian](broken-reference) | -| [Automox](broken-reference) | -| [BusinessMap](broken-reference) | -| [Celonis](broken-reference) | -| [Cisco Duo](broken-reference) | -| [Cisco Meraki](broken-reference) | -| [Clickup](broken-reference) | -| [Contentful](broken-reference) | -| [Couchbase](broken-reference) | -| [Coveo](broken-reference) | +| [Aha.io](../../configure-cortex-xsiam/cortex-xsiam-data-sources/vendor-specific-data-sources-and-connectors/aha/aha) | +| [Asana](connect-a-saas-application/onboard-asana) | +| [Atlassian](connect-a-saas-application/onboard-atlassian) | +| [Automox](connect-a-saas-application/onboard-automox) | +| [BusinessMap](connect-a-saas-application/onboard-businessmap) | +| [Celonis](connect-a-saas-application/onboard-celonis) | +| [Cisco Duo](connect-a-saas-application/onboard-cisco-duo) | +| [Cisco Meraki](connect-a-saas-application/onboard-cisco-meraki) | +| [Clickup](connect-a-saas-application/onboard-clickup) | +| [Contentful](connect-a-saas-application/onboard-contentful) | +| [Couchbase](connect-a-saas-application/onboard-couchbase) | +| [Coveo](connect-a-saas-application/onboard-coveo) | | [Databricks](broken-reference) | | [DataDog](broken-reference) | | [Gainsight](broken-reference) | | [Grammarly](broken-reference) | | [Harness](broken-reference) | | [Intercom](broken-reference) | | [Jamf Pro](broken-reference) | | [Jumpcloud](broken-reference) |
-
▸ ▾ Onboard Aha.io deleted +0 −55 Deleted; the onboarding instructions it carried were moved to the Aha! vendor connector page.
xsiam/cloud-security/cortex-cloud-saas-security/connect-a-saas-application/onboard-aha.ioRead it on the Cortex docs portal ↗ This file's diff on GitHub ↗
Before After@@ -1,55 +0,0 @@---description: >-Onboard Aha.io in Cortex XSIAM to track misconfigurations and applicationcompliance.---# Onboard Aha.ioFor SaaS Security to detect posture risks in your Aha.io instance, you must onboard your Aha.io instance to SaaS Security. Through the onboarding process, SaaS Security logs in to Aha.io using administrator account credentials. This account is used to scan your Aha.io 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 Aha.io instance by using Okta SSO or Microsoft Azure credentials that you provide during the onboarding process. For this reason, your organization must be using Okta or Microsoft Azure as an identity provider. The Okta or Microsoft Azure account must be configured for multi-factor authentication (MFA) using one-time passcodes.\To onboard your Aha.io instance, you must complete the following actions:1. Collect information for accessing your Aha.io instance.To access your Aha.io instance, you will need the following information, which you will specify during the onboarding process:• User email: The login email address of the account that SSPM will use to access your Aha.io instance. Required Permissions: The user account must be assigned to both the Account and Billing administrator roles in Aha.io.• Password: The password for the login account.• Instance Host: The custom domain for accessing your organization's Aha.io account. You specify this domain when you sign up for an Aha.io account, and it is included as part of the URL that you use to access the account.If you're logging in through Okta, you must provide SaaS Security with the following additional information:• Okta subdomain: The Okta subdomain for your organization. The subdomain was included in the login URL that Okta assigned to your organization.• Okta 2FA secret: A key that is used to generate one-time passcodes for MFA.If you're using Azure Active Directory (AD) as your identity provider, you must provide SSPM with the following additional information:• Azure 2FA secret: A key that is used to generate one-time passcodes for MFA.As you complete the following steps, make note of the values of the items described in the preceding tables. You will need to enter these values during onboarding to access your Aha.io instance from SaaS Security.2. Identify the Okta user account that SaaS Security will use to access your Aha.io instance. The user account must be assigned to both the Account and Billing administrator roles in Aha.io.3. Get a secret key for MFA. The steps you follow to get the MFA secret key differ depending on the identity provider you're using to access the account.4. (For Okta log in) To access the account through Okta:1. Identify your Okta subdomain.2. Generate and copy an MFA secret key.5. (For Microsoft Azure log in) To access the account through Microsoft Azure:1. Enable third-party software OATH tokens for the administrator account.2. Configure the account for MFA and copy the MFA secret key.3. Make note of your organization's Aha.io instance host name.After you log in to Aha.io, the instance host name is a unique subdomain included in the Aha.io URL. The URL format is <instance_host>.aha.io.4. Connect SaaS Security to your Aha.io instance.1. Log in to Cortex.2. Select Modules > SaaS Security > Add Data Source. You can use the Search bar to find the app you wish to connect to.3. Click the Aha.io tile.4. Under Capabilities, Enter a Name for your application.5. Select Security Posture under Default Capabilities and click Next.6. Under Connections, provide the Tenant ID, Client ID, and Client Secret.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.Show markdown source
@@ -1,55 +0,0 @@ ---- -description: >- - Onboard Aha.io in Cortex XSIAM to track misconfigurations and application - compliance. ---- - -# Onboard Aha.io - -For SaaS Security to detect posture risks in your Aha.io instance, you must onboard your [Aha.io](http://aha.io) instance to SaaS Security. Through the onboarding process, SaaS Security logs in to Aha.io using administrator account credentials. This account is used to scan your Aha.io 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 Aha.io instance by using Okta SSO or Microsoft Azure credentials that you provide during the onboarding process. For this reason, your organization must be using Okta or Microsoft Azure as an identity provider. The Okta or Microsoft Azure account must be configured for multi-factor authentication (MFA) using one-time passcodes. - -\ -To onboard your Aha.io instance, you must complete the following actions: - -1. Collect information for accessing your Aha.io instance. - -To access your Aha.io instance, you will need the following information, which you will specify during the onboarding process: - -* User email: The login email address of the account that SSPM will use to access your Aha.io instance. Required Permissions: The user account must be assigned to both the Account and Billing administrator roles in Aha.io. -* Password: The password for the login account. -* Instance Host: The custom domain for accessing your organization's Aha.io account. You specify this domain when you sign up for an Aha.io account, and it is included as part of the URL that you use to access the account. - -If you're logging in through Okta, you must provide SaaS Security with the following additional information: - -* Okta subdomain: The Okta subdomain for your organization. The subdomain was included in the login URL that Okta assigned to your organization. -* Okta 2FA secret: A key that is used to generate one-time passcodes for MFA. - -If you're using Azure Active Directory (AD) as your identity provider, you must provide SSPM with the following additional information: - -* Azure 2FA secret: A key that is used to generate one-time passcodes for MFA. - -As you complete the following steps, make note of the values of the items described in the preceding tables. You will need to enter these values during onboarding to access your Aha.io instance from SaaS Security. - -2. Identify the Okta user account that SaaS Security will use to access your Aha.io instance. The user account must be assigned to both the Account and Billing administrator roles in Aha.io. -3. Get a secret key for MFA. The steps you follow to get the MFA secret key differ depending on the identity provider you're using to access the account. -4. (For Okta log in) To access the account through Okta: - 1. Identify your Okta subdomain. - 2. Generate and copy an MFA secret key. -5. (For Microsoft Azure log in) To access the account through Microsoft Azure: - 1. Enable third-party software OATH tokens for the administrator account. - 2. Configure the account for MFA and copy the MFA secret key. - 3. Make note of your organization's Aha.io instance host name. - -After you log in to Aha.io, the instance host name is a unique subdomain included in the Aha.io URL. The URL format is \<instance\_host>.aha.io. - -4. Connect SaaS Security to your Aha.io instance. - 1. Log in to Cortex. - 2. Select **Modules > SaaS Security > Add Data Source**. You can use the Search bar to find the app you wish to connect to. - 3. Click the Aha.io tile. - 4. Under **Capabilities**, Enter a Name for your application. - 5. Select Security Posture under Default Capabilities and click Next. - 6. Under **Connections**, provide the Tenant ID, Client ID, and Client Secret. - 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.
-
▸ ▾ Aha! modified +44 −1 Gains a Prerequisites section on Okta or Azure MFA secrets and admin roles, plus a Configure Aha! step naming Tenant ID, Client ID and Client Secret.
xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/vendor-specific-data-sources-and-connectors/aha/ahaRead it on the Cortex docs portal ↗ Read it here → This file's diff on GitHub ↗
Before After@@ -6,9 +6,52 @@ description: Use Aha! data with Cortex XSIAM.The capabilities and sub-capabilities listed for this connector are available with any active Cortex XSIAM or Cortex Cloud Posture Security license.The capabilities and sub-capabilities listed for this connector are available with any active Cortex XSIAM or Cortex Cloud Posture Security license.This connector includes the following capabilities and sub-capabilities (if applicable):This connector includes the following capabilities and sub-capabilities (if applicable):• Security Posture: Detect, monitor and alert on settings of your SaaS application.• Security Posture: Detect, monitor and alert on settings of your SaaS application.• saas-posture-config-remediation: Help remediate the misconfigured security settings of your SaaS application.• saas-posture-config-remediation: Help remediate the misconfigured security settings of your SaaS application.To configure this connector, follow the steps outlined in the configuration wizard.### PrerequisitesComplete the steps below on your Aha! instance to connect with Cortex.Cortex connects to your Aha! instance using Okta SSO or Microsoft Azure credentials that you provide during the connection process. For this reason, your organization must be using Okta or Microsoft Azure as an identity provider. The Okta or Microsoft Azure account must be configured for multi-factor authentication (MFA) using one-time passcodes.\\Cortex logs in to Aha! instance using administrator account credentials. This account is used to scan your Aha! instance for misconfigured settings. If there are misconfigured settings, Cortex suggests a remediation action based on best practices.To onboard your Aha! instance, complete the following actions:1. Collect information for accessing your Aha! instance.To access your Aha! instance, you will need the following information, which you will specify during the onboarding process:1. User email: The login email address of the account that SSPM will use to access your Aha! instance. Required Permissions: The user account must be assigned to both the Account and Billing administrator roles in Aha!.2. Password: The password for the login account.3. Instance Host: The custom domain for accessing your organization's Aha! account. You specify this domain when you sign up for an Aha! account, and it is included as part of the URL that you use to access the account.If you're logging in through Okta, you must provide SaaS Security with the following additional information:• Okta subdomain: The Okta subdomain for your organization. The subdomain was included in the login URL that Okta assigned to your organization.• Okta 2FA secret: A key that is used to generate one-time passcodes for MFA.If you're using Azure Active Directory (AD) as your identity provider, you must provide Cortex with the following additional information:• Azure 2FA secret: A key that is used to generate one-time passcodes for MFA.As you complete the following steps, make note of the values of the items described in the preceding sections. You will need to enter these values during onboarding to access your Aha.io instance from SaaS Security.1. Identify the Okta user account that SaaS Security will use to access your Aha! instance. The user account must be assigned to both the Account and Billing administrator roles in Aha.io.2. Get a secret key for MFA. The steps you follow to get the MFA secret key differ depending on the identity provider you're using to access the account.1. To access the account through Okta:1. Identify your Okta subdomain.2. Generate and copy an MFA secret key.2. To access the account through Microsoft Azure:1. Enable third-party software OATH tokens for the administrator account.2. Configure the account for MFA and copy the MFA secret key.3. Make note of your organization's Aha.io instance host name.After you log in to Aha!, the instance host name is a unique subdomain included in the Aha! URL. The URL format is <instance_host>.aha.io.### Configure Aha!Once you have setup your Aha! instance, follow the steps outlined in the Cortex Aha! data connector configuration wizard to complete the connection process. Provide the Tenant ID, Client ID, and Client Secret, of your Aha! instance, under the Connections step when prompted.Show markdown source
@@ -6,9 +6,52 @@ description: Use Aha! data with Cortex XSIAM. The capabilities and sub-capabilities listed for this connector are available with any active Cortex XSIAM or Cortex Cloud Posture Security license. This connector includes the following capabilities and sub-capabilities (if applicable): * Security Posture: Detect, monitor and alert on settings of your SaaS application. * saas-posture-config-remediation: Help remediate the misconfigured security settings of your SaaS application. -To configure this connector, follow the steps outlined in the configuration wizard. +### Prerequisites + +Complete the steps below on your Aha! instance to connect with Cortex. + +Cortex connects to your Aha! instance using Okta SSO or Microsoft Azure credentials that you provide during the connection process. For this reason, your organization must be using Okta or Microsoft Azure as an identity provider. The Okta or Microsoft Azure account must be configured for multi-factor authentication (MFA) using one-time passcodes.\ +\ +Cortex logs in to Aha! instance using administrator account credentials. This account is used to scan your Aha! instance for misconfigured settings. If there are misconfigured settings, Cortex suggests a remediation action based on best practices. + +To onboard your Aha! instance, complete the following actions: + +1. Collect information for accessing your Aha! instance. + + To access your Aha! instance, you will need the following information, which you will specify during the onboarding process: + + 1. User email: The login email address of the account that SSPM will use to access your Aha! instance. Required Permissions: The user account must be assigned to both the Account and Billing administrator roles in Aha!. + 2. Password: The password for the login account. + 3. Instance Host: The custom domain for accessing your organization's Aha! account. You specify this domain when you sign up for an Aha! account, and it is included as part of the URL that you use to access the account. + +If you're logging in through Okta, you must provide SaaS Security with the following additional information: + +* Okta subdomain: The Okta subdomain for your organization. The subdomain was included in the login URL that Okta assigned to your organization. +* Okta 2FA secret: A key that is used to generate one-time passcodes for MFA. + +If you're using Azure Active Directory (AD) as your identity provider, you must provide Cortex with the following additional information: + +* Azure 2FA secret: A key that is used to generate one-time passcodes for MFA. + +As you complete the following steps, make note of the values of the items described in the preceding sections. You will need to enter these values during onboarding to access your Aha.io instance from SaaS Security. + +1. Identify the Okta user account that SaaS Security will use to access your Aha! instance. The user account must be assigned to both the Account and Billing administrator roles in Aha.io. +2. Get a secret key for MFA. The steps you follow to get the MFA secret key differ depending on the identity provider you're using to access the account. + 1. To access the account through Okta: + 1. Identify your Okta subdomain. + 2. Generate and copy an MFA secret key. + 2. To access the account through Microsoft Azure: + 1. Enable third-party software OATH tokens for the administrator account. + 2. Configure the account for MFA and copy the MFA secret key. + 3. Make note of your organization's Aha.io instance host name. + +After you log in to Aha!, the instance host name is a unique subdomain included in the Aha! URL. The URL format is \<instance\_host>.aha.io. + +### Configure Aha!  + +Once you have setup your Aha! instance, follow the steps outlined in the Cortex Aha! data connector configuration wizard to complete the connection process. Provide the Tenant ID, Client ID, and Client Secret, of your Aha! instance, under the **Connections** step when prompted.