Microsoft 365 Defender Pack.#This Playbook is part of the
Supported Cortex XSOAR versions: 6.5.0 and later.
This playbook retrieves email data based on the
MessageID inputs. The output is a unified object with all of the retrieved emails based on the following sub-playbooks outputs:
- Microsoft 365 Defender - Get Email URL clicks: Retrieves data based on URL click events.
- Microsoft 365 Defender - Emails Indicators Hunt: Retrieves data based on several different email events.
Read the playbooks' descriptions in order to get the full details.
This playbook uses the following sub-playbooks, integrations, and scripts.
- Microsoft 365 Defender - Get Email URL Clicks
- Microsoft 365 Defender - Emails Indicators Hunt
This playbook does not use any integrations.
This playbook does not use any commands.
|Domain or URL to search within emails. Can be a single domain or URL, or an array of domains or URLs to search.
|The SHA256 hash file or an array of hashes to search within emails.
|The source or destination IP address to search. Can be a single address or an array of IP addresses.
|Message ID of the email from which the URL was clicked. Note that this can be either of the following 2 values:
- The value of the header "Message-ID".
- The internal ID of the message within Microsoft's products (e.g NetworkMessageId).
Can be a single MessageID or an array of NMessageIDs to search.
|The time limit in seconds for the HTTP request to run.
|Number of days past to search.
|Number of retrieved entries. Enter -1 for unlimited query.
|The mailbox of the listening integration. In case it is provided, the emails found in it will be ignored.
|Email objects containing relevant fields related to URL click events.
|Public-facing identifier for the email that is set by the sending email system. This will be the value of the "Message-ID" header.
|Sender domain in the FROM header, which is visible to email recipients on their email clients.
|Direction of the email relative to your network: Inbound, Outbound, Intra-org.
|Location where the email was delivered: Inbox/Folder, On-premises/External, Junk, Quarantine, Failed, Dropped, Deleted items.
|List of pass or fail verdicts by email authentication protocols like DMARC, DKIM, SPF or a combination of multiple authentication types (CompAuth).
|Delivery action of the email: Delivered, Junked, Blocked, or Replaced.
|Subject of the email.
|Number of attachments in the email.
|Detection name for malware or other threats found.
|Email address of the recipient, or email address of the recipient after distribution list expansion.
|Final action taken on the email based on filter verdict, policies, and user actions: Move message to junk mail folder, Add X-header, Modify subject, Redirect message, Delete message, Send to quarantine, No action taken, Bcc message.
|Sender email address in the FROM header, which is visible to email recipients on their email clients.
|Date and time when the record was generated.
|Sender display name.
|IPv4 address of the last detected mail server that relayed the message.
|List of confidence levels of any spam or phishing verdicts. For spam, this column shows the spam confidence level (SCL), indicating if the email was skipped (-1), found to be not spam (0,1), found to be spam with moderate confidence (5,6), or found to be spam with high confidence (9). For phishing, this column displays whether the confidence level is "High" or "Low".
|Verdict from the email filtering stack on whether the email contains malware, phishing, or other threats.
|SHA256 of the attachments (if exists in the email).
|URL that was clicked.
|Number of embedded URLs in the email.
|IPv6 address of the last detected mail server that relayed the message.
|User principal name (UPN) of the account.
|Indicates whether the user was able to click through to the original URL or not.
|Threshold assigned to email from bulk mailers. A high bulk complain level (BCL) means the email is more likely to generate complaints, and thus more likely to be spam.
|IP address assigned to the device during communication.
|Methods used to detect whether the URL contains or leads to malware, phishing, or other threats.
|Type of activity that triggered the event.
|List of URLs in the redirection chain.
|Unique identifier for the email, generated by Office 365.
|Name of the sender displayed in the address book, typically a combination of a given or first name, a middle initial, and a last name or surname.
|Sender domain in the MAIL FROM header, also known as the envelope sender or the Return-Path address.
|Sender email address in the MAIL FROM header, also known as the envelope sender or the Return-Path address.
|Date and time when the record was generated (url click).