Skip to main content

SailPoint Source

The SailPoint Source provides a secure endpoint to receive Events and User Inventory data from the IdentityNow V3 API. It securely stores the required authentication, scheduling, and state tracking information.


This source is not available in the Fed deployment.

Data collected

Polling IntervalData
5 minEvents
12 hoursUsers Inventory


Vendor configuration

You need a SailPoint Admin account generated Client ID and Client Secret Key as well as the customer-specific organization name, such as {organization}

To generate a personal access token from the IdentityNow UI, perform the following steps after logging into your IdentityNow instance:

  1. Select Preferences from the dropdown menu under your username, then Personal Access Tokens on the left. You can also go straight to the page using this URL, replacing {tenant} with your IdentityNow tenant: https://{tenant}
  2. Click New Token and enter a meaningful description to help differentiate the token from others.

    The New Token button will be disabled when you’ve reached the limit of 10 personal access tokens per user. To avoid reaching this limit, we recommend you delete any tokens that are no longer needed.

  3. Click Create Token to generate and view the two components that comprise the token: the Secret and the Client ID.

    After you create the token, the value of the Client ID will be visible in the Personal Access Tokens list, but the corresponding Secret will not be visible after you close the window. You will need to store the Secret somewhere secure.

  4. Copy both values somewhere that will be secure and accessible to you when you need to use the token.

Source configuration

When you create a SailPoint Source, you add it to a Hosted Collector. Before creating the Source, identify the Hosted Collector you want to use or create a new Hosted Collector. For instructions, see Create a Hosted Collector.

To configure a Duo Source:

  1. In the main Sumo Logic menu, select Manage Data > Collection > Collection.  
  2. On the Collectors page, click Add Source next to a Hosted Collector.
  3. Search for and select SailPoint.
  4. Enter a Name for the Source. The description is optional.
  5. (Optional) For Source Category, enter any string to tag the output collected from the Source. Category metadata is stored in a searchable field called _sourceCategory.
  6. Forward to SIEM. Check the checkbox to forward your data to Cloud SIEM.
  7. (Optional) Fields. Click the +Add Field link to define the fields you want to associate, each field needs a name (key) and value.
    • green check circle.png A green circle with a check mark is shown when the field exists in the Fields table schema.
    • orange exclamation point.png An orange triangle with an exclamation point is shown when the field doesn't exist in the Fields table schema. In this case, an option to automatically add the nonexistent fields to the Fields table schema is provided. If a field is sent to Sumo that does not exist in the Fields schema it is ignored, known as dropped.
  8. Tenant Name. Provide your SailPoint customer-specific organization name, such as {organization}
  9. Client ID and Client Secret. Enter the ID and Secret you got from creating your SailPoint access token in the Vendor configuration section above.
  10. Supported APIs to collect. Select one or more of the available APIs, Events and Users.
  11. Processing Rules. Configure any desired filters, such as allowlist, denylist, hash, or mask, as described in Create a Processing Rule.
  12. When you are finished configuring the Source, click Submit.

Metadata fields

_siemVendorEvents, Users SailPointSet when Forward To SIEM is checked.
_siemProductEvents, Users SailPointSet when Forward To SIEM is checked.
_siemFormatJSONSet when Forward To SIEM is checked.
_siemEventIDEvents <technicalName>Set when Forward To SIEM is checked and specific to the API collected.
_siemDataTypeUsers InventorySet when Forward To SIEM is checked.

JSON schema

Sources can be configured using UTF-8 encoded JSON files with the Collector Management API. See Use JSON to Configure Sources for details. 

schemaRefJSON Object{"type":"SailPoint"}YesDefine the specific schema type.
sourceTypeString"Universal"YesType of source.
configJSON ObjectConfiguration objectYesSource type specific values.

Configuration Object

nameStringYesnullType a desired name of the source. The name must be unique per Collector. This value is assigned to the metadata field _source."mySource"
descriptionStringNonullType a description of the source."Testing source"
categoryStringNonullType a category of the source. This value is assigned to the metadata field _sourceCategory. See best practices for details."mySource/test"
fieldsJSON ObjectNonullJSON map of key-value fields (metadata) to apply to the Collector or Source. Use the boolean field _siemForward to enable forwarding to SIEM.{"_siemForward": false, "fieldA": "valueA"}
org_nameStringYesnullProvide your SailPoint customer-specific organization name, such as {organization}
client_idStringYesnullProvide the SailPoint client ID you want to use to authenticate collection requests.
client_secretStringYesnullProvide the SailPoint secret you want to use to authenticate collection requests.
supported_apisArray of stringsYesnullDefine one or more of the available APIs to collect: Events, and Users.
For example, for both you'd use: ["Events","Users"]

See Create processing rules using JSON.

JSON example

"name": "Sail",
"org_name": "TenantName",
"supported_apis": ["Events", "Users"],
"client_id": "********",
"client_secret": "********",
"fields": {
"_siemForward": true

Download example

Terraform example

resource "sumologic_cloud_to_cloud_source" "sailpoint_source" {
collector_id =
schema_ref = {
type = "SailPoint"
config = jsonencode({
"name": "Sail",
"org_name": "TenantName",
"supported_apis": ["Events", "Users"],
"client_id": "********",
"client_secret": "********",
"fields": {
"_siemForward": true
resource "sumologic_collector" "collector" {
name = "my-collector"
description = "Just testing this"

Download example



Click here for more information about Cloud-to-Cloud sources.

Privacy Statement
Terms of Use

Copyright © 2024 by Sumo Logic, Inc.