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.

ISC PAT Generation

 High-Level Steps:-

# Login to SailPoint ISC tenant.

# Navigate to your profile/name, it is available on leftside topmost.

# Navigate to Personal Access Tokens

# Click on New token

# Provide the name of the token, remove the expiration date,  and give the scope is sp:scopes:all

# Click on create

# PAT contains Secret and Client ID

Note: 

Any user with admin access to the tenant can create up to 10 tokens.

PAT - Personal Access Token

Sailpoint ISC URL's & Paths

ISC Tenant URL :
https://{{tenant}}.{{domain}}/login/login/?brand=default

ISC Docs:
https://documentation.sailpoint.com/saas/help/index.html

ISC Glossary URL:
https://documentation.sailpoint.com/saas/help/common/glossary.html

ISC Developer Community URL: 
https://developer.sailpoint.com/docs/

ISC Postman Setup URL:
https://developer.sailpoint.com/docs/api/postman-collections
https://www.postman.com/sailpoint/identitynow/overview
Token URL : https://[tenant].api.identitynow.com/oauth/token

ISC API's URL:
https://developer.sailpoint.com/docs/api

Access Intelligence Center

 Search Overview - SailPoint Identity Services

https://documentation.sailpoint.com/saas/help/search/index.html

Search

 Search :

Search Overview - SailPoint Identity Services

https://documentation.sailpoint.com/saas/help/search/index.html

SailPoint Support Portal

SailPoint Support Homepage - Customer Support

https://support.sailpoint.com/csm

SailPoint Developer Community

SailPoint Developer Community

https://developer.sailpoint.com/

User Level Access Matrix

Reference:

https://documentation.sailpoint.com/saas/help/common/users/user_level_matrix.html

Multifactor Authentication

Reference:
https://documentation.sailpoint.com/saas/help/common/strong_auth.html

CLI

Reference :
https://developer.sailpoint.com/docs/tools/cli/

ISC Connectors

Reference : 
https://community.sailpoint.com/t5/IdentityNow-Connectors/Identity-Security-Cloud-Connectors/ta-p/80019

Leading Practices

1.Locate VAs close to sources

2.Restarting the VA cluster is almost always the best first action to resolve problems with a VA

3.Use Static IP addresses to simplify networking setup and monitoring

4.To avoid a single point of failure in your environment, maintain a 1:1 VA-to-VM ratio

5.Create New VAs to Switch Deployment Locations and Platforms

6.Allow inbound communications over SSH (port 22) secure shell access for administrative purposes so you can access the VA from inside your network

7.Deploy a minimum of 2 VAs per cluster

8.Separate Sandbox and Production clusters

9.Allow unrestricted outbound traffic on ports 53 (DNS), 123 (NTP), and 443 (HTTPS). As an alternative, you can set up a proxy or single point of access. (Network proxy, firewalls, and caching products can interfere with VA communications)

10.Optional: for added security within your network, configure VAs to communicate with connected sources over Transport Layer Security (TLS)

Email Notifications

Reference:

https://documentation.sailpoint.com/saas/help/common/getting_notified_org_health.html

System and Network Requirements

Reference:
System and Network Requirements - SailPoint Identity Services

Identity Security Cloud Updates & Announcements

Reference:
https://community.sailpoint.com/t5/Identity-Security-Cloud-Updates/bg-p/Updates

SailPoint Identity Services Glossary

Reference:
https://documentation.sailpoint.com/saas/help/common/glossary.html

SailPoint Documentation Home

Reference :
https://documentation.sailpoint.com/

SaaS Configuration

Reference:
https://developer.sailpoint.com/docs/extensibility/configuration-management/saas-configuration/

Event Triggers

Reference: 
https://developer.sailpoint.com/docs/extensibility/event-triggers/