IAM, IGA & Identity Security

IAM sets up the employee's account so they can log in and access the application with their credentials.

IGA makes sure that access requests go through the proper channels—meaning they need to be formally requested, approved by a manager, and reviewed regularly (like during those quarterly access checks). It also keeps things in check if an employee switches departments or leaves the company, making sure their access is updated or revoked quickly.

Identity Security keeps an eye on employee activity to spot anything unusual, such as logging in from different locations at the same time or accessing sensitive info at odd hours. If something seems off, it’ll trigger alerts or ask for extra verification when needed.

SailPoint Path

Identity University Blog:
https://community.sailpoint.com/t5/Identity-University-Blog/bg-p/identity-university-blog

Identity University - Identity Security Cloud:
https://community.sailpoint.com/t5/Identity-University-Identity/gh-p/identity-university-isc

Glossary

Identity Security : 

# Identity security is the ability to get the right access at the right time for the right individuals.

# Identity security is the identification, authorization, and authentication of users.

# Identity security protects the organization.

Simply put...

Identity security

is all about giving the right identities

the right access,

to the right stuff,

at the right time,

to do their job.

IAM : This framework ensures the right identities can access an organization's data and resources based on business processes, policies, and technologies.

IGA : This framework allows organizations to verify that the right controls are in place to meet the security and privacy requirements of regulations like SOX, HIPAA, and GDPR.

SailPoint - Certification

 To help you navigate your SailPoint journey, I’ve outlined the recommended order for taking the certifications below.

1. Identity Security Leader Credential

Cost : Free (Includes 2 attempts)

Format : Non-proctored

Prerequisite : Must complete all related training modules before the final exam.

Who it’s for : This is a general credential (not role-based) designed to give anyone a foundational understanding of SailPoint.

Link : https://university.sailpoint.com/path/identity-security-leader

2. Identity Security Professional Credential

Cost : Free (Includes 2 attempts)

Format : Non-proctored

Prerequisite : Training completion required.

Who it’s for : A general credential that builds confidence before moving on to the paid, proctored exams. 

Link : https://university.sailpoint.com/path/identity-security-administrator/sailpoint-identity-security-professional-credential

3. Identity Security Administrator

Cost : Paid

Format : Proctored

Prerequisite : Training completion required.

Who it’s for : Specifically designed for those in Administrator or Support roles. 

Link: https://university.sailpoint.com/path/identity-security-administrator

4. Identity Security Expert Credential

Cost : Free (Includes 2 attempts)

Format : Non-proctored

Prerequisite : Training completion required.

Who it’s for : Another great stepping stone to help you prepare for the advanced paid certifications.

Link :https://university.sailpoint.com/path/identity-security-engineer

5. Identity Security Engineer

Cost : Paid

Format : Proctored

Prerequisite : Training completion required.

Who it’s for : This is the final certification in this track, specifically tailored for Developers. 

Link :https://university.sailpoint.com/path/identity-security-engineer

Important Note:

The Administrator and Engineer certifications require hands-on experience. I highly recommend attempting these only if you have practical project experience. That said, our internal training program is comprehensive enough to fully prepare you for the Engineer exam. You can directly take Engineer cert as well.

ISC-File Upload Utility

Reference:-

https://community.sailpoint.com/t5/Professional-Services/SailPoint-File-Upload-Utility/ta-p/76392

https://developer.sailpoint.com/discuss/t/file-upload-utility/18181

Which actions or operations cannot be performed through the ISC UI?

 # Optimization

# Lifecycle State deletion

Lifecycle State

# Lifecycle states can be managed through the UI; however, deletion of lifecycle states is not supported via the UI. Deletion can be performed using VS Code or Postman.

# Lifecycle states can be validated through Access History (up to 18 months) or via Events.

# All lifecycle states can be implemented within a single transform.

Optimization

 

Account Aggregation

 

ISC Postman Set up

 High-Level Steps:-

# Download and install the postman.

# Navigate to the home icon and click on a Workspace.

# Click on a create Workspace.

# Create an Environment

•     Configure the variables (clientId, clientSecret, tenant) in the Environment.

# Create a Collection

•     Configure the variable (domain) in the collection.
•     Configure the Authorization for child API's to connect ISC tenant
•     Select the Authentication type as OAuth 2.0

# Configure New Token

•         Select the Grant Type as Client Credentials
•         Provide the Access Token URL : https://{{tenant}}.api.identitynow-demo.com/oauth/token
•         Configure the tenant using an Environment variable
•         Reference    :    https://developer.sailpoint.com/docs/api/authentication
•         https://[tenant].api.identitynow.com/oauth/token
•         Configure the Client ID using an Environment variable
•         Configure the Client Secret using an Environment variable

# Click on Get New Access Token, then select Use Token to enable usage for child APIs.

ISC VSC Code Set up

High-Level Steps:-

# Download and install the Visual Studio Code (VSC).

# Navigate to the Extensions icon, located at the center of the left-hand panel.

# Search with "sailpoint identity sec" and look for the author Yannick.

# Open the "SailPoint Identity Security Cloud for Visual Studio Code" and click on setting icon for install specific version selection.

# Select the version to install - 1. 3. 29

#The ISC tenant will be added automatically; if it is not, restart Visual Studio Code.

# Navigate to the ISC extension icon, click on Add tenant.

# Provide the following details:

    tenant name (Ex: Tenant + domain),

    display name (Ex: Tenant + domain),

    Select the AuthN method as PAT, then provide the clientId & clientSecret.

# The tenant is configured as read-only by default; update the setting to writable for a sandbox environment.