Showing results for 
Show  only  | Search instead for 
Did you mean: 

SailPoint AuditEvent Integration for Amazon Security Lake - Setup and User Guide

SailPoint AuditEvent Integration for Amazon Security Lake - Setup and User Guide

The Open Cybersecurity Schema Framework (OCSF) is an open-source effort to facilitate interoperability of cybersecurity data across platforms and tools by establishing a standardized schema for common security events and defining a collaborative governance process for security log producers and consumers. The SailPoint Identity Security Cloud AuditEvent Integration for Amazon Security Lake is designed to provide customers the ability to extract audit information from an Identity Security Cloud tenant, transform those events into an OCSF schema, and store the data in an Amazon Security Lake. 






The integration utilizes a set of cloud based AWS resources to automate the process of delivering audit event data in an OCSF compliant schema to an Amazon Security Lake custom source location. The components included in this integration are:

Lambda Package: contains a python script, libraries, and json mapping data files for transforming audit events from the Identity Security Cloud API to an OCSF compliant schema.

Glue ETL script: is a Python script that transforms the json output provided by the Lambda function into a parquet format for storage in Amazon Security Lake.

CloudFormation template: cloudformation.yaml is provided to build the AWS resource stack. 


Process Flow

  1. Schedule event using Amazon EventBridge to periodically execute integration process.
  2. Event triggers invocation of Lambda function which calls SailPoint Identity Security Cloud API to retrieve event data since last timestamp.
  3. Events are translated to OCSF schema and stored as JSON data in Amazon S3 storage.
  4. JSON data is crawled by Amazon Glue to populate the Glue catalog with SailPoint Identity Security Cloud schema extensions represented as OCSF.
  5. Amazon Glue ETL job converts JSON to Apache Parquet
  6. Files are stored in Amazon Security Lake

AuditEvent Transformation to OCSF

AuditEvents in Identity Security Cloud represent "things of interest" that occur during the normal day to day operations of Identity Security Cloud. The AuditEvent types supported for transformation into OCSF can be found in ocsf_map.json. Each top level key in the file is named for the "type" value associated with a  "_type": "event". The key-value pairs nested in "staticValues" include the settings for identifying the OCSF schema that each event of that type will be transformed into. 

It should be noted that the intention behind this integration is not to capture every event from Identity Security Cloud, but rather a selection of events which apply to an OCSF class and category. Only top level keys in ocsf_map.json that match event values in "type": "event" will be captured by this process. The ocsf_map.json file can be inspected in this integrations GitHub repository

Event Types

OCSF Schema Category

OCSF Schema Class 

Metadata Version


Audit Activity




Audit Activity

Account Change



Audit Activity

Account Change



Audit Activity




Audit Activity

Account Change



System Activity

Scheduled Job Activity



Integration Setup


Prior to beginning the setup process for this integration an Amazon Security Lake account must be enabled and custom sources must be setup. For an overview please see the Amazon Security Lake Getting Started guide and Collecting data from custom sources.

The CloudFormation process should be performed by an AWS administrator. For more about CloudFormation see What is AWS CloudFormation?

The integration requires the use of a Personal Access Token from your Identity Security Cloud tenant. It is recommended that when using the 'client_credentials' mechanism with a Personal Access Token, that a service account is created in Identity Security Cloud for this process. These credentials are saved in an SSM Parameter and a Secret manager resource during the CloudFormation process. 

Step 1: Custom Sources Setup

1. Open the Amazon Security Lake console

2. Click on Custom Sources in the left navigation menu.



3. Click the Create custom source button.



4. In Custom source details enter the following information:

  • Data source name: sailpoint-auth *
  • OCSF Event Class: Authentication


5. In Account details enter the following information:

    • AWS account ID: The AWS Account ID where the SailPoint integration resource stack will reside (this can be the same account that Security Lake resides or any other AWS account)
    • External ID: Must be “SailPoint_” followed by the tenant name associated with your Identity
  • Identity Security Cloud Tenant (https://{SailPointTenantName}


6. In Service Access choose “Create and use a new service role”

7. Click the Create button

8. Repeat this process 2 more times for the following Data Source Names and Event Classes:

  • Data source name: sailpoint-acct-chng*
  • OCSF Event Class: Account Change
  • Data source name: sailpoint-sched-job*
  • OCSF Event Class: Scheduled Job Activity

*It is important that these data source names are input exactly as provided for the integration to function properly.



Step 2: Identity Security Cloud OAuth2.0 Configuration

A personal access token is required to generate access tokens to authenticate API calls. See this guide for instructions on how to generate a personal access token.

Note: When you setup your personal access token, be sure to enable the scope ‘sp:search:read’ and only this scope.

Save your Client ID and Client Secret for use during the Cloud Formation process.

Screenshot 2023-09-11 at 17.16.24.png


Step 3: AWS CloudFormation

AWS CloudFormation handles the provisioning of a resource stack. This integration includes cloudformation.yaml which is a template specifically designed to provision all of the resource components necessary to enable the integration. We recommend using this template to provision AWS resources.

To obtain the CloudFormation template visit the GitHub repository release page and download cloudformation.yaml from release 1.0.0. The template provisions the following resources:


Logical ID





Lambda function to copy source code from GitHub to S3.



Used by SailPointGlueCrawler to collect metadata from json audit event data.



Grants permission for Glue to use a database to store and access metadata collected by a Crawler.



Grants permission for a Glue Crawler to collect metadata from json audit event data.



Gives Lake Formation permission to use a service linked role to access json log data.



Database to store audit event data temporarily before it is transformed from json to parquet.



Custom code used by CopyFilesToS3 Lambda function.



Gives CopyFilesToS3 Lambda function permission to write files to SourceCodeS3Bucket.



Collects metadata from json audit event data, needed for parquet file conversion.



Runs the code in to transform data from json to parquet.



Grants permission for SailPointLambdaFunction to assume roles created during custom source creation.



Grants various permissions for SailPointLambdaFunction on SailPointOCSFGlueCrawler, OCSFDatabase, SailPointSSMParameter and TempFileS3Bucket



This is the main function that will execute the data ETL process.



Grants permission for Glue resources on TempFileS3Bucket, SourceCodeS3Bucket and Lake Formation



This parameter is used to store the date/time of the last event captured from the Identity Security Cloud API.



This resource is used to store the Identity Security Cloud personal access token Client Secret value.



A bucket used to store code used by SailPointGlueETLJob and SailPointLambdaFunction



Temporary storage for transformed audit events in json format


CloudFormation Configuration

1. Open the CloudFormation console.

2. In the top right corner click the Create Stack button and choose With new resources (standard).


3. On the Specify template section choose Upload a template file.

4. Click the Choose file button and browse to the cloudformation.yaml file provided, then click Next.


5. In the Stack name section choose a name for this resource stack (For example, SailPointResourceStack).


6. Review the Parameters section carefully. Some values have been provided as default values that you can change to fit your needs. Values are required for each parameter. (See the CloudFormation Parameters table below for detailed instructions)



7. No changes are required for the Configure stack options settings. These settings can be altered according to your preferences. When your review is complete, click Next. 

8. The last screen will be for review and acknowledgement. When you scroll down to the bottom you will see an information box indicating that the template contains IAM resources. You must acknowledge this in order to proceed. Click the acknowledgment check box, then click Submit. 




CloudFormation Parameters

Parameter Name Definition Instructions

Provider Role ARN associated with the Amazon Security Lake custom Source name sailpoint-acct-chng.

This should be copied from your Security Lake console.

  • Open your Security Lake console.
  • Select Custom sources from the navigation menu
  • Copy the value in the Provider role ARN column associated with the Custom source name sailpoint-acct-chng
AuthenticationExecutionRole Provider Role ARN associated with the Amazon Security Lake custom Source name sailpoint-auth.

This should be copied from your Security Lake console.

  • Open your Security Lake console
  • Select Custom sources from the navigation menu
  • Copy the value in the Provider role ARN column associated with the Custom source name sailpoint-auth

Number of events to request from SailPoint API during each run (10000 max)

This value can be changed at any time in Configuration -> Environment Variables -> MaxEventsFromAPI for the SailPointOCSFLambdaFunction Lambda function. 

Personal Access Token ClientID value

The ClientID from the Personal Access Token you created in your Identity Security Cloud Tenant (from Step 2)

Personal Access Token Client Secret value


The Client Secret from the Personal Access Token you created in your Identity Security Cloud Tenant (from Step 2)

SailPointTenantName The tenant name associated with your Identity Security Cloud Tenant  https://{SailPointTenantName}

Provider Role ARN associated with the Amazon Security Lake custom Source name sailpoint-sched-job

This should be copied from your Security Lake console.

  • Open your Security Lake console.
  • Select Custom sources from the navigation menu.
  • Copy the value in the Provider role ARN column associated with the custom source name sailpoint-sched-job.
SecurityLakeAccountID Target AWS Account ID for Amazon Security Lake data Enter the AWS Account ID associated with your Amazon Security Lake configuration. This is the account that has your custom sources configured.
SecurityLakeDatabaseName The name of the database for Amazon Security Lake data. 

 This value can be found in your AWS Lake Formation console.

  • Open your Security Lake console.
  • Select Summary from the navigation menu.
  • Select Lake formation database from the Quick links section.
  • Copy the database name from the Database details section.

The External ID associated with each Amazon Security Lake custom source. 

This must be set to same value that was used for External ID when you setup your custom sources.

SecurityLakeS3Bucket Name of the S3 bucket where your Amazon Security Lakes Custom Source data is stored. 

This should be copied from your Security Lake console.

  • Open your Security Lake console.
  • Select Regions from the navigation menu.
  • Click on the S3 location associated with the region where your custom source is hosted.
  • Copy the bucket name at the top of the page (should start with “aws-security-data-lake”)



1. From the CloudFormation stacks screen click on the name of your stack and select the Resources tab.

2. Click the link to SailPointOCSFLambdaFunction in the Physical ID column.

3. Click on the Test tab, then click on the Test button. You will see the Executing Function message in the information dialog box. Depending on the value you specified for MaxEventsFromAPI the operation will take from 5 to 10 minutes to complete. You can click on Details to see a summary of the operation after completion. EricPanico_4-1696365350721.png

4. Open your S3 console and browse to the location for your Security Lake custom source data. You should see one folder for each of the OCSF custom sources you created. Within each folder you should see the following hierarchy representing the partitioned data:


5. Check one of the eventDay folders for the parquet file data left by the script. Select the checkbox next to one parquet file, then select Query with S3 select from the Actions menu. EricPanico_6-1696365350736.png
6. In the Input settings section make sure Apache Parquet is selected.  EricPanico_7-1696365350737.png
7. In the Output settings section select JSON Format. EricPanico_8-1696365350738.png

8. In the SQL query section, use the default query to select 5 records from the file.

9. Click the Run SQL query button. You should see 5 events converted to the OCSF schema*



* You should notice that the first object in each record named “data” contains the original source record from the SailPoint API. “data” is an optional JSON object provided in the OCSF v1.0.0-rc.2 schema that has been chosen to use to store the original event data and schema for reference.

Schedule the Lambda Function

We recommend running the Lambda function (SailPointLambdaFunction) at intervals no more frequent than once every hour. You can use Amazon EventBridge to accomplish this. See Tutorial: Schedule AWS Lambda functions using EventBridge



Thank you for sharing.

Version history
Revision #:
15 of 15
Last update:
‎May 02, 2024 04:24 PM
Updated by: