Send SailPoint Identity Security Cloud logs to LogPulse
SailPoint audit events: sign-ins, access requests and approvals, provisioning, certifications and admin changes.
Configure → Sources → Cloud. LogPulse reads the SailPoint search API itself, without an agent. Events land in the iam index with source sailpoint and fill the Authentication, Change data models.Overview
- SailPoint search API to Integration poller
- Integration poller to index=iam
LogPulse signs in to SailPoint Identity Security Cloud with the credential you give it and fetches new events every five minutes by default. You can set the interval per integration, from one minute to 24 hours.
What you need
- A personal access token or API client with sp:search:read
- In LogPulse: a role that may manage API keys. Cloud integrations fall under that right.
1. Create a credential in SailPoint Identity Security Cloud
| Field in LogPulse | Where you find it |
|---|---|
| Tenant | The address you sign in to SailPoint with, such as acme.identitynow.com. |
| Client ID | A personal access token (Preferences, Personal Access Tokens) or an API client with the scope sp:search:read. |
| Client secret | Stored encrypted and never shown again. |
2. Add the integration in LogPulse
Go to Configure → Sources → Cloud and choose SailPoint Identity Security Cloud. Fill in the fields, tick the data sources you want and save. LogPulse first tests the connection with your credential and tells you what is wrong when it fails.
What arrives
| Data source | Index | Source | Sourcetype | What it holds |
|---|---|---|---|---|
| Audit events | iam | sailpoint | sailpoint_identitynow | Every audit event: who, on whom, which action and whether it passed. Sign-ins use the Authentication data model. |
The index is the kind of data and the source is the product, so detection rules for that kind of data find SailPoint Identity Security Cloud without changes.
Fields and data models
| Data model | What you get |
|---|---|
| Authentication | Sign-ins with user, src_ip and result. |
| Change | Access and provisioning changes with actor, target and action. |
Field names follow the CIM field names. These are the fields LogPulse sets on SailPoint Identity Security Cloud events; a field is left out when SailPoint Identity Security Cloud did not send a value.
actionappdest_useridobjectobject_categoryoperationsignaturesrc_ipstatustracking_numberuservendor_action
The original record of SailPoint Identity Security Cloud is kept with each event under raw, so nothing the vendor sent is lost.
3. Check the data
The first events arrive within a few minutes. Check what came in:
earliest=-1h index IN (iam) source IN (sailpoint)
| stats count by index, source, sourcetypeThe integration page in LogPulse shows when it last read events and the last error, if any.
Troubleshooting
The connection test names what is wrong. These are the answers you are most likely to see.
| What you see | What to do |
|---|---|
| SailPoint refused the client id and secret. | Create a new personal access token or API client and copy both values. The secret is shown only once. |
| The API client cannot search events. It needs the sp:search:read scope. | Add the scope sp:search:read to the token or API client. |
| tenantUrl is your tenant, e.g. acme.identitynow.com | Use the address you sign in to SailPoint with. |
| The test passes but no events arrive. | Run the search above over a longer time. No results: check on the integration page that the data source is switched on and when it last read events. SailPoint Identity Security Cloud may also simply have had nothing new. |
Frequently asked questions
- How do I send SailPoint Identity Security Cloud logs to LogPulse?
- Add the SailPoint Identity Security Cloud cloud integration under Configure, Sources, Cloud in LogPulse and fill in Tenant, Client ID, Client secret. LogPulse reads the SailPoint search API itself, every five minutes by default; there is nothing to install.
- Which permissions does LogPulse need in SailPoint Identity Security Cloud?
- A personal access token or API client with sp:search:read. Read access is enough for collecting logs.
- Which index does SailPoint Identity Security Cloud data go to?
- The index is the kind of data: iam. The source is the product: sailpoint. Each data source has its own sourcetype, listed on this page.
- Which data models does SailPoint Identity Security Cloud fill?
- Authentication, Change. Detection rules and dashboards written for a data model work on SailPoint Identity Security Cloud without changes.
- Why do SailPoint events arrive five minutes late?
- SailPoint makes audit events searchable a little after they happen. LogPulse reads five minutes behind real time so that it does not miss them.