integrations/okta

SYEN Comply for Okta

what we read

Okta System Log API authentication events including actor identity, session context, authentication method, IP address, and privilege level.

what we produce

The identity and authentication context fields in every SYEN Comply evidence record are populated with Okta event data and cryptographically bound into the signed chain at decision time.

schema mapping
okta system log field
syen comply schema field
actor.id
identity_context.actor_id
actor.displayName
identity_context.actor_display_name
actor.type
identity_context.actor_type
authenticationContext.authenticationStep
identity_context.auth_method
securityContext.ipAddress
identity_context.ip_address
transaction.id
identity_context.session_id
compliance satisfied
SR 11-7OCC Bulletin 2026-13OMB M-25-22NIST AI RMFEU AI Act Article 12
configuration
  1. 01

    Create an API Service app in your Okta org.

  2. 02

    Grant the okta.logs.read scope.

  3. 03

    Add your client ID and secret to your SYEN Comply configuration.

integration support

support@syensystems.com