Integrating SailPoint with Mimecast Incydr
Mimecast Incydr (formerly Code42 Incydr) is a SaaS data loss protection and insider risk platform. Administrators manage users, roles, organisations, and security events from the Incyder console, and the same entities are exposed through Code42's REST API. This document provides instructions to configure a new direct connection to a Mimecast Incydr 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 Mimecast Incydr connector supports the following:
Account Management
- Aggregate Accounts (Users)
Entitlement Management
- Aggregate Roles
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 Mimecast Incydr tenant with administrator-level access. The user creating the API client must hold a role that authorizes user-management API access for the target organization.
- Supported authentication type: OAuth 2.0 Client Credentials grant.
- An API client must be registered in the Mimecast Incydr console (under the API clients management area) to obtain the
client_idandclient_secret. - For more information about API client registration, refer to the Mimecast Incydr API clients documentation.
Required Permissions
- API credentials for Mimecast Incydr are issued as a
client_id/client_secretpair from a registered API client in the Mimecast Incydr console. There is no separate “service account” object. - The API client itself is the service identity. It is recommended to provision a dedicated API client for the SailPoint integration rather than reusing one created for other automations.
- The API client must be created by, or assigned to, an administrator-tier user in the Mimecast Incydr tenant. Non-administrator users cannot mint API client credentials that authorize user-management API calls.
- The API client must have the
user:readandorg:readpermissions in order to fetch all users and roles properly. - A correct regional base URL (
https://api.us.code42.com,https://api.us2.code42.com,https://api.ie.code42.com, orhttps://api.gov.code42.com) matching the Mimecast Incydr console domain in use. - For more information about API authentication and configuration, refer to the following resources:
Note
The linked document is not maintained by SailPoint and is subject to change without notice.