Overview
TOTAL ingests identity governance events from your Saviynt instance via the Saviynt REST API. We poll the audit log and access request endpoints on a configurable interval to collect, normalize, and correlate access governance events — including access requests, approval workflows, entitlement changes, role assignments, certification campaigns, and policy violations. Connector Type: PollingPrerequisites
- Saviynt Administrator access with permission to create service accounts and manage API access
- Saviynt Enterprise Identity Cloud (EIC) instance with active users and governance workflows
- API access enabled on your Saviynt tenant
- Approximately 15 minutes to complete setup
Step 1: Identify Your Saviynt Instance URL
- Sign in to your Saviynt Admin Console
- Your instance URL follows the format
https://your-company.saviyntcloud.com - Paste the Base URL into the TruU Portal
Step 2: Create a Service Account
- In the Saviynt Admin Console, navigate to Admin → Identity Repository → Users
- Click Create User
- Enter:
- Username:
truu-total-integration - Email: Your TOTAL admin contact email
- User Type: Service Account
- Username:
- Click Save
- Set a strong password for this account
Step 3: Grant API Permissions
- Navigate to Admin → SAV Roles
- Create or assign a role with the following API permissions:
- Read Audit Logs (
/ECM/api/v5/getAuditLogs) - Read Access Request History (
/ECM/api/v5/getRequestHistory) - Read User Data (
/ECM/api/v5/getUser) - Read Entitlements (
/ECM/api/v5/getEntitlements) - Read Roles (
/ECM/api/v5/getRoles) - Read Certification Data (
/ECM/api/v5/getCertificationData)
- Read Audit Logs (
- Assign this role to the
truu-total-integrationuser - Click Save
All permissions are read-only. TOTAL cannot create, approve, or modify access requests or governance workflows.
Step 4: Enter Credentials in the TruU Portal
In the TruU Portal, navigate to Settings → Connectors → Add Connector → Saviynt and enter:- Saviynt Base URL:
https://your-company.saviyntcloud.com - Username:
truu-total-integration - Password: The service account password
Security & Privacy
What We Access
- Read-only access to Saviynt audit logs and access request history via REST API
- Queries use timestamp filtering — we only fetch new events since the last poll
- All API calls use HTTPS (TLS 1.2+)
What We Don’t Have Access To
- Write access to your Saviynt instance
- Ability to create, approve, or reject access requests
- Access to user passwords or Saviynt configuration
- Administrative functions or policy management
Updating or Rotating Credentials
Rotate Password (Recommended: Every 90 days)
- In Saviynt Admin Console, navigate to Identity Repository → Users
- Find the
truu-total-integrationuser - Reset the password
- Paste the new password in the TruU Portal under the Saviynt connector settings
- Click Test Connection to verify
Revoke Access
To immediately remove TOTAL’s access:-
Option A — Disable in the TruU Portal:
- Go to the TruU Portal → Settings → Connectors
- Find the Saviynt connector and click Disable
-
Option B — Disable the service account:
- In Saviynt, navigate to Identity Repository → Users
- Find
truu-total-integrationand click Disable
-
Option C — Delete the service account:
- Find
truu-total-integrationand click Delete
- Find
Rate Limiting & Scalability
Saviynt API Rate Limits
Ingestion Capacity
IGA events are inherently low-volume. A large enterprise with 100K+ users typically generates 1K–15K Saviynt events/day (with spikes up to 50K during certification campaigns). At ~5–10 req/s practical throughput, TOTAL has orders of magnitude of headroom above expected volume. Rate limiting is rarely a factor for this signal class.Event Freshness
Events appear in the Saviynt audit log within seconds to low minutes. TOTAL polls on a configurable interval (default: 5 minutes). End-to-end latency is typically under 10 minutes.Resilience
TOTAL uses cursor-based ingestion with at-least-once delivery. The polling cursor only advances after events are successfully collected, normalized, and published. If any step fails, the cursor stays put and the next poll replays from the last known-good position. No events are lost. Transient failures (429s, 5xx, timeouts) are retried automatically with exponential backoff. After 5 consecutive failures, the connector self-pauses and can be re-enabled from the TruU Portal. On recovery from an extended outage, TOTAL resumes from its last cursor — Saviynt retains audit logs for the configured retention period.Connector Design
Each connector polls on an independent, configurable interval. Events are batched and published in per-user order to preserve sequence integrity for persona building. Connector workers are stateless and scale horizontally. All polling intervals, page sizes, and batching parameters are tunable from the TruU Portal.Part 2: Event Types & Data Schema
Signal Classification
Event Types We Ingest
TOTAL extracts the following categories of events from Saviynt. Every event ingested is tied to a specific human identity — either the user performing the action or the user being acted upon. System-level events (campaign launches, configuration changes, report generation) that cannot be attributed to a specific person are excluded.Access Request Events
Entitlement & Role Events
User Lifecycle Events
Certification & Compliance Events
SoD & Policy Violation Events
Audit Trail Events
Sample Source Event (Saviynt Audit Log)
TOTAL Normalized Event
How This Feeds TOTAL
Persona Building
Saviynt events define the access boundary of each user’s persona. By tracking which entitlements, roles, and applications a user has been granted access to — and the governance workflows that authorized that access — TOTAL builds a precise model of what each identity should be doing. This separates baseline user behavior from expected privileged actions, particularly for administrators and operators.Anomaly Detection
TOTAL’s behavioral engine uses Saviynt events to detect:- Abnormal privilege activation — access requests for entitlements outside a user’s historical pattern or job function
- Privilege accumulation — gradual buildup of entitlements that collectively represent excessive access
- Governance bypass indicators — auto-approved requests that circumvent normal approval chains, or bulk provisioning actions
- SoD violations — segregation of duties conflicts that indicate a single identity holds incompatible privileges
- Certification anomalies — rubber-stamping patterns where reviewers certify all access without meaningful review
- Orphaned access — entitlements that persist after role changes or termination events

