LogoLogo
Knowledge BaseCommunityRelease NotesRequest Demo
  • Overview
  • Quick Start
    • Onboarding Guide
  • Data Sources & Transports
    • Supported Logs
      • 1Password Logs
      • Apache Logs
      • AppOmni Logs
      • Asana Logs
      • Atlassian Logs
      • Auditd Logs
      • Auth0 Logs
      • AWS Logs
        • AWS ALB
        • AWS Aurora
        • AWS CloudFront
        • AWS CloudTrail
        • AWS CloudWatch
        • AWS Config
        • AWS EKS
        • AWS GuardDuty
        • AWS Security Hub
        • Amazon Security Lake
        • AWS S3
        • AWS Transit Gateway
        • AWS VPC
        • AWS WAF
      • Azure Monitor Logs
      • Bitwarden Logs
      • Box Logs
      • Carbon Black Logs
      • Cisco Umbrella Logs
      • Cloudflare Logs
      • CrowdStrike Logs
        • CrowdStrike Falcon Data Replicator
        • CrowdStrike Event Streams
      • Docker Logs
      • Dropbox Logs
      • Duo Security Logs
      • Envoy Logs
      • Fastly Logs
      • Fluentd Logs
      • GCP Logs
      • GitHub Logs
      • GitLab Logs
      • Google Workspace Logs
      • Heroku Logs
      • Jamf Pro Logs
      • Juniper Logs
      • Lacework Logs
        • Lacework Alert Channel Webhook
        • Lacework Export
      • Material Security Logs
      • Microsoft 365 Logs
      • Microsoft Entra ID Audit Logs
      • Microsoft Graph Logs
      • MongoDB Atlas Logs
      • Netskope Logs
      • Nginx Logs
      • Notion Logs
      • Okta Logs
      • OneLogin Logs
      • Orca Security Logs (Beta)
      • Osquery Logs
      • OSSEC Logs
      • Proofpoint Logs
      • Push Security Logs
      • Rapid7 Logs
      • Salesforce Logs
      • SentinelOne Logs
      • Slack Logs
      • Snowflake Audit Logs (Beta)
      • Snyk Logs
      • Sophos Logs
      • Sublime Security Logs
      • Suricata Logs
      • Sysdig Logs
      • Syslog Logs
      • Tailscale Logs
      • Teleport Logs
      • Tenable Vulnerability Management Logs
      • Thinkst Canary Logs
      • Tines Logs
      • Tracebit Logs
      • Windows Event Logs
      • Wiz Logs
      • Zeek Logs
      • Zendesk Logs
      • Zoom Logs
      • Zscaler Logs
        • Zscaler ZIA
        • Zscaler ZPA
    • Custom Logs
      • Log Schema Reference
      • Transformations
      • Script Log Parser (Beta)
      • Fastmatch Log Parser
      • Regex Log Parser
      • CSV Log Parser
    • Data Transports
      • HTTP Source
      • AWS Sources
        • S3 Source
        • CloudWatch Logs Source
        • SQS Source
          • SNS Source
        • EventBridge
      • Google Cloud Sources
        • Cloud Storage (GCS) Source
        • Pub/Sub Source
      • Azure Blob Storage Source
    • Monitoring Log Sources
    • Ingestion Filters
      • Raw Event Filters
      • Normalized Event Filters (Beta)
    • Data Pipeline Tools
      • Chronosphere Onboarding Guide
      • Cribl Onboarding Guide
      • Fluent Bit Onboarding Guide
        • Fluent Bit Configuration Examples
      • Fluentd Onboarding Guide
        • General log forwarding via Fluentd
        • MacOS System Logs to S3 via Fluentd
        • Syslog to S3 via Fluentd
        • Windows Event Logs to S3 via Fluentd (Legacy)
        • GCP Audit to S3 via Fluentd
      • Observo Onboarding Guide
      • Tarsal Onboarding Guide
    • Tech Partner Log Source Integrations
  • Detections
    • Using Panther-managed Detections
      • Detection Packs
    • Rules and Scheduled Rules
      • Writing Python Detections
        • Python Rule Caching
        • Data Models
        • Global Helper Functions
      • Modifying Detections with Inline Filters (Beta)
      • Derived Detections (Beta)
        • Using Derived Detections to Avoid Merge Conflicts
      • Using the Simple Detection Builder
      • Writing Simple Detections
        • Simple Detection Match Expression Reference
        • Simple Detection Error Codes
    • Correlation Rules (Beta)
      • Correlation Rule Reference
    • PyPanther Detections (Beta)
      • Creating PyPanther Detections
      • Registering, Testing, and Uploading PyPanther Detections
      • Managing PyPanther Detections in the Panther Console
      • PyPanther Detections Style Guide
      • pypanther Library Reference
      • Using the pypanther Command Line Tool
    • Signals
    • Policies
    • Testing
      • Data Replay (Beta)
    • Framework Mapping and MITRE ATT&CK® Matrix
  • Cloud Security Scanning
    • Cloud Resource Attributes
      • AWS
        • ACM Certificate
        • CloudFormation Stack
        • CloudWatch Log Group
        • CloudTrail
        • CloudTrail Meta
        • Config Recorder
        • Config Recorder Meta
        • DynamoDB Table
        • EC2 AMI
        • EC2 Instance
        • EC2 Network ACL
        • EC2 SecurityGroup
        • EC2 Volume
        • EC2 VPC
        • ECS Cluster
        • EKS Cluster
        • ELBV2 Application Load Balancer
        • GuardDuty Detector
        • GuardDuty Detector Meta
        • IAM Group
        • IAM Policy
        • IAM Role
        • IAM Root User
        • IAM User
        • KMS Key
        • Lambda Function
        • Password Policy
        • RDS Instance
        • Redshift Cluster
        • Route 53 Domains
        • Route 53 Hosted Zone
        • S3 Bucket
        • WAF Web ACL
  • Alerts & Destinations
    • Alert Destinations
      • Amazon SNS Destination
      • Amazon SQS Destination
      • Asana Destination
      • Blink Ops Destination
      • Custom Webhook Destination
      • Discord Destination
      • GitHub Destination
      • Google Pub/Sub Destination (Beta)
      • Incident.io Destination
      • Jira Cloud Destination
      • Jira Data Center Destination (Beta)
      • Microsoft Teams Destination
      • Mindflow Destination
      • OpsGenie Destination
      • PagerDuty Destination
      • Rapid7 Destination
      • ServiceNow Destination (Custom Webhook)
      • Slack Bot Destination
      • Slack Destination (Webhook)
      • Splunk Destination (Beta)
      • Tines Destination
      • Torq Destination
    • Assigning and Managing Alerts
      • Managing Alerts in Slack
    • Alert Runbooks
      • Panther-managed Policies Runbooks
        • AWS CloudTrail Is Enabled In All Regions
        • AWS CloudTrail Sending To CloudWatch Logs
        • AWS KMS CMK Key Rotation Is Enabled
        • AWS Application Load Balancer Has Web ACL
        • AWS Access Keys Are Used Every 90 Days
        • AWS Access Keys are Rotated Every 90 Days
        • AWS ACM Certificate Is Not Expired
        • AWS Access Keys not Created During Account Creation
        • AWS CloudTrail Has Log Validation Enabled
        • AWS CloudTrail S3 Bucket Has Access Logging Enabled
        • AWS CloudTrail Logs S3 Bucket Not Publicly Accessible
        • AWS Config Is Enabled for Global Resources
        • AWS DynamoDB Table Has Autoscaling Targets Configured
        • AWS DynamoDB Table Has Autoscaling Enabled
        • AWS DynamoDB Table Has Encryption Enabled
        • AWS EC2 AMI Launched on Approved Host
        • AWS EC2 AMI Launched on Approved Instance Type
        • AWS EC2 AMI Launched With Approved Tenancy
        • AWS EC2 Instance Has Detailed Monitoring Enabled
        • AWS EC2 Instance Is EBS Optimized
        • AWS EC2 Instance Running on Approved AMI
        • AWS EC2 Instance Running on Approved Instance Type
        • AWS EC2 Instance Running in Approved VPC
        • AWS EC2 Instance Running On Approved Host
        • AWS EC2 Instance Running With Approved Tenancy
        • AWS EC2 Instance Volumes Are Encrypted
        • AWS EC2 Volume Is Encrypted
        • AWS GuardDuty is Logging to a Master Account
        • AWS GuardDuty Is Enabled
        • AWS IAM Group Has Users
        • AWS IAM Policy Blocklist Is Respected
        • AWS IAM Policy Does Not Grant Full Administrative Privileges
        • AWS IAM Policy Is Not Assigned Directly To User
        • AWS IAM Policy Role Mapping Is Respected
        • AWS IAM User Has MFA Enabled
        • AWS IAM Password Used Every 90 Days
        • AWS Password Policy Enforces Complexity Guidelines
        • AWS Password Policy Enforces Password Age Limit Of 90 Days Or Less
        • AWS Password Policy Prevents Password Reuse
        • AWS RDS Instance Is Not Publicly Accessible
        • AWS RDS Instance Snapshots Are Not Publicly Accessible
        • AWS RDS Instance Has Storage Encrypted
        • AWS RDS Instance Has Backups Enabled
        • AWS RDS Instance Has High Availability Configured
        • AWS Redshift Cluster Allows Version Upgrades
        • AWS Redshift Cluster Has Encryption Enabled
        • AWS Redshift Cluster Has Logging Enabled
        • AWS Redshift Cluster Has Correct Preferred Maintenance Window
        • AWS Redshift Cluster Has Sufficient Snapshot Retention Period
        • AWS Resource Has Minimum Number of Tags
        • AWS Resource Has Required Tags
        • AWS Root Account Has MFA Enabled
        • AWS Root Account Does Not Have Access Keys
        • AWS S3 Bucket Name Has No Periods
        • AWS S3 Bucket Not Publicly Readable
        • AWS S3 Bucket Not Publicly Writeable
        • AWS S3 Bucket Policy Does Not Use Allow With Not Principal
        • AWS S3 Bucket Policy Enforces Secure Access
        • AWS S3 Bucket Policy Restricts Allowed Actions
        • AWS S3 Bucket Policy Restricts Principal
        • AWS S3 Bucket Has Versioning Enabled
        • AWS S3 Bucket Has Encryption Enabled
        • AWS S3 Bucket Lifecycle Configuration Expires Data
        • AWS S3 Bucket Has Logging Enabled
        • AWS S3 Bucket Has MFA Delete Enabled
        • AWS S3 Bucket Has Public Access Block Enabled
        • AWS Security Group Restricts Ingress On Administrative Ports
        • AWS VPC Default Security Group Restricts All Traffic
        • AWS VPC Flow Logging Enabled
        • AWS WAF Has Correct Rule Ordering
        • AWS CloudTrail Logs Encrypted Using KMS CMK
      • Panther-managed Rules Runbooks
        • AWS CloudTrail Modified
        • AWS Config Service Modified
        • AWS Console Login Failed
        • AWS Console Login Without MFA
        • AWS EC2 Gateway Modified
        • AWS EC2 Network ACL Modified
        • AWS EC2 Route Table Modified
        • AWS EC2 SecurityGroup Modified
        • AWS EC2 VPC Modified
        • AWS IAM Policy Modified
        • AWS KMS CMK Loss
        • AWS Root Activity
        • AWS S3 Bucket Policy Modified
        • AWS Unauthorized API Call
    • Tech Partner Alert Destination Integrations
  • Investigations & Search
    • Search
      • Search Filter Operators
    • Data Explorer
      • Data Explorer SQL Search Examples
        • CloudTrail logs queries
        • GitHub Audit logs queries
        • GuardDuty logs queries
        • Nginx and ALB Access logs queries
        • Okta logs queries
        • S3 Access logs queries
        • VPC logs queries
    • Visualization and Dashboards
      • Custom Dashboards (Beta)
      • Panther-Managed Dashboards
    • Standard Fields
    • Saved and Scheduled Searches
      • Templated Searches
        • Behavioral Analytics and Anomaly Detection Template Macros (Beta)
      • Scheduled Search Examples
    • Search History
    • Data Lakes
      • Snowflake
        • Snowflake Configuration for Optimal Search Performance
      • Athena
  • PantherFlow (Beta)
    • PantherFlow Quick Reference
    • PantherFlow Statements
    • PantherFlow Operators
      • Datatable Operator
      • Extend Operator
      • Join Operator
      • Limit Operator
      • Project Operator
      • Range Operator
      • Sort Operator
      • Search Operator
      • Summarize Operator
      • Union Operator
      • Visualize Operator
      • Where Operator
    • PantherFlow Data Types
    • PantherFlow Expressions
    • PantherFlow Functions
      • Aggregation Functions
      • Date/time Functions
      • String Functions
      • Array Functions
      • Math Functions
      • Control Flow Functions
      • Regular Expression Functions
      • Snowflake Functions
      • Data Type Functions
      • Other Functions
    • PantherFlow Example Queries
      • PantherFlow Examples: Threat Hunting Scenarios
      • PantherFlow Examples: SOC Operations
      • PantherFlow Examples: Panther Audit Logs
  • Enrichment
    • Custom Lookup Tables
      • Creating a GreyNoise Lookup Table
      • Lookup Table Examples
        • Using Lookup Tables: 1Password UUIDs
      • Lookup Table Specification Reference
    • Identity Provider Profiles
      • Okta Profiles
      • Google Workspace Profiles
    • Anomali ThreatStream
    • IPinfo
    • Tor Exit Nodes
    • TrailDiscover (Beta)
  • Panther AI (Beta)
  • System Configuration
    • Role-Based Access Control
    • Identity & Access Integrations
      • Azure Active Directory SSO
      • Duo SSO
      • G Suite SSO
      • Okta SSO
        • Okta SCIM
      • OneLogin SSO
      • Generic SSO
    • Panther Audit Logs
      • Querying and Writing Detections for Panther Audit Logs
      • Panther Audit Log Actions
    • Notifications and Errors (Beta)
      • System Errors
    • Panther Deployment Types
      • SaaS
      • Cloud Connected
        • Configuring Snowflake for Cloud Connected
        • Configuring AWS for Cloud Connected
        • Pre-Deployment Tools
      • Legacy Configurations
        • Snowflake Connected (Legacy)
        • Customer-configured Snowflake Integration (Legacy)
        • Self-Hosted Deployments (Legacy)
          • Runtime Environment
  • Panther Developer Workflows
    • Panther Developer Workflows Overview
    • Using panther-analysis
      • Public Fork
      • Private Clone
      • Panther Analysis Tool
        • Install, Configure, and Authenticate with the Panther Analysis Tool
        • Panther Analysis Tool Commands
        • Managing Lookup Tables and Enrichment Providers with the Panther Analysis Tool
      • CI/CD for Panther Content
        • Deployment Workflows Using Panther Analysis Tool
          • Managing Panther Content via CircleCI
          • Managing Panther Content via GitHub Actions
        • Migrating to a CI/CD Workflow
    • Panther API
      • REST API (Beta)
        • Alerts
        • Alert Comments
        • API Tokens
        • Data Models
        • Globals
        • Log Sources
        • Queries
        • Roles
        • Rules
        • Scheduled Rules
        • Simple Rules
        • Policies
        • Users
      • GraphQL API
        • Alerts & Errors
        • Cloud Account Management
        • Data Lake Queries
        • Log Source Management
        • Metrics
        • Schemas
        • Token Rotation
        • User & Role Management
      • API Playground
    • Terraform
      • Managing AWS S3 Log Sources with Terraform
      • Managing HTTP Log Sources with Terraform
    • pantherlog Tool
    • Converting Sigma Rules
  • Resources
    • Help
      • Operations
      • Security and Privacy
        • Security Without AWS External ID
      • Glossary
      • Legal
    • Panther System Architecture
Powered by GitBook
On this page
  • Overview
  • Video Walkthrough
  • How to onboard Okta logs to Panther
  • Step 1: Create a new Okta API token
  • Step 2: Create a new Okta source in Panther
  • Panther-Built Detections
  • Custom Detections
  • Supported log types
  • Okta.SystemLog

Was this helpful?

  1. Data Sources & Transports
  2. Supported Logs

Okta Logs

Panther supports pulling logs directly from Okta

PreviousNotion LogsNextOneLogin Logs

Last updated 6 months ago

Was this helpful?

Overview

Panther has the ability to fetch Okta events by querying the . Panther will query the System Log API every 1 minute. In order for Panther to access the API you need to create a new API token or use an existing one.

You can also enable .

Video Walkthrough

How to onboard Okta logs to Panther

Step 1: Create a new Okta API token

  1. Log in as Okta administrator.

  2. In the Okta Admin Console, navigate to Security > API.

  3. Click Create Token.

  4. Enter a memorable name for your token, e.g. Panther API token.

  5. Copy the Token value and store it in a secure location. You will need it in the next steps.

    • Note: Okta will not display this value again.

Step 2: Create a new Okta source in Panther

  1. In the left-hand navigation bar of your Panther Console, click Configure > Log Sources.

  2. Click Create New.

  3. Search for “Okta,” then click its tile.

  4. On the slide-out panel, click Start Setup.

  5. On the Configuration page, fill in the following fields:

    • : Enter a descriptive name for the source, e.g. My Okta logs.

    • Okta domain: Select the appropriate domain name from the Okta domain drop-down.

    • API Token: Enter the token value you generated in the previous step.

  6. Click Setup.

    • For each of the toggles set to ON, set a Refresh period (min). This represents the cadence at which Panther will update profile data with what is stored in Okta.

  7. Click Setup. You will be directed to a success screen:

    • The Trigger an alert when no events are processed setting defaults to YES. We recommend leaving this enabled, as you will be alerted if data stops flowing from the log source after a certain period of time. The timeframe is configurable, with a default of 24 hours.

Panther-Built Detections

Custom Detections

Suspicious Behavior Reported

Description: A user has reported suspicious behavior from their account

def rule(event):
    if event.get('eventtype') == 'user.account.report_suspicious_activity_by_enduser':
        return True
#Okta has many event types that are listed here. You can begin your detection based on one of these eventtypes
#https://developer.okta.com/docs/reference/api/event-types/
event.get('eventtype')

#To access the city, state, lat, lon etc. 
deep_get(event, 'client', 'geographicalContext', 'city')
deep_get(event, 'client', 'geographicalContext', 'state')
deep_get(event, 'client', 'geographicalContext', 'country')
deep_get(event, 'client', 'geographicalContext', 'geolocation', 'lon')
deep_get(event, 'client', 'geographicalContext', 'geolocation', 'lat')

#Details on the source of the event
deep_get(event, 'client' 'device')
deep_get(event, 'client', 'ipAddress')
deep_get(event, 'client', 'userAgent')


deep_get(event, 'actor', 'alternateId')
deep_get(event, 'actor', 'displayName')

## Global helpers that may be useful with Okta

# within panther_base_helpers
def okta_alert_context(event: dict):
    """Returns common context for automation of Okta alerts"""
    return {
        "ips": event.get("p_any_ip_addresses", []),
        "actor": event.get("actor", ""),
        "target": event.get("target", ""),
        "client": event.get("client", ""),
    }
    
# within panther_base_helpers
def is_ip_in_network(ip_addr, networks):
    """Check that a given IP is within a list of IP ranges"""
    return any(ip_address(ip_addr) in ip_network(network) for network in networks)

Supported log types

Okta.SystemLog

The Okta System Log records system events related to your organization in order to provide an audit trail that can be used to understand platform activity and to diagnose problems.

schema: Okta.SystemLog
description: |
    The Okta System Log records system events related to your organization in order to provide an audit trail that can be used to understand platform activity and to diagnose problems.
referenceURL: https://developer.okta.com/docs/reference/api/system-log/
fields:
    - name: uuid
      required: true
      description: Unique identifier for an individual event
      type: string
    - name: published
      required: true
      description: Timestamp when event was published
      type: timestamp
      timeFormat: rfc3339
      isEventTime: true
    - name: eventType
      required: true
      description: Type of event that was published
      type: string
    - name: version
      required: true
      description: Versioning indicator
      type: string
    - name: severity
      required: true
      description: 'Indicates how severe the event is: DEBUG, INFO, WARN, ERROR'
      type: string
    - name: legacyEventType
      description: Associated Events API Action objectType attribute value
      type: string
    - name: displayMessage
      description: The display message for an event
      type: string
    - name: actor
      description: Describes the entity that performed an action
      type: object
      fields:
        - name: id
          required: true
          description: ID of actor
          type: string
        - name: type
          required: true
          description: Type of actor
          type: string
        - name: alternateId
          description: Alternative id of the actor
          type: string
          indicators:
            - email
        - name: displayName
          description: Display name of the actor
          type: string
        - name: details
          description: Details about the actor
          type: json
        - name: detailEntry
          description: Detail entry
          type: json
    - name: client
      description: The client that requested an action
      type: object
      fields:
        - name: id
          description: For OAuth requests this is the id of the OAuth client making the request. For SSWS token requests, this is the id of the agent making the request.
          type: string
        - name: userAgent
          description: The user agent used by an actor to perform an action
          type: object
          fields:
            - name: browser
              description: If the client is a web browser, this field identifies the type of web browser (e.g. CHROME, FIREFOX)
              type: string
            - name: os
              description: The Operating System the client runs on (e.g. Windows 10)
              type: string
            - name: rawUserAgent
              description: A raw string representation of the user agent, formatted according to section 5.5.3 of HTTP/1.1 Semantics and Content. Both the browser and the OS fields can be derived from this field.
              type: string
        - name: geographicalContext
          description: The physical location where the client made its request from
          type: object
          fields:
            - name: geolocation
              description: Contains the geolocation coordinates (latitude, longitude)
              type: object
              fields:
                - name: lat
                  description: Latitude
                  type: float
                - name: lon
                  description: Longitude
                  type: float
            - name: city
              description: The city encompassing the area containing the geolocation coordinates, if available (e.g. Seattle, San Francisco)
              type: string
            - name: state
              description: Full name of the state/province encompassing the area containing the geolocation coordinates (e.g. Montana, Incheon)
              type: string
            - name: country
              description: Full name of the country encompassing the area containing the geolocation coordinates (e.g. France, Uganda)
              type: string
            - name: postalCode
              description: Full name of the country encompassing the area containing the geolocation coordinates (e.g. France, Uganda)
              type: string
        - name: zone
          description: The name of the Zone that the client's location is mapped to
          type: string
        - name: ipAddress
          description: Ip address that the client made its request from
          type: string
          indicators:
            - ip
        - name: device
          description: Type of device that the client operated from (e.g. Computer)
          type: string
    - name: request
      description: The request that initiated an action
      type: object
      fields:
        - name: ipChain
          description: If the incoming request passes through any proxies, the IP addresses of those proxies will be stored here in the format (clientIp, proxy1, proxy2, ...).
          type: array
          element:
            type: object
            fields:
                - name: ip
                  description: IP address
                  type: string
                  indicators:
                    - ip
                - name: geographicalContext
                  description: Geographical context of the IP address
                  type: object
                  fields:
                    - name: geolocation
                      description: Contains the geolocation coordinates (latitude, longitude)
                      type: object
                      fields:
                        - name: lat
                          description: Latitude
                          type: float
                        - name: lon
                          description: Longitude
                          type: float
                    - name: city
                      description: The city encompassing the area containing the geolocation coordinates, if available (e.g. Seattle, San Francisco)
                      type: string
                    - name: state
                      description: Full name of the state/province encompassing the area containing the geolocation coordinates (e.g. Montana, Incheon)
                      type: string
                    - name: country
                      description: Full name of the country encompassing the area containing the geolocation coordinates (e.g. France, Uganda)
                      type: string
                    - name: postalCode
                      description: Full name of the country encompassing the area containing the geolocation coordinates (e.g. France, Uganda)
                      type: string
                - name: version
                  description: IP version
                  type: string
                - name: source
                  description: Details regarding the source
                  type: string
    - name: outcome
      description: The outcome of an action
      type: object
      fields:
        - name: result
          description: 'Result of the action: SUCCESS, FAILURE, SKIPPED, ALLOW, DENY, CHALLENGE, UNKNOWN'
          type: string
        - name: reason
          description: Reason for the result, for example INVALID_CREDENTIALS
          type: string
    - name: target
      description: Zero or more targets of an action
      type: array
      element:
        type: object
        fields:
            - name: id
              required: true
              description: ID of target
              type: string
            - name: type
              required: true
              description: Type of target
              type: string
            - name: alternateId
              description: Alternative id of the target
              type: string
            - name: displayName
              description: Display name of the target
              type: string
            - name: details
              description: Details about the target
              type: json
            - name: detailEntry
              description: Detail entry
              type: json
    - name: transaction
      description: The transaction details of an action
      type: object
      fields:
        - name: id
          description: Unique identifier for this transaction.
          type: string
        - name: type
          description: Describes the kind of transaction. WEB indicates a web request. JOB indicates an asynchronous task.
          type: string
        - name: detail
          description: Details for this transaction.
          type: json
    - name: debugContext
      description: The debug request data of an action
      type: object
      fields:
        - name: debugData
          description: Dynamic field containing miscellaneous information dependent on the event type.
          type: json
    - name: authenticationContext
      description: The authentication data of an action
      type: object
      fields:
        - name: authenticationProvider
          description: The system that proves the identity of an actor using the credentials provided to it
          type: string
        - name: authenticationStep
          description: The zero-based step number in the authentication pipeline. Currently unused and always set to 0.
          type: int
        - name: credentialProvider
          description: A credential provider is a software service that manages identities and their associated credentials. When authentication occurs via credentials provided by a credential provider, that credential provider will be recorded here.
          type: string
        - name: credentialType
          description: The underlying technology/scheme used in the credential
          type: string
        - name: rootSessionId
          type: string
        - name: issuer
          description: The specific software entity that created and issued the credential.
          type: object
          fields:
            - name: id
              description: Varies depending on the type of authentication. If authentication is SAML 2.0, id is the issuer in the SAML assertion. For social login, id is the issuer of the token.
              type: string
            - name: type
              description: Information regarding issuer and source of the SAML assertion or token.
              type: string
        - name: externalSessionId
          description: A proxy for the actor's session ID
          type: string
        - name: interface
          description: The third party user interface that the actor authenticates through, if any.
          type: string
        - name: authenticatorProvider
          description: 'DEPRECATED: This field is kept here for backwards compatibility.'
          type: string
    - name: securityContext
      description: The security data of an action
      type: object
      fields:
        - name: asNumber
          description: Autonomous system number associated with the autonomous system that the event request was sourced to
          type: bigint
        - name: asOrg
          description: Organization associated with the autonomous system that the event request was sourced to
          type: string
        - name: isp
          description: Internet service provider used to sent the event's request
          type: string
        - name: domain
          description: The domain name associated with the IP address of the inbound event request
          type: string
          indicators:
            - domain
        - name: isProxy
          description: Specifies whether an event's request is from a known proxy
          type: boolean

To create an Okta API token with permissions to query System Logs, you must be logged in as one of the following types of Okta administrator: a , , or .

We recommend using a role, for least privilege.

See for more information on managing administrator roles.

Okta subdomain: Enter the subdomain of your Okta organization domain. You can refer to to find out more about your Okta org domain.

On the Enrichment page, if you would like to enable , to the right of User Profiles and/or Device Profiles, click the toggle ON.

Note .

You can optionally enable one or more .

See the Panther-built .

- A user has been granted administrative privileges in Okta

- A user created an API Key in Okta

- A user has revoked an API Key in Okta

- A user has subsequent logins from two geographic locations that are very far apart

- Okta system-wide MFA has been disabled by an Admin user

- Okta Support reset a password or MFA for a user

- Okta support access was granted

Have other Okta detections that can be used by other customers? Consider sharing detections back to the repository or work with your Customer Success team!

Below are some common functions and example deep_get() uses when writing custom detections for Okta. Explanations on different event types can be found in the Okta .

Reference:

super administrator
organization administrator
read-only administrator
read-only administrator
Okta's documentation
Okta documentation
Okta Identity Profiles
Detection Packs
rules and investigative queries for Okta in panther-analysis in Github
Okta Admin Role Assigned
Okta API Key Created
Okta API Key Revoked
Geographically Improbable Okta Login
Okta MFA Globally Disabled
Okta Support Reset Credential
Okta Support Access Granted
Panther Analysis
documentation
Okta Documentation on System Log APIs.
Okta System Log API
Okta user and device profiles
Video walkthrough showing how to onboard Okta logs to Panther
On the Enrichment settings page of the Create Okta source flow, there are toggles for User Profiles and Device Profiles. Next to each of the toggles is a Refresh period (min) field.
The success screen reads, "Everything looks good! Panther will now automatically pull & process logs from your account"
The "Trigger an alert when no events are processed" toggle is set to YES. The "How long should Panther wait before it sends you an alert that no events have been processed" setting is set to 1 Day
the prerequisite for enabling Okta device profiles