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 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 |
|---|---|---|
| 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 |
|---|---|
| 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. |
Documentation Feedback
Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.