VerifAIdentity

Integrations

Exactly what we read, how, and where it stops.

Every connector is read-only. This is the permission list your reviewers will ask for, with what each connector supports today and its known limits.

Sources

Built in lab tested end to end against our own tenant In development built and tested with recorded data, no live tenant yet Planned not built
SourceMaturitySign-in methodExact permissionsWhat it readsSupportsKnown limits
OktaBuilt in labAPI service app, OAuth 2.0 client credentials with a private key (private_key_jwt), Read-Only Administrator roleokta.users.read okta.logs.read okta.groups.read okta.apps.read okta.policies.readUsers and status, last sign-in, System Log eventsAccounts, leaver and inactivity clocks, all sign-in detectionsSessions cannot be listed through the API; sign-in policies that might deny access are not evaluated; group and app assignments not yet mapped to access
Microsoft Entra IDBuilt in labApp registration, client credentials, admin consentDirectory.Read.All AuditLog.Read.All Policy.Read.All Device.Read.All (application permissions)Users, enabled state, session revocation time, directory roles, service principals, app secret and certificate end dates, application owners, audit log, Conditional Access policies, sign-in logAccounts, admin roles, workloads and owners, credential expiry, leaver and privileged clocks, sign-in capability through Conditional AccessSign-in logs need Entra ID P1 or P2 (our lab has neither, so inactivity shows as cannot be verified); only block-all policies count as a full sign-in block; PIM activation history not read
PingOneBuilt in labWorker application, client credentialsRoles: Identity Data Read Only, Environment Read Only. The connector warns if any role that can change data is granted.Users, enabled and lock state, applications, activity eventsAccounts, leaver clocks, sign-in capability, spray and multi-system detectionsSessions not exposed read-only; application entitlements not read
midPoint (governance)Built in labREST API account with read accessSearch users and roles (read)Identities, status, end dates, assigned roles as approvalsApproval and privileged clocks, governance as leaver trigger when there is no HR recordApproval expiry, approver authority and request history not read
SailPoint Identity Security CloudIn developmentOAuth 2.0 client credentials with a personal access token of a user who can read identitiesGET requests and one read-only query: POST /v2025/searchIdentities, lifecycle state, accessGovernance source for the same clocks as midPointTested with recorded responses only; needs a live tenant before any claim
HRBuilt in labCSV worker export placed in a folderRead the export fileWorker ID, name, work email, worker type, status, hire and termination dates and reasonLeaver trigger, person matchingDirect HR system APIs (Workday and others) planned
SaviyntPlannedWaiting for developer access.

Refresh: every pull reads the last 24 hours of events by default (configurable); vendor rate limits are respected with back-off. Each source records its sync time, and evidence older than 48 hours is treated as stale.

What each system lets us see

The access layers depend on what each vendor exposes read-only. Where a layer is blank, the product says so on every finding.

LayerOktaEntraPingOneGovernance
Account stateStatusaccountEnabledenabledStatus, end date
Sign-in possibleStatus onlyEnabled plus Conditional Access block policiescanAuthenticate, lockNot a sign-in account
SessionsNot observableSession revocation timeNot observableNot applicable
Use after triggerSystem Log, last sign-inNeeds P1 or P2Activity eventsNot applicable
What it holdsNot yet mappedDirectory rolesNot readApproved roles

Outputs

DestinationMaturityFormatAuthenticationNotes
SplunkBuilt in labOCSF JSON over HTTP Event CollectorHEC token held with the other secretsOnly new or changed findings are sent; each carries its fingerprint
Any syslog SIEMBuilt in labCEF in RFC 5424 syslog, TCP or UDPNetwork controlsTested over UDP against a local listener
WebhookBuilt in labOCSF JSONOptional bearer token and HMAC-SHA256 signature headerFor ticketing, GRC or custom pipelines
Audit packBuilt in labJSONDownloaded by a signed-in userRules, settings, every clock with history, coverage, chain verification and the head to keep

See it on your own identity data.

A read-only pilot with Okta, Microsoft Entra ID and your HR export. 30 to 60 days, measured against targets we agree up front.