OpenAi ChatGPT v3

This integration assists security professionals with security investigations, threat hunting, and anomaly detection by leveraging OpenAI GPT models' natural language conversation capabilities.

Messaging and Conferencing · OpenAI

Details

IDOpenAi ChatGPT v3
ProviderOpenAI
CategoryMessaging and Conferencing
From Version6.0.0
Docker Imagedemisto/parse-emails:0.1.48.10120494
Supported ModulesAgentix XSIAM

README

OpenAI GPT

Instance Configuration

  • Generate an API Key

    1. Sign up or log in to OpenAI developer platform.
    2. Generate a new API key at OpenAI developer platform - api-keys.
  • Choose a GPT model to interact with

    1. This integration supports only the ‘Chat Completions’ endpoint. Therefore, you can only configure models that support this endpoint (https://api.openai.com/v1/chat/completions).

    2. For tasks requiring deep understanding and extensive inputs, opt for more advanced models (e.g. gpt-4). These models offer a larger context window, allowing them to process bigger documents, and provide more refined and comprehensive responses.
      The more elementary models (e.g. gpt-3.5) often provide shallower answers and input analysis.
      Refer to Models overview for more information.

  • Text generation setting (Optional)

    1. max-tokens: The maximum number of tokens that can be generated for the response. (Allows controlling tokens’ consumption). Default: unset.
    2. temperature: Sets the randomness in responses. Lower values (closer to 0) produce more deterministic and consistent outputs, while higher values (up to 2) increase randomness and variety. It is generally recommended altering this or top_p but not both. Default: 1.
    3. top_p: Enables nucleus sampling where only the top ‘p’ percent of probable tokens are considered. Lower values (closer to 0) result in more focused outputs, while higher values (closer to 1) increase diversity. It is generally recommended altering this or temperature but not both. Default: unset.
  • Event Collector — Generate API Keys

    1. Admin API Key (required for OpenAI Audit logs): generate from the OpenAI Platform admin console. Used to call /v1/organization/audit_logs.
    2. Compliance API Key (required for any Compliance event type): generate from the ChatGPT Platform. Used to call /v1/compliance/workspaces/{workspace_id}/....
    3. Workspace ID (required for any Compliance event type): the UUID of the compliance workspace whose events you want to collect.
  • Event Collector — Select event types to fetch

    Toggle Fetch events, then select one or more Events types to fetch:

    User-facing label Source Required credentials
    OpenAI Audit logs OpenAI Platform — Admin API Admin API Key
    Conversation Messages ChatGPT Platform — Compliance API Compliance API Key + Workspace ID
    Apps ChatGPT Platform — Compliance API Compliance API Key + Workspace ID
    Apps Auth ChatGPT Platform — Compliance API Compliance API Key + Workspace ID
    Compliance Audit ChatGPT Platform — Compliance API Compliance API Key + Workspace ID
    Auth ChatGPT Platform — Compliance API Compliance API Key + Workspace ID
    Codex ChatGPT Platform — Compliance API Compliance API Key + Workspace ID
    ChatGPT ChatGPT Platform — Compliance API Compliance API Key + Workspace ID
    Codex Security ChatGPT Platform — Compliance API Compliance API Key + Workspace ID
    Workspace Agents ChatGPT Platform — Compliance API Compliance API Key + Workspace ID

    Selecting an event type without its matching credentials raises an informative error at instance test time, naming the missing parameter.

  • Event Collector — Datasets

    Each Event Collector stream lands in its own Cortex dataset:

    Stream Vendor Product Dataset
    OpenAI Audit logs openai chatgpt_audit openai_chatgpt_audit_raw
    Compliance logs (all) openai chatgpt_compliance openai_chatgpt_compliance_raw
  • Event Collector — Tuning (Optional)

    Parameter Default Description
    Maximum number of OpenAI Audit events per fetch 1000 Cap on Audit events ingested per fetch cycle.
    Maximum number of Compliance events per fetch 900 Cap on Compliance events ingested per fetch cycle.
    Events Fetch Interval 1 minute How often the scheduled fetch runs.
    ChatGPT Server URL https://api.chatgpt.com Base URL of the ChatGPT Compliance API. Override only for non-default tenants.
  • Click ‘Test’

Commands

You can execute these commands from the Cortex XSOAR CLI, as part of an automation, or in a playbook.

gpt-send-message


Send a message as a prompt to the GPT model.

!gpt-send-message message="<MESSAGE_TEXT>"

Input

Argument Name Description Required
message The message to send to the GPT model wrapped with quotes. Yes
reset_conversation_history Whether to reset conversation history or keep it as context for the sent message. (Conversation history is not reset by default). No
max_tokens The maximum number of tokens that can be generated for the response. Overrides text generation setting for the specific message sent. No
temperature Sets the randomness in responses. Overrides text generation setting for the specific message sent. No
top_p Enables nucleus sampling where only the top ‘p’ percent of probable tokens are considered. Overrides text generation setting for the specific message sent. No

gpt-check-email-body


Check email body for possible security issues.

!gpt-check-email-body entryId="<ENTRY_ID_OF_UPLOADED_EML_FILE>"

Input

Argument Name Description Required
entryId Entry ID of an uploaded .eml file from the context window. Yes
additionalInstructions Provide additional instructions for the GPT model when analyzing the email body. No
max_tokens The maximum number of tokens that can be generated for the response. Overrides text generation setting for the specific message sent. No
temperature Sets the randomness in responses. Overrides text generation setting for the specific message sent. No
top_p Enables nucleus sampling where only the top ‘p’ percent of probable tokens are considered. Overrides text generation setting for the specific message sent. No

gpt-check-email-header


Check email body for possible security issues.

!gpt-check-email-header entryId="<ENTRY_ID_OF_UPLOADED_EML_FILE>"

Input

Argument Name Description Required
entryId Entry ID of an uploaded .eml file from context window. Yes
additionalInstructions Provide additional instructions for the GPT model when analyzing the email headers. No
max_tokens The maximum number of tokens that can be generated for the response. Overrides text generation setting for the specific message sent. No
temperature Sets the randomness in responses. Overrides text generation setting for the specific message sent. No
top_p Enables nucleus sampling where only the top ‘p’ percent of probable tokens are considered. Overrides text generation setting for the specific message sent. No

gpt-analyze-email-header


Analyze email headers for potential security issues using the OpenAI Responses API. This command uses the Responses API which is recommended for all new projects (instead of gpt-check-email-header which uses the Chat Completions API).

!gpt-analyze-email-header entry_id="3@123" additional_instructions="Pay close attention to SPF/DKIM."

Input

Argument Name Description Required
entry_id Entry ID of an uploaded .eml file. Yes
additional_instructions Additional instructions or security issue to focus on. Substituted into the prompt template. No
max_tokens The maximum number of tokens that can be generated for the response. Maps internally to the API body field max_output_tokens. No
temperature Sets the randomness in responses. Lower values (closer to 0) produce more deterministic and consistent outputs, while higher values (up to 2) increase randomness and variety. No
top_p Enables nucleus sampling where only the top ‘p’ percent of probable tokens are considered. Range 0–1. No
reasoning_effort Reasoning effort level for reasoning models (o1, o3, o4, gpt-5). Controls how much thinking the model does before responding. Possible values: low, medium, high. No

Context Output

Path Type Description
OpenAiChatGPTV3.Response Unknown The conversation state including the response_id.
OpenAiChatGPTV3.Response.user String The prompt sent to the model.
OpenAiChatGPTV3.Response.assistant String The assistant response text.
OpenAiChatGPTV3.Response.response_id String The OpenAI response ID.

Human Readable Output

Two war-room entries are produced:

  1. A table of the parsed email headers.
  2. The AI verdict followed by a token-usage table. A Reasoning tokens row appears in the usage table when a reasoning model is used.

gpt-analyze-email-body


Analyze email body for potential security risks using the OpenAI Responses API. This command uses the Responses API which is recommended for all new projects (instead of gpt-check-email-body which uses the Chat Completions API).

!gpt-analyze-email-body entry_id="3@123"

Input

Argument Name Description Required
entry_id Entry ID of an uploaded .eml file. Yes
additional_instructions Additional instructions or security issue to focus on. Substituted into the prompt template. No
max_tokens The maximum number of tokens that can be generated for the response. Maps internally to the API body field max_output_tokens. No
temperature Sets the randomness in responses. Lower values (closer to 0) produce more deterministic and consistent outputs, while higher values (up to 2) increase randomness and variety. No
top_p Enables nucleus sampling where only the top ‘p’ percent of probable tokens are considered. Range 0–1. No
reasoning_effort Reasoning effort level for reasoning models (o1, o3, o4, gpt-5). Controls how much thinking the model does before responding. Possible values: low, medium, high. No

Context Output

Path Type Description
OpenAiChatGPTV3.Response Unknown The conversation state including the response_id.
OpenAiChatGPTV3.Response.user String The prompt sent to the model.
OpenAiChatGPTV3.Response.assistant String The assistant response text.
OpenAiChatGPTV3.Response.response_id String The OpenAI response ID.

Human Readable Output

Two war-room entries are produced:

  1. A table of the parsed email body (text and HTML).
  2. The AI verdict followed by a token-usage table. A Reasoning tokens row appears in the usage table when a reasoning model is used.

gpt-create-soc-email-template


Create an email template out of the conversation context to be sent from the SOC.

!gpt-create-soc-email-template

Input

Argument Name Description Required
additionalInstructions Provide additional instructions for the GPT model when analyzing the email headers. No
max_tokens The maximum number of tokens that can be generated for the response. Overrides text generation setting for the specific message sent. No
temperature Sets the randomness in responses. Overrides text generation setting for the specific message sent. No
top_p Enables nucleus sampling where only the top ‘p’ percent of probable tokens are considered. Overrides text generation setting for the specific message sent. No

gpt-draft-soc-email


Draft a SOC email template using the OpenAI Responses API. This command uses the Responses API which is recommended for all new projects (instead of gpt-create-soc-email-template which uses the Chat Completions API). Consumes prior conversation context by design (e.g. from a preceding gpt-analyze-email-body call).

Cortex XSOAR sequence (typical phishing flow)

!gpt-analyze-email-body entry_id="3@123"
…assistant returns analysis…
!gpt-draft-soc-email additional_instructions="Notify the user the email was quarantined."

Input

Argument Name Description Required
additional_instructions Specific issue or focus area to weave into the template. Substituted into the prompt template. No
max_tokens The maximum number of tokens that can be generated for the response. Maps internally to the API body field max_output_tokens. No
temperature Sets the randomness in responses. Lower values (closer to 0) produce more deterministic and consistent outputs, while higher values (up to 2) increase randomness and variety. No
top_p Enables nucleus sampling where only the top ‘p’ percent of probable tokens are considered. Range 0–1. No
reasoning_effort Reasoning effort level for reasoning models (o1, o3, o4, gpt-5). Controls how much thinking the model does before responding. Possible values: low, medium, high. No

Context Output

Path Type Description
OpenAiChatGPTV3.Response Unknown The conversation state including the response_id.
OpenAiChatGPTV3.Response.user String The prompt sent to the model.
OpenAiChatGPTV3.Response.assistant String The assistant response text.
OpenAiChatGPTV3.Response.response_id String The OpenAI response ID.

Human Readable Output

Two war-room entries are produced:

  1. The SOC email template context output (replace_existing=True — running twice overwrites the previous draft).
  2. The AI-generated template followed by a token-usage table. A Reasoning tokens row appears in the usage table when a reasoning model is used.

openai-get-events


Manually fetch a bounded batch of Audit and/or Compliance events for development/debugging. Does NOT advance the persisted last_run cursor, so it is safe to run against production tenants. Use should_push_events=true to additionally ingest the fetched events into the matching Cortex dataset.

Base Command

openai-get-events

Input

Argument Name Description Required
event_type The event type(s) to fetch. Comma-separated list. Possible values: OpenAI Audit logs, Conversation Messages, Apps, Apps Auth, Compliance Audit, Auth, Codex, ChatGPT, Codex Security, Workspace Agents. Defaults to the values configured in the integration parameters. No
limit Maximum number of events to return per stream. Default: 50. No
start_time Lookback start time for the fetch. Supports ISO 8601 or relative time (e.g., 3 days ago, 2099-01-01T00:00:00Z). No
should_push_events If true, the command also pushes the retrieved events to Cortex (Audit -> openai_chatgpt_audit_raw, Compliance -> openai_chatgpt_compliance_raw). Possible values: true, false. Default: false. No

Context Output

Path Type Description
OpenAI.Event.id String The unique identifier of the event.
OpenAI.Event._event_type String The upstream event_type for Compliance events. Left empty for Audit events.
OpenAI.Event.source_log_type String The source log type used by downstream parsing rules.
OpenAI.Event._time Date The event timestamp in ISO 8601 format.

Human Readable Output

OpenAI GPT Events

id _event_type source_log_type _time
FAKE_AUDIT_EVENT_001   openai_audit_logs 2099-01-01T00:00:00Z
FAKE_LISTING_002 AUDIT_LOG compliance_audit_log 2099-01-02T00:00:00Z

gpt-create-response


Sends a message to the OpenAI Responses API and receives the generated response. This command uses the Responses API which is recommended for all new projects (instead of gpt-send-message which uses the Chat Completions API). Supports multi-turn conversations via previous_response_id, reasoning effort control for o-series and gpt-5 models, and background execution.

Base Command

gpt-create-response

Input

Argument Name Description Required
message The user message to send. Required
reset_conversation_history Whether to discard the existing conversation context and start fresh. Possible values are: yes, no. Default is no. Optional
max_tokens The maximum number of output tokens. Falls back to instance config. Maps internally to the API body field max_output_tokens. Optional
temperature The randomness level in responses. Falls back to instance config. Range 0-2. Lower values produce more deterministic outputs, while higher values increase variety. Optional
top_p The nucleus sampling threshold. Falls back to instance config. Range 0-1. Lower values result in more focused outputs, while higher values increase diversity. Optional
reasoning_effort The reasoning effort level. Honored only for reasoning families (o1, o3, o4, gpt-5); silently dropped on others. Default medium. Possible values are: none, minimal, low, medium, high, xhigh. Optional
background Whether to run the model response in the background. When true, the command uses polling to wait for the response to complete. Possible values are: true, false. Optional
compact_threshold The token threshold at which compaction should be triggered for this entry. Minimum 1000. Optional
model The model to use. Use the gpt-list-models command to see available models. Falls back to instance config. Optional

Context Output

Path Type Description
OpenAiChatGPTV3.Response Unknown The conversation state, which includes the response_id for multi-turn continuity.
OpenAiChatGPTV3.Response.user String The user message sent.
OpenAiChatGPTV3.Response.assistant String The assistant response text.
OpenAiChatGPTV3.Response.response_id String The OpenAI response ID used for multi-turn conversation continuity.

gpt-list-models


Lists all models available to the configured API key. Lets users discover models per their actual API-key tier without redeploying the integration when OpenAI ships new ones.

Base Command

gpt-list-models

Input

| Argument Name | Description | Required |
| — | — | — |

Context Output

Path Type Description
OpenAiChatGPTV3.Model.Id String The model identifier (e.g., gpt-4, gpt-3.5-turbo).
OpenAiChatGPTV3.Model.Created Number The Unix timestamp when the model was created.
OpenAiChatGPTV3.Model.OwnedBy String The organization or entity that owns the model.

gpt-create-moderation


Runs text or an image through the OpenAI Moderations API and returns per-category flagging results. Exactly one of text, entry_id, or image_url must be provided.

Base Command

gpt-create-moderation

Input

Argument Name Description Required
text A comma-separated list of text strings to moderate. Exactly one of text, entry_id, or image_url must be provided. Optional
entry_id The war-room entry ID of an uploaded image file. The file is base64-encoded internally and posted as a data URL. Exactly one of text, entry_id, or image_url must be provided. Optional
image_url The publicly reachable HTTP(S) URL of an image (limited to 20 MB). Exactly one of text, entry_id, or image_url must be provided. Optional
model The moderation model to use. Possible values are: omni-moderation-latest, omni-moderation-2024-09-26. Default is omni-moderation-latest. Optional

Context Output

Path Type Description
OpenAiChatGPTV3.Moderation.Input.input_type String The type of input that was moderated (text, image, or image_url).
OpenAiChatGPTV3.Moderation.Input.input_value String The value of the input that was moderated.
OpenAiChatGPTV3.Moderation.Flagged Boolean Whether the content was flagged by the moderation model.
OpenAiChatGPTV3.Moderation.Categories Unknown The object of boolean values indicating which categories were flagged.
OpenAiChatGPTV3.Moderation.CategoryScores Unknown The object of float values indicating the confidence score for each category.

<~PLATFORM>

License Requirements

The following configuration parameters require the Cortex XSIAM license:

  • Fetch events

</~PLATFORM>

Configuration parameters

  • url — Server URL (required)
  • chatgpt_api_url — ChatGPT Server URL
  • apikey
  • admin_api_key — Admin API Key
  • compliance_api_key — Compliance API Key
  • workspace_id — Workspace ID
  • model-select — Model
  • model-freetext — Model (Optional - overrides selected choice)
  • max_tokens — Max tokens
  • temperature — Temperature
  • top_p — Top P
  • insecure — Trust any certificate (not secure)
  • proxy — Use system proxy settings
  • isFetchEvents — Fetch events
  • event_types_to_fetch — Events types to fetch
  • audit_max_fetch — Maximum number of OpenAI Audit events per fetch
  • compliance_max_fetch — Maximum number of Compliance events per fetch
  • eventFetchInterval — Events Fetch Interval

Commands (11)

  • gpt-analyze-email-body

    Analyzes email body for potential security risks using the OpenAI Responses API. This is the Responses-API counterpart of gpt-check-email-body (which uses the Chat Completions API).

  • gpt-analyze-email-header

    Analyzes email headers for potential security issues using the OpenAI Responses API. This is the Responses-API counterpart of gpt-check-email-header (which uses the Chat Completions API).

  • gpt-check-email-body

    Checks the email body for possible security issues. Enables you to ask subsequent questions on the provided information using the 'gpt-send-message' command, and resets the conversation context by default.

  • gpt-check-email-header

    Checking email header for possible security issues. It is possible to keep asking questions on the provided info using 'gpt-send-message'. Resets conversation context by default.

  • gpt-create-moderation

    Runs text or an image through the OpenAI Moderations API and returns per-category flagging results. Exactly one of text, entry_id, or image_url must be provided.

  • gpt-create-response

    Sends a message to the OpenAI Responses API and receives the generated response. This command uses the Responses API which is recommended for all new projects (instead of gpt-send-message which uses the Chat Completions API). Supports multi-turn conversations via previous_response_id, reasoning effort control for o-series and gpt-5 models, and background execution.

  • gpt-create-soc-email-template

    Create an email template out of the conversation context to be sent from the SOC.

  • gpt-draft-soc-email

    Drafts a SOC email template using the OpenAI Responses API. This command uses the Responses API which is recommended for all new projects (instead of gpt-create-soc-email-template which uses the Chat Completions API). Consumes prior conversation context by design (e.g. from a preceding gpt-analyze-email-body call).

  • gpt-list-models

    Lists all models available to the configured API key. Lets users discover models per their actual API-key tier without redeploying the integration when OpenAI ships new ones.

  • gpt-send-message

    Send a plain message to the selected GPT model and receive the generated response.

  • openai-get-events

    Manually retrieves events from OpenAI. Use this command for development and debugging only, as it may produce duplicate events, exceed API rate limits, or disrupt the fetch mechanism.

## OpenAI

### Generate an API Key

1. Sign-up or login to [https://platform.openai.com](https://platform.openai.com).
2. Generate a new API Key at [https://platform.openai.com/api-keys](https://platform.openai.com/api-keys).

### Models & Rate Limits

The integration utilizes the **'Chat Completions'** endpoint merely. Therefore, it will only be possible to configure models that support the following endpoint: _https://api.openai.com/v1/chat/completions_.

_For many basic tasks, the difference between GPT-4 and GPT-3.5 models is not significant. However, in more complex reasoning situations, GPT-4 is much more capable than any of our previous models._

For tasks requiring deep understanding and extensive inputs, opt for more advanced models (e.g. gpt-4). These models offer a larger context window, allowing them to process bigger documents, and provide more refined and comprehensive responses.
The more elementary models (e.g. gpt-3.5) often provide shallower answers with a smaller input tokens' limit, but are less costly.

- [Models overview](https://platform.openai.com/docs/models/overview)

- Each model has its own requests' rate-limit: Refer to [rate-limits](https://platform.openai.com/docs/guides/rate-limits).

### How to use this integration with XSOAR

#### The following blog post ['Palo Alto Networks - Playbook of the week'](https://www.paloaltonetworks.com/blog/security-operations/using-chatgpt-in-cortex-xsoar/) by Sam Testov explains how to use this integration in your playbooks:

<~XSIAM>

---

## ChatGPT

### Event Collector Setup

The OpenAI integration can collect **Audit logs** (OpenAI Admin API) and **Compliance logs** (ChatGPT Platform) and forward them to Cortex as events. This section covers the prerequisites for both feeds. For full background, see the [design document](https://docs.google.com/document/d/1AQdeSL4RZya19ZVtnBJK-hIk8wBUElIahF4NlZ9nti8/edit?tab=t.0).

#### Setting up your organization

After signing in to your OpenAI account, your organization name and ID are listed under **Organization settings**. The organization name is the human-readable label; the organization ID is the unique identifier used in API requests.

If your account belongs to multiple organizations, you can pass an `OpenAI-Organization` header to scope an API request to a specific organization. Usage from those requests counts against that organization's quota. If the header is omitted, the default organization is billed. The default organization can be changed in your user settings.

- Create an Admin key: <https://platform.openai.com/settings/organization/admin-keys>
- Enable Audit logging: <https://platform.openai.com/settings/organization/data-controls/data-retention>

#### Enable Audit logging for the organization

> **Important**: Once Audit logging is enabled for an API Platform organization it **cannot be self-disabled**. Only Organization Owners can contact OpenAI support to disable it afterwards.

Organization Owners enable Audit logging from **Organization settings → Data controls → Data retention**, then toggle **Enable** under **Audit logging** at the bottom of the page and save. Once saved, Audit logging is active for the organization. See OpenAI's [Audit logging documentation](https://platform.openai.com/docs/guides/audit-logs) for the full reference.

#### Who can use Audit log API keys?

Only **Organization Owners** can create and use Admin API keys for the purpose of pulling Audit Logs. Audit logging must be enabled (see the previous step) before the Admin API will return any data.

#### Authentication for the Compliance Logs Platform

Owners generate the Compliance API key in the **OpenAI API Platform Portal**. Make sure the **correct Organization** is selected when creating the key — it must correspond to the workspace being administered. **Do not select the owner's personal organization.**

When creating the key, use:

- **Settings**: _Default Project_ | _All Permissions_

A few important constraints:

- This must be a **new** key. Once Compliance API scopes are granted to it, all other scopes on the key are revoked.
- The key value can only be **viewed/copied once at creation time** — store it securely.

To enable Compliance API access on the key:

1. Email **[support@openai.com](mailto:support@openai.com)** with:
   - The **last 4 digits** of the API key.
   - The **Key Name**.
   - The **Created By** name.
   - The **requested scope** (`read`, `delete`, or both).
2. OpenAI's team will verify the key and grant the requested Compliance API scopes.
3. Once the key has Compliance scopes, administrators can use it directly or hand it to a partner for use against the Compliance API.

Use `https://api.chatgpt.com/v1/` as the base URL for all Compliance API endpoints.

</~XSIAM>