Okta — CraftedSignal Threat Feed

Unusual Spike in Okta User Lifecycle Management Change Events

hello@craftedsignal.io — Sat, 02 Nov 2024 12:00:00 +0000

This alert detects potential privileged access activity within an Okta environment. The detection is triggered by a machine learning job that identifies anomalous spikes in user lifecycle management change events. Threat actors may target user accounts to escalate their privileges or to establish persistence within the environment. This is achieved by manipulating user accounts, such as modifying roles, permissions, or other attributes. The prebuilt ML job “pad_okta_spike_in_user_lifecycle_management_changes_ea” is used to detect these anomalies. The rule requires the Privileged Access Detection integration assets to be installed, as well as Okta logs collected by integrations such as Okta. The rule looks for activity within a 3-hour window, checking every 15 minutes.

Attack Chain

An attacker gains initial access to an Okta account, possibly through compromised credentials or other means. (T1078)
The attacker begins enumerating user accounts and their associated roles and permissions within the Okta environment.
The attacker identifies a target user account with elevated privileges or a role that would grant them desired access.
The attacker modifies the target user account’s attributes, such as adding the attacker’s account to a privileged group or changing the user’s role. (T1098)
The attacker leverages the newly acquired privileges to access sensitive resources or perform unauthorized actions.
The attacker may create new user accounts with elevated privileges to maintain persistent access to the environment. (T1098)
The attacker covers their tracks by deleting logs or modifying audit trails to conceal their activity.
The attacker achieves their objective, such as data exfiltration or system compromise.

Impact

A successful attack can result in privilege escalation, allowing unauthorized access to sensitive data and systems. Depending on the level of access gained, attackers may be able to compromise critical infrastructure, steal confidential information, or disrupt business operations. The impact can range from minor data breaches to significant financial losses and reputational damage. Early detection of anomalous user lifecycle changes is crucial to mitigating these risks.

Recommendation

Ensure the Privileged Access Detection integration is installed and properly configured, including the preconfigured anomaly detection job “pad_okta_spike_in_user_lifecycle_management_changes_ea”.
Investigate any alerts generated by this rule by following the investigation steps outlined in the rule’s note section within the Kibana UI.
Review and update access management policies and procedures to prevent similar incidents in the future, ensuring that changes to user accounts are logged and regularly reviewed as described in the rule’s documentation.
Monitor Okta logs for any unusual or unauthorized activity, focusing on user account changes, as described in the setup documentation.
Implement additional monitoring on the affected accounts and related systems to detect any further suspicious activity or attempts to regain unauthorized access as mentioned in the response and remediation guidelines.

Okta Admin Console Unusual Behavior Detection

hello@craftedsignal.io — Thu, 02 May 2024 10:00:00 +0000

This threat brief focuses on detecting unusual behaviors within the Okta Admin Console, as identified by Okta’s heuristics. While the specific campaign details are unknown, identifying anomalous access patterns to the Admin Console is crucial for detecting various malicious activities. This includes potential privilege escalation by compromised accounts or insider threats attempting to gain elevated permissions, establishing persistence through unauthorized modifications, evading existing security controls, or gaining initial access through account compromise. The detection relies on Okta’s system logs which can signal unusual administrative activity. Defenders should prioritize monitoring and alerting on these events to quickly identify and respond to potential security breaches.

Attack Chain

An attacker gains initial access to an Okta account, possibly through credential phishing or brute-force attacks.
The attacker attempts to log in to the Okta Admin Console.
Okta’s behavior detection engine analyzes the login attempt, considering factors like the user’s location, device, and time of day.
The system logs record a policy.evaluate_sign_on event when a sign-on policy is evaluated.
The target.displayName field within the log specifies “Okta Admin Console” indicating the user is attempting to access the administrative interface.
If Okta identifies the behavior as unusual, the debugContext.debugData.behaviors or debugContext.debugData.logOnlySecurityData fields will contain “POSITIVE”.
An alert is triggered based on the identified unusual behavior.
The attacker, if successful in bypassing initial checks, may proceed to create new admin accounts, modify existing policies, or exfiltrate sensitive data.

Impact

Compromise of the Okta Admin Console can lead to significant damage, including unauthorized access to sensitive data, modification of security policies, creation of rogue administrator accounts, and ultimately, a complete takeover of the Okta environment. This can impact all applications and services integrated with Okta, potentially affecting thousands of users and causing significant financial and reputational damage. Early detection is crucial to limiting the scope and impact of such attacks.

Recommendation

Deploy the provided Sigma rule Okta Admin Console Unusual Behavior to your SIEM to detect suspicious Okta Admin Console access based on Okta’s internal behavior analysis.
Investigate any alerts generated by the Sigma rule to determine if the unusual behavior is legitimate or indicative of malicious activity.
Review Okta’s System Log API documentation to understand the various event types and data fields available for monitoring and detection.
Implement multi-factor authentication (MFA) for all Okta accounts, especially administrator accounts, to mitigate the risk of account compromise (related to initial access).
Monitor Okta’s security advisories and announcements for updates on emerging threats and recommended security practices (references).

Okta Password Entered in AlternateID Field

hello@craftedsignal.io — Thu, 29 Feb 2024 12:00:00 +0000

Okta, a leading identity and access management provider, retains login attempt data in its system logs. This data can be valuable for security monitoring and incident response. However, a misconfiguration or user error can lead to sensitive information, such as passwords, being inadvertently captured within these logs. Specifically, if a user mistakenly enters their password in the username field (referred to as ‘alternateId’ in Okta logs) during a failed login attempt, the password may be stored in plain text within the log entry. This exposes the password to anyone with access to Okta system logs. This issue was highlighted in a Mitiga blog post, underscoring the risk to user data. Defenders must implement measures to detect and prevent such occurrences to maintain the confidentiality of user credentials and the overall security posture.

Attack Chain

User attempts to log in to an Okta-protected application.
The user mistakenly enters their password in the username (alternateId) field.
The Okta authentication process fails due to incorrect credentials.
Okta logs the failed login attempt, including the ‘core.user_auth.login_failed’ event.
The password, entered in the alternateId field, is recorded in the Okta system log.
An attacker gains unauthorized access to Okta system logs, potentially through compromised credentials or a misconfigured integration.
The attacker searches for ‘core.user_auth.login_failed’ events and examines the ‘actor.alternateId’ field.
The attacker discovers exposed passwords within the ‘actor.alternateId’ field, potentially enabling account takeover or further lateral movement.

Impact

A successful attack exploiting this vulnerability could lead to widespread credential compromise. The number of potentially affected users depends on how frequently users make this mistake and the duration for which logs are retained. Sectors heavily reliant on Okta for authentication, such as technology, finance, and healthcare, are particularly at risk. If passwords are leaked, attackers can gain unauthorized access to sensitive data, applications, and systems, leading to data breaches, financial loss, and reputational damage.

Recommendation

Deploy the provided Sigma rule “Okta Password Entered in AlternateID Field” to your SIEM to detect instances of passwords potentially being logged in the actor.alternateId field.
Review and adjust the regular expression in the Sigma rule’s filter_main section to align with the specific character restrictions in your Okta username configuration.
Implement stricter input validation on Okta login pages to prevent users from entering passwords in the username field.
Regularly audit Okta system logs for sensitive information and enforce least privilege access to log data.
Educate users about the proper use of login forms to reduce the likelihood of entering passwords in the username field.
Implement multi-factor authentication (MFA) to mitigate the impact of compromised passwords, as referenced in security best practices.

Okta Policy Rule Modification or Deletion

hello@craftedsignal.io — Mon, 29 Jan 2024 12:00:00 +0000

Okta is a widely used identity and access management platform. Threat actors may target Okta configurations to weaken an organization’s security posture. This activity involves modifications or deletions of policy rules within Okta. Such changes can reduce the effectiveness of multi-factor authentication (MFA) requirements, bypass access controls, or disable security logging. Detection of these changes is crucial to maintaining a strong security baseline and preventing unauthorized access to sensitive resources. Defenders should monitor Okta logs for unexpected or unauthorized policy rule modifications or deletions.

Attack Chain

Initial Access: The attacker gains unauthorized access to an Okta administrator account, possibly through credential theft or phishing.
Authentication: The attacker authenticates to the Okta admin dashboard using the compromised credentials.
Discovery: The attacker enumerates existing policy rules to understand the current security configuration.
Modification: The attacker modifies an existing policy rule to weaken its security controls. This could involve disabling MFA, bypassing location restrictions, or altering group membership requirements.
Deletion: Alternatively, the attacker deletes a policy rule entirely, effectively removing a layer of security.
Privilege Escalation: With weakened or removed policy rules, the attacker escalates privileges, gaining access to sensitive applications or data.
Lateral Movement: The attacker leverages the compromised Okta environment to move laterally within the organization’s network, accessing additional systems and resources.
Impact: The attacker achieves their final objective, such as data exfiltration, financial fraud, or system disruption, due to the weakened security posture.

Impact

Successful modification or deletion of Okta policy rules can severely compromise an organization’s security. Consequences include unauthorized access to sensitive data, privilege escalation, lateral movement, and ultimately, data breaches or financial loss. The number of affected users and systems depends on the scope of the compromised policy rules and the attacker’s subsequent actions. Organizations in all sectors that rely on Okta for identity management are vulnerable.

Recommendation

Deploy the “Okta Policy Rule Modified or Deleted” Sigma rule to your SIEM to detect unauthorized changes (rule reference).
Review Okta system logs regularly for policy rule modifications or deletions, focusing on unusual source IPs or user agents.
Implement multi-factor authentication (MFA) for all Okta administrator accounts to prevent unauthorized access (reference: Okta documentation).
Enforce the principle of least privilege for Okta administrator roles, limiting the number of users who can modify policy rules.
Alert on eventType policy.rule.update or policy.rule.delete in Okta logs using the provided Sigma rule (rule reference).

Okta Network Zone Deactivation or Deletion

hello@craftedsignal.io — Fri, 26 Jan 2024 18:22:00 +0000

Okta network zones define trusted network boundaries for user access. These zones are configured with specific IP address ranges and can be used to restrict access to applications and resources. When an Okta network zone is deactivated or deleted, it can indicate a malicious actor attempting to weaken security policies, potentially allowing unauthorized access from untrusted locations. This activity is relevant for defenders because it may signal a breach in progress or preparation for future attacks. Compromised administrator accounts are often used to make unauthorized configuration changes in SaaS platforms. This alert focuses on activity within the Okta platform itself.

Attack Chain

An attacker gains unauthorized access to an Okta administrator account, potentially through credential theft or phishing.
The attacker authenticates to the Okta administrative console.
The attacker navigates to the network zone configuration within the Okta admin console.
The attacker identifies a target network zone that restricts access to critical resources.
The attacker deactivates the target network zone, effectively disabling its restrictions. Alternatively, the attacker deletes the network zone.
The attacker may modify other security settings, such as MFA policies, to further weaken the security posture.
The attacker leverages the relaxed network restrictions to access sensitive applications or data from previously unauthorized locations.
The attacker performs malicious actions, such as data exfiltration or lateral movement, using the compromised Okta session.

Impact

The deactivation or deletion of an Okta network zone can have serious consequences. It can lead to unauthorized access to sensitive applications and data, potentially resulting in data breaches, financial loss, and reputational damage. The impact is especially high if the affected network zone was protecting critical infrastructure or sensitive customer data. Depending on the scope of access granted, a single deactivated zone could expose data belonging to thousands of users.

Recommendation

Deploy the “Okta Network Zone Deactivated or Deleted” Sigma rule to your SIEM to detect this activity (logsource: okta, service: okta, eventType: zone.deactivate/zone.delete).
Investigate any detected instances of network zone deactivation or deletion to determine if they were authorized changes.
Review Okta administrator account activity for signs of compromise, such as login attempts from unusual locations.
Enforce multi-factor authentication (MFA) for all Okta administrator accounts to prevent unauthorized access.
Monitor the Okta system logs for other suspicious configuration changes, such as modifications to MFA policies or application assignments.

Okta Identity Provider Creation Detected

hello@craftedsignal.io — Thu, 25 Jan 2024 12:00:00 +0000

The creation of a new identity provider (IdP) in Okta is a sensitive action that should be closely monitored. While legitimate administrators may create IdPs for federation purposes, adversaries can abuse this functionality to establish persistence or escalate privileges within an Okta environment. This involves creating a malicious IdP that they control and configuring it to authenticate users, potentially bypassing existing security controls such as multi-factor authentication (MFA) or implementing cross-tenant impersonation. The creation of a rogue IdP within Okta can be an indicator of compromise, potentially leading to unauthorized access to applications and data protected by Okta. Defenders should monitor Okta system logs for the creation of new identity providers and validate their legitimacy.

Attack Chain

An attacker gains initial access to an Okta tenant with sufficient administrative privileges, either through compromised credentials or by exploiting a vulnerability.
The attacker navigates to the Okta admin console.
The attacker creates a new identity provider (IdP) within the Okta tenant (system.idp.lifecycle.create).
The attacker configures the rogue IdP with attacker-controlled settings, such as SAML endpoints or OIDC configurations, potentially pointing to an attacker-controlled server.
The attacker configures routing rules within Okta to direct specific users or groups to authenticate through the newly created, malicious IdP.
Users attempting to access Okta-protected applications are redirected to the attacker-controlled IdP for authentication.
The attacker’s IdP captures user credentials or issues fraudulent authentication tokens, allowing the attacker to impersonate legitimate users.
The attacker leverages the stolen credentials or fraudulent tokens to access sensitive applications and data protected by Okta, achieving their objective of data theft or service disruption.

Impact

A successful attack involving the creation of a rogue Okta identity provider can lead to significant consequences. Attackers can gain persistent access to the Okta environment, bypass multi-factor authentication, and impersonate legitimate users. This can result in unauthorized access to sensitive applications and data, data breaches, financial loss, and reputational damage. The scope of the impact depends on the privileges of the compromised accounts and the sensitivity of the data accessed.

Recommendation

Deploy the Sigma rule “Okta Identity Provider Created” to your SIEM to detect the creation of new identity providers and tune it for your environment.
Regularly review and validate all configured identity providers within your Okta tenant to ensure their legitimacy.
Implement strong access controls and multi-factor authentication for all Okta administrative accounts to prevent unauthorized creation of identity providers.
Monitor Okta system logs for suspicious activity related to identity provider configuration and authentication.
Investigate any alerts triggered by the “Okta Identity Provider Created” Sigma rule to determine the legitimacy of the IdP creation event.

Okta User Account Created

hello@craftedsignal.io — Tue, 23 Jan 2024 12:00:00 +0000

This alert detects the creation of new user accounts within an Okta environment. While legitimate user creation is common, malicious actors may create accounts to gain unauthorized access to resources, escalate privileges, or establish persistence within the network. Monitoring for anomalous user creation activity, such as accounts created outside of normal business hours or with suspicious naming conventions, is crucial for identifying potential security breaches. Reviewing the source IP and administrator account used for the user creation can also provide valuable context.

Attack Chain

An attacker gains initial access to an Okta administrator account, potentially through phishing, credential stuffing, or exploiting a vulnerability.
The attacker authenticates to the Okta admin portal.
The attacker navigates to the user management section within the Okta admin console.
The attacker creates a new user account, potentially mimicking an existing user or using a generic naming convention.
The attacker assigns the new user account specific roles and permissions, potentially granting elevated privileges.
The attacker may use the newly created account to access sensitive applications and data within the Okta-protected environment.
The attacker uses the compromised or newly created account to maintain persistence within the Okta environment.

Impact

A successful attack leading to unauthorized user creation can result in significant data breaches, privilege escalation, and unauthorized access to sensitive applications and resources. This could lead to financial loss, reputational damage, and compliance violations. The impact depends on the permissions granted to the created user and the applications they can access.

Recommendation

Deploy the Sigma rule “New Okta User Created” to your SIEM to detect user creation events and tune for your environment.
Investigate any detected user creation events for legitimacy, focusing on the source IP address and the administrator account used.
Implement multi-factor authentication (MFA) for all Okta administrator accounts to mitigate the risk of credential compromise.
Review Okta event logs regularly for suspicious activity, including user creation, permission changes, and application access.
Establish baseline user creation patterns to identify anomalous behavior, such as accounts created outside of normal business hours.

Okta Security Threat Detected

hello@craftedsignal.io — Tue, 23 Jan 2024 12:00:00 +0000

This alert focuses on identifying security threats detected by Okta’s ThreatInsight. Okta ThreatInsight analyzes traffic patterns and user behavior to identify and block malicious login attempts, brute-force attacks, and other suspicious activities. When ThreatInsight identifies a security threat, it generates a system log event with the eventType security.threat.detected. This event serves as a high-level indicator of potential command and control activity within the Okta environment. Defenders should investigate these alerts promptly to determine the nature and scope of the threat and take appropriate remediation steps. This detection leverages Okta system logs and is relevant for organizations using Okta as their identity provider.

Attack Chain

An attacker attempts to gain unauthorized access to an Okta account, possibly through credential stuffing or brute-force attacks.
Okta’s ThreatInsight analyzes the login attempt, evaluating factors such as IP address reputation, geographical location, and login frequency.
ThreatInsight identifies the login attempt as a security threat based on predefined risk factors.
Okta generates a system log event with eventType security.threat.detected, recording details of the suspicious activity.
The security team receives an alert based on the Sigma rule detecting the security.threat.detected event.
The security team investigates the alert, examining the associated IP address, user account, and other relevant log data.
Based on the investigation, the security team takes appropriate remediation steps, such as blocking the IP address, resetting the user’s password, or enabling multi-factor authentication.

Impact

A successful attack targeting Okta could lead to unauthorized access to sensitive data, account takeover, and disruption of services. The impact of such an attack depends on the level of access granted to the compromised account and the sensitivity of the data accessible through Okta. Successful exploitation can lead to lateral movement within an organization’s cloud infrastructure and potentially compromise other critical systems.

Recommendation

Deploy the provided Sigma rule to your SIEM to detect security.threat.detected events in Okta system logs.
Investigate all triggered alerts to determine the nature and scope of the threat.
Review Okta’s ThreatInsight configuration to ensure it is properly configured and tuned for your environment (references: Okta ThreatInsight documentation).
Monitor Okta system logs for suspicious activity, such as unusual login patterns, account lockouts, and password resets (references: Okta system log documentation).
Enforce strong password policies and multi-factor authentication to reduce the risk of unauthorized access.

Okta Admin Role Assignment Creation

hello@craftedsignal.io — Tue, 23 Jan 2024 12:00:00 +0000

Okta is a widely used identity and access management (IAM) platform, making it a prime target for malicious actors seeking to gain unauthorized access to sensitive resources. This threat focuses on the creation of new admin role assignments within Okta. An attacker who successfully compromises an Okta account with sufficient privileges, or bypasses security controls, may attempt to escalate their privileges or establish persistence by creating new admin role assignments for themselves or other accounts they control. This activity can go unnoticed if not actively monitored, granting the attacker extended access and control over the Okta environment and connected applications. Monitoring for anomalous admin role assignments is crucial for early detection and prevention of potential breaches.

Attack Chain

Initial Access: Attacker gains unauthorized access to an Okta account, possibly through credential phishing, brute-force attacks, or exploitation of vulnerabilities.
Privilege Check: The attacker verifies the privileges of the compromised account to determine if it has sufficient permissions to create new admin role assignments.
Account Impersonation: The attacker uses the compromised account to access the Okta admin dashboard.
Role Assignment Creation: The attacker navigates to the role assignment section and initiates the creation of a new admin role assignment.
Configuration: The attacker specifies the target user or group for the new admin role assignment.
Audit Logging: Okta logs the event ‘iam.resourceset.bindings.add’ indicating the creation of a new admin role assignment.
Persistence: The attacker uses the newly created admin role assignment to maintain persistent access to the Okta environment even if the initial compromised account is detected and remediated.

Impact

Successful exploitation could lead to complete control over the Okta environment, affecting all connected applications and services. An attacker with admin privileges can modify user accounts, reset passwords, access sensitive data, and potentially compromise the entire organization. The number of affected users and systems depends on the scope of the Okta deployment, but the impact can be significant, potentially affecting thousands of users and critical business operations.

Recommendation

Deploy the Sigma rule Okta Admin Role Assignment Created to your SIEM and tune it for your environment to detect suspicious admin role creation activity in Okta logs.
Investigate any alerts generated by the Okta Admin Role Assignment Created rule to determine if the role assignment was legitimate and authorized.
Implement multi-factor authentication (MFA) for all Okta accounts, especially those with administrative privileges, to mitigate the risk of credential compromise.
Regularly review and audit Okta admin role assignments to identify and remove any unnecessary or unauthorized privileges.

Okta End-User Reports Suspicious Account Activity

hello@craftedsignal.io — Wed, 17 Jan 2024 12:00:00 +0000

This alert focuses on detecting when an end-user within an Okta environment reports suspicious activity related to their account. This is a critical indicator that the account may be compromised, or that unauthorized access has occurred. The activity is reported directly by the end-user. While this alert does not directly reveal the method of compromise, it serves as an important signal for security teams to investigate potentially malicious activity. This event triggers from an Okta system log event generated when an end-user utilizes the “report suspicious activity” feature, available in many Okta deployments. Early detection allows security teams to rapidly respond, contain potential damage, and investigate the source of the suspicious activity. This type of self-reporting by end-users can be an invaluable source of threat intelligence within an organization.

Attack Chain

An attacker gains unauthorized access to an end-user’s Okta account, possibly via credential phishing or password reuse.
The attacker attempts to perform actions such as accessing applications, changing profile details, or initiating password resets.
The legitimate end-user observes suspicious activity in their Okta account, such as unfamiliar login locations, unauthorized application access, or unexpected password reset requests.
The end-user utilizes the “report suspicious activity” feature within their Okta account portal.
This action generates an Okta system log event with the eventType user.account.report_suspicious_activity_by_enduser.
The detection rule triggers based on this specific Okta log event.
Security analysts investigate the reported activity, examining Okta logs and other relevant data sources.
Based on the investigation, appropriate remediation steps are taken, such as resetting the user’s password, revoking active sessions, and blocking any identified malicious IP addresses.

Impact

A successful account compromise can lead to unauthorized access to sensitive applications and data within the organization. The number of affected users and the impact will depend on the permissions and access granted to the compromised Okta account. This can result in data breaches, financial loss, and reputational damage. Prompt detection of end-user reported suspicious activity allows for rapid incident response, minimizing potential damage.

Recommendation

Deploy the Sigma rule “Okta Suspicious Activity Reported by End-user” to your SIEM to detect when users report suspicious activity, using eventType: 'user.account.report_suspicious_activity_by_enduser'.
Review Okta system logs for further details surrounding the events that prompted the user report (see references for log details).
Implement end-user training programs to educate users on how to identify and report suspicious activity.
Investigate all triggered alerts to determine the root cause of the reported suspicious activity.

Okta Group Lifecycle Change Spike Indicating Privilege Escalation

hello@craftedsignal.io — Tue, 09 Jan 2024 12:00:00 +0000

This alert identifies potential privileged access activity within Okta environments by detecting unusual spikes in group lifecycle change events. The activity is detected using Elastic’s Anomaly Detection feature. Adversaries may manipulate group structures to achieve privilege escalation, establish persistence, or move laterally within an organization. The anomaly detection job, pad_okta_spike_in_group_lifecycle_changes_ea, monitors these changes. This activity matters because unauthorized group modifications can grant attackers elevated permissions, compromise sensitive data, and disrupt normal business operations. The detection is based on machine learning analysis of Okta logs collected via an integration.

Attack Chain

Initial Compromise: An attacker gains initial access to a user account, possibly through credential theft or phishing (not directly observed, but a common precursor).
Account Enumeration: The attacker enumerates existing groups and their memberships within the Okta environment.
Group Manipulation: The attacker initiates unauthorized group lifecycle changes, such as adding or removing members, to escalate privileges.
Privilege Escalation: By adding their compromised account to a privileged group (e.g., Okta administrators, application owners), the attacker gains elevated access.
Lateral Movement: The attacker leverages their newly acquired privileges to access other systems or applications within the organization’s network.
Persistence: The attacker modifies group memberships to maintain persistent access even if their initial access is revoked (T1098.007).
Data Access/Exfiltration: The attacker accesses sensitive data or resources that were previously inaccessible due to insufficient privileges.

Impact

A successful attack can lead to unauthorized access to sensitive data, compromise of critical systems, and disruption of business operations. The number of victims and the scope of the impact depend on the level of access achieved by the attacker and the sensitivity of the compromised data. While the alert is low severity, the potential consequences of privilege escalation are significant, requiring prompt investigation and remediation.

Recommendation

Investigate triggered alerts by reviewing the specific group lifecycle change events that triggered the alert in Okta logs to identify which groups were altered and the nature of the changes.
Examine the user accounts associated with the changes to determine if they have a history of suspicious activity or if they have recently been granted elevated privileges using the provided investigation steps.
Tune the machine learning job anomaly threshold anomaly_threshold in the rule configuration to reduce false positives based on your environment’s baseline.

Unusual Source IP for Okta Privileged Operations Detected

hello@craftedsignal.io — Tue, 09 Jan 2024 10:00:00 +0000

This alert leverages machine learning to identify deviations in IP usage patterns associated with privileged Okta operations, flagging unusual access attempts that could signify privilege escalation or account compromise. It identifies a user performing privileged operations in Okta from an uncommon source IP, potentially indicating account compromise, misuse of administrative privileges, or an attacker leveraging a new network location. The detection rule analyzes Okta logs, specifically focusing on events related to privileged operations and source IP addresses, to establish baseline behavior and detect anomalies. This detection is important because Okta controls access to many downstream applications, and any compromise of Okta privileges can lead to widespread data breaches. The rule requires the Privileged Access Detection integration assets to be installed, as well as Okta logs collected by integrations such as Okta. The minimum stack version is 9.4.0

Attack Chain

Adversary gains initial access to a valid user account through phishing, credential stuffing, or other means (T1078, T1078.004).
The adversary leverages the compromised account to authenticate to Okta, potentially bypassing or circumventing MFA.
The adversary attempts to perform privileged operations within Okta, such as modifying user permissions, accessing sensitive applications, or changing security settings.
Okta logs record the privileged operation attempt, including the source IP address of the request.
The machine learning job analyzes the source IP address and compares it to the user’s historical access patterns.
If the source IP address is determined to be unusual or rare for the user, the machine learning job generates an anomaly.
The “Unusual Source IP for Okta Privileged Operations Detected” rule triggers based on the anomaly score exceeding a predefined threshold (anomaly_threshold = 75).
The alert triggers, potentially leading to account takeover, data exfiltration, or further privilege escalation.

Impact

A successful attack can lead to unauthorized access to sensitive applications and data managed by Okta. This can result in data breaches, financial loss, reputational damage, and legal liabilities. Since Okta is a widely used identity management service, a compromise can impact numerous downstream applications and services that rely on Okta for authentication and authorization. The number of affected users and systems can vary depending on the scope of the privileged access and the attacker’s objectives.

Recommendation

Install the Privileged Access Detection integration assets, as well as Okta logs collected by integrations such as Okta, as described in the “Setup” section of the rule to enable the machine learning job.
Review the source IP address flagged by the alert to determine its geolocation and assess if it aligns with the user’s typical access patterns or known locations, as described in the rule’s “Triage and analysis” section.
Tune the anomaly_threshold parameter in the machine learning job based on your environment to reduce false positives.
Correlate the flagged IP address with any known threat intelligence feeds to check for any history of malicious activity associated with it, as described in the rule’s “Triage and analysis” section.

Okta Session Hijacking via Multiple Device Token Hashes

hello@craftedsignal.io — Wed, 03 Jan 2024 18:41:22 +0000

This threat brief addresses the risk of Okta session hijacking, where adversaries may steal session cookies or tokens to gain unauthorized access to Okta resources. The alert focuses on detecting anomalous Okta sessions characterized by multiple device token hashes and source IP addresses associated with a single authenticated user. This activity may indicate that an authenticated session has been compromised and is being replayed from different devices or networks. Defenders should be aware of the potential for attackers to leverage stolen sessions to access the Okta admin console, applications, tenants, and other sensitive resources. Elastic has published a rule to detect this behavior, last updated on April 13, 2026, which can be used to proactively identify potentially compromised Okta sessions within the environment.

Attack Chain

Initial Access: An attacker gains access to a valid Okta session token or cookie through methods such as phishing or malware.
Session Token Theft: The attacker steals a valid Okta session token/cookie from a compromised endpoint.
Session Replay: The attacker replays the stolen session token/cookie from a different device and network location than the original user.
Okta Authentication: The replayed session token authenticates to Okta, creating a new session instance.
Multiple Device Hashes: Because the session is accessed from a different device, a new device token hash is generated. The attacker may also use proxy services from different locations.
Unauthorized Access: The attacker uses the hijacked session to access Okta resources, such as the admin console or applications.
Privilege Escalation (Optional): If the hijacked session belongs to a privileged user, the attacker may escalate privileges within the Okta environment.
Data Exfiltration/Manipulation: The attacker exfiltrates sensitive data or modifies Okta configurations to establish persistence or further compromise the environment.

Impact

A successful Okta session hijacking attack can lead to unauthorized access to sensitive applications and data, privilege escalation, and disruption of business operations. The impact can range from data breaches and financial loss to reputational damage and regulatory fines. Attackers can potentially access and modify user accounts, security policies, and application integrations. The number of potential victims depends on the scope of the attacker’s access and the sensitivity of the data they can access.

Recommendation

Deploy the provided Sigma rule to your SIEM to detect multiple device token hashes and source IPs for single Okta sessions and tune for your environment.
Investigate alerts generated by the Sigma rule by pivoting into Okta system logs using the okta.actor.alternate_id and okta.authentication_context.external_session_id fields.
Monitor Okta system logs for suspicious post-authentication activity, such as admin console access, policy changes, or application assignment modifications as described in the rule’s triage steps.
Enforce MFA enrollment for all Okta users to mitigate the risk of session hijacking and credential theft, as recommended in the investigation guide.
Revoke active sessions and reset passwords for affected users exhibiting suspicious activity as mentioned in the false positive analysis.

Okta Alerts Following Unusual Proxy Authentication

hello@craftedsignal.io — Wed, 03 Jan 2024 15:00:00 +0000

Attackers frequently use proxy infrastructure (VPNs, Tor, residential proxies) to mask their origin when using stolen credentials. This behavior often triggers additional detection rules after the initial authentication. By correlating the first instance of Okta user authentication via a proxy with subsequent Okta security alerts for the same user, this rule aims to identify potentially compromised accounts. This correlation focuses on activity within a 30-minute window following the initial proxy authentication, helping to pinpoint users whose proxy-based authentication was followed by suspicious activity. The rule leverages Okta system logs and alerts to identify these patterns. This is important for defenders to quickly identify compromised accounts and prevent further damage.

Attack Chain

An attacker obtains valid Okta credentials through phishing, credential stuffing, or other means. (T1078)
The attacker initiates an Okta user session from behind a proxy (VPN, Tor, etc.) to mask their origin.
Okta classifies the connection as originating from a proxy.
The user successfully authenticates and starts a session.
Post-authentication, the attacker attempts to access sensitive applications or data. (T1078.004)
The attacker’s activity triggers an Okta security alert, such as unusual access patterns or MFA bypass attempts.
The detection rule correlates the proxy authentication event with the subsequent security alert.
Security team investigates and responds to the potential account compromise.

Impact

A successful attack can lead to unauthorized access to sensitive data, privilege escalation, and lateral movement within the organization’s cloud environment. Multiple alerts, coupled with proxy authentication, indicate a higher likelihood of account compromise. If successful, attackers could exfiltrate sensitive data, modify configurations, or disrupt services.

Recommendation

Deploy the Sigma rule “Okta Alerts Following Unusual Proxy Authentication” to your SIEM and tune for your environment to detect suspicious activity after proxy authentication.
Investigate correlated security alerts triggered after proxy authentication events for affected users, as highlighted by the Sigma rule.
Monitor Okta system logs for authentication events originating from known malicious proxy IP addresses and block them at the network perimeter.
Review user’s Okta activity for signs of account takeover (MFA changes, new devices, unusual app access) after proxy authentication.
Implement multi-factor authentication (MFA) to reduce the risk of account compromise via stolen credentials, as this attack relies on valid accounts.

Okta Policy Modification or Deletion Detected

hello@craftedsignal.io — Wed, 03 Jan 2024 12:00:00 +0000

This alert identifies modifications or deletions of Okta policies, which govern authentication, authorization, and access control within the Okta Identity Cloud platform. While legitimate administrators routinely update policies, unauthorized changes can weaken security postures and grant malicious actors elevated privileges or bypass security controls. The source event indicates a potential compromise or insider threat activity within the Okta environment. Because Okta serves as a critical identity provider for many organizations, any unauthorized change to its policies can have far-reaching consequences. Detecting policy changes is crucial for maintaining the integrity and security of the Okta environment and preventing potential breaches. The targeted scope includes all Okta-managed applications and resources protected by the modified or deleted policy.

Attack Chain

Initial Access: The attacker gains access to an Okta administrator account, either through compromised credentials (e.g., phishing, credential stuffing) or insider access.
Authentication: The attacker authenticates to the Okta admin console using the compromised or legitimate administrator account.
Policy Enumeration: The attacker identifies target Okta policies to modify or delete using the Okta admin console or API.
Policy Modification/Deletion: The attacker modifies or deletes the targeted Okta policy through the Okta admin console or API. This generates an policy.lifecycle.update or policy.lifecycle.delete event.
Privilege Escalation (Potential): By modifying policies, the attacker may escalate privileges, granting themselves or other unauthorized users access to sensitive applications and resources.
Lateral Movement (Potential): With escalated privileges, the attacker moves laterally within the Okta environment, accessing other applications and resources.
Data Exfiltration/Damage (Potential): The attacker leverages the compromised Okta environment to exfiltrate sensitive data or cause damage to connected systems.

Impact

A successful Okta policy modification or deletion can have significant consequences. Unauthorized policy changes can weaken security controls, allowing attackers to bypass authentication mechanisms, escalate privileges, and gain unauthorized access to sensitive applications and data. This could lead to data breaches, financial loss, and reputational damage. The impact depends on the scope of the affected policy and the applications it protects. The number of victims could range from a few individuals to the entire organization, depending on the scope of the compromised policy.

Recommendation

Deploy the provided Sigma rule to your SIEM to detect Okta policy modifications or deletions (policy.lifecycle.update, policy.lifecycle.delete event types).
Investigate any detected policy changes to verify their legitimacy and identify the user responsible.
Review Okta administrator account activity for any signs of compromise or unauthorized access.
Implement multi-factor authentication (MFA) for all Okta administrator accounts to prevent unauthorized access.
Regularly review and audit Okta policies to ensure they are configured securely and in accordance with security best practices.

Okta MFA Reset or Deactivation Attempt

hello@craftedsignal.io — Wed, 03 Jan 2024 12:00:00 +0000

Attackers may attempt to disable or reset MFA to bypass security controls and gain unauthorized access to user accounts. This activity is often part of a broader attack campaign, such as credential stuffing or account takeover. The Okta platform provides detailed logs of user authentication events, including MFA resets and deactivations. Monitoring these events is crucial for detecting and responding to potential account compromise attempts. These attempts can originate from various sources, including compromised administrator accounts or direct attacks on user accounts. The impact of successful MFA bypass can be significant, potentially leading to data breaches, financial loss, and reputational damage.

Attack Chain

The attacker gains initial access to a user’s Okta account, possibly through phishing or credential compromise.
The attacker authenticates to the Okta tenant using the compromised credentials.
The attacker initiates a request to reset or deactivate one or more of the user’s MFA factors through the Okta API or web interface.
Okta generates a system log event of type user.mfa.factor.deactivate or user.mfa.factor.reset_all.
If successful, the attacker can then authenticate without providing the MFA factor, bypassing a critical security control.
The attacker leverages the compromised account to access sensitive applications and data within the Okta environment.
The attacker may perform lateral movement to access other user accounts or systems.
The final objective may include data exfiltration, financial fraud, or other malicious activities.

Impact

Successful MFA deactivation or reset can lead to complete account takeover. Depending on the compromised user’s role and access permissions, this could result in significant data breaches, unauthorized access to sensitive systems, and financial losses. The impact scales with the number of compromised accounts and the sensitivity of the data they can access. This activity targets all sectors relying on Okta for identity and access management.

Recommendation

Deploy the provided Sigma rules to your SIEM to detect suspicious MFA reset or deactivation attempts in Okta logs.
Investigate any triggered alerts for user.mfa.factor.deactivate or user.mfa.factor.reset_all events, as described in the Sigma rule.
Review Okta system logs for unusual authentication patterns, focusing on users with recently deactivated MFA factors, as detailed in the Okta API documentation.
Implement strict access controls and monitoring for Okta administrator accounts to prevent unauthorized MFA modifications.
Educate users about phishing and credential security to reduce the risk of initial access compromise.

Okta Group Privilege Change Spike via ML Detection

hello@craftedsignal.io — Wed, 03 Jan 2024 12:00:00 +0000

This alert focuses on detecting potential privilege escalation attempts within Okta environments. The Elastic Security prebuilt machine learning job pad_okta_spike_in_group_privilege_changes_ea identifies unusual spikes in Okta group privilege change events. Attackers may add themselves or compromised accounts to high-privilege groups to gain unauthorized access and persist within the environment. This activity can lead to significant data breaches, system compromise, and long-term persistence. The rule leverages Elastic’s Anomaly Detection feature. This detection is particularly relevant for organizations heavily reliant on Okta for identity and access management, especially those with sensitive data or critical infrastructure.

Attack Chain

An attacker compromises a low-privilege user account through phishing or credential stuffing.
The attacker logs into Okta using the compromised credentials, bypassing MFA if possible.
The attacker attempts to add the compromised account to a high-privilege Okta group, such as “Administrators” or “Security Admins.”
Okta logs an event indicating a group privilege change for the compromised account.
The machine learning job pad_okta_spike_in_group_privilege_changes_ea detects a statistically significant spike in these group privilege change events.
The attacker gains elevated privileges within Okta and connected applications.
The attacker leverages the newly acquired privileges to access sensitive data or modify critical system configurations.
The attacker establishes persistence by creating new administrative accounts or modifying existing account permissions, ensuring continued access even if the initial compromised account is discovered.

Impact

A successful privilege escalation attack in Okta can have severe consequences. Attackers can gain complete control over the Okta environment, leading to unauthorized access to all connected applications and systems. This can result in data breaches, financial losses, and reputational damage. The number of affected users and systems depends on the scope of the attacker’s access and the sensitivity of the data stored within the connected applications.

Recommendation

Deploy the “Spike in Group Privilege Change Events” machine learning job in your Elastic Security environment and tune the anomaly_threshold for your specific Okta usage patterns (references: Elastic ML Jobs, Privileged Access Detection Setup).
Investigate any alerts generated by the machine learning job, focusing on identifying the accounts involved in the privilege changes, the source IP addresses, and the affected groups (reference: Investigation Guide section in the content).
Implement multi-factor authentication (MFA) for all Okta users, especially those with administrative privileges, to prevent account compromise (reference: remediation steps in the content).
Review and update access control policies to ensure that only authorized personnel can modify group memberships, reducing the risk of future privilege escalation (reference: remediation steps in the content).
Enable Okta integration and collect Okta logs in Elastic Agent policy (reference: Okta integration).
Implement the Sigma rule “Okta Suspicious Group Membership Changes” to detect specific patterns of malicious group modifications, and tune for your environment.

Okta Group Application Assignment Spike Indicates Privilege Escalation

hello@craftedsignal.io — Wed, 03 Jan 2024 12:00:00 +0000

A machine learning job, pad_okta_spike_in_group_application_assignment_changes_ea, has detected an unusual spike in Okta group application assignment change events. This activity, monitored by the Privileged Access Detection integration, suggests potential malicious activity where threat actors may be assigning applications to groups to escalate access, maintain persistence, or facilitate lateral movement. This is particularly relevant for organizations using Okta for identity and access management, as attackers targeting this platform could gain significant control over user access and sensitive resources. The detection is based on identifying anomalies in Okta events and requires the Privileged Access Detection integration to be installed and configured properly, along with the Okta integration. This detection has been in production since February 2025, and updated in April 2026, requiring Elastic Stack version 9.4.0 or later to function correctly due to its reliance on Entity Analytics fields.

Attack Chain

Initial Compromise: An attacker compromises a user account with some level of administrative privileges within the Okta environment (T1078).
Privilege Escalation: The attacker leverages the compromised account to modify group application assignments, granting unauthorized access to sensitive applications (T1098).
Group Modification: The attacker assigns applications to groups that the compromised user has access to modify. This allows the attacker to extend their reach within the organization.
Application Assignment: The attacker assigns applications to a group, potentially giving all members of that group access to the applications without proper authorization.
Lateral Movement: With access to new applications, the attacker uses the newly gained privileges to access other systems and resources within the network (T1078).
Persistence: The attacker may create or modify additional group application assignments to ensure continued access, even if the initial compromised account is detected and remediated (T1098).
Data Access/Exfiltration: The attacker leverages the escalated privileges to access and potentially exfiltrate sensitive data from the applications they now have access to.

Impact

A successful attack could lead to widespread unauthorized access to critical applications and data within the organization. The number of affected users and the extent of data breaches depend on the sensitivity of the applications accessed and the scope of the group membership changes. Consequences range from compliance violations and financial losses to reputational damage and operational disruption.

Recommendation

Ensure the Privileged Access Detection integration is installed and properly configured in your Elastic Stack environment as described in the setup guide.
Investigate any alerts generated by the pad_okta_spike_in_group_application_assignment_changes_ea machine learning job, prioritizing those involving sensitive applications or high-privilege groups.
Review and update access controls and group assignment policies within Okta, as the advisory recommends to prevent similar unauthorized changes in the future.
Implement the following Sigma rule to detect suspicious Okta group application assignment changes and tune it for your environment.

Okta FastPass Phishing Attempt Detection

hello@craftedsignal.io — Wed, 03 Jan 2024 12:00:00 +0000

This alert identifies instances where Okta FastPass successfully blocked a user authentication attempt due to a detected phishing attack. This is based on Okta system logs that record when FastPass declines an authentication because the user was attempting to log in to a known phishing site. The event indicates that a user was likely targeted via phishing, potentially through email or other means, and entered their Okta credentials into a fraudulent site. While the authentication was blocked, the event warrants investigation to determine the scope of the phishing campaign and whether the user may have entered credentials elsewhere.

Attack Chain

An attacker crafts a phishing email or message mimicking a legitimate Okta login page.
The user receives the phishing message and clicks the embedded link.
The user is directed to a fake Okta login page that is designed to steal credentials.
The user enters their Okta username and password on the phishing site.
The phishing site attempts to authenticate the user to Okta using the stolen credentials.
Okta FastPass detects that the authentication attempt is originating from a known phishing site.
Okta FastPass declines the authentication request, preventing access.
The Okta system logs record the event “user.authentication.auth_via_mfa” with outcome “FAILURE” and reason “FastPass declined phishing attempt”.

Impact

While Okta FastPass successfully prevented the immediate breach, the incident confirms that a user was targeted by a phishing campaign. This could lead to the compromise of other accounts if the user reuses the same password. Furthermore, successful phishing attacks can lead to data breaches, financial loss, and reputational damage. The number of affected users depends on the scale of the phishing campaign.

Recommendation

Deploy the provided Sigma rule to your SIEM to detect Okta FastPass phishing prevention events.
Investigate users who triggered the detection to identify the phishing campaign and assess potential credential compromise.
Review Okta system logs for other suspicious activity associated with the targeted user accounts.
Educate users about phishing tactics and how to identify malicious websites to reduce susceptibility to future attacks.

Okta Application Sign-On Policy Modified or Deleted

hello@craftedsignal.io — Wed, 03 Jan 2024 12:00:00 +0000

Okta application sign-on policies control how users authenticate to applications integrated with Okta. An attacker who gains administrative access to an Okta tenant can modify or delete these policies, effectively weakening or bypassing multi-factor authentication (MFA) requirements and other security controls. This allows unauthorized access to sensitive applications and data. While this activity itself is not initial access, it represents a significant escalation of privileges and a deliberate attempt to subvert existing security measures within the Okta environment. Detection of these changes is critical to identify potential breaches early and prevent further damage.

Attack Chain

An attacker gains unauthorized access to an Okta administrator account through compromised credentials or other means.
The attacker authenticates to the Okta admin dashboard.
The attacker navigates to the “Security” section and then to “Authentication Policies”.
The attacker identifies the target application sign-on policy to modify or delete.
To modify, the attacker changes the policy rules, such as disabling MFA requirements or allowing access from untrusted locations.
Alternatively, to delete, the attacker selects the policy and confirms its removal.
The attacker’s actions are logged as “application.policy.sign_on.update” or “application.policy.sign_on.rule.delete” events in the Okta system log.
Unauthorized users can now access applications protected by the modified or deleted policy, potentially leading to data exfiltration or other malicious activities.

Impact

Successful modification or deletion of Okta application sign-on policies can severely compromise an organization’s security posture. This can lead to unauthorized access to sensitive applications and data, resulting in data breaches, financial losses, and reputational damage. The number of affected users and applications depends on the scope of the compromised policies.

Recommendation

Deploy the Sigma rule “Okta Application Sign-On Policy Modified or Deleted” to your SIEM and tune for your environment to detect changes to sign-on policies (rule reference).
Monitor the Okta system log for “application.policy.sign_on.update” and “application.policy.sign_on.rule.delete” events to identify suspicious activity (log source reference).
Implement strong access controls and MFA for Okta administrator accounts to prevent unauthorized policy modifications (best practice).
Regularly review Okta application sign-on policies to ensure they are properly configured and meet security requirements (best practice).

Okta Application Modified or Deleted

hello@craftedsignal.io — Wed, 03 Jan 2024 12:00:00 +0000

This alert detects modifications or deletions of applications within the Okta identity and access management platform. While the specific actor is unknown, the modification or deletion of an application can lead to significant disruptions and potential security breaches. The activity is detected through Okta system logs that record application lifecycle events. This is crucial for defenders because unauthorized changes to applications can lead to privilege escalation, data breaches, or denial of service. Monitoring these events allows for prompt investigation and mitigation of potentially malicious activity.

Attack Chain

Attacker gains unauthorized access to an Okta administrator account.
The attacker authenticates to the Okta admin console.
Attacker navigates to the Applications section in the Okta admin console.
The attacker identifies a target application for modification or deletion.
If modifying, the attacker alters application settings such as permissions, user assignments, or SSO configurations.
If deleting, the attacker initiates the application deletion process.
Okta logs the “application.lifecycle.update” or “application.lifecycle.delete” event.
The change impacts end-users and their ability to access resources through the modified or deleted application.

Impact

The impact of unauthorized application modification or deletion can be significant. Modified applications can grant unintended access to sensitive resources, leading to data breaches or privilege escalation. Deleted applications disrupt user access and business operations, potentially causing significant downtime and financial losses. The scope of the impact depends on the criticality of the affected application and the extent of the unauthorized changes.

Recommendation

Deploy the provided Sigma rule to your SIEM to detect application.lifecycle.update or application.lifecycle.delete events in Okta logs.
Investigate any triggered alerts for unexpected application modifications or deletions, focusing on the user account that initiated the change (source: Okta logs).
Review Okta administrator account access and enforce multi-factor authentication to prevent unauthorized access (reference: Okta documentation on security best practices).

Okta API Token Revoked

hello@craftedsignal.io — Wed, 03 Jan 2024 12:00:00 +0000

This alert focuses on detecting the revocation of Okta API tokens. Okta API tokens are used to authenticate and authorize applications to access Okta’s APIs. When a token is revoked, it means that the token is no longer valid and can no longer be used to access Okta’s APIs. This can happen for a number of reasons, including: a user manually revoking the token, an administrator revoking the token, or Okta automatically revoking the token due to inactivity or security concerns. Detecting API token revocations is crucial because it can indicate that a token has been compromised and is being used by an attacker. A revoked token could be a sign of successful lateral movement or data exfiltration attempts within the Okta environment.

Attack Chain

Initial Access: An attacker gains unauthorized access to an Okta API token through methods like phishing, credential stuffing, or malware.
API Usage: The attacker uses the stolen API token to access Okta’s APIs, potentially gathering sensitive information or modifying user accounts.
Anomaly Detection: Okta’s security mechanisms or custom alerts identify unusual activity associated with the API token, such as access from unfamiliar locations or excessive API calls.
Investigation Triggered: Security personnel initiate an investigation based on the flagged anomalous activity.
Token Revocation: As part of the incident response process, the compromised API token is manually or automatically revoked to prevent further unauthorized access. This action generates a “system.api_token.revoke” event in the Okta system log.
Post-Revocation Analysis: Security teams analyze the events leading up to the token revocation to identify the root cause of the compromise and assess the scope of the attacker’s activities.

Impact

Successful compromise of an Okta API token can lead to significant damage, including unauthorized access to sensitive user data, modification of user accounts and permissions, and disruption of critical business operations. If not detected promptly, attackers can leverage compromised tokens to escalate privileges, move laterally within the Okta environment, and potentially gain access to other connected systems. A single compromised API token could affect hundreds or thousands of users, depending on the scope of access granted to the token.

Recommendation

Deploy the provided Sigma rule to your SIEM to detect system.api_token.revoke events in Okta logs.
Investigate any detected system.api_token.revoke events to determine the cause of the revocation and assess the potential impact.
Review Okta system logs for anomalous activity prior to the token revocation to identify the source of the compromise.
Implement multi-factor authentication (MFA) for all Okta users to reduce the risk of credential compromise.
Regularly audit and review Okta API tokens to identify and revoke unused or overly permissive tokens.

Okta API Token Creation

hello@craftedsignal.io — Wed, 03 Jan 2024 12:00:00 +0000

The creation of Okta API tokens is a legitimate administrative function, but can also be abused by malicious actors to establish persistence within an Okta environment. Monitoring for the creation of these tokens, especially when performed by unexpected users or under unusual circumstances, is crucial for identifying potential security breaches. Okta API tokens allow for programmatic access to Okta resources, making them a valuable asset for attackers seeking to maintain access or perform unauthorized actions. Defenders should prioritize monitoring for these events to quickly identify and respond to potentially malicious activity.

Attack Chain

An attacker gains unauthorized access to an Okta account with sufficient privileges (e.g., Super Administrator).
The attacker authenticates to the Okta Admin Console.
The attacker navigates to the Security > API > Tokens section of the Okta Admin Console.
The attacker creates a new API token with broad or specific permissions.
Okta logs the system.api_token.create event.
The attacker uses the newly created API token to programmatically access Okta resources.
The attacker may leverage the API token for various malicious activities, such as user enumeration, group manipulation, or application access.
The attacker maintains persistent access to the Okta environment even if their initial access is revoked.

Impact

Successful exploitation can lead to unauthorized access to sensitive data, modification of user accounts and permissions, and potentially complete control over the Okta environment. The impact can range from data breaches and service disruptions to complete compromise of identity management. The number of victims and sectors targeted depends on the scope of the compromised Okta environment.

Recommendation

Deploy the Sigma rule “Okta API Token Created” to your SIEM to detect API token creation events (logsource: okta, service: okta).
Investigate any detected system.api_token.create events to verify the legitimacy of the token creation.
Review Okta system logs for unusual administrative activity preceding the API token creation event (logsource: okta, service: okta).
Implement multi-factor authentication (MFA) for all Okta administrator accounts to reduce the risk of unauthorized access.

Detection of Okta Administrator Role Assignment to User or Group

hello@craftedsignal.io — Wed, 03 Jan 2024 12:00:00 +0000

The assignment of administrator roles within Okta to users or groups is a sensitive action that requires careful monitoring. While legitimate administrator actions can account for these events, malicious actors may attempt to escalate privileges or establish persistence by assigning themselves or their controlled groups administrative rights. This activity could lead to unauthorized access, data breaches, or disruption of services within the Okta environment. Defenders should prioritize monitoring these role assignments to identify and respond to potential threats promptly.

Attack Chain

Compromise an Okta user account through phishing or credential stuffing.
Leverage the compromised account to authenticate to the Okta environment.
Identify an existing administrator account within the Okta organization.
Impersonate the targeted admin user to assign admin roles.
Assign the Okta Administrator role to either a compromised user account or a newly created rogue group.
The user or members of the rogue group now possess elevated privileges within the Okta environment.
The attacker leverages these elevated privileges to access sensitive applications, data, or configurations.

Impact

Successful assignment of administrator roles to unauthorized users can lead to severe consequences, including data breaches, unauthorized access to critical applications, and disruption of business operations. The impact can range from compromised user accounts to full control over the Okta tenant, affecting all integrated applications and services.

Recommendation

Deploy the provided Sigma rule to detect anomalous Okta admin role assignments to users or groups, focusing on eventType: group.privilege.grant and eventType: user.account.privilege.grant.
Investigate any alerts generated by the Sigma rule to determine the legitimacy of the role assignment and the user or group involved.
Implement multi-factor authentication (MFA) for all Okta user accounts, especially those with administrative privileges, to mitigate the risk of account compromise.
Regularly review Okta administrator role assignments and revoke any unnecessary privileges to minimize the attack surface.

Okta User Session Start via Anonymizing Proxy Service

hello@craftedsignal.io — Tue, 02 Jan 2024 12:00:00 +0000

This threat brief focuses on detecting Okta user session starts that originate from anonymizing proxy services. Anonymizing proxies can be used by malicious actors to mask their true IP addresses and location, making it more difficult to trace their activities. The use of such proxies during Okta authentication is suspicious because it bypasses geographical restrictions and may indicate compromised credentials. Defenders should be aware that legitimate users may occasionally use anonymizing proxies for privacy reasons, but the activity warrants close scrutiny. The detection of this activity relies on Okta system logs and the security context of the authentication event.

Attack Chain

Attacker obtains valid Okta credentials through phishing, credential stuffing, or other means.
Attacker configures their network connection to route traffic through an anonymizing proxy service (e.g., Tor, VPN).
Attacker initiates an Okta user session using the compromised credentials.
Okta system logs record a “user.session.start” event.
The “securityContext.isProxy” field within the Okta event is set to “true”, indicating the use of a proxy service.
If successful, the attacker gains access to the Okta account and any associated applications or resources.
Attacker may then attempt to escalate privileges, access sensitive data, or perform other malicious activities within the Okta environment.
The attacker may attempt lateral movement to other systems within the organization that trust Okta for authentication.

Impact

Successful exploitation can lead to unauthorized access to sensitive applications and data protected by Okta. This could result in data breaches, financial loss, or reputational damage. Depending on the compromised user’s privileges, an attacker may be able to escalate privileges and gain control over critical systems. The number of potential victims depends on the scope of applications using Okta for authentication.

Recommendation

Deploy the provided Sigma rule to your SIEM to detect Okta user sessions initiated through anonymizing proxies (logsource: okta, service: okta).
Investigate all alerts generated by the Sigma rule to determine the legitimacy of the proxy usage.
Implement multi-factor authentication (MFA) to reduce the risk of account compromise.
Monitor Okta system logs for other suspicious activities, such as failed login attempts or unusual access patterns (references: Okta System Log API).
Review and enforce Okta’s cross-tenant impersonation prevention and detection measures (references: Okta cross-tenant impersonation article).

Okta User Account Lockout Detection

hello@craftedsignal.io — Tue, 02 Jan 2024 12:00:00 +0000

This brief describes detection measures for Okta user account lockouts. An account lockout occurs when a user exceeds the maximum number of permitted failed login attempts, potentially indicating a brute-force attack or other unauthorized access attempts against user accounts. Monitoring for account lockouts is crucial for identifying and mitigating potential security breaches. The rule detects the “Max sign in attempts exceeded” message in Okta logs, which signifies that an account has been locked. Detecting this activity can alert security teams to potential compromise attempts.

Attack Chain

Attacker attempts to authenticate to Okta with a valid or guessed username.
Attacker provides an incorrect password.
Okta logs the failed authentication attempt.
Attacker repeats steps 2 and 3 multiple times within a defined timeframe.
Okta’s account lockout policy is triggered when the maximum number of failed attempts is reached.
Okta logs an event with the displayMessage “Max sign in attempts exceeded”.
The user account is locked, preventing further login attempts.
Security team investigates the lockout event to determine the root cause and potential impact.

Impact

A successful account lockout can disrupt legitimate user access and indicate potential malicious activity. Multiple lockouts within a short period may signify a brute-force attack aimed at gaining unauthorized access to sensitive resources. While the lockout itself prevents immediate unauthorized access, it can lead to denial of service and requires investigation to rule out successful credential compromise. The number of impacted users depends on the scope and sophistication of the attack.

Recommendation

Deploy the Sigma rule Okta User Account Locked Out to your SIEM to detect account lockout events in Okta logs.
Investigate any triggered alerts to determine the cause of the lockout, potentially indicating a brute-force attack (reference: displayMessage: Max sign in attempts exceeded).
Review and adjust Okta’s account lockout policies to balance security and usability based on your organization’s risk tolerance.
Consider implementing multi-factor authentication (MFA) to mitigate the risk of brute-force attacks and credential compromise.

Okta Privileged Operations from Unusual Host Name Detected

hello@craftedsignal.io — Tue, 02 Jan 2024 12:00:00 +0000

This alert identifies potentially malicious Okta activity based on unusual host names associated with privileged operations. The Elastic prebuilt machine learning job pad_okta_rare_host_name_by_user_ea analyzes Okta logs to detect anomalies in device usage, specifically focusing on unusual host names. This activity could indicate a compromised user account, an attacker using stolen credentials, or an insider threat leveraging an unauthorized device to escalate privileges within the Okta environment. This detection is part of the Privileged Access Detection (PAD) integration, designed to identify abnormalities across Windows, Linux, and Okta events, starting with Elastic Stack version 9.4.0. Defenders should investigate users exhibiting this behavior to determine the legitimacy of the access and the device being used.

Attack Chain

An attacker gains initial access to an Okta user’s credentials, possibly through phishing (not specified in source, but likely).
The attacker authenticates to Okta using the compromised credentials.
The attacker attempts to perform privileged operations within Okta (e.g., modifying user permissions, accessing sensitive applications).
The attacker uses a device with a host name that is uncommon for the compromised user, triggering the machine learning alert.
Okta logs the privileged operation and the associated host name.
Elastic’s machine learning job, pad_okta_rare_host_name_by_user_ea, detects the unusual host name based on historical data.
A security alert is generated, indicating potential privileged access from an unusual host.
The attacker escalates privileges within the Okta environment, potentially gaining access to sensitive resources or data.

Impact

A successful attack could lead to unauthorized access to sensitive applications and data managed by Okta. The potential impact includes data breaches, financial loss, and reputational damage. While the rule severity is low, successful privilege escalation can significantly increase the attacker’s access and control, impacting all applications and services integrated with Okta. The exact number of potential victims varies depending on the organization’s size and the scope of Okta’s usage.

Recommendation

Ensure the Privileged Access Detection integration assets are installed and configured properly as per the official Elastic documentation.
Investigate alerts from the pad_okta_rare_host_name_by_user_ea machine learning job by reviewing user login history, device usage patterns, and associated IP addresses as outlined in the rule’s “Triage and analysis” section.
Implement multi-factor authentication (MFA) for all privileged accounts to add an additional layer of security as mentioned in the “Response and remediation” section.
Enable Okta integration and configure the Fleet agent policy according to the Elastic documentation to ensure proper data collection.

Okta Group Membership Spike Detection

hello@craftedsignal.io — Tue, 02 Jan 2024 12:00:00 +0000

This rule leverages machine learning to detect unusual spikes in Okta group membership events, potentially indicating privileged access activity. The detection logic is based on the “pad_okta_spike_in_group_membership_changes_ea” machine learning job. The rule aims to identify scenarios where attackers or malicious insiders are adding accounts to privileged groups within Okta to escalate their privileges, which could lead to unauthorized actions and data breaches. This rule requires the Privileged Access Detection integration assets to be installed, as well as Okta logs collected by integrations such as Okta. The rule’s anomaly threshold is set to 75, and it analyzes data from the last 3 hours at 15-minute intervals.

Attack Chain

An attacker gains initial access to an Okta account, potentially through compromised credentials or phishing.
The attacker uses the compromised account to access the Okta admin interface.
The attacker identifies high-privilege groups within Okta, such as those with access to sensitive applications or data.
The attacker adds their controlled account or a compromised user account to one or more of these privileged groups.
Okta logs the group membership change event.
The machine learning job “pad_okta_spike_in_group_membership_changes_ea” detects an unusual spike in these group membership events.
The detection rule triggers, alerting security personnel to the potential privilege escalation.
The attacker leverages the newly acquired privileges to access sensitive resources or perform unauthorized actions.

Impact

A successful privilege escalation attack in Okta can lead to significant damage. Attackers can gain access to sensitive applications and data, compromise other user accounts, and potentially disrupt business operations. The number of affected users and the scope of the damage depend on the privileges associated with the compromised groups. Detecting and responding to these spikes is crucial to preventing widespread data breaches and maintaining the integrity of the Okta environment.

Recommendation

Ensure the Privileged Access Detection integration is installed and configured correctly, including the “pad_okta_spike_in_group_membership_changes_ea” machine learning job, as outlined in the setup instructions.
Review the specific Okta group membership events that triggered the alert to identify which accounts were added to privileged groups, as suggested in the investigation guide.
Implement additional monitoring on affected accounts and privileged groups to detect any further suspicious activity, following the response and remediation steps.
Create exceptions for routine administrative tasks or automated scripts that legitimately manage group memberships to reduce false positives, as detailed in the false positive analysis.