ProcessUnity

This is a custom integration and is not enabled by default for your account. Please contact SAFE Support to have the ProcessUnity integration enabled for your organization

Overview

This guide outlines how to integrate ProcessUnity with the SAFEOne TPRM platform. The integration enables automated ingestion of third-party data using secure SFTP (file-based data exchange) methods or Amazon S3.

Integration Method

ProcessUnity exports data related to third-party vendors, assessments, and risk findings. These data sets can be transmitted to SAFEOne TPRM for processing and risk quantification.

SAFE supports two primary file-based integration methods for ProcessUnity:

SFTP-based integration

How does it work?

1. ProcessUnity generates data exports (CSV/JSON/XML) at scheduled intervals.

2. Files are uploaded to a secure SFTP server accessible by SAFE.

3. SAFE ingests and maps the data into relevant vendor risk profiles.

Setup

1. Export Configuration in ProcessUnity

   • Configure exports for Vendor List, Vendor Risk Ratings, and Questionnaire Responses

   • Schedule exports (e.g., daily at 2 AM UTC).

   • Format: .csv or .json preferred

2. SFTP Credentials

   • SAFE provides SFTP endpoint and authentication credentials (username + SSH key).

   • Alternatively, vendor-hosted SFTP endpoints can be supported with whitelisted SAFE IPs.

3. File Structure & Naming

   • Use consistent naming (e.g., vendor_risks_{date}.csv).

   • Each file must adhere to the SAFE-provided schema.

4. Data Ingestion in SAFE

   • SAFE connector polls SFTP location at scheduled intervals.

   • Files are validated, transformed if needed, and mapped to Vendor Risk Profiles and Risk Scores

Amazon S3-based integration

How does it work?

1. Customer drops data exports from ProcessUnity into a shared S3 bucket.

2. SAFE periodically scans the bucket to fetch and ingest new data files.

Setup Steps

1. S3 Bucket Configuration

   1. SAFE provides a bucket path (e.g., s3://safe-vendor-integrations/processunity/) OR

   2. Cusotmers provide a their own S3 bucket with proper access permissions.

2. Export Settings

   1. Files exported and uploaded to S3 at agreed cadence.

   2. Formats: .csv, .json.

3. Security

   1. Access via IAM roles, bucket policies, or pre-signed URLs.

   2. Encryption enforced (SSE-KMS or SSE-S3).

4. SAFE Sync Job

   1. SAFE connector fetches new files on a fixed schedule (e.g., every 6 hours).

   2. Schema compliance check is performed before ingestion.