This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Sources

Connecting all the entities in Traverse.

    Sources is the main front end entry point for Protegrity’s enterprise data catalog service, the system of record for an organization’s entire data estate. It connects to and scans datastores, object stores, knowledge graphs, and identity providers and Active Directory integrations. It maintains a continuously updated inventory of every data source, schema, table, column, file structure, graph entity, principal, role, group, and access path across the organization. Every scan logs not just what exists, but who can reach it and how. It thus maps the relationship between data and the identities that have access to it.

    The catalog that Sources maintains is the intelligence foundation for the rest of the Protegrity platform. A scan is a job that runs against the configured sources to discover and classify data at scale. When a scan executes, it checks connectivity, traverses the source structure, and identifies sensitive content. It produces a set of findings that are surfaced in the Source Details for review and action.

    Scans can be run on demand or on a schedule. Over time, operational control increases and measurable risk decreases. Coverage can be tracked, newly introduced sensitive data can be detected before it becomes a liability. Timestamped evidence can be generated for governance, compliance reporting, and remediation workflows.

    Creating a Scan

    A scan is a job that runs against the configured sources to discover and classify data at scale. When a scan executes, it checks connectivity, traverses the source structure, and identifies sensitive content. It produces a set of findings that are surfaced in the Source Details for review and action.

    Scans can be run on demand or on a schedule. Over time, operational control increases and measurable risk decreases. Coverage can be tracked, newly introduced sensitive data can be detected before it becomes a liability. Timestamped evidence can be generated for governance, compliance reporting, and remediation workflows.

    1. On the UI, click New Scan to create a scan.
    2. Enter the scan name and description in the Name and Description fields respectively.
    3. From the Select Datastore drop-down list, select the datastore to be scanned. If a new datastore needs to be created, click Add new Datastore to create a new datastore.
    4. Select the scan type from the Scan Type drop-down list. The following options are available:
      • Full Scan. If this option is selected, the entire datastore will be scanned for PII data.
      • Map Only Scan. If this option is selected, only the structure will be scanned. PII data will not be classified.
    5. Under Classification, set the minimum confidence score for the classification results by sliding the Score Threshold slider. The default value is 50%. Any classification with a score below this threshold will be excluded from the scan results.
    6. Enter a value in the Sample Size field to set the maximum number of rows per table.
    7. Click Save to create the scan.

    Adding a Source

    On the UI, click New Data Source to create a data source. The following data sources are supported:

    The following object stores are supported:

    The following graph databases are supported:

    The following identity providers are supported:

    Creating a PostgreSQL Source

    1. Enter the source name and description in the Name and Description fields respectively.
    2. Select the PostgreSQL from the Data Source type drop-down list.
    3. Under Connection, enter data in the following fields:
      • Host - Hostname
      • Port - Port number
      • Database Name - Name for the database
      • Username - username to connect to the database
      • SSL mode - Select the SSL mode from the drop-down list. The following options are available:
        • disable
        • allow
        • prefer
        • require
    4. Under Authentication, select the authentication method from the drop-down list. The following options are available:
      • Username and Password. If this option is selected, enter the password in the Password field.
      • No credentials
    5. Click Test Connection to verify the connection to the database.
    6. After the connection is successful, click Save to create the source.

    Creating a Databricks Source

    1. Enter the source name and description in the Name and Description fields respectively.
    2. Select the Databricks from the Data Source type drop-down list.
    3. Under Connection, enter data in the following fields:
      • Workspace URL - URL of the Databricks workspace.
      • HTTP Path - HTTP path.
      • Catalog - Name of the catalog.
      • Schema - Enter the username.
    4. Under Authentication, select the authentication method from the drop-down list. The following options are available:
      • Personal Access Token. If this option is selected, enter the token in the Personal Access Token field.
      • Username and Password. If this option is selected, enter the username and password in the Username and Password fields respectively.
      • No credentials.
    5. Click Test Connection to verify the connection to the database.
    6. After the connection is successful, click Save to create the source.

    Creating an Apache Hive Source

    1. Enter the source name and description in the Name and Description fields respectively.
    2. Select the Apache Hive from the Data Source type drop-down list.
    3. Under Connection, enter data in the following fields:
      • Metastore URI - URI of the Hive metastore.
      • Database - Name of the database.
    4. Under Authentication, select the authentication method from the drop-down list. The following options are available:
      • Username and Password. If this option is selected, enter the username and password in the Username and Password fields respectively.
      • No credentials.
    5. Click Test Connection to verify the connection to the database.
    6. After the connection is successful, click Save to create the source.

    Creating an Amazon Redshift Source

    1. Enter the source name and description in the Name and Description fields respectively.
    2. Select the Amazon Redshift from the Data Source type drop-down list.
    3. Under Connection, enter data in the following fields:
      • Host - Hostname of the Amazon Redshift cluster.
      • Port - Port number.
      • Database - Name of the database.
      • Schema - Name of the schema.
    4. Under Authentication, select the authentication method from the drop-down list. The following options are available:
      • IAM Access Key. If this option is selected, enter the IAM Access Key ID in the Access Key ID field and the IAM Secret Access Key in the Secret Access Key field.
      • Username and Password. If this option is selected, enter the username and password in the Username and Password fields respectively.
      • No credentials.
    5. Click Test Connection to verify the connection to the database.
    6. After the connection is successful, click Save to create the source.

    Creating an Oracle Database Source

    1. Enter the source name and description in the Name and Description fields respectively.
    2. Select the Oracle Database from the Data Source type drop-down list.
    3. Under Connection, enter data in the following fields:
      • Driver - Oracle JDBC driver class name. For example, oracle.jdbc.OracleDriver.
      • Port - Port number.
      • Database - Name of the database.
      • Schema - Name of the schema.
    4. Under Authentication, select the authentication method from the drop-down list. The following options are available:
      • Username and Password. If this option is selected, enter the username and password in the Username and Password fields respectively.
      • No credentials.
    5. Click Test Connection to verify the connection to the database.
    6. After the connection is successful, click Save to create the source.

    Creating an Amazon S3 Source

    1. Enter the source name and description in the Name and Description fields respectively.
    2. Select the Amazon S3 from the Data Source type drop-down list.
    3. Under Connection, enter data in the following fields:
      • Region - AWS region where the bucket is located.
      • Bucket - Name of the S3 bucket.
    4. Under Authentication, select the authentication method from the drop-down list. The following options are available:
      • IAM Role. If this option is selected, enter the IAM role ARN in the Role ARN field.
      • Access Key ID. If this option is selected, enter the AWS access key ID in the Access Key ID field and the AWS secret access key in the Secret Access Key field.
    5. Click Test Connection to verify the connection to the database.
    6. After the connection is successful, click Save to create the source.

    Creating a TigerGraph Source

    1. Enter the source name and description in the Name and Description fields respectively.
    2. Select the TigerGraph from the Data Source type drop-down list.
    3. Under Connection, enter data in the following fields:
      • Host - Hostname of the TigerGraph server.
      • Graph Name - Name of the graph.
      • REST++Port - Port number.
      • GS Port - Port number.
    4. Under Authentication, select the authentication method from the drop-down list. The following options are available:
      • Username and Password. If this option is selected, enter the username and password in the Username and Password fields respectively.
      • GSQL Secret. If this option is selected, enter the GSQL secret in the GSQL Secret field.
      • No credentials
    5. Click Test Connection to verify the connection to the database.
    6. After the connection is successful, click Save to create the source.

    Creating a Neo4j Source

    1. Enter the source name and description in the Name and Description fields respectively.
    2. Select the Neo4j from the Data Source type drop-down list.
    3. Under Connection, enter data in the following fields:
      • Host/URI - Hostname or the URL of the Neo4j server
      • Database - Name of the database
    4. Under Authentication, select the authentication method from the drop-down list. The following options are available:
      • Username and Password. If this option is selected, enter the username and password in the Username and Password fields respectively.
      • No credentials
    5. Click Test Connection to verify the connection to the database.
    6. After the connection is successful, click Save to create the source.

    Creating a OIDC/Okta Source

    1. Enter the source name and description in the Name and Description fields respectively.
    2. Select the OIDC/Okta from the Data Source type drop-down list.
    3. Under Connection, enter data in the following fields:
      • Issuer URL - The URL of the OIDC/Okta issuer
      • Client ID - The client ID for the OIDC/Okta application
      • Client Secret - The client secret for the OIDC/Okta application
      • Token URL - The URL to obtain the access token
    4. Click Test Connection to verify the connection to the OIDC/Okta provider.
    5. After the connection is successful, click Save to create the source.

    Creating a LDAP/Active Directory Source

    1. Enter the source name and description in the Name and Description fields respectively.
    2. Select the LDAP/Active Directory from the Data Source type drop-down list.
    3. Under Connection, enter data in the following fields:
      • Host - The URL of the LDAP/Active Directory server
      • Port - The port of the LDAP/Active Directory server
      • Base DN - The base distinguished name for LDAP/Active Directory searches
    4. Under Authentication, enter the username and password in the Username and Password fields respectively.
    5. Click Test Connection to verify the connection to the LDAP/Active Directory server.
    6. After the connection is successful, click Save to create the source.

    Creating an SCIM 2.0 Source

    1. Enter the source name and description in the Name and Description fields respectively.
    2. Select the SCIM 2.0 from the Data Source type drop-down list.
    3. Under Connection, enter the URL of the SCIM 2.0 server in the Base URL field.
    4. Under Authentication, enter the bearer token for the SCIM 2.0 server in the Bearer Token
    5. Click Test Connection to verify the connection to the SCIM 2.0 server.
    6. After the connection is successful, click Save to create the source.

    Reviewing a Scan

    Reviewing scan details is where users turn discoveries into decisions. The Schema tab shows object-level results, exposing classifications at each discovered asset level: datasource, schema, table, column, and node or path for hierarchical sources. The value is traceable evidence and faster action. Teams can verify coverage, compare drift over time, confirm whether sensitive data increased or moved, prioritize remediation by risk and location. They can then provide defensible audit and compliance reporting based on exact findings rather than assumptions.

    To investigate the metadata or classification history for any object, click the representative row to open the Source Detail Panel. The panel displays object metadata at the top, followed by the classification response and an activity log showing changes to that row over time.

    The Scanners tab displays all configured scanners. For recurring scanners, click into a scanner item to see its individual jobs, such as currently running, scheduled, and past. Each job shows when it ran or is scheduled to run, its scope, status, and duration, along with how findings changed across executions.