Common Scripts

Extracts the text from a QR code. The output of this script includes the output of the script "extractIndicators" run on the text extracted from the QR code.

Changes the remediation SLA once a change in incident severity occurs.
This is done automatically and the changes can be configured to your needs.

Adds provided entries to the incident Evidence Board. In playbook, can be positioned after a task to add the previous task's entries to Evidence Board automatically (with no need to provide arguments)

Executes a test for all integration instances available and returns detailed information about succeeded and failed integration instances.

Set multiple keys/values to the context.

Indicates whether a given value is a member of given array

Encodes an input to Base64 format.

Creates a Grid table from items or key-value pairs.

Will encode an input using Base64 format.

DNS lookup utility to provide 'A' and 'PTR' record.

Converts Base64 file in a list to a binary file and upload to warroom

Gets hashes (MD5,SHA1,SHA256) from context.

Gets all currently enabled integration instances.

Sets a custom incident field with current date

Edit the server configuration (under settings/troubleshooting). You can either add a new configuration or update and remove an existing one.

Export given array to csv file.

Add a remote system (such as a desktop under investigation) to an investigation (this will allow you to install and agent on the system)

Set a value in context under the key you entered. If no value is entered, the script doesn't do anything.

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here:

• For Cortex XSOAR 6 see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.x/Cortex-XSOAR-Playbook-Design-Guide/Automations
• For Cortex XSOAR 8 Cloud see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Create-a-script
• For Cortex XSOAR 8.7 On-prem see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Create-a-script

Compares a single timestamp to a list of timestamps.

The script takes one or more IP addresses and checks whether they're in the private IP ranges defined in the PrivateIPsListName argument. By default, the PrivateIPsListName argument will use the Cortex XSOAR list called "PrivateIPs".
The list can be modified, and by default uses the ranges defined by the Internet Assigned Numbers Authority (IANA). The following are the default CIDR ranges for private IPv4 addresses:

• 10.0.0.0/8 (range: 10.0.0.0 to 10.255.255.255)
• 172.16.0.0/12 (range: 172.16.0.0 to 172.31.255.255)
• 192.168.0.0/16 (range: 192.168.0.0 to 192.168.255.255)
  In addition to ranges, it's also possible to add specific IP addresses to the list. You may also tag IPs or IP ranges by adding a comma after the IP or range, and then adding the tag that you want to tag the corresponding IP indicators with.

Return indicators appears in resolved incidents, and resolved incident ids.

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here:

• For Cortex XSOAR 6 see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.x/Cortex-XSOAR-Playbook-Design-Guide/Automations
• For Cortex XSOAR 8 Cloud see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Create-a-script
• For Cortex XSOAR 8.7 On-prem see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Create-a-script

Deprecated. Use the MatchRegexV2 script instead.

Generate report summaries for the passed incidents.

This script is designed to analyze a PFX (Personal Information Exchange) file for various suspicious or noteworthy characteristics from a security perspective.

Enrich and calculate the reputation of a certificate indicator.

Uses the Core REST API integration to query the server audit trail logs, and return back a CSV or JSON file.

The automation takes Excel file (entryID) as an input and parses its content to the war room and context.

This automation calculates the similarity ratio between every string in 2 different arrays and outputs a decimal value between 0.0 and 1.0 (1.0 if the sequences are identical, and 0.0 if they don't have anything in common).

Adds/Replaces a key in key/value store backed by an XSOAR list.

Pretty-print data using Python's pprint library. This is useful for seeing the structure of incident and context data. Here's how to use it:

!PrettyPrint value=${incident}

Replaces regex match/es in string.
Returns the string after replace was preformed.

List the redirects for a given URL

This stops the scheduled task whose ID is given in the taskID argument.

This script displays the execution results of the tab's buttons in an HTML table format.

Mark entries as notes if they are tagged with given tag.

Extract regular text from the given HTML.

Searches for string in context and returns context path, returns null if not found.

Runs the polling command repeatedly, completes a blocking manual task when polling is done.

Strips, unquotes and unescapes URLs. If the URL is a Proofpoint or ATP URL, extracts its redirect URL. If more than one URL is passed to the formatter, the separator must be a pipe ("|").

Load a PDF file's content and metadata into context. Supports extraction of hashes, urls, and emails when available.

Sends an email informing the user of an SLA breach. The email is sent to the user who is assigned to the incident. It includes the incident name, ID, name of the SLA field that was breached, duration of that SLA field, and the date and time when that SLA was started.
In order to run successfully, the script should be configured to trigger on SLA breach, through field edit mode.

Input Text Data to Encode as ASCII (Ignores any chars that aren't interpreted as ASCII)

Filter context keys by applying one of the various available manipulations and storing in a new context key. Please notice that the resulting context key will not be available automatically as an option but you can still specify it.

This script updates an indicator's grid field in Cortex XSOAR with provided row data. You can input the rows directly or extract them from the context.

Removes a key in key/value store backed by an XSOAR list.

Called by the GenericPolling playbook, schedules the polling task.

Deprecated. Use DBotPreProcessTextData instead.

Returns yes if the IP is in one of the ranges provided, returns no otherwise.

Script to convert a War Room output JSON File to a CSV file.

This button will generate summary 'Case Report' template for a given Incident

Generate a JSON file that can be downloaded and used to create the As-Built document for Cortex XSOAR.

Returns wether a PDF is both valid and encrypted.

Populates critical assets in a grid field that has the section headers "Asset Type" and "Asset Name".

Data output script for populating dashboard pie graph widget with the percentage of incidents closed by DBot vs. incidents closed by analysts.

Execute a command on a remote machine (without installing a D2 agent)

Check if list exist in demisto lists.

Convert an array to a nice table display. Usually, from the context.

Uses the ssh integration to grab the host server logs. This script is supported only on Cortex XSOAR on-prem (version 6.X).

Deprecated. Use ParseEmailFilesV2 instead." Parse an email from an eml or msg file and populate all relevant context data to investigate the email. Also extracts inner attachments and returns them to the war room. The incident labels themselves are preserved and not modified - only the "Label/x" context items that originated from the labels, and the best practice is to rely on these for the remainder of the playbook.

Calculates the entropy for the given data.

Display the mapped fields in a dynamic-section.

Identify whether the incident includes an email message attached as an eml or msg file and return the answer to playbook. Also saves the identified entry ID to context for use for later. Commonly used in automated playbooks that handle phishing reports sent to a special phishing mailbox set up by the security team.

The script downloads a Python library using PIP, archives it, and returns the file to the war room.

Extract strings from a file with optional filter - similar to binutils strings command

Utility script to use in playbooks - returns "yes" if the input is non-empty.

Deprecated. Use the "PhishingDedupPreprocessingRule" script instead.
Find duplicate incidents candidates.
Using machine learning techniques with pre-defined data (can also use data from the local environment), this script takes into consideration different features such as: labels comparison, email labels (relevant for phishing), incident time difference and shared indicators, which can be customized by the arguments.

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here:

• For Cortex XSOAR 6 see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.x/Cortex-XSOAR-Playbook-Design-Guide/Automations
• For Cortex XSOAR 8 Cloud see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Create-a-script
• For Cortex XSOAR 8.7 On-prem see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Create-a-script

Encode a file as base64 and store it in a Demisto list.

This script checks that a context key exists (and contains data), and optionally checks the value of the context key for a match against an input value. If a regex is not supplied, the script checks that the key is not empty. This script can be used with the "GenericPolling" playbook to poll for field population or that a field contains a specific value. This scripts does not support a context key which holds a list of values.

A context script for URL entities.

Verifies that an email address is valid and only returns the address if it is valid.

Checks if the Docker container running this script has been hardened according to the recommended settings at:

• For Docker hardening guide (Cortex XSOAR 6.13) https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.13/Cortex-XSOAR-Administrator-Guide/Docker-Hardening-Guide
• For Docker hardening guide (Cortex XSOAR 8 Cloud) https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Docker-hardening-guide
• For Docker hardening guide (Cortex XSOAR 8.7 On-prem) https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Docker-hardening-guide.

Sends a HTTP request with advanced capabilities.

Retrieves the current date and time.

This script is only meant to be used to disable the Enrich Excluded button in an indicator. It should not be used otherwise.

This script finds similar files that can be related to each other by fuzzy hash (SSDeep).

Deprecated. Use FileCreateAndUploadV2 instead. Will create a file (using the given data input or entry ID) and upload it to current investigation war room.

Widget script to view information about the relationship between an indicator, entity and other indicators and connect to indicators, if relevant.

Check if an email address's domain is trying to squat other domain using Levenshtein distance algorithm.

Get the string distance for the sender from our domain

This is a wrapper to isolate or unisolate hash lists from Cortex XDR, MSDE or CrowdStrike (Available from Cortex XSOAR 6.0.0).

Sleep for X seconds.

Checks if the email address is part of the internal domains.

Expose the incident owner into IncidentOwner context key

A context script for hash entities.

Gets all IP addresses in context, excluding ones given.

Searches Cortex XSOAR Incidents and returnrs the most relevant fields. Default search range is the last 30 days, if you want to change this, use the fromDate argument.

Returns the id, name, type, severity, status, owner, and created/closed times to context. You can add additional fields using the add_field_to_context argument.

This automation runs using the default Limited User role, unless you explicitly change the permissions. Based on the SearchIncidentsV2 from the Common Scripts pack, but more efficient.

Delete field from context.

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here:

• For Cortex XSOAR 6 see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.x/Cortex-XSOAR-Playbook-Design-Guide/Automations
• For Cortex XSOAR 8 Cloud see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Create-a-script
• For Cortex XSOAR 8.7 On-prem see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Create-a-script

Parses a list by header and value.

Ask a user a question via email and process the reply directly into the investigation.

This script resolves the original URL from a given shortened URL and places the resolved URL in the playbook context and output.

Find tables inside HTML and extract the contents into objects using the following logic:

• If table has a single column, just create an array of strings from the values
• If table has 2 columns and has no header row, treat the first column as key and second as value and create a table of key/value
• If table has a header row, create a table of objects where attribute names are the headers
• If table does not have a header row, create table of objects where attribute names are cell1, cell2, cell3…

Publish entries to incident's context

Will create an array object in context from given string input

Converts a given array to an HTML table

Creates indicators from the submitted STIX file. Supports STIX 1.0 and STIX 2.x. This automation creates indicators and adds an indicator's relationships if available.

Unzip a file using fileName or entryID to specify a file. Unzipped files will be loaded to the War Room and names will be put into the context.

Checks if the supplied URLs are in the specified domains.

A script to generate investigation summary report in an automated way
Can be used in post-processing flow as well.

A context script for Email entities.

Content packs installer from marketplace.

Checks if the supplied hostnames match either the organization's internal naming convention or the domain suffix.

Set a value built by a template in context under the key you entered.

Converting time in Ticks to readable time. Ticks are used to represent time by some vendors, most commonly by Microsoft.

Checks whether the PDF file is encrypted.

Returns the license ID.

Find the top malicious ratio indicators.
Malicious ratio is defined by the ratio between the number of "bad" incidents divided by the number of total number of incidents that the indicators appears in.

This script searches for a value in a context path.

Check if a given value is true. Will return 'no' otherwise

The script calculates the average DBot score for each indicator in the context.

Not in context verification is a script that executes the given command and verifies that the specified field is not in the context after execution.

Prints text to war room (Markdown supported)

Incident action button script to link or unlink Incidents from an Incident

Gets a value from the specified incident's context.

Converts XML file entry to JSON format

Load the contents of a file into context.

Verifies if the given input contains valid IP addresses (IPv4 or IPv6).

Used to extract indicators from Word files (DOC, DOCX).
The script does not extract data from macros (e.g., embedded code).

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here: - For Cortex XSOAR 6 see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.x/Cortex-XSOAR-Playbook-Design-Guide/Automations - For Cortex XSOAR 8 Cloud see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Create-a-script - For Cortex XSOAR 8.7 On-prem see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Create-a-script

Gets all email addresses in context, excluding ones given.

This script allows sending an HTML email, using a template stored as a list item under Lists (Settings -> Advanced -> Lists).
Placeholders are marked in DT format (i.e. ${incident.id} for incident ID).
Available placeholders for example:

• ${incident.labels.Email/from}
• ${incident.name}
• ${object.value}
  See incident Context Data menu for available placeholders

Note: Sending emails require an active Mail Sender integration instance.

Parse an email from an eml or msg file and populate all relevant context data to investigate the email. Also extracts inner attachments and returns them to the war room. The incident labels themselves are preserved and not modified - only the "Label/x" context items that originated from the labels, and the best practice is to rely on these for the remainder of the playbook. This script is based on the parse-emails XSOAR python package, check the script documentation for more info.

Converts a simple Array into a textual comma separated string

This script pre-processes (resizes, sharpens, and grayscales) an image file from context, given an entry_id.

Generates a random UUID (UUID 4).

When you apply this script to an incident field, that incident field is hidden for new incidents, and it displays in edit mode.

Converts a date from a different timezone to UTC timezone.

Extracts regex data from the provided text. The script support groups and looping.

Deprecated. No available replacement. Search for a binary on an endpoint using Carbon Black

Generates random string

Parses a CSV and looks for a specific value in a specific column, returning a dict of the entire matching row. If no column value is specified, the entire CSV is read into the context.

Schedule a command to run inside the war room at a future time (once or reoccurring)

Take a list of devices and pull a specific file (given by path) from each using SCP.

Create indicators to the Threat Intel database only if they are not registered. All submitted indicators will be associated with the parent incident. When using the script with many indicators, or when the Threat Intel Management database is highly populated, this script may have low performance issue.

Works the same as the 'Set' command, but can work across incidents by specifying 'id' as an argument.
Sets a value into the context with the given context key. Doesn't append by default.

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here:

• For Cortex XSOAR 6 see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.x/Cortex-XSOAR-Playbook-Design-Guide/Automations
• For Cortex XSOAR 8 Cloud see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Create-a-script
• For Cortex XSOAR 8.7 On-prem see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Create-a-script

This automation uses the Core REST API Integration to batch export Indicators to CSV and return the resulting CSV file to the war room.

Shows a bar chart of the number of Positive Detections out of overall detections

Joins values from two lists by index according to a given format.

Count an array size

Returns DNS details for a domain.

Shows a bar chart of the number of incident the 'To' and 'From' email addresses.

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here:

• For Cortex XSOAR 6 see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.x/Cortex-XSOAR-Playbook-Design-Guide/Automations
• For Cortex XSOAR 8 Cloud see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Create-a-script
• For Cortex XSOAR 8.7 On-prem see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Create-a-script

Creating a hash of a given input, support sha1, sha256, sha512, md5 and blake. Wrapper for https://docs.python.org/3/library/hashlib.html.

Sends http request. Returns the response as json.

Extract indicators from a text-based file.
Indicators that can be extracted:

• IP
• Domain
• URL
• File Hash
• Email Address

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here:

• For Cortex XSOAR 6 see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.x/Cortex-XSOAR-Playbook-Design-Guide/Automations
• For Cortex XSOAR 8 Cloud see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Create-a-script
• For Cortex XSOAR 8.7 On-prem see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Create-a-script

Returns a string with all matches of a regex pattern groups replaced by a replacement.

This script allows disabling a specified user using one or more of the following integrations: SailPointIdentityIQ, ActiveDirectoryQuery, Okta, MicrosoftGraphUser, and IAM.

Stops the "Time To Assign" timer if the owner of the incident was changed.

Script will run the provided mathematical action on 2 provided values and produce a result.
The result can be stored on the context using the contextKey argument

Uses the ssh integration to grab the host server logs. This script is supported only on Cortex XSOAR on-prem (version 6.X).

Mark entries as evidence if they are tagged with given tag

Set indicator reputation to "suspicious" when malicious ratio is above threshold.
Malicious ratio is the ration between number of "bad" incidents to total number of incidents the indicator appears in.

Decode MIME base64 headers.

Check if a given value is true. Will return 'no' otherwise

The script takes one or more domain names and checks whether they're in the Cortex XSOAR list defined in the InternalDomainsListName argument. By default, the InternalDomainsListName argument will use the Cortex XSOAR list called "InternalDomains".
The list can be customized by the user. It should contain the organization's internal domain names, separated by new lines. Subdomains are also supported in the list.
The results of the script are tagged with the "Internal_Domain_Check_Results" tag, so they can be displayed in the War Room entry sections in incident layouts.

This dynamic automation parses the CVSS score of a CVE and presents it in the layout in color according to its score.

Provides the severity of the CVE based on the CVSS score where available.

Deprecated. Use the UnzipFile script instead. UnPack a file using fileName or entryID to specify a file. Files unpacked will be pushed to the war room and names will be pushed to the context.
supported types are:
7z (.7z), ACE (.ace), ALZIP (.alz), AR (.a), ARC (.arc), ARJ (.arj), BZIP2 (.bz2), CAB (.cab), compress (.Z), CPIO (.cpio), DEB (.deb), DMS (.dms), GZIP (.gz), LRZIP (.lrz), LZH (.lha, .lzh), LZIP (.lz), LZMA (.lzma), LZOP (.lzo), RPM (.rpm), RAR (.rar), RZIP (.rz), TAR (.tar), XZ (.xz), ZIP (.zip, .jar) and ZOO (.zoo)

This script evaluates command-line threats by analyzing both original and decoded inputs. It assigns weighted scores to detected patterns, such as AMSI bypass or credential dumping, and applies risk combination bonuses for multiple detections. The total score is normalized to a 0-100 scale, with risk levels categorized as follows:

• 0-25: Low Risk
• 26-50: Medium Risk
• 51-90: High Risk
• 91-100: Critical Risk

The scoring mechanism provides a comprehensive risk assessment, considering both the severity and frequency of malicious behaviors.

Deprecated. Use PCAPMinerV2 instead. PCAPMiner is a tool to parse PCAP files and will return things like extracted files that are found, HTTP flows, and a variety of other information. It is uses a docker instance located on docker hub trorabaugh/dempcap:1.0. To use simply upload a PCAP file and then run PCAPMiner entryId="<your_entry_id>". To get the entry id click on the link on the top right hand corner of a file attachment.

Lookup incidents with specified indicator. Use currentIncidentId to omit the existing incident from output.

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here:

• For Cortex XSOAR 6 see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.x/Cortex-XSOAR-Playbook-Design-Guide/Automations
• For Cortex XSOAR 8 Cloud see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Create-a-script
• For Cortex XSOAR 8.7 On-prem see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Create-a-script

Extract URLs redirected by security tools like Proofpoint.
Changes https://urldefense.proofpoint.com/v2/url?u=https-3A__example.com_something.html -> https://example.com/something.html
Also, un-escape URLs that are escaped for safety with formats like hxxps://www[.]demisto[.]com

Verify that the address is a valid IPv6 address.

Removing the password protection from a PDF file and adding a new file entry with the unlocked PDF.

Verifies if the supplied JSON string is valid and optionally verifies against a provided schema. The script utilizes Powershell's Test-JSON cmdlet.

Prints a raw representation of a string or object, visualising things likes tabs and newlines. For instance, '\n' will be displayed instead of a newline character, or a Windows CR will be displayed as '\r\n'. This is useful for debugging issues where things aren't behaving as expected, such as when parsing a string with a regular expression.

compares two JSON files and returns their differences, such as added, removed, or changed fields, in a structured format.

Fill the current time in a custom incident field

This script is used to display the indicators of an incident in an incident field of type Array. It can be used to select indicators from the incident in order to later perform some actions, like tagging the indicators for blocking via EDL.
This script is a field-display script, so it needs to be configured as such, when editing the incident field that will be used to display the indicators.

Pings an IP or url address, to verify it's up. Note - On Cortex XSOAR 8 and Cortex XSIAM, the script can run only on a custom engine.

Convert country name to country code or country code to country name.
Only one of 'country_code' or 'country_name' can be provided.
Example:
Input: { "country_code": "US" }
Output: { "United States" }
Another Example:
Input: { "country_name": "United States" }
Output: { "US" }.

Display HTML with embedded images.

A context script for IP entities.

Verify that the CIDRs are valid.

Converts a file from one format to a different format by using the convert-to function of Libre Office. For a list of supported input/output formats see: https://wiki.openoffice.org/wiki/Framework/Article/Filter/FilterList_OOo_3_0

Checks whether the specified item is in a list. The default list is the Demisto Indicators Whitelist.

Parse CEF data into the context. Please notice that outputs will display only the 7 mandatory fields even if the CEF event includes many other custom or extended fields.

Extracts hyperlinks from office files. Supported file types are: xlsx, docx, pptx.

Returns a dict of all incident fields that exist in the system.

Compare two lists and put the differences in context.

Extract Domain(s) from URL(s) and/or Email(s).

Fetches the numbers of ads in the given url.

Converts HTML to Markdown.

Parse RDP bitmap cache data into a single collage image file.

Set a value in context under the key you entered.

Get the error(s) associated with a given entry/entries. Use ${lastCompletedTaskEntries} to check the previous task entries. The automation will return an array of the error contents from those entries.

Calculate the time difference, in minutes.

Optionally increases the incident severity to the new value if it is greater than the existing severity.

This script adds the reputation to Onion URL indicators. The script is automatically triggered when a Onion URL indicator is auto-extracted. For instance, if you run a Cortex XSOAR CLI on a valid Onion URL, the indicators are extracted automatically and this script is triggered for the extracted indicators.

Check whether given entry/entries returned an error. Use ${lastCompletedTaskEntries} to check the previous task entries. If array is provided, will return yes if one of the entries returned an error.

Generate an as built document, as HTML, based on the running XSOAR instance. Requires an instance of the Demisto API integration configured.

This command will allow you to run commands against a local Docker Container. You can run commands like wc for instance with word count, or other types of commands that you want on the docker container.

We recommend for tools that you want to use that are not part of the default Docker container, to cope this Automation script and then create a customer docker container with /docker_image_create with a custom docker container to add any command level tool to Demisto and output the results directly to the context.

Get the string distance between inputString and compareString (compareString can be a comma-separated list) based on Levenshtein Distance algorithm.

Loads a JSON file from the war room to context.

Marks given incidents as related to current incident.

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here:

• For Cortex XSOAR 6 see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.x/Cortex-XSOAR-Playbook-Design-Guide/Automations
• For Cortex XSOAR 8 Cloud see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Create-a-script
• For Cortex XSOAR 8.7 On-prem see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Create-a-script

List all Docker images that are in use by the installed integrations and automations.

This script calculates the CVSS Base Score, Temporal Score, and Environmental Score using either the CVSS 3.0 or CVSS 3.1 calculator according to https://www.first.org/cvss/ calculation documentation.

Searches Demisto incidents. A summarized version of this scrips is available with the summarizedversion argument.

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here:

• For Cortex XSOAR 6 see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.x/Cortex-XSOAR-Playbook-Design-Guide/Automations
• For Cortex XSOAR 8 Cloud see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Create-a-script
• For Cortex XSOAR 8.7 On-prem see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Create-a-script
  https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.10/Cortex-XSOAR-Administrator-Guide/Automations

Takes the comments of a given entry ID and stores them in the incident context, under a provided context key.
For accessing the last executed task's comments, provide ${lastCompletedTaskEntries.[0]} as the value for the entryId input parameter.

Send message to Demisto online users over Email, Slack, Mattermost or all.

Collect entries matching to the conditions in the war room.

Extracts FQDNs from URLs and emails.

Gets a value and return it. This is to be used in playbook conditional tasks - get a value from incident field, label or context, and act accordingly.
If an array is returned. the first value will be the decision making value.

Extract Attack Pattern Threat Intel Object. After auto extract extracts the Attack Pattern IDs, this script is executed and extracts the value (name) of the Attack Pattern.

Get a MITRE ATT&CK object name by its ID. The script is using TIMs IOCs to find the correct name. (MITRE ATT&CK IOCs must exist in the Threat Intel data).

This script will parse a CSV file and place the unique IPs, Domains and Hashes into the context.

This function generates a password and allows various parameters to customize the properties of the password depending on the use case (e.g. password complexity requirements). The default behavior is to generate a password of random length including all four character classes (upper, lower, digits, symbols) with at least five and at most ten characters per class.

The min_* values all default to 0. This means that if the command is executed in this way:
!GeneratePassword max_lcase=10
It is possible that a password of length zero could be generated. It is therefore recommended to always include a min_* parameter that matches.

The debug parameter will print certain properties of the command into the WarRoom for easy diagnostics.

Searches Cortex XSOAR Indicators.

Search for XSOAR Indicators and returns the id, indicator_type, value, and score/verdict.

You can add additional fields from the indicators using the add_field_to_context argument.

Assign analyst to incident.
By default, the analyst is picked randomly from the available users, according to the provided roles (if no roles provided, will fetch all users).
Otherwise, the analyst will be picked according to the 'assignBy' arguments.
machine-learning: DBot will calculated and decide who is the best analyst for the job.
top-user: The user that is most commonly owns this type of incident
less-busy-user: The less busy analyst will be picked to be the incident owner.
online: The analyst is picked randomly from all online analysts, according to the provided roles (if no roles provided, will fetch all users).
current: The user that executed the command.

Automation used to more easily populate a grid field. This is necessary when you want to assign certain values as static or if you have context paths that you will assign to different values as well. Instead of a value you can enter TIMESTAMP to get the current timestamp in ISO format. For example:
!GridFieldSetup keys=ip,src,timestamp val1=${AWS.EC2.Instances.NetworkInterfaces.PrivateIpAddress} val2="AWS" val3="TIMESTAMP" gridfiled="gridfield".

Checks if one percentage is less than another
Returns less: if firstPercentage < secondPercentage
Returns more: if firstPercentage >= secondPercentage
Returns exception if one of the inputs is not a float

Get the overall score for the indicator as calculated by DBot.

Exports context data to a Microsoft Excel Open XML Spreadsheet (XLSX) file.

Deprecated. Use DBotFindSimilarIncidents instead.

Finds similar incidents by common incident keys, labels, custom fields or context keys.
It's highly recommended to use incident keys if possible (e.g., "type" for the same incident type).
For best performance, it's recommended to avoid using context keys if possible (for example, if the value also appears in a label key, use label).

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here:

• For Cortex XSOAR 6 see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.x/Cortex-XSOAR-Playbook-Design-Guide/Automations
• For Cortex XSOAR 8 Cloud see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Create-a-script
• For Cortex XSOAR 8.7 On-prem see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Create-a-script

Checks whether a port was open on given host.

Extracts domains and FQDNs from URLs and emails.

Takes UTC and converts it to the specified timezone. Format must match the UTC date's format and output will be the same format. Can use in conjunction with ConvertDateToString

Recursively un-escapes JSON data if escaped JSON is found

Finds which integrations implement a specific Demisto command. The results will be returned as comma-separated values (CSV). The "Core REST API" integration must first be enabled.

Returns the length of the string passed as argument

Zip a file and upload to war room.

Map the given values to the translated values. If given values: a,b,c, and translated: 1,2,3, then the input will return 1.

Add into the incident's context the system internal DBot score for the input indicator.

Close the current investigation as duplicate to other investigation.

Copy a context key to an incident field of multiple incidents, based on an incident query.

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here:

• For Cortex XSOAR 6 see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.x/Cortex-XSOAR-Playbook-Design-Guide/Automations
• For Cortex XSOAR 8 Cloud see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Create-a-script
• For Cortex XSOAR 8.7 On-prem see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Create-a-script

Runs a specified polling command one time. This is useful for initiating a local playbook context before running a polling scheduled task.

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here:

• For Cortex XSOAR 6 see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.x/Cortex-XSOAR-Playbook-Design-Guide/Automations
• For Cortex XSOAR 8 Cloud see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Create-a-script
• For Cortex XSOAR 8.7 On-prem see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Create-a-script

Gather information regarding CIDR -
1. Broadcast_address
2. CIDR
3. First_address
4. Last address
5. Max prefix len
6. Num addresses
7. Private
8. Version.

Allows to parse and extract http flows (requests & responses) from a pcap/pcapng file.

Read image files metadata and provide Exif tags.

Returns 'yes' if integration brand is available. Otherwise returns 'no'.

Try to get the hostname correlated with the input IP.

Verify URL SSL certificate.

Gets docker image latest tag. Script simulates the docker pull flow but doesn't actually pull the image. Returns an entry with the docker image latest tag if all is good, otherwise will return an error.

Takes an input docx file (entryID) as an input and saves an output text file (file entry) with the original file's contents.

This script checks that a field exists (and contains data), and optionally checks the value of the field for a match against an input value. If a regex is not supplied, the script checks that the field is not empty. This script can be used with the "GenericPolling" playbook to poll for field population or that a field contains a specific value.

Checks if the investigation found any malicious indicators (file, URL, IP address, domain, or email). Returns "yes" if at least one malicious indicator is found.

Returns the incident field names associated to the specified incident type.

Remove escaping chars from IP
127[.]0[.]0[.]1 -> 127.0.0.1

Gets a list of indicators from the indicators argument, and generates a JSON file in STIX 2.1 format.

Convert a JSON War Room output via EntryID to a CSV file.

Converts XML string to JSON format

Get the Server URL.

Given a list of objects and a key found in each of those objects, return a unique list of values associated with that key. Returns error if the objects provided do not contain the key of interest.

Show all scheduled entries for specific incident.

Calculate ssdeep reputation based on similar files (by ssdeep similarity) on the system.

This script accepts multiple values for both arguments and will iterate through each of the domains to check if the specified subdomains are located in at least one of the specified main domains. If the tested subdomain is in one of the main domains, the result will be true. For example, if the domain_to_check values are apps.paloaltonetworks.com and apps.paloaltonetworks.bla and the domains_to_compare values are paloaltonetworks.com and demisto.com, the result for apps.paloaltonetworks.com will be true since it is a part of the paloaltonetworks.com domain. The result for apps.paloaltonetworks.bla will be false since it is not a part of the paloaltonetworks.com or demisto.com domain.

Exports the Context for the current Incident to a JSON file in the war room.

Prints an error entry with a given message.

Fetches indicators from a file. Supports TXT, XLS, XLSX, CSV, DOC and DOCX file types.

Extract fields from a certificate file and return the standard context.

A context script for Domain entities

Returns a map entry with a marker on the given coordinates (lat,lng), or address (requires a configured GoogleMaps instance).

Returns integration instances configured in Cortex XSOAR. You can filter by instance status and/or brand name (vendor).

Extract user's response from EmailAskUser reply. Returns the first textual response line of the provided entry that contains the reply body. Use ${lastCompletedTaskEntries} to analyze the previous playbook task containing the user's reply.

Compares the labels of two incidents. Returns the labels that are unique to each incident.

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here:

• For Cortex XSOAR 6 see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.x/Cortex-XSOAR-Playbook-Design-Guide/Automations
• For Cortex XSOAR 8 Cloud see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Create-a-script
• For Cortex XSOAR 8.7 On-prem see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Create-a-script

Use this script to avoid DB version errors when simultaneously running multiple linked incidents.

This automation uses the Core REST API Integration to batch export Incidents to CSV and return the resulting CSV file to the war room.

Parses a YAML string into context.

A wrapper script to the 'AppendindicatorField' script that enables adding tags to certain indicators.
Note: You can use this script in an incident Layout button to allow tags to be added to indicators through the incident.

This script will extract indicators from given HTML and will handle bad top-level domains to avoid false positives caused by file extensions.

Creates a file (using the given data input or entry ID) and uploads it to the current investigation War Room.

Dumps a json from context key input, and returns a json object string result

Searches for string in a path in context. If path is null, string will be searched in full context.

This widget displays the incident verdict or the alert verdict based on the 'incident.verdict' or 'alert.verdict' field.

Pretty-print the contents of the playbook context.

Return the Demisto server version.

Check whether the values provided in arguments are equal. If either of the arguments are missing, no is returned.

Add DBot score to context for indicators with custom vendor, score, reliability, and type.

Analyze a list of Unix timestamps in milliseconds, to detect simple patterns of consistency or high frequency. The script can aid in the investigation of multi-event alerts that contain a list of timestamps.

Enables changing context in two ways. The first is to capitalize the first letter of each key in following level of the context key entered. The second is to change context keys to new values.

Generates the URL for a Data Collection Task into Context. Can be used to get the url for tasks send via Email, Slack, or even if you select "By Task Only".

To generate links for specific users, add an array of users in the users argument.

Lists executed commands in War Room

Sends email to incident owner when selected field is triggered.

Assigns the current Incident to the Cortex XSOAR user who clicked the button

Checks if one number(float) as bigger than the other(float)
Returns yes: if first > second
Returns no: if first <= second
Returns exception if one of the inputs is not a number

aquatone-discover will find the targets nameservers and shuffle DNS lookups between them. Should a lookup fail on the target domains nameservers, aquatone-discover will fall back to using Google public DNS servers to maximize discovery.

Check if indicators exist in the Threat Intel database.

Language detection based on Google's language-detection.

After running DeleteContext, this script can repopulate all the file entries in the ${File} context key

Check if a given value exists in the context. Will return 'no' for empty empty arrays. To be used mostly with DQ and selectors.

Copy all entries marked as notes from current incident to another incident.

Show indicator geo location on map.

This is only an example script, to showcase how to use and write JavaScript scripts

Display HTML in the War Room.

Loads a json from string input, and returns a json object result.

The status of the media notification

Is account information breached

Is the DPO confirm the breach

"A data protection impact assessment (…) shall in particular be required in the case of: (a) a systematic and extensive evaluation of personal aspects relating to natural persons which is based on automated processing, including profiling, and on which decisions are based that produce legal effects concerning the natural person or similarly significantly affect the natural person; (b) processing on a large scale of special categories of data referred to in Article 9(1), or of personal data relating to criminal convictions and offences referred to in Article 10; or (c) a systematic monitoring of a publicly accessible area on a large scale. - GDPR Art. 35

"In the case of a personal data breach, the controller shall without undue delay and, where feasible, not later than 72 hours after having become aware of it, notify the personal data breach to the supervisory authority competent in accordance with Article 55, unless the personal data breach is unlikely to result in a risk to the rights and freedoms of natural persons." - GDPR Art. 33

Is unique biometric data breached

"‘main establishment’ means: as regards a controller with establishments in more than one Member State, the place of its central administration in the Union, unless the decisions on the purposes and means of the processing of personal data are taken in another establishment of the controller in the Union and the latter establishment has the power to have such decisions implemented, in which case the establishment having taken such decisions is to be considered to be the main establishment; as regards a processor with establishments in more than one Member State, the place of its central administration in the Union, or, if the processor has no central administration in the Union, the establishment of the processor in the Union where the main processing activities in the context of the activities of an establishment of the processor take place to the extent that the processor is subject to specific obligations under this Regulation;" - GDPR Art. 4

" (d) describe the measures taken or proposed to be taken by the controller to address the personal data breach, including, where appropriate, measures to mitigate its possible adverse effects." - GDPR Art. 33

Is unique identification number breached

Is financial information breached

Is Medical Information breached

Is health insurance breached

Is other PII data breached

"‘personal data’ means any information relating to an identified or identifiable natural person (‘data subject’); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person;" - GDPR Art. 4

Deprecated. Use DBotPreProcessTextData instead.

Send message to Demisto online users over Email, Slack, Mattermost or all.

Set a value in context under the key you entered. If no value is entered, the script doesn't do anything.

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here:

• For Cortex XSOAR 6 see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.x/Cortex-XSOAR-Playbook-Design-Guide/Automations
• For Cortex XSOAR 8 Cloud see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Create-a-script
• For Cortex XSOAR 8.7 On-prem see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Create-a-script

Find the top malicious ratio indicators.
Malicious ratio is defined by the ratio between the number of "bad" incidents divided by the number of total number of incidents that the indicators appears in.

Mark entries as evidence if they are tagged with given tag

Content packs installer from marketplace.

Loads a JSON file from the war room to context.

Verifies that an email address is valid and only returns the address if it is valid.

Checks if the investigation found any malicious indicators (file, URL, IP address, domain, or email). Returns "yes" if at least one malicious indicator is found.

Set a value built by a template in context under the key you entered.

Check whether the values provided in arguments are equal. If either of the arguments are missing, no is returned.

Pings an IP or url address, to verify it's up. Note - On Cortex and Cortex XSIAM, the script can run only on a custom engine.

Parse RDP bitmap cache data into a single collage image file.

This script finds similar files that can be related to each other by fuzzy hash (SSDeep).

Show all scheduled entries for specific incident.

Checks whether a port was open on given host.

Converts Base64 file in a list to a binary file and upload to warroom

Prints a raw representation of a string or object, visualising things likes tabs and newlines. For instance, '\n' will be displayed instead of a newline character, or a Windows CR will be displayed as '\r\n'. This is useful for debugging issues where things aren't behaving as expected, such as when parsing a string with a regular expression.

Compares the labels of two incidents. Returns the labels that are unique to each incident.

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here:

• For Cortex XSOAR 6 see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.x/Cortex-XSOAR-Playbook-Design-Guide/Automations
• For Cortex XSOAR 8 Cloud see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Create-a-script
• For Cortex XSOAR 8.7 On-prem see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Create-a-script

Compares the labels of two alerts. Returns the labels that are unique to each alert.

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here:

• For Cortex XSOAR 6 see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.x/Cortex-XSOAR-Playbook-Design-Guide/Automations
• For Cortex XSOAR 8 Cloud see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Create-a-script
• For Cortex XSOAR 8.7 On-prem see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Create-a-script

Fetches the numbers of ads in the given url.

Fetches indicators from a file. Supports TXT, XLS, XLSX, CSV, DOC and DOCX file types.

Sends email to incident owner when selected field is triggered.

This script resolves the original URL from a given shortened URL and places the resolved URL in the playbook context and output.

Converts a simple Array into a textual comma separated string

Creating a hash of a given input, support sha1, sha256, sha512, md5 and blake. Wrapper for https://docs.python.org/3/library/hashlib.html.

Extract indicators from a text-based file.
Indicators that can be extracted:

• IP
• Domain
• URL
• File Hash
• Email Address

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here:

• For Cortex XSOAR 6 see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.x/Cortex-XSOAR-Playbook-Design-Guide/Automations
• For Cortex XSOAR 8 Cloud see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Create-a-script
• For Cortex XSOAR 8.7 On-prem see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Create-a-script

Sets a custom incident field with current date

Checks whether the specified item is in a list. The default list is the Demisto Indicators Whitelist.

Generate an as built document, as HTML, based on the running XSOAR instance. Requires an instance of the Demisto API integration configured.

Searches for string in context and returns context path, returns null if not found.

Add into the incident's context the system internal DBot score for the input indicator.

Checks if one number(float) as bigger than the other(float)
Returns yes: if first > second
Returns no: if first <= second
Returns exception if one of the inputs is not a number

Removing the password protection from a PDF file and adding a new file entry with the unlocked PDF.

Searches Cortex Indicators.

Search for XSOAR Indicators and returns the id, indicator_type, value, and score/verdict.

You can add additional fields from the indicators using the add_field_to_context argument.

This script will parse a CSV file and place the unique IPs, Domains and Hashes into the context.

Edit the server configuration (under settings/troubleshooting). You can either add a new configuration or update and remove an existing one.

Data output script for populating dashboard pie graph widget with the percentage of incidents closed by DBot vs. incidents closed by analysts.

Data output script for populating dashboard pie graph widget with the percentage of alerts closed by DBot vs. alerts closed by analysts.

Recursively un-escapes JSON data if escaped JSON is found

compares two JSON files and returns their differences, such as added, removed, or changed fields, in a structured format.

Indicates whether a given value is a member of given array

Assigns the current Incident to the Cortex user who clicked the button

This script will extract indicators from given HTML and will handle bad top-level domains to avoid false positives caused by file extensions.

Encode a file as base64 and store it in a Demisto list.

Zip a file and upload to war room.

Export given array to csv file.

Converts a given array to an HTML table

Checks if one percentage is less than another
Returns less: if firstPercentage < secondPercentage
Returns more: if firstPercentage >= secondPercentage
Returns exception if one of the inputs is not a float

Searches Demisto incidents. A summarized version of this scrips is available with the summarizedversion argument.

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here:
https://docs-cortex.paloaltonetworks.com/r/Cortex-XSIAM/Cortex-XSIAM-Administrator-Guide/Permission-Management

Searches Demisto alerts. A summarized version of this scrips is available with the summarizedversion argument.

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here:
https://docs-cortex.paloaltonetworks.com/r/Cortex-XSIAM/Cortex-XSIAM-Administrator-Guide/Permission-Management

A context script for hash entities.

Converting time in Ticks to readable time. Ticks are used to represent time by some vendors, most commonly by Microsoft.

Copy a context key to an incident field of multiple incidents, based on an incident query.

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here:

• For Cortex XSOAR 6 see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.x/Cortex-XSOAR-Playbook-Design-Guide/Automations
• For Cortex XSOAR 8 Cloud see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Create-a-script
• For Cortex XSOAR 8.7 On-prem see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Create-a-script

Exports context data to a Microsoft Excel Open XML Spreadsheet (XLSX) file.

Extract fields from a certificate file and return the standard context.

Returns the license ID.

Gets all IP addresses in context, excluding ones given.

Shows a bar chart of the number of incident the 'To' and 'From' email addresses.

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here:

• For Cortex XSOAR 6 see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.x/Cortex-XSOAR-Playbook-Design-Guide/Automations
• For Cortex XSOAR 8 Cloud see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Create-a-script
• For Cortex XSOAR 8.7 On-prem see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Create-a-script

Verify that the CIDRs are valid.

This script evaluates command-line threats by analyzing both original and decoded inputs. It assigns weighted scores to detected patterns, such as AMSI bypass or credential dumping, and applies risk combination bonuses for multiple detections. The total score is normalized to a 0-100 scale, with risk levels categorized as follows:

• 0-25: Low Risk
• 26-50: Medium Risk
• 51-90: High Risk
• 91-100: Critical Risk

The scoring mechanism provides a comprehensive risk assessment, considering both the severity and frequency of malicious behaviors.

Gets a list of indicators from the indicators argument, and generates a JSON file in STIX 2.1 format.

This dynamic automation parses the CVSS score of a CVE and presents it in the layout in color according to its score.

Returns 'yes' if integration brand is available. Otherwise returns 'no'.

This script is designed to analyze a PFX (Personal Information Exchange) file for various suspicious or noteworthy characteristics from a security perspective.

This automation uses the Core REST API Integration to batch export Incidents to CSV and return the resulting CSV file to the war room.

This automation uses the Core REST API Integration to batch export Alerts to CSV and return the resulting CSV file to the war room.

Converts a file from one format to a different format by using the convert-to function of Libre Office. For a list of supported input/output formats see: https://wiki.openoffice.org/wiki/Framework/Article/Filter/FilterList_OOo_3_0

Given a list of objects and a key found in each of those objects, return a unique list of values associated with that key. Returns error if the objects provided do not contain the key of interest.

Display the mapped fields in a dynamic-section.

Language detection based on Google's language-detection.

Deprecated. Use FileCreateAndUploadV2 instead. Will create a file (using the given data input or entry ID) and upload it to current investigation war room.

Expose the incident owner into IncidentOwner context key

Expose the alert owner into AlertOwner context key

Verify URL SSL certificate.

After running DeleteContext, this script can repopulate all the file entries in the ${File} context key

This command will allow you to run commands against a local Docker Container. You can run commands like wc for instance with word count, or other types of commands that you want on the docker container.

We recommend for tools that you want to use that are not part of the default Docker container, to cope this Automation script and then create a customer docker container with /docker_image_create with a custom docker container to add any command level tool to Demisto and output the results directly to the context.

Finds which integrations implement a specific Demisto command. The results will be returned as comma-separated values (CSV). The "Core REST API" integration must first be enabled.

Converts XML string to JSON format

Checks whether the PDF file is encrypted.

Parse an email from an eml or msg file and populate all relevant context data to investigate the email. Also extracts inner attachments and returns them to the war room. The incident labels themselves are preserved and not modified - only the "Label/x" context items that originated from the labels, and the best practice is to rely on these for the remainder of the playbook. This script is based on the parse-emails XSOAR python package, check the script documentation for more info.

Script will run the provided mathematical action on 2 provided values and produce a result.
The result can be stored on the context using the contextKey argument

Calculate the time difference, in minutes.

Check if a given value is true. Will return 'no' otherwise

Gets a value and return it. This is to be used in playbook conditional tasks - get a value from incident field, label or context, and act accordingly.
If an array is returned. the first value will be the decision making value.

Get a MITRE ATT&CK object name by its ID. The script is using TIMs IOCs to find the correct name. (MITRE ATT&CK IOCs must exist in the Threat Intel data).

DNS lookup utility to provide 'A' and 'PTR' record.

Verifies if the given input contains valid IP addresses (IPv4 or IPv6).

Count an array size

This script allows disabling a specified user using one or more of the following integrations: SailPointIdentityIQ, ActiveDirectoryQuery, Okta, MicrosoftGraphUser, and IAM.

Fill the current time in a custom incident field

This function generates a password and allows various parameters to customize the properties of the password depending on the use case (e.g. password complexity requirements). The default behavior is to generate a password of random length including all four character classes (upper, lower, digits, symbols) with at least five and at most ten characters per class.

The min_* values all default to 0. This means that if the command is executed in this way:
!GeneratePassword max_lcase=10
It is possible that a password of length zero could be generated. It is therefore recommended to always include a min_* parameter that matches.

The debug parameter will print certain properties of the command into the WarRoom for easy diagnostics.

This script adds the reputation to Onion URL indicators. The script is automatically triggered when a Onion URL indicator is auto-extracted. For instance, if you run a Cortex CLI on a valid Onion URL, the indicators are extracted automatically and this script is triggered for the extracted indicators.

Convert a JSON War Room output via EntryID to a CSV file.

This button will generate summary 'Case Report' template for a given Incident

This script accepts multiple values for both arguments and will iterate through each of the domains to check if the specified subdomains are located in at least one of the specified main domains. If the tested subdomain is in one of the main domains, the result will be true. For example, if the domain_to_check values are apps.paloaltonetworks.com and apps.paloaltonetworks.bla and the domains_to_compare values are paloaltonetworks.com and demisto.com, the result for apps.paloaltonetworks.com will be true since it is a part of the paloaltonetworks.com domain. The result for apps.paloaltonetworks.bla will be false since it is not a part of the paloaltonetworks.com or demisto.com domain.

Deprecated. Use ParseEmailFilesV2 instead." Parse an email from an eml or msg file and populate all relevant context data to investigate the email. Also extracts inner attachments and returns them to the war room. The incident labels themselves are preserved and not modified - only the "Label/x" context items that originated from the labels, and the best practice is to rely on these for the remainder of the playbook.

Sleep for X seconds.

When you apply this script to an incident field, that incident field is hidden for new incidents, and it displays in edit mode.

When you apply this script to an alert field, that alert field is hidden for new alerts, and it displays in edit mode.

Deprecated. Use the MatchRegexV2 script instead.

This is a wrapper to isolate or unisolate hash lists from Cortex XDR, MSDE or CrowdStrike (Available from Cortex).

The script calculates the average DBot score for each indicator in the context.

Prints a value to the parent incident's war-room of the current alert.

Prints a value to the specified incident's war-room.

Widget script to view information about the relationship between an indicator, entity and other indicators and connect to indicators, if relevant.

Retrieves the current date and time.

Extract URLs redirected by security tools like Proofpoint.
Changes https://urldefense.proofpoint.com/v2/url?u=https-3A__example.com_something.html -> https://example.com/something.html
Also, un-escape URLs that are escaped for safety with formats like hxxps://www[.]demisto[.]com

Analyze a list of Unix timestamps in milliseconds, to detect simple patterns of consistency or high frequency. The script can aid in the investigation of multi-event alerts that contain a list of timestamps.

Check if list exist in demisto lists.

This script searches for a value in a context path.

Extracts domains and FQDNs from URLs and emails.

Parse CEF data into the context. Please notice that outputs will display only the 7 mandatory fields even if the CEF event includes many other custom or extended fields.

The automation takes Excel file (entryID) as an input and parses its content to the war room and context.

Checks if the Docker container running this script has been hardened according to the recommended settings at:

• For Docker hardening guide (Cortex XSOAR 6.13) https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.13/Cortex-XSOAR-Administrator-Guide/Docker-Hardening-Guide
• For Docker hardening guide (Cortex XSOAR 8 Cloud) https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Docker-hardening-guide
• For Docker hardening guide (Cortex XSOAR 8.7 On-prem) https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Docker-hardening-guide.

Gets all email addresses in context, excluding ones given.

Used to extract indicators from Word files (DOC, DOCX).
The script does not extract data from macros (e.g., embedded code).

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here: - For Cortex XSOAR 6 see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.x/Cortex-XSOAR-Playbook-Design-Guide/Automations - For Cortex XSOAR 8 Cloud see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Create-a-script - For Cortex XSOAR 8.7 On-prem see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Create-a-script

Works the same as the 'Set' command, but can work across incidents by specifying 'id' as an argument.
Sets a value into the context with the given context key. Doesn't append by default.

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here:

• For Cortex XSOAR 6 see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.x/Cortex-XSOAR-Playbook-Design-Guide/Automations
• For Cortex XSOAR 8 Cloud see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Create-a-script
• For Cortex XSOAR 8.7 On-prem see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Create-a-script

Works the same as the 'Set' command, but can work across alerts by specifying 'id' as an argument.
Sets a value into the context with the given context key. Doesn't append by default.

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here:

• For Cortex XSOAR 6 see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.x/Cortex-XSOAR-Playbook-Design-Guide/Automations
• For Cortex XSOAR 8 Cloud see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Create-a-script
• For Cortex XSOAR 8.7 On-prem see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Create-a-script

Lookup incidents with specified indicator. Use currentIncidentId to omit the existing incident from output.

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here:

• For Cortex XSOAR 6 see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.x/Cortex-XSOAR-Playbook-Design-Guide/Automations
• For Cortex XSOAR 8 Cloud see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Create-a-script
• For Cortex XSOAR 8.7 On-prem see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Create-a-script

Lookup alerts with specified indicator. Use currentAlertId to omit the existing alert from output.

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here:

• For Cortex XSOAR 6 see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.x/Cortex-XSOAR-Playbook-Design-Guide/Automations
• For Cortex XSOAR 8 Cloud see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Create-a-script
• For Cortex XSOAR 8.7 On-prem see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Create-a-script

Get the Server URL.

Convert country name to country code or country code to country name.
Only one of 'country_code' or 'country_name' can be provided.
Example:
Input: { "country_code": "US" }
Output: { "United States" }
Another Example:
Input: { "country_name": "United States" }
Output: { "US" }.

Extracts hyperlinks from office files. Supported file types are: xlsx, docx, pptx.

Utility script to use in playbooks - returns "yes" if the input is non-empty.

Display HTML with embedded images.

A context script for Domain entities

Prints a value to the specified alert's war-room. The alert must be in status "Under Investigation".

Converts a date from a different timezone to UTC timezone.

Returns a map entry with a marker on the given coordinates (lat,lng), or address (requires a configured GoogleMaps instance).

Load a PDF file's content and metadata into context. Supports extraction of hashes, urls, and emails when available.

Pretty-print data using Python's pprint library. This is useful for seeing the structure of incident and context data. Here's how to use it:

!PrettyPrint value=${incident}

Strips, unquotes and unescapes URLs. If the URL is a Proofpoint or ATP URL, extracts its redirect URL. If more than one URL is passed to the formatter, the separator must be a pipe ("|").

Schedule a command to run inside the war room at a future time (once or reoccurring)

Add a remote system (such as a desktop under investigation) to an investigation (this will allow you to install and agent on the system)

Add a remote system (such as a desktop under investigation) to an investigation (this will allow you to install and agent on the system)

Deprecated. Use PCAPMinerV2 instead. PCAPMiner is a tool to parse PCAP files and will return things like extracted files that are found, HTTP flows, and a variety of other information. It is uses a docker instance located on docker hub trorabaugh/dempcap:1.0. To use simply upload a PCAP file and then run PCAPMiner entryId="<your_entry_id>". To get the entry id click on the link on the top right hand corner of a file attachment.

Takes the comments of a given entry ID and stores them in the incident context, under a provided context key.
For accessing the last executed task's comments, provide ${lastCompletedTaskEntries.[0]} as the value for the entryId input parameter.

Check if a given value exists in the context. Will return 'no' for empty empty arrays. To be used mostly with DQ and selectors.

Identify whether the incident includes an email message attached as an eml or msg file and return the answer to playbook. Also saves the identified entry ID to context for use for later. Commonly used in automated playbooks that handle phishing reports sent to a special phishing mailbox set up by the security team.

Automation used to more easily populate a grid field. This is necessary when you want to assign certain values as static or if you have context paths that you will assign to different values as well. Instead of a value you can enter TIMESTAMP to get the current timestamp in ISO format. For example:
!GridFieldSetup keys=ip,src,timestamp val1=${AWS.EC2.Instances.NetworkInterfaces.PrivateIpAddress} val2="AWS" val3="TIMESTAMP" gridfiled="gridfield".

Input Text Data to Encode as ASCII (Ignores any chars that aren't interpreted as ASCII)

Returns yes if the IP is in one of the ranges provided, returns no otherwise.

Decode MIME base64 headers.

Creates a Grid table from items or key-value pairs.

Removes a key in key/value store backed by an XSOAR list.

This widget displays the incident verdict or the alert verdict based on the 'incident.verdict' or 'alert.verdict' field.

This automation uses the Core REST API Integration to batch export Indicators to CSV and return the resulting CSV file to the war room.

Compare two lists and put the differences in context.

Converts HTML to Markdown.

Try to get the hostname correlated with the input IP.

Adds provided entries to the incident Evidence Board. In playbook, can be positioned after a task to add the previous task's entries to Evidence Board automatically (with no need to provide arguments)

Compares a single timestamp to a list of timestamps.

Read image files metadata and provide Exif tags.

This stops the scheduled task whose ID is given in the taskID argument.

Returns DNS details for a domain.

Close the current investigation as duplicate to other investigation.

Gets a value from the specified incident's context.

Gets a value from the specified alert's context.

Ask a user a question via email and process the reply directly into the investigation.

Prints an error entry with a given message.

This automation calculates the similarity ratio between every string in 2 different arrays and outputs a decimal value between 0.0 and 1.0 (1.0 if the sequences are identical, and 0.0 if they don't have anything in common).

This script updates an indicator's grid field in Cortex with provided row data. You can input the rows directly or extract them from the context.

Execute a command on a remote machine (without installing a D2 agent)

This script calculates the CVSS Base Score, Temporal Score, and Environmental Score using either the CVSS 3.0 or CVSS 3.1 calculator according to https://www.first.org/cvss/ calculation documentation.

Verify that the address is a valid IPv6 address.

Parses a YAML string into context.

Verifies if the supplied JSON string is valid and optionally verifies against a provided schema. The script utilizes Powershell's Test-JSON cmdlet.

Load the contents of a file into context.

Returns integration instances configured in Cortex. You can filter by instance status and/or brand name (vendor).

Shows a bar chart of the number of Positive Detections out of overall detections

A context script for Email entities.

Populates critical assets in a grid field that has the section headers "Asset Type" and "Asset Name".

Checks if the email address is part of the internal domains.

Get the overall score for the indicator as calculated by DBot.

A wrapper script to the 'AppendindicatorField' script that enables adding tags to certain indicators.
Note: You can use this script in an incident Layout button to allow tags to be added to indicators through the incident.

Filter context keys by applying one of the various available manipulations and storing in a new context key. Please notice that the resulting context key will not be available automatically as an option but you can still specify it.

Creates indicators from the submitted STIX file. Supports STIX 1.0 and STIX 2.x. This automation creates indicators and adds an indicator's relationships if available.

Deprecated. Use the UnzipFile script instead. UnPack a file using fileName or entryID to specify a file. Files unpacked will be pushed to the war room and names will be pushed to the context.
supported types are:
7z (.7z), ACE (.ace), ALZIP (.alz), AR (.a), ARC (.arc), ARJ (.arj), BZIP2 (.bz2), CAB (.cab), compress (.Z), CPIO (.cpio), DEB (.deb), DMS (.dms), GZIP (.gz), LRZIP (.lrz), LZH (.lha, .lzh), LZIP (.lz), LZMA (.lzma), LZOP (.lzo), RPM (.rpm), RAR (.rar), RZIP (.rz), TAR (.tar), XZ (.xz), ZIP (.zip, .jar) and ZOO (.zoo)

Get the error(s) associated with a given entry/entries. Use ${lastCompletedTaskEntries} to check the previous task entries. The automation will return an array of the error contents from those entries.

Optionally increases the incident severity to the new value if it is greater than the existing severity.

Optionally increases the alert severity to the new value if it is greater than the existing severity.

Remove escaping chars from IP
127[.]0[.]0[.]1 -> 127.0.0.1

Not in context verification is a script that executes the given command and verifies that the specified field is not in the context after execution.

Check if a given value is true. Will return 'no' otherwise

Set multiple keys/values to the context.

Incident action button script to link or unlink Incidents from an Incident

Alert action button script to link or unlink Alerts from an Alert

Generate report summaries for the passed incidents.

Parses a CSV and looks for a specific value in a specific column, returning a dict of the entire matching row. If no column value is specified, the entire CSV is read into the context.

Gets hashes (MD5,SHA1,SHA256) from context.

Searches for string in a path in context. If path is null, string will be searched in full context.

Collect entries matching to the conditions in the war room.

Check if indicators exist in the Threat Intel database.

List all Docker images that are in use by the installed integrations and automations.

Uses the Core REST API integration to query the server audit trail logs, and return back a CSV or JSON file.

Loads a json from string input, and returns a json object result.

Convert an array to a nice table display. Usually, from the context.

Called by the GenericPolling playbook, schedules the polling task.

Get the string distance for the sender from our domain

Deprecated. Use the "PhishingDedupPreprocessingRule" script instead.
Find duplicate incidents candidates.
Using machine learning techniques with pre-defined data (can also use data from the local environment), this script takes into consideration different features such as: labels comparison, email labels (relevant for phishing), incident time difference and shared indicators, which can be customized by the arguments.

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here:

• For Cortex XSOAR 6 see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.x/Cortex-XSOAR-Playbook-Design-Guide/Automations
• For Cortex XSOAR 8 Cloud see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Create-a-script
• For Cortex XSOAR 8.7 On-prem see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Create-a-script

Enables changing context in two ways. The first is to capitalize the first letter of each key in following level of the context key entered. The second is to change context keys to new values.

A context script for IP entities.

Generates random string

Script to convert a War Room output JSON File to a CSV file.

This script is only meant to be used to disable the Enrich Excluded button in an indicator. It should not be used otherwise.

The script downloads a Python library using PIP, archives it, and returns the file to the war room.

Create indicators to the Threat Intel database only if they are not registered. All submitted indicators will be associated with the parent incident. When using the script with many indicators, or when the Threat Intel Management database is highly populated, this script may have low performance issue.

This script displays the execution results of the tab's buttons in an HTML table format.

Prints text to war room (Markdown supported)

aquatone-discover will find the targets nameservers and shuffle DNS lookups between them. Should a lookup fail on the target domains nameservers, aquatone-discover will fall back to using Google public DNS servers to maximize discovery.

Returns a dict of all incident fields that exist in the system.

Returns a dict of all alert fields that exist in the system.

This is only an example script, to showcase how to use and write JavaScript scripts

Mark entries as notes if they are tagged with given tag.

Adds/Replaces a key in key/value store backed by an XSOAR list.

Display HTML in the War Room.

Sends http request. Returns the response as json.

Extracts FQDNs from URLs and emails.

This script is used to display the indicators of an incident in an incident field of type Array. It can be used to select indicators from the incident in order to later perform some actions, like tagging the indicators for blocking via EDL.
This script is a field-display script, so it needs to be configured as such, when editing the incident field that will be used to display the indicators.

This script is used to display the indicators of an alert in an alert field of type Array. It can be used to select indicators from the alert in order to later perform some actions, like tagging the indicators for blocking via EDL.
This script is a field-display script, so it needs to be configured as such, when editing the alert field that will be used to display the indicators.

Converts XML file entry to JSON format

Runs the polling command repeatedly, completes a blocking manual task when polling is done.

Pretty-print the contents of the playbook context.

This script checks that a field exists (and contains data), and optionally checks the value of the field for a match against an input value. If a regex is not supplied, the script checks that the field is not empty. This script can be used with the "GenericPolling" playbook to poll for field population or that a field contains a specific value.

This script pre-processes (resizes, sharpens, and grayscales) an image file from context, given an entry_id.

A context script for URL entities.

Takes UTC and converts it to the specified timezone. Format must match the UTC date's format and output will be the same format. Can use in conjunction with ConvertDateToString

Searches Cortex Incidents and returnrs the most relevant fields. Default search range is the last 30 days, if you want to change this, use the fromDate argument.

Returns the id, name, type, severity, status, owner, and created/closed times to context. You can add additional fields using the add_field_to_context argument.

This automation runs using the default Limited User role, unless you explicitly change the permissions. Based on the SearchIncidentsV2 from the Common Scripts pack, but more efficient.

Searches Cortex Alerts and returnrs the most relevant fields. Default search range is the last 30 days, if you want to change this, use the fromDate argument.

Returns the id, name, type, severity, status, owner, and created/closed times to context. You can add additional fields using the add_field_to_context argument.

This automation runs using the default Limited User role, unless you explicitly change the permissions. Based on the SearchAlertsV2 from the Common Scripts pack, but more efficient.

Gets docker image latest tag. Script simulates the docker pull flow but doesn't actually pull the image. Returns an entry with the docker image latest tag if all is good, otherwise will return an error.

Returns wether a PDF is both valid and encrypted.

List the redirects for a given URL

Extracts regex data from the provided text. The script support groups and looping.

Creates a file (using the given data input or entry ID) and uploads it to the current investigation War Room.

Will create an array object in context from given string input

Takes an input docx file (entryID) as an input and saves an output text file (file entry) with the original file's contents.

Joins values from two lists by index according to a given format.

Will encode an input using Base64 format.

Executes a test for all integration instances available and returns detailed information about succeeded and failed integration instances.

Sends a HTTP request with advanced capabilities.

Checks if the supplied hostnames match either the organization's internal naming convention or the domain suffix.

Allows to parse and extract http flows (requests & responses) from a pcap/pcapng file.

Assign analyst to incident.
Note: the script should be executed from within an alert.
By default, the analyst is picked randomly from the available users, according to the provided roles (if no roles provided, will fetch all users).
Otherwise, the analyst will be picked according to the 'assignBy' arguments.
machine-learning: DBot will calculated and decide who is the best analyst for the job.
top-user: The user that is most commonly owns this type of incident
less-busy-user: The less busy analyst will be picked to be the incident owner.
online: The analyst is picked randomly from all online analysts, according to the provided roles (if no roles provided, will fetch all users).
current: The user that executed the command.

Runs a specified polling command one time. This is useful for initiating a local playbook context before running a polling scheduled task.

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here:

• For Cortex XSOAR 6 see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.x/Cortex-XSOAR-Playbook-Design-Guide/Automations
• For Cortex XSOAR 8 Cloud see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Create-a-script
• For Cortex XSOAR 8.7 On-prem see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Create-a-script

Take a list of devices and pull a specific file (given by path) from each using SCP.

Dumps a json from context key input, and returns a json object string result

Generates the URL for a Data Collection Task into Context. Can be used to get the url for tasks send via Email, Slack, or even if you select "By Task Only".

To generate links for specific users, add an array of users in the users argument.

Parses a list by header and value.

Lists executed commands in War Room

This script allows sending an HTML email, using a template stored as a list item under Lists (Settings -> Advanced -> Lists).
Placeholders are marked in DT format (i.e. ${incident.id} for incident ID).
Available placeholders for example:

• ${incident.labels.Email/from}
• ${incident.name}
• ${object.value}
  See incident Context Data menu for available placeholders

Note: Sending emails require an active Mail Sender integration instance.

Check if an email address's domain is trying to squat other domain using Levenshtein distance algorithm.

Generates a random UUID (UUID 4).

Extract strings from a file with optional filter - similar to binutils strings command

Add DBot score to context for indicators with custom vendor, score, reliability, and type.

Encodes an input to Base64 format.

Set a value in context under the key you entered.

Unzip a file using fileName or entryID to specify a file. Unzipped files will be loaded to the War Room and names will be put into the context.

Copy all entries marked as notes from current incident to another incident.

Copy all entries marked as notes from current alert to another alert.

Set indicator reputation to "suspicious" when malicious ratio is above threshold.
Malicious ratio is the ration between number of "bad" incidents to total number of incidents the indicator appears in.

Map the given values to the translated values. If given values: a,b,c, and translated: 1,2,3, then the input will return 1.

Deprecated. No available replacement. Search for a binary on an endpoint using Carbon Black

Enrich and calculate the reputation of a certificate indicator.

Show indicator geo location on map.

Returns the length of the string passed as argument

Returns the incident field names associated to the specified incident type.

Returns the alert field names associated to the specified alert type.

Delete field from context.

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here:

• For Cortex XSOAR 6 see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.x/Cortex-XSOAR-Playbook-Design-Guide/Automations
• For Cortex XSOAR 8 Cloud see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Create-a-script
• For Cortex XSOAR 8.7 On-prem see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Create-a-script

Calculates the entropy for the given data.

Provides the severity of the CVE based on the CVSS score where available.

Extract user's response from EmailAskUser reply. Returns the first textual response line of the provided entry that contains the reply body. Use ${lastCompletedTaskEntries} to analyze the previous playbook task containing the user's reply.

Publish entries to incident's context

Extracts the text from a QR code. The output of this script includes the output of the script "extractIndicators" run on the text extracted from the QR code.

This script checks that a context key exists (and contains data), and optionally checks the value of the context key for a match against an input value. If a regex is not supplied, the script checks that the key is not empty. This script can be used with the "GenericPolling" playbook to poll for field population or that a field contains a specific value. This scripts does not support a context key which holds a list of values.

Deprecated. Use DBotFindSimilarIncidents instead.

Finds similar incidents by common incident keys, labels, custom fields or context keys.
It's highly recommended to use incident keys if possible (e.g., "type" for the same incident type).
For best performance, it's recommended to avoid using context keys if possible (for example, if the value also appears in a label key, use label).

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here:

• For Cortex XSOAR 6 see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.x/Cortex-XSOAR-Playbook-Design-Guide/Automations
• For Cortex XSOAR 8 Cloud see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Create-a-script
• For Cortex XSOAR 8.7 On-prem see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Create-a-script

Deprecated. Use DBotFindSimilarAlerts instead.

Finds similar alerts by common alert keys, labels, custom fields or context keys.
It's highly recommended to use alert keys if possible (e.g., "type" for the same alert type).
For best performance, it's recommended to avoid using context keys if possible (for example, if the value also appears in a label key, use label).

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here:

• For Cortex XSOAR 6 see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.x/Cortex-XSOAR-Playbook-Design-Guide/Automations
• For Cortex XSOAR 8 Cloud see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Create-a-script
• For Cortex XSOAR 8.7 On-prem see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Create-a-script

Return indicators appears in resolved incidents, and resolved incident ids.

This automation runs using the default Limited User role, unless you explicitly change the permissions.
For more information, see the section about permissions here:

• For Cortex XSOAR 6 see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.x/Cortex-XSOAR-Playbook-Design-Guide/Automations
• For Cortex XSOAR 8 Cloud see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Create-a-script
• For Cortex XSOAR 8.7 On-prem see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Create-a-script

Gather information regarding CIDR -
1. Broadcast_address
2. CIDR
3. First_address
4. Last address
5. Max prefix len
6. Num addresses
7. Private
8. Version.

Gets all currently enabled integration instances.

Checks if the supplied URLs are in the specified domains.

Calculate ssdeep reputation based on similar files (by ssdeep similarity) on the system.

Exports the Context for the current Incident to a JSON file in the war room.

Replaces regex match/es in string.
Returns the string after replace was preformed.

A script to generate investigation summary report in an automated way
Can be used in post-processing flow as well.

Check whether given entry/entries returned an error. Use ${lastCompletedTaskEntries} to check the previous task entries. If array is provided, will return yes if one of the entries returned an error.

Returns a string with all matches of a regex pattern groups replaced by a replacement.

Find tables inside HTML and extract the contents into objects using the following logic:

• If table has a single column, just create an array of strings from the values
• If table has 2 columns and has no header row, treat the first column as key and second as value and create a table of key/value
• If table has a header row, create a table of objects where attribute names are the headers
• If table does not have a header row, create table of objects where attribute names are cell1, cell2, cell3…

Get the string distance between inputString and compareString (compareString can be a comma-separated list) based on Levenshtein Distance algorithm.

Extract Attack Pattern Threat Intel Object. After auto extract extracts the Attack Pattern IDs, this script is executed and extracts the value (name) of the Attack Pattern.

Extract Domain(s) from URL(s) and/or Email(s).

Extract regular text from the given HTML.

"A data protection impact assessment (…) shall in particular be required in the case of: (a) a systematic and extensive evaluation of personal aspects relating to natural persons which is based on automated processing, including profiling, and on which decisions are based that produce legal effects concerning the natural person or similarly significantly affect the natural person; (b) processing on a large scale of special categories of data referred to in Article 9(1), or of personal data relating to criminal convictions and offences referred to in Article 10; or (c) a systematic monitoring of a publicly accessible area on a large scale. - GDPR Art. 35

Is account information breached

Is financial information breached

Is the DPO confirm the breach

"‘main establishment’ means: as regards a controller with establishments in more than one Member State, the place of its central administration in the Union, unless the decisions on the purposes and means of the processing of personal data are taken in another establishment of the controller in the Union and the latter establishment has the power to have such decisions implemented, in which case the establishment having taken such decisions is to be considered to be the main establishment; as regards a processor with establishments in more than one Member State, the place of its central administration in the Union, or, if the processor has no central administration in the Union, the establishment of the processor in the Union where the main processing activities in the context of the activities of an establishment of the processor take place to the extent that the processor is subject to specific obligations under this Regulation;" - GDPR Art. 4

Is Medical Information breached

The status of the media notification

Is unique biometric data breached

"‘personal data’ means any information relating to an identified or identifiable natural person (‘data subject’); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person;" - GDPR Art. 4

"In the case of a personal data breach, the controller shall without undue delay and, where feasible, not later than 72 hours after having become aware of it, notify the personal data breach to the supervisory authority competent in accordance with Article 55, unless the personal data breach is unlikely to result in a risk to the rights and freedoms of natural persons." - GDPR Art. 33

" (d) describe the measures taken or proposed to be taken by the controller to address the personal data breach, including, where appropriate, measures to mitigate its possible adverse effects." - GDPR Art. 33

Is health insurance breached

Is unique identification number breached

Is other PII data breached