Identity — CraftedSignal Threat Feed

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 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 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 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.

AWS Identity Center Identity Provider Modification

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

AWS Identity Center (formerly AWS SSO) enables centralized management of access to AWS accounts and applications. Attackers can manipulate the configured identity provider to gain unauthorized access. The modification of the configured Identity Provider (IdP) within AWS Identity Center can lead to a full compromise of the AWS environment. By associating a malicious directory or disabling/disassociating legitimate directories, attackers can potentially establish persistent access, escalate privileges, and impersonate legitimate users. This can be achieved by utilizing compromised AWS credentials or exploiting vulnerabilities in the AWS environment.

Attack Chain

Initial access is gained via compromised AWS credentials or by exploiting an AWS vulnerability.
The attacker enumerates the current AWS Identity Center configuration to identify the currently associated directory.
The attacker disassociates the existing, legitimate directory using DisassociateDirectory.
The attacker associates a malicious directory they control using AssociateDirectory. This malicious directory is configured to impersonate legitimate users.
Alternatively, the attacker disables external IdP configuration for the directory using DisableExternalIdPConfigurationForDirectory.
The attacker enables external IdP configuration for the directory, pointing to an attacker-controlled IdP, using EnableExternalIdPConfigurationForDirectory.
The attacker uses the malicious or attacker-controlled IdP to authenticate as legitimate users, gaining access to AWS resources.
The attacker performs malicious actions within the AWS environment, such as data exfiltration or resource destruction.

Impact

Successful modification of the AWS Identity Center identity provider can lead to complete compromise of an AWS environment. Attackers can gain persistent access, escalate privileges, and impersonate legitimate users. This can result in data breaches, service disruption, financial loss, and reputational damage. The impact can extend to all AWS accounts and applications managed by the compromised Identity Center instance.

Recommendation

Deploy the provided Sigma rule to your SIEM to detect unauthorized changes to the AWS Identity Center identity provider.
Investigate any detected events related to AssociateDirectory, DisableExternalIdPConfigurationForDirectory, DisassociateDirectory, or EnableExternalIdPConfigurationForDirectory in AWS CloudTrail logs.
Implement multi-factor authentication (MFA) for all AWS accounts and users to reduce the risk of credential compromise.
Review and restrict IAM permissions to minimize the blast radius of compromised credentials.
Monitor AWS CloudTrail logs for unusual activity patterns that might indicate malicious directory association attempts.

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 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 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 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.