Common Scripts

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.

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.

Enrich and calculate the reputation of a certificate indicator.

This script allows sending an HTML email, using a template stored as a list item under Lists:

• Cortex XSIAM: Settings -> Configurations -> Lists.
• Cortex XSOAR: Settings -> 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.

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

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

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

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

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

Retrieves the current date and time.

Fill the current time in a custom incident field.

Set a value in context under the key you entered.

Set multiple keys/values to the context.

The script is for use with GenericPolling, which checks the completion condition. It uses a DT to retrieve a value from the context data and evaluates it using another DT.

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

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

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.

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

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

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

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

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.

Indicates whether a given value is a member of given array

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

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.

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

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

Publish entries to incident's context

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.

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

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

Returns the license ID.

A context script for hash entities.

Expose the incident owner into IncidentOwner context key

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

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

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".

A context script for IP entities.

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.

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

Returns the length of the string passed as argument

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.

Checks whether the PDF file is encrypted.

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

Pretty-print the contents of the playbook context.

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

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…

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

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

Converts XML file entry to JSON format

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

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

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

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

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

Read image files metadata and provide Exif tags.

Gets all IP addresses in context, excluding ones given.

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.

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

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

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.

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

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

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.

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

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.

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

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

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

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

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.

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

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

Generates a random UUID (UUID 4).

Count an array size

Encodes an input to Base64 format.

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.

Will create an array object in context from given string input

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

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

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

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

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

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

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

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

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

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

Sends http request. Returns the response as json.

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

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

Will encode an input using Base64 format.

Compare two lists and put the differences in context.

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

Gets all email addresses in context, excluding ones given.

Close the current investigation as duplicate to other investigation.

Show all scheduled entries for specific incident.

Generates random string.

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

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

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

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.

Sleep for X seconds.

Gets all currently enabled integration instances.

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

Checks whether a port was open on given host.

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

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.

Prints an error entry with a given message.

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.

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

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

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.

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.

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 will parse a CSV file and place the unique IPs, Domains and Hashes into the context.

Zip a file and upload to war room.

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

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.

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.

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

Converts HTML to Markdown.

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.

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.

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.

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

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

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

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.

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.

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.

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.

Display HTML in the War Room.

Display the mapped fields in a dynamic-section.

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

Get the string distance for the sender from our domain.

Gets a value from the specified incident's context.

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

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

Checks if the supplied URLs are in the specified domains.

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.

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.

Verify that the CIDRs are valid.

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

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

Deprecated. Use the MatchRegexV2 script instead.

Calculate the time difference, in minutes.

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

Check if list exist in demisto lists.

Return the Demisto server version.

A wrapper script for the executeCommandAt command to be used in playbooks or the war-room.

This script searches for a value in a context path.

Loads a JSON file from the war room to 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).

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

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

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

Load the contents of a file into context.

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.

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

Verify URL SSL certificate.

Generate report summaries for the passed incidents.

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

Sends a HTTP request with advanced capabilities.

Sends email to incident owner when selected field is triggered.

Called by the GenericPolling playbook, schedules the polling task.

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

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

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.

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

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

Prints text to war room (Markdown supported)

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

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.

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

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}.

Collect entries matching to the conditions in the war room.

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

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

Try to get the hostname correlated with the input IP.

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

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).

Show indicator geo location on map.

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

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

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

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.

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

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.

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

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.

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

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.

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

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

Converts XML string to JSON format

Get the Server URL.

A context script for URL entities.

Lists executed commands in War Room

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.

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

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.

Parses a list by header and value.

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

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

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

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

Parses a YAML string into context.

Language detection based on Google's language-detection.

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

Check if indicators exist in the Threat Intel database.

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

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

Converts a date from a different timezone to UTC timezone.

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

A context script for Domain entities.

Calculates the entropy for the given data.

Sets a custom incident field with current date.

Converts a given array to an HTML table

Display HTML with embedded images.

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

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

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.

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

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 automation uses the Core REST API Integration to batch export Incidents to CSV and return the resulting CSV file to the war room.

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

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

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

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.

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

Converts a simple Array into a textual comma separated string.

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

Verify that the address is a valid IPv6 address.

Compares a single timestamp to a list of timestamps.

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.

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.

Returns wether a PDF is both valid and encrypted.

Decode MIME base64 headers.

Export given array to csv file.

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.

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

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

Fetches the numbers of ads in the given url.

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.

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.

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

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

Deprecated. Use DBotPreProcessTextData instead.

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.

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

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

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

Content packs installer from marketplace.

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

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

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

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

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

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" }.

A context script for Email entities.

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

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

Extract regular text from the given HTML.

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

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

Extracts FQDNs from URLs and emails.

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

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

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)

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

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

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.

Recursively un-escapes JSON data if escaped JSON is found.

List the redirects for a given URL.

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

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

Returns DNS details for a domain.

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.

Extracts domains and FQDNs from URLs and emails.

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

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.

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)

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 ("|").

Is financial information breached

"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 unique biometric data breached

The status of the media notification

Is Medical Information breached

"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

"‘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 health insurance breached

Is the DPO confirm the breach

"‘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

Is account information breached

Is other PII data breached

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

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

Converts XML file entry to JSON format

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

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.

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

Prints an error entry with a given message.

Gets a value from the specified incident's context.

Gets a value from the specified alert's 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.

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.

Display HTML with embedded images.

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.

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.

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)

Generates a random UUID (UUID 4).

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 dynamic automation parses the CVSS score of a CVE and presents it in the layout in color according to its score.

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

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.

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

Sends email to incident owner when selected field is triggered.

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

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

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

Prints text to war room (Markdown supported)

Calculate the time difference, in minutes.

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

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.

Extracts domains and FQDNs from URLs and emails.

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

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

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

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.

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

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

Compares a single timestamp to a list of timestamps.

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

Try to get the hostname correlated with the input IP.

Show indicator geo location on map.

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

Verify that the CIDRs are valid.

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.

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.

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

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

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

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

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

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.

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

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

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

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

Returns wether a PDF is both valid and encrypted.

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

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.

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

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

Count an array size

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

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

A context script for IP entities.

Returns the license ID.

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

Called by the GenericPolling playbook, schedules the polling task.

Converts XML string to JSON format

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

A context script for URL entities.

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

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

Checks whether a port was open on given host.

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

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

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

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

Check if list exist in demisto lists.

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.

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

Language detection based on Google's language-detection.

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

Deprecated. Use DBotPreProcessTextData instead.

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

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

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.

A context script for Email entities.

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

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

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

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

Gets all currently enabled integration instances.

Encodes an input to Base64 format.

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

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.

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

Decode MIME base64 headers.

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…

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

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

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".

Calculates the entropy for the given data.

A wrapper script for the executeCommandAt command to be used in playbooks or the war-room.

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

Get the string distance for the sender from our domain.

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

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.

Sets a custom incident field with current date.

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

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.

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

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.

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

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.

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

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.

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.

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.

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

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

Recursively un-escapes JSON data if escaped JSON is found.

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.

Verify that the address is a valid IPv6 address.

Converts HTML to Markdown.

Check if indicators exist in the Threat Intel database.

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

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).

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

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

Sleep for X seconds.

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

Lists executed commands in War Room

Parses a list by header and value.

Publish entries to incident's context

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.

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

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

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

A context script for hash entities.

Fetches the numbers of ads in the given url.

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

Checks whether the PDF file is encrypted.

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.

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.

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.

Verify URL SSL certificate.

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.

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

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

List the redirects for a given URL.

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

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

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 exists in the context. Will return 'no' for empty empty arrays. To be used mostly with DQ and selectors.

This script allows sending an HTML email, using a template stored as a list item under Lists:

• Cortex XSIAM: Settings -> Configurations -> Lists.
• Cortex: Settings -> 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.

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

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

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

Converts a given array to an HTML table

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

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

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

Converts a date from a different timezone to UTC timezone.

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.

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

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

Loads a JSON file from the war room to context.

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

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

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

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.

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.

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

Compare two lists and put the differences in context.

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}.

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

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.

Set a value in context under the key you entered.

Read image files metadata and provide Exif tags.

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

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

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

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)

Converts a simple Array into a textual comma separated string.

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

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.

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.

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

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

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.

Generates random string.

Expose the incident owner into IncidentOwner context key

Expose the alert owner into AlertOwner context key

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

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

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

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.

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

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.

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" }.

Checks if the supplied URLs are in the specified domains.

Enrich and calculate the reputation of a certificate indicator.

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

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

Extract regular text from the given HTML.

Fill the current time in a custom incident field.

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)

Sends http request. Returns the response as json.

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

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.

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.

Deprecated. Use the MatchRegexV2 script instead.

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 ("|").

Retrieves the current date and time.

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.

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

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

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.

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

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

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.

Returns DNS details for a domain.

Collect entries matching to the conditions in the war room.

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

Will encode an input using Base64 format.

Content packs installer from marketplace.

Close the current investigation as duplicate to other investigation.

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

Sends a HTTP request with advanced capabilities.

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.

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.

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.

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

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

Display the mapped fields in a dynamic-section.

Extracts FQDNs from URLs and emails.

Show all scheduled entries for specific incident.

Parses a YAML string into context.

The script is for use with GenericPolling, which checks the completion condition. It uses a DT to retrieve a value from the context data and evaluates it using another DT.

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.

Zip a file and upload to war room.

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

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

Will create an array object in context from given string input

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

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

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

Get the Server URL.

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

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.

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

Returns the length of the string passed as argument

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

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

A context script for Domain entities.

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

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

Gets all IP addresses in context, excluding ones given.

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.

Gets all email addresses in context, excluding ones given.

Display HTML in the War Room.

Set multiple keys/values to the context.

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

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

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

Export given array to csv file.

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

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.

Load the contents of a file into context.

Indicates whether a given value is a member of given array

Pretty-print the contents of the playbook context.

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

This script searches for a value in a context path.

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.

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

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.

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.

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

Is account information breached

Is other PII data breached

Is the DPO confirm the breach

" (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

"‘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

"‘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

Is financial information breached

"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 unique identification number breached

"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

The status of the media notification

Is unique biometric data breached

Is health insurance breached