# Data Classification Vendor Import

Classification ingestion enables customers to bring classification results from third-party solutions into Data Access Security where they can be combined with SailPoint’s identity context and native data access security capabilities.

By integrating existing classification data with identity and access information, customers can move beyond simply identifying sensitive data to governing who has access to it and understanding risk without having to replace their existing classification investment.

## Classification Label Imports

The Classification Label Imports page provides users with the ability to view various import integrations from DSPM vendors and imported files (CSV) while also allowing the management of these integrations.

To view the import options, go to **Compliance > Data Classification > Classification Label Imports**.

On the Classification Label Imports page, each import has the option to edit, run it now, or delete the import.

Search for a specific import using the search bar.

## Creating a New Import

!!! tip
    When [configuring an application](https://documentation.sailpoint.com/das-connectors/help/index.html) to have data classification, a classification method needs to be selected. You can either choose to classify through Data Access Security or by a third-party classification integration.

To create a new classification import:

1. Select **Create Import**.
2. Select if this import will be created from [another vendor](#integrating-with-a-vendor) or from a [CSV file](#csv-upload).

### CSV Upload

Uploading classification from a CSV file allows you to map classification labels into Data Access Security.

Data Access Security provides a downloadable CSV template with required columns of information.

1. Upload the correct .csv file by either dragging it to the upload box or by selecting **choose a file** .

2. Select **Upload**.

### Integrating with a Vendor

This method of importing allows classification labels to be linked from other vendors.

1. Select **Create Integration**.

2. On the **General Details** page, select the **Vendor** from the dropdown and provide a **Name** and **Description** for the connection. Providing a description is optional.

3. Select **Next**.
4. The connection details for each vendor will differ. Select the correct vendor to know what connection details are needed.

??? example "BigID"
        Provide the following:
          
          - **Tenant URL** - For example, `sailpoint-poc.bigid.cloud`. **Note:** The name cannot just be the tenant name because "bigid.cloud" is not consistent for all tenants.  
          - **Session Token** - Value generated for a BigID user within their platform. For more information on this value and how to create it, refer to [BigID documentation](https://developer.bigid.com/).

??? example "Purview"
        Provide the following:
          
          - **Tenant Domain Name** - The Microsoft 365 tenant's initial domain. For example, `contoso.onmicrosoft.com`.
          - **Application ID** - Enter the Application ID for the Microsoft 365 application used by the Data Access Security
          - **Certificate File** - Certificate assigned to the Azure application used by Data Access Security. Either navigate to the certificate by selecting **Choose a File**, or drag the certificate onto the Certificate File Path field.
          - **Certificate Password** - Enter the password for the certificate.

5. To test the connection, select **Test Connection**. Once the connection was successful, select **Next**.
6. On the **Vendor Source Mapping** page, you can map vendors to one or more applications that are within Data Access Security. 
7. Locate the appropriate vendor and select the desired applications from that dropdown within the vendor card.

!!! note
        One vendor source can map to one or multiple Data Access Security applications. However, only one Data Access Security application can be mapped to a vendor.

8. Once everything is mapped, select **Next**.
9. Setting a schedule is enabled by default. If setting a scheduled integration, select a scheduling frequency from the dropdown list.

??? note "Schedule Frequency Options"

- **Run After** - Create dependency of tasks. The task starts running only upon successful completion of the first task.
         - **Daily** - Set the start date and time.
         - **Weekly** - Set the day(s) of the week on which to run.
         - **Monthly** - Set the day of the month on which to run a task.
         - **Quarterly** - Set a monthly schedule with an interval of 3 months.
         - **Semi-Annually** - Set a monthly schedule with an interval of 6 months.
         - **Yearly** - Set a monthly schedule with an interval of 12 months.

10. Set the desired days of the week for the recurrence.
11. Fill the time and date fields with scheduling times. These fields differ depending upon the scheduling frequency selected.
12. Select **Next**.
13. On the **Summary** page, review all of the selected vendor integration details.
14. Select **Save**.

Data Classification Vendor Import

Classification ingestion enables customers to bring classification results from third-party solutions into Data Access Security where they can be combined with SailPoint’s identity context and native data access security capabilities.

By integrating existing classification data with identity and access information, customers can move beyond simply identifying sensitive data to governing who has access to it and understanding risk without having to replace their existing classification investment.

Classification Label Imports

The Classification Label Imports page provides users with the ability to view various import integrations from DSPM vendors and imported files (CSV) while also allowing the management of these integrations.

To view the import options, go to Compliance > Data Classification > Classification Label Imports.

On the Classification Label Imports page, each import has the option to edit, run it now, or delete the import.

Search for a specific import using the search bar.

Creating a New Import

Tip

When configuring an application to have data classification, a classification method needs to be selected. You can either choose to classify through Data Access Security or by a third-party classification integration.

To create a new classification import:

Select Create Import.
Select if this import will be created from another vendor or from a CSV file.

CSV Upload

Uploading classification from a CSV file allows you to map classification labels into Data Access Security.

Data Access Security provides a downloadable CSV template with required columns of information.

Upload the correct .csv file by either dragging it to the upload box or by selecting choose a file .
Select Upload.

Integrating with a Vendor

This method of importing allows classification labels to be linked from other vendors.

Select Create Integration.
On the General Details page, select the Vendor from the dropdown and provide a Name and Description for the connection. Providing a description is optional.
Select Next.
The connection details for each vendor will differ. Select the correct vendor to know what connection details are needed.
BigID

Provide the following:
- Tenant URL - For example, sailpoint-poc.bigid.cloud. Note: The name cannot just be the tenant name because "bigid.cloud" is not consistent for all tenants.
- Session Token - Value generated for a BigID user within their platform. For more information on this value and how to create it, refer to BigID documentation.
Purview

Provide the following:
- Tenant Domain Name - The Microsoft 365 tenant's initial domain. For example, contoso.onmicrosoft.com.
- Application ID - Enter the Application ID for the Microsoft 365 application used by the Data Access Security
- Certificate File - Certificate assigned to the Azure application used by Data Access Security. Either navigate to the certificate by selecting Choose a File, or drag the certificate onto the Certificate File Path field.
- Certificate Password - Enter the password for the certificate.
To test the connection, select Test Connection. Once the connection was successful, select Next.
On the Vendor Source Mapping page, you can map vendors to one or more applications that are within Data Access Security.
Locate the appropriate vendor and select the desired applications from that dropdown within the vendor card.

Note

One vendor source can map to one or multiple Data Access Security applications. However, only one Data Access Security application can be mapped to a vendor.
Once everything is mapped, select Next.
Setting a schedule is enabled by default. If setting a scheduled integration, select a scheduling frequency from the dropdown list.
Schedule Frequency Options
- Run After - Create dependency of tasks. The task starts running only upon successful completion of the first task.
- Daily - Set the start date and time.
- Weekly - Set the day(s) of the week on which to run.
- Monthly - Set the day of the month on which to run a task.
- Quarterly - Set a monthly schedule with an interval of 3 months.
- Semi-Annually - Set a monthly schedule with an interval of 6 months.
- Yearly - Set a monthly schedule with an interval of 12 months.
Set the desired days of the week for the recurrence.
Fill the time and date fields with scheduling times. These fields differ depending upon the scheduling frequency selected.
Select Next.
On the Summary page, review all of the selected vendor integration details.
Select Save.

Documentation Feedback

Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.