Skip to content

Integrating SailPoint with Kentik

Kentik is a network observability platform that ingests flow telemetry, BGP, SNMP, synthetic test, and cloud-flow data to give organisations real-time visibility into network performance and security. Administrators rely on Kentik to manage user access to dashboards, alerts, RBAC roles, and the underlying APIs that drive automation around traffic analytics. This document provides instructions to configure a new direct connection to a Kentik source. For a reference to the terminology specific to SailPoint products, refer to Source and Connector Definitions.

Note

To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the SaaS Release Notes page.

Supported Features

The Kentik connector supports the following:

Account Management

  • Aggregate Users

Important

Quick Compliance connectors have the following manual aggregation limits within a 24-hour period:

  • Organization Admins: Limited to 3 manual account or entitlement aggregations per day per source. This limit is cumulative across all admins in the organization.
  • Regular Users: Limited to 1 manual account or entitlement aggregation per day per source.

These limits ensure that individual compliance statuses are kept up to date while maintaining continuous compliance monitoring. If you need to run additional aggregations beyond these limits, contact SailPoint Support.

Prerequisites

Ensure the following prerequisites are met before proceeding with the configuration:

  • A Kentik tenant with administrator-level access.
  • The user generating the API token must already be a member of the Kentik organization with required user access.
  • The user’s API token.
  • For more information about authentication and API token generation, refer to the following resources:

Required Permissions

  • API credentials in Kentik are minted per Kentik user account from that user’s Profile page in the Kentik Portal.
  • There is no separate “service account” object. It is recommended to provision a dedicated Kentik user (for example, an automation/service identity) and use that user’s email and API token rather than a human’s personal credentials.
  • The owning user must have a role that grants visibility of all users in the organization. Based on the roles surfaced by Kentik’s User API (for example, ROLE_ADMINISTRATOR, ROLE_SUPER_ADMINISTRATOR), an administrator-tier role is required; a viewer-level role will not return the full user list.
  • For more information about authentication, RBAC, and user permissions, refer to the following resources:

Note

The linked document is not maintained by SailPoint and is subject to change without notice.