OpenAI ChatGPT Enterprise Multiple Authentication Failures


Description

Detects multiple failed ChatGPT Enterprise login attempts for the same user email within a short window. Password spraying or credential stuffing against enterprise accounts often precedes a successful compromise.

Query · esql

from logs-openai_chatgpt_enterprise.auth_log-*
| where
    data_stream.dataset == "openai_chatgpt_enterprise.auth_log" and
    event.action == "login_failed" and
    user.email is not null
| stats
    Esql.event_count = count(*),
    Esql.source_ip_values = values(source.ip),
    Esql.source_geo_country_iso_code_values = values(source.geo.country_iso_code),
    Esql.user_agent_original_values = values(user_agent.original),
    Esql.timestamp_first_seen = min(@timestamp),
    Esql.timestamp_last_seen = max(@timestamp)
  by user.email
| where Esql.event_count >= 10
| keep user.email, Esql.*

Investigation fields

Pivot points the source recommends for triage.

  • user.email
  • Esql.event_count
  • Esql.source_ip_values
  • Esql.source_geo_country_iso_code_values
  • Esql.timestamp_first_seen
  • Esql.timestamp_last_seen

Implementation guide

This rule requires the OpenAI ChatGPT Enterprise integration to collect compliance logs into Elasticsearch.

https://www.elastic.co/docs/reference/integrations/openai_chatgpt_enterprise

Known false positives

  • Users mistype passwords repeatedly or SSO misconfiguration can generate clusters of failed logins.

Analyst notes

Investigating OpenAI ChatGPT Enterprise Multiple Authentication Failures

One email produced a burst of failed ChatGPT Enterprise login attempts. That pattern can indicate password spraying, credential stuffing, or repeated guessing before a successful compromise.

Escalate when many distinct source IPs are involved, failures precede a successful login from an unfamiliar IP or user agent, or privileged activity follows. Close as a false positive for repeated typos or SSO misconfiguration from a single client.

Possible investigation steps

  • Review Esql.event_count, Esql.source_ip_values, and geo values on the alert.
  • Low IP diversity usually indicates one device or egress. High diversity suggests distributed automation.
  • Search for successful logins for the same email immediately after the failure burst.
  • Correlate with role changes, invites, or data-access events if a successful login follows.

False positive analysis

  • Users mistyping passwords or temporary SSO misconfiguration can generate short clusters of failures from one IP and user agent.

Response and remediation

  • If compromise is suspected, lock or reset the account, revoke sessions, and review subsequent successful authentication and audit activity.
Raw source OpenAI ChatGPT Enterprise Multiple Authentication Failures · Elastic TOML
Esc
Published by elastic/detection-rules ↗, licensed under Elastic License 2.0 ↗. Reproduced here unmodified.
[metadata]
creation_date = "2026/10/06"
integration = ["openai_chatgpt_enterprise"]
maturity = "production"
updated_date = "2026/10/06"

[rule]
author = ["Elastic"]
description = """
Detects multiple failed ChatGPT Enterprise login attempts for the same user email within a short window. Password
spraying or credential stuffing against enterprise accounts often precedes a successful compromise.
"""
false_positives = [
    "Users mistype passwords repeatedly or SSO misconfiguration can generate clusters of failed logins.",
]
from = "now-1h"
interval = "15m"
language = "esql"
license = "Elastic License v2"
name = "OpenAI ChatGPT Enterprise Multiple Authentication Failures"
note = """## Triage and analysis

### Investigating OpenAI ChatGPT Enterprise Multiple Authentication Failures

One email produced a burst of failed ChatGPT Enterprise login attempts. That pattern can indicate password spraying, credential stuffing, or repeated guessing before a successful compromise.

Escalate when many distinct source IPs are involved, failures precede a successful login from an unfamiliar IP or user agent, or privileged activity follows. Close as a false positive for repeated typos or SSO misconfiguration from a single client.

#### Possible investigation steps

- Review `Esql.event_count`, `Esql.source_ip_values`, and geo values on the alert.
- Low IP diversity usually indicates one device or egress. High diversity suggests distributed automation.
- Search for successful logins for the same email immediately after the failure burst.
- Correlate with role changes, invites, or data-access events if a successful login follows.

### False positive analysis

- Users mistyping passwords or temporary SSO misconfiguration can generate short clusters of failures from one IP and user agent.

### Response and remediation

- If compromise is suspected, lock or reset the account, revoke sessions, and review subsequent successful authentication and audit activity.
"""
references = [
    "https://www.elastic.co/docs/reference/integrations/openai_chatgpt_enterprise",
    "https://platform.openai.com/docs/compliance",
]
risk_score = 47
rule_id = "9330b47d-75df-4e55-85e9-409244c6f3b6"
setup = """## Setup

This rule requires the OpenAI ChatGPT Enterprise integration to collect compliance logs into Elasticsearch.

https://www.elastic.co/docs/reference/integrations/openai_chatgpt_enterprise
"""
severity = "medium"
tags = [
    "Domain: GenAI",
    "Platform: OpenAI",
    "Data Source: OpenAI ChatGPT Enterprise",
    "Service: OpenAI ChatGPT Enterprise",
    "Use Case: Threat Detection",
    "Resources: Investigation Guide",
    "Rule Type: ES|QL",
    "Domain: Identity",
    "Use Case: Identity and Access Audit",
    "Tactic: Credential Access",
]
timestamp_override = "event.ingested"
type = "esql"

query = '''
from logs-openai_chatgpt_enterprise.auth_log-*
| where
    data_stream.dataset == "openai_chatgpt_enterprise.auth_log" and
    event.action == "login_failed" and
    user.email is not null
| stats
    Esql.event_count = count(*),
    Esql.source_ip_values = values(source.ip),
    Esql.source_geo_country_iso_code_values = values(source.geo.country_iso_code),
    Esql.user_agent_original_values = values(user_agent.original),
    Esql.timestamp_first_seen = min(@timestamp),
    Esql.timestamp_last_seen = max(@timestamp)
  by user.email
| where Esql.event_count >= 10
| keep user.email, Esql.*
'''


[[rule.threat]]
framework = "MITRE ATT&CK"
[[rule.threat.technique]]
id = "T1110"
name = "Brute Force"
reference = "https://attack.mitre.org/techniques/T1110/"
[rule.threat.tactic]
id = "TA0006"
name = "Credential Access"
reference = "https://attack.mitre.org/tactics/TA0006/"

[[rule.threat_mappings]]
framework = "MITRE ATLAS"
version = "2026.08"
[[rule.threat_mappings.threat]]
framework = "MITRE ATLAS"

[rule.threat_mappings.threat.tactic]
id = "AML.TA0013"
name = "Credential Access"
reference = "https://atlas.mitre.org/tactics/AML.TA0013/"

[rule.alert_suppression]
group_by = ["user.email"]
missing_fields_strategy = "suppress"

[rule.alert_suppression.duration]
unit = "h"
value = 1

[rule.investigation_fields]
field_names = [
    "user.email",
    "Esql.event_count",
    "Esql.source_ip_values",
    "Esql.source_geo_country_iso_code_values",
    "Esql.timestamp_first_seen",
    "Esql.timestamp_last_seen",
]

Detection rules belong to the projects that publish them and remain under their own licenses. This site indexes and links to them; it claims no rights in them.