# SailPoint Elevate Security Connector Documentation > Elevate Security Connector Documentation # Documentation # Connecting SailPoint and Elevate Security To connect SailPoint with Elevate Security, perform the following tasks: ## Adding the Source in SailPoint To connect to SailPoint, perform the following steps. Once the connection is made, you can configure it to meet your company's needs. > [!IMPORTANT] > > By default, the provisioning feature is **disabled**, and the connector only supports read-only operations. To support provisioning operations, you must manually enable the feature in the source configuration. **To configure a new source:** 1. Sign in to SailPoint. 2. Go to **Admin \> Connections \> Sources**. 3. Select **Create New**. 4. Search for the connector by entering the name in the search box, and then select **Actions**. 5. In the **Actions** dropdown list, select the setup method: - [**Express Setup**](<#configuring-a-source-using-express-setup>) - Quickly create a read-only connection to your target system by providing minimal configurations and authentication. On completion, aggregation is automatically started. > **Note** > > Express Setup supports Credential Providers. For information on supported credential providers and configuration, refer to [Credential Providers](). For more information, contact your SailPoint Customer Service Manager. - [**Standard Setup**](<#configuring-a-source-using-standard-setup>) - Provide detailed basic configuration to create the source. Once the source is created, continue with source setup. ### Configuring a Source Using Express Setup Express Setup minimizes the initial configuration process so you can quickly connect the application and immediately begin aggregating user account and entitlement data. 1. Review the directions and select **Start Express Setup**. 2. Review the pre-populated **Source Name**, **Source Owner**, and **Description**. To update, select **Edit**. > **Note** > > The source name must be unique. You can change these settings later in the source configuration. 3. (Optional) If enabled for your organization, select the **Use a Credential Provider** checkbox to manage the source's authentication using a credential provider. > **Note** > > To add a Credential Provider in SailPoint, go to **Admin \> Connections \> Credential Providers**. For more information about credential providers, refer to [Credential Providers](). 4. Configure the authentication to allow SailPoint to connect to the source. For more information, refer to the **Connection Settings** section. 5. Select **Finish**. After a successful test connection, the system creates your source and prompts you to run an aggregation. - If you want to aggregate now, select **Aggregate**. - To see the latest account aggregation history, go to **Account Management \> Account Aggregation**. - To see the list of aggregated source accounts, go to **Account Management \> Accounts**. - If you want to aggregate later, select **Exit**. This returns you to the **Sources** page. Your new source is listed, but contains no accounts or aggregation history yet. ### Configuring a Source Using Standard Setup Use Standard Setup to configure the connector for full feature support. 1. In the **Source Name** field, enter a unique and descriptive name for your source. Source names cannot exceed 128 characters. 2. In the **Description** field, provide additional details about the source to help distinguish it from similar sources. This field allows a maximum of 2,000 characters. 3. In the **Source Owner** field, begin typing the name of an owner. Matches appear after you type two or more letters. For more information, refer to [Assigning a Source Owner](). 4. (Optional) Select a governance group to grant its members [source]() or [role]() sub-admin level oversight of the source and its access. For more information, refer to [Creating and Managing Governance Groups](). 5. If this source represents a primary system containing your organization's personnel records, select the **Authoritative Source** checkbox. For more information, refer to [Creating Identity Profiles](). 6. Select **Continue**. The source is created, and you are navigated to the **Source Setup \> Base Configuration** page. Continue to configure your connected source there. ## Base Configuration Provide the base configuration parameters. Information you entered in the Create New Source dialog is automatically entered into the fields in the Base Configuration page. You can edit this information if necessary. 1. Enter a unique name and description for the source. 2. In the **Source Owner** dropdown list, select the identity that owns this source. - To find a source owner, begin entering their name. 3. (Optional) If enabled for your organization, select the **Use a Credential Provider** checkbox to manage the source's authentication using a credential provider. > **Note** > > To add a credential provider, go to **Admin \> Connections \> Credential Providers**. For more information about credential providers, refer to [Credential Providers](). 4. Configure the authentication to allow SailPoint to connect to the source. Refer to [Connection Settings](<#connection-settings>) for more information. 5. (Optional) In the **Governance Group for Source Management** dropdown list, select a governance group to associate with this source. For more information about governance groups, refer to [Associating Governance Groups with a Source](). 6. (Optional) Choose whether to enable or disable provisioning for the source. Provisioning is disabled by default. - **Enable Provisioning** - Set the toggle to **Enabled** to allow the source to create, update, and deactivate accounts in the connected source system. - **Disable Provisioning** - Set the toggle to **Disabled** to disable provisioning for the source. Disabling provisioning will prevent the creation, updating, or deactivating of accounts on this source. 7. Select **Save**. ## Connection Settings The following information is required to connect and interact with Elevate Security. > [!NOTE] > > **Screenshot** > > [![Connection Settings]()]() 1. Enter the **Organization API Key** for the Elevate Security tenant. 2. In the **Organization Shortname** field, enter the Elevate Security subdomain that you authenticate to. For example, if your subdomain is `https://sailpoint.elevatesecurity.com`, then you would enter `sailpoint`. 3. Select **Save**. ## Aggregation Settings Configure settings related to account aggregation processes. > [!NOTE] > > **Screenshot** > > [![Aggregation Settings]()]() 1. In the **Page Size** field, enter the number of records to aggregate in a single page when iterating over large datasets. The minimum allowed value is 250 records, and the maximum value is 1000 records. The default is 1000 records. 2. Select **Save**. ## Review and Test Perform a test to confirm the connection to SailPoint. 1. Go to **Review and Test**. 2. Confirm that the entries in each field are correct. If you note any mistakes, return to the section and make corrections. 3. Select **Test Connection**. ## SailPoint Application Onboarding SailPoint application onboarding enables you to easily onboard new applications and create sources following the successful onboarding of a discovery source. To use this feature, continue to **Discovered Applications** in the SailPoint user interface. For more information, refer to [Application Onboarding]() in the SailPoint SaaS documentation. # Integrating SailPoint with Elevate Security The Elevate Security connector aggregates risk information for identities from your Elevate Security system. This document is designed to give specific information about the requirements and fields needed to successfully configure an instance of the Elevate Security connector. > [!NOTE] > > To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes]() page. ## Supported Features The Elevate Security connector supports the following features: - Aggregation of Accounts - Single Account Aggregation - Identity Protection - Risky User Alert Feature - With the security reports in Elevate Security, you can gauge the probability of compromised user accounts in your environment. A user flagged for risk is an indicator for a user account that might have been compromised. The risky user represents the probability that a given identity or account is compromised. These risks are calculated offline using Elevate Security's internal and external threat intelligence sources. For more information on the supported Risky User Alert attributes, refer to [Account Attributes](). ## Prerequisites The following prerequisites are required: - An API key from your Elevate Security tenant. To locate your key, complete the following: 1. Log in to your Elevate Platform and select your name in the left-hand menu. 2. Select **Organization Details**. 3. Copy the value in the **Organization API Key** field. - Your organization shortname. This is the subdomain that you authenticate to. For example, `https://.elevatesecurity.com` ## Required Permissions You must have administrator access to your Elevate Security tenant to generate an API key. # Schema Reference The application schema is used to configure the objects returned from a connector. > [!NOTE] > > - The **Account Schema** tab is used to define the attributes for each object type in the application being configured. The schema attributes can be defined as **Entitlement** or **Multi-Valued**. Refer to [Managing Source Account Schemas]() for more information. > - The schema attributes that are not present by [default](<#default-account-schema>) must be defined as strings if not specified. The Elevate Security connector uses the following default correlation and object configurations. ## Default Correlation Configuration Before you aggregate accounts from this source, you can map account attributes with their corresponding identity attributes based on your requirements. You can customize the correlation configuration. Refer to [Assigning Source Accounts to Identities]() for more information. When you first create the Elevate Security source, the default correlation mapping is: | Account Attribute | Operation | Identity Attribute | | --- | --- | --- | | email | Equals | Work Email | ## Default Account Schema Each source supports a variety of details, or attributes, about each user who has an account, such as their name, email address, manager name, and location. The set of account attributes each source stores and how they're organized is known as the account's *schema*. To best represent your data, you can configure sources to use an account schema matching the one you use in the external connector. Refer to [Managing Source Account Schemas]() for more information. ### Default Account Attributes The Elevate Security connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified. | Attribute Name | Description | | --- | --- | | email | The email address of the entity. This is also used as the entity’s unique identifier. | | full\_name | The display name of the entity. For example, Firstname+Lastname | | action\_factor | Indicates the action factor. For example, `very_low`, `low`, `medium`, `high`, and `very_high` | | actions\_score | A number that indicates the action score of the entity. These are actions, good or bad, that contribute to the entity's risk level. | | actual\_phishing | A number that indicates the actual phishing score of the entity. | | alternate\_user\_id\_1 | First alternate user ID of the entity. | | alternate\_user\_id\_2 | Second alternate user ID of the entity. | | attack\_factor | Indicates the attack level that this individual is targeted or attacked for. For example, `very_low`, `low`, `medium`, `high`, and `very_high` | | human\_risk\_score | A number that indicates the human risk score of the entity. | | malware | A number that indicates the malware score of the entity. | | person\_nid | The person NID of the entity. This can also be used as an alternate unique identifier. | | secure\_browsing | A number that indicates the secure browsing score of the entity. | | sensitive\_data\_handling | A number that indicates the sensitive data handling score of the entity. | | simulated\_phishing | A number that indicates the simulated phishing score of the entity. | | training | A number that indicates the training score of the entity. | # Troubleshooting If you encounter any of the following issues or errors, SailPoint recommends that you follow the guidance provided below to resolve the error before contacting SailPoint Support. For issues or errors that are not addressed in this connector guide, refer to the following resources for troubleshooting information: - [SailPoint Identity Services Documentation]() - [SailPoint Support Knowledge Base]() - [SailPoint Developer Community]() ## Debug Logs For information about managing additional source settings, including debug logging and downloading connector logs, refer to [Managing Additional Settings](). ## Saving configuration fails with error: 'Client ID' is required and can not be less than 32 characters **Resolution**: Ensure the Client ID value is exactly 32 characters in length. Elevate Security requires that all Client ID values be exactly 32 characters in length, and the connector configuration UI enforces this requirement.