OpenAI ChatGPT Enterprise Resources Sharing Updated

edit
IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.

OpenAI ChatGPT Enterprise Resources Sharing Updated

edit

Detects ChatGPT Enterprise audit events that publish a GPT or update sharing for GPTs, skills, or projects (gpt_publish, update_sharing, skill_share, project_update_sharing). Broadening share scope can expose custom instructions, tools, or proprietary agent configurations beyond the original audience.

Rule type: esql

Rule indices: None

Severity: medium

Risk score: 47

Runs every: 5m

Searches indices from: now-9m (Date Math format, see also Additional look-back time)

Maximum alerts per execution: 100

References:

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
  • Tactic: Exfiltration
  • Mitre Atlas: AML.T0025

Version: 1

Rule authors:

  • Elastic

Rule license: Elastic License v2

Investigation guide

edit

Triage and analysis

Investigating OpenAI ChatGPT Enterprise Resources Sharing Updated

A GPT was published or a GPT, skill, or project sharing setting changed. Broadening share scope can expose proprietary instructions, connectors, or data.

Escalate when shared_to.recipient_type or related fields indicate a wider audience than policy allows, the asset includes sensitive instructions or connectors, or the publisher is unexpected. Close as a false positive for intentional publication under an approved release process.

Possible investigation steps

  • Identify the actor and the GPT, skill, or project identifiers on the alert.
  • Review openai_chatgpt_enterprise.audit_log.action_data.shared_to.recipient_type and other share-scope fields when present.
  • Confirm whether store or broad visibility was enabled and whether that matches change management.
  • Look for related publish, share, or connector-link events from the same actor.

False positive analysis

  • Teams intentionally publish GPTs or skills for approved internal or partner use under change management.

Response and remediation

  • Restrict unauthorized shares, unpublish if needed, and inventory other published assets by the same actor.

Setup

edit

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

Rule query

edit
from logs-openai_chatgpt_enterprise.audit_log-* metadata _id, _version, _index
| where
    data_stream.dataset == "openai_chatgpt_enterprise.audit_log" and
    event.action in ("gpt_publish", "update_sharing", "skill_share", "project_update_sharing")
| keep
    _id, _version, _index, @timestamp, event.action, user.id, user.email, source.ip,
    openai_chatgpt_enterprise.audit_log.action_data.gpt_id,
    openai_chatgpt_enterprise.audit_log.action_data.agent_id,
    openai_chatgpt_enterprise.audit_log.action_data.skill_id,
    openai_chatgpt_enterprise.audit_log.action_data.shared_to.recipient_type,
    openai_chatgpt_enterprise.audit_log.action_data.third_party_gizmo_id,
    openai_chatgpt_enterprise.audit_log.action_privilege, data_stream.*

Framework: MITRE ATT&CKTM