Skip to main content

Reference Docs

Find reference documentation for Integrations, Automations, Playbooks and more.

Integrations#

NameDescription
1Touch.io's Inventa ConnectorUse the Inventa integration to generate DSAR reports within Inventa instance and retrieve DSAR data for the XSOAR.
Abnormal SecurityAbnormal Security detects the whole spectrum of email attacks, from vendor email compromise and spear-phishing to unwanted email spam and graymail. To stop these advanced attacks, Abnormal leverages the industry’s most advanced behavioral data science to baseline known good behavior and detects anomalies.
Abnormal Security Event CollectorAbnormal Security Event Collector integration for XSIAM.
AbsoluteAbsolute is an adaptive endpoint security solution that delivers device security, data security, and asset management of endpoints.
abuse.ch SSL Blacklist FeedThe SSL IP Blacklist contains all hosts (IP addresses) that SSLBL has seen in the past 30 days and identified as being associated with a malicious SSL certificate.
AbuseIPDBCentral repository to report and identify IP addresses that have been associated with malicious activity online. Check the Detailed Information section for more information on how to configure the integration.
Acalvio ShadowPlexAcalvio ShadowPlex is a comprehensive Autonomous Deception Platform that offers Advanced Threat Detection, Investigation and Response capabilities.
Accenture CTI (Deprecated)Deprecated. Use Accenture CTI v2 instead.
Accessdata (Deprecated)Deprecated. Use Exterro FTK instead.
ACTI Feed (Deprecated)Deprecated. Use Accenture CTI Feed instead.
ACTI Indicator FeedFetches indicators from a ACTI feed. You can filter returned indicators by indicator type, indicator severity, threat type, confidence, and malware family (each of these are an integration parameter).
ACTI Indicator QueryACTI provides intelligence regarding security threats and vulnerabilities.
ACTI Vulnerability QueryACTI provides intelligence regarding security threats and vulnerabilities.
Active Directory AuthenticationAuthenticate using Active Directory.
Active Directory Query v2The Active Directory Query integration enables you to access and manage Active Directory objects (users, contacts, and computers).
ActiveMQIntegration with ActiveMQ queue.
Aella Star LightAella Star Light Integration
Agari Phishing DefenseAgari Phishing Defense stops phishing, BEC, and other identity deception attacks that trick employees into harming your business.
AhaUse the Aha! integration to list and manage Cortex XSOAR features from Aha.
Akamai WAFUse the Akamai WAF integration to manage common sets of lists used by various Akamai security products and features.

This is the modified version where a new command "akamai-update-network-list-elements" was added by the SA.
Akamai WAF SIEMUse the Akamai WAF SIEM integration to retrieve security events from Akamai Web Application Firewall (WAF) service.
Alexa Rank Indicator (Deprecated)Deprecated. Vendor has declared end of life for this product. No available replacement.
Alexa Rank Indicator v2 (Deprecated)Deprecated. Vendor has declared end of life for this product. No available replacement.
AlgoSecAlgosec BusinessFlow(ABF), Firewall Analyzer (AFA) and FireFlow(AFF).
Alibaba Action Trail Event CollectorAlibaba logs event collector integration for XSIAM.
AlienVault OTX TAXII FeedThis integration fetches indicators from AlienVault OTX using a TAXII client.
AlienVault OTX v2Query Indicators of Compromise in AlienVault OTX.
AlienVault Reputation FeedUse the AlienVault Reputation feed integration to fetch indicators from the feed.
AlienVault USM AnywhereSearches for and monitors alarms and events from AlienVault USM Anywhere.
AlphaSOC Network Behavior AnalyticsRetrieve alerts from the AlphaSOC Analytics Engine
AlphaSOC WisdomDNS and IP threat intelligence via the AlphaSOC platform
AlphaVantageThis is an API to get stock prices etc
Amazon DynamoDBAmazon DynamoDB Amazon DynamoDB is a fully managed NoSQL database service that provides fast and predictable performance with seamless scalability. DynamoDB lets you offload the administrative burdens of operating and scaling a distributed database, so that you don't have to worry about hardware provisioning, setup and configuration, replication, software patching, or cluster scaling. With DynamoDB, you can create database tables that can store and retrieve any amount of data, and serve any level of request traffic. You can scale up or scale down your tables' throughput capacity without downtime or performance degradation, and use the AWS Management Console to monitor resource utilization and performance metrics. DynamoDB automatically spreads the data and traffic for your tables over a sufficient number of servers to handle your throughput and storage requirements, while maintaining consistent and fast performance. All of your data is stored on solid state disks (SSDs) and automatically replicated across multiple Availability Zones in an AWS region, providing built-in high availability and data durability.
Amazon Security LakeAmazon Security Lake is a fully managed security data lake service.
AMPUses CISCO AMP Endpoint
Analyst1This integration utilizes Analyst1's system to enrich Demisto indicators with data provided by the Analyst1 REST API, such as actor and malware information, activity and reported dates, evidence and hit counts, and more.
Anomali MatchUse Anomali Match to search indicators and enrich domains.
Anomali ThreatStream (Deprecated)Deprecated. Use Anomali ThreatStream v3 instead. Use Anomali ThreatStream to query and submit threats
Anomali ThreatStream v2 (Deprecated)Deprecated. Use Anomali ThreatStream v3 integration instead.
Anomali ThreatStream v3Use Anomali ThreatStream to query and submit threats.
Ansible ACMEControl Automatic Certificate Management Environment on Linux hosts
Ansible Alibaba CloudManage Alibaba Cloud Elastic Compute Instances
Ansible Automation PlatformScale IT automation, manage complex deployments, and speed productivity.
Ansible AzureManage Azure resources
Ansible Cisco IOSCisco IOS Platform management over SSH
Ansible Cisco NXOSCisco NX-OS Platform management over SSH
Ansible DNSManage DNS records using NSUpdate
Ansible HCloudManage your Hetzner Cloud environment
Ansible KubernetesManage Kubernetes
Ansible Microsoft WindowsAgentless Windows host management over WinRM
Ansible OpenSSLControl OpenSSL on a remote Linux hosts
Ansible VMwareManage VMware vSphere Server, Guests, and ESXi Hosts
ANY.RUNANY.RUN is a cloud-based sanbox with interactive access.
APIVoidAPIVoid wraps up a number of services such as ipvoid & urlvoid
appNoviSearch across meshed network, security, and business data in appNovi to make efficient informed security decisions for risk management and incident response. Gain immediate intelligence on assets, visualize risk and threats across your network, and undertake interactive investigations across the network to reduce MTTR for incident response.
Arcanna.AIArcanna integration for using the power of AI in SOC
ArcSight ESM v2ArcSight ESM SIEM by Micro Focus (Formerly HPE Software).
ArcSight LoggerArcSight events logger
ArcusTeamThe ArcusTeam API allows the user to inspect connected devices' attack surface. By feeding device identifiers and the software it runs: DeviceTotal will return a map of the device’s attack surface. DeviceTotal was built from the ground up in order to provide complete visibility into connected devices and mitigate 3rd party risk. DeviceTotal can continuously identify & predict such that the connected device security posture is being assessed, prioritized and mitigated effectively.
ArduinoConnects to and controls an Arduino pin system using the network.
ARIA Packet IntelligenceThe ARIA Cybesecurity Solutions Software-Defined Security (SDS) platform integrates with Cortex XSOAR to add robustness when responding to incidents. The combination of ARIA hardware, in the form of a Secure Intelligent Adapter (SIA), and software, specifically Packet Intelligence and SDS orchestrator (SDSo), provides the elements required to react instantly when an incident is detected. When integrated with the ARIA solution, you can create playbooks that instruct one or more SIAs to add, modify, or delete rules automatically. These rule changes, which take effect immediately, can block conversations, redirect packets to a recorder or VLAN, or perform a variety of other actions.
ArkimeArkime (formerly Moloch) is a large scale, open source, indexed packet capture and search tool.
ArmisUse the Armis integration to search alerts and devices, tag and untag devices, and set alert statuses.
Armis Event CollectorCollects alerts, devices and activities from Armis resources.
ArmorbloxArmorblox is an API-based platform that stops targeted email attacks,
protects sensitive data, and automates incident response.
Ataya HarmonyUse the Ataya Harmony integration to assign client which has not yet under assigned status by client imsi.
Atlassian Confluence CloudAtlassian Confluence Cloud allows users to interact with confluence entities like content, space, users, and groups. Users can also manage the space permissions.
Atlassian Confluence ServerAtlassian Confluence Server API.
Atlassian IAMIntegrate with Atlassian's services to execute CRUD operations for employee lifecycle processes.
Atlassian Jira v2 (Deprecated)Deprecated. Use the Atlassian Jira v3 integration instead
Atlassian Jira v3Use the Jira integration to manage issues, create Cortex XSOAR incidents from Jira projects, and mirror issues to existing issue incidents in Cortex XSOAR. The integration now supports both OnPrem, and Cloud instances.
AttackIQ PlatformAn attack simulation platform that provides validations for security controls, responses, and remediation exercises.
Attivo BotsinkNetwork-based Threat Deception for Post-Compromise Threat Detection.
AutoFocus Daily Feed (Deprecated)Deprecated. No available replacement.
AutoFocus FeedUse the AutoFocus Feeds integration to fetch indicators from AutoFocus.
AutoFocus Tags Feed (Deprecated)Deprecated. Use Unit 42 Intel Objects Feed instead. Use the AutoFocus Tags Feed integration to fetch indicators from AutoFocus Tags.
AutomoxAdministrate your IT organization from XSOAR with comprehensive commands for the Automox platform.
Awake SecurityNetwork Traffic Analysis.
AWS - AccessAnalyzerAmazon Web Services IAM Access Analyzer.
AWS - ACMAmazon Web Services Certificate Manager Service (ACM).
AWS - AthenaAmazon Web Services Athena.
AWS - CloudTrailAmazon Web Services CloudTrail.
AWS - CloudWatchLogsAmazon Web Services CloudWatch Logs (logs).
AWS - EC2Amazon Web Services Elastic Compute Cloud (EC2).
AWS - GuardDutyAmazon Web Services Guard Duty Service (gd).
AWS - GuardDuty Event CollectorAmazon Web Services Guard Duty Service (gd) event collector integration for Cortex XSIAM.
AWS - IAM (user lifecycle management)Integrate with AWS's services to execute CRUD and Group operations for employee lifecycle processes.
AWS - IAM Identity CenterAmazon Web Services IAM Identity Center.
AWS - Identity and Access ManagementAmazon Web Services Identity and Access Management (IAM).
AWS - LambdaAmazon Web Services Serverless Compute service (lambda).
AWS - OrganizationsManage Amazon Web Services accounts and their resources.
AWS - Route53Amazon Web Services Managed Cloud DNS Service.
AWS - S3Amazon Web Services Simple Storage Service (S3).
AWS - Security HubAmazon Web Services Security Hub Service.
AWS - SNSAmazon Web Services Simple Notification Service (SNS).
AWS - SQSAmazon Web Services Simple Queuing Service (SQS).
AWS - System ManagerAWS Systems Manager is the operations hub for your AWS applications and resources and a secure end-to-end management solution for hybrid cloud environments that enables safe and secure operations at scale.
AWS FeedUse the AWS feed integration to fetch indicators from the feed.
AWS Network FirewallAWS Network Firewall is a stateful, managed, network firewall and intrusion detection and prevention service for Amazon Virtual Private Cloud (Amazon VPC). With Network Firewall, you can filter traffic at the perimeter of your VPC. This includes filtering traffic going to and coming from an internet gateway, NAT gateway, or over VPN or AWS Direct Connect. Network Firewall uses rules that are compatible with Suricata, a free, open source intrusion detection system (IDS) engine.
AWS SagemakerAWS Sagemaker - Demisto Phishing Email Classifier.
Aws Secrets ManagerAWS Secrets Manager helps you to securely encrypt, store, and retrieve credentials for your databases and other services.
AWS Security Hub Event CollectorAn XSIAM event collector integration for AWS Security Hub.
AWS Simple Notification Service (AWS SNS)Use AWS SNS to send notifications to XSOAR.
AWS-EKSThe AWS EKS integration allows for the management and operation of Amazon Elastic Kubernetes Service (EKS) clusters.
AWS-SNS-ListenerAmazon Simple Notification Service (SNS) is a managed service that provides message delivery from publishers to subscribers.
AWS-WAFAmazon Web Services Web Application Firewall (WAF).
AxoniusThis integration is for fetching information about assets in Axonius.
Azure Active Directory ApplicationsUse the Azure Active Directory Applications integration to manage authorized applications.
Azure Active Directory GroupsMicrosoft Graph Groups enables you to create and manage different types of groups and group functionality according to your requirements.
Azure Active Directory Identity And AccessUse the Azure Active Directory Identity And Access integration to manage roles and members.
Azure Active Directory Identity Protection (Deprecated)Deprecated. Use Microsoft Graph Identity and Access instead.
Azure Active Directory UsersUnified gateway to security insights - all from a unified Microsoft Graph User API.
Azure AD Connect Health FeedUse the Microsoft Azure AD Connect Health Feed integration to get indicators from the feed.
Azure Compute v2Create and Manage Azure Virtual Machines.
Azure Data ExplorerUse the Azure Data Explorer integration to collect and analyze data inside Azure Data Explorer clusters, and to manage search queries.
Azure FeedAzure.CloudIPs Feed Integration.
Azure FirewallAzure Firewall is a cloud-native and intelligent network firewall security service that provides breed threat protection for cloud workloads running in Azure. It's a fully stateful, firewall as a service, with built-in high availability and unrestricted cloud scalability.
Azure Key VaultUse the Azure Key Vault integration to safeguard and manage cryptographic keys and secrets used by cloud applications and services.
Azure Kubernetes ServicesDeploy and manage containerized applications with a fully managed Kubernetes service.
Azure Log AnalyticsLog Analytics is a service that helps you collect and analyze data generated by resources in your cloud and on-premises environments.
Azure Network Security GroupsAzure network security groups are used to filter network traffic to and from Azure resources in an Azure virtual network.
Azure Risky UsersAzure Risky Users provides access to all at-risk users and risk detections in the Azure AD environment.
Azure SQL ManagementMicrosoft Azure SQL Management Integration manages the Auditing and Threat Policies for Azure SQL.
Azure Storage ContainerCreate and Manage Azure Storage Container services.
Azure Storage FileShareCreate and Manage Azure FileShare Files and Directories.
Azure Storage ManagementDeploy and manage storage accounts and blob services.
Azure Storage QueueCreate and Manage Azure Storage Queues and Messages.
Azure Storage TableCreate and Manage Azure Storage Tables and Entities.
Azure Web Application FirewallThe Azure WAF (Web Application Firewall) integration provides centralized protection of your web applications from common exploits and vulnerabilities.
It enables you to control policies that are configured in the Azure Firewall management platform, and allows you to add, delete, or update policies,
and also to get details of a specific policy or a list of policies.
AzureDevOpsManage Git repositories in Azure DevOps Services. Integration capabilities include retrieving, creating, and updating pull requests. Run pipelines and retrieve Git information.
Bambenek Consulting FeedUse the Bambenek Consulting feed integration to fetch indicators from the feed.
Barracuda Reputation Block List (BRBL)This integration enables reputation checks against IPs from Barracuda Reputation Block List (BRBL)
Bastille NetworksRF monitoring for wireless intrusion detection and policy enforcement. Visit https://www.bastille.net for details.
BeyondTrust Password SafeUnified password and session management for seamless accountability and control over privileged accounts.
BigFixHCL BigFix Patch provides an automated, simplified patching process that is administered from a single console.
Binalyze AIRCollect your forensics data under 10 minutes.
BitbucketBitbucket Cloud is a Git-based code and CI/CD tool optimized for teams using Jira.
BitcoinAbuse Feed (Deprecated)Deprecated. No available replacement.
BitDamBitDam secure email gateway protects from advanced content-borne threats with the most accurate prevention of known and unknown threats, at their source.
Bitsight for Security Performance ManagementUse the "Bitsight for Security Performance Management" Integration to get company guid, details, and findings. This integration also allows to fetch the findings by using the fetch incidents capability.
Blocklist_de FeedUse the Blocklist.de feed integration to fetch indicators from the feed.
Bluecat Address ManagerUse the BlueCat Address Manager integration to enrich IP addresses and manage response policies.
Blueliv ThreatCompassBlueliv ThreatCompass systematically looks for information about companies,products, people, brands, logos, assets, technology and other information, depending on your needs. Blueliv ThreatCompass allows you to monitor and track all this information to keep your data, your
organization and its employees safe.
Blueliv ThreatContextThe Threat Context module provides SOC, Incident Response, and Threat Intelligence teams with continuously updated and intuitive information around threat actors, campaigns, malware indicators, attack patterns, tools, signatures and CVEs.
BMC DiscoveryBMC Discovery is a SaaS-based, cloud-native discovery and dependency modeling system that provides instant visibility into hardware, software, and service dependencies across multi-cloud, hybrid, and on-premises environments.
BMC Helix ITSMBMC Helix ITSM integration enables customers to manage service request, incident, change request, task, problem investigation, known error and work order tickets.
BMC Helix RemedyforceBMC Helix Remedyforce integration enables customers to create/update service requests and incidents, update statuses, and resolve service requests and incidents with customer notes. This integration exposes standard ticketing capabilities that can be utilized as part of automation & orchestration.
BMC Remedy ARBMC Remedy AR System is a professional development environment that leverages the recommendations of the IT Infrastructure Library (ITIL) and provides a foundation for Business Service Management (BSM) solutions. For incident management (i.e. create, fetch, update), please refer to Remedy On-Demand integration.
BonuslyThe Bonusly integration is used to interact with the Bonusly platform through the API. Bonusly is an employee recognition platform which enterprises use to for employee recognition.
Box (Deprecated)Deprecated. Use the Box v2 integration instead.
Box Event CollectorCollect events from Box's logs.
Box v2Manage Box users.
BreachRxAutomate your privacy Incident Response workflow through the BreachRx platform.
BruteForceBlocker FeedBruteForceBlocker is a Perl script that works with pf – firewall developed by the OpenBSD team, and is also available on FreeBSD from version 5.2. From BruteForceBlocker version 1.2 it is also possible to report blocked IP addresses to the project site and share your information with other users.
C2sec iriskUnderstand Your Cyber Exposure as Easy as a Google Search
Cado ResponseAutomate data collection. Process data at cloud speed. Analyze with purpose.
CamlyticsYou can use this integration to automate different Camlytics surveillance analysis actions.
Carbon Black Endpoint Standard Event CollectorEndpoint Standard (formerly called Carbon Black Defense), a Next-Generation Anti-Virus + EDR. Collect Anti-Virus & EDR alerts and Audit Log Events.
Carbon Black Endpoint Standard v2Endpoint Standard is an industry-leading next-generation antivirus (NGAV) and behavioral endpoint detection and response (EDR) solution. Endpoint Standard is delivered through the Carbon Black Cloud, an endpoint protection platform that consolidates security in the cloud using a single agent, console and data set.
Carbon Black Enterprise EDRVMware Carbon Black Enterprise EDR (formerly known as Carbon Black ThreatHunter) is an advanced threat hunting and incident response solution delivering continuous visibility for top security operations centers (SOCs) and incident response (IR) teams. (formerly known as ThreatHunter).
Carbon Black Live Response CloudVMware Carbon Black Endpoint Standard Live Response is a feature that enables security operators to collect information and take action on remote endpoints in real time. These actions include the ability to upload, download, and remove files, retrieve and remove registry entries, dump contents of physical memory, and execute and terminate processes.
Censys v2Censys is a search engine that allows computer scientists to ask questions about the devices and networks that compose the internet. Driven by internet-wide scanning, Censys lets researchers find specific hosts and create aggregate reports on how devices, and certificates are configured and deployed.
CentreonIT & Network Monitoring.
Centrify VaultLeverage the Centrify Vault integration to create and manage Secrets.
Check Point Dome9 (CloudGuard)Dome9 integration allows to easily manage the security and compliance of the public cloud.
Check Point Firewall (Deprecated)Deprecated. Use the Check Point Firewall v2 integration instead. Manage Check Point firewall via API
Check Point Harmony Email and Collaboration (HEC)The Best Way to Protect Enterprise Email & Collaboration from phishing, malware, account takeover, data loss, etc.
Check Point Network Detection and Response (Infinity NDR)Collect network security events from Check Point Infinity NDR for your secured SaaS periodically.
Check Point Threat Emulation (SandBlast)Uploads files using polling. The service supports Microsoft Office files, as well as PDF, SWF, archives, and executables. Active content will be cleaned from any documents that you upload (Microsoft Office and PDF files only). Queries on existing IOCs, file status, analysis, and reports. Downloads files from the database. Supports both appliance and cloud. Supported Threat Emulation versions are any R80x.
CheckPhishCheck any URL to detect supsicious behavior.
CheckPoint Firewall v2Use this integration to read information and send commands to the Check Point Firewall server.
CherwellCloud-based IT service management solution
ChronicleUse the Chronicle integration to retrieve Asset alerts or IOC Domain matches as Incidents. Use it to fetch a list of infected assets based on the indicator accessed. This integration also provides reputation and threat enrichment of indicators observed in the enterprise.
CimTrak - System Integrity AssuranceThe CimTrak integration helps you detect unexpected system/device/config modifications and automatically respond/react to threats.
CIRCLCIRCL Passive DNS is a database storing historical DNS records from various resources.
CIRCL Passive SSL is a database storing historical X.509 certificates seen per IP address. The Passive SSL historical data is indexed per IP address.
CIRCL CVE SearchSearches for CVE information using circl.lu.
CircleCIGets the details of the CircleCI workflows; including the details of the last runs and the jobs, and retrieves the artifacts of the jobs.
CIRCLEHashlookupCIRCL hash lookup is a public API to lookup hash values against known database of files. NSRL RDS database is included and many others are also included. The API is accessible via HTTP ReST API and the API is also described as an OpenAPI. The service is free and served as a best-effort basis.
Cisco AMP (Deprecated)Deprecated. Use Cisco AMP v2 instead.
Cisco AMP Event CollectorThis is the Cisco AMP event collector integration for Cortex XSIAM.
Cisco AMP v2Cisco Advanced Malware Protection software is designed to prevent, detect, and help remove threats in an efficient manner from computer systems. Threats can take the form of software viruses and other malware such as ransomware, worms, Trojans, spyware, adware, and fileless malware.
Cisco ASAUse the Cisco Adaptive Security Appliance Software integration to manage interfaces, rules, and network objects.
Cisco Email Security Appliance (IronPort) (Deprecated)Deprecated. Use Cisco Email Security Appliance (IronPort) V2 instead.
Cisco ESAThe Cisco Email Security Appliance is an email security gateway product. It is designed to detect and block a wide variety of email-born threats, such as malware, spam and phishing attempts.
Cisco FirepowerUse the Cisco Firepower integration for unified management of firewalls, application control, intrusion prevention, URL filtering, and advanced malware protection.
Cisco ISENext-generation secure network access.
Cisco MerakiCloud controlled WiFi, routing, and security.
Cisco Secure Cloud Analytics (Stealthwatch Cloud)Protect your cloud assets and private network
Cisco Secure Malware Analytics (Threat Grid) v2Query and upload samples to Cisco threat grid.
Cisco Secure Malware Analytics FeedSecure Malware Analytics (formerly Threat Grid) combines advanced sandboxing with threat intelligence into one unified solution to protect organizations from malware.
Cisco Secure Network Analytics (Stealthwatch)Scalable visibility and security analytics.
Cisco Security Management ApplianceThe Security Management Appliance (SMA) is used to centralize services from Email Security Appliances (ESAs) and Web Security Appliances (WSAs).
Cisco Threat Grid (Deprecated)Deprecated. Use Cisco Secure Malware Analytics (Threat Grid) v2 instead.
Cisco Umbrella Cloud Security (Deprecated)Deprecated. Use Cisco Umbrella Cloud Security v2 instead.
Cisco Umbrella Cloud Security v2Cisco Umbrella is a cloud security platform providing the first line of defense against internet threats. It uses DNS-layer security to block malicious requests before a connection is established, offering protection against malware, ransomware, phishing, and more. It offers real-time reporting, integrates with other Cisco solutions for layered security, and uses machine learning to uncover and predict threats.
Cisco Umbrella EnforcementAdd and remove domains in Cisco OpenDNS.
Cisco Umbrella InvestigateCisco Umbrella Investigate.
Cisco Umbrella ReportingThe Umbrella Reporting v2 API provides visibility into your core network and security activities and Umbrella logs.
Cisco Webex Event CollectorCisco Webex Event Collector fetches Events and Admin Audit Events and Security Audit Events.
Cisco Webex FeedUse the Cisco Webex Feed integration to fetch indicators from Webex.
Cisco Webex TeamsSend messages, create rooms and more, via the Cisco Spark API.
Cisco WSA v2Cisco Secure Web Appliance protects your organization by automatically blocking risky sites and testing unknown sites before allowing users to click on them.
CiscoEmailSecurity (Beta) (Deprecated)Deprecated. Use Cisco Security Management Appliance instead.
CiscoWSA (Deprecated)Deprecated. Use CiscoWSAV2 instead.
Clarizen IAMIAM integration for Clarizen. Handles user account auto-provisioning to Clarizen.
ClarotyUse the Claroty CTD integration to manage assets and alerts.
ClickSendThis is the ClickSend integration for make a phonecall from XSOAR made by Trustnet
CloakenUnshorten URLs onsite using the power of a Tor proxy server to prevent leaking IP addresses to adversaries.
CloudConvertUse the CloudConvert integration to convert your files to the desired format.
Cloudflare FeedUse the Cloudflare feed integration to fetch indicators from the feed.
Cloudflare WAFCloudflare WAF integration allows customers to manage firewall rules, filters, and IP-lists. It also allows to retrieve zones list for each account.
CloudShare (Beta)Cloudshare integration.
CloudSharkUse the CloudShark integration to upload, share, and collaborate on network packet capture files using your on-premises CS Enterprise system.
Code42Use the Code42 integration to identify potential data exfiltration from insider threats while speeding investigation and response by providing fast access to file events and metadata across physical and cloud environments.
Code42 Event CollectorCode42 Insider Risk software solutions provide the right balance of transparency, technology and training to detect and appropriately respond to data risk. Use the Code42EventCollector integration to fetch file events and audit logs.
Cofense FeedUse the Cofense Feed Integration to fetch indicators from the feed.
Cofense Intelligence (Deprecated)Deprecated. Use Cofense Intelligence v2 instead. Use the Cofense Intelligence integration to check the reputation of URLs, IP addresses, file hashes, and email addresses.
Cofense Intelligence v2Use the Cofense Intelligence integration to check the reputation of domains, URLs, IP addresses, file hashes, and email addresses.
Cofense Triage (Deprecated)Deprecated. Use the Cofense Triage v2 integration instead.
Cofense Triage v2Use the Cofense Triage integration to ingest reported phishing indicators.
Cofense Triage v3The integration uses the Cofense Triage v2 API that allows users to ingest phishing reports as incident alerts and execute commands such as threat indicators, reporters, categorize reports, and more.
Cofense VisionThe Cofense Vision integration provides commands to initiate advanced search jobs to hunt suspicious emails matching IOCs. It also contains commands to quarantine emails, download messages and their attachments, and aids to manage IOCs in the local repository to keep up with upcoming emerging threats.
CognniAutonomous detection and investigation of information security incidents and other potential threats.
Cohesity Helios Event CollectorThis is the Cohesity Helios Event Collector integration for XSIAM.
CohesityHeliosIntegrate with Cohesity Helios services to fetch alerts and take remedial action.
Commvault Security IQCommvault Security IQ provides pre-built integrations, automation workflows, and playbooks to streamline operations, enhance threat intelligence integration, and gain actionable insights through advanced reporting and analytics.
ConcentricAIConcentric’s Semantic Intelligence™ solution discovers and protects business critical, unstructured data. We use deep learning to identify risky sharing, inappropriate third party access, assets in the wrong location, mis-classified documents, or lateral movement of data – all without rules or complex upfront configuration.
ConflueraThis is the confluera Iq-Hub integration with cortex.
CoralogixFetch incidents, search for supporting data and tag interesting datapoints in/from your Coralogix account
Core LockLocking mechanism that prevents concurrent execution of different tasks
Core REST APIUse Core REST APIs.
Cortex Attack Surface ManagementIntegration to pull assets and other ASM related information.
Cortex XDR - IOCUse the Cortex XDR - IOCs feed integration to sync indicators from Cortex XSOAR to Cortex XDR and back to Cortex XSOAR. Cortex XDR is the world's first detection and response app that natively integrates network, endpoint and cloud data to stop sophisticated attacks.
Cortex XDR - IR CTFCortex XDR is the world's first detection and response app that natively integrates network, endpoint, and cloud data to stop sophisticated attacks.
Cortex XDR - XQL Query EngineCortex XDR - XQL Query Engine enables you to run XQL queries on your data sources.
Cortex XpanseIntegration to pull assets and other ASM related information.
Cortex Xpanse LegacyThe Xpanse integration for Cortex XSOAR leverages the Expander API to create incidents from Xpanse issues. It also leverages Xpanse's unparalleled view of the Internet to enrich IPs, domains and certificates using information from assets discovered by Xpanse Expander and risky flows detected by Xpanse Behavior.
CounterCraft Deception DirectorCounterCraft Deception Solution detects advanced adversaries. Automate counterintelligence campaigns to discover targeted attacks with real-time active response.
CounterTackCounterTack empowers endpoint security teams to assure endpoint protection for Identifying Cyber Threats. Integrating a predictive endpoint protection platform
Covalence For Security ProvidersTriggers by any alert from endpoint, cloud, and network security monitoring, with mitigation steps where applicable. Query Covalence for more detail.
Covalence Managed SecurityTriggers by triaged alerts from endpoint, cloud, and network security monitoring. Contains event details and easy-to-follow mitigation steps.
Create Test IncidentsCreateIncidents fetches custom incidents that are created manually.
CrowdSecIdentify Malicious IP addresses with the CrowdSec CTI API.
CrowdStrike FalconThe CrowdStrike Falcon OAuth 2 API (formerly the Falcon Firehose API), enables fetching and resolving detections, searching devices, getting behaviors by ID, containing hosts, and lifting host containment.
CrowdStrike Falcon Intel (Deprecated)Deprecated. Use CrowdStrike Falcon Intel v2 integration instead.
CrowdStrike Falcon Intel Feed ActorsThe CrowdStrike intelligence team tracks the activities of threat actor groups and advanced persistent threats (APTs) to understand as much as possible about their known aliases, targets, methods, and more. This integration retrieves indicators from the CrowdStrike Falcon Intel Feed.
CrowdStrike Falcon Intel v2CrowdStrike Threat intelligence service integration helps organizations defend themselves against adversary activity by investigating incidents, and accelerating alert triage and response.
CrowdStrike Falcon Intelligence SandboxUse the CrowdStrike Falcon Intelligence Sandbox integration to submit files, file hashes, URLs, and FTPs for sandbox analysis, and to retrieve reports.
CrowdStrike Falcon Sandbox (Deprecated)Deprecated. Use CrowdStrike Falcon Sandbox V2 instead.
CrowdStrike Falcon Sandbox v2 (Hybrid-Analysis)Fully automated malware analysis using Hybrid Analysis API.
CrowdStrike Falcon Streaming v2Use the CrowdStrike Falcon Stream v2 integration to stream detections and audit security events.
CrowdStrike Indicator FeedRetrieves indicators from the CrowdStrike Falcon Intel Feed.
CrowdStrike MalqueryUse the MalQuery Integration to query the contents of clean and malicious binary files, which forms part of Falcon's search engine.
CrowdStrike OpenAPI (Beta)Use the CrowdStrike OpenAPI integration to interact with CrowdStrike APIs that do not have dedicated integrations in Cortex XSOAR, for example, CrowdStrike FalconX, etc.
CryptocurrencyCryptocurrency will help classify Cryptocurrency indicators with the configured score when ingested.
CryptosimCRYPTOSIM gets correlations and correlation's alerts. Integration fetchs alerts to incident according to instance.
CSV FeedFetch indicators from a CSV feed.
CTIX v3This is Cyware Threat Intelligence eXhange(CTIX) integration which enriches IP/Domain/URL/File Data.
CTM360 CyberBlindspotTake action on incidents derived from CTM360 CBS threat intelligence that is directly linked to your organization.
Cuckoo SandboxMalware dynamic analysis sandboxing
CustomIndicatorDemoThis is a demo integration that demonstrates the usage of the CustomIndicator helper class.
CVE Search v2 (Deprecated)Deprecated. Use CIRCL CVE Search instead.
CybelAngel Event CollectorCybelAngel Event Collector collects reports from the CybelAngel platform, which specializes in external attack surface protection and management.
Cyber TriageAllows you to conduct a mini-forensic investigation on an endpoint. It pushes a collection tool to the remote endpoint, collects volatile and file system data, and analyzes the data.
CyberArk AIM (Deprecated)Deprecated. Use the CyberArk AIM v2 integration instead.
CyberArk AIM v2The CyberArk Application Identity Manager (AIM) provides a secure safe in which to store your account credentials. Use this integration to retrieve the account credentials in CyberArk AIM.
CyberArk EPM Event CollectorCyberArk EPM Event Collector fetches events.
CyberArk Identity Event CollectorThis integration collects events from the Idaptive Next-Gen Access (INGA) using REST APIs.
CyberArk PASUse the CyberArk Privileged Access Security (PAS) solution to manage users, safes, vaults, and accounts from Cortex XSOAR.
CyberChefCyberChef is a web-application developed by GCHQ that's been called the “Cyber Swiss Army Knife”.
CybereasonEndpoint detection and response to manage and query malops, connections and processes.
CyberintCyberint provides intelligence-driven digital risk protection. This integration will help your enterprise effectively consume actionable cyber alerts to increase your security posture.
CyberpionThe Cyberpion integration allows you to seamlessly receive all your Cyberpion security solution Action Items and supportive information to your Cortex XSOAR.
Cybersixgill Actionable AlertsCybersixgill automatically collects intelligence in real-time on all items that appear in the underground sources which we monitor. By using various rules and machine learning models, Cybersixgill automatically correlates these intelligence items with pre defined organization assets, and automatically alerts users in real time of any relevant intelligence items.
Cybersixgill DVE EnrichmentBy enriching CVEs with the DVE Score, Cortex XSOAR customers gain deeper visibility with relevant threat intel from the deep and dark web with dynamic attributes such as where they are trending, POC exploit details, and more. Loaded with extra-context, this allows users to accurately understand the real impact of CVEs to effectively prioritize critical vulnerabilities.
Cybersixgill DVE Feed Threat Intelligence (Deprecated)Deprecated. Use Cybersixgill DVE Feed Threat Intelligence v2 from the Cybersixgill-DVE pack instead.
Cybersixgill DVE Feed Threat Intelligence v2The Cybersixgill Dynamic Vulnerability Exploit (DVE) Score is based on the most comprehensive collection of vulnerability-related threat intelligence and is the only solution that provides users total context and predicts the immediate risks of a vulnerability based on threat actors’ intent. Cortex XSOAR users can track threats stemming from CVEs that most others define as irrelevant and have a higher probability of being exploited via their Cortex XSOAR dashboard.
CyberTotalCyberTotal is a cloud-based threat intelligence service developed by CyCraft.
Cyble EventsCyble Events for Vision Users. Must have Vision API access to use the threat intelligence.
Cyble Threat IntelCyble Threat Intelligence for Vision Users. Must have access to Cyble TAXII Feed to access the threat intelligence.
CybleEvents v2Cyble Events for Vision Users. Must have Vision API access to use the threat intelligence.
CyCognitoThe CyCognito integration fetches issues discovered by the CyCognito platform, thereby providing users with a view of their organization's internet-exposed attack surface. These issues include identification, prioritization, and recommendations for remediation of the risks faced by the organization. The integration contains commands to query assets and issues detected by the CyCognito platform, and includes a rich dashboard and layout with issue management capability.
CyCognito FeedThe CyCognito Feed integration retrieves the discovered assets from the CyCognito platform based on user-specified filters. A comprehensive dashboard and layout are also included.
Cyjax FeedThe feed allows customers to pull indicators of compromise from cyber incidents (IP addresses, URLs, domains, CVE and file hashes).
Cylance Protect v2Manage Endpoints using Cylance protect.
CymptomCymptom is a Breach and Attack Simulation solution that revolutionizes the existing approach by transforming attack simulation into a data analysis question. Cymptom agentless scanning brings real-time always-on visibility into the entire security posture.
CymulateMulti-Vector Cyber Attack, Breach and Attack Simulation
Cymulate v2Multi-Vector Cyber Attack, Breach and Attack Simulation.
Cyren Inbox SecurityCyren Inbox Security is an innovative solution that safeguards Office 365 mailboxes in your organization against evasive phishing, business email compromise (BEC), and fraud. This integration imports incidents from Cyren Inbox Security into XSOAR, and includes a playbook for incident resolution.
Cyren Threat InDepth Threat Intelligence FeedThreat InDepth's actionable and contextualized intelligence helps enterprises improve their threat detection and response by providing unprecedented visibility into new email-borne security threats faster than other security vendors.
Cyware Threat Intelligence eXchangeThis is Cyware Threat Intelligence eXhange(CTIX) integration which enriches IP/Domain/URL/File Data.
Darktrace (Deprecated)Deprecated. Use DarktraceMBs, DarktraceAIA, DarktraceAdmin instead.
Darktrace AdminThis pack includes configurations to combine the world-class threat detection of Darktrace with the synchrony and automation abilities of XSOAR, allowing security teams to manage device actions including device statuses and tags. Your understanding of potential threats can also be levelled-up with Advanced Search logs from DPI.
Darktrace AI AnalystRapid detection of malicious behaviour can make all the difference in the response to a security event. This pack includes configurations to combine the world-class threat detection of Darktrace with the synchrony and automation abilities of XSOAR, allowing security teams to investigate critical incidents along with accompanying summaries and timelines. AI actions can also be applied.
Darktrace Event CollectorUse this integration to fetch model breaches from Darktrace as events in XSIAM.
Darktrace Model BreachesRapid detection of malicious behaviour can make all the difference in the response to a security event. This pack includes configurations to combine the world-class threat detection of Darktrace with the synchrony and automation abilities of XSOAR, allowing security teams to investigate model breaches and all model breach related actions (such as commenting, acknowledging and model logic info).
Datadog Cloud SIEMDatadog is an observability service for cloud-scale applications, providing monitoring of servers, databases, tools, and services, through a SaaS-based data analytics platform.

The SaaS platform integrates and automates infrastructure monitoring, application performance monitoring and log management to provide unified, real-time observability of our customers' entire technology stack.
Dataminr PulseDataminr Pulse's AI-powered, real-time intelligence integrates into Cortex XSOAR workflows for faster detection and response.
DB2Integration to provide connectivity to IBM DB2 using the python ibm_db2 library.
DeCYFIRDeCYFIR API's provides External Threat Landscape Management insights.
DeCYFIR Indicators & Threat Intelligence FeedDeCYFIR API's provides External Threat Landscape Management insights.
Deep InstinctThe Deep Learning cybersecurity platform, for zero time prevention.
DeepInstinct v3Deep Instinct is a prevention-first approach to stopping ransomware and other malware using the world's first purpose-built, deep learning cybersecurity framework.
DeepLThis integration uses DeepL (https://www.deepl.com/) to translate text or files
DeHashedThis integration allows you to check if your personal information such as your email, username, or password is being compromised.
DelineaDSVManage credentials for applications, databases, CI/CD tools, and services without causing friction in the development process.
DelineaSSSecret Server is the only fully featured Privileged Account Management (PAM) solution available both on premise and in the cloud. It empowers security and IT ops teams to secure and manage all types of privileged accounts and offers the fastest time to value of any PAM solution.
Dell SecureworksProvides access to the Secureworks CTP ticketing system
Demisto LockLocking mechanism that prevents concurrent execution of different tasks.
Demisto REST API (Deprecated)Deprecated. Use Core REST API instead.
Devo (Deprecated)Deprecated. Use the Devo v2 integration instead.
Devo v2Use the Devo v2 integration to query Devo for alerts, lookup tables, with support of pagination, and to write to lookup tables.
DHS FeedThe Cybersecurity and Infrastructure Security Agency’s (CISA’s) free Automated Indicator Sharing (AIS) capability enables the exchange of cyber threat indicators, at machine speed, to the Federal Government community.
DHS Feed v2The Cybersecurity and Infrastructure Security Agency’s (CISA’s) free Automated Indicator Sharing (AIS) capability enables the exchange of cyber threat indicators, at machine speed, to the Federal Government community.
Digital Defense FrontlineVMUse the Digital Defense FrontlineVM to identify and evaluate the security and business risks of network devices and applications deployed as premise, cloud, or hybrid network-based implementations.
Digital GuardianUse Digital Guardian Integration to fetch incidents and to programmatically add or remove entries from watchlists and component lists.
Digital Guardian ARC Event CollectorDigital Guardian ARC event collector.
Digital ShadowsDigital Shadows monitors and manages an organization's digital risk across the widest range of data sources within the open, deep, and dark web.
DiscordThis is the Discord integration for sending Messages from XSOAR to Discord server made by Trustnet
DNSOverHttpsQuery dns names over https from Cloudflare or Google
dnstwistUse the DNSTwist integration to detect typosquatting, phishing, and corporate espionage.
Docker Engine APIThe Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API.
DomainToolsDomain name, DNS and Internet OSINT-based cyber threat intelligence and cybercrime forensics products and data
DomainTools IrisTogether, DomainTools and Cortex XSOAR automate and orchestrate the incident response process with essential domain profile, web crawl, SSL and infrastructure data. SOCs can create custom, automated workflows to trigger Indicator of Compromise (IoC) investigations, block threats based on connected infrastructure, and identify potentially malicious domains before weaponization. The DomainTools App for Cortex XSOAR is shipped with pre-built playbooks to enable automated enrichment, decision logic, ad-hoc investigations, and the ability to persist enriched intelligence.
DomainTools Iris DetectDomainTools is an essential component in the security stack of mature enterprises and performance-driven security teams.
Dragos WorldviewCustom integration designed to pull in reports from the Dragos Worldview API as incidents.
DriftDrift integration to fetch, modify, create and delete contacts within the Drift Plattform's Contact API.
Dropbox Event CollectorCollect events from Dropbox's logs.
Druva Ransomware ResponseDruva Ransomware Response Integration provides ransomware protection for endpoints, SaaS applications and data center workloads for Druva Ransomware Recovery customers.
DShield FeedThis integration fetches a list that summarizes the top 20 attacking class C (/24) subnets over the last three days from Dshield.
DuoDUO authentication service.
DUO AdminDUO for admins.
Must have access to the admin api in order to use this.
Duo Event CollectorCollects Auth and Audit events for Duo using the API.
EasyVistaEasyVista Service Manager manages the entire process of designing, managing and delivering IT services.
EclecticIQ Intelligence Center v3Threat Intelligence Platform that connects and interprets intelligence data from open sources, commercial suppliers and industry partnerships .
EclecticIQ Platform (Deprecated)Deprecated. No available replacement.
EclecticIQ Platform v2 (Deprecated)Deprecated. Use EclecticIQ Intelligence Center v3 instead.
EdgescanCloud-based continuous vulnerability management and penetration testing solution.
EDL MonitorThis integration can monitor EDLs by emailing the content of an EDL as a zipped file to a specified user at an interval (when run with a job), and/or simply monitor the EDL for availability and email the user if the EDL is not available in other playbooks
Elasticsearch FeedFetches indicators stored in an Elasticsearch database.
Elasticsearch v2Search for and analyze data in real time.
Supports version 6 and later.
Email HippoThis is the Email Hippo integration used to verify email sources as fake emails that were used as part of phishing attacks.
EmailRep.ioProvides email address reputation and reports.
EndaceThe EndaceProbe Analytics Platform provides 100% accurate, continuous packet capture on network links up to 100Gbps, with unparalleled depth of storage and retrieval performance. Coupled with the Endace InvestigationManager, this provides a central search and data-mining capability across a fabric of EndaceProbes deployed in a network.

This integration uses Endace APIs to search, archive and download PCAP file from either a single EndaceProbe or many via the InvestigationManager and enables integration of full historical packet capture into security automation workflows.
Envoy IAMIntegrate with Envoy Identity Access Management services to execute CRUD operations to employee lifecycle processes.
EWS Extension Online Powershell v2 (Deprecated)Deprecated. Use EWS Extension Online Powershell v3 instead.
EWS Extension Online Powershell v3Use the EWS Extension Online Powershell v3 integration to get information about mailboxes and users in your organization. This integration can also retrieve and modify Tenant Allow/Block Lists.
EWS Mail Sender (Deprecated)Exchange Web Services mail sender. Note: this integration supports Office 365 basic authentication only. If you are using Office 365, we recommend using the EWS O365 Integration instead, which supports modern authentication (oauth2). Deprecated. Use EWS v2 instead
EWS O365The new EWS O365 integration uses OAuth 2.0 protocol and can be used with Exchange Online and Office 365 (mail).
EWS v2Exchange Web Services and Office 365 (mail).
ExabeamThe Exabeam Security Management Platform provides end-to-end detection, User Event Behavioral Analytics, and SOAR.
Exabeam Data LakeExabeam Data Lake provides a searchable log management system. Data Lake is used for log collection, storage, processing, and presentation.
Exabeam Security Operations PlatformExabeam Security Operations Platform offers a centralized and scalable platform for log management.
ExceedLMS IAMIntegrate with Exceed LMS Identity Access Management services to execute CRUD operations to employee lifecycle processes.
Exchange 2016 Compliance Search (Deprecated)Deprecated. Use EWS V2 instead.
Exodus Intelligence VulnerabilitiesExodus Intelligence
Expanse (Deprecated)Deprecated. Use the Expanse v2 integration instead. The Expanse App for Demisto leverages the Expander API to retrieve network exposures and risky flows to create incidents in Demisto. This application also allows for IP, Domain, Certificate, Behavior, and Exposure enrichment, retrieving assets and exposures information drawn from Expanse’s unparalleled view of the Internet.
Expanse Expander FeedUse this feed to retrieve the discovered IPs/Domains/Certificates from Expanse Expander asset database.
Export Indicators Service (Deprecated)Deprecated. Use the Generic Export Indicators Service integration instead. Use the Export Indicators Service integration to provide an endpoint with a list of indicators as a service for the system indicators.
Exterro FTKUse the Exterro FTK integration to protect against and provide additional visibility into phishing and other malicious email attacks.
ExtraHop Reveal(x)ExtraHop Reveal(x) for Cortex XSOAR is a network detection and response solution that provides complete visibility of network communications at enterprise scale, real-time threat detections backed by machine learning, and guided investigation workflows that simplify response.
F5 Application Security Manager (WAF)Manages F5 firewall
F5 firewallManages F5 firewall rules
F5 LTMManages F5 LTM
F5 SilverlineF5 Silverline Threat Intelligence is a cloud-based service incorporating external IP reputation and reducing threat-based communications. By identifying IP addresses and security categories associated with malicious activity, this managed service integrates dynamic lists of threatening IP addresses with the Silverline cloud-based platform, adding context-based security to policy decisions.
FalconHost (Deprecated)Deprecated. Use the CrowdStrike Falcon integration instead.
Farsight DNSDBQuery Farsight DNSDB service
Farsight DNSDB v2Farsight Security DNSDB
DNSDB is a Passive DNS (pDNS) historical database that provides a unique, fact-based, multifaceted view of the configuration of the global Internet infrastructure DNSDB leverages the richness of Farsight’s Security Information Exchange (SIE) data-sharing platform and is engineered and operated by leading DNS experts.
Fastly FeedUse Fastly Feed to get assigned CIDRs and add them to your firewall's allowlist in order to enable using Fastly's services.
Feedly FeedIngest articles with indicators, entities and relationships from Feedly into XSOAR.
Feodo Tracker IP Blocklist FeedGets a list of bad IPs from Feodo Tracker.
Fidelis EDRUse the Fidelis Endpoint integration for advanced endpoint detection and response (EDR) across Windows, Mac and Linux OSes for faster threat remediation.
Fidelis Elevate NetworkAutomate Detection and Response to Network Threats and data leakage in your organization with Fidelis Elevate Network Integration.
FileOrbisManage FileOrbis operations.
FireEye (AX Series)Perform malware dynamic analysis
FireEye Central ManagementFireEye Central Management (CM Series) is the FireEye threat intelligence hub. It services the FireEye ecosystem, ensuring that FireEye products share the latest intelligence and correlate across attack vectors to detect and prevent cyber attacks.
FireEye Detection on DemandFireEye Detection On Demand is a threat detection service delivered as an API for integration into the SOC workflow, SIEM analytics, data repositories, or web applications, etc. It delivers flexible file and content analysis to identify malicious behavior wherever the enterprise needs it.
FireEye Email SecurityFireEye Email Security (EX) series protects against breaches caused by advanced email attacks.
FireEye Endpoint Security (HX) v2FireEye Endpoint Security is an integrated solution that detects and protects endpoints against known and unknown threats. This integration provides access to information about endpoints, acquisitions, alerts, indicators, and containment. You can extract critical data and effectively operate the security operations automated playbook.
FireEye ETPFireEye Email Threat Prevention (ETP Cloud) is a cloud-based platform that protects against advanced email attacks.
FireEye ETP Event CollectorUse this integration to fetch email security incidents from FireEye ETP as XSIAM events.
FireEye FeedFireEye Intelligence Feed Integration.
FireEye HelixFireEye Helix is a security operations platform. FireEye Helix integrates security tools and augments them with next-generation SIEM, orchestration and threat intelligence tools such as alert management, search, analysis, investigations and reporting.
FireEye HX (Deprecated)Deprecated. Use FireEyeHX v2 instead.
FireEye HX Event CollectorPalo Alto Networks FireEye HX Event Collector integration for XSIAM.
FireEye iSIGHTFireEye cyber threat intelligence.
FireEye NXFireEye Network Security is an effective cyber threat protection solution that helps organizations minimize the risk of costly breaches by accurately detecting and immediately stopping advanced, targeted, and other evasive attacks hiding in internet traffic.
FireMon Security ManagerFireMon Security Manager delivers comprehensive rule lifecycle management to help you manage and automate every stage of the change management process. Workflows can be customized and automated to conform to your security goals and standards, with tools at your disposal to evolve policy and protection over time.
FlashpointUse the Flashpoint integration to reduce business risk. Flashpoint allows users to ingest alerts and compromised credentials as incident alerts and executes commands such as search intelligence report, ip, url, get events, and more.
Flashpoint FeedFlashpoint Feed Integration allows importing indicators of compromise that occur in the context of an event on the Flashpoint platform which contains finished intelligence reports data, data from illicit forums, marketplaces, chat services, blogs, paste sites, technical data, card shops, and vulnerabilities. The indicators of compromise are ingested as indicators on the Cortex XSOAR and displayed in the War Room using a command.
Forcepoint DLP (Beta) Event CollectorUse this integration to fetch security incidents from Forcepoint DLP as Cortex XSIAM events.
Forcepoint Security Management CenterForcepoint SMC provides unified, centralized management of all models of Forcepoint engines whether physical, virtual or cloud—across large, geographically distributed enterprise environments.
Forcepoint Web SecurityAdvanced threat protection with added local management controls.
Forescout CounterACTUnified device visibility and control platform for IT and OT Security.
Forescout EyeInspectDelivers flexible and scalable OT/ICS asset visibility.
Fortanix DSMManage Secrets and Protect Confidential Data using Fortanix Data Security Manager
FortiAuthenticatorThis integration allows you to manage the user configuration on FortiAuthenticator.
FortiGateFortiGate provides flawless convergence that can scale to any location: remote office, branch, campus, data center, and cloud. FortiGate always delivered on the concept of hybrid mesh firewalls with FortiManager for unified management and consistent security across complex hybrid environments. The Fortinet FortiOS operating system provides deep visibility and security across a variety of form factors.
FortiMailFortiMail is a comprehensive email security solution by Fortinet, offering advanced threat protection, data loss prevention, encryption, and email authentication to safeguard organizations against email-based cyber threats and protect sensitive information.
FortiManagerFortiManager is a single console central management system that manages Fortinet devices.
FortiSandbox (Deprecated)FortiSandbox integration is used to submit files to FortiSandbox for malware analysis and retrieving the report of the analysis. It can also provide file rating based on hashes for already scanned files. Deprecated. Use FortiSandboxv2 instead.
FortiSandbox v2FortiSandbox is an advanced security tool that goes beyond standard sandboxing. It combines proactive mitigation, enhanced threat detection, and in-depth reporting, using Fortinet's dynamic antivirus technology, dual-level sandboxing, and FortiGuard cloud integration to counter advanced threats. It effectively detects viruses, Advanced Persistent Threats (APTs), and malicious URLs, integrating seamlessly with existing Fortinet devices like FortiGate and FortiMail for comprehensive network protection.
FortiSIEMSearch and update events of FortiSIEM and manage resource lists.
FortiSIEM v2Use FortiSIEM v2 to fetch and update incidents, search events and manage watchlists of FortiSIEM.
Fortiweb VMFortiweb VM integration allows to manage WAF policies and block cookies, URLs, and host names.
FraudWatchManage incidents via the Fraudwatch API. FraudWatch International provides a fully managed Enterprise Digital Brand Protection Suite, including online brand management & monitoring, as well as providing other brand protection solutions that protect organizations and their customers around the world against online brand-related abuse.
FreshdeskThe Freshdesk integration allows you to create, update, and delete tickets; reply to and create notes for tickets as well as view Groups, Agents and Contacts.
Freshworks FreshserviceFreshservice is a service management solution that allows customers to manage service requests, incidents, change requests tasks, and problem investigation.
FullHuntCortex XSOAR integration with FullHunt.io API
G Suite AuditorG Suite Auditor is an integration that receives Audit logs from G Suite's different applications - admin, drive, calender, and more.
G Suite Security Alert CenterG Suite Security Alert Center allows users to fetch different alert types such as Suspicious login, Device compromised, Leaked password, and more. Users can delete or recover a single alert or a batch of alerts and retrieve the alert's metadata. This integration allows users to provide feedback for alerts and fetch existing feedback for a particular alert.
GammaQuery and update violations in Gamma.
GCenterThis integration allows, via about twenty commands, to interact with the GCenter appliance via its API.
GCP Whitelist Feed (Deprecated)Deprecated. Use the Google IP Ranges Feed integration instead.
GCP-IAMManage identity and access control for Google Cloud Platform resources.
GemUse Gem alerts as a trigger for Cortex XSOAR’s custom playbooks, to automate response to specific TTPs.
Generic Export Indicators ServiceUse the Generic Export Indicators Service integration to provide an endpoint with a list of indicators as a service for the system indicators.
Generic SQLUse the Generic SQL integration to run SQL queries on the following databases: MySQL, PostgreSQL, Microsoft SQL Server, and Oracle.
Generic WebhookThe Generic Webhook integration is used to create incidents on event triggers. The trigger can be any query posted to the integration.
Genetec Security Center Event CollectorGenetec Security Center Audit Trail Event Collector.
GeniansUse the Genian NAC integration to block IP addresses using the assign tag.
Gigamon ThreatINSIGHTGigamon ThreatINSIGHT is a cloud-native network detection and response solution built for the rapid detection of threat activity, investigation of suspicious behavior, proactive hunting for potential risks, and directing a fast and effective response to active threats.
GiphyDisplay random GIF in the War Room (e.g. !giphy hello). Powered By Giphy.
GitGuardian Event CollectorThis is the GitGuardian event collector integration for Cortex XSIAM.
GitHubIntegration to GitHub API.
Github Event CollectorGithub logs event collector integration for Cortex XSIAM.
GitHub IAMIntegrate with GitHub services to perform Identity Lifecycle Management operations.
Github Maltrail FeedFetches Indicators from Github Repo https://github.com/stamparm/maltrail
GitLab (Deprecated)Deprecated. Use GitLab v2 in GitLab Pack instead.
GitLab Event Collector
GitLab v2Integration to GitLab API.
GLIMPS DetectUse the GLIMPS Detect Integration to send files to GLIMPS Malware and get results from it
GLPIGLPI open source ITSM solution.
GmailGmail API and user management (This integration replaces the Gmail functionality in the GoogleApps API and G Suite integration).
Gmail Single UserGmail API using OAuth 2.0.
Google BigQueryIntegration for Google BigQuery, a data warehouse for querying and analyzing large databases. In all commands, for any argument not specified, the BigQuery default value for that argument will be applied.
Google CalendarGoogle Calendar is a time-management and scheduling calendar service developed by Google. This integration helps you to perform various tasks on the access control list (ACL).
Google Chat via WebhookIntegration for sending notifications to a Google Chat space via Incoming Webhook.
Google Cloud ComputeGoogle Compute Engine delivers virtual machines running in Google's innovative data centers and worldwide fiber network. Compute Engine's tooling and workflow support enable scaling from single instances to global, load-balanced cloud computing.
Google Cloud FunctionsGoogle Cloud Functions is an event-driven serverless compute platform that enables you to run your code locally or in the cloud without having to provision servers.
Google Cloud LoggingWith Google Cloud Logging, users can centralize all their logs in a single location, making it easier to troubleshoot issues and gain insights from their data.
Google Cloud Pub/SubGoogle Cloud Pub/Sub is a fully-managed real-time messaging service that enables you to send and receive messages between independent applications.
Google Cloud SCCSecurity Command Center is a security and risk management platform for Google Cloud. Security Command Center enables you to understand your security and data attack surface by providing asset inventory and discovery, identifying vulnerabilities and threats, and helping you mitigate and remediate risks across an organization. This integration helps you to perform tasks related to findings and assets.
Google Cloud StorageGoogle Cloud Storage is a RESTful online file storage web service for storing and accessing data on Google Cloud Platform infrastructure.
Google Cloud TranslateA Google API cloud based translation service.
Google DocsUse the Google Docs integration to create and modify Google Docs documents.
Google DorkingAutomate the process of google dorking searches in order to detect leaked data.
Google DriveGoogle Drive allows users to store files on their servers, synchronize files across devices, and share files. This integration helps you to create a new drive, query past activity, and view change logs performed by the users.
Google IP Ranges FeedUse the Google IP Ranges integration to get GCP and Google global IP ranges.
Google Key Management ServiceUse the Google Key Management Service API for CryptoKey management and encrypt/decrypt functionality.
Google Kubernetes EngineThe Google Kubernetes Engine integration is used for building and managing container based
applications in Google Cloud Platform (GCP), powered by the open source Kubernetes technology.
Google MapsUse the Google Maps API.
Google Resource ManagerGoogle Cloud Platform Resource Manager
Google Safe Browsing (Deprecated)Deprecated. Use Google Safe Browsing v2 instead.
Google Safe Browsing v2Search Safe Browsing, The Safe Browsing APIs (v4) let your client applications check URLs against Google's constantly updated lists of unsafe web resources.
Google SheetsGoogle Sheets is a spreadsheet program that is part of the free web-based Google applications to create and format spreadsheets. Use this integration to create and modify spreadsheets.
Google Threat IntelligenceAnalyzes suspicious hashes, URLs, domains, and IP addresses.
Google VaultArchiving and eDiscovery for G Suite.
Google Vertex AIFine-tuned to conduct natural conversation. Using Google Vertex Ai (PaLM API for Chat)

The current integration of Google Vertex Ai is focusing only on the Generative AI model (PaLM) using the Chat prediction.

Later, this plugin will be updated to include the following:
- Model Creation
- Model Fine Tuning
- PaLM Text
Google Vision AIImage processing with Google Vision API
Google Workspace AdminG Suite or Google Workspace Admin is an integration to perform an action on IT infrastructure, create users, update settings, and more administrative tasks.
GoogleApps API and G SuiteSend messages and notifications to your Mattermost Team.
GophishGophish is a powerful, open-source phishing framework that makes it easy to test your organization's exposure to phishing. For Free
GrafanaGrafana alerting service.
GraphQLThe Generic GraphQL client can interact with any GraphQL server API.
GraylogIntegration with Graylog to search for logs and events
GreatHornThe only cloud-native security platform that stops targeted social engineering and phishing attacks on cloud email platforms like Office 365 and G Suite.
GreyNoiseGreyNoise is a cybersecurity platform that collects and analyzes Internet-wide scan and attack traffic. With this integration, users can contextualize existing alerts, filter false-positives, identify compromised devices, and track emerging threats.
GreyNoise CommunityGreyNoise is a cybersecurity platform that collects and analyzes Internet-wide scan and attack traffic. With this integration, users can contextualize existing alerts, filter false-positives, identify compromised devices, and track emerging threats. This Integration is design specifically for GreyNoise Community users and only provides the subset of intel available via the GreyNoise Community API.
GreyNoise Indicator FeedGreyNoise is a cybersecurity platform that collects and analyzes Internet-wide scan and attack traffic. With this integration, users can contextualize existing alerts, filter false-positives, identify compromised devices, and track emerging threats. This Integration provides a feed of IPv4 Internet Scanners from GreyNoise.
Group-IB THF PolygonTHF Polygon is a Malware Detonation & Research platform designed for deep dynamic analysis and enhanced indicators extraction. THF Polygon analyzes submitted files and urls and extracts deep IOCs that appear when malicious code is triggered and executed. Polygon could be used either for application-level tasks (like smtp-based mail filtering) and analytical purposes (files/urls analysis for verdict, report and indicators).
Group-IB Threat IntelligencePack helps to integrate Group-IB Threat Intelligence and get incidents directly into Cortex XSOAR.
The list of included collections:
Compromised Accounts, Compromised Cards, Brand Protection Phishing, Brand Protection Phishing Kit, OSI Git Leak, OSI Public Leak, Targeted Malware.
Group-IB Threat Intelligence FeedUse Group-IB Threat Intelligence Feed integration to fetch IOCs from various Group-IB collections.
GRRUse GRR Rapid Response framework
GuardiCore (Deprecated)Deprecated. Use GuardiCore v2 instead.
GuardiCore v2GuardiCore v2 Integration enables you to get information about incidents and endpoints (assets) via the GuardiCore API.
Gurucul-GRAGurucul Risk Analytics (GRA) is a Unified Security and Risk Analytics platform.
HackerOneHackerOne integration allows users to fetch reports by using the fetch incidents capability. It also provides commands to retrieve all the reports and programs.
HackuityFrom a war-room, query your Hackuity cockpit in order to seamlessly retrieve information related to your vulnerability stock.
HarfangLab EDRHarfangLab EDR Connector,
Compatible version 2.13.7+.
HashiCorp TerraformHashicorp Terraform provide infrastructure automation to provision and manage resources in any cloud or data center with Terraform.
HashiCorp VaultManage Secrets and Protect Sensitive Data through HashiCorp Vault.
Hatching TriageSubmit a high volume of samples to run in a sandbox and view reports.
Have I Been Pwned? v2Uses the Have I Been Pwned? service to check whether email addresses, domains, or usernames were compromised in previous breaches.
Hello World IAMAn Identity and Access Management integration template.
HelloWorldThis is the Hello World integration for getting started.
HelloWorld Event CollectorThis is the Hello World event collector integration for Cortex XSIAM.
HelloWorld FeedThis is the Feed Hello World integration for getting started with your feed integration.
HostIoUse the HostIo integration to enrich domains using the Host.io API.
HPE Aruba ClearPassAruba ClearPass Policy Manager provides role and device-based network access control for employees, contractors, and guests across any multi-vendor wired, wireless, and VPN infrastructure.
HumioIntegration with Humio
HYAS InsightUse the HYAS Insight integration to interactively lookup PassiveDNS, DynamicDNS, WHOIS, Sample Malware Records, C2 Attribution, Passive Hash, SSL Certificate, Open Source Indicators, Device Geo, Sinkhole, Malware Sample Information – either as playbook tasks or through API calls in the War Room.
HYAS ProtectUse the HYAS Protect integration to get the verdict information for FQDN, IP Address and NameServer – either as playbook tasks or through API calls in the War Room.
Hybrid Analysis (Deprecated)Deprecated. Use CrowdStrike Falcon Sandbox v2 instead.
IBM QRadar (Deprecated)Deprecated. Use IBM QRadar v2 or IBM QRadar v3 instead.
IBM QRadar v2 (Deprecated)Deprecated. Use the IBM QRadar v3 integration instead. Fetch offenses from QRadar using Cortex XSOAR. Supports API versions until 10.0. You can fetch the offenses with their related events and assets by creating a comma-separated list of event fields.
IBM QRadar v3IBM QRadar SIEM helps security teams accurately detect and prioritize threats across the enterprise, supports API versions 10.1 and above. Provides intelligent insights that enable teams to respond quickly to reduce the impact of incidents.
IBM Resilient SystemsCase management that enables visibility across your tools for continual IR improvement.
IBM X-Force Exchange v2IBM X-Force Exchange lets you receive threat intelligence about applications, IP addresses, URls and hashes.
ibossManage block lists, manage allow lists, and perform domain, IP, and/or URL reputation and categorization lookups.
IcebrgReduces risk by accelerating threat detection, triage, and response to rapidly-evolving breaches across global networks.
iDefense (Deprecated)Deprecated. Use the iDefense v2 integration instead.
iLertAlert and notify users using iLert
illuminate (Deprecated)Deprecated. Use Analyst1 integration instead.
Illumio CoreConnects to Illumio Core APIs to perform investigative and restorative actions.
IllusiveNetworksThe Illusive Attack Management API allows customers to retrieve detected incidents with a forensics timeline, attack surface insights, collect forensics on-demand, and manage a variety of operations with regard to deceptive entities, deception policies, and more.
Image OCRExtracts text from images.
Imperva IncapsulaUses incapsula to manage sites and IPs
Imperva SkyfenceThe Imperva Skyfence Cloud Gateway is a Cloud Access Security Broker (CASB) that provides visibility and control over sanctioned and unsanctioned cloud apps to enable their safe and productive use.
Imperva WAFUse the Imperva WAF integration to manage IP groups and web security policies in Imperva WAF.
IndeniIndeni is a turn-key automated monitoring providing visibility for security infrastructure. Indeni's production-ready Knowledge is curated from vetted, community-sourced experience, to deliver automation of tedious tasks with integration with your existing processes.
Indicators detectionThe Cortex Core - IOCs integration uses the Cortex API for detection and response, by natively integrating network, endpoint, and cloud data to stop sophisticated attacks.
InfinipointUse the Infinipoint integration to retrieve security and policy incompliance events, vulnerabilities or incidents. Investigate and respond to events in real-time.
InfoArmor VigilanteATIVigilanteATI redefines Advanced Threat Intelligence. InfoArmor's VigilanteATI platform and cyber threat services act as an extension of your IT security team.
InfobloxInfoblox enables you to receive metadata about IPs in your network and manages the DNS Firewall by configuring RPZs. It defines RPZ rules to block DNS resolution for malicious or unauthorized hostnames, or redirect clients to a walled garden by substituting responses.
Infoblox BloxOne Threat DefenseBloxOne Threat Defense is a hybrid cybersecurity solution that leverages DNS as the first line of defense to detect and block cyber threats.
Infoblox BloxOne Threat Defense Event CollectorBloxOne Threat Defense is a hybrid cybersecurity solution that leverages DNS as the first line of defense to detect and block cyber threats.
InfocyteInfocyte can pivot off incidents to automate triage, validate events with forensic data and enabling dynamic response actions against any or all host using both agentless or agented endpoint access.
Intel471 Actors Feed (Deprecated)Deprecated. To be replaced by use case centric functionality. No available replacement.
Intel471 Malware Feed (Deprecated)Deprecated. Use Intel471 Malware Indicator Feed instead.
Intel471 Malware Indicator Feed"Intel471's Malware Intelligence is focused on the provisioning of a high fidelity and timely indicators feed with rich context, TTP information, and malware intelligence reports.
This feed allows customers to block and gain an understanding of the latest crimeware campaigns and is for those that value timeliness, confidence (little to no false positives), and seek rich context and insight around the attacks they are seeing."
Intel471 Watcher Alerts'Intel 471's watcher alerts provide a mechanism by which customers can be notified in a timely manner of Titan content that is most relevant to them.'
Intezer v2Malware detection and analysis based on code reuse.
IntSights (Deprecated)Deprecated. Use Rapid7 Threat Command instead.
Investigation & ResponseThe Cortex Core IR integration uses the Cortex API for detection and response, by natively integrating network, endpoint, and cloud data to stop sophisticated attacks.
IP-APIThis integration will enrich IP addresses from IP-API with data about the geolocation, as well as a determination of the IP address being associated with a mobile device, hosting or proxy. Revers DNS is also returned.

This service is available for free (with a throttle) - or paid.
IP2LocationIOIP2Location.io integration to query IP geolocation data.
ipinfo (Deprecated)Deprecated. Use IPinfo v2 instead. Use the ipinfo.io API to get data about an IP address
IPinfo v2Use the IPinfo.io API to get data about an IP address.
IPQualityScoreProactively Prevent Fraud
ipstackOne of the leading IP to geolocation
APIs and global IP database services.
IRIS DFIRIRIS is a collaborative platform aiming to help incident responders to share technical details during investigations. It's free and open-source.
IronDefenseThe IronDefense Integration for Cortex XSOAR allows users to interact with IronDefense alerts within Cortex XSOAR. The Integration provides the ability to rate alerts, update alert statuses, add comments to alerts, to report observed bad activity, get alerts, get events, and get IronDome information.
IronscalesIRONSCALES, a self-learning email security platform integration
Ironscales Event CollectorUse this integration to fetch email security incidents from Ironscales as XSIAM events.
IsItPhishingCollaborative web service that provides validation on whether a URL is a phishing page or not by analyzing the content of the webpage.
Ivanti HeatUse the Ivanti Heat integration to manage issues and create Cortex XSOAR incidents from Ivanti Heat.
Ja3erQuery the ja3er API for MD5 hashes of JA3 fingerprints.
Jamf Protect Event CollectorUse this integration to fetch audits and alerts from Jamf Protect as events in Cortex XSIAM.
JAMF v2Enterprise Mobility Management (EMM) for Apple devices (Mac, iPhone, Apple TV, iPad). Can be used to control various configurations via different policies, install and uninstall applications, lock devices, smart groups searches, and more.
JARMActive TLS fingerprinting using JARM.
Jask (Deprecated)Deprecated. Use Sumo Logic Cloud SIEM instead. Freeing the analyst with autonomous decisions.
Jira Event CollectorJira logs event collector integration for Cortex XSIAM.
Joe Security (Deprecated)Deprecated. Use Joe Security v2 instead.
Joe Security v2Access the full set of possibilities the JoeSandbox Cloud provides via the RESTful Web API v2.
JSON FeedFetches indicators from a JSON feed.
JSON Sample Incident GeneratorA utility for testing incident fetching with mock JSON data.
JsonWhoIsProvides data enrichment for domains and IP addresses.
JWTJSON Web Token (JWT) is a compact, URL-safe means of representing claims to be transferred between two parties. This Integration can be used to Generate New JWT Tokens, Encode and Decode Existing Ones.
Kafka v2 (Deprecated)Deprecated. Use the Kafka v3 integration instead. The Open source distributed streaming platform.
Kafka v3Kafka is an open source distributed streaming platform.
Kali Dog Security CertStreamHunts for homograph-attacks by monitoring newly created X.509 certificates using CertStream by Kali Dog Security.
Kaspersky Security Center (Beta)Manages endpoints and groups through the Kaspersky Security Center.
Keeper Secrets ManagerUse the Keeper Secrets Manager integration to manage secrets and protect sensitive data through Keeper Vault.
Kenna v2Use the Kenna v2 integration to search and update vulnerabilities, schedule a run connector, and manage tags and attributes.
KnowBe4 KMSAT Event CollectorKnowBe4_KMSAT allows you to push and pull your external data to and from the KnowBe4 console.
KnowBe4KMSATKnowBe4 KMSAT integration allows you to pull Risk Scores, Phishing Tests, Campaigns and Enrollments.
KoodousCheck Android app samples (APK) against Koodous API
LaceworkLacework provides end-to-end cloud security automation for AWS, Azure, and GCP with a comprehensive view of risks across cloud workloads and containers.
LansweeperThe Lansweeper integration allows users to retrieve the asset details.
LastInfoSecThis integration allow to interact with the Gatewatcher LastInfoSec product via API.
Lastline v2Use the Lastline v2 integration to provide threat analysts and incident response teams with the advanced malware isolation and inspection environment needed to safely execute advanced malware samples, and understand their behavior.
LDAP AuthenticationAuthenticate using OpenLDAP or Active Directory.
LGTMAn Integration with LGTM API
LINENotifyLINE API Integration is used for sending a message to LINE Group.
LinkshadowFetch Network Anomalies data from LinkShadow and execute the remediation Actions.
LinuxAgentlesss Linux host management over SSH
Lockpath KeyLight v2Use the LockPath KeyLight integration to manage GRC tickets in the Keylight platform.
LogPoint SIEM IntegrationUse this Content Pack to search logs, fetch incident logs from LogPoint, analyze them for underlying threats, and respond to these threats in real-time.
LogRhythm (Deprecated)Deprecated. Use the LogRhythmRest v2 integration instead.
LogRhythmRestLogRhythm security intelligence.
LogRhythmRest v2LogRhythm security intelligence.
LogsignSiemLogsign SIEM provides to collect and store unlimited data, investigate and detect threats, and respond automatically.
Logz.ioFetch & remediate security incidents identified by Logz.io Cloud SIEM.
LOLBAS Feed"Living off the land binaries" is a term used to describe malware or hacking techniques that take advantage of legitimate tools and processes that are already present on a computer or network, rather than introducing new malware or malicious code. The goal is to blend in with normal activity and avoid detection. Examples of this include using built-in Windows commands to move laterally through a network, or using scripting languages that are commonly installed on a system to execute malicious code. LOLBAS project is documenting binaries, scripts, and libraries that can be used for Living Off The Land techniques.
LookerUse the Looker integration to query an explore, save queries as looks, run looks, and fetch look results as incidents.
Luminar IOCs & leaked credentialsThis connector allows integration of intelligence-based IOC data and customer-related leaked records identified by Luminar.
LumuSecOps operations - Reflect and manage the Lumu Incidents either from XSOAR Cortex or viceversa using the mirroring integration flow, https://lumu.io/
MAC VendorsQuery MAC Vendors for vendor names when providing a MAC address.
MAC Vendors maintains a list of vendors provided directly from the IEEE Standards Association and is updated multiple times each day. The IEEE is the registration authority and provides data on over 16,500 registered vendors.
Mail Listener v2Listens to a mailbox and enables incident triggering via e-mail.
Mail Sender (New)Send emails implemented in Python with embedded image support.
MailListener - POP3Listen to a mailbox, enable incident triggering via e-mail
Majestic Million FeedFree search and download of the top million websites.
MaltiverseUse the Maltiverse integration to analyze suspicious hashes, URLs, domains and IP addresses.
MalwareBazaarMalwareBazaar is a project from abuse.ch with the goal of sharing malware samples with the Infosec community, AV vendors, and threat intelligence providers.
MalwareBazaar FeedUse the MalwareBazaar Feed integration to get the list of malware samples added to MalwareBazaar within the last 60 minutes.
MalwarebytesScan and Remediate threats on endpoints in the Malwarebytes cloud.
Malwation AIMA (Deprecated)Deprecated. Use ThreatZone instead.
ManageEngine PAM360Integration to fetch passwords from the PAM360 repository, and to manage accounts, resources, and privileged credentials.
Mandiant Advantage Feed (Deprecated)Deprecated. Use Mandiant Advantage Threat Intelligence instead.
Mandiant Advantage Threat IntelligenceEnrich Indicators of Compromise, and fetch information about Actors, Malware Families, and Campaigns from Mandiant Advantage.
Mandiant Attack Surface ManagementIntegrate with Mandiant Advantage Attack Surface Management to import "issues" as Incidents.
Mandiant Automated Defense (Formerly Respond Software)Use the Mandiant Automated Defense integration to fetch and update incidents from Mandiant Automated Defense. Mandiant Automated Defense fetches open incidents and updates them every minute. Changes made within XSOAR are reflected in Mandiant Automated Defense platform with bi-directional mirroring capabilities enabled.
Mantiscreate and update issues in MantisBT,MantisBT is a popular free web-based bug tracking system
MattermostSend messages and notifications to your Mattermost Team.
MaxMind GeoIP2Enriches IP addresses.
McAfee Active ResponseConnect to MAR using its DXL client
McAfee Advanced Threat DefenseIntegrated advanced threat detection: Enhancing protection from network edge to endpoint
McAfee DAMMcAfee Database Activity Monitoring
McAfee DXLMcAfee DXL client
McAfee ePO (Deprecated)Deprecated. Use McAfee ePO v2 instead.
McAfee ePO v2McAfee ePolicy Orchestrator.
McAfee ESM v10 and v11 (Deprecated)Deprecated. Use the McAfee ESM v2 integration instead.
McAfee ESM v2This integration runs queries and receives alarms from McAfee Enterprise Security Manager (ESM). Supports version 10 and above.
McAfee NSM (Deprecated)Deprecated. Use McAfee NSM v2 integration instead.
McAfee NSM v2McAfee Network Security Manager gives you real-time visibility and control over all McAfee intrusion prevention systems deployed across your network.
McAfee Threat Intelligence Exchange (Deprecated)Deprecated. Use McAfee Threat Intelligence Exchange V2 integration instead.
McAfee Threat Intelligence Exchange v2Connect to McAfee TIE using the McAfee DXL client.
McAfee Web Gateway (Deprecated)Deprecated. Use Skyhigh Secure Web Gateway (On Prem) instead.
MetaDefender SandboxUnique adaptive threat analysis technology, enabling zero-day malware detection and more Indicator of Compromise (IOCs) extraction (previously known as OPSWAT Filescan Sandbox).
Micro Focus Service ManagerService Manager By Micro Focus (Formerly HPE Software).
MicroFocus SMAXFetch SMAX cases and automate differen SMAX case management actions
Microsoft 365 DefenderMicrosoft 365 Defender is a unified pre- and post-breach enterprise defense suite that natively coordinates detection, prevention, investigation, and response across endpoints, identities, email, and applications to provide integrated protection against sophisticated attacks.
Microsoft Advanced Threat AnalyticsUse Microsoft Advanced Threat Analytics integration to manage suspicious activities, monitoring alerts and entities.
Microsoft Defender for CloudUnified security management and advanced threat protection across hybrid cloud workloads.
Microsoft Defender for Cloud AppsMicrosoft Cloud App Security is a multimode Cloud Access Security Broker (CASB). It provides rich visibility, control over data travel, and sophisticated analytics to identify and combat cyber threats across all your cloud services. Use the integration to view and resolve alerts, view activities, view files, and view user accounts.
Microsoft Defender for Cloud Apps Event CollectorCollects the events log for alerts and activities provided Microsoft Defender for Cloud Apps API.
Microsoft Defender for Cloud Event CollectorXSIAM collector for Microsoft Defender for Cloud alerts.
Microsoft Defender for EndpointMicrosoft Defender for Endpoint (previously Microsoft Defender Advanced Threat Protection (ATP)) is a unified platform for preventative protection, post-breach detection, automated investigation, and response.
Microsoft Defender for Endpoint Event CollectorMicrosoft 365 Defender Event Collector integration.
Microsoft Endpoint Configuration ManagerThe Microsoft Endpoint Configuration Manager provides the overall Configuration Management (CM) infrastructure and environment to the product development team (formerly known as SCCM).
Microsoft Endpoint Manager (Intune)Microsoft Intune is a Microsoft cloud-based management solution that provides for mobile device and operating system management.
Microsoft Graph APIUse the Microsoft Graph API integration to interact with Microsoft APIs that do not have dedicated integrations in Cortex XSOAR, for example, Mail Single-User, etc.
Microsoft Graph Mail Single UserMicrosoft Graph grants Cortex XSOAR authorized access to a user's Microsoft Outlook mail data in a personal account or organization account.
Microsoft Graph SearchUse the Microsoft Search API in Microsoft Graph to search content stored in OneDrive or SharePoint: files, folders, lists, list items, or sites.
Microsoft Graph SecurityUnified gateway to security insights - all from a unified Microsoft Graph Security API.
Microsoft Intune FeedUse the Microsoft Intune Feed integration to get indicators from the feed.
Microsoft Management Activity API (O365 Azure Events)The Microsoft Management Activity API integration enables you to subscribe or unsubscribe to different audits, receive their content, and fetch new content as incidents.
Microsoft Policy And Compliance (Audit Log)Use the integration to get logs from the O365 service.
Microsoft SentinelMicrosoft Sentinel is a scalable, cloud-native solution that provides: Security information and event management (SIEM) Security orchestration, automation, and response (SOAR).
Microsoft TeamsSend messages and notifications to your team members.
Microsoft Teams ManagementManage teams and members in Microsoft Teams.
Microsoft Teams via WebhookIntegration for sending notifications to a Microsoft Teams channel via Incoming Webhook.
Mimecast Event Collector
Mimecast v2Mimecast unified email management offers cloud email services for email security, continuity and archiving emails. Please read detailed instructions in order to understand how to set the integration's parameters.
Minerva Labs Anti-Evasion PlatformMinerva eliminates the endpoint security gap while empowering companies to embrace technology fearlessly.
MinIOAn Integration with MinIO Object Storage.
MISP FeedIndicators feed from MISP.
MISP v2 (Deprecated)Deprecated. Use the MISP v3 integration instead.
MISP v3Malware information sharing platform and threat sharing.
MITRE ATT&CKUse the MITRE ATT&CK® feed to fetch MITRE’s Adversarial Tactics, Techniques, and Common Knowledge (ATT&CK®) content. MITRE ATT&CK is a globally-accessible knowledge base of adversary tactics and techniques based on real-world observations. The ATT&CK knowledge base is used as a foundation for the development of specific threat models and methodologies in the private sector, in government, and in the cybersecurity product and service community.
MITRE IDs Feed (Deprecated)Deprecated. Use MITRE ATT&CK Feed v2 instead.
MitreCalderaMitre Caldera can be used to test endpoint security solutions and assess a network's security posture against the common post-compromise adversarial techniques contained in the ATT&CK model. CALDERA leverages the ATT&CK model to identify and replicate adversary behaviors as if a real intrusion is occurring.
mnemonic MDR - Argus Managed DefenceRapidly detect, analyse and respond to security threats with mnemonic’s leading Managed Detection and Response (MDR) service.
MobileIronCLOUDMobileIron Cloud Integration.
MobileIronCOREMobileIron CORE Integration.
Moloch (Deprecated)Deprecated. Use Arkime instead.
MongoDBUse the MongoDB integration to search and query entries in your MongoDB.
MongoDB Key Value StoreManipulates key/value pairs according to an incident utilizing the MongoDB collection.
MongoDB LogWrites log data to a MongoDB collection.
MS-ISACThis API queries alerts and alert data from the MS-ISAC API to enrich and query alerts from the platform
MxToolBoxAll of your MX record, DNS, blacklist and SMTP diagnostics in one integrated tool
National Vulnerability DatabaseCVE feed from the National Vulnerability Database.
National Vulnerability Database Feed v2This feed pulls CVE information from the NIST National Vulnerability Database using v2.0 of the API.

Rejected CVEs are not ingested as part of this integration.

This integration/feed deprecates the original National Vulnerability Database Feed integraiton as v1.0 of the API is being sunsetted in 2023.
NcurionThis is the Ncurion integration for getting started.
NeosecNeosec is reinventing application security. Its pioneering SaaS platform gives security professionals visibility into behavior across their entire API estate. Built for organizations that expose APIs to partners, suppliers, and users, Neosec discovers all your APIs, analyzes their behavior, and stops threats lurking inside.
NessusVulnerability scanner for auditors and security analysts by Tenable Network Security
NetBox Event CollectorNetBox event collector integration for Cortex XSIAM.
NetcraftNetcraft takedown, submission and screenshot management.
Netcraft (Deprecated)Deprecated. Use Netcraft_V2 (Display name: Netcraft) instead.
NetmikoMulti-vendor library to simplify SSH connections to network devices. Utilizes the Python library Netmiko for connections. Supports SSH Key authentication and username / password.
Netscout Arbor Edge DefenseUse the Netscout Arbor Edge Defense integration to detect and stop both inbound threats and outbound malicious communication from compromised internal devices.
Netscout Arbor Sightline (Peakflow)DDoS protection and network visibility.
Netskope (API v1)Get alerts and events, manage quarantine files as well as URL and hash lists using Netskope API v1.
Netskope (API v2)Block URLs, domains and file hashes.
Netskope (Deprecated)Cloud access security broker that enables to find, understand, and secure cloud apps. Deprecated. Use Netskope (API v1) instead.
Netskope Event CollectorNetskope Event Collector integration.
NexthinkNexthink helps IT teams deliver on the promise of the modern digital workplace. Nexthink is the only solution to provide enterprises with a way to visualize, act and engage across the entire IT ecosystem to lower IT cost and improve digital employee experience.
Nist NVDNational Vulnerability Database
nmapRun nmap scans with the given parameters
Nozomi NetworksThe Nozomi Networks Guardian platform is a hardware or virtual appliance that is used to monitor OT/IoT/IT networks. It combines asset discovery, network visualization, vulnerability assessment, risk monitoring and threat detection in a single solution.
This integration is used to gather alerts and assets information from Nozomi.
NTT Cyber Threat SensorRetrieve alerts and recommendations from NTT CTS
NucleonCyberFeedThis is the NucleonCyber Feed integration
Nutanix HypervisorNutanix Hypervisor abstracts and isolates the VMs and their programs from the underlying server hardware, enabling a more efficient use of physical resources, simpler maintenance and operations, and reduced costs.
O365 - EWS - Extension (Deprecated)Deprecated. Use EWS Extension Online Powershell v3 instead.
O365 - Security And Compliance - Content Search (Deprecated)This integration allows you to manage and interact with Microsoft security and compliance content search.
O365 - Security And Compliance - Content Search v2This integration allows you to manage and interact with Microsoft security and compliance content search.
O365 Defender SafeLinksProvides URL scanning and rewriting of inbound email messages in mail flow, and time-of-click verification of URLs and links in email messages and other locations.
O365 Defender SafeLinks - Single UserEnables URL scanning, rewriting inbound email messages in the mail flow, time-of-click URL verification, and links in email messages and other locations.
O365 File Management (Onedrive/Sharepoint/Teams)Use the O365 File Management (Onedrive/Sharepoint/Teams) integration to enable your app to get authorized access to files in OneDrive, SharePoint, and MS Teams across your entire organization. This integration requires admin consent.
O365 Outlook CalendarO365 Outlook Calendar enables you to create and manage different calendars and events according to your requirements.
O365 Outlook Mail (Using Graph API)Microsoft Graph lets your app get authorized access to a user's Outlook mail data in a personal or organization account.
O365 Teams (Using Graph API)Microsoft Graph lets your app get authorized access to a user's Teams app in a personal or organization account.
OctoxLabsOctox Labs Cyber Security Asset Management platform.
Office 365 FeedThe Office 365 IP Address and URL web service is a read-only API provided by Microsoft to expose the URLs and IPs used by Office 365. The Office 365 Feed integration fetches indicators from the service, with which you can create a list (allow list, block list, EDL, etc.) for your SIEM or firewall service to ingest and apply to its policy rules.
okta (Deprecated)Deprecated. Use the Okta v2 integration instead.
Okta Auth0 Event CollectorOkta Auth0 logs event collector integration for Cortex XSIAM.
Okta Event CollectorCollects the events log for authentication and Audit provided by Okta admin API.
Okta IAMIntegrate with Okta's Identity Access Management service to execute CRUD operations to employee lifecycle processes.
Okta v2Integration with Okta's cloud-based identity management service.
OllamaIntegrate with open source LLMs using Ollama. With an instance of Ollama running locally you can use this integration to have a conversation in an Incident, download models, and create new models.
OneLogin Event CollectorSimple customer authentication and streamlined workforce identity operations.
OpenAI (Deprecated)Deprecated. Use `OpenAI GPT` instead.
OpenAI GPTDesigned to assist security professionals with security investigations, threat hunting, and anomaly detection, leveraging OpenAI GPT models' natural language conversational capabilities.
OpenCTIManages indicators from OpenCTI. Compatible with OpenCTI 5.12.17 API version.
OpenCTI Feed 3.X (Deprecated)Deprecated. Use OpenCTI Feed 4.X instead.
OpenCTI Feed 4.XIngest indicators from the OpenCTI feed. Compatible with OpenCTI 5.12.17 and above.
OpenCVESearches for CVE information using OpenCVE.
OpenPhish v2OpenPhish uses proprietary Artificial Intelligence algorithms to automatically identify zero-day phishing sites and provide comprehensive, actionable, real-time threat intelligence.
OPNSenseManage OPNsense Firewall.
For more information see OPNsense documentation.
OPNsense is an open source, easy-to-use and easy-to-build HardenedBSD based firewall and routing platform.
OpsGenie (Deprecated)Deprecated. Use the OpsGenie v3 integration instead
Opsgenie v2 (Deprecated)Deprecated. Use the OpsGenieV3 integration instead.
OpsGenie v3Integration with Atlassian OpsGenie. OpsGenie is a cloud-based service that enables operations teams to manage alerts generated by monitoring tools to ensure the right people are notified, and the problems are addressed in a timely manner.
OPSWAT Filescan Sandbox (Deprecated)Deprecated. Use MetaDefender Sandbox instead.
OPSWAT-Metadefender v2multi-scanning engine uses 30+ anti-malware engines to scan files for threats, significantly increasing malware detection.
Oracle Cloud Infrastructure Event CollectorCollects audit log events from Oracle Cloud Infrastructure resources.
Oracle Cloud Infrastructure FeedOracle Cloud Infrastructure Feed (OCI Feed)
This feed provides information about public IP address ranges for services that are deployed in Oracle Cloud Infrastructure.
Oracle IAMIntegrate with Oracle's services to execute CRUD and Group operations for employee lifecycle processes.
OrcaAgentless, Workload-Deep, Context-Aware Security and Compliance for AWS, Azure, and GCP.
Orca Event CollectorOrca Security event collector integration for Cortex XSIAM.
ORKL Threat Intel FeedUse the ORKL Threat Intel Feed integration to get receive threat intelligence indicators from the feed.
OSVOSV (Open Source Vulnerability) is a vulnerability database for open source projects. For each vulnerability, it perform bisects to figure out the exact commit that introduces the bug, as well the exact commit that fixes it. This is cross referenced against upstream repositories to figure out the affected tags and commit ranges
OTRSService management suite that comprises ticketing, workflow automation, and notification.
PacketsledPacketsled Network Security API commands
PagerDuty v2Alert and notify users using PagerDuty.
Palo Alto AutoFocus (Deprecated)Deprecated. Use the Palo Alto Networks AutoFocus v2 integration instead. Palo Alto Networks AutoFocus enables you to distinguish the most important threats from everyday commodity attacks.
Palo Alto Networks - Prisma Cloud ComputeUse the Prisma Cloud Compute integration to fetch incidents from your Prisma Cloud Compute environment.
Palo Alto Networks - Strata Cloud ManagerProvides commands for interaction with Prisma SASE API.
Palo Alto Networks AIOpsPalo Alto Networks Best Practice Assessment (BPA) analyzes NGFW and Panorama configurations and compares them to the best practices.
Palo Alto Networks AutoFocus v2Use the Palo Alto Networks AutoFocus integration to distinguish the most important threats from everyday commodity attacks.
Palo Alto Networks Automatic SLRAllow XSOAR to automatically generate Security Lifecycle Review's (SLR's).
Palo Alto Networks BPA (Deprecated)Deprecated. Use Palo Alto Networks AIops instead, run aiops-bpa-report-generate command.
Palo Alto Networks Cortex (Deprecated)Deprecated. We recommend using the Cortex Data Lake integration instead. This framework manages all PA's cloud managed products
Palo Alto Networks Cortex XDR - Investigation and ResponseCortex XDR is the world's first detection and response app that natively integrates network, endpoint, and cloud data to stop sophisticated attacks.
Palo Alto Networks Enterprise DLPPalo Alto Networks Enterprise DLP discovers and protects company data across every data channel and repository. Integrated Enterprise DLP enables data protection and compliance everywhere without complexity.
Palo Alto Networks IoTThis is the Palo Alto Networks IoT integration (previously Zingbox).
Palo Alto Networks IoT 3rd Party (Deprecated)Deprecated. Use the following link instead. To get the latest Palo Alto Networks IoT 3rd Party Integrations content pack, visit: https://docs.paloaltonetworks.com/iot/iot-security-integration/get-started-with-iot-security-integrations/third-party-integrations-using-a-full-featured-xsoar-server
Palo Alto Networks MineMeld (Deprecated)Deprecated. MineMeld streamlines the aggregation, enforcement and sharing of threat intelligence.
Palo Alto Networks PAN-OSManage Palo Alto Networks Firewall and Panorama. Use this pack to manage Prisma Access through Panorama. For more information, see the Panorama documentation.
Palo Alto Networks PAN-OS EDL Management (Deprecated)Deprecated. Use the Generic Export Indicators Service integration instead. This integration is still supported however, for customers with over 1000 Firewalls.
Palo Alto Networks Security Advisories (Beta)Queries the public repository of PAN-OS CVEs.
Palo Alto Networks Threat Vault (Deprecated)Deprecated. Use Threat Vault v2 instead.
Palo Alto Networks Threat Vault v2Use the Palo Alto Networks Threat Vault to research the latest threats (vulnerabilities/exploits, viruses, and spyware) that Palo Alto Networks next-generation firewalls can detect and prevent.
Query the Advanced Threat Protection (ATP) API endpoint for Analysis reports and PCAPs
Palo Alto Networks Traps (Deprecated)Deprecated. Use CortexXDR instead.
Palo Alto Networks WildFire ReportsGenerates a Palo Alto Networks WildFire PDF report. For internal use with the TIM Sample Analysis feature.
Palo Alto Networks WildFire v2Perform malware dynamic analysis.
PAN-OS Policy Optimizer (Beta)Automate your AppID Adoption by using this integration together with your Palo Alto Networks Next-Generation Firewall or Panorama.
PassiveTotal v2Analyze and understand threat infrastructure from a variety of sources-passive DNS, active DNS, WHOIS, SSL certificates and more-without devoting resources to time-intensive manual threat research and analysis.
PAT HelpdeskAdvancedImprove the effectiveness of your service provision and resources, and the quality of your IT department.
PenfieldThe penfield-get-assignee command takes in necessary context data, and returns the analyst that Penfield believes the incident should be assigned to based on Penfield's models of skill and process. The test command verfies that the endpoint is reachable.
PenteraAutomate remediation actions based on Pentera, the Automated Security Validation Platform, proactively exposing high-risk vulnerabilities.
PerceptionPointLoads incidents from Perception Point and releases falsely quarantined emails.
PerchPerch is a co-managed threat detection and response platform.
PerimeterX BotDefenderGathers PerimeterX related data.
Phish.AI (Deprecated)Deprecated. Vendor has declared end of life for this integration. No available replacement.
PhishERKnowBE4 PhishER integration allows to pull events from PhishER system and do mutations
PhishLabs IOCGet indicators of compromise from PhishLabs.
PhishLabs IOC DRPRetrieves Digital Risk cases Protection from PhishLabs.
PhishLabs IOC EIRGet Email Incident Reports from PhishLabs.
PhishTank v2PhishTank is a free community site where anyone can submit, verify, track, and share phishing data.
PhishUpPhishUp prevents phishing attacks, protects your staff and your brand with AI.
Picus SecurityRun commands on Picus and automate security validation with playbooks.
Picus Security NGPicus - The Complete Security Control Validation NG Platform.
PiHolePi-hole is a network-level advertisement and Internet tracker blocking application which acts as a DNS sinkhole and optionally a DHCP server, intended for use on a private network.
PingCastleThis integration will run a server that will listen for PingCastle XML reports.
PingOneIntegrates with the PingOne Management API to unlock, create, delete and update users.
PiplGet contact, social, and professional information about people.
Plain Text FeedFetches indicators from a plain text feed.
Polar SecurityPolar Security, an innovator in technology that helps companies discover, continuously monitor and secure cloud and software-as-a-service (SaaS) application data – and addresses the growing shadow data problem.
PolySwarmReal-time threat intelligence from a crowd-sourced network of security experts and antivirus companies.
Popular NewsPopular News integration fetches from three sources of news - Threatpost, The Hacker News and Krebs on Security. It outputs the title, links of the news articles and other metadata as a markdown table. The integration commands can either fetch the news from one source or all sources at a time.
Postmark SpamcheckPostmark's spam API, Spamcheck, is a RESTfull interface to the Spam filter tool SpamAssassin.
PowerShell Remoting (Beta)PowerShell Remoting is a comprehensive built-in remoting subsystem that is a part of Microsoft's native Windows management framework (WMF) and Windows remote management (WinRM).
This feature allows you to handle most remoting tasks in any configuration you might encounter by creating a remote PowerShell session to Windows hosts and executing commands in the created session.
The integration includes out-of-the-box commands which supports agentless forensics for remote hosts.
Preempt (Deprecated)Deprecated. No available replacement. Preempt Behavioral Firewall - Detection and enforcement based on user identity
Prisma AccessIntegrate with Prisma Access to monitor the status of the Service, alert and take actions.

Prisma Access Egress IP feedDynamically retrieve and add to allow list IPs Prisma Access uses to egress traffic to the internet and SaaS apps.
Prisma Cloud (RedLock) (Deprecated)Deprecated. Use the Prisma Cloud v2 integration instead.
Prisma Cloud v2Prisma Cloud secures infrastructure, workloads and applications, across the entire cloud-native technology stack.
PrismaCloud IAMThe Prisma Cloud IAM API consists of a set of API endpoints that allow customers to perform CRUD operation on their user profiles.
Proofpoint Email Security Event CollectorCollects events for Proofpoint Email Security using the streaming API.
Proofpoint FeedDetailed feed of domains and ips classified in different categories. You need a valid authorization code from Proofpoint ET to access this feed
Proofpoint Protection Server (Deprecated)Deprecated. The integration uses an unsupported scraping API. Use Proofpoint Protection Server v2 instead.
Proofpoint Protection Server v2Proofpoint email security appliance.
Proofpoint TAP v2Use the Proofpoint Targeted Attack Protection (TAP) integration to protect against and provide additional visibility into phishing and other malicious email attacks.
Proofpoint Threat Response (Beta)Use the Proofpoint Threat Response integration to orchestrate and automate incident response.
Proofpoint Threat Response Event CollectorUse the Proofpoint Threat Response integration to orchestrate and automate incident response.
ProtectWiseCloud based Security Network DVR
Public DNS FeedA feed of known benign IPs of public DNS servers.
PulsediveEnrich and analyze any domain, URL, or IP. Pivot to search on data points and linked indicators to investigate risky properties.
Qintel PMIQintel’s Patch Management Intelligence (PMI) product simplifies the vulnerability management process by providing vital context around reported Common Vulnerabilities and Exposures. With this integration, users can query PMI to surface CVEs that are known by Qintel to be leveraged by eCrime and Nation State adversaries.
Qintel QSentryQSentry queries help measure the likelihood that a user is masking their identity using publicly or privately available proxy or VPN services. The returns also flag any known fraud associations. QSentry aggregates data from Qintel’s proprietary Deep and DarkWeb research, as well as from commercially available anonymization services.
Qintel QWatchQintel's QWatch system contains credentials obtained from dump sites, hacker collaboratives, and command and control infrastructures of eCrime- and APT-related malware. With this integration, users can fetch exposure alerts as incidents and discover exposed credentials associated with their organization.
QR Code Reader - goqr.meRead QR Code from image file.
QSSQSS integration helps you to fetch Cases from Q-SCMP and add new cases automatically through XSOAR.
Qualys FIMLog and track file changes across global IT systems.
Qualys VMDRQualys Vulnerability Management lets you create, run, manage reports and to fetch Activity Logs, Assets and Vulnerabilities, launch and manage vulnerability and compliance scans, and manage the host assets you want to scan for vulnerabilities and compliance.
Query.AIQuery.AI is a decentralized data access and analysis technology that simplifies security investigations across disparate platforms without data duplication.
Quest KACE Systems Management Appliance (Beta)Use the Comprehensive Quest KACE solution to Provision, manage, secure, and service all network-connected devices.
QutteraWebsiteMalwareScannerQuttera Website Malware Scanner.
RaDarkThis integration enables you to fetch incidents and manage your RaDark monitor from Cortex XSOAR.
Rapid7 - Threat Command (IntSights)Rapid7 Insight - Threat Command allows managing alerts, CVEs, IOCs, and assets by accounts and MSSP accounts.
Rapid7 InsightIDRRapid7’s InsightIDR is your security center for incident detection and response, authentication monitoring, and endpoint visibility. Together, these form Extended Detection and Response (XDR). InsightIDR identifies unauthorized access from external and internal threats and highlights suspicious activity so you don’t have to weed through thousands of data streams.
Rapid7 InsightVMVulnerability management solution to help reduce threat exposure.
Rapid7 InsightVM CloudInsightVM is a vulnerability management tool that can scan your network, eliminate vulnerabilities, and track and communicate its progress.
Rapid7AppSecRapid7 AppSec integration allows the management of applications vulnerabilities and scans.
RasterizeConverts URLs, PDF files, and emails to an image file or PDF file.
RecoReco is a Saas data security solution that protects your data from accidental leaks and malicious attacks.
Recorded Future (Deprecated)Deprecated. Use Recorded Future v2 from RecordedFuture pack instead. Unique threat intel technology that automatically serves up relevant insights in real time.
Recorded Future - ListsSearch and manage watchlists in Recorded Future.
Recorded Future - Playbook AlertsFetch & triage Recorded Future Playbook Alerts.
Recorded Future Attack Surface IntelligenceAttack Surface Intelligence Risk Rules help security teams take risk and vulnerability prioritization to the next level by helping organizations identify the biggest weaknesses within their attack surface in mere seconds.
Recorded Future Event CollectorThis integration fetches alerts from Recorded Future.
Recorded Future IdentityRecorded Future Identity Integration that provides access to Recorded Future Identity module data.
Recorded Future RiskList FeedIngests indicators from Recorded Future feeds into Demisto.
Recorded Future v2Unique threat intel technology that automatically serves up relevant insights in real time.
Red CanaryRed Canary collects endpoint data using Carbon Black Response and CrowdStrike Falcon. The collected data is standardized into a common schema which allows teams to detect, analyze and respond to security incidents.
RedmineA project management and issue tracking system that provides a web-based platform for managing projects, tracking tasks, and handling various types of project-related activities.
ReliaQuest GreyMatter DRP Event CollectorReliaQuest GreyMatter DRP Event Collector monitors and manages an organization's digital risk across the widest range of data sources within the open, deep, and dark web.
Remedy On-Demand (Deprecated)Deprecated. Use BMC Helix ITSM instead.
Remote Access (Deprecated)File transfer and execute commands via ssh, on remote machines.
RemoteAccess v2This integration transfers files between Cortex XSOAR and a remote machine and executes commands on the remote machine.
Resecurity MonitoringThis package allows retrieving asset monitoring results from monitoring tasks that can be configured in Context and Risk platforms.
ReversingLabs A1000 (Deprecated)Deprecated. Use the ReversingLabs A1000 v2 integration instead.
ReversingLabs A1000 v2ReversingLabs A1000 advanced Malware Analysis Platform.
ReversingLabs Ransomware and Related Tools FeedA timely and curated threat intel list containing recent indicators extracted from ransomware and the tools used to deploy ransomware which are suitable for threat hunting or deployment to security controls.
ReversingLabs TitaniumCloud (Deprecated)Deprecated. Use the ReversingLabs TitaniumCloud v2 integration instead.
ReversingLabs TitaniumCloud v2ReversingLabs TitaniumCloud provides threat analysis data from various ReversingLabs cloud services.
ReversingLabs TitaniumScaleReversingLabs advanced file decomposition appliance.
RiskIQ Digital FootprintThe RiskIQ Digital Footprint integration enables your security team to manage assets outside your firewall. Using the integration, you can view asset details, add or update assets and analyze your digital footprint from the adversary's perspective.
RiskSenseRiskSense is a cloud-based platform that provides vulnerability management and prioritization to measure and control cybersecurity risk.
Roksit DNS Security (DNSSense)This integration provides adding selected domains to the Roksit Secure DNS's Blacklisted Domain List through API .
RSA Archer (Deprecated)Deprecated. Use the RSA Archer v2 integration instead.
RSA Archer v2The RSA Archer GRC platform provides a common foundation for managing policies, controls, risks, assessments, and deficiencies across lines of business.
RSA NetWitness EndpointRSA NetWitness Endpoint provides deep visibility beyond basic endpoint security solutions by monitoring and collecting activity across all of your endpoints on and off your network. The RSA Demisto integration provides access to information about endpoints, modules and indicators.
RSA NetWitness Packets and LogsRSA NetWitness Logs and Packets decoders are responsible for the real-time collection of network data. The decode captures data in real time and can normalize and reconstruct data for full session analysis. In addition, the decoder can collect flow and endpoint data.
RSA NetWitness Security AnalyticsRSA Security Analytics, compatible with prior to v11. A distributed and modular system that enables highly flexible deployment architectures that scale with the needs of the organization. Security Analytics allows administrators to collect two types of data from the network infrastructure, packet data and log data.
RSA NetWitness v11.1 (Deprecated)Deprecated. Use RSA NetWitness v11.5 instead
RSANetWitness v11.5The RSA NetWitness integration provides system log, network, and endpoint visibility for real-time collection, detection, and automated response with the Cortex XSOAR Enterprise platform. Using full session analysis, customers can extract critical data and effectively run security operations automated playbooks.
RSS FeedRSS Feed reader can ingest new items as report indicators.
RST Cloud - Threat Feed APIThis is the RST Threat Feed integration for interacting with API
RTIRRequest Tracker for Incident Response is a ticketing system which provides pre-configured queues and workflows designed for incident response teams.
Rubrik Security CloudThe Rubrik Security Cloud integration will fetch the Rubrik Anomaly Event and is rich with commands to perform the on-demand scans, backups, recoveries and many more features to manage and protect the organizational data.
RundeckRundeck is a runbook automation for incident management, business continuity, and self-service operations. |- The integration enables you to install software on a list of machines or perform a task periodically. Can be used when there is a new attack and you want to perform an update of the software to block the attack.
RunZeroRunZero is a network discovery and asset inventory
platform that uncovers every network in use and identifies every device connected – without credentials.
Scan your network and build your asset inventory in minutes.
RunZero Event CollectorThis is the RunZero event collector integration for XSIAM.
SaaS SecuritySaaS Security API is a cloud-based service that you can connect directly to your sanctioned SaaS applications using the cloud app’s API to provide data classification, sharing and permission visibility, and threat detection. This Content Pack provides insights into risks posed by data exposure and policy violations and enables you to use Cortex XSOAR to effectively manage the incidents discovered by SaaS Security API.
SaaS Security Event CollectorPalo Alto Networks SaaS Security Event Collector integration for XSIAM.
SafeBreachFor enterprises using SafeBreach and XSOAR, integrating this package streamlines operations by allowing you to operate SafeBreach through XSOAR, making SafeBreach an integral part of the enterprise workflows. This integration includes commands for managing tests, insight indicators, simulators and deployments, users, API keys, integration issues, and more.
SafeBreach (Deprecated)Deprecated. SafeBreach simulates attacks across the kill chain, to validate security policy, configuration, and effectiveness. Quantify the real impact of a cyber attack on your systems at any given moment. Identify remediation options. Stay ahead of attackers.
SafeBreach v2 (Deprecated)Deprecated. No available replacement.
Safewalk ManagementSafewalk server integration
Safewalk ReportsSafewalk server integration
SailPoint IdentityIQSailPoint IdentityIQ context pack enables XSOAR customers to utilize the deep, enriched contextual data in the SailPoint predictive identity platform to better drive identity-aware security practices.
SailPoint IdentityNowThe SailPoint Identity Security platform can be configured either on-prem/single tenant SaaS, or multi-tenant. This package is intended to be used with the SaaS, multi-tenant solution, IdentityNow.
SalesforceCRM Services
Salesforce Event Collector (Deprecated)Deprecated. Use Cortex XSIAM/XDR Salesforce integration instead.
Salesforce Fusion IAMIntegrate with Salesforce Fusion Identity Access Management service to execute CRUD (create, read, update, and delete) operations for employee lifecycle processes.
Salesforce IAMIntegrate with Salesforce's services to perform Identity Lifecycle Management operations.
Salesforce v2CRM Services
SAML 2.0Authenticate your Cortex XSOAR users using SAML 2.0 authentication with your organization`s identity provider.
SAML 2.0 - ADFS as IdPYou can authenticate your Demisto users using SAML 2.0 authentication and ADFS as the identity provider.
SAML 2.0 - Okta as IdPYou can authenticate your Demisto users using SAML 2.0 authentication and Okta as the identity provider.
SAML 2.0 - PingOne as IdPYou can authenticate your XSOAR users using SAML 2.0 authentication and PingOne as the identity provider.
SAP - IAMIntegrate with SAP's services to execute CRUD operations for employee lifecycle processes.
SCADAfence CNMfetching data from CNM
Screenshot MachineUses screenshot machine to get a screenshot
SecBIA threat, intelligence, and investigation platform, enabled by automation of detection and investigation, including remediation and prevention policy enforcements on all integrated appliances.
SecneurX AnalysisFully automated malware dynamic analysis sandboxing.
SecneurX Threat FeedsSecneurX provides real-time threat intelligence that protects companies against the latest cyber threats, including APTs, phishing, malware, ransomware, data exfiltration, and brand infringement. Security teams rely on our dependable and rich data to expand their threat landscape visibility, resulting in improved detection rates and response times.
Security Intelligence Services FeedA PassiveTotal with Security Intelligence Services Feed provides you with newly observed Domain, Malware, Phishing, Content and Scam Blacklist with Hourly ingestion available.
SecurityAdvisor (Deprecated)Deprecated. No available replacement.
SecurityScorecardProvides scorecards for domains.
SecurityTrailsThis integration provides API access to the SecurityTrails platform.
SecuronixUse the Securonix integration to manage incidents, threats, lookup tables, whitelists and watchlists.
SEKOIAIntelligenceCenterFetch Indicator and Observables from SEKOIA.IO Intelligence Center.
To use this integration, please create an API Key with the right permissions.
SendGridSendGrid provides a cloud-based service that assists businesses with email delivery. It allows companies to track email opens, unsubscribes, bounces, and spam reports. Our SendGrid pack utilize these SendGrid use cases to help you send and manage your emails.
SentinelOne Event CollectorThis integration fetches activities, threats, and alerts from SentinelOne.
SentinelOne v2Use the SentinelOne integration to send requests to your management server and get responses with data pulled from agents or from the management database.
SepioGet Agent, Switches and Events from your Sepio Prime
Server Message Block (SMB) (Deprecated)Deprecated. Use the Server Message Block (SMB) v2 integration instead.
Server Message Block (SMB) v2Files and Directories management with an SMB server. Supports SMB2 and SMB3 protocols.
Service Desk PlusUse this integration to manage on-premises and cloud Service Desk Plus requests. The integration allows you to create, update, and delete requests, assign groups and technicians to requests, and link/unlink requests and modify their resolution.
Service Desk Plus (On-Premise) (Deprecated)Deprecated. Use the Service Desk Plus instead.
ServiceNow (Deprecated)Deprecated. Use the ServiceNow v2 integration instead.
ServiceNow CMDBServiceNow CMDB is a service‑centric foundation that proactively analyzes service‑impacting changes, identifies issues, and eliminates outages.
ServiceNow Event CollectorUse this integration to fetch audit logs from ServiceNow as Cortex XSIAM events.
ServiceNow IAMIntegrate with ServiceNow's services to execute CRUD operations for employee lifecycle processes.
ServiceNow v2Use The ServiceNow IT Service Management (ITSM) solution to modernize the way you manage and deliver services to your users.
ShiftLeft COREIntegrate ShiftLeft CORE code analysis platform with Cortex XSOAR.
Shodan v2A search engine used for searching Internet-connected devices.
Signal Sciences WAFProtect your web application using Signal Sciences.
SilverfortUse the Silverfort integration to get and update Silverfort risk severity.
Simple SFTPSimple SFTP Integration to copy files from SFTP Server using paramiko.
Single ConnectSingle Connect is a PAM product that enables enterprises to remove static passwords stored in applications by instead keeping passwords in a secure password vault. Single Connect provides a token-based authentication for 3rd party applications when accessing the password vault. This authentication process verifies the application identity and gives secure access to the password associated with that identity.
Sixgill DarkFeed EnrichmentSixgill Darkfeed Enrichment – powered by the broadest automated collection from the deep and dark web – is the most comprehensive IOC enrichment solution on the market. By enriching Palo Alto Networks Cortex XSOAR IOCs with Darkfeed, customers gain unparalleled context and essential explanations in order to accelerate their incident prevention and response and stay ahead of the threat curve. Automatically enrich Cortex XSOAR IOCs (machine to machine) via Darkfeed. Block threats and enrich endpoint protection in real-time from the Cortex XSOAR dashboard, gain contextual and actionable insights with essential explanations of Cortex XSOAR IOCs.
Sixgill DarkFeed Threat IntelligenceLeverage the power of Sixgill to supercharge Cortex XSOAR with real-time Threat Intelligence indicators. Get IOCs such as domains, URLs, hashes, and IP addresses straight into the XSOAR platform.
Skyformation (Deprecated)Deprecated. Vendor has declared end of life for this integration. No available replacement.
Skyhigh Secure Web Gateway (On Prem)Manages the block and allow lists within Skyhigh Secure Web Gateway.
Skyhigh SecuritySkyhigh Security is a cloud-based, multi-tenant service that enables Cloud Discovery and Risk Monitoring, Cloud Usage Analytics, Cloud Access and Control.
Slack Event CollectorSlack logs event collector integration for XSIAM.
Slack IAMIntegrate with Slack's services to execute CRUD operations for employee lifecycle processes.
Slack v2 (Deprecated)Deprecated. Use SlackV3 instead.
Slack v3Send messages and notifications to your Slack team.
SlashNext Phishing Incident ResponseSlashNext Phishing Incident Response integration allows Cortex XSOAR users to fully automate analysis of suspicious URLs. For example, IR teams responsible for abuse inbox management can extract links or domains out of suspicious emails and automatically analyze them with the SlashNext SEER threat detection cloud to get definitive, binary verdicts (malicious or benign) along with IOCs, screen shots, and more. Automating URL analysis can save IR teams hundreds of hours versus manually triaging these emails or checking URLs and domains against less accurate phishing databases and domain reputation services.
SMIME MessagingUse the S/MIME (Secure Multipurpose Internet Mail Extensions) integration to send and receive secure MIME data.
Smokescreen IllusionBLACKSmokescreen IllusionBLACK is a deception-based threat defense platform designed to accurately and efficiently detect targeted threats including reconnaissance, lateral movement, malware-less attacks, social engineering, Man-in-the-Middle attacks, and ransomware in real-time.
SNDBOX (Deprecated)Deprecated. No available replacement.
Snort IP Blocklist FeedThis is the Snort IP Block List feed obtained from https://snort.org/
SnowflakeAnalytic data warehouse provided as Software-as-a-Service.
SOCRadar IncidentsFetches SOCRadar incidents with desired parameters so that relevant actions over the incidents can be taken by using Cortex XSOAR.
SOCRadar Threat FeedRetrieve indicators provided by collections via SOCRadar Threat Intelligence Feeds.
SOCRadar ThreatFusionEnrich indicators by obtaining enhanced information and reputation via ThreatFusion of SOCRadar.
SolarWindsThe SolarWinds integration interacts with the SWIS API to allow you to fetch alerts and events. It also provides commands to retrieve lists of alerts and events.
Sophos CentralThe unified console for managing Sophos products.
Sophos FirewallOn-premise firewall by Sophos enables you to manage your firewall, respond to threats, and monitor what’s happening on your network.
SpamcopSpamCop is an email spam reporting service, integration allow checking the reputation of an IP address
Spamhaus FeedUse the Spamhaus feed integration to fetch indicators from the feed.
SplunkPyRuns queries on Splunk servers.
SplunkPy Prerelease (Beta)Runs queries on Splunk servers.
SpurContextAPIEnrich indicators using the Spur Context API.
SpyCloudWith the SpyCloud integration data from breaches can be pulled and further processed in Playbooks. Filtering parameters can be used to filter the data set
SpyCloud Enterprise Protection EnrichmentIntegrate the SpyCloud Enterprise Protection API to use enrichment commands (along with sample Enrichment Playbooks) to look up your watchlists, domains, emails, IP addresses, usernames, and passwords. Data for malware-infected devices and exposed corporate applications are available for SpyCloud Compass users.
SpyCloud Enterprise Protection FeedFetch SpyCloud watchlist data (breach and malware records) for daily monitoring, incident response, and mitigation.
Stairwell InceptionStairwell Inception is a security intelligence engine that automates the continuous capture, storage, and of executable files and other primary security artifacts to improve detection and response against advanced attacks that evade traditional security tools.
Stamus[Get Declaration of Compromises from Stamus Security Platform and build Incidents. Then get related artifacts, events and Host Insight information].
Starter Base Integration - Name the integration as it will appear in the XSOAR UI[Enter a comprehensive, yet concise, description of what the integration does, what use cases it is designed for, etc.]
Stellar CyberFetches and mirrors in Cases from Stellar Cyber to XSOAR. In addition, provides a command to update Case severity/status/assignee/tags, and a command to query an Alert.
Strata Logging Service XSOAR ConnectorPalo Alto Networks Strata Logging Service XSOAR Connector provides cloud-based, centralized log storage and aggregation for your organization on premise, virtual (private cloud and public cloud) firewalls, for Prisma Access, and for cloud-delivered services such as Cortex XDR.
Sumo Logic Cloud SIEMFreeing the analyst with autonomous decisions.
SumoLogicCloud-based service for logs & metrics management
Symantec Advanced Threat Protection (Deprecated)Deprecated. No available replacement.
Symantec Blue Coat Content and Malware Analysis (Beta)Symantec Blue Coat Content and Malware Analysis integration.
Symantec Cloud Secure Web Gateway Event CollectorPalo Alto Networks Symantec Cloud Secure Web Gateway Event Collector integration for Cortex XSIAM.
Symantec CloudSOC Event CollectorGets Events from Symantec CloudSOC.
Symantec Data Loss Prevention (Deprecated)Deprecated. Use the Symantec Data Loss Prevention V2 integration instead. Symantec Data Loss Prevention enables you to discover, monitor and protect your sensitive corporate information.
Symantec Data Loss Prevention v2Symantec Data Loss Prevention version 15.7 enables you to discover, monitor and protect your sensitive corporate information.
Symantec Endpoint Detection and Response (EDR) - On PremSymantec EDR (On Prem) endpoints help to detect threats in your network by filter endpoints data to find Indicators of Compromise (IoCs) and take actions to remediate the threat(s). EDR on-premise capabilities allow incident responders to quickly search, identify, and contain all impacted endpoints while investigating threats using a choice of on-premises.
Symantec Endpoint Protection v2Query the Symantec Endpoint Protection Manager using the official REST API.
Symantec Managed Security ServicesLeverage the power of Symantec Managed Security Services for continual threat monitoring and customized guidance 24x7.
Symantec Management CenterSymantec Management Center provides a unified management environment for the Symantec Security Platform portfolio of products.
Symantec Messaging GatewaySymantec Messaging Gateway protects against spam, malware, targeted attacks and provides advanced content filtering, data loss prevention, and email encryption.
SynapseSynapse intelligence analysis platform.
SysAidSysAid is a robust IT management system designed to meet all of the needs of an IT department.
Syslog (Deprecated)Syslog events logger. Automatically convert incoming logs to incidents.
Syslog SenderUse the Syslog Sender integration to send messages and mirror incident War Room entries to Syslog.
Syslog v2A Syslog server enables automatically opening incidents from Syslog clients. This integration supports filtering logs to convert to incidents, or alternatively converting all logs.
TaegisXDR (Deprecated)Deprecated. Use TaegisXDR v2 instead.
TaegisXDR v2For integration with the Secureworks Taegis XDR platform.
Talos FeedUse the Talos Feed integration to get indicators from the feed.
Tanium (Deprecated)Deprecated. Use Tanium v2 instead.
Tanium Threat ResponseUse the Tanium Threat Response integration to manage endpoints processes, evidence, alerts, files, snapshots, and connections. This Integration works with Tanium Threat Response version below 3.0.159. In order to use Tanium Threat Response version 3.0.159 and above, use Tanium Threat Response V2 Integration.
Tanium Threat Response v2Use the Tanium Threat Response integration to manage endpoint processes, evidence, alerts, files, snapshots, and connections. This integration works with Tanium Threat Response version 3.0.159 and above.
Tanium v2Tanium endpoint security and systems management, filters out [current results unavailable] when returning question results.
TAXII 2 FeedIngests indicator feeds from TAXII 2.0 and 2.1 servers.
TAXII FeedIngests indicator feeds from TAXII 1.x servers.
TAXII ServerThis integration provides TAXII Services for system indicators (Outbound feed).
TAXII2 ServerThis integration provides TAXII2 Services for system indicators (Outbound feed).
Team CymruTeam Cymru provides various service options dedicated to mapping IP numbers to BGP prefixes and ASNs. Each of the services is based on the same BGP feeds from 50+ BGP peers and is updated at 4-hour intervals.
TeamViewer Event CollectorTeamViewer event collector integration for Cortex XSIAM.
Tenable Vulnerability Management (formerly Tenable.io)A comprehensive asset-centric solution to accurately track resources while accommodating dynamic assets such as cloud, mobile devices, containers, and web applications.
Tenable.scWith Tenable.sc (formerly SecurityCenter) you get a real-time, continuous assessment of your security posture so you can find and fix vulnerabilities faster.
TessianTessian is an email security platform that allows organizations to protect their users from inbound phishing threats, outbound data loss (both malicious and accidental) and account takeovers.
Thales SafeNet Trusted AccessThis integration enables you to process alerts from SafeNet Trusted Access (STA) indicating security risks to end user accounts, and apply security remediation actions on SafeNet Trusted Access through security orchestration playbooks.
Thales SafeNet Trusted Access Event CollectorRetrieve access, authentication, and audit logs and store them on a Security Information and Event Management (SIEM) system, local repository, or syslog file server. You can retrieve the logs only for the tenant that is associated with the API key, or for a direct or delegated child of that tenant.
TheHive ProjectIntegration with The Hive Project Security Incident Response Platform.
Thinkst CanaryBy presenting itself as an apparently benign and legitimate service(s), the Canary draws the attention of unwanted activity. When someone trips one of the Canary's triggers, an alert is sent to notify the responsible parties so that action can be taken before valubale systems in your network are compromised.
ThousandEyesThis Integration is used to to fetch-incidents via “Active alerts”, get alert details via “Alert details”, and get the “Agent list”.
Threat Crowd v2 (Deprecated)Deprecated. No available replacement.
ThreatConnect (Deprecated)Deprecated. Use the ThreatConnect v3 integration instead.
ThreatConnect FeedThis integration fetches indicators from ThreatConnect.
ThreatConnect v2 (Deprecated)Deprecated. Use the ThreatConnect v3 integration instead.
ThreatConnect v3ThreatConnect's integration is a intelligence-driven security operations solution with intelligence, automation, analytics, and workflows.
ThreatExchange (Deprecated)Deprecated. Use the ThreatExchange v2 integration instead.
ThreatExchange v2Receive threat intelligence about applications, IP addresses, URLs, and hashes. A service by Facebook.
ThreatMinerData Mining for Threat Intelligence
ThreatQ v2A threat intelligence platform that collects and interprets intelligence data from open sources and manages indicator scoring, types, and attributes.
ThreatXThe ThreatX integration allows automated enforcement and intel gathering actions.
ThreatZoneThreatZone malware analysis sandboxing.
Thycotic (Deprecated)Deprecated. Use DelineaSS instead.
ThycoticDSV (Deprecated)Deprecated. Use DelineaDSV instead.
TidyTidy integration handle endpoints enviorment installation.
TOPdeskTOPdesk’s Enterprise Service Management software (ESM) lets your service teams join forces and process requests from a single platform.
Tor Exit Addresses FeedTor is free software and an open network that helps you defend against traffic analysis, a form of network surveillance that threatens personal freedom and privacy, confidential business activities and relationships, and state security.
TraceableTraceable Platform Integration enables publishing Traceable Detected Security Events to be published to Cortex Xsoar for further action.
TrelloInteract with the Trello task manager
Trend Micro Apex OneTrend Micro Apex One central automation to manage agents and User-Defined Suspicious Objects
Trend Micro Cloud App SecurityUse Trend Micro Cloud App Security integration to protect against ransomware, phishing, malware, and unauthorized transmission of sensitive data for cloud applications, such as Microsoft 365, Box, Dropbox, Google G Suite and Salesforce.
Trend Micro Deep SecurityCloud Security Protection.
Trend Micro Email Security Event CollectorPalo Alto Networks Trend Micro Email Security Event Collector integration for XSIAM.
Trend Micro Vision OneTrend Micro Vision One is a purpose-built threat defense platform that provides added value and new benefits beyond XDR solutions, allowing you to see more and respond faster. Providing deep and broad extended detection and response (XDR) capabilities that collect and automatically correlate data across multiple security layers—email, endpoints, servers, cloud workloads, and networks—Trend Micro Vision One prevents the majority of attacks with automated protection.
Trend Micro Vision One Event CollectorPalo Alto Networks Trend Micro Vision One Event Collector integration for Cortex XSIAM collects the Workbench, Observed Attack Techniques, Search Detections and Audit logs.
Trend Micro Vision One V3.Trend Micro Vision One is a purpose-built threat defense platform that provides added value and new benefits beyond XDR solutions, allowing you to see more and respond faster. Providing deep and broad extended detection and response (XDR) capabilities that collect and automatically correlate data across multiple security layers—email, endpoints, servers, cloud workloads, and networks—Trend Micro Vision One prevents the majority of attacks with automated protection.
TripwireTripwire is a file integrity management (FIM), FIM monitors files and folders on systems and is triggered when they have changed.
TruSTAR (Deprecated)Deprecated. Not supported since TrueSTAR was acquired by Splunk, No available replacement.
TruSTAR v2 (Deprecated)Deprecated. Not supported since TrueSTAR was acquired by Splunk, No available replacement.
Trustwave Secure Email GatewayTrustwave SEG is a secure messaging solution that protects businesses and users from email-borne threats, including phishing, blended threats, and spam. Trustwave Secure Email Gateway also delivers improved policy enforcement and data leakage prevention.
TrustwaveFusionThe Trustwave Fusion platform connects your organization’s digital footprint
to a robust security cloud comprised of the Trustwave data lake, advanced
analytics, actionable threat intelligence and a wide range of Trustwave
services including Trustwave SpiderLabs , elite team of security
specialists. Your team will benefit from deep visibility and the advanced
security expertise necessary for protecting assets and eradicating threats as
they arise.
TufinRetrieve and analyze network access controls across Tufin-managed firewalls, SDN, and public cloud to identify vulnerable access paths of an attack.
TwilioSend SMS notifications
TwinwaveTwinWave’s threat analysis platform analyzes both URLs and files to detect credential phishing and malware threats. Our platform automatically navigates complex attack chains that attackers put in front of threats in order to evade analysis. In addition to detecting threats, the TwinWave platform generates actionable intelligence for threat hunting and other activities.
Twitter (Deprecated)Deprecated. Use Twitter v2 instead.
Twitter v2Twitter integration provides access to searching recent Tweets (in last 7 days) and user information using the Twitter v2 API.
TwitterIOCHunter FeedFetch the full daily feed from www.tweettioc.com/v1/tweets/daily/full
UBIRCHThe UBIRCH solution can be seen as an external data certification provider, as a data notary service, giving data receivers the capability to verify data they have received with regard to its authenticity and integrity and correctness of sequence.
UltraMSGThis is the UltraMSG integration for getting started made by Trustnet
Unisys StealthThis integration is intended to aid companies in integrating with the Stealth EcoAPI service. Using the included commands, security teams can trigger dynamically isolation of users or endpoints from the rest of the Stealth network.
Unit 42 ATOMs FeedUnit 42 feed of published IOCs, which contains known malicious indicators.
Unit 42 Feed (Deprecated)Deprecated. Use Unit42 ATOMs Feed instead.
Unit 42 Intel Objects FeedUse the Unit 42 Intel Objects Feed integration to fetch indicators from Unit 42 Intel Objects.
UptycsFetches data from the Uptycs database.
URLhausURLhaus has the goal of sharing malicious URLs that are being used for malware distribution.
URLhaus FeedFetch url indicators for URLhaus
urlscan.ioUse urlscan.io integration to perform scans on suspected URLs and see their reputation.
USTAUSTA is an Cyber Intelligence Platform that responds directly and effectively to today's complex cyber threats.
Varonis Data Security PlatformStreamline alerts and related forensic information from Varonis DSP.
Varonis SaaSStreamline alerts and related forensic information from Varonis SaaS.
Vectra (Deprecated)Deprecated. Use Vectra Detect instead.
Vectra AI Event CollectorCollects Vectra Detections and Audits into XSIAM Events.
Vectra DetectThis integration allows to create incidents based on Vectra Accounts/Hosts/Detections objects.
Vectra v2 (Deprecated)Deprecated. Use Vectra Detect instead.
Vectra XDRThis integration allows to create incidents based on Vectra XDR Entities.
Venafi (Deprecated)Deprecated. Use Venafi TLS Protect instead.
Venafi TLS ProtectRetrieves information about certificates stored in Venafi.
Versa DirectorVersa Director is a virtualization and service creation platform that simplifies the design, automation, and delivery of SASE services. Versa Director provides the essential management, monitoring, and orchestration capabilities needed to deliver all of the networking and security capabilities within Versa SASE.
VerticaAnalytic database management software
ViperViper is a binary analysis and management framework.
VirusTotal (API v3)Analyzes suspicious hashes, URLs, domains, and IP addresses.
VirusTotal (Deprecated)Deprecated. Use VirusTotalV3 integration instead.
VirusTotal - Premium (API v3)Analyse retro hunts, read live hunt notifications and download files from VirusTotal.
VirusTotal - Private API (Deprecated)Deprecated. Use "VirusTotal (API v3)" or "VirusTotal - Premium (API v3)" integrations instead.
VirusTotal Livehunt FeedUse this feed integration to fetch VirusTotal Livehunt notifications as indicators.
VirusTotal Retrohunt FeedUse this feed integration to fetch VirusTotal Retrohunt matches.
VMRayMalware analysis sandboxing.
VMwareVMware vCenter server is a centralized management application that lets you manage virtual machines and ESXi hosts centrally.
VMware Carbon Black App Control v2VMware Carbon Black App Control (formerly known as Carbon Black Enterprise Protection) is a next-generation endpoint threat prevention solution to deliver a portfolio of protection policies, real-time visibility across environments, and comprehensive compliance rule sets in a single platform. This integration only supports Carbon Black on-premise APIs.
VMware Carbon Black EDR (Deprecated)Deprecated. Use VMware Carbon Black EDR v2 instead.
VMware Carbon Black EDR (Live Response API)Collect information and take action on remote endpoints in real time with VMware Carbon Black EDR (Live Response API) (formerly known as Carbon Black Enterprise Live Response).
VMware Carbon Black EDR v2VMware Carbon Black EDR (formerly known as Carbon Black Response).
VMware Carbon Black Endpoint Standard (Deprecated)Deprecated. Use Carbon Black Endpoint Standard instead.
VMware Workspace ONE UEM (AirWatch MDM)VMware Workspace ONE UEM integration allows users to search enrolled corporate or employee-owned devices, provides detailed information about each device such as its serial number, installed OS's, pending OS updates, network details, and much more leveraging Workspace ONE UEM's (formerly AirWatch MDM) API.
VulnDBLists all of the security vulnerabilities for various products (OS,Applications) etc).
WALLIX BastionCentralized Control and Monitoring of Privileged Access to Sensitive Assets.
Web File RepositorySimple web server with a file uploading console to store small files.
This is helpful to make your environment ready for testing purpose for your playbooks or automations to download files from a web server.
WhatIsMyBrowserParse user agents and determine if they are malicious as well as enrich information about the agent
WhoisProvides data enrichment for domains.
Windows Remote Management (Beta)Uses the Python pywinrm library and commands to execute either a process or using Powershell scripts.
WithSecure Event CollectorWithSecure event collector integration for Cortex XSIAM.
WizAgentless cloud security.
Wolken ITSMUse The Wolken IT Service Management (ITSM) solution to modernize the way you manage and deliver services to your users.
WootCloudAppend HyperContext™ insights to your SIEM data and feed them into your orchestration workflows.
WordpressThe WordPress REST API provides an interface for applications to interact with your WordPress site by sending and receiving data as JSON (JavaScript Object Notation) objects. It is the foundation of the WordPress Block Editor, and can likewise enable your theme, plugin or custom application to present new, powerful interfaces for managing and publishing your site content.
WorkdayWorkday offers enterprise-level software solutions for financial management, human resources, and planning.
Workday Event CollectorUse Workday Event Collector integration to get activity loggings from Workday.
Workday IAMUse the Workday IAM Integration as part of the IAM premium pack.
Workday IAM Event Generator (Beta)Generates mock reports and events for Workday IAM. Use these for testing and development.
Workday Sign On Event CollectorUse the Workday Sign On Event Collector integration to get sign on logs from Workday.
Workday Signon Event Generator (Beta)Generates mock sign on events for Workday Signon Event Collector. Use these for testing and development.
xDomeUse the xDome integration to manage assets and alerts.
XM CyberThe XM Cyber integration creates unique incidents with valuable data collected daily, and enriches your existing incidents with attack simulation context. This enables you to prioritize your responses based on XM Cyber’s insights.
xMattersThis is an integration for using xMatters.
XSOAR EDL CheckerChecks an XSOAR hosted EDL to make sure it's returning a valid response. Supports PAN-OS (text), CSV, or JSON EDLs.
XSOAR Engineer TrainingThe XSOAR Engineer Training (XET) integration provides sample data to fetch events into Cortex XSOAR, and commands to build playbooks around.

Use for training purposes only.
XSOAR File ManagementThis integration uses the XSOAR API to perform basic but essentials actions on files.
XSOAR MirroringFacilitates mirroring of Cortex XSOAR incidents between different Cortex XSOAR tenants.
XSOAR StorageFacilitates the storage and retrieval of key/value pairs within XSOAR.
XSOAR-Web-ServerThis is a simple web-server that as of now, supports handling configurable user responses (like Yes/No/Maybe) and data collection tasks that can be used to fetch key value pairs. What makes it different from Data collection tasks is that, the URL to perform a certain action is predictable and written to the incident context when an action is setup.This URL can be inserted to for eg: an HTML email. User clicks are are recorded in the integration context and can be polled by Scheduled Commands/ Generic Polling.
Xsoar_UtilsThis is a wrapper on top of XSOAR API. Can be used to implement commands that call the XSOAR API in the background. This is mostly to avoid constructing raw json strings while calling the demisto rest api integration.

The first implemented command can be used to create an entry on any investigation; playground by default. An example use-case could be debugging a pre-process script. (Call demisto.execute_command("xsoar-create-entry",{arguments})

The idea is to use the same code to test from a local machine.
python3 Xsoar_Utils.py xsoar-create-entry '{"data":"# testapi4","inv_id":"122c7bff-feae-4177-867e-37e2096cd7d9"}'

Read the code to understand more.
ZabbixAllow integration with Zabbix api.
Zendesk v2IT service management
Zero Day Live TI FUSION FeedZero Day Live is Blackwired’s flagship product that delivers proprietary cyber threat intelligence, enabling our clients to operate at the same speed as the adversary. Zero Day Live specializes in unknown, zero day and early warning threats. Our intelligence is delivered finished, actionable and seamlessly orchestrated, directly into the existing security infrastructure – measurably reducing the risk of breach.
ZeroFoxCloud-based SaaS to detect risks found on social media and digital channels.
Zerohack XDRThe companion integration for Zerohack XDR. Current versions allow the user to collect data from the XDR and later versions will support data exfiltration to XDR.
ZeroTrustAnalyticsPlatformZero Trust Analytics Platform (ZTAP) is the underlying investigation platform and user interface for Critical Start's MDR service.
ZimperiumFetch and investigate mobile security alerts, generated based on anomalous or unauthorized activities detected on a user's mobile device.
Zimperium v2Fetch and investigate mobile security alerts, generated based on anomalous or unauthorized activities detected on a user's mobile device. Compatible with Zimperium 5.X API version.
ZoomUse the Zoom integration to manage your Zoom users and meetings.
Zoom Event CollectorThis is the Zoom event collector integration for Cortex XSIAM.
Zoom FeedUse the Zoom Feed integration to get indicators from the feed.
Zoom MailEnables interaction with the Zoom Mail API.
Zoom_IAMAn Identity and Access Management integration template.
Zscaler Internet AccessZscaler is a cloud security solution built for performance and flexible scalability. This integration enables you to manage URL and IP address allow lists and block lists, manage and update categories, get Sandbox reports, create, manage, and update IP destination groups and manually log in, log out, and activate changes in a Zscaler session.

Playbooks#

NameDescription
3CXDesktopApp Supply Chain Attack### 3CXDesktopApp Supply Chain Attack

#### Executive Summary
On March 29, 2023, CrowdStrike released a blog discussing a supply chain attack involving a software-based phone application called 3CXDesktopApp.

As of March 30, the 3CXDesktopApp installer hosted on the developer’s website will install the application with two malicious libraries included. The malicious libraries will ultimately run shellcode to load a backdoor on the system that allows actors to install additional malware on the victim machine.

Between March 9-30, 2023, we observed activity at 127 Cortex XDR customers that involved the 3CXDesktopApp process attempting to run shellcode, which was blocked by the XDR Agent’s In-process Shellcode Protection Module. Due to blocking the shellcode, we were unable to obtain the secondary payload used in this attack, so we cannot determine its capabilities or any post-exploitation activities carried out by the threat actor.

#### Affected Products
According to 3CX’s announcement, the supply chain attack involved 3CX’s Electron Windows App shipped in Update 7, version numbers 18.12.407 & 18.12.416 and Electron Mac App version numbers 18.11.1213, 18.12.402, 18.12.407 & 18.12.416.

#### Playbook Flow

This playbook should be triggered manually or can be configured as a job.
Please create a new incident and choose the 3CXDesktopApp Supply Chain Attack playbook and Rapid Breach Response incident type.

The playbook includes the following tasks:

Hunting:
- Cortex XDR
- XQL hunting queries
- Advanced SIEM queries
- Splunk
- QRadar
- Elasticsearch
- Azure Log Analytics
- Indicators hunting

References:

Threat Brief: 3CXDesktopApp Supply Chain Attack

CrowdStrike Falcon Platform Detects and Prevents Active Intrusion Campaign Targeting 3CXDesktopApp Customers

Note: This is a beta playbook, which lets you implement and test pre-release software. Since the playbook is beta, it might contain bugs. Updates to the pack during the beta phase might include non-backward compatible features. We appreciate your feedback on the quality and usability of the pack to help us identify issues, fix them, and continually improve.
Abuse Inbox Management Detect & RespondWhen combined with ‘SlashNext Abuse Management Protection’, this playbook fully automates the identification and remediation of phishing emails found in Microsoft 365 user inboxes. Using the indicators of compromise, URL, domain, and IP, found in the original email, it searches and remediates other emails containing the same IOCs.
Abuse Inbox Management ProtectionAnalyzes the URLs, domains, and IPs in suspicious emails, reported by end users, and returns a binary verdict (malicious or benign) and forensic information including screenshot of attack page, threat name and type, threat status, and first/last seen date
Access Investigation - GenericThis playbook investigates an access incident by gathering user and IP information.

The playbook then interacts with the user that triggered the incident to confirm whether or not they initiated the access action.
Access Investigation - Generic - NISTThis playbook investigates an access incident by gathering user and IP information, and handling the incident based on the stages in "Handling an incident - Computer Security Incident Handling Guide" by NIST.
https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-61r2.pdf

Used Sub-playbooks:
- IP Enrichment - Generic v2
- Account Enrichment - Generic v2.1
- Block IP - Generic v3
- NIST - Lessons Learned
Access Investigation - QRadarDeprecated. No available replacement. This playbook uses the QRadar integration to investigate an access incident by gathering user and IP information.

The playbook then interacts with the user that triggered the incident to confirm whether or not they initiated the access action.
Accessdata: Dump memory for malicious processDeprecated. No available replacement.
Account EnrichmentDeprecated. Use the "Account Enrichment - Generic v2.1" playbook instead.\ \ Enrich the accounts under the Account context key with details from relevant integrations such as AD.
Account Enrichment - GenericDeprecated. Use "Account Enrichment - Generic v2.1" playbook instead.\ \ Enrich Accounts using one or more integrations
Account Enrichment - Generic v2Deprecated. Use "Account Enrichment - Generic v2.1" playbook instead.\ \ Enrich accounts using one or more integrations. Supported integrations - - Active Directory
Account Enrichment - Generic v2.1Enrich accounts using one or more integrations.
Supported integrations:
- Active Directory
- Microsoft Graph User
- SailPoint IdentityNow
- SailPoint IdentityIQ
- PingOne
- Okta
- AWS IAM
- Cortex XDR (account enrichment and reputation)

Also, the playbook supports the generic command 'iam-get-user' (implemented in IAM integrations). For more information, visit https://xsoar.pan.dev/docs/integrations/iam-integrations.
Acquire And Analyze Host ForensicsThis playbook enables gathering forensic data from a host and analyzing the acquired data by using the relevant forensics automations.
ACTI Block High Severity IndicatorsDeprecated. No available replacement.
ACTI Block Indicators from an IncidentDeprecated. No available replacement.
ACTI Create Report-Indicator AssociationsDeprecated. No available replacement.
ACTI Incident EnrichmentThis playbook enriches Intelligence Alerts, Intelligence Reports, Malware Families, Threat Actors, Threat Groups & Threat Campaigns
ACTI Indicator EnrichmentDeprecated. No available replacement.
ACTI Report EnrichmentDeprecated. No available replacement.
ACTI Vulnerability EnrichmentDeprecated. No available replacement.
Active Directory - Get User Manager DetailsTakes an email address or a username of a user account in Active Directory, and returns the email address of the user's manager.
Active Directory InvestigationActive Directory Investigation playbook provides tools and guidance to investigate changes and manipulation in Active Directory containers, ACLs, Schema, and objects.
This playbook uses a 3rd party tool provided by Microsoft to scan the Active Directory access list, trees, and objects.
Additional investigative information is provided for manual investigation.
Add Employees to Departing Employee WatchlistLoops through stand-down tickets provided by the Departing Employee Auto-Add playbook and adds employees to the Departing Employee watchlist in Code42 Incydr.
Add Employees to New Hire WatchlistLoops through stand-up tickets provided by the New Hire Auto-Add playbook and adds employees to the New Hire watchlist in Code42 Incydr.
Add Indicator to Miner - Palo Alto MineMeldDeprecated. Add indicators to the relevant Miner using MineMeld.
Add IOCs - Cofense VisionAdd or update IOCs in Cofense Vision.
Add Note - Vectra XDRThis playbook will add a note in Vectra for an entity based on its type.
Add Unknown Indicators To Inventory - RiskIQ Digital FootprintAdds the unknown indicators or updates/removes the indicators identified as a known asset in the RiskIQ Digital Footprint inventory according to the user inputs for each asset. To select the indicators you want to add, go to playbook inputs, choose "from indicators" and set your query. For example reputation:None etc. The purpose of the playbook is to check if the indicators with the unknown reputation are known assets. The default playbook query is "reputation:None". In case indicators with different reputations are to be added to the inventory, the query must be edited accordingly. This playbook cannot be run in quiet mode. This playbook needs to be used with caution as it might use up the integration’s API license when running for large amounts of indicators.
Supported integration:
- RiskIQ Digital Footprint
Agari Message Remediation - Agari Phishing DefenseInvestigates Agari policy events by obtaining the original message and attachments from the existing email integrations and remediates in Agari.
Akamai WAF - Activate Network ListsActivates network lists in Staging or Production on Akamai WAF. The playbook finishes running when the network list is active on the requested enviorment.
Alibaba ActionTrail - multiple unauthorized action attempts detected by a userThis playbook investigates an “Alibaba ActionTrail - multiple unauthorized action attempts detected by a user” alert by gathering user and IP information and performing remediation based on the information gathered and received from the user.

Used Sub-playbooks:
Enrichment for Verdict
Block IP - Generic v3

To link this playbook to the relevant alerts automatically, we recommend using the following filters when configuring the playbook triggers:
Alert Source = Correlation
Alert Name = Alibaba ActionTrail - multiple unauthorized action attempts detected by a user
Allow IP - Okta ZoneSync a list of IP addresses to the Okta Network Zone with the given ID.
Existing IPs in the Okta Zone which are not in the input list will be removed and the indicator will be untagged in Cortex XSOAR.
IDs can be retrieved using !okta-list-zones. This playbook supports CIDR notation only (1.1.1.1/32) and not range notation (1.1.1.1-1.1.1.1)
Analyze File - Sandbox - ThreatZoneAnalyzes one file using the ThreatZone sandbox integration.
Returns relevant reports to the War Room and file reputations to the context data.
Dynamic Scan Extensions: exe, docx, dochtml, docm, doc, rtf, ps1, bat, cmd, xlw, xltx, xltm, xls, xlsx, odc, csv, xlshtml.
Analyze File - Static Scan - ThreatZoneAnalyzes one file using the ThreatZone static scan integration.
Returns relevant reports to the War Room and file reputations to the context data.
All file types are supported.
Analyze URL - ReversingLabs TitaniumCloudGet threat intelligence data for the submitted URL.
Required TitaniumCloud API rights:

TCA-0403
TCA-0402
Anomali Enterprise Forensic SearchInitiates a Forensic Search on IOCs in Anomali Match.
appNovi-MAC-Address-LookupLookup servers and IPs by MAC address
Arcanna-Generic-InvestigationAutomatically triage alert using Arcanna.Ai Machine Learning capabilities closing or assign incidents to analysts based on ML decision
Arcanna-Generic-Investigation-V2-With-FeedbackAlert Triage using Arcanna.Ai Machine Learning capabilities and reinforcement learning by offerring analyst feedback to incidents closed
Archer initiate incidentDeprecated. Use the `archer-get-file` command directly instead. initiate Archer incident
Arcsight - Get events related to the CaseGet the Case's Arcsight ResourceID from the FetchID field, or the "ID" label. If neither is there, ask user for the ID.
Use the resource ID to get full data for the case, the correlated/aggregate events underneath it, and all base events underneath them.
Armis Alert EnrichmentEnrich Armis alerts with the devices in the context details.
Armorblox Needs ReviewThis playbook sends email alerts to admins for Armorblox incidents that need review.
Assess Wiz IssuesExample basic Playbook to assess Wiz Issues
Assign Active Incidents to Next ShiftThis playbook reassigns Active Incidents to the current users on call, requires shift management to be setup. Can be run as a job a few minutes after the scheduled shift change time.

Update the playbook input with a different search query if required. Will also branch if there are no Incidents that match the query, and no users on call.

Search results are the default 100 Incidents returned by the query.
Assign Active Incidents to Next Shift V2This playbook reassigns Active Incidents to the current users on call. It requires shift management to be set up. The playbook can be run as a job a few minutes after the scheduled shift change time.

You can update the playbook input with a different search query, if required. Will branch if there are no incidents that match the query and no users on call.

Cases will not be assigned to users that defined OOO (by OutOfOffice automation).
Ataya - Securely logging device access to networkWith this playbook, we can enable Identity-Aware Security Across Multiaccess Networks.
ATD - Detonate FileDetonates a File using the McAfee Advanced Threat Defense sandbox.
Advanced Threat Defense supports the following File Types:
32-bit Portable Executables (PE)files; 64-bit PE+files
exe, sys, dll, com, scr, cpl, ocx, cgi
Microsoft Office Suite documents
doc,dotm, docx, dotx, xls, ppam, xlsx, pps, xlsb, ppsx, xlsm, ppsm, ppt, ppt, pptx, pptm, rtf, shs, xltm, sldm, xltx, sldx, xlam, thmx, docm, xar
Just Systems Ichitaro documents
jtd, jtdc
Adobe
pdf, swf
Compressed files
gz, 7z, tgz, msi, zip, lzh, cab, lzma, rar
Android application package
apk, Java, JAR, CLASS, Java Script, Java bin files
Image files
jpeg, png, gif
Other file types
cmd, ace, bat, arj, vbs, chm, xml, lnk, url, mof, htm, ocx, html, potm, eml, potx, msg, ps1, vb, reg, vba, wsc, vbe, wsf, vbs, wsh
Auto Add Assets - RiskIQ Digital FootprintThis playbook automatically adds the provided asset(s) to the RiskIQ Digital Footprint inventory according to the values provided. Use this playbook as a sub playbook and loop over each asset in the asset list in order to add multiple assets.
Supported integration:
- RiskIQ Digital Footprint
Auto Update Or Remove Assets - RiskIQ Digital FootprintThis playbook automatically updates or removes the provided asset(s) from the RiskIQ Digital Footprint inventory according to the values provided. Use this playbook as a sub playbook and loop over each asset in the asset list in order to update or remove multiple assets.
Supported integration:
- RiskIQ Digital Footprint
Autofocus - File Indicators HuntingThe playbook queries the PANW Autofocus session and samples log data for file indicators such as MD5, SHA256, and SHA1 hashes.

A simple search mode is used to query Autofocus based on the file indicators specified in the playbook inputs. Advanced search mode queries can also be used with multiple query parameters, but require all field names, parameters, and operators (JSON format) to be specified.
We recommended using the Autofocus UI to create an advanced query, exporting it, and pasting it into the relevant playbook inputs.

Note that multiple search values should be separated by commas only (without spaces or any special characters).
Autofocus - Hunting And Threat DetectionThe playbook queries the PANW Autofocus session and samples log data for file and traffic indicators, such as SHA256, SHA1, MD5, IP addresses, URLs, and domains.

A simple search mode queries Autofocus based on the indicators specified in the playbook inputs. Advanced queries can also use with multiple query parameters, but require all field names, parameters, and operators (JSON format) to be specified.
We recommended using the Autofocus UI to create an advanced query, exporting it, and pasting it into the relevant playbook inputs.

Note that multiple search values should be separated by commas only (without spaces or any special characters).
Autofocus - Traffic Indicators HuntingThe playbook queries the PANW Autofocus session and samples log data for traffic indicators such as URLs, IP addresses, and domains.

A simple search mode queries Autofocus based on the traffic indicators specified in the playbook inputs. Advanced search mode queries can also be used with multiple query parameters, but require all field names, parameters, and operators (JSON format) to be specified.
We recommended using the Autofocus UI to create an advanced query, exporting it, and pasting it into the relevant playbook inputs.

Note that multiple search values should be separated by commas only (without spaces or any special characters).
Autofocus Query Samples, Sessions and TagsThis playbook is used for querying the PANW threat intelligence Autofocus system. The playbook accepts indicators such as IP's, hashes, domains to run basic queries or mode advanced queries that can leverage several query parameters. In order to run the more advanced queries its recommended to use the Autofocus UI https://autofocus.paloaltonetworks.com/#/dashboard/organization to created a query and than use the export search button. The result can be used as a playbook input.

The playbook supports searching both the Samples API and the sessions API.
AutoFocusPollingUse this playbook as a sub-playbook to query PANW Autofocus Threat intelligence system. This sub-playbook is the same as the generic polling sub-playbook besides that it provides outputs in the playbook. The reason for that is that in Autofocus its impossible to query the results of the same query more than once so the outputs have to be in the polling context.

This playbook implements polling by continuously running the command in Step #2 until the operation completes.
The remote action should have the following structure:

1. Initiate the operation.
2. Poll to check if the operation completed.
3. (optional) Get the results of the operation.
AWS - EnrichmentGiven the IP address this playbook enriches EC2 and IAM information.
AWS - Security Group RemediationReplace current security groups with limited access security groups.
AWS - Security Group Remediation v2This playbook takes in some information about an EC2 instance (ID and public_ip) and with provided port and protocol, determines what security groups on the primary interface of an EC2 instance are over-permissive. It uses an automation to determine what interface on an EC2 instance has an over-permissive security group on, determine which security groups have over-permissive rules and to replace them with a copy of the security group that has only the over-permissive portion removed. Over-permissive is defined as sensitive ports (SSH, RDP, etc) being exposed to the internet via IPv4.
AWS - Unclaimed S3 Bucket RemediationThe playbook will create the unclaimed S3 bucket.
AWS - Unclaimed S3 Bucket ValidationThe playbook sends a HTTP get response to the hostname and validates if there is missing bucket information.
AWS - User InvestigationThis playbook performs an investigation on a specific user in AWS environments, using queries and logs from AWS CloudTrail to locate the following activities performed by the user:
- Failed login attempt
- Suspicious activities
- API access denied
- Administrative user activities
- Security rules and policies changes
- Access keys and access token activities
- Script-based user agent usage
- User role changes activities
- MFA device changes activities
AWS IAM - User enrichmentEnrich AWS IAM user information from AWS Identity and Access Management.
- List user access keys
- Get user information
AWS IAM User Access InvestigationDeprecated. Use `Cloud IAM User Access Investigation` instead. Investigate and respond to Cortex XSIAM alerts where an AWS IAM user`s access key is used suspiciously to access the cloud environment.
The following alerts are supported for AWS environments.
- Penetration testing tool attempt
- Penetration testing tool activity
- Suspicious API call from a Tor exit node
This is a beta playbook, which lets you implement and test pre-release software. Although AWS is supported, we are working towards multi-cloud support. As the playbook is beta, it might contain bugs. Updates to the playbook during the beta phase might include non-backward compatible features. We encourage feedback on the quality and usability of the content to help us identify and fix issues, so we can continually improve the content.
AWS IAM User Access Investigation - RemediationDeprecated. Use `Cloud IAM User Access Investigation` instead. Respond to Cortex XDR Cloud alerts where an AWS IAM user`s access key is used suspiciously to access the cloud environment.
The following alerts are supported for AWS environments.
- Penetration testing tool attempt
- Penetration testing tool activity
- Suspicious API call from a Tor exit node
This is a beta playbook, which lets you implement and test pre-release software. Although AWS is supported, we are working towards multi-cloud support. As the playbook is beta, it might contain bugs. Updates to the playbook during the beta phase might include non-backward compatible features. We encourage your feedback on the quality and usability of the content to help us identify and fix issues, so we can continually improve the content.
Azure - EnrichmentGiven an IP address, this playbook enriches Azure Compute, Microsoft Graph User, and IAM information and outputs Azure Compute, Microsoft Graph User, and IAM information.
Azure - Network Security Group RemediationThis playbook adds new Azure Network Security Groups (NSG) rules to NSGs attached to a NIC. The new rules will give access only to a private IP address range and block traffic that's exposed to the public internet (using the private IP of the VM as stated in Azure documentation). For example, if RDP is exposed to the public internet, this playbook adds new firewall rules that only allow traffic from private IP addresses and blocks the rest of the RDP traffic.

Conditions and limitations:
- Limited to one resource group.
- 200 Azure rules viewed at once to find offending rule.
- 2 priorities lower than the offending rule priority must be available.
- Adds rules to NSGs associated to NICs.
Azure - User InvestigationThis playbook performs an investigation on a specific user in Azure environments, using queries and logs from Azure Log Analytics to locate the following activities performed by the user:
- Script-based user agent usage
- Administrative user activities
- Security rules and policies changes
- Failed login attempt
- MFA failed login attempt
- Login attempt from an uncommon country
- Anomalies activities
- Risky users
- Uncommon high volume of actions
- Action uncommonly performed by the user
Azure Log Analytics - Query From Saved SearchExecutes a query from a saved search in Azure Log Analytics.
Azure-DevOps-Pipeline-RunDeprecated. Use azure-devops-pipeline-run command instead.
BeyondTrust Retrieve CredentialsPlaybook for retrieving credentials for BeyondTrust Password Safe
Block Account - GenericDeprecated. Use 'Block Account - Generic v2' instead. This playbook blocks malicious usernames using all integrations that you have enabled.

Supported integrations for this playbook:
Active Directory
PAN-OS - This requires PAN-OS 9.1 or higher.
Block Account - Generic v2This playbook blocks malicious usernames using all integrations that you have enabled.

Supported integrations for this playbook:
Active Directory
PAN-OS - This requires PAN-OS 9.1 or higher.
SailPoint
PingOne
AWS IAM
Clarizen IAM
Envoy IAM
ExceedLMS IAM
Okta
Microsoft Graph User (Azure Active Directory Users)
Google Workspace Admin
Slack IAM
ServiceNow IAM
Prisma Cloud IAM
Zoom IAM
Atlassian IAM
* GitHub IAM.
Block Domain - Cisco StealthwatchThis playbook blocks domains using Cisco Stealthwatch Cloud.
Block Domain - External Dynamic ListThis playbook blocks domains using External Dynamic Link.
The playbook adds a tag to the inputs domain indicators. the tagged domains can be publish as External Dynamic list that can be added to blocklist using products like Panorama by Palo Alto Networks.
For Panorama - You can block the tagged domains by creating EDL(in Panorama) with the XSOAR EDL Url, and assign it to Anti-Spyware profile under "DNS Signature Policies"
Block Domain - FireEye Email SecurityThis playbook blocks domains using FireEye Email Security.
The playbook checks whether the FireEye Email Security integration is enabled, whether the Domain input has been provided and if so, blocks the domain.
Block Domain - GenericDeprecated. Use 'Block Domain - Generic v2' instead. This playbook blocks malicious Domains using all integrations that are enabled.

Supported integrations for this playbook:
Zscaler
Symantec Messaging Gateway
FireEye EX
Trend Micro Apex One
* Proofpoint Threat Response
Block Domain - Generic v2This playbook blocks malicious Domains using all integrations that are enabled.

Supported integrations for this playbook:
Zscaler
Symantec Messaging Gateway
FireEye EX
Trend Micro Apex One
Proofpoint Threat Response
Cisco Stealthwatch Cloud
Block Domain - Proofpoint Threat ResponseThis playbook blocks domains using Proofpoint Threat Response.
The playbook checks whether the Proofpoint Threat Response integration is enabled, whether the Domain input has been provided and if so, blocks the domain.
Block Domain - Symantec Messaging GatewayThis playbook blocks domains using Symantec Messaging Gateway.
The playbook checks whether the Symantec Messaging Gateway integration is enabled, whether the Domain input has been provided and if so, blocks the domain.
Block Domain - Trend Micro Apex OneThis playbook blocks domains using Trend Micro Apex One.
The playbook checks whether the Trend Micro Apex One integration is enabled, whether the Domain input has been provided and if so, blocks the domain.
Block Domain - ZscalerThis playbook blocks domains using Zscaler.
The playbook checks whether the Zscaler integration is enabled, whether the Domain input has been provided and if so, blocks the domain.
Block Email - GenericDeprecated. Use 'Block Email - Generic v2' instead. This playbook will block emails at your mail relay integration.
Block Email - Generic v2This playbook will block emails at your mail relay integration.

Supported integrations for this playbook:
Mimecast
FireEye Email Security (EX)
Cisco Email Security
Symantec Email Security
Block Endpoint - Carbon Black ResponseDeprecated. Use the `Block Endpoint - Carbon Black Response V2.1` playbook instead. Carbon Black Response - isolate an endpoint, given a hostname.
Block Endpoint - Carbon Black Response V2Deprecated. Use the `Block Endpoint - Carbon Black Response V2.1` playbook instead. Carbon Black Response - isolates an endpoint for a given hostname.
Block Endpoint - Carbon Black Response V2.1Carbon Black Response - isolates an endpoint for a given hostname.
Block File - Carbon Black ResponseThis playbook receives an MD5 hash and adds it to the block list in Carbon Black Enterprise Response. Files with that MD5 hash are blocked from execution on the managed endpoints. If the hash is already on the block list, no action is taken on the MD5.

The playbook uses the integration ''VMware Carbon Black EDR v2".
Block File - CybereasonThis playbook accepts an MD5 hash and blocks the file using the Cybereason integration.
Block File - Cylance Protect v2This playbook accepts a SHA256 hash and adds the hash to the Global Quarantine list using the Cylance Protect v2 integration.
Block File - GenericDeprecated. Use "Block File - Generic v2" playbook instead. A generic playbook for blocking files from running on endpoints. This playbook currently supports Carbon Black Enterprise Response.
Block File - Generic v2This playbook is used to block files from running on endpoints.
This playbook supports the following integrations:
- Palo Alto Networks Traps
- Palo Alto Networks Cortex XDR
- Cybereason
- Carbon Black Enterprise Response
- Cylance Protect v2
- Crowdstrike Falcon
- Microsoft Defender for Endpoint.
Block Indicators - GenericDeprecated. We recommend using the 'Block Indicators - Generic v2' playbook instead.
This playbook blocks malicious indicators using all integrations that are enabled.

Supported integrations for this playbook:
Active Directory
Check Point Firewall
Palo Alto Networks Minemeld
Palo Alto Networks Panorama
Zscaler
Carbon Black Enterprise Response
Block Indicators - Generic v2Deprecated. Use the `Block Indicators - Generic V3` playbook instead.
This playbook blocks malicious Indicators using all integrations that are enabled, using the following sub-playbooks:

- Block URL - Generic
- Block Account - Generic
- Block IP - Generic v2
- Block File - Generic v2
- Block Email - Generic
- Block Domain - Generic

Block Indicators - Generic v3This playbook blocks malicious indicators using all integrations that are enabled, using the following sub-playbooks:

- Block URL - Generic v2
- Block Account - Generic v2
- Block IP - Generic v3
- Block File - Generic v2
- Block Email - Generic v2
- Block Domain - Generic v2.
Block IOCs from CSV - External Dynamic ListDeprecated. Use Generic Export Indicators Service instead.
Block IP - GenericDeprecated. Use "Block IP - Generic v2" playbook instead. This playbook blocks malicious IPs using all integrations that you have enabled.

Supported integrations for this playbook:
Check Point Firewall
Palo Alto Networks Minemeld
Palo Alto Networks Panorama
Zscaler
Block IP - Generic v2Deprecated. Use the `Block IP - Generic v3` playbook instead.
This playbook blocks malicious IPs using all integrations that are enabled.

Supported integrations for this playbook:
Check Point Firewall
Palo Alto Networks Minemeld
Palo Alto Networks PAN-OS
Zscaler
* FortiGate
Block IP - Generic v3This playbook blocks malicious IP addresses using all integrations that are enabled. The direction of the traffic that will be blocked is determined by the XSOAR user (and set by default to outgoing)
Note the following:
- some of those integrations require specific parameters to run, which are based on the playbook inputs. Also, certain integrations use FW rules or appended network objects.
- Note that the appended network objects should be specified in blocking rules inside the system later on.


Supported integrations for this playbook [Network security products such as FW/WAF/IPs/etc.]:

Check Point Firewall
Palo Alto Networks PAN-OS
Zscaler
FortiGate
Aria Packet Intelligence
Cisco Firepower
Cisco Secure Cloud Analytics
Cisco ASA
Akamai WAF
F5 SilverLine
ThreatX
Signal Sciences WAF
* Sophos Firewall

Block URL - GenericDeprecated. Use 'Block URL - Generic v2' instead.
Block URL - Generic v2This playbook blocks malicious URLs using all integrations that are enabled.

Supported integrations for this playbook:
Palo Alto Networks PAN-OS
Zscaler
Sophos
Forcepoint
Checkpoint
Netcraft
Bonusly - AutoGratitudeAutoGratitude is a playbook to give back a positive gratitude to security engineers and developers when they successfully complete an SLA
BreachRx - Create Incident and get Active TasksThis Playbook creates a privacy Incident on the BreachRx platform, and pulls in all tasks from that created privacy Incident into the Cortex XSOAR Incident.
Brute Force Investigation - GenericThis playbook investigates a "Brute Force" incident by gathering user and IP information, calculating the incident severity based on the gathered information and information received from the user, and performs remediation.

The playbook handles the following use-cases:

Brute Force IP Detected - A detection of source IPs that are exceeding a high threshold of rejected and/or invalid logins.
Brute Force Increase Percentage - A detection of large increase percentages in various brute force statistics over different periods of time.
* Brute Force Potentially Compromised Accounts - A detection of accounts that have shown high amount of failed logins with one successful login.

Used Sub-playbooks:
- IP Enrichment - Generic v2
- Account Enrichment - Generic v2.1
- Calculate Severity - Critical Assets v2
- Isolate Endpoint - Generic v2
- Block Indicators - Generic v3
Brute Force Investigation - Generic - SANSThis playbook investigates a "Brute Force" incident by gathering user and IP information, and calculating the incident severity based on the gathered information and information received from the user. It then performs remediation.
This is done based on the phases for handling an incident as they are described in the SANS Institute ‘Incident Handler’s Handbook’ by Patrick Kral.

https://www.sans.org/reading-room/whitepapers/incident/incident-handlers-handbook-33901

The playbook handles the following use-cases:

Brute Force IP Detected - A detection of source IPs that are exceeding a high threshold of rejected and/or invalid logins.
Brute Force Increase Percentage - A detection of large increase percentages in various brute force statistics over different periods of time.
* Brute Force Potentially Compromised Accounts - A detection of accounts that have shown high amount of failed logins with one successful login.

Used Sub-playbooks:
- IP Enrichment - Generic v2
- Account Enrichment - Generic v2.1
- Calculate Severity - Critical Assets v2
- Isolate Endpoint - Generic v2
- Block Indicators - Generic v3
- SANS - Lessons Learned

***Disclaimer: This playbook does not ensure compliance to SANS regulations.
Bulk Export Devices to ServiceNow - PANW IoT 3rd Party IntegrationThis playbook gets all available devices from PANW IoT Cloud and updates/creates endpoints with custom attributes in ServiceNow.
Bulk Export to Cisco ISE - PANW IoT 3rd Party IntegrationThis playbook gets all available device inventory from PANW IoT Cloud and updates/create endpoints with custom attributes on Cisco ISE.
Bulk Export to SIEM - PANW IoT 3rd Party IntegrationThis playbook gets all available assets ( alerts, vulnerabilities and devices) and send then to configured PANW third-party integration SIEM server.
C2SEC-Domain ScanLaunches a C2sec scan by domain name and waits for the scan to finish by polling its status in pre-defined intervals.
Calculate Severity - 3rd-party integrationsCalculates the incident severity level according to the methodology of a 3rd-party integration.
Calculate Severity - Cortex XDR Risky AssetsCalculates a severity for the incident based on the involvement of risky users or risky hosts in the incident, as determined by the Cortex XDR ITDR module.
Calculate Severity - Critical assetsDeprecated. Use Calculate Severity - Critical Assets v2 playbook instead. Determines if a critical assest is associated with the invesigation. The playbook returns a severity level of \"Critical\" if a critical asset is associated with the investigation.\n\nThis playbook verifies if a user account or an endpoint is part of a critical list or a critical AD group.
Calculate Severity - Critical Assets v2Determines if a critical assest is associated with the invesigation. The playbook returns a severity level of "Critical" if at least one critical asset is associated with the investigation.
Critical assets refer to: users, user groups, endpoints and endpoint groups.
Calculate Severity - GenericDeprecated. Use "Calculate Severity - Generic v2" playbook instead. Calculates and assign the incident severity based on the highest returned severity level from the following severity calculations:

Indicators DBotScore - Calculates the incident severity level according to the highest indicator DBotScore.
Critical assets - Determines if a critical assest is associated with the invesigation.
* 3rd-party integrations - Calculates the incident severity level according to the methodology of a 3rd-party integration.

NOTE: the new severity level overwrites the previous severity level even if the previous severity level was more severe.
Calculate Severity - Generic v2Calculate and assign the incident severity based on the highest returned severity level from the following calculations:

- DBotScores of indicators
- Critical assets
- Email authenticity
- Current incident severity
- Microsoft Headers
- Risky users (XDR)
- Risky hosts (XDR).
Calculate Severity - GreyNoiseCalculate and assign the incident severity based on the highest returned severity level from the following calculations:

- DBotScores of indicators
- Current incident severity
Calculate Severity - Indicators DBotScoreCalculates the incident severity level according to the highest indicator DBotScore.
Calculate Severity - StandardCalculates and sets the incident severity based on the combination of the current incident severity, and the severity returned from the Calculate Severity By Highest DBotScore playbook.
Calculate Severity By Email AuthenticityCalculates a severity according to the verdict coming from the CheckEmailAuthenticity script.
Calculate Severity By Highest DBotScoreCalculates the incident severity level according to the highest DBotScore.
Calculate Severity Highest DBotScore For Egress Network Traffic - GreyNoisePlaybook to calculate the severity based on GreyNoise
Calculate Severity Highest DBotScore For Ingress Network Traffic - GreyNoisePlaybook to calculate the severity based on GreyNoise
Caldera OperationThis playbook is used to create a new Operation in Mitre Caldera.
California - Breach NotificationThis playbook helps an analyst determine if the breached data meets the criteria for breach notification according to California law, and, if necessary, follows through with the notification procedures.

DISCLAIMER: Please consult with your legal team before implementing this playbook.

Source: http://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=CIV&sectionNum=1798.82.
Carbon Black EDR Search ProcessUse this playbook to search processes in Carbon Black Enterprise EDR.
This playbook implements polling by continuously running the `cb-eedr-process-search-results` command
until the operation completes.
Carbon black Protection Rapid IOC HuntingHunt for endpoint activity involving hash and domain IOCs, using Carbon black Protection (Bit9).
Carbon Black Rapid IOC HuntingDeprecated. Use "Search Endpoints By Hash - Carbon Black Response V2" playbook instead. Hunt for malicious indicators using Carbon Black
Carbon Black Response - Unisolate EndpointThis playbook unisolates sensors according to the sensor ID that is provided in the playbook input.
Case Management - GenericThis playbook executes when no other playbook is associated with an incident. It enriches indicators in an incident using one or more integrations.
Case Management - Generic - Send On Call NotificationThis playbook can be used to send email notification if an Incidents severity is Critical or High.

Can be used as a sub-playbook to perform the same logic across different playbooks/use cases.
Case Management - Generic - Set SLAs based on SeveritySets the SLAs for Incidents, the Time to Assignment Timer, and the Remediation SLA Timer based on the Incident Severity.
Case Management - Generic - Start SLA TimersThis playbook will start the Time to Assignment or Remediation SLA timers based on whether an Owner is assigned to the Incident.

Can be used as a sub-playbook to perform the same logic across different playbooks/use cases.
Case Management - Generic v2This playbook will extract and enrich indicators upon trigger, calculate Severity, and set SLAs and Timers.

Can be used as a default playbook to ingest new Incidents, or for manually created Incidents.
Change ManagementIf you are using PAN-OS/Panorama firewall and Jira or ServiceNow as a ticketing system this playbook is a perfect match for your change management for Firewall process.
This playbook can be triggered by 2 different options - a fetch from ServiceNow or Jira - and will help you manage and automate your change management process.
Check For Content InstallationThis playbook checks for content updates.
Check Incydr Status and Close XSOAR IncidentLoops through open XSOAR incidents and closes incidents created from Incydr alerts that are now dismissed.
Check Indicators For Unknown Assets - RiskIQ Digital FootprintThis playbook receives indicators from its parent playbook and checks if the indicator is an unknown or a known asset in the RiskIQ Digital Footprint inventory and gives out a list of the unknown as well as known assets. This playbook cannot be run in quiet mode. This playbook needs to be used with caution as it might use up the integration’s API license when running for large amounts of indicators.
Supported integration:
- RiskIQ Digital Footprint
Check IP Address For Whitelisting - RiskIQ Digital FootprintChecks if the provided IP Address should be added to allow list and excluded or not. Use this playbook as a sub-playbook to loop over multiple IP Addresses to check if they should be added to allow list and excluded.
Checkpoint - Block IP - Append GroupThe playbook receives malicious IP addresses as inputs, checks if the object group exists (if not, the object group is created), and appends the related IPs to that object. If you have not assigned the appended group to a rule in your firewall policy, you can use `rule_name` and the playbook creates a new rule.
Checkpoint - Block IP - Custom Block RuleThis playbook blocks IP addresses using Custom Block Rules in Check Point Firewall.
The playbook receives malicious IP addresses as inputs, creates a custom bi-directional rule to block them, and publishes the configuration.
Checkpoint - Block URLThis playbook blocks URLs using Check Point Firewall through Custom URL Categories.
The playbook checks whether the input URL category already exists, and if the URLs are a part of this category. Otherwise, it creates the category, blocks the URLs, and publishes the configuration.
Checkpoint - Publish&Install configurationPublish the Check Point Firewall configuration and install policy on all available gateways.
Checkpoint Firewall Configuration Backup PlaybookDeprecated. Triggers a backup task on each firewall appliance and pulls the resulting file into the war room via SCP.
CheckPointHEC Get email for incidentGet email entity for a specific incident.
ChronicleAsset Investigation - ChronicleThis playbook receives indicators from its parent playbook, performs enrichment and investigation for each one of them, provides an opportunity to isolate and block the hostname or IP address associated with the current indicator, and gives out a list of isolated and blocked entities. This playbook also lists the events fetched for the asset identifier information associated with the indicator.
ChronicleAssets Investigation And Remediation - ChroniclePerforms enrichment and investigation of the ChronicleAsset type of indicators, provides an opportunity to remediate in case any of the ChronicleAsset information i.e., hostname or IP address is found to be malicious or suspicious, and sends out an email containing the list of isolated and potentially blocked entities. To select the indicators you want to add, go to playbook inputs, choose "from indicators" and set your query. For example, type:ChronicleAsset etc. The default playbook query is "type:ChronicleAsset". In case indicators with different query parameters are to be investigated, the query must be edited accordingly. This playbook needs to be used with caution as it might use up the integration’s API license when running large amounts of indicators.
CimTrak - Example - Analyze IntrusionExample to analyze intrusion
CimTrak - Example - Scan Compliance By IPExample on how to run a compliance scan for an agent based on IP address
Cisco FirePower- Append network group objectThis playbook will append a network group object with new elements (IPs or network objects).
Claroty Incident
Claroty Manage Asset CVEs
Cloaked Ursa Diplomatic Phishing Campaign## Cloaked Ursa: Targeting Diplomatic Missions with Phishing Lures

Summary:

Cloaked Ursa, a hacking group associated with Russia's Foreign Intelligence Service, has been persistently targeting diplomatic missions globally. Using phishing tactics, Their initial access attempts over the past two years have predominantly used phishing lures with a theme of diplomatic operations such as the following:

- Notes verbale (semiformal government-to-government diplomatic communications)
- Embassies’ operating status updates
- Schedules for diplomats
- Invitations to embassy events

Recently, Unit42 researchers observed a shift in their strategy, with a focus on targeting diplomats themselves. In Kyiv alone, at least 22 out of over 80 foreign missions were targeted.

This playbook should be triggered manually or can be configured as a job.

Please create a new incident and choose the Cloaked Ursa (APT29) Diplomatic Phishing Campaign playbook and Rapid Breach Response incident type.

The playbook includes the following tasks:

IoCs Collection
- Blog IoCs download

Hunting:
- Cortex XDR XQL exploitation patterns hunting
- Advanced SIEM exploitation patterns hunting
- Indicators hunting

The hunting queries are searching for the following activities:
- Related LNK files execution command line
- Dropped file names

Mitigations:
- Unit42 mitigation measures

References:

Diplomats Beware: Cloaked Ursa Phishing With a Twist
Close Related XSOAR and Incydr IncidentsChecks for open XSOAR incidents associated with Incydr alerts and passes them to the Check Incydr Status and Close XSOAR Incident playbook.
Cloud Compute Enrichment - GenericThis playbook provides a generic enrichment of AWS, GCP, and Azure compute resources.
Cloud Credentials Rotation - AWS## AWS Credentials Rotation Playbook

### Identity Remediation
Secure compromised accounts by taking swift action:
- Reset Password: Resets the user password to halt any unauthorized access.

- Access Key Deactivation: Deactivate any suspicious or known-compromised access keys.

- Combo Action: In some cases, you may want to reset both the password and deactivate the access key for absolute security.

### Role Remediation
If a role is suspected to be compromised:
- Deny Policy Implementation: Attach a deny-all policy to the compromised role, thus preventing it from performing any further actions.

- Role Cloning: Before outright remediation, clone the role. This ensures that you have a backup with the same permissions, making transition smoother.
Cloud Credentials Rotation - Azure## Azure Credentials Rotation Playbook

### IAM Remediation
Protect your identity and access management:
- Reset Password: Resets the user password to halt any unauthorized access.

- Revoke Session: Terminates current active sessions to ensure the malicious actor is locked out.

- Combo Action: Resets the password and terminates all active sessions.

### Service Principal Remediation
Guard your applications:
- Password Regeneration: Generate a new password for the service principal, making sure the old one becomes obsolete.
Cloud Credentials Rotation - GCP## GCP Credentials Rotation Playbook

### IAM Remediation
For compromised service accounts:
- Access Key Disabling: Immediately disable the compromised service account access key.

- New Key Generation: After ensuring the old key is disabled, generate a new access key.

### GSuite Admin Remediation
Admin accounts are crucial:
- Reset Password: Resets the user password to halt any unauthorized access.

- Revoke Access Token: Revoke any suspicious or unauthorized access tokens.

- Combo Action: Reset the password and revoke access tokens to ensure complete safety.
Cloud Credentials Rotation - Generic## Cloud Credentials Rotation - Generic

This comprehensive playbook combines the remediation steps from AWS, Azure, and GCP sub-playbooks into a single, cohesive guide. Regardless of which Cloud Service Provider (CSP) you're working with, this playbook will direct you to the relevant steps, ensuring swift and effective response.

The primary objective is to offer an efficient way to address compromised credentials across different cloud platforms. By consolidating the key steps from AWS, Azure, and GCP, it minimizes the time spent searching for platform-specific procedures and accelerates the remediation process, ensuring the highest level of security for your cloud environments.

## Integrations for Each Sub-Playbook

In order to seamlessly execute the actions mentioned in each sub-playbook, specific integrations are essential. These integrations facilitate the automated tasks and processes that the playbook carries out. Here are the required integrations for each sub-playbook:

### AWS Sub-Playbook:
1. AWS - IAM: Used to manage AWS Identity and Access Management.
2. AWS - EC2: Essential for managing Amazon Elastic Compute Cloud (EC2) instances.

### GCP Sub-Playbook:
1. Google Workspace Admin: Manages users, groups, and other entities within Google Workspace.
2. GCP-IAM: Ensures management and control of GCP's Identity and Access Management.

### Azure Sub-Playbook:
1. Microsoft Graph Users: Manages users and related entities in Microsoft Graph.
2. Microsoft Graph Applications: Manages applications within Microsoft Graph.
Cloud Data Exfiltration Response## Cloud Data Exfiltration Response

The Cloud Data Exfiltration Response playbook is designed to address data exfiltration activity alerts in the cloud environment. This playbook is intended for handling "An identity performed a suspicious download of multiple cloud storage object" alert.
The playbook supports AWS, GCP, and Azure and executes the following:
- Enrichment involved assets.
- Determines the appropriate verdict based on the data collected from the enrichment.
- Cloud Persistence Threat Hunting:
- Conducts threat hunting activities to identify any cloud persistence techniques
- Verdict Handling:
- Handles false positives identified during the investigation
- Handles true positives by initiating appropriate response actions
Cloud Enrichment - Generic
## Generic Cloud Enrichment Playbook

The Cloud Enrichment - Generic Playbook is designed to unify all the relevant playbooks concerning the enrichment of information in the cloud. It provides a standardized approach to enriching information in cloud environments.

### Supported Blocks

1. Cloud IAM Enrichment - Generic
- Enriches information related to Identity and Access Management (IAM) in the cloud.

2. Cloud Compute Enrichment - Generic
- Enriches information related to cloud compute resources.

The playbook supports a single CSP enrichment at a time.
Cloud IAM Enrichment - GenericThis playbook is responsible for collecting and enriching data on Identity Access Management (IAM) in cloud environments (AWS, Azure, and GCP).
Cloud IAM User Access InvestigationInvestigate and respond to Cortex XSIAM alerts where a Cloud IAM user access key is used suspiciously to access the cloud environment.
The following alerts are supported for AWS, Azure, and GCP environments.
Penetration testing tool attempt
Penetration testing tool activity
Suspicious API call from a Tor exit node
Cloud IDS-IP Blacklist-GCP Firewall_AppendSet a list of IP addresses in GCP firewall.
Cloud IDS-IP Blacklist-GCP Firewall_CombineSet a list of IP addresses in GCP firewall.
Cloud IDS-IP Blacklist-GCP Firewall_ExtractGet Source IP
Cloud Response - AWSThis playbook provides response actions to AWS. The following are available for execution automatically/manually:
- Resource remediation:
- Terminate the instance
- Stop the instance
- Identity remediation:
- Delete the user
- Revoke the user's credentials
- Access key remediation:
- Disable the access key
- Delete the access key
- Block indicators.
Cloud Response - AzureThis playbook provides response actions to Azure. The following are available for execution automatically/manually:
- Resource remediation
- Delete the instance
- Power off the instance
- Identity remediation:
- Disable the user
- Delete the user
- Block indicators.
Cloud Response - GCPThis playbook provides response actions to GCP. The following are available for execution automatically/manually:
- Resource remediation:
- Delete the instance
- Stop the instance
- Identity remediation:
- Disable the user
- Delete the user
- Access key remediation:
- Disable the access key
- Delete the access key
- Block indicators.
Cloud Response - GenericThis playbook provides response playbooks for:
- AWS
- Azure
- GCP

The response actions available are:
- Terminate/Shut down/Power off an instance
- Delete/Disable a user
- Delete/Revoke/Disable credentials
- Block indicators
Cloud Threat Hunting - Persistence---

## Cloud Threat Hunting - Persistence Playbook

The playbook is responsible for hunting persistence activity in the cloud. It supports AWS, GCP, and Azure - one at a time.

### Hunting Queries

The playbook executes hunting queries for each provider related to each of the following:

1. IAM
2. Compute Resources
3. Compute Functions

### Indicator Extraction

If relevant events are found during the search, indicators will be extracted using the `ExtractIndicators-CloudLogging` script.

---
Cloud Token Theft - Set Verdict---

## Cloud Token Theft - Set Verdict Playbook

The playbook is built from a decision tree whose ultimate goal is to decide whether the observed activity is malicious.

### Event Search

The playbook searches for events based on the attacker's IP address within the last two hours.

### Tests Performed

The following tests are performed on the observed activity:

1. Malicious IP Check: Determines if the IP address is malicious.
2. CSP ASN Check: Checks if the activity was performed from an Autonomous System Number (ASN) belonging to one of the Cloud Service Providers (CSPs).
3. IP and ASN History Check: Verifies if the IP address and ASN have been previously observed.
4. Region Check: Determines if the API call was made from outside the recognized region.
5. Anomalous State Check: Checks if the API call was made from an anomalous state.
6. Alert Check: Looks for any related alerts around the event, including:
- Possible cloud instance metadata service (IMDS) abuse.
- Impossible Traveler by cloud identity.

---
Cloud Token Theft Response---

## Cloud Token Theft Response Playbook

The Cloud Token Theft Response Playbook provides a structured and comprehensive flow to effectively respond to and mitigate alerts involving the theft of cloud tokens. The playbook supports AWS, GCP, and Azure and executes the following:

Cloud Enrichment:
- Enriches the involved resources
- Enriches the involved identities
- Enriches the involved IPs

Verdict Decision Tree:
- Determines the appropriate verdict based on the investigation findings

Early Containment using the Cloud Response - Generic Playbook:
- Implements early containment measures to prevent further impact

Cloud Persistence Threat Hunting:
- Conducts threat hunting activities to identify any cloud persistence techniques

Enriching and Responding to Hunting Findings:
- Performs additional enrichment and responds to the findings from threat hunting

Verdict Handling:
- Handles false positives identified during the investigation
- Handles true positives by initiating appropriate response actions

---
Cloud User Investigation - GenericThis playbook performs an investigation on a specific user in cloud environments, using queries and logs from Azure Log Analytics, AWS CloudTrail, G Suite Auditor, and GCP Logging.
CloudConvert - Convert FileUse this playbook to convert a file to the required format using CloudConvert.
Cluster Report Categorization - Cofense Triage v3Cluster Report Categorization playbook is used to retrieve the reports of specific clusters and perform the categorization of reports.
Code42 Add Departing Employee From Ticketing System v2Parses a Ticket Summary containing a username='username' and optionally a departure='date' and adds the user to the Code42 Departing Employee list. This playbook uses Jira out-of-the-box, but you can swap it with a different Ticketing system and achieve the same result. For example, to use Zendesk, change the command `jira-get-issue` to be `zendesk-ticket-details` and use the `id` parameter for `issueId`. Change the output (what gets parsed) to be either the Subject or the Description from Zendesk.
Code42 Copy File To Ticketing System v2Downloads a file from Code42 and attaches it to a ticketing system. This playbook uses Jira out-of-the-box, but you can swap it with a different Ticketing system and achieve the same result. For example, to use ServiceNow, change the command `jira-issue-upload-file` to be `servicenow-upload-file` and use the `id` parameter for `issueId` and `file_id` for `entryId`.
Code42 Exfiltration PlaybookThe Code42 Exfiltration playbook acts on Code42 Security Alerts, retrieves file event data, and allows security teams to remediate file exfiltration events by revoking access rights to cloud files or containing endpoints.
Code42 File DownloadThis playbook downloads a file via Code42 by either MD5 or SHA256 hash.
Code42 File SearchThis playbook searches for files via Code42 security events by either MD5 or SHA256 hash. The data is output to the Code42.SecurityData context for use.
Code42 File Search v2This playbook searches for files via Code42 security events by either MD5 or SHA256 hash. The data is output to the Code42.FileEvents context for use.
Code42 Security AlertRetrieves Incydr alert details, assigns the alert to an analyst, and gathers employee and supervisor data from Active Directory, if applicable. Note: this playbook can be used as an alternate default to "Code42 Exfiltration Playbook" when the Code42 Incydr integration is set to "Fetch Incidents".
Code42 Suspicious Activity Action v2Take corrective actions against a Code42 user found to be exposing file data.
Code42 Suspicious Activity Review v2Detects suspicious activities of a user and allows a recipient to assess the results. Afterward, the playbook takes action on the user such as adding them to legal hold.
Codecov Breach - Bash UploaderThis playbook includes the following tasks:
- Search for the Security Notice email sent from Codecov.
- Collect indicators to be used in your threat hunting process.
- Query network logs to detect related activity.
- Search for the use of Codecov bash uploader in GitHub repositories
- Query Panorama to search for logs with related anti-spyware signatures
- Data Exfiltration Traffic Detection
- Malicious Modified Shell Script Detection
Note: This is a beta playbook, which lets you implement and test pre-release software. Since the playbook is beta, it might contain bugs. Updates to the pack during the beta phase might include non-backward compatible features. We appreciate your feedback on the quality and usability of the pack to help us identify issues, fix them, and continually improve.

More information:
Codecov Security Notice
Command-Line AnalysisThis playbook takes a command line from the alert and performs the following actions:
- Checks for base64 string and decodes if exists
- Extracts and enriches indicators from the command line
- Checks specific arguments for malicious usage

At the end of the playbook, it sets a possible verdict for the command line, based on the finding:
1. Indicators found in the command line
2. Found AMSI techniques
3. Found suspicious parameters
4. Usage of malicious tools
5. Indication of network activity
6. Indication of suspicious LOLBIN execution

Note: To run this playbook with a list of command lines, set this playbook to run in a loop. To do so, navigate to 'Loop' and check "For Each Input".
Commvault Suspicious File Activity RemediationPlaybook to disable data-aging on commvault client when a threat is detected.
Compare Process Execution Arguments To LOLBAS PatternsThis playbook takes a process name and determines its presence in the LOLBAS repository. It then proceeds to compare the incident command line against known patterns of malicious commands listed in TIM by using LOLBAS feed integration. The playbook outputs results when the similarity between the analyzed command line and the malicious patterns is greater than or equal to the preconfigured StringSimilarity threshold. The playbook offers the flexibility to adjust this threshold through the use of the dedicated playbook input, 'StringSimilarityThreshold'.
Compromised Credentials Match - FlashpointCompromised Credentials Match playbook uses the details of the compromised credentials ingested from the Flashpoint and authenticates using the Active Directory integration by providing the compromised credentials of the user, expires the credentials if it matches, and sends an email alert about the breach.
Supported integrations:
- Flashpoint
- OpenLDAP
- Active Directory Query v2
Configuration SetupPlaybook for the configuration incident type.
Containment PlanThis playbook handles the main containment actions available with Cortex XSIAM, including the following sub-playbooks:
Containment Plan - Isolate endpoint
Containment Plan - Disable account
Containment Plan - Quarantine file
Containment Plan - Block indicators
* Containment Plan - Clear user session (currently, the playbook supports only Okta)

Note: The playbook inputs enable manipulating the execution flow. Read the input descriptions for details.
Containment Plan - Block Indicators## Containment Plan - Block Indicators

This playbook is a sub-playbook within the containment plan playbook.

### Indicator Blocking

The playbook block indicators by two methods:

1. It adds the malicious hashes into the XSIAM hash block list
2. It utilizes the sub-playbook "Block Indicators - Generic v3"
Containment Plan - Clear User Sessions## Containment Plan - Clear User Sessions

This playbook is a sub-playbook within the containment plan playbook.
The playbook clears the users' sessions using Okta integration. (currently, the playbook supports only Okta)
Containment Plan - Disable Account## Containment Plan - Disable Account

This playbook is a sub-playbook within the containment plan playbook.
The playbook disables users by utilizing the sub-playbook "Block Account - Generic v2"
Containment Plan - Isolate Device## Containment Plan - Isolate Device

This playbook is a sub-playbook within the containment plan playbook.
The playbook isolates devices using core commands.
Containment Plan - Quarantine File## Containment Plan - Quarantine File

This playbook is a sub-playbook within the containment plan playbook.
The playbook quarantines files using core commands.
Content Update CheckDeprecated. Use "Content Update Manager" playbook instead. This playbook will check to see if there are any content updates available for installed packs and notify users via e-mail or Slack.
Content Update ManagerThis playbook checks for any available content updates for selected installed content packs and notifies users via e-mail or Slack.
It also contains an auto-update flow that lets users decide via playbook inputs or communication tasks if they want to trigger an auto-update process to install all updates that were found.
This playbook can be used as a Cortex XSOAR job to help users track marketplace pack updates and install them regularly.
Context Polling - GenericThis playbook polls a context key to check if a specific value exists.
Continuously Process Survey ResponsesNote: This is a beta playbook, which lets you implement and test pre-release software. Since the playbook is beta, it might contain bugs. Updates to the playbook during the beta phase might include non-backward compatible features. We appreciate your feedback on the quality and usability of the playbook to help us identify issues, fix them, and continually improve. Continuously processes new questionnaire responses as they are received.
Convert file hash to corresponding hashesThe playbook enables you to get all of the corresponding file hashes for a file even if there is only one hash type available.
For example, if we have only the SHA256 hash, the playbook will get the SHA1 and MD5 hashes as long as the
original searched hash is recognized by any our the threat intelligence integrations.
Cortex ASM - Active Directory EnrichmentPlaybook to enriches Service ownership info in Azure and On-Prem Active Directory.
Cortex ASM - ASM AlertThis playbook handles ASM alerts by enriching asset information and providing a means of remediating the issue directly or through contacting service owners.
Cortex ASM - AWS EnrichmentGiven the IP address this playbook enriches AWS information relevant to ASM alerts.
Cortex ASM - Azure EnrichmentGiven the IP address, this playbook enriches Azure information relevant to ASM alerts.
Cortex ASM - CMDB EnrichmentDeprecated. No available replacement. This playbook will look up a CI in ServiceNow CMDB by IP.
Cortex ASM - Cortex Endpoint EnrichmentThis playbook is used to pull information from Cortex Endpoint (XSIAM/XDR) systems for enrichment purposes.
Cortex ASM - Cortex Endpoint RemediationThis playbook is used to isolate a single Cortex Endpoint (XSIAM/XDR) for remediation purposes.
Cortex ASM - DecisionDeprecated. No available replacement. This playbook returns "RemediationAction" options based on meeting "Automated Remediation Requirements" (https://github.com/demisto/content/tree/master/Packs/CortexAttackSurfaceManagement#automated-remediation-requirements) as well as whether ServiceNowV2 integration is set up. Possible return values are:
- Prompt base - data collection task with only email/manual options.
- Prompt all options - data collection task with all options (meets Automated Remediation requirements and ServiceNow is enabled).
- Prompt no snow - all options except ServiceNow (Automated Remediation requirements are met).
- Prompt no ar - all options except Automated Remediation (ServiceNow is enabled).
Cortex ASM - Detect ServicePlaybook that looks to see if a service ID exists and chooses to start a Remediation Confirmation Scan.
Cortex ASM - Email NotificationThis playbook is used to send email notifications to service owners to notify them of their internet exposures.
Cortex ASM - EnrichmentUsed as a container folder for all enrichments of ASM alerts.
Cortex ASM - Extract IP IndicatorDeprecated. No available replacement. Identifies IPv4 Address associated with Alert and creates a new Indicator.
Cortex ASM - GCP EnrichmentGiven the IP address this playbook enriches GCP and Firewall information.
Cortex ASM - Jira NotificationThis playbook is used to create Jira tickets directed toward service owners to notify them of their internet exposures.
Cortex ASM - On Prem EnrichmentGiven an IP address, port, and protocol of a service, this playbook enriches on-prem integrations to find the related firewall rule and other related information.

Conditions:
- Multiple integration instances configured at the same time are not supported (Panorama or standalone NGFW).
- !pan-os-security-policy-match fails if any firewall is disconnected (Panorama).
- Matching on different rules for different firewalls not supported (Panorama).
Cortex ASM - On Prem RemediationThis playbook adds new block rule(s) to on-prem firewall vendors in order to block internet access for internet exposures.

Conditions:
- Multiple integration instances configured at the same time are not supported (Panorama or standalone NGFW).
- Multiple rules with the same name in different device-groups not supported (Panorama).
- !pan-os-list-services will fail if there are no services in a specific device-group (Panorama).
Cortex ASM - Prisma Cloud EnrichmentGiven the IP address this playbook enriches information from Prisma Cloud.
Cortex ASM - Qualys EnrichmentGiven the IP address this playbook enriches information from Qualys assets.
Cortex ASM - Rapid7 EnrichmentGiven the IP address this playbook enriches Rapid7 InsightVM (Nexpose) information relevant to ASM alerts.
Cortex ASM - RemediationThis playbook contains all the cloud provider sub playbooks for remediation.
Cortex ASM - Remediation Confirmation ScanPlaybook for Remediation Confirmation Scan
(RCS) creation and polling.
Cortex ASM - Remediation GuidanceThis playbook pulls remediation guidance off of a list based on ASM RuleID to be used in service owner notifications (email or ticketing system).
Cortex ASM - Remediation ObjectivesPlaybook that populates the remediation objectives field that is used to display the remediation actions to the end user.
Cortex ASM - Remediation Path RulesThis playbook returns "RemediationAction" options based on the return from the Remediation Path Rules API, or defaults to data collection task.
Cortex ASM - Service OwnershipIdentifies and recommends the most likely owners of the service, additionally citing an explanation and ranking score for each.
Cortex ASM - ServiceNow CMDB EnrichmentGiven the IP address this playbook enriches ServiceNow CMDB information relevant to ASM alerts.
Cortex ASM - ServiceNow ITSM EnrichmentGiven search terms, this playbook will query ServiceNow ticket descriptions and short descriptions over the last 30 days and set users that were found in the assigned_to field in those ServiceNow tickets. Note, the max amount of tickets returned from querying is 100.
Cortex ASM - ServiceNow NotificationThis playbook is used to create ServiceNow tickets directed toward service owners to notify them of their internet exposures.
Cortex ASM - SNMP CheckDeprecated. No available replacement.
Cortex ASM - Splunk EnrichmentGiven the IP address this playbook enriches information from Splunk results relevant to ASM alerts.
Cortex ASM - Tenable.io EnrichmentGiven the IP address this playbook enriches Tenable.io information relevant to ASM alerts.
Cortex ASM - Vulnerability Management EnrichmentDeprecated. No available replacement. This playbook will look up an IP address in Tenable.io or Rapid7 InsightVM.
Cortex XDR - AWS IAM user access investigationDeprecated. Use `Cortex XDR - Cloud IAM User Access Investigation` instead. Investigate and respond to Cortex XDR Cloud alerts where an AWS IAM user`s access key is used suspiciously to access the cloud environment.
The following alerts are supported for AWS environments.
- Penetration testing tool attempt
- Penetration testing tool activity
- Suspicious API call from a Tor exit node
This is a beta playbook, which lets you implement and test pre-release software. At the moment we support AWS but are working towards multi-cloud support. Since the playbook is beta, it might contain bugs. Updates to the playbook during the beta phase might include non-backward compatible features. We appreciate your feedback on the quality and usability of the content to help us identify issues, fix them, and continually improve.
Cortex XDR - Block FileUse this playbook to add files to Cortex XDR block list with a given file SHA256 playbook input.
Cortex XDR - Check Action StatusChecks the action status of an action ID. \nEnter the action ID of the action whose status you want to know.
Cortex XDR - check file existenceDeprecated. Use `xdr-file-exist-script-execute` command instead. Initiates a new endpoint script execution to check if the file exists and retrieve the results.
Cortex XDR - Cloud Data Exfiltration Response## Data Exfiltration Response

The Data Exfiltration Response playbook is designed to address data exfiltration activity alerts in the cloud environment. This playbook is intended for handling "An identity performed a suspicious download of multiple cloud storage object" alert.
The playbook supports AWS, GCP, and Azure and executes the following:
- Enrichment involved assets.
- Determines the appropriate verdict based on the data collected from the enrichment phase.
- Cloud Persistence Threat Hunting:
- Conducts threat hunting activities to identify any cloud persistence techniques
- Verdict Handling:
- Handles false positives identified during the investigation
- Handles true positives by initiating appropriate response actions
Cortex XDR - Cloud EnrichmentThis playbook is responsible for collecting data from Cortex XDR detector and enriching data for further usage and building the layout.

The playbook collects or enriches the following data:
- Resource enrichment
- Previous activity seen in the specified region or project
- Account enrichment
- Network enrichment
- Attacker IP
- Geolocation
- ASN
Cortex XDR - Cloud IAM User Access InvestigationInvestigate and respond to Cortex XDR Cloud alerts where a Cloud IAM user`s access key is used suspiciously to access the cloud environment.
The following alerts are supported for AWS, Azure, and GCP environments.
- Penetration testing tool attempt
- Penetration testing tool activity
- Suspicious API call from a Tor exit node

Cortex XDR - delete fileDeprecated. Use the `xdr-file-delete-script-execute` command instead. Initiates a new endpoint script execution to delete the specified file and retrieve the results.
Cortex XDR - Display Risky AssetsThis playbooks displays risky users and risky hosts, as detected by Cortex XDR's ITDR module. The data is displayed in incident fields in Cortex XDR incidents.
Cortex XDR - Endpoint InvestigationThis playbook is part of the 'Malware Investigation And Response' pack. For more information, refer to https://xsoar.pan.dev/docs/reference/packs/malware-investigation-and-response. This playbook handles all the endpoint investigation actions available with Cortex XSOAR, including the following tasks:
Pre-defined MITRE Tactics
Host fields (Host ID)
Attacker fields (Attacker IP, External host)
MITRE techniques
* File hash (currently, the playbook supports only SHA256)

Note: The playbook inputs enable manipulating the execution flow; read the input descriptions for details.
Cortex XDR - Execute commandsDeprecated. Use the `xdr-script-commands-execute` command instead. Initiates a new script execution of shell commands.
Cortex XDR - Execute snippet code scriptDeprecated. Use the `xdr-snippet-code-script-execute` command instead. Initiates a new endpoint script execution action using the provided snippet code and retrieves the file results.
Cortex XDR - False Positive Incident HandlingThis playbook is part of the 'Malware Investigation And Response' pack. For more information, refer to https://xsoar.pan.dev/docs/reference/packs/malware-investigation-and-response.
This playbook handles false-positive incident closures for Cortex XDR - Malware investigation.
Cortex XDR - First SSO AccessDeprecated. Use `Cortex XDR - Identity Analytics` instead.
Investigates a Cortex XDR incident containing First SSO access from ASN in organization
or First successful SSO connection from a country in organization.

The playbook executes the following:
- IP and User Enrichment.
- User Investigation - Using 'User Investigation - Generic' sub-playbook.
- Set alert's verdict - Using 'Cortex XDR - First SSO access - Set Verdict' sub-playbook.
- Response based on the verdict.

The playbook is used as a sub-playbook in ‘Cortex XDR Incident Handling - v3’.
Cortex XDR - First SSO Access - Set VerdictDeprecated. Use `Cortex XDR - Identity Analytics` instead.
This playbook determines the alert’s verdict based on the results of multiple checks.
By default, if at least two of the checks' results are true, the verdict is set to malicious.
else if only one check's results are true, the verdict is set to suspicious.
If none of the conditions is true, the verdict is set to non-malicious.
It is possible to change the threshold value of the inputs to change the sensitivity of the verdict.
Cortex XDR - Get entity alerts by MITRE tacticsThis playbook is part of the Cortex XDR by Palo Alto Networks’ pack. This playbook searches alerts related to specific entities from Cortex XDR, on a given timeframe, based on MITRE tactics.
Note: The playbook's inputs enable manipulating the execution flow. Read the input descriptions for details.
Cortex XDR - Get entity alerts by MITRE tactics CTFThis playbook is part of the Cortex XDR by Palo Alto Networks’ pack. This playbook searches alerts related to specific entities from Cortex XDR, on a given timeframe, based on MITRE tactics.
Note: The playbook's inputs enable manipulating the execution flow. Read the input descriptions for details.
Cortex XDR - Get File Path from alerts by hashThis playbook is part of the 'Malware Investigation And Response' pack. For more information, refer to https://xsoar.pan.dev/docs/reference/packs/malware-investigation-and-response.
This playbook assists in retrieving file paths from the Cortex XDR incident by hash.
Cortex XDR - Identity AnalyticsThe `Cortex XDR - Identity Analytics` playbook is designed to handle Cortex XDR Identity Analytics alerts and executes the following:

Analysis:
- Enriches the IP address and the account, providing additional context and information about these indicators.

Verdict:
- Determines the appropriate verdict based on the data collected from the enrichment phase.

Investigation:
- Checks for related Cortex XDR alerts to the user by Mitre tactics to identify malicious activity.
- Checks for specific arguments for malicious usage from Okta using the 'Okta User Investigation' sub-playbook.
- Checks for specific arguments for malicious usage from Azure using the 'Azure User Investigation' sub-playbook.

Verdict Handling:
- Handles malicious alerts by initiating appropriate response actions, including blocking malicious IP addresses and revoking or clearing user's sessions.
- Handles non-malicious alerts identified during the investigation.

The playbook is used as a sub-playbook in ‘Cortex XDR Alerts Handling v2’.
Cortex XDR - Isolate EndpointThis playbook accepts an XDR endpoint ID and isolates it using the 'Palo Alto Networks Cortex XDR - Investigation and Response' integration.
Cortex XDR - kill processDeprecated. Use the `xdr-kill-process-script-execute` command instead. Initiates a new endpoint script execution kill process and retrieves the results.
Cortex XDR - Large UploadThe playbook investigates Cortex XDR incidents involving large upload alerts. The playbook is designed to run as a sub-playbook of ‘Cortex XDR Alerts Handling v2’.

The playbook consists of the following procedures:
- Searches for similar previous incidents that were closed as false positives.
- Enrichment and investigation of the initiator and destination hostname and IP address.
- Enrichment and investigation of the initiator user, process, file, or command if it exists.
- Detection of related indicators and analysis of the relationship between the detected indicators.
- Utilize the detected indicators to conduct threat hunting.
- Blocks detected malicious indicators.
- Endpoint isolation.

This playbook supports the following Cortex XDR alert names:
- Large Upload (Generic)
- Large Upload (SMTP)
- Large Upload (FTP)
- Large Upload (HTTPS)
Cortex XDR - Malware InvestigationInvestigates a Cortex XDR incident containing internal malware alerts. The playbook:
- Enriches the infected endpoint details.
- The analyst can manually retrieve the malicious file.
- Performs file detonation.

The playbook is used as a sub- playbook in ‘Cortex XDR Incident Handling - v2’.
Cortex XDR - Port ScanDeprecated. Use the Cortex XDR - Port Scan - Adjusted playbook instead.
Investigates a Cortex XDR incident containing internal port scan alerts. The playbook:
- Syncs data with Cortex XDR
- Enriches the hostname and IP address of the attacking endpoint
- Notifies management about host compromise
- Escalates the incident in case of lateral movement alert detection
- Hunts malware associated with the alerts across the organization
- Blocks detected malware associated with the incident
- Blocks IPs associated with the malware
- Isolates the attacking endpoint
- Allows manual blocking of ports that were used for host login following the port scan
Cortex XDR - Port Scan - AdjustedThe playbook investigates Cortex XDR incidents involving port scan alerts. The playbook is designed to run as a sub-playbook of ‘Cortex XDR Alerts Handling’.

The playbook consists of the following procedures:
- Enrichment and investigation of the scanner and scanned hostname and IP address.
- Enrichment and investigation of the initiator user, process, file, or command if it exists.
- Detection of related indicators and analysis of the relationship between the detected indicators.
- Utilize the detected indicators to conduct threat hunting.
- Blocks detected malicious indicators.
- Endpoint isolation.

This playbook supports the following Cortex XDR alert names:
- Suspicious port scan
- Port scan by suspicious process
- Highly suspicious port scan
- Port scan.
Cortex XDR - Possible External RDP Brute-ForceThis playbook investigates a “Possible External RDP Brute Force” XDR Alert by gathering user, IP, and hostname information, and investigating if the following suspicious elements exists:

- "IP Reputation" - Dbot Score is 2-3
- "Source geolocation" - RDP Connection made from rare geo-location
- Related to campaign - IP address is related to campaign, based on TIM module
- Hunting results - the hunt for indicators related to the source IP and the related campaign returned results
- XDR Alert search - XDR Alerts that related to the same username and endpoint, and to the MITRE tactics that comes after "Credential Access", were found.
- Risky User - The user that was identified in the attack was given a medium or high score by XDR's ITDR module.
- Risky Host - The destination host that was identified in the attack was given a medium or high score by XDR's ITDR module.

Set verdict method:
Critical Element - The "Critical Element" input allows you to select a specific element that, if identified as suspicious, the investigation's final verdict will be deemed a "True Positive".

Final Verdict - Each suspicious element is being added to an array called "Suspicious Elements", which is used to count potential security threats. The array size will be compared to a final threshold. If the size is greater than or equal to the threshold, the investigation's final verdict will be deemed a "True Positive".

* User Engagement - The "UserEngagementThreshold" input allows you to set the number of suspicious elements that trigger user engagement. When this threshold is met, an email will be sent to the user and their manager asking for authorization of RDP activity. If the RDP activity is not authorized by the user, the investigation's final verdict will be deemed a "True Positive".
Cortex XDR - Possible External RDP Brute-Force - Set VerdictThis playbook creating an array called "Suspicious Elements", which is used to count potential security threats. The following elements can be added to the array:

- "IP Reputation" - DBot Score is 2-3
- "Source geolocation" - RDP Connection made from rare geo-location
- Related to campaign - IP address is related to campaign, based on TIM module
- Hunting results - the hunt for indicators related to the source IP and the related campaign returned results
- XDR Alert search - XDR Alerts that related to the same username and endpoint, and to the MITRE tactics that comes after "Credential Access", were found.
- Risky User - one or more risky users are involved in the incident, as identified by the Cortex XDR - IR integration's ITDR module.
- Risky Host - one or more risky hosts are involved in the incident, as identified by the Cortex XDR - IR integration's ITDR module.


The array will then be outputted and its size will be compared to a final threshold. If the size is greater than or equal to the threshold, the investigation's final verdict will be deemed a "True Positive."
Cortex XDR - Possible External RDP Brute-Force CTFThis playbook investigates a “Possible External RDP Brute Force” XDR Alert by gathering user, IP, and hostname information, and investigating if the following suspicious elements exists:

- "IP Reputation" - Dbot Score is 2-3
- "Source geolocation" - RDP Connection made from rare geo-location
- Related to campaign - IP address is related to campaign, based on TIM module
- Hunting results - the hunt for indicators related to the source IP and the related campaign returned results
- XDR Alert search - XDR Alerts that related to the same username and endpoint, and to the MITRE tactics that comes after "Credential Access", were found.

Set verdict method:
Critical Element - The "Critical Element" input allows you to select a specific element that, if identified as suspicious, the investigation's final verdict will be deemed a "True Positive".

Final Verdict - Each suspicious element is being added to an array called "Suspicious Elements", which is used to count potential security threats. The array size will be compared to a final threshold. If the size is greater than or equal to the threshold, the investigation's final verdict will be deemed a "True Positive".

* User Engagement - The "UserEngagementThreshold" input allows you to set the number of suspicious elements that trigger user engagement. When this threshold is met, an email will be sent to the user and their manager asking for authorization of RDP activity. If the RDP activity is not authorized by the user, the investigation's final verdict will be deemed a "True Positive".
Cortex XDR - PrintNightmare Detection and ResponseThe playbook targets specific PrintNightmare rules written by Cortex XDR for both vulnerabilities:
CVE-2021-1675 LPE
CVE-2021-34527 RCE

This playbook includes the following tasks:
- Containment of files, endpoints, users and IP Addresses
- Enrichment of indicators
- Data acquisition of system info and files using Cortex XDR
- Eradicating compromised user credentials

** Note: This is a beta playbook, which lets you implement and test pre-release software. Since the playbook is beta, it might contain bugs. Updates to the pack during the beta phase might include non-backward compatible features. We appreciate your feedback on the quality and usability of the pack to help us identify issues, fix them, and continually improve.
Cortex XDR - quarantine fileDeprecated. Use Cortex XDR - quarantine file v2 instead.
Cortex XDR - Quarantine File v2This playbook accepts "file path", "file hash" and "endpoint id" to quarantine a selected file and wait until the action is done. All 3 inputs are required to quarantine a single file. This playbook does not support the quarantine of multiple files.
Cortex XDR - Retrieve File by sha256This playbook is part of the 'Malware Investigation And Response' pack. For more information, refer to https://xsoar.pan.dev/docs/reference/packs/malware-investigation-and-response.
The playbook facilitates the process of retrieving files from the investigated devices, unzipping the retrieved files, and loading them into the War Room.

This playbook consists of the following steps:
Initially, the sub-playbook 'Cortex XDR - Get File Path from alerts by hash' examines the SHA256 file hashes and retrieves the file paths associated with each hash.
As soon as the SHA256 hashes, file paths, and endpoint IDs are obtained, the playbook attempts to retrieve the files from all the investigated devices.
Once the file retrieval automation has been completed successfully, the playbook will unzip the files and load them into the War Room.

Note: When retrieving multiple files, ensure that the SHA256 input is set to run in a loop.
Cortex XDR - Retrieve File PlaybookDeprecated. Use Cortex XDR - Retrieve File Playbook v2 instead.
Cortex XDR - Retrieve File v2This playbook retrieves files from selected endpoints. You can retrieve up to 20 files, from 10 endpoints.
Inputs for this playbook are:
- A comma-separated list of endpoint IDs.
- A comma-separated list of file paths for your operating system, either Windows, Linux, or Mac. At least one file path is required.
Cortex XDR - Run scriptInitiates a new endpoint script execution action using a provided script unique id from Cortex XDR script library.
Cortex XDR - Search And Block Software - XQL EngineThis playbook will search a file or process activity of a software by a given image file name using Cortex XDR XQL Engine. The analyst can then choose the files to block.
Cortex XDR - Search and Compare Process Executions - XDR AlertsThis playbook is a generic playbook that receives a process name and command-line argument. It uses the "Cortex XDR IR" integration to search for the given process executions inside Cortex XDR alerts and compares the command-line argument from the results to the command-line argument received from the playbook input.

Note: Under the "Processes" input, the playbook should receive an array that contains the following keys:
- value: process name
- commands: command-line arguments.
Cortex XDR - Search and Compare Process Executions - XQL EngineThis playbook is a generic playbook that receives a process name and a command-line argument. It uses the "Cortex XDR - XQL Engine" integration to search for the given process executions and compare the command-line argument from the results to the command-line argument received from the playbook input.

Note: Under the "Processes" input, the playbook should receive an array that contains the following keys:
- value: process name
- commands: command-line arguments
Cortex XDR - True Positive Incident HandlingThis playbook is part of the 'Malware Investigation And Response' pack. For more information, refer to https://xsoar.pan.dev/docs/reference/packs/malware-investigation-and-response.
This playbook handles a true-positive incident closure for Cortex XDR - Malware Investigation.
Cortex XDR - Unisolate EndpointThis playbook unisolates endpoints according to the endpoint ID that is provided in the playbook input.
Cortex XDR - XCloud CryptojackingInvestigates a Cortex XDR incident containing a Cloud Cryptojacking related alert.
The playbook supports AWS, Azure, and GCP and executes the following:

- Cloud enrichment:
- Collects info about the involved resources
- Collects info about the involved identities
- Collects info about the involved IPs
- Verdict decision tree
- Verdict handling:
- Handle False Positives
- Handle True Positives
- Cloud Response - Generic sub-playbook.
- Notifies the SOC if a malicious verdict was found
Cortex XDR - XCloud Cryptojacking - Set VerdictThis playbook sets the alert's verdict as malicious if one of the following conditions is true:
1. If the source IP address is malicious
2. If the incident includes both "Unusual allocation of multiple cloud compute resources" AND "Cloud identity reached a throttling API rate" (medium/high severity)
3. If the incident includes both "Unusual allocation of multiple cloud compute resources" AND "Suspicious heavy allocation of compute resources - possible mining activity"
4. If the incident includes "Unusual allocation of multiple cloud compute resources" with medium/high severity, the source ASN isn't known, and the source IP isn't known as well.
5. If the incident includes both "Unusual allocation of multiple cloud compute resources" AND "A cloud compute instance was created in a dormant region"

If none of the conditions is true, the playbook will wait for an analyst's decision.
Cortex XDR - XCloud Token Theft - Set Verdict---

## Cloud Token Theft - Set Verdict Playbook

The playbook is built from a decision tree whose ultimate goal is to decide whether the observed activity is malicious.

### Event Search

The playbook searches for events based on the attacker's IP address within the last two hours.

### Tests Performed

The following tests are performed on the observed activity:

1. Malicious IP Check: Determines if the IP address is malicious.
2. CSP ASN Check: Checks if the activity was performed from an Autonomous System Number (ASN) belonging to one of the Cloud Service Providers (CSPs).
3. IP and ASN History Check: Verifies if the IP address and ASN have been previously observed.
4. Region Check: Determines if the API call was made from outside the recognized region.
5. Anomalous State Check: Checks if the API call was made from an anomalous state.
6. Alert Check: Looks for any related alerts around the event, including:
- Possible cloud instance metadata service (IMDS) abuse.
- Impossible Traveler by cloud identity.

---
Cortex XDR - XCloud Token Theft Response---

## Cloud Token Theft Response Playbook

The Cloud Token Theft Response Playbook provides a structured and comprehensive flow to effectively respond to and mitigate alerts involving the theft of cloud tokens. The playbook supports AWS, GCP, and Azure and executes the following:

Cloud Enrichment:
- Enriches the involved resources.
- Enriches the involved identities.
- Enriches the involved IPs.

Verdict Decision Tree:
- Determines the appropriate verdict based on the investigation findings.

Early Containment using the Cloud Response - Generic Playbook:
- Implements early containment measures to prevent further impact.

Cloud Persistence Threat Hunting:
- Conducts threat hunting activities to identify any cloud persistence techniques.

Enriching and Responding to Hunting Findings:
- Performs additional enrichment and responds to the findings from threat hunting.

Verdict Handling:
- Handles false positives identified during the investigation.
- Handles true positives by initiating appropriate response actions.

---
Cortex XDR Alerts HandlingDeprecated. Use Cortex XDR - Alerts Handling v2 instead. When using the v2 version, enabling globally shared context for that playbook is required because outputs are no longer declared.
Cortex XDR Alerts Handling CTFThis playbook is used to loop over every alert in a Cortex XDR incident.
Supported alert categories:
- Malware
- Port Scan.
Cortex XDR Alerts Handling v2This playbook is used to loop over every alert in a Cortex XDR incident.
Supported alert categories:
- Malware
- Port Scan
- Cloud Cryptojacking
- Cloud Token Theft
- RDP Brute-Force
- First SSO Access
- Cloud IAM User Access Investigation
- Identity Analytics
Cortex XDR device control violationsQueries Cortex XDR for device control violations for the specified hosts, IP address, or XDR endpoint ID. It then communicates via email with the involved users to understand the nature of the incident and if the user connected the device.
All the collected data will be displayed in the XDR device control incident layout.
This playbook can also be associated with Cortex XDR device control violation job to periodically query and investigate XDR device control violations. In this configuration, the playbook will only communicate with the involved users.
Cortex XDR disconnected endpointsA Job to periodically query disconnected Cortex XDR endpoints with a provided last seen time range playbook input.
The Collected data, if found will be generated to a CSV report, including a detailed list of the disconnected endpoints.
The report will be sent to the recipient's provided email addresses in the playbook input.
The playbook includes an incident type with a dedicated layout to visualize the collected data.
To set the job correctly, you will need to.
1. Create a new recurring job.
2. Set the recurring schedule.
3. Add a name.
4. Set type to Cortex XDR disconnected endpoints.
5. Set this playbook as the job playbook.

https://xsoar.pan.dev/docs/incidents/incident-jobs

The scheduled run time and the timestamp relative date should be identical,
If the job is recurring every 7 days, the time range should be 7 days as well.
Cortex XDR Incident HandlingDeprecated. Use `Cortex XDR incident handling v3` instead. This playbook is triggered by fetching a Palo Alto Networks Cortex XDR incident.
The playbook syncs and updates new XDR alerts that construct the incident. It enriches indicators using Threat Intelligence integrations and Palo Alto Networks AutoFocus. The incident's severity is then updated based on the indicators reputation and an analyst is assigned for manual investigation. If chosen, automated remediation with Palo Alto Networks FireWall is initiated. After a manual review by the SOC analyst, the XDR incident is closed automatically.

*** Note - The XDRSyncScript used by this playbook sets data in the XDR incident fields that were released to content from the Demisto server version 5.0.0.
For Demisto versions under 5.0.0, please follow the 'Palo Alto Networks Cortex XDR' documentation to upload the new fields manually.
Cortex XDR incident handling v2Deprecated. Use `Cortex XDR incident handling v3` instead. This playbook is triggered by fetching a Palo Alto Networks Cortex XDR incident.
The playbook syncs and updates new XDR alerts that construct the incident and triggers a sub-playbook to handle each alert by type.
Then, the playbook performs enrichment on the incident's indicators and hunting for related IOCs.
Based on the severity, it lets the analyst decide whether to continue to the remediation stage or close the investigation as a false positive.
After the remediation, if there are no new alerts, the playbook stops the alert sync and closes the XDR incident and investigation.
Cortex XDR incident handling v3This playbook is triggered by fetching a Palo Alto Networks Cortex XDR incident.
The playbook syncs and updates new XDR alerts that construct the incident and triggers a sub-playbook to handle each alert by type.
Then, the playbook performs enrichment on the incident’s indicators and hunts for related IOCs.
Based on the severity, it lets the analyst decide whether to continue to the remediation stage or close the investigation as a false positive.
After the remediation, if there are no new alerts, the playbook stops the alert sync and closes the XDR incident and investigation. For performing the bidirectional sync, the playbook uses the incoming and outgoing mirroring feature added in XSOAR version 6.0.0. After the Calculate Severity - Generic v2 sub-playbook’s run, Cortex XSOAR will be treated as the single source of truth for the severity field, and it will sync only from Cortex XSOAR to XDR, so manual changes for the severity field in XDR will not update in the XSOAR incident.
Cortex XDR incident handling v3 CTFThis playbook is triggered by fetching a Palo Alto Networks Cortex XDR incident.
The playbook syncs and updates new XDR alerts that construct the incident and triggers a sub-playbook to handle each alert by type.
Then, the playbook performs enrichment on the incident’s indicators and hunts for related IOCs.
Based on the severity, it lets the analyst decide whether to continue to the remediation stage or close the investigation as a false positive.
After the remediation, if there are no new alerts, the playbook stops the alert sync and closes the XDR incident and investigation. For performing the bidirectional sync, the playbook uses the incoming and outgoing mirroring feature added in XSOAR version 6.0.0. After the Calculate Severity - Generic v2 sub-playbook’s run, Cortex XSOAR will be treated as the single source of truth for the severity field, and it will sync only from Cortex XSOAR to XDR, so manual changes for the severity field in XDR will not update in the XSOAR incident.
Cortex XDR Incident SyncDeprecated. No available replacement. Compares incidents in Palo Alto Networks Cortex XDR and Cortex XSOAR, and updates the incidents appropriately. When an incident is updated in Cortex XSOAR, the XDRSyncScript will update the incident in XDR. When an incident is updated in XDR, the XDRSyncScript will update the incident fields in Cortex XSOAR and rerun the current playbook. Do not use this playbook when enabling the incident mirroring feature added in XSOAR version 6.0.0.
Cortex XDR IOCs - Disable expired IOCs in XDRThis is a sub-playbook of "Cortex XDR IOCs - Push new IOCs to XDR (Main)". This playbook disables indicators in Cortex XDR after they expire from Cortex XSOAR using a loop and querying on the "xdr_pushed" tag.
Cortex XDR IOCs - Push new IOCs to XDRThis is a sub-playbook of "Cortex XDR IOCs - Push new IOCs to XDR - Main" and should not be run on its own. This sub-playbook retrieves IOCs according to the users query input (passed from the main playbook) and pushes them into Cortex XDR, and marks them as "xdr_pushed" or "xdr_not_processed" for further processing.
Cortex XDR IOCs - Push new IOCs to XDR (Main)This is the main playbook for Cortex XDR IOCs sync. The playbook will "sync" IOCs into Cortex XDR by pushing new IOCs in and disabling expired IOCs. The playbook utilizes Cortex XSOAR tags and loops in order to find IOCs using a query provided by the user. The playbook will iterate over the IOCs pushing them in batches into Cortex XDR. In the second phase, the playbook will disable expired IOCs that were previously pushed into Cortex XDR. We recommend running this playbook as a job a twice a day after disabling the integration sync function.
Cortex XDR Lite - Incident HandlingThe Cortex XDR Lite - Incident Handling playbook is triggered by fetching a Palo Alto Networks Cortex XDR incident and executes the following:

Analysis:
- Enriches all the indicators from XDR incidents and alerts, providing additional context and information about these indicators.

Investigation:
- Checks for related XDR alerts to the user and the endpoint by Mitre tactics to identify malicious activity.
- Checks for specific arguments for malicious usage from the command line.

Verdict:
- Determines the incident's verdict by considering indicator enrichment results, user and host risk levels, command line analysis, and the number of related XDR alerts (medium severity or higher) to the user and the endpoint by Mitre tactics.

Verdict Handling:
- Handles malicious incidents by initiating appropriate response actions, including blocking malicious indicators, isolating endpoints, and disabling user accounts.

To utilize this playbook as the default for handling XDR incidents, the classifier should be empty, and the selected incident type should be `Cortex XDR - Lite`.
The selected Mapper (incoming) should be `XDR - Incoming Mapper`, and the selected Mapper (outgoing) should be Cortex `XDR - Outgoing Mapper`.
Cortex XDR Malware - Incident EnrichmentThis playbook is part of the 'Malware Investigation And Response' pack. For more information, refer to https://xsoar.pan.dev/docs/reference/packs/malware-investigation-and-response.
This playbook enriches the Cortex XDR incident. The enrichment is done on the involved endpoint and Mitre technique ID information, and sets the 'Malware-Investigation and Response' layout.
Cortex XDR Malware - Investigation And ResponseThis playbook is part of the 'Malware Investigation And Response' pack. For more information, refer to https://xsoar.pan.dev/docs/reference/packs/malware-investigation-and-response.
This playbook investigates Cortex XDR malware incidents. It uses:
- Cortex XDR insights
- Command Line Analysis
- Dedup
- Sandbox hash search and detonation
- Cortex XDR enrichment
- Incident Handling (True/False Positive).
Cortex XDR Remote PsExec with LOLBIN command execution alertThe "Remote PsExec-like LOLBIN Command Execution" playbook is designed to address and respond to alerts indicating suspicious activities related to remote PsExec-like LOLBIN command execution from an unsigned non-standard source.
The playbook aims to efficiently:
- Get the alert data and check if the execution is blocked. If not will terminate the process (manually by default).
- Enrich any entities and indicators from the alert and find any related campaigns.
- Perform command analysis to provide insights and a verdict for the executed command.
- Perform further endpoint investigation using Cortex XDR.
- Checks for any malicious verdicts found to raise the severity of the alert.
- Perform automatic/manual remediation response by blocking any malicious indicators found.
The playbook is designed to run as a sub-playbook in "Cortex XDR Incident Handling - v3 & Cortex XDR Alerts Handling".
It depends on the data from the parent playbooks and cannot be used as a standalone version.
Courses of Action - CollectionThis playbook handles MITRE ATT&CK Techniques using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified techniques, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).

Techniques Handled:
- T1005 - Data from Local System
- Kill Chain phase:
- Collection

MITRE ATT&CK Description:
The adversary is attempting to gather data of interest to accomplish their goal.

Collection consists of techniques adversaries may use to gather information and the sources information is collected from that are relevant to following through on the adversary’s objectives. Frequently, the next goal after collecting data is to steal (exfiltrate) the data. Common target sources include various drive types, browsers, audio, video, and email. Common collection methods include capturing screenshots and keyboard input.

Possible playbook triggers:
- The playbook can be used as a part of the “Courses of Action - Collection” playbook to remediate techniques based on kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, that can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
Courses of Action - Command and ControlThis playbook handles MITRE ATT&CK Techniques using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team. It utilizes each of the sub-playbooks for specific techniques that belong to this phase (tactic) according to the MITRE ATT&CK kill chain. The sub-playbook called depends on the technique input.

***Disclaimer: This playbook does not simulate an attack using the specified techniques, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).

Tactic:
- TA0011: command and control

MITRE ATT&CK Description:
The adversary is trying to communicate with compromised systems to control them.

Command and Control consists of techniques that adversaries may use to communicate with systems under their control within a victim network. Adversaries commonly attempt to mimic normal, expected traffic to avoid detection. There are many ways an adversary can establish command and control with various levels of stealth depending on the victim’s network structure and defenses.

Possible playbook triggers:
- The playbook can be used as a part of the “Courses of Action - Collection” playbook to remediate techniques based on kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, that can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
Courses of Action - Credential AccessThis playbook handles MITRE ATT&CK Techniques using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team. It utilizes each of the sub-playbooks for specific techniques that belong to this phase (tactic) according to the MITRE ATT&CK kill chain. The sub-playbook called depends on the technique input.

***Disclaimer: This playbook does not simulate an attack using the specified techniques, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).

Tactic:
- TA0006: Credential Access

MITRE ATT&CK Description:
The adversary is trying to steal account names and passwords.

Credential Access consists of techniques for stealing credentials like account names and passwords. Techniques used to get credentials include keylogging or credential dumping. Using legitimate credentials can give adversaries access to systems, make them harder to detect, and provide the opportunity to create more accounts to help achieve their goals.

Possible playbook triggers:
- The playbook can be used as a part of the “Courses of Action - Collection” playbook to remediate techniques based on kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, that can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
Courses of Action - Defense EvasionThis playbook handles MITRE ATT&CK Techniques using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team. It utilizes each of the sub-playbooks for specific techniques that belong to this phase (tactic) according to the MITRE ATT&CK kill chain. The sub-playbook called depends on the technique input.

***Disclaimer: This playbook does not simulate an attack using the specified techniques, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).

Tactic:
- TA0005: Defense Evasion

MITRE ATT&CK Description:
The adversary is trying to avoid being detected.

Defense Evasion consists of techniques that adversaries use to avoid detection throughout their compromise. Techniques used for defense evasion include uninstalling/disabling security software or obfuscating/encrypting data and scripts. Adversaries also leverage and abuse trusted processes to hide and masquerade their malware. Other tactics’ techniques are cross-listed here when those techniques include the added benefit of subverting defenses.

Possible playbook triggers:
- The playbook can be used as a part of the “Courses of Action - Collection” playbook to remediate techniques based on kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, that can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
Courses of Action - DiscoveryThis playbook handles MITRE ATT&CK Techniques using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team. It utilizes each of the sub-playbooks for specific techniques that belong to this phase (tactic) according to the MITRE ATT&CK kill chain. The sub-playbook called depends on the technique input.

***Disclaimer: This playbook does not simulate an attack using the specified techniques, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).

Tactic:
- TA0007: Discovery

MITRE ATT&CK Description:
The adversary is trying to figure out your environment.

Discovery consists of techniques an adversary may use to gain knowledge about the system and internal network. These techniques help adversaries observe the environment and orient themselves before deciding how to act. They also allow adversaries to explore what they can control and what’s around their entry point in order to discover how it could benefit their current objective. Native operating system tools are often used toward this post-compromise information-gathering objective.

Possible playbook triggers:
- The playbook can be used as a part of the “Courses of Action - Collection” playbook to remediate techniques based on kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, that can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
Courses of Action - ExecutionThis playbook handles MITRE ATT&CK Techniques using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team. It utilizes each of the sub-playbooks for specific techniques that belong to this phase (tactic) according to the MITRE ATT&CK kill chain. The sub-playbook called depends on the technique input.

***Disclaimer: This playbook does not simulate an attack using the specified techniques, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).

Tactic:
- TA0002: Execution

MITRE ATT&CK Description:
The adversary is trying to run malicious code.

Execution consists of techniques that result in adversary-controlled code running on a local or remote system. Techniques that run malicious code are often paired with techniques from all other tactics to achieve broader goals, like exploring a network or stealing data. For example, an adversary might use a remote access tool to run a PowerShell script that does Remote System Discovery.

Possible playbook triggers:
- The playbook can be used as a part of the “Courses of Action - Collection” playbook to remediate techniques based on kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, that can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
Courses of Action - ExfiltrationThis playbook handles MITRE ATT&CK Techniques using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team. It utilizes each of the sub-playbooks for specific techniques that belong to this phase (tactic) according to the MITRE ATT&CK kill chain. The sub-playbook called depends on the technique input.

***Disclaimer: This playbook does not simulate an attack using the specified techniques, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).

Tactic:
- TA0010: Exfiltration

MITRE ATT&CK Description:
The adversary is trying to steal data.

Exfiltration consists of techniques that adversaries may use to steal data from your network. Once they’ve collected data, adversaries often package it to avoid detection while removing it. This can include compression and encryption. Techniques for getting data out of a target network typically include transferring it over their command and control channel or an alternate channel and may also include putting size limits on the transmission.

Possible playbook triggers:
- The playbook can be used as a part of the “Courses of Action - Collection” playbook to remediate techniques based on kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, that can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
Courses of Action - ImpactThis playbook handles MITRE ATT&CK Techniques using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team. It utilizes each of the sub-playbooks for specific techniques that belong to this phase (tactic) according to the MITRE ATT&CK kill chain. The sub-playbook called depends on the technique input.

***Disclaimer: This playbook does not simulate an attack using the specified techniques, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).

Tactic:
- TA0040: Impact

MITRE ATT&CK Description:
The adversary is trying to manipulate, interrupt, or destroy your systems and data.

Impact consists of techniques that adversaries use to disrupt availability or compromise integrity by manipulating business and operational processes. Techniques used for impact can include destroying or tampering with data. In some cases, business processes can look fine, but may have been altered to benefit the adversaries’ goals. These techniques might be used by adversaries to follow through on their end goal or to provide cover for a confidentiality breach.

Possible playbook triggers:
- The playbook can be used as a part of the “Courses of Action - Collection” playbook to remediate techniques based on kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, that can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
Courses of Action - Initial AccessThis playbook handles MITRE ATT&CK Techniques using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team. It utilizes each of the sub-playbooks for specific techniques that belong to this phase (tactic) according to the MITRE ATT&CK kill chain. The sub-playbook called depends on the technique input.

***Disclaimer: This playbook does not simulate an attack using the specified techniques, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).

Tactic:
- TA0001: Initial Access

MITRE ATT&CK Description:
The adversary is trying to get into your network.

Initial Access consists of techniques that use various entry vectors to gain their initial foothold within a network. Techniques used to gain a foothold include targeted spearphishing and exploiting weaknesses on public-facing web servers. Footholds gained through initial access may allow for continued access, like valid accounts and use of external remote services, or may be limited-use due to changing passwords.

Possible playbook triggers:
- The playbook can be used as a part of the “Courses of Action - Collection” playbook to remediate techniques based on kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, that can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
Courses of Action - Lateral MovementThis playbook handles MITRE ATT&CK Techniques using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team. It utilizes each of the sub-playbooks for specific techniques that belong to this phase (tactic) according to the MITRE ATT&CK kill chain. The sub-playbook called depends on the technique input.

***Disclaimer: This playbook does not simulate an attack using the specified techniques, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).

Tactic:
- TA0008: Lateral Movement

MITRE ATT&CK Description:
The adversary is trying to move through your environment.

Lateral Movement consists of techniques that adversaries use to enter and control remote systems on a network. Following through on their primary objective often requires exploring the network to find their target and subsequently gaining access to it. Reaching their objective often involves pivoting through multiple systems and accounts to gain. Adversaries might install their own remote access tools to accomplish Lateral Movement or use legitimate credentials with native network and operating system tools, which may be stealthier.

Possible playbook triggers:
- The playbook can be used as a part of the “Courses of Action - Collection” playbook to remediate techniques based on kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, that can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
Courses of Action - PersistenceThis playbook handles MITRE ATT&CK Techniques using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team. It utilizes each of the sub-playbooks for specific techniques that belong to this phase (tactic) according to the MITRE ATT&CK kill chain. The sub-playbook called depends on the technique input.

***Disclaimer: This playbook does not simulate an attack using the specified techniques, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).

Tactic:
- TA0003: Persistence

MITRE ATT&CK Description:
The adversary is trying to maintain their foothold.

Persistence consists of techniques that adversaries use to keep access to systems across restarts, changed credentials, and other interruptions that could cut off their access. Techniques used for persistence include any access, action, or configuration changes that let them maintain their foothold on systems, such as replacing or hijacking legitimate code or adding startup code.

Possible playbook triggers:
- The playbook can be used as a part of the “Courses of Action - Collection” playbook to remediate techniques based on kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, that can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
Courses of Action - Privilege EscalationThis playbook handles MITRE ATT&CK Techniques using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team. It utilizes each of the sub-playbooks for specific techniques that belong to this phase (tactic) according to the MITRE ATT&CK kill chain. The sub-playbook called depends on the technique input.

***Disclaimer: This playbook does not simulate an attack using the specified techniques, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).

Tactic:
- TA0004: Privilege Escalation

MITRE ATT&CK Description:
The adversary is trying to gain higher-level permissions.

Privilege Escalation consists of techniques that adversaries use to gain higher-level permissions on a system or network. Adversaries can often enter and explore a network with unprivileged access but require elevated permissions to follow through on their objectives. Common approaches are to take advantage of system weaknesses, misconfigurations, and vulnerabilities. Examples of elevated access include: • SYSTEM/root level• local administrator• user account with admin-like access • user accounts with access to specific system or perform specific functionThese techniques often overlap with Persistence techniques, as OS features that let an adversary persist can execute in an elevated context.

Possible playbook triggers:
- The playbook can be used as a part of the “Courses of Action - Collection” playbook to remediate techniques based on kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, that can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
Create Jira IssueCreate Jira issue allows you to open new issues.
When creating the issue, you can decide to update based on on the issue's state, which will wait for the issue to resolve or close with StatePolling.
Alternatively, you can select to mirror the Jira issue and incident fields. To apply either of these options, set the SyncTicket value in the playbook inputs to one of the following options:
1. StatePolling
2. Mirror
3. Leave Blank to use none

When creating Jira issues through XSOAR, using the mirroring function, make sure that you exclude those issues when fetching incidents. To exclude these issues, tag the relevant issues with a dedicated label and exclude that label from the JQL query (Labels!=).
Create Jira Ticket - XM CyberXM Cyber generates a Jira ticket based on the trend in the Security Score
Create list for PTHThis playbook help analysts creating a new list of domains to monitor using CertStream integration.
Create ServiceNow TicketCreate ServiceNow Ticket allows you to open new tickets as a task from a parent playbook.
When creating the ticket, you can decide to update based on on the ticket's state, which will wait for the ticket to resolve or close with StatePolling.
Alternatively, you can select to mirror the ServiceNow ticket and incident fields. To apply either of these options, set the SyncTicket value in the playbook inputs to one of the following options:
1. StatePolling
2. Mirror
3. Leave Blank to use none.
CrowdStrike Endpoint EnrichmentDeprecated. Use CrowdStrike Falcon instead.
CrowdStrike Falcon - Block FileThis playbook receives an MD5 or a SHA256 hash and adds it to the block list in CrowdStrike Falcon.
The playbook uses the integration "CrowdStrike Falcon".
CrowdStrike Falcon - False Positive Incident HandlingThis playbook is part of the 'Malware Investigation And Response' pack. For more information, refer to https://xsoar.pan.dev/docs/reference/packs/malware-investigation-and-response.
This playbook handles a CrowdStrike incident that was determined
to be a false positive by the analyst. Actions include unisolating the host, allowing
the indicator by the EDR, and tagging it.
CrowdStrike Falcon - Get Detections by IncidentThis playbook is part of the 'Malware Investigation And Response' pack. For more information, refer to https://xsoar.pan.dev/docs/reference/packs/malware-investigation-and-response.
This playbook enables getting CrowdStrike Falcon detection details based on the CrowdStrike incident ID.
CrowdStrike Falcon - Get Endpoint Forensics DataThis playbook is part of the 'Malware Investigation And Response' pack. For more information, refer to https://xsoar.pan.dev/docs/reference/packs/malware-investigation-and-response.
This playbook extracts data from the host using RTR commands. For example, commands for getting a list of running processes and network connections.
Crowdstrike Falcon - Isolate EndpointThis playbook will auto isolate endpoints by the device ID that was provided in the playbook.
CrowdStrike Falcon - Retrieve FileThis playbook is part of the 'Malware Investigation And Response' pack. For more information, refer to https://xsoar.pan.dev/docs/reference/packs/malware-investigation-and-response.
This playbook retrieves and unzips files from CrowdStrike Falcon and returns a list of the files that were and were not retrieved.
CrowdStrike Falcon - Search Endpoints By HashThis playbook is part of the 'Malware Investigation And Response' pack. For more information, refer to https://xsoar.pan.dev/docs/reference/packs/malware-investigation-and-response.
This playbook searches across the organization for other endpoints associated with a specific SHA256/MD5/SHA1 hash.
CrowdStrike Falcon - SIEM ingestion Get Incident DataThis playbook is part of the 'Malware Investigation And Response' pack. For more information, refer to https://xsoar.pan.dev/docs/reference/packs/malware-investigation-and-response.
This playbook handles incident ingestion from a SIEM.
The user provides the field for the incident ID or detection ID and the field indicating whether the ingested item is an incident or detection. This playbook enables changing the severity scale in Cortex XSOAR as well as fetching CrowdStrike detections based on the CrowdStrike incident type.
CrowdStrike Falcon - True Positive Incident HandlingThis playbook is part of the 'Malware Investigation And Response' pack. For more information, refer to https://xsoar.pan.dev/docs/reference/packs/malware-investigation-and-response. This playbook handles a CrowdStrike incident that was determined to be a true positive by the analyst. Actions include isolating the host, blocking the indicator by the EDR, and tagging it.
Crowdstrike Falcon - Unisolate EndpointThis playbook unisolates devices according to the device ID that is provided in the playbook input.
CrowdStrike Falcon Intelligence Sandbox Detonate and Analyze FileThis playbook uploads, detonates, and analyzes files for the CrowdStrike Falcon Intelligence Sandbox.
CrowdStrike Falcon Malware - Incident EnrichmentThis playbook is part of the 'Malware Investigation And Response' pack. For more information, refer to https://xsoar.pan.dev/docs/reference/packs/malware-investigation-and-response.
This playbook enables enriching CrowdStrike Falcon incidents by pivoting to their detections as well as mapping all the relevant data to the Cortex XSOAR incident fields.
CrowdStrike Falcon Malware - Investigation and Response This playbook is part of the 'Malware Investigation And Response' pack. For more information, refer to https://xsoar.pan.dev/docs/reference/packs/malware-investigation-and-response. This playbook handles a CrowdStrike Falcon malware investigation, including:
- Extracting and displaying MITRE data from the EDR and sandboxes
- Deduplicating similar incidents
- Searching for hashes in an alert in a sandbox to provide their relevant information. If the hashes are not found, retrieving them from the endpoint and detonating them in the sandbox.
- Verifying the actions taken by the EDR
- Analyzing the command line
- Searching for relevant hashes in additional hosts in the organization
- Retrieving data about the host, including process list and network connections
- Performing containment and mitigation actions as part of handling false/true positives
- Setting the relevant layouts
CrowdStrike Falcon Malware - Verify Containment ActionsThis playbook is part of the 'Malware Investigation And Response' pack. For more information, refer to https://xsoar.pan.dev/docs/reference/packs/malware-investigation-and-response.
This playbook verifies and sets the policy actions applied by CrowdStrike Falcon.
CrowdStrike Falcon Sandbox - Detonate fileDeprecated. Use the cs-falcon-sandbox-submit-file command with polling=true instead.
CrowdStrike Rapid IOC HuntingDeprecated. Use "CrowdStrike Rapid IOC Hunting v2" playbook instead. Hunt for endpoint activity involving hash and domain IOCs, using Crowdstrike Falcon Host.\nAlso use AnalystEmail label to determine where to send an email alert if something is found.
CrowdStrike Rapid IOC Hunting v2Deprecated. Use CrowdStrike Falcon instead.
CTF 1 - Get to know XSOAR8Get to know XSOAR 8 - Run this playbook and follow the questions.
CTF 2 - Classify an incident - RDP Brute forceClassify an RDP Brute Force Incident - Run this playbook and follow the questions.
CTF-XNot so easy...
CVE Enrichment - GenericDeprecated. Use "CVE Enrichment - Generic v2" playbook instead. Enrich CVE using one or more integrations.
CVE Enrichment - Generic v2This playbook performs CVE Enrichment using the following integrations:
- VulnDB
- CVE Search
- IBM X-Force Exchange
CVE Exposure - RiskSenseBlock IPs and apply the tag to assets that are vulnerable to the specified CVE.
CVE-2021-22893 - Pulse Connect Secure RCEOn April 20th, a new Remote Code Execution vulnerability in Pulse Connect Secure was disclosed.
The reference number for the vulnerability is CVE-2021-22893 with the CVSS Score of 10.0.
This playbook should be trigger manually and includes the following tasks:

Enrich related known CVEs and Malware Hashes used by the suspected APT actor.
Search for unpatched endpoints vulnerable to the exploits.
Search network facing system using Expanse for relevant issues.
Indicators and known webshells hunting using SIEM products.
Block indicators automatically or manually.
Provide different mitigations that has been publicly published such as:
Patches
Workarounds
* Yara and Snort Rules

Note: This is a beta playbook, which lets you implement and test pre-release software. Since the playbook is beta, it might contain bugs. Updates to the pack during the beta phase might include non-backward compatible features. We appreciate your feedback on the quality and usability of the pack to help us identify issues, fix them, and continually improve.

More information:
Exploitation of Pulse Connect Secure Vulnerabilities
CVE-2021-34527 | CVE-2021-1675 - PrintNightmareThe playbook can be triggered manually or automatically by setting up a reoccurring job.

Microsoft has released a security update in June 2021 Patch Tuesday for CVE-2021-1675, a Local Privilege Escalation vulnerability in the Print Spooler Service. Later that month, researchers found another method to exploit the Print Spooler service remotely, which raised the severity of the vulnerability due to the fact that the new method allows Remote Code Execution, a new ID was given to the critical vulnerability - CVE-2021-34527.

Microsoft patched the vulnerability in June but an exploit POC and complete technical analysis were made publicly available online.

Update 7.8.2021 - Microsoft has released an emergency patch for the PrintNightmare. A reference for the patch can be found in "Install Microsoft spooler service patches" task.

This playbook includes the following tasks:
- Manual actions to mitigate the exploit
- Search Vulnerable Devices using the CVE
- Query SIEM, FW, XDR to detect malicious activity and compromised hosts
- Run Dedicated Detection and Response playbook for Cortex XDR

More details on the vulnerabilities:
CVE-2021-1675 LPE
CVE-2021-34527 RCE

Note: This is a beta playbook, which lets you implement and test pre-release software. Since the playbook is beta, it might contain bugs. Updates to the pack during the beta phase might include non-backward compatible features. We appreciate your feedback on the quality and usability of the pack to help us identify issues, fix them, and continually improve.
CVE-2021-40444 - MSHTML RCECVE-2021-4044 refers to the MSHTML engine, that has been found vulnerable to arbitrary code execution by a specially crafted Microsoft Office document or rich text format file.

Mitigations:
Microsoft official patch addressing CVE-2021-40444
Several workarounds suggested by Microsoft.

Researchers have validated this attack triggered in Windows Explorer with “Preview Mode” enabled, even in just a rich-text format RTF file (not an Office file and without ActiveX). This indicates it can be exploited even without opening the file and this invalidates Microsoft’s workaround mitigation mentioned above.

This playbook should be trigger manually and includes the following tasks:

Collect related known indicators from several sources.
Indicators, Files and Process creation patterns hunting using PAN-OS, Cortex XDR and SIEM products.
Block indicators automatically or manually.
Provide workarounds and detection capabilities.
* Microsoft official CVE-2021-40444 patch.

More information:
Microsoft MSHTML Remote Code Execution Vulnerability

Note: This is a beta playbook, which lets you implement and test pre-release software. Since the playbook is beta, it might contain bugs. Updates to the pack during the beta phase might include non-backward compatible features. We appreciate your feedback on the quality and usability of the pack to help us identify issues, fix them, and continually improve.
CVE-2021-44228 - Log4j RCECritical RCE Vulnerability: log4j - CVE-2021-44228

On Dec. 9, 2021, a remote code execution (RCE) vulnerability in Apache log4j 2 was identified being exploited in the wild. Public proof of concept (PoC) code was released and subsequent investigation revealed that exploitation was incredibly easy to perform.

On Dec. 14 2021, another vulnerability was discovered related the log4j 0-day exploit known as CVE-2021-45046.

On Dec 18 2021, yet another vulnerability was discovered related the log4j 0-day exploit known as CVE-2021-45105 that allows an attacker with control over Thread Context Map data to cause a denial of service when a crafted string is interpreted. This issue was fixed in Log4j 2.17.0 and 2.12.3.

On Dec 28 2021, another RCE vulnerability was published for Apache Log4j2, versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4).
In order to exploit this vulnerability, an attacker with permission to modify the logging configuration file can construct a malicious configuration using a JDBC Appender with a data source referencing a JNDI URI which can execute remote code. This issue is fixed by limiting JNDI data source names to the java protocol in Log4j2 versions 2.17.1, 2.12.4, and 2.3.2.

Affected Version

Apache Log4j 2.x <= 2.17.0

This playbook should be triggered manually or can be configured as a job.
Please create a new incident and choose the CVE-2021-44228 - Log4j RCE playbook and Rapid Breach Response incident type.

The playbook includes the following tasks:

Collect related known indicators from several sources.
Indicators and exploitation patterns hunting using PAN-OS, Cortex XDR and SIEM products.
Search for possible vulnerable servers using Xpanse and Prisma Cloud.
Block indicators automatically or manually.

Mitigations:
Apache official CVE-2021-44228 patch.
Unit42 recommended mitigations.
Detection Rules.
Snort
Suricata
Sigma
Yara
Zeek Intel

More information:
Apache Log4j Vulnerability Is Actively Exploited in the Wild (CVE-2021-44228)

Note: This is a beta playbook, which lets you implement and test pre-release software. Since the playbook is beta, it might contain bugs. Updates to the pack during the beta phase might include non-backward compatible features. We appreciate your feedback on the quality and usability of the pack to help us identify issues, fix them, and continually improve.
CVE-2022-26134 - Confluence RCEAtlassian has been made aware of the current active exploitation of a critical severity unauthenticated remote code execution vulnerability in Confluence Data Center and Server. The OGNL injection vulnerability allows an unauthenticated user to execute arbitrary code on a Confluence Server or Data Center instance.

All versions of Confluence Server and Data Center prior to the fixed versions listed above are affected by this vulnerability.

Atlassian has released the following versions to address this issue:

Released versions 7.4.17, 7.13.7, 7.14.3, 7.15.2, 7.16.4, 7.17.4, and 7.18.1 which contain a fix for this issue.

This playbook includes the following tasks:

Collect detection rules.
Exploitation patterns & IoCs hunting using PANW Next-Generation Firewalls and 3rd party SIEM products.
Cortex Xpanse policies coverage.
Provides Atlassian workarounds and patched versions.

More information:

Threat Brief: Atlassian Confluence Remote Code Execution Vulnerability (CVE-2022-26134)

Confluence Security Advisory 2022-06-02

Note: This is a beta playbook, which lets you implement and test pre-release software. Since the playbook is beta, it might contain bugs. Updates to the pack during the beta phase might include non-backward compatible features. We appreciate your feedback on the quality and usability of the pack to help us identify issues, fix them, and continually improve.
CVE-2022-30190 - MSDT RCEOn May 27th, a new Microsoft Office Zero-Day was discovered by Nao_sec.

The new Zero-Day is a remote code execution vulnerability that exists when MSDT is called using the URL protocol from a calling application such as Word.

On May 30th, Microsoft assigned CVE-2022-30190 to the MSDT vulnerability, aka Follina vulnerability.

This playbook includes the following tasks:

Collect detection rules.
Exploitation patterns hunting using Cortex XDR - XQL Engine and 3rd party SIEM products.
Cortex XDR BIOCs coverage.
Provides Microsoft workarounds and detection capabilities.

More information:

Guidance for CVE-2022-30190 Microsoft Support Diagnostic Tool Vulnerability


Note: This is a beta playbook, which lets you implement and test pre-release software. Since the playbook is beta, it might contain bugs. Updates to the pack during the beta phase might include non-backward compatible features. We appreciate your feedback on the quality and usability of the pack to help us identify issues, fix them, and continually improve.
CVE-2022-3786 & CVE-2022-3602 - OpenSSL X.509 Buffer OverflowsOn November 1, OpenSSL released a security advisory describing two high severity vulnerabilities within the OpenSSL library, CVE-2022-3786 and CVE-2022-3602. OpenSSL versions from 3.0.0 - 3.0.6 are vulnerable, with 3.0.7 containing the patch for both vulnerabilities. OpenSSL 1.1.1 and 1.0.2 are not affected by this issue.

The vulnerability described in CVE-2022-3602 allows an attacker to obtain a 4-byte overflow on the stack by crafting a malicious email address within the attacker-controlled certificate. The overflow will result in a crash (most likely scenario) or potentially remote code execution (much less likely). In CVE-2022-3786, an attacker can achieve a stack overflow of arbitrary length by crafting a malicious email address within the attacker-controlled certificate.

Both vulnerabilities are “triggered through X.509 certificate verification, specifically, name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer.”

The playbook includes the following tasks:
Hunting for active processes running OpenSSL vulnerable versions using:
Cortex XDR
Splunk
Azure Sentinel
Cortex Xpanse
Prisma
PANOS

Mitigations:
OpenSSL official patch

More information:
Unit42 Threat Brief: CVE-2022-3786 and CVE-2022-3602: OpenSSL X.509 Buffer Overflows
NCSC-NL - OpenSSL overview Scanning software

Note: This is a beta playbook that lets you implement and test pre-release software. Since the playbook is beta, it might contain bugs. Updates to the pack during the beta phase might include non-backward compatible features. We appreciate your feedback on the quality and usability of the pack to help us identify issues, fix them, and continually improve.
CVE-2022-41040 & CVE-2022-41082 - ProxyNotShellUPDATE
A new method for bypassing ProxyNotShell mitigations was found after being seen exploited in the wild by the Play ransomware gang.
While the original exploit took advantage of the Autodiscover endpoint, the new exploit is using the OWA endpoint leading to SSRF.
The OWASSRF exploit method involves two different vulnerabilities tracked by CVE-2022-41080 and CVE-2022-41082 that allow remote code execution (RCE) via Outlook Web Access (OWA).

This playbook introduces several updates in response to the new discovery:
- Hunting:
- Detecting possibly successful exploitation of the OWA SSRF vulnerability.
- Mitigations:
- IIS URL Rewrite rule for the modified exploitation URI path.
- Remediation:
- Block Indicators - Generic v3 playbook.

Microsoft is investigating two reported zero-day vulnerabilities affecting Microsoft Exchange Server 2013, Exchange Server 2016, and Exchange Server 2019. The first one, identified as CVE-2022-41040, is a Server-Side Request Forgery (SSRF) vulnerability, and the second one, identified as CVE-2022-41082, allows Remote Code Execution (RCE) when PowerShell is accessible to the attacker.

Currently, Microsoft is aware of limited targeted attacks using these two vulnerabilities. In these attacks, CVE-2022-41040 can enable an authenticated attacker to remotely trigger CVE-2022-41082. It should be noted that authenticated access to the vulnerable Exchange Server is necessary to successfully exploit either vulnerability.

This playbook includes the following tasks:

Collect detection rules, indicators and mitigation tools.
Exploitation patterns hunting using Cortex XDR - XQL Engine.
Exploitation patterns hunting using 3rd party SIEM products:
Azure Sentinel
Splunk
QRadar
Elasticsearch
Indicators hunting using:
PAN-OS
Splunk
QRadar
Provides Microsoft mitigation and detection capabilities.

More information:

Threat Brief: OWASSRF Vulnerability Exploitation

Threat Brief: CVE-2022-41040 and CVE-2022-41082: Microsoft Exchange Server (ProxyNotShell)

References:

OWASSRF: CrowdStrike Identifies New Exploit Method for Exchange Bypassing ProxyNotShell Mitigations

Analyzing attacks using the Exchange vulnerabilities CVE-2022-41040 and CVE-2022-41082

Customer Guidance for Reported Zero-day Vulnerabilities in Microsoft Exchange Server

WARNING: NEW ATTACK CAMPAIGN UTILIZED A NEW 0-DAY RCE VULNERABILITY ON MICROSOFT EXCHANGE SERVER

ProxyNotShell— the story of the claimed zero days in Microsoft Exchange

Note: This is a beta playbook, which lets you implement and test pre-release software. Since the playbook is beta, it might contain bugs. Updates to the pack during the beta phase might include non-backward compatible features. We appreciate your feedback on the quality and usability of the pack to help us identify issues, fix them, and continually improve.
CVE-2023-23397 - Microsoft Outlook EoP### CVE-2023-23397 - Critical Elevation of Privilege vulnerability in Microsoft Outlook

#### Summary
Microsoft Threat Intelligence discovered limited, targeted abuse of a vulnerability in Microsoft Outlook for Windows that allows for new technology LAN manager (NTLM) credential theft. Microsoft has released CVE-2023-23397 to address the critical elevation of privilege (EoP) vulnerability affecting Microsoft Outlook for Windows. We strongly recommend all customers update Microsoft Outlook for Windows to remain secure.

#### Affected Products
All supported versions of Microsoft Outlook for Windows are affected. Other versions of Microsoft Outlook such as Android, iOS, Mac, as well as Outlook on the web and other M365 services are not affected.

#### Technical Details
CVE-2023-23397 is a critical EoP vulnerability in Microsoft Outlook that is triggered when an attacker sends a message with an extended MAPI property with a UNC path to an SMB (TCP 445) share on a threat actor-controlled server. No user interaction is required.

The threat actor is using a connection to the remote SMB server sends the user’s NTLM negotiation message, which the attacker can then relay for authentication against other systems that support NTLM authentication.

This playbook should be triggered manually or can be configured as a job.
Please create a new incident and choose the CVE-2023-23397 - Microsoft Outlook EoP playbook and Rapid Breach Response incident type.

The playbook includes the following tasks:

Hunting:
- Panorama Threat IDs
- Cortex XDR
- XQL hunting query
- BTP hunting
- Microsoft PowerShell hunting script
- Advanced SIEM hunting queries
- Indicators hunting
- Endpoint by CVE hunting

Mitigations:
- Cortex XDR Advanced API Monitoring
- Microsoft official CVE-2023-23397 patch
- Microsoft workarounds
- Detection Rules
- Yara

References:

Microsoft Mitigates Outlook Elevation of Privilege Vulnerability

CVE-2023-23397 Audit & Eradication Script

Neo23x0 Yara Rules

Note: This is a beta playbook, which lets you implement and test pre-release software. Since the playbook is beta, it might contain bugs. Updates to the pack during the beta phase might include non-backward compatible features. We appreciate your feedback on the quality and usability of the pack to help us identify issues, fix them, and continually improve.
CVE-2023-34362 - MOVEit Transfer SQL Injection### CVE-2023-34362 - Critical SQL Injection vulnerability in MOVEit Transfer.

#### Summary

A critical vulnerability has been identified in MOVEit Transfer, a managed file transfer solution. The vulnerability affects versions prior to the latest release and involves improper input validation. Exploiting this vulnerability can lead to remote execution of arbitrary code, potentially resulting in unauthorized access and compromise of sensitive data.

To mitigate the risk associated with this vulnerability, it is crucial for users to update to the latest version of MOVEit Transfer that includes necessary security patches.

#### Affected Products


| Affected Version | Fixed Version | Documentation |
|-------------------------------|---------------------------|-------------------------------------|
| MOVEit Transfer 2023.0.0 (15.0) | MOVEit Transfer 2023.0.1 | MOVEit 2023 Upgrade Documentation |
| MOVEit Transfer 2022.1.x (14.1) | MOVEit Transfer 2022.1.5 | MOVEit 2022 Upgrade Documentation |
| MOVEit Transfer 2022.0.x (14.0) | MOVEit Transfer 2022.0.4 | MOVEit 2022 Upgrade Documentation |
| MOVEit Transfer 2021.1.x (13.1) | MOVEit Transfer 2021.1.4 | MOVEit 2021 Upgrade Documentation |
| MOVEit Transfer 2021.0.x (13.0) | MOVEit Transfer 2021.0.6 | MOVEit 2021 Upgrade Documentation |
| MOVEit Transfer 2020.1.x (12.1) | Special Patch Available | See KB 000234559 |
| MOVEit Transfer 2020.0.x (12.0) or older | MUST upgrade to a supported version | See MOVEit Transfer Upgrade and Migration Guide |


This playbook should be triggered manually or can be configured as a job.

Please create a new incident and choose the CVE-2023-34362 - MOVEit SQL Injection playbook and Rapid Breach Response incident type.

The playbook includes the following tasks:

IoCs Collection
- Blog IoCs download
- Yara Rules download
- Sigma rules download

Hunting:
- Cortex XDR XQL exploitation patterns hunting
- Cortex Xpanse external facing instances hunting
- Advanced SIEM exploitation patterns hunting
- Indicators hunting

The hunting queries are searching for the following activities:
- ASPX file creation by w3wp.exe
- IIS compiling binaries via the csc.exe on behalf of the MOVEit
- Detects get requests to specific exploitation related files

Mitigations:
- Progress official CVE-2023-34362 patch
- Progress mitigation measures
- Detection Rules
- Yara
- Sigma


References:

CVE-2023-34362: MOVEit Transfer SQL Injection Vulnerability Threat Brief

MOVEit Transfer Critical Vulnerability (May 2023)

Note: This is a beta playbook, which lets you implement and test pre-release software. Since the playbook is beta, it might contain bugs. Updates to the pack during the beta phase might include non-backward compatible features. We appreciate your feedback on the quality and usability of the pack to help us identify issues, fix them, and continually improve.
CVE-2023-36884 - Microsoft Office and Windows HTML RCE## CVE-2023-36884 - Microsoft Office and Windows HTML RCE

Summary:

Microsoft recently detected a sophisticated phishing campaign orchestrated by a threat actor called Storm-0978. The targets of this campaign were defense and government organizations in Europe and North America. The attackers exploited the previously undisclosed CVE-2023-36884, introduced in July's recent Patch Tuesday release.

CVE-2023-36884 is affecting both Office and Windows. This zero-day vulnerability enables remote code execution through specially crafted Microsoft Office documents.

This playbook should be triggered manually or can be configured as a job.

Please create a new incident and choose the CVE-2023-36884 - Office and Windows HTML RCE playbook and Rapid Breach Response incident type.

The playbook includes the following tasks:

IoCs Collection
- Unit42 IoCs download

Hunting:
- PANW Hunting:
- Cortex XDR XQL exploitation patterns hunting
- Panorama Threat IDs hunting
- Advanced SIEM exploitation patterns hunting
- Indicators hunting
- Endpoints by CVE hunting

The hunting queries are searching for the following activities:
- Detects a Microsoft Office file drops a file called 'file001.url'.
- Suspicious New Instance Of An Office COM Object
- Change PowerShell Policies to an Insecure Level

`Please note that the threat hunting queries are related to the behavior identified as part of the exploitation patterns and may result in false positive detections.`

Mitigations:
- Microsoft mitigation measures

References:

CVE-2023-36884 - Microsoft Office and Windows HTML Remote Code Execution: Threat Brief
Storm-0978 attacks reveal financial and espionage motives
CyberArk - Brute Force_InvestigationThis playbook investigates a “Brute Force” incident by gathering user and IP information and performs remediation based on the information gathered and received from the user.

Used Sub-playbooks:
Enrichment for Verdict
Block IP - Generic v3
* Block Account - Generic v2

If you wish to link this playbook to the relevant alerts automatically, we recommend using the following filters when configuring the playbook triggers: Alert Source = Correlation AND Alert Name = CyberArk Failed Logins

CyberBlindspot Incident ManagementThis playbook runs the incidents through indicator enrichment, then based on the mirroring settings, it can communicate with the remote server to assist the user in the next course of action (Whether it be closing the incident, initiating the takedown of an online asset or simply waiting for a process on the remote server to end) to take on the incident if any.
Cybereason - Download Close FileThis playbook aborts a file download operation which is in progress based on the Malop ID and username provided.
Cybereason - Download FileThis playbook downloads a file from Cybereason platform, based on the Malop ID and username provided.
Cyberpion Domain StateAllows analyst to get basic information about the domain
CyberTotal Auto Enrichment - CyCraftThis playbook automatically enriches indicators (including IPs, URLs, domains; MD5, SHA-1, and SHA-256 file hashes). Playbook input: the indicators you want to enrich. Playbook output: detection engine results, positive detections, detection ratios; as well as severity, confidence, and threat scores.
CyberTotal Whois - CyCraftThis playbook is used to automatically retrieve Whois information regarding IPs, URLs and domains. Playbook input: IPs, URLs, domains. Playbook output: Whois lookup information.
Cyble Intel AlertThis is a playbook which will handle the alerts coming from the Cyble Events service
Cyble Vision Alert V2
Cyren Inbox Security DefaultProcesses Cyren Incidents, sets resolutions, and applies remediations to end-user mailboxes.
D2 - Endpoint data collectionUses Demisto's d2 agent to collect data from an endpoint for IR purposes.

Input:
Hostname (default: ${Endpoint.Hostname})
OS (default: windows)
Credentials (default: Admin)
Path (default: None)
Darkfeed - malware download from feedSet this playbook as an automated job in order to automatically download malware from new Darkfeed IOCs and run them through the "Darkfeed IOC detonation and proactive blocking" playbook
Darkfeed IOC detonation and proactive blockingDownload malicious files from a Darkfeed IOC, detonate them in automated sandboxes, and extract and block any additional indicators and files.
Darkfeed Threat hunting-researchAutomatically discover and enrich indicators with the same actor and source as the triggering IOC. Search for and isolate any compromised endpoints and proactively block IOCs from entering your network.
Darktrace Basic AI Analyst Event HandlerRuns a common AI Analyst workflow for fetched AI Analyst events.
Darktrace Basic Model Breach HandlerRuns a common Model Breach workflow for fetched Model breach alerts.
DBot Create Phishing ClassifierDeprecated. Use "DBot Create Phishing Classifier V2" playbook instead. Create a phishing classifier using machine learning technique, based on email content
DBot Create Phishing Classifier JobDeprecated. Use "DBot Create Phishing Classifier V2" playbook instead. Train the phishing machine learning model. This playbook should be used as job, to run repeatedly, for example every week.
DBot Create Phishing Classifier V2Create a phishing classifier using machine learning techniques, based on email content.
DBot Create Phishing Classifier V2 JobTrain the phishing machine learning model. This playbook should be used as job, to run repeatedly, for example every week.
DBot Indicator Enrichment - GenericGet indicators internal Dbot score
DeCYFIR - v1DeCYFIR API's provides External Threat Landscape Management insights.
Dedup - GenericDeprecated. Use "Dedup - Generic v2" playbook instead. This playbook identifies duplicate incidents using one of the supported methods.
Dedup - Generic v2Deprecated. Use the Dedup Generic v3 playbook instead. This playbook identifies duplicate incidents using one of the supported methods.
Dedup - Generic v3Deprecated. Use the `Dedup - Generic v4` playbook instead. This playbook identifies duplicate incidents using one of the supported methods.
Select one of the following methods to identify duplicate incidents in Cortex XSOAR.
- ml: Machine learning model, which is trained mostly on phishing incidents.
-rules: Rules help identify duplicate incidents when the logic is well defined, for example, the same label or custom fields.
-text: Statistics algorithm that compares text, which is generally useful for phishing incidents.
For each method, the playbook will search for the oldest similar incident. when there is a match for a similar incident the playbook will close the current incident and will link it to the older incident.
Dedup - Generic v4This playbook identifies duplicate incidents using the Cortex XSOAR machine learning method (script).
In this playbook, you can choose fields and/or indicators to be compared against other incidents in the Cortex XSOAR database.

Note: To identify similar incidents you must properly define the playbook inputs.
DeDup incidentsDeprecated. Check for duplicate incidents for the current incident, and close it if any duplicate has found.
DeDup incidents - MLDeprecated. Check for duplicate incidents for the current incident, and close it if any duplicate has been found by machine-learning find duplicates automation.
DeepL Translate Document
DefaultThis playbook executes when no other playbook is associated with an incident. It enriches indicators in an incident using one or more integrations.
Delete Custom ContentThis playbook deletes custom content from the system. It deletes Playbooks, Scripts, Layouts, Classifiers, Mappers, Incident Types and Incident Fields.
Demisto Self-Defense - Account policy monitoring playbookDeprecated. Get list of Demisto users through the REST API, and alert if any non-SAML user accounts are found.
Departing Employee Auto-AddQueries stand-down tickets from a ticketing system and passes relevant employee data to the Add Employees to Departing Employee Watchlist playbook. Intended to be run as a scheduled job.
Departing Employee Clean-UpQueries the Departing Employee watchlist in Code42 Incydr and passes relevant employee data to the Remove Employees from Departing Employee Watchlist playbook. Intended to be run as a scheduled job.
Detect & Manage Phishing CampaignsThis playbook is used to find, create and manage phishing campaigns. When a number of similar phishing incidents exist in the system, the playbook can be used to do the following:
1. Find and link related incidents to the same phishing attack (a phishing campaign).
2. Search for an existing Phishing Campaign incident, or create a new incident for the linked Phishing incidents.
3. Link all detected phishing incidents to the Phishing Campaign incident that was found or that was created previously.
4. Update the Phishing Campaign incident with the latest data about the campaign, and update all related phishing incidents to indicate that they are part of the campaign.
Detonate and Analyze File - GenericThis playbook uploads, detonates, and analyzes files for supported sandboxes. Currently supported sandboxes are Falcon Intelligence Sandbox, JoeSecurity, and Wildfire.
Detonate and Analyze File - JoeSecurityDeprecated. Use the joe-submit-sample command instead.
Detonate File - ANYRUNDetonates one or more files using the ANYRUN sandbox integration.
Returns relevant reports to the War Room and file reputations to the context data.
All file types are supported.
Detonate File - BitDamDetonates one or more files using BitDam integration.
Returns verdict to the War Room and file reputations to the context data.
Supported file types are mainly PDF & microsoft office software/
Detonate File - CrowdStrike Falcon Intelligence SandboxDeprecated. Use Detonate File - CrowdStrike Falcon Intelligence Sandbox v2 instead.
Detonate File - CrowdStrike Falcon Intelligence Sandbox v2Detonates a file using CrowdStrike Falcon Intelligence Sandbox.
Accepted file formats:
Portable executables: .exe, .scr, .pif, .dll, .com, .cpl, etc.
Office documents: .doc, .docx, .ppt, .pps, .pptx, .ppsx, .xls, .xlsx, .rtf, .pub
PDF
APK
Executable JAR
Windows script component: .sct
Windows shortcut: .lnk
Windows help: .chm
HTML application: .hta
Windows script file: .wsf
Javascript: .js
Visual Basic: .vbs, .vbe
Shockwave Flash: .swf
Perl: .pl
Powershell: .ps1, .psd1, .psm1
Scalable vector graphics: .svg
Python: .py
Linux ELF executables
Email files: MIME RFC 822 .eml, Outlook .msg.
Detonate file - CrowdStrike Falcon Sandbox v2Detonates a File using CrowdStrike Falcon sandbox.
Detonate File - CuckooDetonating file with Cuckoo
Detonate File - FireEye AXDetonate one or more files using the FireEye AX integration. This playbook returns relevant reports to the War Room and file reputations to the context data. The detonation supports the following file types - PE32, EXE, DLL, JAR, JS, PDF, DOC, DOCX, RTF, XLS, PPT, PPTX, XML, ZIP, VBN, SEP, XZ, GZ, BZ2, TAR, MHTML, SWF, LNK, URL, MSI, JTD, JTT, JTDC, JTTC, HWP, HWT, HWPX, BAT, HTA, PS1, VBS, WSF, JSE, VBE, CHM, JPG, JPEG, GIF, PNG, XLSX
Detonate File - FireEye Detection on DemandDetonate one or more files using the FireEye Detection on Demand integration. This playbook returns relevant reports to the War Room and file reputations to the context data.
Detonate File - GenericDetonate files through one or more active integrations that support file detonation.
Supported integrations:
- SecneurX Analysis
- ANY.RUN
- McAfee Advanced Threat Defense
- WildFire
- Lastline
- Cuckoo Sandbox
- Cisco Secure Malware Analytics (ThreatGrid)
- JoeSecurity
- CrowdStrike Falcon Sandbox
- FireEye AX
- VMRay Analyzer
- Polygon
- CrowdStrike Falcon Intelligence Sandbox
- OPSWAT Filescan.
Detonate File - Group-IB TDS PolygonDetonate file using Group-IB THF Polygon integration. This playbook returns relevant reports to the War Room and file reputations to the context data. The detonation supports the following file types: 7z, ace, ar, arj, bat, bz2, cab, chm, cmd, com, cpgz, cpl, csv, dat, doc, docm, docx, dot, dotm, dotx, eml, exe, gz, gzip, hta, htm, html, iqy, iso, jar, js, jse, lnk, lz, lzma, lzo, lzh, mcl, mht, msg, msi, msp, odp, ods, odt, ots, ott, pdf, pif, potm, potx, pps, ppsm, ppsx, ppt, pptm, pptx, ps1, pub, py, pyc, r, rar, reg, rtf, scr, settingcontent-ms, stc, svg, sxc, sxw, tar, taz, .tb2, .tbz, .tbz2, tgz, tlz, txz, tzo, txt, url, uue, vbe, vbs, wsf, xar, xls, xlsb, xlsm, xlsx, xml, xz, z, zip.
Detonate File - HybridAnalysisDeprecated. Use cs-falcon-sandbox-submit-sample with polling=true instead.
Detonate File - JoeSecurityDeprecated. Use the joe-submit-sample command instead.
Detonate File - JoeSecurity V2The Detonate File using Joe Sandbox Process is designed to streamline and enhance the security assessment of files. This automated system accepts a user-submitted file, sends it for in-depth analysis using Joe Sandbox technology, and returns comprehensive results as attachments to the user. The process is designed to be swift, efficient, and secure, providing users with valuable insights into potential threats and vulnerabilities within their files.
Detonate File - LastlineDetonates a File using the Lastline sandbox.
Lastline supports the following File Types:
EXE, SYS, DLL, COM, SCR, CPL, OCX, CGI, DOC, DOTM, DOCX, DOTX, XLS, PPAM, XSLX, PPS, XLSB, PPSX, XLSM, PPSM, PPT, PPTX, PPTM, RTF, SHS, XLTM, SLDM, XLTX, SLDX, XLAM, THMX, DOCM, XAR, JTD, JTDC, PDF, SWF, GZ, 7Z, TGZ, MSI, ZIP, LZH, CAB, LZMA, APK, JAR, CLASS, JPEG, PNG, GIF, CMD, ACE, BAT, ARJ, VBS, CHM, XML, LNK, URL, MOF, HTM, OCX, HTML, POTM, EML, POTX, MSG, PS, |VB, REG, VBA, WSC, VBE, WSF, VBS, WSH
Detonate File - Lastline v2Detonates a File using the Lastline sandbox.
Lastline supports the following File Types:
EXE, SYS, DLL, COM, SCR, CPL, OCX, CGI, DOC, DOTM, DOCX, DOTX, XLS, PPAM, XSLX, PPS, XLSB, PPSX, XLSM, PPSM, PPT, PPTX, PPTM, RTF, SHS, XLTM, SLDM, XLTX, SLDX, XLAM, THMX, DOCM, XAR, JTD, JTDC, PDF, SWF, GZ, 7Z, TGZ, MSI, ZIP, LZH, CAB, LZMA, APK, JAR, CLASS, JPEG, PNG, GIF, CMD, ACE, BAT, ARJ, VBS, CHM, XML, LNK, URL, MOF, HTM, OCX, HTML, POTM, EML, POTX, MSG, PS, |VB, REG, VBA, WSC, VBE, WSF, VBS, WSH
Detonate File - ReversingLabs A1000Upload sample to ReversingLabs A1000 appliance and automatically retrieve full & classification reports. Calculate final classification.
Detonate File - ReversingLabs TitaniumScaleUpload sample to ReversingLabs TitaniumScale instance and retrieve the analysis report.
Detonate File - SecneurX AnalysisDetonates a file using the SecneurX Analysis Integration. Returns relevant reports to the War Room and file reputations to the context data.
Detonate File - SNDBOXDeprecated. No available replacement.
Detonate File - ThreatGridDeprecated. Use Detonate File - ThreatGrid v2 instead.
Detonate File - ThreatGrid v2Detonate one or more files using the ThreatGrid integration. This playbook returns relevant reports to the War Room and file reputations to the context data. The detonation supports the following file types - EXE, DLL, JAR, JS, PDF, DOC, DOCX, RTF, XLS, PPT, PPTX, XML, ZIP, VBN, SEP, XZ, GZ, BZ2, TAR, MHTML, SWF, LNK, URL, MSI, JTD, JTT, JTDC, JTTC, HWP, HWT, HWPX, BAT, HTA, PS1, VBS, WSF, JSE, VBE, CHM
Detonate File - ThreatStreamDetonate one or more files using the Anomali ThreatStream v2 integration. This playbook returns relevant reports to the War Room, and file reputations to the context data.
Detonate File - VirusTotal (API v3)Detonate a file through VirusTotal (API v3)
Detonate File - VMRayDetonates a file with VMRay.
Detonate File From URL - ANYRUNDetonates one or more remote files using the ANYRUN sandbox integration.
Returns relevant reports to the War Room and file reputations to the context data.
This type of analysis works only for direct download links.
Detonate File From URL - JoeSecurityDeprecated. Use the joe-submit-sample command instead.
Detonate File From URL - WildFireDeprecated. Use Detonate File From URL - WildFire v2 instead.
Detonate File From URL - WildFire v2Detonate one or more files using the Wildfire v2 integration. This playbook returns relevant reports to the War Room and file reputations to the context data.
The detonation supports the following file types -
APK, JAR, DOC, DOCX, RTF, XLS, XLSX, PPT, PPTX, XML, PE32, PDF, DMG, PKG, RAR, 7Z.
Detonate Private File - VirusTotal Private ScanningDetonate a private file through VirusTotal Private Scanning service
Detonate Remote File from URL - McAfee ATDDetonates a File from a URL using the McAfee Advanced Threat Defense sandbox integration.
Detonate URL - ANYRUNDetonates one or more URLs using the ANYRUN sandbox integration.
Returns relevant reports to the War Room and url reputations to the context data.
Detonate URL - CrowdStrikeDeprecated. Use the cs-falcon-sandbox-submit-url command with polling=true instead.
Detonate URL - CrowdStrike Falcon Intelligence SandboxDeprecated. Use Detonate URL - CrowdStrike Falcon Intelligence Sandbox v2 instead.
Detonate URL - CrowdStrike Falcon Intelligence Sandbox v2Detonate one or more URL's using the CrowdStrike Falcon Intelligence Sandbox integration. This playbook returns relevant reports to the War Room and file reputations to the context data.
Detonate URL - CuckooDetonating URL with Cuckoo
Detonate URL - FireEye AXDetonating URL with FireEye AX.
Detonate URL - GenericDeprecated. Use Detonate URL - Generic v1.5 playbook instead. Detonate URL through active integrations that support URL detonation.
Detonate URL - Generic v1.5Detonate URL through one or more active integrations that support URL detonation.
Supported integrations:
- SecneurX Analysis
- ANY.RUN
- McAfee Advanced Threat Defense
- WildFire
- Lastline
- Cuckoo Sandbox
- Cisco Secure Malware Analytics (ThreatGrid)
- JoeSecurity
- CrowdStrike Falcon Sandbox
- FireEye AX
- VMRay Analyzer
- Polygon
- CrowdStrike Falcon Intelligence Sandbox
- OPSWAT Filescan
- ANYRUN
- VirusTotal
- Anomali ThreatStream
- Hatching Triage
- ThreatGrid
Detonate URL - Group-IB TDS PolygonDetonate URL using Group-IB THF Polygon integration.
Detonate URL - Hatching TriageDetonating URL with Hatching Triage.
Detonate URL - Hybrid AnalysisDeprecated. Use cs-falcon-sandbox-submit-url with polling=true instead.
Detonate URL - JoeSecurityDeprecated. Use the joe-submit-url command instead.
Detonate URL - LastlineDetonates a URL using the Lastline sandbox integration.
Detonate URL - Lastline v2Detonates a URL using the Lastline sandbox integration.
Detonate URL - McAfee ATDDetonates a URL using the McAfee Advanced Threat Defense sandbox integration.
Detonate URL - Phish.AIDeprecated. Vendor has declared end of life for this product. No available replacement.
Detonate URL - SecneurX AnalysisDetonates a URL using the SecneurX Analysis integration. Returns relevant reports to the War Room and file reputations to the context data.
Detonate URL - ThreatGridDeprecated. Use Detonate URL - ThreatGrid v2 instead.
Detonate URL - ThreatGrid v2Detonate one or more URLs using the ThreatGrid integration.
Detonate URL - ThreatStreamDetonates one or more URLs using the Anomali ThreatStream v2 sandbox integration.
Returns relevant reports to the War Room and URL reputations to the context data.
Detonate URL - VirusTotal (API v3)Detonate URL through VirusTotal (API v3) integration.
Detonate URL - VMRayDetonates a URL using the VMRay sandbox integration.
Detonate URL - WildFire v2.1Deprecated. Use Detonate URL - WildFire v2.2 instead.
Detonate URL - WildFire v2.2Detonate a webpage or remote file using the WildFire v2 integration. This playbook returns relevant reports to the War Room and file reputations to the context data.
The detonation supports the following file types:
APK, JAR, DOC, DOCX, RTF, OOXLS, XLSX, PPT, PPTX, XML, PE32, PDF, DMG, PKG, RAR, 7Z, JS.
Detonate URL - WildFire-v2Deprecated. Use Detonate URL - WildFire v2.2 instead.
Digital Defense FrontlineVM - Old Vulnerabilities FoundThis will query Frontline.Cloud's active view for any critical level vulnerabilities found to be older than 90 days.
Digital Defense FrontlineVM - PAN-OS block assetsThis playbook will pull Panorama queried threat logs and check for any correlating assets that are found to have a minimum of high level vulnerabilities. If so, it will block the the IP using Panorama's PAN-OS - Block IP and URL - External Dynamic List playbook.
Digital Defense FrontlineVM - Scan Asset Not Recently ScannedThis playbook will pull the IP address from the details value of an incident and check if that asset has been scanned within the past 60 days. If not then it will prompt to perform a scan on the asset.
Digital Guardian Demo PlaybookThis playbook will show how to handle an exfiltration event through Digital Guardian by emailing a user's manager and adding the user to a DG Watchlist.
Digital Shadows - CVE_IoC Assessment & EnrichmentEnrichment of CVE IOC types - sub-playbook for IOC Assessment & Enrichment playbook
Digital Shadows - Domain Alert Intelligence (Automated)Provides intelligence and reputation outputs based on the most recent Impersonating Domain, Subdomain or Phishing URL reported by Digital Shadows SearchLight.
Digital Shadows - Domain_IoC Assessment & EnrichmentEnrichment of Domain IOC types - sub-playbook for IOC Assessment & Enrichment playbook
Digital Shadows - IoC Assessment & EnrichmentEnrich indicators by providing intelligence and more associated indicators based on confirmed reporting in Digital Shadows SearchLight.
Digital Shadows - IP_IoC Assessment & EnrichmentEnrichment of IP IOC types - sub-playbook for IOC Assessment & Enrichment playbook
Digital Shadows - MD5_IoC Assessment & EnrichmentEnrichment of MD5 IOC types - sub-playbook for IOC Assessment & Enrichment playbook
Digital Shadows - SHA1_IoC Assessment & EnrichmentEnrichment of SHA1 IOC types - sub-playbook for IOC Assessment & Enrichment playbook
Digital Shadows - SHA256_IoC Assessment & EnrichmentEnrichment of SHA256 IOC types - sub-playbook for IOC Assessment & Enrichment playbook
Digital Shadows - URL_IoC Assessment & EnrichmentEnrichment of URL IOC types - sub-playbook for IOC Assessment & Enrichment playbook
Dispatch Incident - Vectra XDRThis playbook is called from the Process Incident - Vectra XDR playbook. It will fetch all active detections for the entity under investigation. It will then assign the entity to a user; if an assignment already exists, it will update that assignment and add a note in Vectra.
DLP - Get ApprovalGet an approver response for an exemption request from a user.
DLP - Get User FeedbackGet the user feedback on a blocked file, whether it is false or true positive and if an exemption is needed.
DLP - Get User Feedback via EmailGet the user feedback via email on a blocked file, whether it is false or true positive and if an exemption is needed.
DLP - User Message App CheckCheck if the given message app exists and is configured and retrieve the user details from it.
DLP Incident Feedback LoopCollects feedback from user about blocked files.
Domain Enrichment - GenericDeprecated. Use "Domain Enrichment - Generic v2" playbook instead. Enrich Domain using one or more integrations.
Domain enrichment includes:
Domain reputation
Threat information
Domain Enrichment - Generic v2Enrich domains using one or more integrations.
Domain enrichment includes:
Threat information
Domain reputation using !domain command
Domain Enrichment - RST Threat FeedEnrich domains using RST Threat Feed integration
DomainTools Associate Indicator to IncidentThis playbook calls the AssociateIndicatorsToIncident Script to Associate an Indicator to its the current incident created. Checks for additionalindicators in the customFields of an incident.
DomainTools Auto PivotsThis playbook retrieves the Iris Investigate profile of domain and automatically identifies potential connected infrastructure related to artifacts based on DomainTools Guided Pivot value.
DomainTools Check Domain Risk Score By Iris TagsThis playbook will alert a user if a monitored set of domains, labeled by Iris Investigate tags, becomes high risk. To use it, tag domains in the Iris Investigate UI. Enter a comma-separated list of tags to monitor to the playbook input "dt_monitored_iris_tags" and run this playbook on a scheduled basis. It will add any new high risk domains (based on the threshold defined in this playbook) as indicators on the associated incident.
DomainTools Check New Domains by Iris HashThis playbook helps monitor for new domains matching given infrastructure parameters (registrar, DNS, SSL certs, etc.). Start with a search in the Iris Investigate UI. Add an advanced search filter for "First Seen", "Within", "the last day" (for example) to your search. Run the search, then click "Import/Export Search" to view the Search Hash. Copy that into this playbook trigger. Every time this playbook runs, it will pull the new indicators matching the search and add them to the current incident
DropBox - Massive scale operations on filesThis playbook investigates “Massive File Alterations” and “DropBox - Massive File Downloads” alerts by gathering user and IP information and performing remediation based on the information gathered and received from the user.

Used Sub-playbooks:
Enrichment for Verdict
Block Indicators - Generic v3
Block IP - Generic v3
Block Account - Generic v2

If you wish to link this playbook to the relevant alerts automatically, we recommend using the following filters when configuring the playbook triggers: Alert Source = Correlation
Alert Name = DropBox - Massive File Alterations, DropBox - Massive File Downloads
Druva-Ransomware-ResponseUse Druva-Ransomware-Response to stop the spread of ransomware and avoid reinfection or contamination spread.
DSAR Inventa HandlerHandling DSAR requests
EDL Monitor- Email EDL contentYou can use the playbook (or a cloned copy) with a job to check the EDL on a schedule.
Email Address Enrichment - GenericDeprecated. Use "Email Address Enrichment - Generic v2.1" playbook instead. Get email address reputation using one or more integrations
Email Address Enrichment - Generic v2Deprecated. Use "Email Address Enrichment - Generic v2.1" playbook instead. Enrich email addresses. Email address enrichment involves:
- Getting information from Active Directory for internal addresses
- Getting the domain-squatting reputation for external addresses
Email Address Enrichment - Generic v2.1Enrich email addresses.
- Get information from Active Directory for internal addresses
- Get the domain-squatting reputation for external addresses
- Email address reputation using !email command.
Email Headers Check - GenericThis playbook executes one sub-playbook and one automation to check the email headers:
- Process Microsoft's Anti-Spam Headers - This playbook stores the SCL, BCL and PCL scores if they exist to the relevant incident fields (Phishing SCL Score, Phishing PCL Score, Phishing BCL Score).
- CheckEmailAuthenticity - This automation checks email authenticity based on its SPF, DMARC, and DKIM.
Employee Offboarding - DelegateThis playbook delegates user resources and permissions as part of the IT - Employee Offboarding playbook.
Employee Offboarding - Gather User InformationThis playbook gathers user information as part of the IT - Employee Offboarding playbook.
Employee Offboarding - Retain & DeleteThis playbook playbook performs retention and deletion of user information as part of the IT - Employee Offboarding playbook.
Employee Offboarding - Revoke PermissionsThis playbook revokes user permissions as part of the IT - Employee Offboarding playbook.
Employee Status SurveyNote: This is a beta playbook, which lets you implement and test pre-release software. Since the playbook is beta, it might contain bugs. Updates to the playbook during the beta phase might include non-backward compatible features. We appreciate your feedback on the quality and usability of the playbook to help us identify issues, fix them, and continually improve. Manages a crisis event where employees have to work remotely due to a pandemic, issues with the workplace or similar situations. Sends a questionnaire to all direct reports under a given manager. The questionnaire asks the employees for their health status and whether they need any help. The data is saved as employee indicators in Cortex XSOAR, while IT and HR incidents are created to provide assistance to employees who requested it. The questionnaire expires after 24 hours by default, and during that time the responses are processed every 5 minutes. These settings can be edited via the task that sends the questionnaire and the loop settings of the Continuously Process Survey Responses playbook, respectively.
Endace Search Archive and DownloadDeprecated. No available replacement. This playbook uses Endace APIs to search, archive and download PCAP file from either a single EndaceProbe or many via the InvestigationManager and enables integration of full historical packet capture into security automation workflows.
Endace Search Archive Download PCAPDeprecated. This playbook has been deprecated. Use Endace Search Archive Download\ \ PCAP v2 instead. This playbook uses Endace APIs to search, archive and download\ \ PCAP file from either a single EndaceProbe or many via the InvestigationManager.\ \ The workflow accepts inputs like “the date and time of the incident or a\ \ timeframe”, “source or destination IP address of the incident”, “source or destination\ \ IP port of the incident”, “protocol of the incident” and name of archive file.\ \ \nThe Workflow in this playbook - \n1. Finds the packet history related to the\ \ search items. Multiple Search Items in an argument field are OR'd. Search Items\ \ between multiple arguments are AND'd. \n2. A successful Search is followed by\ \ an auto archival process of matching packets on EndaceProbe which can be accessed\ \ from an investigation link on the Evidence Board and/or War Room board that can\ \ be used to start forensic analysis of the packets history on EndaceProbe.\n3.\ \ Finally Download the archived PCAP file to XSOAR system provided the file size\ \ is less than a user defined threshold say 10MB. Files greater than 10MB can be\ \ accessed or analyzed on EndaceProbe via \"Download PCAP link\" or \"Endace PivotToVision\ \ link\" displayed on Evidence Board.\n
Endace Search Archive Download PCAP v2This playbook uses Endace APIs to search, archive and download PCAP file from either a single EndaceProbe or many via the InvestigationManager. The workflow accepts inputs like “the date and time of the incident or a timeframe”, “source or destination IP address of the incident”, “source or destination IP port of the incident”, “protocol of the incident” and name of archive file.
Required Inputs -
Either timeframe or start and timeframe or end and timeframe or start and end fields.
Either src_host_list or dest_host_list or ip fields.
Either src_port_list or dest_port_list or port fields.
archive_filename field is required
delete_archive field is required
download_threshold field is required

The Workflow in this playbook :
1. Finds the packet history related to the search items. Multiple Search Items in an argument field are OR'd. Search Items between multiple arguments are AND'd.
2. A successful Search is followed by an auto archival process of matching packets on EndaceProbe which can be accessed from an investigation link on the Evidence Board and/or War Room board that can be used to start forensic analysis of the packets history on EndaceProbe.
3. Finally Download the archived PCAP file to XSOAR system provided the file size is less than a user defined threshold say 10MB. Files greater than this threshold can be accessed or analyzed on EndaceProbe via "Download PCAP link" or "Endace PivotToVision link" displayed on Evidence Board.
Endpoint data collectionDeprecated. Generic playbook to collect data from endpoints for IR purposes. Will use whichever integrations are configured and available.
Endpoint Enrichment - Cylance Protect v2Enriches endpoints using the Cylance Protect v2 integration.
Endpoint Enrichment - GenericDeprecated. Use "Endpoint Enrichment - Generic v2.1" playbook instead. Enrich an Endpoint Hostname using one or more integrations
Endpoint Enrichment - Generic v2Deprecated. Use "Endpoint Enrichment - Generic v2.1" playbook instead. Enrich an endpoint by hostname using one or more integrations.
Currently, the following integrations are supported:
- Active Directory
- McAfee ePolicy Orchestrator
- Carbon Black Enterprise Response
- Cylance Protect
- CrowdStrike Falcon Host
Endpoint Enrichment - Generic v2.1Enrich an endpoint by hostname using one or more integrations.
Supported integrations:
- Active Directory Query v2
- McAfee ePO v2
- VMware Carbon Black EDR v2
- Cylance Protect v2
- CrowdStrike Falcon
- ExtraHop Reveal(x)
- Cortex XDR / Core (endpoint enrichment, reputation and risk)
- Endpoint reputation using !endpoint command.
Endpoint Enrichment By EntityId - XM CyberEnrich an endpoint by entityId using XM Cyber integration. Outputs include affected assets, affected entities, complexity of compromise, and more
Endpoint Enrichment By Hostname - XM CyberEnrich an endpoint by hostname using XM Cyber integration. Outputs include affected assets, affected entities, complexity of compromise, and more
Endpoint Enrichment By IP - XM CyberEnrich IP addresses using XM Cyber integration.
- Resolve IP address to entity
- Get entity information for IP addresses regarding impact on critical assets and complexity of compromise
Endpoint Investigation PlanThis playbook handles all the endpoint investigation actions by performing the following tasks on every alert associated with the incident:
Pre-defined MITRE Tactics
Host fields (Host ID)
Attacker fields (Attacker IP, External host)
MITRE techniques
* File hash (currently, the playbook supports only SHA256)

Note: The playbook inputs enable manipulating the execution flow; read the input descriptions for details.
Endpoint Malware Investigation - GenericDeprecated. Use 'Malware Investigation & Response Incident handler' instead. (From the 'Malware Investigation And Response Pack')
This playbook is triggered by a malware incident from an 'Endpoint' type integration. The playbook performs enrichment, detonation, and hunting within the organization, and remediation on the malware.
Used sub-playbooks:
- Endpoint Enrichment - Generic v2.1
- Retrieve File from Endpoint - Generic
- Detonate File - Generic
- File Enrichment - Generic v2
- Calculate Severity - Generic v2
- Isolate Endpoint - Generic
- Block Indicators - Generic v2
Endpoint Malware Investigation - Generic V2Deprecated. Use 'Malware Investigation & Response Incident handler' instead. (From the 'Malware Investigation And Response Pack')


This playbook provides a framework for handling malware investigation through all essential steps. The playbook consists of 7 stages. Each stage contains the relevant playbook or tasks.
This playbook auto extracts indicators from incidents using indicator extraction rules of the malware incident type.
To use Illusive integration in the `Forensics - Generic` playbook, note that you will be able to set the forensic timeline by editing the `Forensics - Generic` playbook inputs.
Enrich DXL with ATD verdictDeprecated. Use "Enrich DXL with ATD verdict v2" playbook instead. Example of using McAfee ATD and pushing any malicious verdicts over DXL.
Detonates a file in ATD and if malicious - push its MD5, SHA1 and SHA256 hashes to McAfee DXL.
Enrich DXL with ATD verdict v2Uses McAfee ATD to push any malicious verdicts over DXL.
Detonates a file in ATD and if malicious, pushes its MD5, SHA1 and SHA256 hashes to McAfee DXL.
Enrich Incident With Asset Details - RiskIQ Digital FootprintEnriches the incident with asset details, and enriches the asset with the incident URL on the RiskIQ Digital Footprint platform. This playbook also sends an email containing the owner's information to the primary or secondary contact of the asset and provides the user with an opportunity to update or remove the asset.
Supported integration:
- RiskIQ Digital Footprint
Enrich McAfee DXL using 3rd party sandboxDeprecated. Use "Enrich McAfee DXL using 3rd party sandbox v2" playbook instead. Example of bridging DXL to a third party sandbox.
Detonate a file in Wildfire and if malicious - push its MD5, SHA1 and SHA256 hashes to McAfee DXL.
Enrich McAfee DXL using 3rd party sandbox v2Example of bridging DXL to a third party sandbox.
Detonate a file in 3rd party sandbox and if malicious, push its MD5, SHA1 and SHA256 hashes to McAfee DXL.
Enrich ThinkstCanary EventsEnrich events that are received as part of a ThinkstCanary incident.
Enrichment for VerdictThis playbook checks prior alert closing reasons and performs enrichment and prevalence checks on different IOC types. It then returns the information needed to establish the alert's verdict.
Entity Enrichment - GenericDeprecated. Use "Entity Enrichment - Generic v3" playbook instead. Enrich entities using one or more integrations
Entity Enrichment - Generic v2Enrich entities using one or more integrations
Entity Enrichment - Generic v3Enrich entities using one or more integrations.
Entity Enrichment - Generic v4Enrich entities using one or more integrations.
Entity Enrichment - Phishing v2Enrich entities using one or more integrations
Eradication PlanThis playbook handles all the eradication actions available with Cortex XSIAM, including the following sub-playbooks:
Eradication Plan - Reset user password
Eradication Plan - Delete file
* Eradication Plan - Kill process (currently, the playbook supports terminating a process by name)

Note: The playbook inputs enable manipulating the execution flow. Read the input descriptions for details.
Eradication Plan - Delete FileThis playbook is one of the sub-playbooks in the eradication plan.
This playbook executes actions of file deletion, which is a crucial step in the eradication process.
Eradication Plan - Reset PasswordThis playbook is one of the sub-playbooks in the eradication plan.
The playbook executes actions to reset the user's passwords, which is a crucial step in the eradication process.
Eradication Plan - Terminate ProcessThis playbook is one of the sub-playbooks in the eradication plan.
This playbook handles the termination of the processes as a crucial step in the eradication action.
The playbook executes actions of process termination, which is a crucial step in the eradication process.
The process termination can be performed based on either the process ID or the process name.
Example-Delinea-Folder OperationsExample for usage integration REST API Folder object for Delinea Secret Server.
Example-Delinea-Retrieved Username and PasswordExample for usage integration REST API for Delinea Secret Server. Methods retrieved username and password form secret.
Example-Delinea-Secret Object OperationsExample for usage integration REST API Secret object for Delinea Secret Server.
Example-Delinea-User object operationsExample for usage integration REST API User object for Delinea Secret Server.
Exchange 2016 Search and DeleteRun a compliance search in Exchange Server 2016, and delete the results.
Expanse AttributionSubplaybook for Handle Expanse Incident playbooks. Given an Expanse Issue IP, Issue Provider, Issue Domain,
Issue Port and Issue Protocol hunts for internal activity related to the detected service.
The playbook looks for logs on Splunk, Cortex Data Lake, Panorama, and ServiceNow CMDB.
Returns a list of potential owner BUs, owner Users, Device and Notes.
Expanse Behavior Severity UpdateDeprecated. Use Xpanse Incident Handling - Generic instead.
Expanse Enrich Cloud AssetsSubplaybook for Handle Expanse Incident playbooks.
This Playbook is meant to be used as a subplaybook to enrich Public Cloud Assets (i.e. IP addresses and FQDNs) by:
- Searching the corresponding Region and Service by correlating the provided IPs with IP range feeds retrieved from Public Cloud Providers (require TIM and Public Cloud feeds such as AWS Feed integrations to be enabled).
- Searching IPs and FQDNs in Prisma Cloud inventory (requires Prisma Cloud).
Expanse Find Cloud IP Address Region and ServiceSubplaybook for Expanse Enrich Cloud Assets subplaybook. This playbook is used to find the corresponding Public Cloud Region (i.e. AWS us-east-1) and Service (i.e. AWS EC2) for a provided IP Address. It works by correlating the provided IP address with the IP Range Indicators (CIDRs) that can be collected from Public Cloud feeds (i.e. AWS Feed) in XSOAR. CIDR Indicators must be tagged properly using the corresponding tags (i.e. AWS for AWS Feed): tags can be configured in the Feed Integrations and must match the ones provided in the inputs of this playbook. Correlation is done based on the longest match (i.e. smaller CIDR such as /20 range wins over a bigger one such as /16).
Expanse Load-Create ListSub-playbook to support Expanse Handle Incident playbook.
Loads a list to be used in the Expanse playbook.
Creates the list if it does not exist.
Expanse Unmanaged CloudSubplaybook for bringing rogue cloud accounts under management.
Expanse VM EnrichThis Playbook is used to verify that all assets found by Expanse are being scanned by a vulnerability management tool by:
- Searching the IP and / or domain of the identified Expanse asset in the vulnerability management tool
This playbook expects an incident with an IP or a Domain to exist in the context.
Export Single Alert to ServiceNow - PANW IoT 3rd Party IntegrationThis playbook handles incidents triggered in the PANW IoT (Zingbox) UI by sending the alert to ServiceNow.
Export Single Asset to SIEM - PANW IoT 3rd Party IntegrationThis playbook handles incidents triggered in the PANW IoT (Zingbox) UI by sending the alert to your SIEM.
Export Single Vulnerability to ServiceNow - PANW IoT 3rd Party IntegrationThis playbook to handles incidents triggered in the PANW IoT (Zingbox) UI by sending the vulnerability to ServiceNow.
Extract and Create RelationshipsExtract and enrich indicators
Extract and Enrich Expanse IndicatorsSubplaybook for Handle Expanse Incident playbooks.
Extract and Enrich Indicators (CIDRs, IPs, Certificates, Domains and DomainGlobs) from Expanse Incidents.
Enrichment is performed via enrichIndicators command and generic playbooks.
Returns the enriched indicators.
Extract Indicators - GenericDeprecated. We recommend using extractIndicators command instead.
Extract indicators from input data.
Extract Indicators From File - GenericDeprecated. Use the "Extract Indicators From File - Generic v2" playbook instead.\
\ Extracts indicators from a file.
Supported file types:
- PDF
- TXT
- HTM, HTML
- DOC, DOCX
Extract Indicators From File - Generic v2This playbook extracts indicators from a file.
Supported file types:
- CSV
- PDF
- TXT
- HTM, HTML
- DOC, DOCX
- PPT
- PPTX
- RTF
- XLS
- XLSX
- XML
- XLSM
- DOCM
- PPTM
- DOTM
- XLSB
- DOT
- PPSM.
ExtraHop - CVE-2019-0708 (BlueKeep)This server received a Remote Desktop Protocol (RDP) connection request that is consistent with a known vulnerability, also known as BlueKeep, in older versions of Microsoft Windows. This vulnerability allows an unauthenticated attacker to remotely run arbitrary code on an RDP server. The attacker can then tamper with data or install malware that could propagate to other Windows devices across the network. Investigate to determine if this server is hosting a version affected by CVE-2019-0708: Windows 7, Windows XP, Windows Vista, Windows Server 2003, and Windows Server 2008.

MITIGATION OPTIONS
- Disable Remote Desktop Services if they are not required
- Implement Network Level Authentication (NLA) on systems running supported versions of Windows 7, Windows Server 2008, and Windows Server 2008 R2
- Configure firewalls to block traffic on TCP port 3389
ExtraHop - DefaultDefault playbook to run for all ExtraHop Detection incidents. This playbook handles ticket tracking as well as triggering specific playbooks based on the name of the ExtraHop Detection.
ExtraHop - Get Peers by HostGiven a host, the playbook will retrieve the peer network devices that communicated with that host in a given time range. In addition to a list of peers and protocols (sorted by bytes) the playbook returns a link to the ExtraHop Live Activity Map to visualize the peer relationships.
ExtraHop - Ticket TrackingDeprecated. Use the "ExtraHop - Ticket Tracking v2" playbook instead.\ \ Links the Demisto incident back to the ExtraHop detection that created it for ticket tracking purposes.
ExtraHop - Ticket Tracking v2Links the Demisto incident back to the ExtraHop detection that created it for ticket tracking purposes.
Failed Login Playbook - Slack v2Deprecated. Use the Slack - General Failed Logins v2.1 playbook. When there are three failed login attempts to Demisto that originate from the same user ID, a direct message is sent to the user on Slack requesting that they confirm the activity. If the reply is "no", then the incident severity is set to "high". If the reply is "yes", then another direct message is sent to the user asking if they require a password reset in AD.
Fetch All Violations - SecuronixGets a list of violations with pagination using queryId parameter.
Fetch Violations - SecuronixGets a list of violation data.
Field Polling - GenericThis playbook polls a field to check if a specific value exists.
File Analysis - ReversingLabs A1000Upload sample to ReversingLabs A1000 appliance and automatically retrieve full & classification reports. Calculate final classification.
File Enrichment - File reputationGet file reputation using one or more integrations
File Enrichment - GenericDeprecated. Use "File Enrichment - Generic v2" playbook instead. Enrich a file using one or more integrations.

File enrichment includes:
File history
Threat information
* File reputation
File Enrichment - Generic v2Enrich a file using one or more integrations.

- Provide threat information
- Determine file reputation using the !file command
File Enrichment - RST Threat FeedEnrich File hashes using RST Threat Feed integrations
File Enrichment - Virus Total (API v3)Get file information using the Virus Total API integration.
File Enrichment - Virus Total Private APIDeprecated. Use the "File Enrichment - Virus Total v3" playbook instead.
File Enrichment - VMRayGet file information using the VMRay integration.
File ReputationThis playbook checks the file reputation and sets the verdict as a new context key.

The verdict is composed by 3 main components:

VirusTotal detection rate
Digital certificate signers
* NSRL DB

Note: a user can provide a list of trusted signers of his own using the playbook inputs
File Reputation - ReversingLabs TitaniumCloudProvides file reputation data for a file (malicious, suspicious, known good or unknown).
Required TitaniumCloud API rights:

TCA-0101
FireEye ETP - Indicators HuntingThis playbook queries FireEye Email Threat Prevention (ETP) for indicators such as domains, IP addresses, sender and recipient email addresses.
Separate searches are conducted for each type of indicator in the playbook.

Note that multiple search values should be separated by commas only (without spaces or any special characters).
FireEye Helix Archive SearchCreate an archive search in FireEye Helix, and fetch the results as events.
FireEye HX - Execution Flow Indicators HuntingThis playbook queries FireEye Endpoint Security (HX) for execution flow indicators, including processes name, registry keys, registry values, and applications.

Note that multiple search values should be separated by commas only (without spaces or any special characters).
FireEye HX - File Indicators HuntingThis playbook queries FireEye Endpoint Security (HX) for file indicators, including MD5 hashes, SHA256 hashes, SHA1 hashes, file names, file paths, and file types.

Note that multiple search values should be separated by commas only (without spaces or any special characters).
FireEye HX - Indicators HuntingThis playbook facilitates threat hunting and detection of IOCs within FireEye Endpoint Security (HX) utilizing three sub-playbooks. The sub-playbooks query FireEye HX for different indicators including files, traffic, and execution flow indicators.

Note that multiple search values should be separated by commas only (without spaces or any special characters).

Supported IOCs for this playbook:
- MD5
- SHA1
- SHA256
- IP Address
- URLDomain
- Registry Value
- Registry Key
- File Name
- Process Name
- Port Number
- File Path
- FileType
FireEye HX - Isolate EndpointThis playbook will auto isolate endpoints by the endpoint ID that was provided in the playbook.
FireEye HX - Traffic Indicators HuntingThis playbook queries FireEye Endpoint Security (HX) for traffic indicators, including IP addresses, URLs, domains, and ports.

Note that multiple search values should be separated by commas only (without spaces or any special characters).
FireEye HX - Unisolate EndpointThis playbook unisolates endpoints according to the hostname/endpoint ID that is provided by the playbook input.
FireEye Red Team Tools Investigation and ResponseThis playbook does the following:

Collect indicators to aid in your threat hunting process.
- Retrieve IOCs of FireEye red team tools.
- Discover IOCs of associated activity related to the infection.
- Generate an indicator list to block indicators with SUNBURST tags.

Hunt for the indicators
- Search endpoints with the FireEye red team tools CVEs.
- Search endpoint logs for FireEye red team tools hashes.
- Search and link previous incidents with the FireEye hashes.

If compromised hosts are found, fire off sub-playbooks to isolate/quarantine infected hosts/endpoints and await further actions from the security team.
FireMon Create Policy Planner TicketCreates a new Policy Planner Ticket for PolicyPlanner in FMOS box.
FireMon Pre Change AssessmentValidates and Return Pre Changes Assessment on Rules added as Requirement.
Forensics Tools AnalysisThis playbook allows the user to analyze forensic evidence acquired from a host, such as registry files and PCAP files.
FortiSandbox - Loop for Job SubmissionsPlaybook used to retrieve job id for submissions of fortisandbox using. Deprecated. Use `fortisandbox-submission-file-upload` instead. the submission id.
FortiSandbox - Loop For Job VerdictPlaybook used to retrieve the verdict for a specific job id for a sample. Deprecated. Use `fortisandbox-submission-file-upload` instead. submitted to FortiSandbox
FortiSandbox - Upload Multiple FilesPlaybook used to upload files to FortiSandbox. Deprecated. Use `fortisandbox-submission-file-upload` instead.
GCP - EnrichmentGiven the IP address this playbook enriches GCP and Firewall information.
GCP - Firewall RemediationThis playbook adds new firewall rules with access only from private ip address range and blocks traffic that's exposed to public internet. For example, if RDP is exposed to the entire world, this playbook adds new firewall rules that only allows traffic from private ip address and blocks rest of the RDP traffic.
GCP - User InvestigationThis playbook performs an investigation on a specific user in GCP environments, using queries and logs from G Suite Auditor, and GCP Logging to locate the following activities performed by the user:
- Failed login attempt
- Suspicious API usage by the user
- Anomalous network traffic by the user
- Unusual and suspicious login attempt
- User's password leaked
GDPR Breach NotificationThis playbook triggers by a GDPR breach incident, and then performs the required tasks that are detailed in GDPR Article 33.
The General Data Protection Regulation (the GDPR) is a regulation in EU law on data protection and privacy of individuals. The GDPR introduces the requirement for a personal data breach to be notified to the competent national supervisory authority and in certain cases, to communicate the breach to the individuals whose personal data have been affected by the breach.
***Disclaimer: This playbook does not ensure compliance to the GDPR regulation. Before using this playbook, we advise consulting with the relevant authority, and adjusting it to the organization's needs.
Gem Handle Alert for Root UsageFind all the users who might’ve performed the actions using root (via the source IP), validate it with them using Slack and resolve the alert in case these actions were planned.
Gem Handle ec2Gem playbook to handle an alert involving an ec2 instance.
Gem Validate triggering eventGet the triggering events of a Gem Alert and send a validation Slack message to the dev team.
The response will be added to the Gem Timeline.
GenericPollingUse this playbook as a sub-playbook to block execution of the master playbook until a remote action is complete.
This playbook implements polling by continuously running the command in Step #2 until the operation completes.
The remote action should have the following structure:

1. Initiate the operation.
2. Poll to check if the operation completed.
3. (optional) Get the results of the operation.
GenericPolling-FortiSIEMThis playbook executes a search query to retrieve FortiSIEM Events.
Get Cloud Account Owner - GenericRetrieves the owners of a cloud account based on account ID.
Current supported platforms:
- GCP
- Prisma Cloud.
Get Code42 Employee InformationReceives usernames from a Code42 Incydr alert and queries Active Directory for employee and supervisor information, if applicable.
Get Email From Email Gateway - FireEyeThis playbook retrieves a specified EML/MSG file directly from FireEye Email Security or Central Management.
Get Email From Email Gateway - GenericThis playbook retrieves a specified EML/MSG file directly from the email security gateway product.
Get Email From Email Gateway - MimecastThis playbook retrieves a specified EML/MSG file directly from Mimecast.
Get Email From Email Gateway - Proofpoint Protection ServerThis playbook retrieves a specified EML/MSG file directly from the Proofpoint Protection Server.
Get endpoint details - GenericDeprecated. Use the `Endpoint Enrichment - Generic v2.1` playbook instead.
This playbook uses the generic command !endpoint to retrieve details on a specific endpoint.
This command currently supports the following integrations:
- Palo Alto Networks Cortex XDR - Investigation and Response.
- CrowdStrike Falcon.
Get entity alerts by MITRE tacticsThis playbook searches XDR alerts related to specific entities, on a given timeframe, based on MITRE tactics.
Note: The playbook's inputs enable manipulating the execution flow. Read the input descriptions for details.
Get File Sample - GenericRetrieves files from endpoints by the file hash or the file path.
Get File Sample By Hash - Carbon Black Enterprise ResponseReturns to the war-room a file sample correlating to MD5 hashes in the input using Carbon Black Enterprise Response integration
Get File Sample By Hash - Cylance ProtectDeprecated. Use "Get File Sample By Hash - Cylance Protect v2" playbook instead.
Get File Sample By Hash - Cylance Protect v2This playbook returns a file sample to the War Room given the file's SHA256 hash, using Cylance Protect v2 integration.
Get File Sample By Hash - GenericDeprecated. Use "Get File Sample By Hash - Generic v2" playbook instead. Returns to the war-room a file sample correlating from a hash using one or more products
Get File Sample By Hash - Generic v2Deprecated. Use `Get File Sample By Hash - Generic v3` instead. This playbook returns a file sample correlating to a hash in the war-room using the following sub-playbooks:
- Get File Sample By Hash - Carbon Black Enterprise Response
- Get File Sample By Hash - Cylance Protect v2
Get File Sample By Hash - Generic v3This playbook returns a file sample correlating to a hash in the War Room using the following sub-playbooks:
- Get binary file by MD5 hash from Carbon Black telemetry data - VMware Carbon Black EDR v2.
- Get the threat (file) associated with a specific SHA256 hash - Cylance Protect v2.
- Get the file associated with a specific MD5 or SHA256 hash - Code42.
Get File Sample From Path - Carbon Black Enterprise ResponseReturns a file sample to the war-room from a path on an endpoint using Carbon Black Enterprise Response
Get File Sample From Path - D2Returns a file sample to the war-room from a path on an endpoint using Demisto Dissolvable Agent (D2)

Input:
Credentials - credentials to use when trying to deploy Demisto Dissolvable Agent (D2) (default: Admin)
${Endpoint.Hostname} - deploy agent on target endpoint
* ${File.Path} - file's path to collect
Get File Sample From Path - GenericDeprecated. Use `Get File Sample From Path - Generic V3` instead. Returns a file sample to the war-room from a path on an endpoint using one or more integrations

inputs:
* UseD2 - if "True", use Demisto Dissolvable Agent (D2) to return the file (default: False)
Get File Sample From Path - Generic V2Deprecated. Use `Get File Sample From Path - Generic V3` instead.
This playbook returns a file sample correlating to a path into the War Room using the following sub-playbooks:
inputs:
1) Get File Sample From Path - D2.
2) Get File Sample From Path - VMware Carbon Black EDR (Live Response API).
Get File Sample From Path - Generic V3This playbook returns a file sample from a specified path and host that you input in the following playbooks:
- PS Remote Get File Sample From Path
- Get File Sample From Path - VMware Carbon Black EDR (Live Response API)
- CrowdStrike Falcon - Retrieve File
- MDE - Retrieve File
- Cortex XDR - Retrieve File V2
Get File Sample From Path - VMware Carbon Black EDR - Live Response APIThis playbook retrieves a file from a path on an endpoint using VMware Carbon Black EDR (Live Response API).
Make sure to provide the Carbon Black sensor ID of the endpoint from which you want to retrieve the file.
Get host forensics - GenericThis playbook retrieves forensics from hosts for the following integrations:
- Illusive Networks
- Microsoft Defender For Endpoint.
Get Original Email - EWSThis playbook retrieves the original email in a thread, including headers and attachments, when the reporting user forwarded the original email not as an attachment.
Note:\ You must have the necessary eDiscovery permissions in the EWS integration to execute a global search.
Get Original Email - EWS v2This v2 playbook retrieves the original email in a thread as an EML file (and not an email object as in the previous version) by using the EWS v2 or EWSO365 integration.
It also reduces the number of tasks to perform the fetch action.
Note: You must have the necessary eDiscovery permissions in the EWS integration to execute a global search.
Get Original Email - GenericDeprecated. Use the "Get Original Email - Generic v2" playbook under the "Phishing" pack instead.
Get Original Email - Generic v2This v2 playbook is used inside the phishing flow. The inputs in this version do not use labels and also allow the user to supply an email brand.
Note: You must have the necessary permissions in your email service to execute a global search.

To retrieve the email files directly from the email service providers, use one of the provided inputs (Agari Phishing Defense customers should also use the following):
- EWS: eDiscovery
- Gmail: Google Apps Domain-Wide Delegation of Authority
- MSGraph: As described in the message-get API and the user-list-messages API
- EmailSecurityGateway retrieves EML files from:
FireEye EX
FireEye CM
Proofpoint Protection Server
Mimecast
Get Original Email - GmailDeprecated. Use GetOriginal_Email-_Gmail_v2 instead.
Use this playbook to retrieve the original email in the thread, including headers and attahcments, when the reporting user forwarded the original email not as an attachment.

You must have the necessary permissions in your Gmail service to execute global search: Google Apps Domain-Wide Delegation of Authority
Get Original Email - Gmail v2This v2 playbook uses the reporter's email headers to retrieve the original email. This decreases the number of tasks to retrieve the original email.
Use this playbook to retrieve the original email using the Gmail integration, including headers and attachments.
Note: You must have the necessary Google Apps Domain-Wide Delegation of Authority permissions in your Gmail service to execute global search.
Get Original Email - Microsoft Graph MailThis playbook retrieves the original email using the Microsoft Graph Mail integration.
Note: You must have the necessary permissions in the Microsoft Graph Mail integration as described in the message-get API and the user-list-messages API
Get prevalence for IOCsThe playbook queries the analytics module to receive the prevalence of an IOC.

Supported IOC:
- Process by SHA256
- Process by file name
- IP
- Domain
- CMD
- Registry (require key and value)

Get RaDark Detailed ItemsEnriches RaDark incident with detailed items.
Get the binary file from Carbon Black by its MD5 hashThis playbook retrieves a binary file by its MD5 hash from the Carbon Black telemetry data.
Get User Devices - GenericThis playbook retrieves information on all of the associated user devices.
In order to get a generic output, the following information on all of the retrieved devices will be saved under the `UserDevices` context key:
- Name
- Serial Number
- ID
- Model
- MAC Address
- OS
- Integration

Note that not all of the supported integrations will be able to retrieve this information.

In order to get the full list of supported integrations, read the following sub-playbooks descriptions:
- Get User Devices by Username - Generic
- Get User Devices by Email Address - Generic
Get User Devices by Email Address - GenericThis playbook retrieves information on all of the associated user devices, based on the user email.
In order to get a generic output, the following information on all of the retrieved devices will be saved under the `UserDevices` context key:
- Name
- Serial Number
- ID
- Model
- MAC Address
- OS
- Integration

Note that not all of the supported integrations will be able to retrieve this information.

Supported integrations:
- jamf v2
- Google Workspace (Gsuite)
- ServiceNow v2
- Active Directory Query v2
- Microsoft Graph API (In order to get devices details, provide the permissions as mentioned here: https://learn.microsoft.com/en-us/graph/api/user-list-owneddevices?view=graph-rest-1.0&tabs=http )
Get User Devices by Username - GenericThis playbook retrieves information on all of the associated user devices, based on the user's username.
In order to get a generic output, the following information on all of the retrieved devices will be saved under the `UserDevices` context key:
- Name
- Serial Number
- ID
- Model
- MAC Address
- OS
- Integration

Note that not all of the supported integrations will be able to retrieve this information.

Supported integrations:
- jamf v2
- Microsoft Defender for Endpoint
- Cortex XDR IR
- ServiceNow v2
- Google Workspace (Gsuite)
- Active Directory Query v2.
Gitlab - Guest user permission changeThis playbook investigates a "User Permissions Changed” alert by gathering user and IP information and performs remediation based on the information gathered and received from the user. To link this playbook to the relevant alerts automatically, we recommend using the following filters when configuring the playbook triggers: Alert Source = Correlation AND Alert Name = Gitlab - Permission change from guest to owner

Used Sub-playbooks:
Enrichment for Verdict
Block IP - Generic v3
* Block Account - Generic v2

Google Dorking File ProcessingThis playbook processes files fetched by the Google Dorking integration.
The SOC will track the file owner and classify the exposed data and users in order to contained the leaked data.
Google Vault - Display ResultsThis is a playbook for queuing and displaying vault search result
Google Vault - Search DriveThis is a playbook for performing Google Vault search in Drive accounts and display the results.
Google Vault - Search GroupsThis is a playbook for performing Google Vault search in Groups and display the results.
Google Vault - Search MailThis is a playbook for performing Google Vault search in Mail accounts and display the results.
GRACasePlaybook for fetching cases assosiated to high risk users.
HAFNIUM - Exchange 0-day exploitsThis playbook includes the following tasks:
Collect indicators to be used in your threat hunting process Retrieve IOCs related to HAFNIUM and the exploited exchange 0-day vulnerabilities Discover IOCs related to the attack Query firewall logs to detect malicious network activity Search endpoint logs for malicious hashes to detect compromised hosts (Available from Cortex XSOAR 5.5.0). Block indicators Note: This is a beta playbook, which lets you implement and test pre-release software. Since the playbook is beta, it might contain bugs. Updates to the pack during the beta phase might include non-backward compatible features. We appreciate your feedback on the quality and usability of the pack to help us identify issues, fix them, and continually improve. Read more about the attack on our Unit42 blog: https://unit42.paloaltonetworks.com/microsoft-exchange-server-vulnerabilities/ Sources: https://www.splunk.com/en_us/blog/security/detecting-hafnium-exchange-server-zero-day-activity-in-splunk.html https://www.microsoft.com/security/blog/2021/03/02/hafnium-targeting-exchange-servers/
Handle Darktrace Model BreachDeprecated. Use Darktrace Basic Model Breach Handler and Darktrace Basic AI Analyst Event Handler instead.
Handle Expanse IncidentMain Playbook to Handle Expanse Incidents.

There are several phases:
1. Enrichment: all the related information from the incident is extracted, and related indicators (IP, CIDR, Domain, DomainGlob, Certificate) are created and enriched.
2. Validation: the found IP and FQDN are correlated with the information available in other products:
- Firewall logs from Strata Logging Service, Panorama, and Splunk.
- User information from Active Directory.
- Public IP address from AWS/GCP/Azure public IP feeds to identify the Public Cloud region and service (i.e., us-west-1 on AWS EC2).
- IP and FQDN from Prisma Cloud inventory.
3. Shadow IT check: based on the information found, the playbook can suggest whether the discovered issue corresponds to an asset that is known to the InfoSec team (i.e., there are firewall logs present, or the asset is protected by Prisma Cloud, or is part of an IP range associated to the company).
4. Attribution: based on the information collected above, the analyst is prompted to assign this issue to an Organization Unit, which is a group within the company with a specific owner. The analyst can choose from existing Organization Units (stored in an XSOAR list) or define a new one.
5. Response: depending on the issue type, several remediation actions can be automatically and manually performed, such as:
- Tagging the asset in Expanse with a specific Organization Unit tag.
- Blocking the service on PAN-OS (if a firewall is deployed in front of the service).
- Creating a new Shadow IT issue (if the asset is detected to be Shadow IT and the analyst confirms it)
- Adding the service to a Vulnerability Management system
- Linking the incident to a related Prisma Cloud alert for the asset (if the asset is found under Prisma Cloud inventory)
- Bringing rogue cloud accounts under management
Handle Expanse Incident - Attribution OnlyShorter version of Handle Expanse Incident playbook with only the Attribution part.

There are several phases:
1. Enrichment: all the related information from the incident is extracted and related Indicators (of types IP, CIDR, Domain, DomainGlob, Certificate) are created and enriched.
2. Validation: the found IP and FQDN are correlated with the information available in other products:
- Firewall logs from Strata Logging Service, Panorama and Splunk
- User information from Active Directory
- Public IP address from AWS/GCP/Azure public IP feeds to identify the Public Cloud region and Service (i.e. us-west-1 on AWS EC2)
- IP and FQDN from Prisma Cloud inventory
3. Shadow IT check: based on the information found, the playbook can suggest whether the discovered issue corresponds to an asset that is known to the InfoSec team (i.e. there are firewall logs present, or the asset is protected by Prisma Cloud, or is part of an IP range associated to the Company).
4. Attribution: based on the information collected above, the Analyst is prompted to assign this issue to an Organization Unit, that is a group within the Company with a specific owner. The Analyst can choose from existing Organization Units (stored in an XSOAR list) or define a new one.
Handle False Positive AlertsThis playbook handles false positive alerts.
It creates an alert exclusion or alert exception, or adds a file to an allow list based on the alert fields and playbook inputs.
Handle Hello World AlertThis is a playbook which will handle the alerts coming from the Hello World service
Handle Shadow IT IncidentThis Playbook is used to handle a Shadow IT incident. A Shadow IT incident occurs when a resource attributed to the organization that is not sanctioned by IT nor protected by the InfoSec team is found.

This playbook handles the incident by helping the analyst to find the owner of the resource based on existing evidence. The playbook also marks the service indicators (IP or FQDN) with a Shadow IT tag. The possible owner and their manager are notified and onboarding of the asset on Prisma Cloud is triggered through a manual process.
Handle TD eventsPlaybook to enrich TD events
Health Check - Collect Log BundleCollect Log bundle and parse data
Health Check - Log Analysis Read All filesParse files from log bundle output
HealthCheckNew version for HealthCheck main playbook
HelloWorld ScanDeprecated. No available replacement.
HIPAA - Breach NotificationUSA Health Insurance Portability and Accountability Act of 1996 (HIPAA) covers organizations that use, store, or process Private Health Information (PHI).
The HIPAA Breach Notification Rule requires companies that deal with health information to disclose cybersecurity breaches; the disclosure will include notification to individuals, to the media, and the Secretary of Health and Human Services.
This playbook is triggered by a HIPAA breach notification incident and follows through with the notification procedures.

DISCLAIMER: Please consult with your legal team before implementing this playbook.

** Source: https://www.hhs.gov/hipaa/for-professionals/breach-notification/index.html
Hostname And IP Address Investigation And Remediation - ChronicleThis playbook receives ChronicleAsset type of indicators from its parent playbook "ChronicleAsset Investigation - Chronicle", performs enrichment and investigation for each one of them, provides an opportunity to isolate and block the hostname or IP address associated with the current indicator, and provides a list of isolated and blocked entities.
Humio QueryJob PollRun and poll a Humio Query Job
Hunt Extracted HashesDeprecated. Use the Hunt Extracted Hashes V2 playbook instead. This playbook extracts IOCs from the incident details and attached\ \ files using regular expressions and then hunts for hashes on endpoints in the organization\ \ using available tools.\nThe playbook supports multiple types of attachments. For\ \ the full supported attachments list, refer to \"Extract Indicators From\ \ File - Generic v2\".
Hunt Extracted Hashes V2This playbook extracts IOCs from the incident details and attached files using regular expressions and then hunts for hashes on endpoints in the organization using available tools.
The playbook supports multiple types of attachments. For the full supported attachments list, refer to "Extract Indicators From File - Generic v2".
Hunt for bad IOCsDeprecated. Use the Search Endpoints By Hash playbook. Assume that malicious IOCs are in the right place in the context and start hunting using available tools.
Hunting C&C Communication PlaybookDeprecated. A playbook to use the latest Threat Intelligence to hunt across your infrastructure and look for malicious C&C communications.
Hurukai - Add indicators to HarfangLab EDRThis playbook add indicators to a HarfangLab EDR IOC source list for detection and/or blocking.
Hurukai - Alert managementManager security events from HarfangLab EDR
Hurukai - Get All ArtifactsBuild a global archive with:
- MFT (Windows)
- Hives (Windows)
- USN logs (Windows)
- Prefetch files (Windows)
- EVT/EVTX files (Windows)
- Log files (Linux)
- Filesystem content (Linux)
Hurukai - Get Artifact EvtxGet Evt/evtx log files
Hurukai - Get Artifact FilesystemGet a CSV list of files in a Linux filesystem
Hurukai - Get Artifact HivesGet the RAW hives
Hurukai - Get Artifact LogsGet all the log files
Hurukai - Get Artifact MFTGet the raw MFT
Hurukai - Get Artifact RAM DumpGet a RAM dump from Windows and Linux endpoints.
Hurukai - Get Driver ListGet the list of loaded drivers
Hurukai - Get Network Connection ListGet the list of active network connections
Hurukai - Get Network Share ListGet the list of network shares
Hurukai - Get Persistence ListGet the list of persistence means
Hurukai - Get Pipe ListGet the list of named pipes
Hurukai - Get Prefetch ListGet the list of prefetch files
Hurukai - Get Process ListGet the list of processes
Hurukai - Get Runkey ListGet the list of RUN keys
Hurukai - Get Scheduled Task ListGet the list of scheduled tasks
Hurukai - Get Service ListGet the list of services
Hurukai - Get Session ListGet the list of active sessions
Hurukai - Get Startup ListGet the list of startup files
Hurukai - Get WMI ListGet the list of WMI items
Hurukai - Hunt IOCsThis playbook allows is triggered by the Hurukai - Process Indicators - Manual Review playbook. It allows to search for IOC sightings in the HarfangLab EDR and tag sighted IOCs accordingly for manual review. All IOCs are tagged in order to be further inserted into a HarfangLab EDR IOC source.
Hurukai - Process Indicators - Manual ReviewThis playbook tags indicators ingested by feeds that require manual approval. The playbook is triggered due to a job. The indicators are tagged as requiring a manual review. The playbook optionally concludes with creating a new incident that includes all of the indicators that the analyst must review.
To enable the playbook, the indicator query needs to be configured. An example query is a list of the feeds whose ingested indicators should be manually reviewed. For example, sourceBrands:"Feed A" or sourceBrands:"Feed B".
Hybrid-analysis quick-scanDeprecated. No available replacement.
Identity Analytics - Alert HandlingThe `Identity Analytics - Alert Handling` playbook is designed to handle Identity Analytics alerts and executes the following:

Analysis:
- Enriches the IP and the account, providing additional context and information about these indicators.

Verdict:
- Determines the appropriate verdict based on the data collected from the enrichment phase.

Investigation:
- Checks for related XDR alerts to the user by Mitre tactics to identify malicious activity.
- Checks for specific arguments for malicious usage from Okta using the 'Okta User Investigation' sub-playbook.
- Checks for specific arguments for malicious usage from Azure using the 'Azure User Investigation' sub-playbook.

Verdict Handling:
- Handles malicious alerts by initiating appropriate response actions, including blocking malicious IP and revoking or clearing user's sessions.
- Handles non-malicious alerts identified during the investigation.
Illinois - Breach NotificationThis playbook helps an analyst determine if the breached data meets the criteria for breach notification according to Illinois law, and, if necessary, follows through with the notification procedures.

DISCLAIMER: Please consult with your legal team before implementing this playbook.

Source: http://www.ilga.gov/legislation/ilcs/ilcs3.asp?ActID=2702&ChapAct=815%C2%A0ILCS%C2%A0530/&ChapterID=67&ChapterName=BUSINESS+TRANSACTIONS&ActName=Personal+Information+Protection+Act.
https://www.mintz.com/newsletter/2007/PrivSec-DataBreachLaws-02-07/state_data_breach_matrix.pdf
Illusive - Data EnrichmentThis playbook is used for automatic enrichment of incidents in the organization network, with Illusive's set of forensics and data
Illusive - Incident EscalationThis playbook is used for creating an automatic analysis of the Illusive's incident details, in order to end up with a certain score or a set of insights that will enable automatic decisions and actions.
Illusive-Collect-Forensics-On-DemandThis playbook is used to collect forensics on-demand on any compromised host and retrieve the forensics timeline upon successful collection.
Illusive-Retrieve-IncidentThis playbook is used for retrieving an extensive view over a detected incident by retrieving the incident details and a forensics timeline if and when forensics have been successfully collected.
Impossible TravelerThis playbook investigates an event whereby a user has multiple application login attempts from various locations in a short time period (impossible traveler). The playbook gathers user, timestamp and IP information
associated with the multiple application login attempts.

The playbook then measures the time difference between the multiple login attempts and computes the distance between the two locations to verify whether it is possible the user could traverse the distance
in the amount of time determined. Also, it takes steps to remediate the incident by blocking the offending IPs and disabling the user account, if chosen to do so.
Impossible Traveler - EnrichmentThis playbook get as an input all of the involved IP addresses and identities from the Impossible Traveler playbook alert, and enriches them based on the following:
Geo location
Active Directory
* IP enrichment e.g. VirusTotal, AbuseIPDB, etc.
Impossible Traveler ResponseThis playbook handles impossible traveler alerts.

An Impossible Traveler event occurs when multiple login attempts seen for a user from multiple remote countries in a short period of time, which shouldn't be possible. This may indicate the account is compromised.

Attacker's Goals:

Gain user-account credentials.

Investigative Actions:

Investigate the IP addresses and identities involved in the detected activity using:

Impossible Traveler - Enrichment playbook
CalculateGeoDistance automation

Response Actions

The playbook's first response actions are based on the data available within the alert. In that phase, the playbook will execute:

Manual block indicators if the IP address found malicious
Manual disable user
Manual clear of the user’s sessions (Okta)

When the playbook continues, after validating the activity with the user’s manager, another phase of response actions is being executed, which includes:

Auto block indicators


External Resources:

Impossible traveler alert
Incident Postprocessing - Group-IB Threat Intelligence & AttributionObtains additional information on the threat actor involved in the incident and associates related indicators to the incident.
Incremental Export Devices to ServiceNow - PANW IoT 3rd Party IntegrationPlaybook to be run every 15 minutes via a job. Each run will get incremental updates for devices to send to ServiceNow server.
Incremental Export to Cisco ISE - PANW IoT 3rd Party IntegrationPlaybook to be run every 15 minutes via a job. Each run will get incremental updates for devices, and will update or create new endpoints in Cisco ISE with PANW IOT discovered attributes (ISE custom attributes).
Incremental Export to SIEM - PANW IoT 3rd Party IntegrationThis playbook should be run as a job at an interval of every 15 minutes. Each run will get incremental updates for devices, alerts, and vulnerabilities and send CEF syslogs to the configured SIEM server.
Indicator Enrichment - QintelEnriches indicators from Qintel products
Indicator Pivoting - DomainTools IrisPivots are used to gather data that share a common attribute with a domain. For instance, pivoting on an IP Address will give you back all domains related to that IP address.
Indicator Registration Polling - GenericThis playbook polls all indicators to check if they exist.
Integration TroubleshootingTroubleshoot a problem with either an integration's configuration or with running a command.
Integrations and Incidents Health Check - Running ScriptsThis playbook is triggered by a 'JOB - Integrations and Playbooks Health' playbook and is responsible for running failed integrations and failed incidents scripts. The playbook may run separately from the main playbook to run health tests on enabled integrations and open incidents.
Intezer - Analyze by hashAnalyze the given file hash on Intezer Analyze and enrich the file reputation. Supports SHA256, SHA1, and MD5.
Intezer - Analyze File and URLAnalyze Files and URLs on Intezer Analyze
Intezer - Analyze Uploaded fileUpload a file to Intezer Analyze to analyze and enrich the file reputation. (up to 150 MB)
Investigate On Bad Domain Matches - ChronicleUse this playbook to investigate and remediate Bad IOC domain matches with recent activity found in the enterprise, as well as notify the SOC lead and network team about the matches.
Supported Integrations:
- Chronicle
- Whois
- Mail Sender (New)
- Palo Alto Networks PAN-OS
- Palo Alto Networks AutoFocus v2
IOC AlertIOCs provide the ability to alert on known malicious objects on endpoints across the organization.

Analysis Actions:
The playbook will use several enrichment sources to determine the IOC verdict. Additionally, will use the Analytics module to run a prevalence check for the IOC.

Response Actions:
The playbook's first response action is a containment plan that is based on the playbook input. In that phase, the playbook will execute endpoint isolation

Investigative Actions:
When the playbook executes, it checks for additional abnormal activity using the Endpoint Investigation Plan playbook that can indicate the endpoint might be compromised.

Remediation Actions:
In case results are found within the investigation phase, the playbook will execute remediation actions that include containment and eradication.

This phase will execute the following containment actions:

File quarantine
Endpoint isolation

And the following eradication actions:

Manual process termination
Manual file deletion
IP Enrichment - External - Generic v2Enrich IP addresses using one or more integrations.

- Resolve IP addresses to hostnames (DNS).
- Provide threat information.
- IP address reputation using !ip command.
- Separate internal and external addresses.
IP Enrichment - External - RST Threat FeedEnrich IP addresses using one or more integrations.

- Resolve IP addresses to hostnames (DNS)
- Provide threat information
- Separate internal and external addresses
IP Enrichment - GenericDeprecated. Enrich IP using one or more integrations.

IP enrichment includes:
Resolve IP to Hostname (DNS)
Threat information
Separate internal and external addresses
IP reputation
* For internal addresses, get host information
IP Enrichment - Generic v2Enrich IP addresses using one or more integrations.

- Resolve IP addresses to hostnames (DNS)
- Provide threat information
- Determine IP address reputation using the !ip command
- Separate internal and external IP addresses
- For internal IP addresses, get host information.

When executing this playbook through IP Enrichment - Generic v2, IP classification and resolution will be handled by the main playbook, improving performance.
IP Enrichment - Internal - Generic v2Enrich Internal IP addresses using one or more integrations.

- Resolve IP address to hostname (DNS)
- Separate internal and external IP addresses
- Get host information for IP addresses.
IP Reputation-GreyNoisePlaybook for the ip reputation command
IP Whitelist - AWS Security GroupSync a list of IP addresses to an AWS Security Group.
IP Whitelist - GCP FirewallSet a list of IP addresses in GCP firewall.
IP Whitelist And Exclusion - RiskIQ Digital FootprintAdds the IP Address(es) to allow list after checking if it should be added to allow list according to the user inputs provided. This playbook also adds these IP Address indicators to the exclusion list and tags it with the "RiskIQ Whitelisted IP Address" tag.
IQ-HUB AutomationThis playbook is used to retrieve real-time detections and progressions data generated by events on different systems present in the network.
Ironscales-Classify-IncidentClassify an Ironscales incident
Isolate Endpoint - CybereasonThis playbook isolates a machine based on the hostname provided.
Isolate Endpoint - GenericDeprecated. Use the "Isolate Endpoint - Generic V2" playbook instead.
Isolate Endpoint - Generic V2This playbook isolates a given endpoint using various endpoint product integrations.
Make sure to provide valid playbook inputs for the integration you are using.
IT - Employee OffboardingThis playbook offboards company employees to maintain organizational security and prevent abuse of company resources. It streamlines the process of returning company property, delegates resources to the employee's manager, retains important data that is in possession of the employee, and deletes the user and user information if chosen to do so.
IT - Employee Offboarding - ManualThis playbook provides a manual alternative to the IT - Employee Offboarding playbook. The playbook guides the user in the process of manually offboarding an employee.
Ivanti Critical VulnerabilitiesIvanti has recently disclosed four critical vulnerabilities in their VPN devices, identified as CVE-2023-46805, CVE-2024-21887, CVE-2024-21888, and CVE-2024-21893, with active exploitation reported. These security flaws impact all supported versions of Ivanti Connect Secure and Ivanti Policy Secure gateways, including versions 9.x and 22.x, and Ivanti Neurons for ZTA.

#### Disclosed Vulnerabilities

CVE-2023-46805, a high-severity vulnerability, allows attackers to bypass authentication checks in the web component, granting access to restricted resources without credentials.

CVE-2024-21887, of critical severity, enables command injection through specially crafted requests by authenticated administrators, leading to arbitrary command execution.

CVE-2024-21888, another critical vulnerability, permits privilege escalation within the web component, enabling users to gain administrative rights.

CVE-2024-21893 exposes a server-side request forgery (SSRF) vulnerability within the SAML component, allowing unauthorized access to specific restricted resources.

The combination of these vulnerabilities, particularly CVE-2023-46805 and CVE-2024-21887, facilitates attackers to execute commands on the compromised system sans authentication, posing a significant security risk. Organizations utilizing affected Ivanti products are urged to apply mitigations and patches to safeguard their systems against potential exploits.

This playbook should be triggered manually or can be configured as a job.

IoCs Collection
- Unit42 IoCs download

Hunting
- PANW Hunting:
- Panorama Threat IDs hunting
- Cortex Xpanse issues hunting
- Indicators hunting
- Endpoints by CVE hunting

Mitigations

Ivanti recommended workaround and patch.

References

Unit42 Threat Brief: Multiple Ivanti Vulnerabilities

CVE-2023-46805 (Authentication Bypass) & CVE-2024-21887 (Command Injection) for Ivanti Connect Secure and Ivanti Policy Secure Gateways

Note: This is a beta playbook, which lets you implement and test pre-release software. Since the playbook is beta, it might contain bugs. Updates to the pack during the beta phase might include non-backward compatible features. We appreciate your feedback on the quality and usability of the pack to help us identify issues, fix them, and continually improve.
Jira Change ManagementIf you are using PAN-OS/Panorama firewall and Jira as a ticketing system, this playbook will be a perfect match for your change management for firewall process.
This playbook is triggered by afetch from Jira and will help you manage and automate your change management process.
Jira Ticket State PollingUse Jira Incident State Polling as a sub-playbook when required to pause the execution of a master playbook until the Jira ticket state is either resolved or closed.
This playbook implements polling by continuously running the jira-get-issue command until the state is either resolved or closed.
JOB - Cortex XDR query endpoint device control violationsA job to periodically query Cortex XDR device control violations by a given timestamp in a relative date playbook input.
The collected data, if found, will be generated for a new incident.
You can configure the created new incident type in the playbook input and use the XDR Device Control Violations incident type to associate it with the response playbook.
The job includes an incident type with a dedicated layout to visualize the collected data.
To configure the job correctly:
1. Create a new recurring job.
2. Configure the recurring schedule.
3. Add a name.
4. Configure the type to XDR Device Control Violations.
5. Configure this playbook as the job playbook.
The scheduled run time and the timestamp relative date should be identical.
If the job recurs every 7 days, the timestamp should be 7 days as well.
JOB - Integrations and Incidents Health CheckYou should run this playbook as a scheduled job. The playbook checks the health of all enabled integrations and open incidents.
JOB - Integrations and Incidents Health Check - Lists handlingThis playbook is triggered by a 'JOB - Integrations and Playbooks Health' playbook and is responsible for creating or updating related XSOAR lists.
JOB - PANW NGFW TS Agent CleanupRun this playbook as a job to cleanup disconnected TS Agents
JOB - Popular NewsPlaybook can be run ad-hoc or as a Job to fetch results from Popular News sites
JOB - XSOAR - Export Selected Custom ContentThis playbook is intended to be run as an adhoc job to quickly create a custom content bundle with only selected items from the servers custom content.

Then you can import this new zip on the other XSOAR server.

Create a Job with the Type “XSOAR Dev to Prod”, and select this playbook to get started. For more information on Jobs: https://xsoar.pan.dev/docs/incidents/incident-jobs
JOB - XSOAR - Simple Dev to ProdThis playbook is intended to be run as an adhoc job to quickly create a custom content bundle with only selected items from the servers custom content. You can import this new zip on the other XSOAR server, or push it to production using the Core REST API integration.

Please ensure to read the setup instructions for this pack carefully.

Create a Job with the Type “XSOAR Dev to Prod”, and select this playbook to get started. For more information on Jobs: https://xsoar.pan.dev/docs/incidents/incident-jobs
JOB - XSOAR EDL CheckerThis playbook executes the XSOAR EDL Checker automation and will send email notification when an EDL is not functioning.

Run this playbook as a job to monitor your EDLs.
Kaseya VSA 0-day - REvil Ransomware Supply Chain AttackOn July 2nd, Kaseya company has experienced an attack against the VSA (Virtual System/Server Administrator) product. Kaseya customers pointed out a ransomware outbreak in their environments.
Further investigation revealed that REvil group exploited VSA zero-day vulnerabilities for authentication bypass and arbitrary command execution. This allowed the attacker to deploy ransomware on Kaseya customers' endpoints.

This playbook should be trigger manually and includes the following tasks:

Collect related known indicators from several sources.
Indicators, PS commands, Registry changes and known HTTP requests hunting using PAN-OS, Cortex XDR and SIEM products.
Splunk advanced queries can be modified through the playbook inputs.
QRadar query is done using Reference Set and "QRadar Indicator Hunting V2" playbook
Search for internet facing Kaseya VSA servers using Xpanse.
Block indicators automatically or manually.
Provide advanced hunting and detection capabilities.
Mitigation using Kaseya On-Premises and SaaS patch.

More information:
Kaseya Incident Overview & Technical Details

Note: This is a beta playbook, which lets you implement and test pre-release software. Since the playbook is beta, it might contain bugs. Updates to the pack during the beta phase might include non-backward compatible features. We appreciate your feedback on the quality and usability of the pack to help us identify issues, fix them, and continually improve.
Kenna - Search and Handle Asset VulnerabilitiesThis playbook accepts an asset, then searches for vulnerabilities on that asset using the Kenna integration. If a vulnerability exists, it looks for relevant patches, lets the analyst deploy them and then generates an investigation summary report.
Large Upload AlertThe playbook investigates Cortex XDR incidents involving large upload alerts.
The playbook consists of the following procedures:
- Searches for similar previous incidents that were closed as false positives.
- Enrichment and investigation of the initiator and destination hostname and IP address.
- Enrichment and investigation of the initiator user, process, file, or command if it exists.
- Detection of related indicators and analysis of the relationship between the detected indicators.
- Utilize the detected indicators to conduct threat hunting.
- Blocks detected malicious indicators.
- Endpoint isolation.
This playbook supports the following Cortex XDR alert names:
- Large Upload (Generic)
- Large Upload (SMTP)
- Large Upload (FTP)
- Large Upload (HTTPS)
Launch Adhoc Command Generic - Ansible Automation PlatformGeneric polling playbook for runing ad hoc commands. Ad-hoc commands in Ansible allows you to execute simple tasks at the command line against one or all of your hosts. This playbook first launchrd an ad hoc command, then reportd the status of the task when it finishes running, and at the end returns the output of the task.
Launch And Fetch Compliance Policy Report - QualysLaunches a compliance policy report and then fetches the report when it's ready.
Launch And Fetch Compliance Report - QualysLaunches a compliance report and fetches the report when it's ready.
Launch And Fetch Host Based Findings Report - QualysLaunches a host based report and fetches the report when it's ready.
Launch And Fetch Map Report - QualysLaunches a map scan report and fetches the report when it's ready.
Launch And Fetch Patch Report - QualysLaunches a patch report and fetches the report when it's ready.
Launch And Fetch PC Scan - QualysLaunches a PC scan and fetches the scan when it's ready.
Launch And Fetch Remediation Report - QualysLaunches a remediation report and fetches the report when it's ready.
Launch And Fetch Scan Based Findings Report - QualysLaunches a scan based report and fetcesh the report when it's ready.
Launch And Fetch Scheduled Report - QualysLaunches a scheduled report and fetches the report when it's ready.
Launch And Fetch VM Scan - QualysLaunches a scan and fetches the scan when it's ready.
Launch Job - Ansible Automation PlatformGeneric polling playbook to launch a specific job template. Returns the job status when the job finishes running.
Launch Scan - Tenable.scDeprecated. Use tenable-sc-launch-scan-report command instead.
List Cisco Stealthwatch Security EventsThis playbook lists security events and returns the results to the context.
List Device Events - ChronicleThis playbook receives ChronicleAsset identifier information and provides a list of events related to each one of them.
Supported integration:
- Chronicle
Local Analysis alert InvestigationWhen an unknown executable, DLL, or macro attempts to run on a Windows or Mac endpoint, the Cortex XDR agent uses local analysis to determine if it is likely to be malware. Local analysis uses a static set of pattern-matching rules that inspect multiple file features and attributes, and a statistical model that was developed with machine learning on WildFire threat intelligence.

Investigative Actions:

Investigate the executed process image and verify if it is malicious using:

XDR trusted signers
VT trusted signers
VT detection rate
NSRL DB

Response Actions

The playbook's first response action is a containment plan that is based on the initial data provided within the alert. In that phase, the playbook will execute:

Auto block indicators
Auto file quarantine
Manual endpoint isolation

When the playbook executes, it checks for additional activity using the Endpoint Investigation Plan playbook, and another phase, which includes containment and eradication, is executed.

This phase will execute the following containment actions:

Manual block indicators
Manual file quarantine
Auto endpoint isolation

And the following eradication actions:

Manual process termination
Manual file deletion
* Manual reset of the user’s password

External resources:

Malware Protection Flow
LogPoint SIEM PlaybookLogPoint SIEM Playbook guides users on use cases like blocking IP and domain and disabling users using products like CheckPoint Firewall, Active Directory, and VirusTotal. The actions depicted in the playbook helps analysts create their playbooks based on actual requirements and products deployed. (Available from Cortex XSOAR 6.0.0).
Logrhythm - Search queryThis playbook used generic polling to gets query result using the command: lr-execute-search-query
LogRhythmRestV2 - Search queryThis playbook used generic polling to get query results using the command: lr-execute-search-query.
Logz.Io Handle AlertHandles a Logz.io Alert by retrieving the events that generated it.
Logz.io Indicator HuntingThis playbook queries Logz.io in order to hunt indicators such as
File Hashes
IP Addresses
Domains \ URLS
And outputs the related users, IP addresses, host names for the indicators searched.
Lost / Stolen Device PlaybookThis manual playbook handles an incident for a lost or stolen device. It guides the analyst through various steps to validate the type of device and its contents, and the required steps for response and remediation. Initial incident details should be the name of the reporting person or ID of the SIEM alert/incident, and description of the lost device.
LSASS Credential DumpinThis playbook is focused on detecting Credential Dumping attack as researched by Accenture Security analysts and engineers.
Malware Investigation & Response Incident HandlerThis playbook is triggered by a malware incident from an endpoint integration. It performs enrichment, detonation, and hunting within the organization, and remediation on the malware.
The playbook also covers the SIEM ingestion flow in which the fetching integration is the SIEM and EDR integrations grab all additional data.
Currently supported EDR integrations are XDR, CrowdStrike Falcon, and Microsoft Defender for Endpoint.
Currently supported SIEM integrations are QRadar and Splunk.
Malware Investigation - GenericDeprecated. Use "Endpoint Malware Investigation - Generic" playbook instead. Investigate a malware using one or more integrations
Malware Investigation - Generic - SetupDeprecated. Verify file sample and hostname information for the "Malware Investigation - Generic" playbook.
If the file sample or hostname are missing, the playbook will attempt to retrieve them using one or more integrations
Malware Investigation - ManualDeprecated. Use 'Malware Investigation & Response Incident handler' instead. (From the 'Malware Investigation And Response Pack')
Master playbook for investigating suspected malware presence on an endpoint.
Labels:
- System: the hostname for the endpoint being investigated
Malware Investigation and Response - Set Alerts GridThis playbook sets the alert grid for the Malware Investigation & Response layout.
Malware Playbook - ManualDeprecated. Use "Malware Investigation - Manual" playbook instead. Master playbook for investigating suspected malware presence on an endpoint.
Labels:
- System: the hostname for the endpoint being investigated
Malware SIEM Ingestion - Get Incident DataThis playbook handles incident ingestion from the SIEM.
The user provides which EDR system to use, the field containing the incident ID or detection ID, and the field indicating whether the ingested item is an incident or detection.
Malware Triage - ReversingLabs TitaniumCloudProvides the TitaniumCloud classification of a file hash, and takes remediation actions based on that classification.
MAR - Endpoint data collectionUse McAfee Active Response to collect data from an endpoint for IR purposes (requires ePO as well).

Input:
* Hostname (Default: ${Endpoint.Hostname})
McAfee ePO Endpoint Compliance PlaybookDeprecated. Use "McAfee ePO Endpoint Compliance Playbook v2" playbook instead. Discover endpoints that are not using the latest McAfee AV Signatures
McAfee ePO Endpoint Compliance Playbook v2Discover endpoints that are not using the latest McAfee AV signatures.
McAfee ePO Endpoint Connectivity Diagnostics Playbook v2Perform a check on ePO endpoints to see if any endpoints are unmanaged or lost connectivity with ePO and take steps to return to a valid state.
McAfee ePO Repository Compliance PlaybookDeprecated. Use "McAfee ePO Repository Compliance Playbook v2" playbook instead. Ensures that ePO servers are updated to the latest McAfee published AV signatures (DAT file version).
McAfee ePO Repository Compliance Playbook v2Ensures that ePO servers are updated to the latest McAfee published AV signatures (DAT file version).
MDE - Block FileThis playbook receives an MD5 or a SHA256 hash and adds it to the block list in Microsoft Defender for Endpoint.
The playbook uses the integration "Microsoft Defender for Endpoint".
MDE - False Positive Incident HandlingThis playbook is part of the 'Malware Investigation And Response' pack. For more information, refer to https://xsoar.pan.dev/docs/reference/packs/malware-investigation-and-response.
This playbook handles closing false positive incidents for Microsoft Defender for Endpoint.
MDE - Host Advanced HuntingThis playbook is part of the 'Malware Investigation And Response' pack. For more information, refer to https://xsoar.pan.dev/docs/reference/packs/malware-investigation-and-response.
This playbook uses the Microsoft Defender For Endpoint Advanced Hunting feature based on the provided inputs.
MDE - Host Advanced Hunting For Network ActivityThis playbook is part of the 'Malware Investigation And Response' pack. For more information, refer to https://xsoar.pan.dev/docs/reference/packs/malware-investigation-and-response.
This playbook uses the Microsoft Defender For Endpoint Advanced Hunting feature to hunt for host network activity.
MDE - Host Advanced Hunting For PersistenceThis playbook is part of the 'Malware Investigation And Response' pack. For more information, refer to https://xsoar.pan.dev/docs/reference/packs/malware-investigation-and-response.
This playbook uses the Microsoft Defender For Endpoint Advanced Hunting feature to hunt for host persistence evidence.
MDE - Host Advanced Hunting For Powershell ExecutionsThis playbook is part of the 'Malware Investigation And Response' pack. For more information, refer to https://xsoar.pan.dev/docs/reference/packs/malware-investigation-and-response.
This playbook uses the Microsoft Defender For Endpoint Advanced Hunting feature to hunt for host PowerShell executions.
MDE - Pro-Active ActionsThis playbook is part of the 'Malware Investigation And Response' pack. For more information, refer to https://xsoar.pan.dev/docs/reference/packs/malware-investigation-and-response.
This playbook supports investigation actions for the analyst, including:
- Running a full AV scan for a specific endpoint
- Requesting an investigation package (a zip file containing forensic data with a size of ~ 15MB) from an endpoint.
- Requesting to run automatic investigation on an endpoint.
MDE - Retrieve FileThis playbook is part of the ‘Malware Investigation And Response’ pack. For more information, refer to https://xsoar.pan.dev/docs/reference/packs/malware-investigation-and-response.
This playbook uses the Live Response feature to retrieve a file from an endpoint. The playbook supports a supplied machine id as an input. Otherwise, it will take the Device ID incident field.
The playbook supports only one element to be retrieved for each task (if needed more then one - use the playbook loop feature).
MDE - Search And Block SoftwareThis playbook will search a file or process activity of a software by a given image file name using Microsoft Defender For Endpoint. The analyst can then choose the files to block.
MDE - Search and Compare Process ExecutionsThis playbook is a generic playbook that receives a process name and a command-line argument. It uses the "Microsoft Defender For Endpoint" integration to search for the given process executions and compares the command-line argument from the results to the command-line argument received from the playbook input.

Note: Under the "Processes", input the playbook should receive an array that contains the following keys:
- value: process name
- commands: command-line arguments
MDE - True Positive Incident HandlingThis playbook is part of the 'Malware Investigation And Response' pack. For more information, refer to https://xsoar.pan.dev/docs/reference/packs/malware-investigation-and-response.
This Playbook handles closing a true positive incident for Microsoft Defender for Endpoint.
MDE Malware - Incident EnrichmentThis playbook is part of the 'Malware Investigation And Response' pack. For more information, refer to https://xsoar.pan.dev/docs/reference/packs/malware-investigation-and-response.
This playbook enriches Microsoft Defender For Endpoint alerts. The enrichment is done on the involved endpoint and Mitre technique ID information, and it sets the 'Malware-Investigation and Response' layout.
MDE Malware - Investigation and ResponseThis playbook is part of the 'Malware Investigation And Response' pack. For more information, refer to https://xsoar.pan.dev/docs/reference/packs/malware-investigation-and-response.
This playbook investigates Microsoft Defender For Endpoint malware alerts. It uses - Microsoft Defender For Endpoint Advanced Hunting - Command Line Analysis - Deduplication - Sandbox hash search and detonation - Proactive investigation actions (AV scan, investigation package collection, running automated investigation on an endpoint) - Microsoft Defender For Endpoint alert enrichment - Incident handling (true/false positive)
MDE SIEM ingestion - Get Incident DataThis playbook is part of the 'Malware Investigation And Response' pack. For more information, refer to https://xsoar.pan.dev/docs/reference/packs/malware-investigation-and-response.
This playbook handles incident ingestion from a SIEM. The user provides the incident fields containing the alert ID. This playbook also enables changing the severity according to a user-defined scale to override the default assigned severity.
Message Quarantine - Cofense VisionThis playbook allows users to quarantine various messages that meet their specified criteria.
Microsoft 365 Defender - Emails Indicators HuntThis playbook retrieves email data based on the "URLDomain", "SHA256" and "IPAddress" inputs.
SHA256 - Emails with attachments matching the "SHA256" input are retrieved.
URLDomain - If the "URLDomain" value is found as a substring of URL(s) in the body of the email, the email is retrieved.
IPAddress - Emails with "SenderIPv4"/SenderIPv6" or URLs (in the body) matching the "IPAddress" input are retrieved.
Microsoft 365 Defender - Get Email URL ClicksThis playbook retrieves email data based on the `URLDomain` and `MessageID` inputs. It uses the Microsoft 365 Defender's Advanced Hunting to search only for URL click events based on the playbook inputs and enriches it with the full email data.

URLDomain - If the “URLDomain” value is found as a substring of the URL(s) in the body of the email, the email is retrieved.

MessageID - The message ID of the email from which the URL was clicked. Note that this can be either of the following 2 values:
- The value of the header "Message-ID".
- The internal ID of the message within Microsoft's products (e.g., NetworkMessageId).

Can be a single MessageID or an array of MessageIDs to search.
Microsoft 365 Defender - Threat Hunting GenericThis playbook retrieves email data based on the `URLDomain`, `SHA256`, `IPAddress`. and `MessageID` inputs. The output is a unified object with all of the retrieved emails based on the following sub-playbooks outputs:

- Microsoft 365 Defender - Get Email URL clicks:
Retrieves data based on URL click events.


- Microsoft 365 Defender - Emails Indicators Hunt:
Retrieves data based on several different email events.

Read the playbook's descriptions in order to get the full details.
Microsoft Defender Advanced Threat Protection Get Machine Action StatusThis playbook used generic polling to get machine action information.
Microsoft Defender For Endpoint - Collect investigation packageThis playbook simplifies retrieving investigation packages to Cortex XSOAR from supported machines (See https://docs.microsoft.com/en-us/microsoft-365/security/defender-endpoint/collect-investigation-package?view=o365-worldwide).

The playbook receives information about the target devices (host name, IP, and device ID), validates the devices exist, and retrieves the collection package from those machines into the Cortex XSOAR console.
Note: This action may take time, the average package size is around ~15 MB.
Microsoft Defender For Endpoint - Isolate EndpointThis playbook accepts an endpoint ID, IP, or host name and isolates it using the Microsoft Defender For Endpoint integration.
Microsoft Defender for Endpoint - Malware DetectedThis playbook investigates “Malware detected by Microsoft Defender for Endpoint” by gathering Hash and User information and performing remediation based on the information gathered and received from the enrichment.

Used Sub-playbooks:
* Enrichment for Verdict

To link this playbook to the relevant alerts automatically, we recommend using the following filters when configuring the playbook triggers: Alert Source = Correlation AND Alert Name = Malware detected by Microsoft Defender for Endpoint
Microsoft Defender For Endpoint - Unisolate EndpointThis playbook accepts an endpoint ID, IP, or host name and unisolates it using the Microsoft Defender For Endpoint integration.
Microsoft Office File Enrichment - OletoolsOletools is a tool for analyzing Microsoft OLE2 files, such as Microsoft Office documents or Outlook messages, mainly for malware analysis, forensics, and debugging.
This playbook will run run the "oleid" command on the files which are passed to to it as playbook inputs. In case any macros or external relationships were found, it will also run "olevba" and "oleobj" commands as well on the relevant files.
oleid - Analyze OLE files to detect specific characteristics usually found in malicious files.
oleobj - Extract embedded objects from OLE files.
olevba - Extract and analyze VBA Macro source code from MS Office documents (OLE and OpenXML).
Mimecast - Block Sender DomainA playbook to block sender domain name using Mimecast integration.
Mimecast - Block Sender EmailA playbook to block sender email address using Mimecast integration.
Mirror Jira TicketMirror Jira Ticket is designed to serve as a sub-playbook, which enables ticket mirroring with Jira.
Mirror ServiceNow TicketMirror ServiceNow Ticket is designed to serve as a sub-playbook, which enables ticket mirroring with ServiceNow.
It enables you to manage ServiceNow tickets in Cortex xSOAR while data is continuously synced between ServiceNow and Cortex xSOAR, including ServiceNow schema, fields, comments, work notes, and attachments.

To enable OOTB mirroring, use the ServiceNow Create ticket - common mappers for incoming and outgoing mirroring.

FieldPolling - You can the FieldPolling value to true if you only want to be informed when the ticket is resolved or closed. If FieldPolling is set to true, the FieldPolling Playbook will poll for the state(ServiceNow State field) of the ServiceNow ticket until it marks as either resolved or closed.

In Addition to the playbook, we recommend that you use the included layout for ServiceNow Ticket, which helps visualize ServiceNow ticket information in Cortex xSOAR.
You can add the new layout as a tab to existing layouts using the Edit Layout page.
MITRE ATT&CK - Courses of ActionThis is the parent playbook, which contains all phases and remediates MITRE ATT&CK techniques using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team. The playbook utilizes several other MITRE ATT&CK remediation playbooks.

The playbook follows the MITRE ATT&CK kill chain phases and takes action to protect the organization from the inputted techniques, displaying and implementing security policy recommendations for Palo Alto Networks products.

***Disclaimer: This playbook does not simulate an attack using the specified techniques, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Possible playbook triggers:
- The playbook can be triggered by a feed integration fetching indicators that contain MITRE ATT&CK techniques as “Feed Related Indicators”, using the "MITRE ATT&CK - Courses of Action - Job" playbook.
- The playbook can be triggered manually for specific MITRE ATT&CK techniques using the ‘techniqueByIncident’ playbook input.
- An incident that contains MITRE ATT&CK technique IDs using the ‘techniqueByIncident’ playbook input.
MITRE ATT&CK - Courses of Action Trigger JobThis is a wrapper playbook for the "MITRE ATT&CK - Courses of Action" use-case.

Possible playbook triggers:
- Through a job, by a feed integration fetching indicators that contain MITRE ATT&CK techniques as “Feed Related Indicators”, or with custom inputs.
- Through an incident, using custom playbook inputs.

Once triggered, the playbook will create a new incident from type "MITRE ATT&CK CoA". The incident will trigger the playbook "MITRE ATT&CK - Courses of Action",
which contains all phases and remediates MITRE ATT&CK techniques using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified techniques, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
MITRE ATT&CK CoA - T1003 - OS Credential DumpingThis playbook Remediates the OS Credential Dumping technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:
- T1003: OS Credential Dumping

Kill Chain phases:
- Defense Evasion

MITRE ATT&CK Description:
Adversaries may attempt to dump credentials to obtain account login and credential material, normally in the form of a hash or a clear text password, from the operating system and software. Credentials can then be used to perform Lateral Movement and to access restricted information.

Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
MITRE ATT&CK CoA - T1005 - Data from Local SystemThis playbook Remediates the Data from Local System technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:
- T1005: Data from Local System

Kill Chain phases:
- Collection

MITRE ATT&CK Description:
Adversaries may search local system sources, such as file systems or local databases, to find files of interest and sensitive data prior to Exfiltration. Adversaries may do this using a Command and Scripting Interpreter, such as cmd, which has functionality to interact with the file system to gather information. Some adversaries may also use Automated Collection on the local system.

Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
MITRE ATT&CK CoA - T1021.001 - Remote Desktop ProtocolThis playbook Remediates the Remote Desktop Protocol technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:
- T1021.001: Remote Desktop Protocol

Kill Chain phases:
- Lateral Movement

MITRE ATT&CK Description:

Adversaries may use Valid Accounts to log into a computer using the Remote Desktop Protocol (RDP). The adversary may then perform actions as the logged-on user.

Remote desktop is a common feature in operating systems. It allows a user to log into an interactive session with a system desktop graphical user interface on a remote system. Microsoft refers to its implementation of the Remote Desktop Protocol (RDP) as Remote Desktop Services (RDS).

Adversaries may connect to a remote system over RDP/RDS to expand access if the service is enabled and allows access to accounts with known credentials. Adversaries will likely use Credential Access techniques to acquire credentials to use with RDP. Adversaries may also use RDP in conjunction with the Accessibility Features technique for Persistence.

Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
MITRE ATT&CK CoA - T1027 - Obfuscated Files or InformationThis playbook Remediates the Obfuscated Files or Information technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:
- T1027: Obfuscated Files or Information

Kill Chain phases:
- Defense Evasion

MITRE ATT&CK Description:

Adversaries may attempt to make an executable or file difficult to discover or analyze by encrypting, encoding, or otherwise obfuscating its contents on the system or in transit. This is common behavior that can be used across different platforms and the network to evade defenses.

Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
MITRE ATT&CK CoA - T1041 - Exfiltration Over C2 ChannelThis playbook Remediates the Exfiltration Over C2 Channel technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:
- T1041: Exfiltration Over C2 Channel

Kill Chain phases:
- Exfiltration

MITRE ATT&CK Description:
Adversaries may steal data by exfiltrating it over an existing command and control channel. Stolen data is encoded into the normal communications channel using the same protocol as command and control communications.

Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
MITRE ATT&CK CoA - T1048 - Exfiltration Over Alternative ProtocolThis playbook Remediates the Exfiltration Over Alternative Protocol technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:
- T1048: Exfiltration Over Alternative Protocol

Kill Chain phases:
- Exfiltration

MITRE ATT&CK Description:
Adversaries may steal data by exfiltrating it over a different protocol than that of the existing command and control channel. The data may also be sent to an alternate network location from the main command and control server.
Alternate protocols include FTP, SMTP, HTTP/S, DNS, SMB, or any other network protocol not being used as the main command and control channel. Different protocol channels could also include Web services such as cloud storage. Adversaries may also opt to encrypt and/or obfuscate these alternate channels.
Exfiltration Over Alternative Protocol can be done using various common operating system utilities such as Net/SMB or FTP.

Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
MITRE ATT&CK CoA - T1057 - Process DiscoveryThis playbook Remediates the Process Discovery technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:
- T1057: Process Discovery

Kill Chain phases:
- Discovery

MITRE ATT&CK Description:

Adversaries may attempt to get information about running processes on a system. Information obtained could be used to gain an understanding of common software/applications running on systems within the network. Adversaries may use the information from Process Discovery during automated discovery to shape follow-on behaviors, including whether or not the adversary fully infects the target and/or attempts specific actions.

Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
MITRE ATT&CK CoA - T1059 - Command and Scripting InterpreterThis playbook Remediates the Command and Scripting Interpreter technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:
- T1059: Command and Scripting Interpreter

Kill Chain phases:
- Execution

MITRE ATT&CK Description:

Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries. These interfaces and languages provide ways of interacting with computer systems and are a common feature across many different platforms. Most systems come with some built-in command-line interface and scripting capabilities, for example, macOS and Linux distributions include some flavor of Unix Shell while Windows installations include the Windows Command Shell and PowerShell.

There are also cross-platform interpreters such as Python, as well as those commonly associated with client applications such as JavaScript/JScript and Visual Basic.

Adversaries may abuse these technologies in various ways as a means of executing arbitrary commands. Commands and scripts can be embedded in Initial Access payloads delivered to victims as lure documents or as secondary payloads downloaded from an existing C2. Adversaries may also execute commands through interactive terminals/shells.

Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
MITRE ATT&CK CoA - T1059.001 - PowerShellThis playbook Remediates the Command and Scripting Interpreter technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:
- T1059.001: Command and Scripting Interpreter: PowerShell

Kill Chain phases:
- Execution

MITRE ATT&CK Description:

Adversaries may abuse PowerShell commands and scripts for execution. PowerShell is a powerful interactive command-line interface and scripting environment included in the Windows operating system. [1] Adversaries can use PowerShell to perform a number of actions, including discovery of information and execution of code. Examples include the Start-Process cmdlet which can be used to run an executable and the Invoke-Command cmdlet which runs a command locally or on a remote computer (though administrator permissions are required to use PowerShell to connect to remote systems).

PowerShell may also be used to download and run executables from the Internet, which can be executed from disk or in memory without touching disk.

Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
MITRE ATT&CK CoA - T1068 - Exploitation for Privilege EscalationThis playbook Remediates the Exploitation for Privilege Escalation technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:
- T1068: Exploitation for Privilege Escalation

Kill Chain phases:
- Privilege Escalation

MITRE ATT&CK Description:
Adversaries may exploit software vulnerabilities in an attempt to collect elevate privileges. Exploitation of a software vulnerability occurs when an adversary takes advantage of a programming error in a program, service, or within the operating system software or kernel itself to execute adversary-controlled code. Security constructs such as permission levels will often hinder access to information and use of certain techniques, so adversaries will likely need to perform privilege escalation to include use of software exploitation to circumvent those restrictions.

When initially gaining access to a system, an adversary may be operating within a lower privileged process which will prevent them from accessing certain resources on the system. Vulnerabilities may exist, usually in operating system components and software commonly running at higher permissions, that can be exploited to gain higher levels of access on the system. This could enable someone to move from unprivileged or user level permissions to SYSTEM or root permissions depending on the component that is vulnerable. This may be a necessary step for an adversary compromising a endpoint system that has been properly configured and limits other privilege escalation methods.

Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
MITRE ATT&CK CoA - T1071 - Application Layer ProtocolThis playbook Remediates the Application Layer Protocol technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:
- T1071: Application Layer Protocol

Kill Chain phases:
- Command And Control

MITRE ATT&CK Description:

Adversaries may communicate using application layer protocols to avoid detection/network filtering by blending in with existing traffic. Commands to the remote system, and often the results of those commands, will be embedded within the protocol traffic between the client and server.

Adversaries may utilize many different protocols, including those used for web browsing, transferring files, electronic mail, or DNS. For connections that occur internally within an enclave (such as those between a proxy or pivot node and other nodes), commonly used protocols are SMB, SSH, or RDP.

Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
MITRE ATT&CK CoA - T1078 - Valid AccountsThis playbook Remediates the Valid Accounts technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:
- T1078: Valid Accounts

Kill Chain phases:
- Defense Evasion
- Persistence
- Privilege Escalation
- Initial Access

MITRE ATT&CK Description:

Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.

The overlap of permissions for local, domain, and cloud accounts across a network of systems is of concern because the adversary may be able to pivot across accounts and systems to reach a high level of access (i.e., domain or enterprise administrator) to bypass access controls set within the enterprise.

Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
MITRE ATT&CK CoA - T1082 - System Information DiscoveryThis playbook Remediates the System Information Discovery technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:
- T1082: System Information Discovery

Kill Chain phases:
- Discovery

MITRE ATT&CK Description:

An adversary may attempt to get detailed information about the operating system and hardware, including version, patches, hotfixes, service packs, and architecture. Adversaries may use the information from System Information Discovery during automated discovery to shape follow-on behaviors, including whether or not the adversary fully infects the target and/or attempts specific actions.

Tools such as Systeminfo can be used to gather detailed system information. A breakdown of system data can also be gathered through the macOS systemsetup command, but it requires administrative privileges.

Infrastructure as a Service (IaaS) cloud providers such as AWS, GCP, and Azure allow access to instance and virtual machine information via APIs. Successful authenticated API calls can return data such as the operating system platform and status of a particular instance or the model view of a virtual machine.

Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
MITRE ATT&CK CoA - T1083 - File and Directory DiscoveryThis playbook Remediates the File and Directory Discovery technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:
- T1083: File and Directory Discovery

Kill Chain phases:
- Discovery

MITRE ATT&CK Description:

Adversaries may enumerate files and directories or may search in specific locations of a host or network share for certain information within a file system. Adversaries may use the information from File and Directory Discovery during automated discovery to shape follow-on behaviors, including whether or not the adversary fully infects the target and/or attempts specific actions.

Many command shell utilities can be used to obtain this information. Examples include dir, tree, ls, find, and locate. Custom tools may also be used to gather file and directory information and interact with the Native API.

Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
MITRE ATT&CK CoA - T1105 - Ingress tool transferThis playbook Remediates the Ingress tool transfer technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:
- T1105: Ingress tool transfer

Kill Chain phases:
- Command And Control

MITRE ATT&CK Description:
Adversaries may transfer tools or other files from an external system into a compromised environment. Files may be copied from an external adversary controlled system through the command and control channel to bring tools into the victim network or through alternate protocols with another tool such as FTP. Files can also be copied over on Mac and Linux with native tools like scp, rsync, and sftp.

Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
MITRE ATT&CK CoA - T1110 - Brute ForceThis playbook Remediates the Brute Force technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:
- T1110 : Brute Force

Kill Chain phases:
- Credential Access

MITRE ATT&CK Description:

Adversaries may use brute force techniques to gain access to accounts when passwords are unknown or when password hashes are obtained. Without knowledge of the password for an account or set of accounts, an adversary may systematically guess the password using a repetitive or iterative mechanism. Brute forcing passwords can take place via interaction with a service that will check the validity of those credentials or offline against previously acquired credential data, such as password hashes.

Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
MITRE ATT&CK CoA - T1133 - External Remote ServicesThis playbook Remediates the External Remote Services technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:
- T1133: External Remote Services

Kill Chain phases:
- Persistence
- Initial Access

MITRE ATT&CK Description:

Adversaries may use brute force techniques to gain access to accounts when passwords are unknown or when password hashes are obtained. Without knowledge of the password for an account or set of accounts, an adversary may systematically guess the password using a repetitive or iterative mechanism. Brute forcing passwords can take place via interaction with a service that will check the validity of those credentials or offline against previously acquired credential data, such as password hashes.

Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
MITRE ATT&CK CoA - T1135 - Network Share DiscoveryThis playbook Remediates the Network Share Discovery technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:
- T1135: Network Share Discovery

Kill Chain phases:
- Discovery

MITRE ATT&CK Description:

Adversaries may look for folders and drives shared on remote systems as a means of identifying sources of information to gather as a precursor for Collection and to identify potential systems of interest for Lateral Movement. Networks often contain shared network drives and folders that enable users to access file directories on various systems across a network.

File sharing over a Windows network occurs over the SMB protocol. [1][2] Net can be used to query a remote system for available shared drives using the net view \remotesystem command. It can also be used to query shared drives on the local system using net share.

Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
MITRE ATT&CK CoA - T1189 - Drive-by CompromiseThis playbook Remediates the Drive-by Compromise technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:
- T1189: Drive-by Compromise

Kill Chain phases:
- Initial Access

MITRE ATT&CK Description:

Adversaries may gain access to a system through a user visiting a website over the normal course of browsing. With this technique, the user's web browser is typically targeted for exploitation, but adversaries may also use compromised websites for non-exploitation behavior such as acquiring Application Access Token.

Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
MITRE ATT&CK CoA - T1199 - Trusted RelationshipThis playbook Remediates the Trusted Relationship technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:
- T1199: Trusted Relationship

Kill Chain phases:
- Initial Access

MITRE ATT&CK Description:

Adversaries may breach or otherwise leverage organizations who have access to intended victims. Access through trusted third party relationship exploits an existing connection that may not be protected or receives less scrutiny than standard mechanisms of gaining access to a network.

Organizations often grant elevated access to second or third-party external providers in order to allow them to manage internal systems as well as cloud-based environments. Some examples of these relationships include IT services contractors, managed security providers, infrastructure contractors (e.g. HVAC, elevators, physical security). The third-party provider's access may be intended to be limited to the infrastructure being maintained, but may exist on the same network as the rest of the enterprise. As such, Valid Accounts used by the other party for access to internal network systems may be compromised and used.

Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
MITRE ATT&CK CoA - T1204 - User ExecutionThis playbook Remediates the User Execution technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:
- T1204: User Execution

Kill Chain phases:
- Execution

MITRE ATT&CK Description:

An adversary may rely upon specific actions by a user in order to gain execution. Users may be subjected to social engineering to get them to execute malicious code by, for example, opening a malicious document file or link. These user actions will typically be observed as follow-on behavior from forms of Phishing.

While User Execution frequently occurs shortly after Initial Access it may occur at other phases of an intrusion, such as when an adversary places a file in a shared directory or on a user's desktop hoping that a user will click on it. This activity may also be seen shortly after Internal Spearphishing.

Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
MITRE ATT&CK CoA - T1486 - Data Encrypted for ImpactThis playbook Remediates the Data Encrypted for Impact technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:
- T1486: Data Encrypted for Impact

Kill Chain phases:
- Impact

MITRE ATT&CK Description:

Adversaries may encrypt data on target systems or on large numbers of systems in a network to interrupt availability to system and network resources. They can attempt to render stored data inaccessible by encrypting files or data on local and remote drives and withholding access to a decryption key. This may be done in order to extract monetary compensation from a victim in exchange for decryption or a decryption key (ransomware) or to render data permanently inaccessible in cases where the key is not saved or transmitted.[1][2][3][4] In the case of ransomware, it is typical that common user files like Office documents, PDFs, images, videos, audio, text, and source code files will be encrypted. In some cases, adversaries may encrypt critical system files, disk partitions, and the MBR.

To maximize impact on the target organization, malware designed for encrypting data may have worm-like features to propagate across a network by leveraging other attack techniques like Valid Accounts, OS Credential Dumping, and SMB/Windows Admin Shares.

Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
MITRE ATT&CK CoA - T1518 - Software DiscoveryThis playbook Remediates the Software Discovery technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:
- T1518: Software Discovery

Kill Chain phases:
- Discovery

MITRE ATT&CK Description:

Adversaries may attempt to get a listing of software and software versions that are installed on a system or in a cloud environment. Adversaries may use the information from Software Discovery during automated discovery to shape follow-on behaviors, including whether or not the adversary fully infects the target and/or attempts specific actions.

Adversaries may attempt to enumerate software for a variety of reasons, such as figuring out what security measures are present or if the compromised system has a version of software that is vulnerable to Exploitation for Privilege Escalation.

Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
MITRE ATT&CK CoA - T1543.003 - Windows ServiceThis playbook Remediates the Windows Service technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:
- T1543.003: Create or Modify System Process: Windows Service

Kill Chain phases:
- Persistence
- Privilege Escalation

MITRE ATT&CK Description:
Adversaries may create or modify Windows services to repeatedly execute malicious payloads as part of persistence. When Windows boots up, it starts programs or applications called services that perform background system functions.[1] Windows service configuration information, including the file path to the service's executable or recovery programs/commands, is stored in the Windows Registry. Service configurations can be modified using utilities such as sc.exe and Reg.

Adversaries may install a new service or modify an existing service by using system utilities to interact with services, by directly modifying the Registry, or by using custom tools to interact with the Windows API. Adversaries may configure services to execute at startup in order to persist on a system.

Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.


MITRE ATT&CK CoA - T1547 - Boot or Logon Autostart ExecutionThis playbook Remediates the Boot or Logon Autostart Execution technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:
- T1547: Boot or Logon Autostart Execution

Kill Chain phases:
- Persistence
- Privilege Escalation

MITRE ATT&CK Description:

Adversaries may configure system settings to automatically execute a program during system boot or logon to maintain persistence or gain higher-level privileges on compromised systems. Operating systems may have mechanisms for automatically running a program on system boot or account logon.[1][2][3][4][5] These mechanisms may include automatically executing programs that are placed in specially designated directories or are referenced by repositories that store configuration information, such as the Windows Registry. An adversary may achieve the same goal by modifying or extending features of the kernel.

Since some boot or logon autostart programs run with higher privileges, an adversary may leverage these to elevate privileges.

Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
MITRE ATT&CK CoA - T1547.001 - Registry Run Keys Startup FolderThis playbook Remediates the Registry Run Keys / Startup Folder technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:
- T1547.001: Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder

Kill Chain phases:
- Persistence
- Privilege Escalation

MITRE ATT&CK Description:
Adversaries may achieve persistence by adding a program to a startup folder or referencing it with a Registry run key. Adding an entry to the "run keys" in the Registry or startup folder will cause the program referenced to be executed when a user logs in. [1] These programs will be executed under the context of the user and will have the account's associated permissions level.

Placing a program within a startup folder will also cause that program to execute when a user logs in. There is a startup folder location for individual user accounts as well as a system-wide startup folder that will be checked regardless of which user account logs in. The startup folder path for the current user is C:\Users[Username]\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup. The startup folder path for all users is C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp.

Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
MITRE ATT&CK CoA - T1560.001 - Archive via UtilityThis playbook Remediates the Data Encrypted technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:
- T1560.001: Archive Collected Data: Archive via Utility

Kill Chain phases:
- Exfiltration

MITRE ATT&CK Description:

An adversary may compress or encrypt data that is collected prior to exfiltration using 3rd party utilities. Many utilities exist that can archive data, including 7-Zip[1], WinRAR[2], and WinZip[3]. Most utilities include functionality to encrypt and/or compress data.

Some 3rd party utilities may be preinstalled, such as tar on Linux and macOS or zip on Windows systems.

Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
MITRE ATT&CK CoA - T1562.001 - Disable or Modify ToolsThis playbook Remediates the Disable or Modify Tools technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:
- T1562.001: Impair Defenses: Disable or Modify Tools

Kill Chain phases:
- Defense Evasion

MITRE ATT&CK Description:
Adversaries may disable security tools to avoid possible detection of their tools and activities. This can take the form of killing security software or event logging processes, deleting Registry keys so that tools do not start at run time, or other methods to interfere with security tools scanning or reporting information.

Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.

MITRE ATT&CK CoA - T1564.004 - NTFS File AttributesThis playbook Remediates the NTFS File Attributes technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:
- T1564.004: NTFS File Attributes

Kill Chain phases:
- Defense Evasion

MITRE ATT&CK Description:

Adversaries may use NTFS file attributes to hide their malicious data in order to evade detection. Every New Technology File System (NTFS) formatted partition contains a Master File Table (MFT) that maintains a record for every file/directory on the partition. [1] Within MFT entries are file attributes, [2] such as Extended Attributes (EA) and Data [known as Alternate Data Streams (ADSs) when more than one Data attribute is present], that can be used to store arbitrary data (and even complete files).

Adversaries may store malicious data or binaries in file attribute metadata instead of directly in files. This may be done to evade some defenses, such as static indicator scanning tools and anti-virus.

Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
MITRE ATT&CK CoA - T1566 - PhishingThis playbook Remediates the Phishing technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:
- T1566: Phishing

Kill Chain phases:
- Initial Access

MITRE ATT&CK Description:

Adversaries may send phishing messages to gain access to victim systems. All forms of phishing are electronically delivered social engineering. Phishing can be targeted, known as spearphishing. In spearphishing, a specific individual, company, or industry will be targeted by the adversary. More generally, adversaries can conduct non-targeted phishing, such as in mass malware spam campaigns.

Adversaries may send victims emails containing malicious attachments or links, typically to execute malicious code on victim systems or to gather credentials for use of Valid Accounts. Phishing may also be conducted via third-party services, like social media platforms.

Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
MITRE ATT&CK CoA - T1566.001 - Spear-Phishing AttachmentThis playbook Remediates the Spear-Phishing Attachment technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:
- T1566.001: Spear-Phishing Attachment

Kill Chain phases:
- Initial Access

MITRE ATT&CK Description:

Adversaries may send spearphishing emails with a malicious attachment in an attempt to gain access to victim systems. Spearphishing attachment is a specific variant of spearphishing. Spearphishing attachment is different from other forms of spearphishing in that it employs the use of malware attached to an email. All forms of spearphishing are electronically delivered social engineering targeted at a specific individual, company, or industry. In this scenario, adversaries attach a file to the spearphishing email and usually rely upon User Execution to gain execution.

Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
MITRE ATT&CK CoA - T1569.002 - Service ExecutionThis playbook Remediates the Service Execution technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:
- T1569.002: System Services: Service Execution

Kill Chain phases:
- Execution

MITRE ATT&CK Description:
Adversaries may abuse the Windows service control manager to execute malicious commands or payloads. The Windows service control manager (services.exe) is an interface to manage and manipulate services.[1] The service control manager is accessible to users via GUI components as well as system utilities such as sc.exe and Net.
PsExec can also be used to execute commands or payloads via a temporary Windows service created through the service control manager API.[2]
Adversaries may leverage these mechanisms to execute malicious content. This can be done by either executing a new or modified service. This technique is the execution used in conjunction with Windows Service during service persistence or privilege escalation.

Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
MITRE ATT&CK CoA - T1573.002 - Asymmetric CryptographyThis playbook Remediates the Standard Cryptographic Protocol technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.

***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:
- 1573.002: Encrypted Channel: Asymmetric Cryptography

Kill Chain phases:
- Command And Control

MITRE ATT&CK Description:
Adversaries may employ a known asymmetric encryption algorithm to conceal command and control traffic rather than relying on any inherent protections provided by a communication protocol. Asymmetric cryptography, also known as public key cryptography, uses a keypair per party: one public that can be freely distributed, and one private. Due to how the keys are generated, the sender encrypts data with the receiver’s public key and the receiver decrypts the data with their private key. This ensures that only the intended recipient can read the encrypted data. Common public key encryption algorithms include RSA and ElGamal.

For efficiency, may protocols (including SSL/TLS) use symmetric cryptography once a connection is established, but use asymmetric cryptography to establish or transmit a key. As such, these protocols are classified as Asymmetric Cryptography.

Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
Mitre Attack - Extract Technique Information From IDThis playbook accepts as input MITRE techniques IDs.
It returns the MITRE technique name and full technique data using the MITRE integration.
MockPlaybook
MockSubplaybook
Modify EDLAdds indicators to or removes indicators from an external dynamic list (EDL) by adding or removing an indicator tag. The EDL itself is generated by using the Cortex XSOAR Generic Export Indicators Service integration and querying on a tag in the Indicator Query parameter.

Incident fields that control the behavior of this playbook:
- EDL Action: Whether to add or remove EDL indicators.
- EDL Indicators List: Input list of indicators to add to or remove from EDL (according to the value of EDL Action).
- EDL Tag: Tag value in the Generic Export Indicators Service integration instance Indicator Query, which controls which indicators are on the EDL.
- EDL Indicator Type: (Only relevant if adding to EDL) Type of indicators to add to EDL.
NetOps - Firewall Version and Content UpgradeNetwork operations playbook that updates the version and content of the firewall. You must have Superuser permissions to update the PAN-OS version.
NetOps - Upgrade PAN-OS Firewall DeviceNetwork operations playbook that upgrades the firewall. You must have Superuser permissions to update the PAN-OS version. Note: This playbook should only be used for minor version upgrades. Major version upgrades will not work due to a change in the API key.
New Hire Auto-AddQueries stand-up tickets from a ticketing system and passes relevant employee data to the Add Employees to New Hire Watchlist playbook.
New Hire Clean-UpQueries the New Hire watchlist in Code42 Incydr and passes relevant employee data to the Remove Employees from New Hire Watchlist playbook.
New York - Breach NotificationThis playbook helps an analyst determine if the breached data meets the criteria for breach notification according to New York State law, and, if necessary, follows through with the notification procedures.

DISCLAIMER: Please consult with your legal team before implementing this playbook.

Sources:
https://ag.ny.gov/internet/data-breach
https://www.dos.ny.gov/consumerprotection/pdf/infosecbreach03.pdf
https://www.nysenate.gov/legislation/laws/GBS/899-AA
Nexpose - Create and Download ReportUse this playbook as a sub-playbook to configure a report and download it.
This playbook implements polling by continuously running the `nexpose-get-report-status` command until the operation completes.
The remote action should have the following structure:

1. Initiate the operation - insert the type of the report (sites, scan, or assets) and it's additional arguments if required.
2. Poll to check if the operation completed.
3. Get the results of the operation.
NGFW Internal ScanThis playbook investigates a scan where the source is an internal IP address.

An attacker might initiate an internal scan for discovery, lateral movement and more.

Attacker's Goals:

An attacker can leverage a scan for open ports and vulnerable systems on remote endpoints in an attempt to identify the endpoint operating system, firewall configuration, and exploitable services.

Investigative Actions:

Endpoint Investigation Plan playbook

Response Actions

The playbook's response actions are based on the Endpoint Investigation Plan playbook results. In that phase, the playbook will execute:

Auto endpoint isolation
Manual block indicators
Manual file quarantine
NGFW Remove Offline TS AgentCheck if TS Agent server is offline and deregister it from the NGFW
NGFW ScanThis playbook handles external and internal scanning alerts.

Attacker's Goals:

Adversaries may attempt to get a listing of services running on remote hosts, including those that may be vulnerable to remote software exploitation. Methods to acquire this information include port scans and vulnerability scans using tools that are brought onto a system.

Investigative Actions:

Investigate the scanner IP address using:

IP enrichment:
NGFW Internal Scan playbook
Endpoint Investigation Plan playbook
Entity enrichment

Response Actions

The playbook's response actions are based on the initial data provided within the alert. In that phase, the playbook will execute:

Automatically block IP address
Report IP address (If configured as true in the playbook inputs)

When the playbook executes, it checks for additional activity using the Endpoint Investigation Plan playbook, and another phase, which includes the Containment Plan playbook, is executed.
This phase will execute the following containment actions:

Automatically isolate involved endpoint
Manual block indicators
Manual file quarantine
Manual disable user

External resources:

Mitre technique T1046 - Network Service Scanning

Port Scan
NIST - Handling an Incident TemplateThis playbook contains the phases to handling an incident as described in the 'Handling an Incident' section of NIST - Computer Security Incident Handling Guide.

Handling an incident - Computer Security Incident Handling Guide
https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-61r2.pdf
NIST - Lessons LearnedThis playbook assists in processing an incident after it occurs and facilitates the lessons learned stage.
NMAP - Banner CheckSub-playbook that performs an Nmap scan and compares the results against a regular expression to determine a match. This could be used to look for OpenSSH versions or other OS information found in the banner.
NMAP - Single Port ScanSub-playbook that conducts a single port Nmap scan and returns the results to the parent playbook.
NOBELIUM - wide scale APT29 spear-phishingOn May 27, 2021, Microsoft reported a wide scale spear phishing campaign attributed to APT29, the same threat actor responsible for the SolarWinds campaign named SolarStorm. This attack had a wide range of targets for an APT spear phishing campaign with 3,000 email accounts targeted within 150 organizations.
https://www.microsoft.com/security/blog/2021/05/27/new-sophisticated-email-based-attack-from-nobelium/
This playbook includes the following tasks:
- Collect IOCs to be used in your threat hunting process
- Query FW, SIEMs, EDR, XDR to detect malicious hashes, network activity and compromised hosts
- Block known indicators
** Note: This is a beta playbook, which lets you implement and test pre-release software. Since the playbook is beta, it might contain bugs. Updates to the pack during the beta phase might include non-backward compatible features. We appreciate your feedback on the quality and usability of the pack to help us identify issues, fix them, and continually improve.
Notify Stock Above PriceThis playbook sends a message on Telegram when a stock price rises higher than a predefined price
NSA - 5 Security Vulnerabilities Under Active Nation-State AttackRussian Foreign Intelligence Service (SVR) actors (also known as APT29, Cozy Bear, and The Dukes) frequently use publicly known vulnerabilities to conduct widespread scanning and exploitation.
This playbook should be trigger manually and includes the following tasks:
- Enrich related known CVEs reported in the US agencies alert.
- Search for unpatched endpoints vulnerable to the exploits.
- Search for vulnerable assets facing the internet using Expanse.

Note: This is a beta playbook, which lets you implement and test pre-release software. Since the playbook is beta, it might contain bugs. Updates to the pack during the beta phase might include non-backward compatible features. We appreciate your feedback on the quality and usability of the pack to help us identify issues, fix them, and continually improve.

More information:
[Cyber Security Advisory] (https://media.defense.gov/2021/Apr/15/2002621240/-1/-1/0/CSA_SVR_TARGETS_US_ALLIES_UOO13234021.PDF/CSA_SVR_TARGETS_US_ALLIES_UOO13234021.PDF)
O365 - Security And Compliance - SearchThis playbook performs the following steps:
1. Creates a compliance search.
2. Starts a compliance search.
3. Waits for the compliance search to complete.
4. Gets the results of the compliance search as an output.
5. Gets the preview results, if specified.
O365 - Security And Compliance - Search Action - DeleteThis playbook performs the following steps:
1. Creates a new compliance search action Purge - Hard or Soft.
2. Waits for the compliance search action to complete.
3. Retrieves the delete search action.
O365 - Security And Compliance - Search Action - PreviewThis playbook perform:
1. Creates a new compliance search action - Preview (Base on created compliance search).
2. Waits for the preview action to complete.
3. Retrieves the preview results.
O365 - Security And Compliance - Search And DeleteThis playbook performs the following steps:
1. Creates a compliance search.
2. Starts a compliance search.
3. Waits for the compliance search to complete.
4. Gets the results of the compliance search.
5. Gets the preview results, if specified.
6. Deletes the search results (Hard/Soft).
Office 365 Search and DeleteRun a ComplianceSearch on Office 365 and delete the results.
Okta - User InvestigationThis playbook performs an investigation on a specific user, using queries and logs from Okta.
Online Brand Protection Detect and RespondAnalyzes the domains and URLs in suspicious emails, reported by end users, to determine if the phishing campaign is impersonating your company’s brand. Playbook can then trigger a domain take down email, with forensic evidence, to a target address.
OpenCTI Create IndicatorCreate indicator at OpenCTI.
Palo Alto Networks - Endpoint Malware InvestigationDeprecated. Use Malware Investigation and Response pack instead. For more information, refer to https://xsoar.pan.dev/docs/reference/packs/malware-investigation-and-response. This playbook is triggered by a Palo Alto Networks Cortex threat alert, generated by Traps. The playbook performs host enrichment for the source host with Palo Alto Networks Traps, enriches information for the suspicious file with Palo Alto Networks Minemeld and AutoFocus, and automatically performs file detonation for the extracted file. It then performs IOC enrichment with Minemeld for all related IOCs, and calculates the incident severity based on all the findings. In addition we detonate the file for the full analysis report.
The analyst can perform a manual memory dump for the suspected endpoint based on the incident’s severity, and choose to isolate the source endpoint with Traps.
Hunting tasks to find more endpoints that are infected is performed automatically based on a playbook input, and after all infected endpoints are found, remediation for all malicious IOCs is performed, including file quarantine, and IP and URLs blocking with Palo Alto Networks FireWall components such as Dynamic Address Groups and Custom URL Categories.
After the investigation review the incident is automatically closed.
Palo Alto Networks - Endpoint Malware Investigation v2Deprecated. Use the "Palo Alto Networks - Endpoint Malware Investigation v3"\ \ playbook instead. This playbook is triggered by a Palo Alto Networks Cortex threat alert,\ \ generated by Traps. The playbook performs host enrichment for the source host\ \ with Palo Alto Networks Traps, enriches information for the suspicious file with\ \ Palo Alto Networks Minemeld and AutoFocus, and automatically performs file detonation\ \ for the extracted file. It then performs IOC enrichment with Minemeld for all\ \ related IOCs, and calculates the incident severity based on all the findings.\ \ In addition we detonate the file for the full analysis report. \nThe analyst can\ \ perform a manual memory dump for the suspected endpoint based on the incident’s\ \ severity, and choose to isolate the source endpoint with Traps.\nHunting tasks\ \ to find more endpoints that are infected is performed automatically based on a\ \ playbook input, and after all infected endpoints are found, remediation for all\ \ malicious IOCs is performed, including file quarantine, and IP and URLs blocking\ \ with Palo Alto Networks FireWall components such as Dynamic Address Groups and\ \ Custom URL Categories.\nAfter the investigation review the incident is automatically\ \ closed.
Palo Alto Networks - Endpoint Malware Investigation v3Deprecated. Use Malware Investigation and Response pack instead. For more information, refer to https://xsoar.pan.dev/docs/reference/packs/malware-investigation-and-response.This playbook is triggered by a Palo Alto Networks Cortex threat alert, generated by Traps. The playbook performs host enrichment for the source host with Palo Alto Networks Traps, enriches information for the suspicious file with Palo Alto Networks Minemeld and AutoFocus, and automatically performs file detonation for the extracted file. It then performs IOC enrichment with Minemeld for all related IOCs, and calculates the incident severity based on all the findings. In addition we detonate the file for the full analysis report.
The analyst can perform a manual memory dump for the suspected endpoint based on the incident’s severity, and choose to isolate the source endpoint with Traps.
Hunting tasks to find more endpoints that are infected is performed automatically based on a playbook input, and after all infected endpoints are found, remediation for all malicious IOCs is performed, including file quarantine, and IP and URLs blocking with Palo Alto Networks FireWall components such as Dynamic Address Groups and Custom URL Categories.
After the investigation review the incident is automatically closed.
Palo Alto Networks - Hunting And Threat DetectionThis is a multipurpose playbook used for hunting and threat detection. The playbook receives inputs based on hashes, IP addresses, or domain names provided manually or from outputs by other playbooks.
The playbook leverages data received by PANW products including, Strata Logging Service, Autofocus and Pan-OS to search for IP addresses, host names and users related to the provided indicators.
The output provided by the playbook enables you to find possibly affected IP addresses, users, and endpoints.
Palo Alto Networks - Malware RemediationDeprecated. Use Malware Investigation and Response pack instead. For more information, refer to https://xsoar.pan.dev/docs/reference/packs/malware-investigation-and-response.This Playbook performs malicious IOC remediation using Palo Alto Networks integrations.
Palo Alto Networks BPA - Submit ScanThis playbook accepts a list of BPA checks, triggers a job and returns the checks results.
PAN-OS - Add Anti-Spyware Security Profile To RuleThis playbook is designed to enhance the security level in PAN-OS firewalls by safely adding an Anti-Spyware security profile to a security rule.
The playbook provides control over the behavior when a a rule:
- Already has an Anti-Spyware profile
- Uses a security profile group, with or without an Anti-Spyware profile

The output of the playbook is the Anti-Spyware profile configured for the rule upon playbook completion. This can be:
- The initial profile, if untouched
- A newly overwritten profile
- A newly added profile
PAN-OS - Add Domains EDL To Anti-SpywareThis playbook add domains EDL to Panorama Anti-Spyware. It assigns External Dynamic List URLs that contain domains to block to Panorama Anti-Spyware. You can create an External Dynamic List (EDL) and add domains to it using the Cortex XSOAR pack called "Generic Export Indicators Service".
We recommend using this playbook as a one-time job. Once EDL is created and assigned to anti-spyware, domains can be blocked by adding them to the EDL.
PAN-OS - Add Static RoutesThis playbook accepts a PAN-OS static route configuration and creates it in the PAN-OS instance.
PAN-OS - Apply Security Profile to Policy RuleThis playbook is used to apply a PAN-OS security profile to a policy rule.
The playbook performs the following tasks:
- Accepts a rule name to apply the security profile to.
- Applies the security profile to the rule if the rule exists. If not, creates the rule and applies.
- Commits the configuration.
PAN-OS - Block all unknown and unauthorized applicationsThis playbook is used to find and remove all rules that allow unauthorized applications communication as any.
The playbook performs the following tasks:
- Lists PAN-OS policy rules.
- Checks for a rule that allows applications as any.
- Deletes the rule based on user approval.
- Commits the configuration.
PAN-OS - Block Destination ServiceThis playbook blocks a destination IP and service (TCP or UDP port) by creating a rule for a specific device group on PAN-OS.
PAN-OS - Block Domain - External Dynamic ListDeprecated. Use Generic Export Indicators Service instead.
PAN-OS - Block IP - Custom Block RuleThis playbook blocks IP addresses using Custom Block Rules in Palo Alto Networks Panorama or Firewall.
The playbook receives malicious IP addresses as inputs, creates a custom bi-directional rule to block them, and commits the configuration.
PAN-OS - Block IP - Static Address GroupThis playbook blocks IP addresses using Static Address Groups in Palo Alto Networks Panorama or Firewall.
The playbook receives malicious IP addresses and an address group name as inputs, verifies that the addresses are not already a part of the address group, adds them and commits the configuration.

***Note - The playbook does not block the address group communication using a policy block rule. This step will be taken once outside of the playbook.
PAN-OS - Block IP and URL - External Dynamic ListDeprecated. Use "PAN-OS - Block IP and URL - External Dynamic List v2" playbook instead. This playbook blocks IP addresses and URLs using Palo Alto Networks Panorama or Firewall External Dynamic Lists.
It checks if the EDL configuration is in place with the 'PAN-OS EDL Setup' sub-playbook (otherwise the list will be configured), and adds the input IPs and URLs to the relevant lists.
PAN-OS - Block IP and URL - External Dynamic List v2Deprecated. Use Generic Export Indicators Service instead.
PAN-OS - Block URL - Custom URL CategoryThis playbook blocks URLs using Palo Alto Networks Panorama or Firewall through Custom URL Categories.
The playbook checks whether the input URL category already exists, and if the URLs are a part of this category. Otherwise, it will create the category, block the URLs, and commit the configuration.
PAN-OS - Configure DNS SinkholeThis playbook creates a DNS sinkhole in a PAN-OS firewall. It does the following:
1. Finds a security rule that allows DNS traffic from the internal network to the internet using the "Security Policy Match" feature against traffic from the internal DNS server/s to the public DNS server.
2. Creates or adds an existing anti-spyware security profile to the security rule/s that were found.
3. Sets the DNS Signature Source under the DNS Policies configuration of the security profile with the "sinkhole" action.
4. Creates an address object for the sinkhole address so that it can be referenced later in a deny rule (the sinkhole IP constantly rotates).
5. Creates a new security rule to deny traffic to the sinkhole address object, in order to generate traffic logs for the compromised systems. The IPs of the compromised systems can then be retrieved using the "PAN-OS - Extract IPs From Traffic Logs To Sinkhole" playbook.

Once the configuration is completed, the playbook will create a Tag object and tag the relevant security rules to indicate that sinkholing is configured. That tag will be checked in consecutive playbook runs in order to minimize the actions done on the firewall and time time spent in the playbook execution.

How it works:
A DNS sinkhole can be used to identify infected hosts on a network where there is an internal DNS Server in-route to the firewall that causes the reference of the original source IP address of the host that first originated the query to be lost (the query is received by the internal DNS server, and the internal DNS server sources a new query if the name-to-IP resolution is not locally cached).

This causes the firewall to report observations of malicious DNS queries in the Threat logs where the source IP of the malicious DNS query is the Internal DNS server, which would force the administrator to look into the DNS Server logs to try to trace down what was the infected host that originally sourced the malicious DNS query.

After a security profile with a "sinkhole" action for domains that are listed in the DNS signature source is applied to a rule that allows DNS traffic from the internal server/s to the external one, the threat logs will show that requests from the internal DNS server/s were sinkholed. However, the compromised systems will not appear in those logs.

In order to find the IP addresses of those systems, a new rule denying all requests to our sinkhole address needs to be created. Since the infected systems received a forged DNS response (due to the security profile involved in our previous step), they will now try to connect to the sinkhole address, assuming it is their C&C server. The new rule will deny the subsequent attempts of those systems when they try to access the sinkhole address, and log them.


Assumptions:
- The domains that should be sinkholed are already in a DNS signature source. It can be one of the following sources available in PAN-OS:
1. An existing External Dynamic List (EDL) of type Domain configured in the PAN-OS firewall. Note: XSOAR simplifies the process of creating an EDL, with the Export Generic Indicators Service integration.
2. Palo Alto Networks Content-delivered malicious domains
3. DNS Security Categories available with a DNS Security subscription.
- There is at least one internal DNS server that is sending the DNS requests out through the firewall to a specific public DNS server.
PAN-OS - Create Or Edit RuleCreates or edits a Panorama rule and moves it into the desired position
PAN-OS - Delete Static RoutesThis playbook deletes a PAN-OS static route from the PAN-OS instance.
PAN-OS - Enforce Anti-Spyware Best Practices ProfileThis playbook enforces the Anti-Spyware Best Practices Profile as defined by Palo Alto Networks BPA.
The playbook performs the following tasks:
- Check for DNS Security license (If license is not activated, the playbook refers users to their Palo Alto Networks account manager for further instructions).
- Get the existing profile information.
- Get the best practices profile information.
- Check if the best practices profile set by Cortex XSOAR is enforced. (If not, the playbook allows the user to compare the existing profile with the best practices and decide on the action to take).
- Create best practices profile.
- Apply profile to policy rules on PAN-OS firewall or Panorama.
PAN-OS - Enforce Anti-Virus Best Practices ProfileThis playbook enforces the Anti-Virus Best Practices Profile as defined by Palo Alto Networks BPA.
The playbook performs the following tasks:
- Check for Threat Prevention license (If license is not activated, the playbook refers users to their Palo Alto Networks account manager for further instructions).
- Get the existing profile information.
- Get the best practices profile information.
- Check if the best practices profile set by Cortex XSOAR is enforced. (If not, the playbook allows the user to compare the existing profile with the best practices and decide on the action to take).
- Create best practices profile.
- Apply profile to policy rules on PAN-OS firewall or Panorama.
PAN-OS - Enforce File Blocking Best Practices ProfileThis playbook enforces the File Blocking Best Practices Profile as defined by Palo Alto Networks BPA.
The playbook performs the following tasks:
- Get the existing profile information.
- Get the best practices profile information.
- Check if the best practices profile set by Cortex XSOAR is enforced. (If not, the playbook allows the user to compare the existing profile with the best practices and decide on the action to take).
- Create best practices profile.
- Apply profile to policy rules on PAN-OS firewall or Panorama.
PAN-OS - Enforce URL Filtering Best Practices ProfileThis playbook enforces the URL Filtering Best Practices Profile as defined by Palo Alto Networks BPA.
The playbook performs the following tasks:
- Check for URL Filtering license (If license is not activated, the playbook refers users to their Palo Alto Networks account manager for further instructions).
- Get the existing profile information.
- Get the best practices profile information.
- Check if the best practices profile set by Cortex XSOAR is enforced. (If not, the playbook allows the user to compare the existing profile with the best practices and decide on the action to take).
- Create best practices profile.
- Apply profile to policy rules on PAN-OS firewall or Panorama.
PAN-OS - Enforce Vulnerability Protection Best Practices ProfileThis playbook enforces the Vulnerability Protection Best Practices Profile as defined by Palo Alto Networks BPA.
The playbook performs the following tasks:
- Check for Threat Prevention license (If license is not activated, the playbook refers users to their Palo Alto Networks account manager for further instructions).
- Get the existing profile information.
- Get the best practices profile information.
- Check if the best practices profile set by Cortex XSOAR is enforced. (If not, the playbook allows the user to compare the existing profile with the best practices and decide on the action to take).
- Create best practices profile.
- Apply profile to policy rules on PAN-OS firewall or Panorama.
PAN-OS - Enforce WildFire Best Practices ProfileThis playbook enforces the WildFire Best Practices Profile as defined by Palo Alto Networks BPA.
The playbook performs the following tasks:
- Check for WildFire license (If license is not activated, the playbook refers users to their Palo Alto Networks account manager for further instructions).
- Get the existing profile information.
- Get the best practices profile information.
- Check if the best practices profile set by Cortex XSOAR is enforced. (If not, the playbook allows the user to compare the existing profile with the best practices and decide on the action to take).
- Create best practices profile.
- Apply profile to policy rules on PAN-OS firewall or Panorama.
PAN-OS - Extract IPs From Traffic Logs To SinkholeThis playbook searches for outgoing traffic to the sinkhole address in PAN-OS. It should be used after a DNS sinkhole was created using the "PAN-OS - Configure DNS Sinkhole" playbook. If a DNS sinkhole was created manually, you should verify in your PAN-OS firewall that there is an address object for the sinkhole FQDN "sinkhole.paloaltonetworks.com", and that there is a rule denying traffic to it from any source. You may specify the name of the deny rule if you know it, or you can let the playbook find the rule automatically.
PAN-OS - Job - Add Malicious Domains To SinkholeThis TIM playbook should be run as a job. The playbook runs on domain indicators and performs various checks to decide if they should be sinkholed.

If a domain is related to a campaign or a threat actor, or if it resolves to a malicious IP or has malware-related tags, the playbook will add a new tag to it in order to sinkhole that domain.

The playbook assumes that the user is exporting indicators with the sinkhole tag to an EDL (External Dynamic List) using the Export Generic Indicators Service integration in Cortex XSOAR. That EDL should be connected to PAN-OS. It also assumes that a DNS sinkhole is configured in the PAN-OS firewall. However, these are not required for the sole purpose of tagging the domains.

Note: This playbook has inputs from both the "From context data" tab and the "From indicators" tab.
PAN-OS - Job - Remove Malicious Domains From SinkholeThis playbook should be run as a job. It is used to periodically remove the specified tag from domain indicators. It should be used in conjunction with the "PAN-OS - Job - Add Malicious Domains To Sinkhole" playbook, to stop domains from being sinkholed after a certain amount of time.
The idea is that traffic to malicious domains will not be redirected to a sinkhole address forever, as malicious domains tend to lose their malicious properties (become inactive, get taken down, or the malware using them is no longer used or maintained).
PAN-OS Commit ConfigurationDeprecated. Use PAN-OS Commit Configuration v2 instead.
PAN-OS Commit Configuration v2Commit the PAN-OS Panorama or Firewall configuration. If specified as Panorama, it also pushes the Policies to the specified Device Group in the instance.
PAN-OS create or edit policyThis playbook will automate the process of creating or editing a policy.
The first task in the playbook checks if there is a security policy that matches the playbook inputs. If there is no security policy that matches, a new policy will be created. If there is a security policy that matches, the user will be able to modify the existing policy or create a new hardened policy.
PAN-OS DAG ConfigurationThis playbook utilizes the Dynamic Address Group (DAG) capability of PAN-OS.
DAG enables analysts to create a rule one time, where the group is the source/destination, and adds IP addresses dynamically without the need to commit the configuration every time.

The playbook checks if the given tag already exists. If the tag exists, then the IP address is added to the tag.

If the tag does not exist, a new address group is created with the given tag and a matching rule, and the configuration is committed.
PAN-OS edit policyThis playbook guides the user in the process of editing an existing policy. The playbook sends a data collection form to retrieve the relevant parameters for editing the existing rule.
PAN-OS EDL Service ConfigurationDeprecated. No available replacement. This single-run playbook enables Cortex XSOAR's built-in External Dynamic List (EDL) as a service for system indicators, and configures PAN-OS EDL Objects and the respective firewall policy rules.
The EDLs will continuously update for each indicator that matches the query syntax input in the playbook
(to validate to which indicators the query applied, you need to enter the query syntax from the indicator tab at the top of the playbook inputs window as well).
If both the IP and URL indicator types exist in the query, it sorts the indicators into two EDLs, IP and URL. If only one indicator type exists in the query, only one EDL is created.
The playbook then creates EDL objects directing to the indicator lists and firewall policy rules in PAN-OS.
- It is recommended to configure a dedicated EDL Service instance for the usage of this playbook.
- If necessary to edit or update the EDL query after this playbook run, use the panorama-edit-edl command and panorama integration to update the URL containing the indicator query syntax.
PAN-OS EDL SetupDeprecated. Use PAN-OS EDL Setup v3 playbook instead. Configures an external dynamic list in PAN-OS.\nIn the event that the file exists on the web server, it will sync it to demisto. Then it will create an EDL object and a matching rule.
PAN-OS EDL Setup v3Deprecated. Use Generic Export Indicators Service instead.
PAN-OS Log Forwarding Setup And ConfigurationThis playbook sets up and maintains log forwarding for the Panorama rulebase.
It can be run when setting up a new instance, or as a periodic job to enforce log forwarding policy.
You can either update all rules and override previous profiles, or update only rules that do not have a log forwarding profile configured.
PAN-OS logging to Strata Logging Service - Action RequiredThis Playbook initiates the steps needed to investigate the PAN-OS logging to Strata Logging Service problems.
PAN-OS Query Logs For IndicatorsThis playbook queries the following PAN-OS log types: traffic, threat, url, data-filtering and wildfire. The playbook accepts inputs such as IP. hash, and url.
PAN-OS Search for Post Quantum Crypto Vuln SigsSearch Vuln Sigs in Threat Logs for use of Post Quantum Crypto Signatures
PAN-OS to Strata Logging Service Monitoring - Cron JobThis playbook verifies that your FWs sent logs to the Strata Logging Service in the last 12 hours. An email notification will be sent if it's not the case.
This playbook is designed to run as a job.
Panorama Query LogsQuery Panorama Logs of types: traffic, threat, url, data-filtering and wildfire.
PanoramaQueryTrafficLogsDeprecated. Use "PAN-OS Query Logs For Indicators" playbook instead. Queries traffic logs in a PAN-OS Panorama or Firewall device.
PANW - Hunting and threat detection by indicator typeDeprecated. Use the "PANW - Hunting and threat detection by indicator type V2" playbook instead.
PANW - Hunting and threat detection by indicator type V2Deprecated. Use the "Palo Alto Networks - Hunting And Threat Detection"\ \ playbook instead. Integrations list - Cortex (Traps, PAN-OS, Analytics)\nThis is a multipurpose\ \ playbook used for hunting and threat detection. The playbook receives inputs based\ \ on hashes, IP addresses, or domain names provided manually or from outputs by\ \ other playbooks. \nWith the received indicators, the playbook leverages Palo Alto\ \ Cortex data received by products such as Traps, Analytics and Pan-OS to search\ \ for IP addresses and hosts related to that specific hash. \nThe output provided\ \ by the playbook facilitates pivoting searches for possibly affected hosts, IP\ \ addresses, or users.
PANW IoT Incident Handling with ServiceNowThis playbook creates a ServiceNow ticket after the incident is enriched by Palo Alto Networks IoT security portal (previously Zingbox Cloud).
PANW IoT ServiceNow Tickets CheckThis playbook should be used in a recurring Job to check the ServiceNow ticket status for the Palo Alto Networks IoT (previously Zingbox) alerts or vulnerabilties.
PANW NGFW TS Agent DeploymentDeploy the PANW NGFW TS Agent to a Windows server
PANW Threat Vault - Signature SearchDeprecated. No available replacement.
PCAP AnalysisThis playbook leverages all of the PCAP miner and PCAP file extractor sub playbook capabilities, including: Search for specific values in a PCAP file Parse and enrich detected indicators such as IP addresses, URLs, email addresses and domains found by the search . * Carve (extract) files found in the http, smb and other protocols and perform enrichment and detonation.
PCAP File CarvingThis playbook is used to carve (extract) files from within PCAP files and perform enrichment and detonation of the extracted files. Supported PCAP file types are pcap, cap, pcapng. The playbook can handle one PCAP file per incident. Additional inputs allow the user to provide the WPA password for decrypting 802.11 (wireless) traffic and adding an RSA certificate to decrypt SSL traffic. Additional options enable you to filter the files to extract according to the file extension or the actual file type (MIME), and limit the amount of files to extract. Another feature enables you to specify a filter to create a new smaller PCAP file. To display the results within the relevant incident fields, the playbook needs to run in a PCAP Analysis incident type. For handling of PCAP files larger than 30 MB, refer to the PcapMinerV2 documentation.
PCAP Parsing And Indicator EnrichmentThis playbook is used to parse and extract indicators within PCAP files and perform enrichment on the detected indicators. Supported file types are pcap, cap, pcapng. The playbook can handle one PCAP file per incident. The user inputs which indicator types are to be enriched including, email, URLs, IP addresses. The user can specify in the inputs which indicators are internal or that will be treated as internal (not enriched). The user can also specify a specific regex pattern to search for. Another option is to specify the protocol types to be printed to context for data extraction. Additional inputs allow the user to provide the WPA password for decrypting 802.11 (wireless) traffic and add an RSA certificate to decrypt SSL traffic. To display the results within the relevant incident fields, the playbook needs to run in a PCAP Analysis incident type. For handling of PCAP files larger than 30 MB, refer to the PcapMinerV2 documentation.
PCAP SearchThis playbook is used to parse and search within PCAP files. Supported file types are pcap, cap, pcapng. The playbook can handle one PCAP file per incident. The user inputs which objects the playbook should search for in the PCAP. The values to search are IP addresses, CIDR ranges, and TCP or UDP ports or protocols. In the event that more than one input type was specified, specify in the QueryOperator input (such as IP addresses and TCP ports) if the PCAP filter query will use an AND or an OR operator between the inputs. Another option is to use advanced filters just like in Wireshark to use refined filters or for objects not specified in other inputs. Additional inputs allow the user to provide the WPA password for decrypting 802.11 (wireless) traffic and adding an RSA certificate to decrypt SSL traffic. To display the results within the relevant incident fields, the playbook needs to run in a PCAP Analysis incident type. For handling of PCAP files larger than 30 MB, refer to the PcapMinerV2 documentation.
Penfield AssignThis playbook invokes Penfield.AI backend to assign incident to an online analyst.
Pentera Filter And Create IncidentSub-playbook to select specific entries from the Pentera action report and create incidents for each of the selected entries
Pentera Run Scan
Pentera Run Scan and Create IncidentsThis playbook will run a pentera task given the Pentera task name. It will generate the full action report that contains all the actions that Pentera made during the scan, and will create incidents according to the filters in the Pentera Filter and Create incidents playbook.
Phishing - CoreDeprecated. Use Phishing - Core v2 instead.
Phishing - Core v2This playbook provides a basic response to phishing incidents, including:
- Calculating reputation for all indicators
- Extracting indicators from email attachments
- Calculating severity for the incident based on indicator reputation
- Updating the reporting user about investigation status
- Enabling manual incident remediation

This updated playbook uses:
1) Incident fields instead of labels
2) The "Process Email - Core v2" playbook
Phishing - Create New IncidentThis playbook take arguments which will be used to create a new phishing incident. It is needed for scenarios such as creating several incidents based on values stored in the context. In such scenarios, the playbook can be looped.
Phishing - Generic v3This playbook investigates and remediates a potential phishing incident. It engages with the user who triggered the incident while investigating the incident itself.

Note:
- Final remediation tasks are manual by default. can be managed by "SearchAndDelete" and "BlockIndicators" inputs.
- Do not rerun this playbook inside a phishing incident since it can produce an unexpected result. Create a new incident instead if needed.
Phishing - Get Original Email LoopWhen the "Get Original Email - Generic v2" playbook is looped, there is no actual way to distinguish which retrieved file is related to which Message-ID. In order to solve this issue, this playbook will be looped instead and will output the "FileAssociation" key with the File-MessageID association.
Phishing - Handle Microsoft 365 Defender ResultsThis playbook is used to handle the results from the "Microsoft 365 Defender - Threat Hunting Generic" playbook inside a phishing incident. It performs the following actions:
1) Set the relevant incident fields based on the results, such as "Clicked URLs", "Malicious URL Viewed", and "Malicious URL Clicked".
2) In case the relevant playbook inputs were configured, it will create new incidents for each email returned in the results of the "Microsoft 365 Defender - Threat Hunting Generic" playbook. First, it will try to retrieve the original emails' files and then it will create an incident for each retrieved email.
3) Link the newly created incidents to the main originating incident.

Note that this playbook should only be used inside a phishing incident and not as a main playbook.
Phishing - Indicators HuntingHunt indicators related to phishing with available integrations and then handle the results. Handling the results will include setting relevant incident fields which will be displayed in the layout and optionally, opening new incidents according to the findings.
Current integration in this playbook:
- Microsoft 365 Defender (using "Advanced Hunting")

Note that this playbook should be used as a sub-playbook inside a phishing incident and not as a main playbook.
Phishing - Machine Learning AnalysisRuns various machine-learning based checks on phishing emails and URLs, in an attempt to predict whether they are phishing or benign. This playbook is available only on Cortex XSOAR.
Phishing - Search Related Incidents (Defender 365)This playbook should only be used as a sub-playbook inside the "Phishing - Handle Microsoft 365 Defender Results" playbook.
It searches through existing Cortex XSOAR incidents based on retrieved email message IDs and returns data only for emails that are not found in existing incidents.
Phishing Alerts - Check SeverityThis playbook calculates and assigns the incident severity based on the highest returned severity level from the following calculations:
- Email security alert action
- DBotScores of indicators
- Critical assets
- Email authenticity
- Current incident severity
- Microsoft Headers
Phishing Alerts InvestigationThis playbook investigates and remediates potential phishing incidents produced by either an email security gateway or a SIEM product. It retrieves original email files from the email security gateway or email service provider and generates a response based on the initial severity, hunting results, and the existence of similar phishing incidents in XSOAR.
No action is taken without an initial approval given by the analyst using the playbook inputs.
Phishing Investigation - GenericDeprecated. Use "Phishing Investigation - Generic v2" playbook instead. Use this playbook to investigate and remediate a potential phishing incident. The playbook simultaneously engages with the user that triggered the incident, while investigating the incident itself.
The final remediation tasks are always decided by a human analyst.
Phishing Playbook - ManualMaster playbook for phishing incidents. This playbook is a manual playbook.
PhishingDemo-OnboardingThis playbook is part of the on-boarding experience, and focuses on phishing scenarios. To use this playbook, you'll need to enable the `on-boarding` integration and configure incidents of type `Phishing`. For more information, refer to the on-boarding walkthroughs in the help section.
PhishLabs - Populate IndicatorsThis playbook can be used in a job to populate indicators from PhishLabs, according to a defined period of time.
PhishLabs - Whitelist false positivesThis playbook can be used in a job to add to the allow list indicators from PhishLabs that were classified as false positives, according to a defined period of time.
PhishUp Mail ScannerExtracts URLs from mail body and checks URLs with PhishUp. Takes action based on PhishUp results.
PICUS - Attack Validation AutomationPicus Attack Validation Automation
PICUS NG - Simulation Validation AutomationPicus NG Simulation Validation Automation
PII Check - Breach NotificationThe playbook checks for all various types of PII, however, each state determines what is considered PII, and which PII requires notification.

DISCLAIMER: Please consult with your legal team before implementing this playbook.

**Sources:
http://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=CIV&sectionNum=1798.82
https://www.nysenate.gov/legislation/laws/GBS/899-AA
and more for each state.
Policy Optimizer - Add Applications to Policy RulesThis playbook edits rules with unused applications or rules that are port based, and adds an application to the rule. It is used in PAN-OS - Policy Optimizer playbooks and includes communication tasks to get a rule name and the application to edit from the user.
Policy Optimizer - GenericThis playbook is triggered by the Policy Optimizer incident type, and can execute any of the following sub-playbooks:
- Policy Optimizer - Manage Unused Rules
- Policy Optimizer - Manage Rules with Unused Applications
- Policy Optimizer - Manage Port Based Rules
Policy Optimizer - Manage Port Based RulesThis playbook migrates port-based rules to application-based allow rules to reduce the attack surface and safely enable applications on your network.
Policy Optimizer - Manage Rules with Unused ApplicationsThis playbook helps identify and remove unused applications from security policy rules. If you have application-based security policy rules that allow a large number of applications, you can remove unused applications (applications never seen on the rules) from those rules to allow only applications actually seen in the rule’s traffic. This strengthens your security posture by reducing the attack surface.
Policy Optimizer - Manage Unused RulesThis playbook helps identify and remove unused rules that do not pass traffic in your environment.
Port Scan - External SourceThis playbook remediates port scans originating outside of the organization's network.
Port Scan - GenericInvestigates a port scan incident. The incident may originate from outside or within the network. The playbook:
- Enriches the hostname and IP address of the attacking endpoint
- Escalates the incident in case a critical asset is involved
- Hunts malware associated with the alerts across the organization
- Blocks detected malware associated with the incident
- Blocks IP addresses associated with the malware, if a malicious file was involved
- Pivots from the attacking IP to detect and block malicious domains hosted on the IP (for external scan)
- Isolates the attacking endpoint (for internal scan)
- Allows manual blocking of ports through an email communication task

If you're using one or more of the following products, make sure to configure their corresponding playbook inputs, respectively:
Splunk - "Splunk Indicator Hunting"
QRadar - "QRadar Indicator Hunting v2"
Palo Alto Networks Cortex Data Lake/Panorma/Autofocus/Analytics - "PANW - Hunting and threat detection by indicator type V2"
Port Scan - Internal SourceRemediates port scans originating within the network.
Possible External RDP Brute-ForceThis playbook investigates a “Possible External RDP Brute Force” XDR Alert by gathering user, IP, and hostname information, and investigating if the following suspicious elements exists:

- "IP Reputation" - DBot Score is 2-3
- "Source geolocation" - RDP Connection made from rare geo-location
- Related to campaign - IP address is related to campaign, based on TIM module
- Hunting results - the hunt for indicators related to the source IP and the related campaign returned results
- XDR Alert search - XDR Alerts that related to the same username and endpoint, and to the MITRE tactics that comes after "Credential Access", were found.
- Risky User - The user that was identified in the attack was given a medium or high score by the Core integration's ITDR module.
- Risky Host - The destination host that was identified in the attack was given a medium or high score by the Core integration's ITDR module.

Set verdict method:
Critical Element - The "Critical Element" input allows you to select a specific element that, if identified as suspicious, the investigation's final verdict will be deemed a "True Positive".

Final Verdict - Each suspicious element is being added to an array called "Suspicious Elements", which is used to count potential security threats. The array size will be compared to a final threshold. If the size is greater than or equal to the threshold, the investigation's final verdict will be deemed a "True Positive".

* User Engagement - The "UserEngagementThreshold" input allows you to set the number of suspicious elements that trigger user engagement. When this threshold is met, an email will be sent to the user and their manager asking for authorization of RDP activity. If the RDP activity is not authorized by the user, the investigation's final verdict will be deemed a "True Positive".
Possible External RDP Brute-Force - Set VerdictThis playbook creating an array called "Suspicious Elements", which is used to count potential security threats. The following elements can be added to the array:

- "IP Reputation" - DBot Score is 2-3
- "Source geolocation" - RDP Connection made from rare geo-location
- Related to campaign - IP address is related to campaign, based on TIM module
- Hunting results - the hunt for indicators related to the source IP and the related campaign returned results
- XDR Alert search - XDR Alerts that related to the same username and endpoint, and to the MITRE tactics that comes after "Credential Access", were found.
- Risky User - one or more risky users are involved in the incident, as identified by the Cortex Core - IR integration's ITDR module.
- Risky Host - one or more risky hosts are involved in the incident, as identified by the Cortex Core - IR integration's ITDR module.

The array will then be outputted and its size will be compared to a final threshold. If the size is greater than or equal to the threshold, the investigation's final verdict will be deemed a "True Positive."
Post Intrusion Ransomware InvestigationProvides the first step in the investigation of ransomware attacks.
The playbook requires the ransom note and an example of an encrypted file (<1MB) to try to identify the ransomware and find a recovery tool via the online database.
You will be guided with further investigation steps throughout the playbook, some of the key features are:

- Encrypted file owner investigation
- Endpoint forensic investigation
- Active Directory investigation
- Timeline of the breach investigation
- Indicator and account enrichment

Playbook settings and mapping:
For the full operation of the playbook, the following data should be mapped to the relevant incident fields.
Username - Usernames (common incident field)
Hostname - Hostnames (common incident field)



Powershell Payload ResponseThe Powershell Payload Response playbook is designed to be used when file payload executions are detected from an endpoint machines Powershell and begins the remediation process.
Prepare your CTFThis playbook aims to assit in configuring you env for the Capture The Flag (CTF) game.
Prisma Access - Logout UserThis playbook forces logout of a specific user and computer from Prisma Access.
Prisma Access - Connection Health CheckUse the Prisma Access integration to run SSH CLI commands and query the connection states for all tunnels. If any tunnels are down - the playbook escalates to a manual task for remediation and provides recommendations on next steps in the task description. The playbook can be run as a job, or triggered from an incoming event to confirm an initial suspicion (such as a tunnel log from Cortex Data Lake) to validate that the issue still exists.
Prisma Access Whitelist Egress IPs on SaaS ServicesRetrieve Prisma Access Egress IP for specific geographic zones and populate in security groups within cloud services.
Prisma Cloud - Find AWS Resource by FQDNDeprecated. Use Prisma Cloud - Find AWS Resource by FQDN v2 instead.
Find AWS resources by FQDN using Prisma Cloud inventory.
Supported services: EC2, Application Load Balancer, ECS, Route53, CloudFront, S3, API Gateway.
Prisma Cloud - Find AWS Resource by FQDN v2Find AWS resources by FQDN using Prisma Cloud inventory.
Supported services: EC2, Application Load Balancer, ECS, Route53, CloudFront, S3, API Gateway.
Prisma Cloud - Find AWS Resource by Public IPDeprecated. Use Prisma Cloud - Find AWS Resource by Public IP v2 instead.
Find AWS resources by Public IP using Prisma Cloud inventory.
Supported services: EC2, Network Load Balancer, ECS, Route53.
Prisma Cloud - Find AWS Resource by Public IP v2Find AWS resources by Public IP using Prisma Cloud inventory.
Supported services: EC2, Network Load Balancer, ECS, Route53.
Prisma Cloud - Find Azure Resource by FQDNDeprecated. Use Prisma Cloud - Find Azure Resource by FQDN v2 instead.
Find Azure resources by FQDN using Prisma Cloud inventory.
Supported services: Azure VM, Azure Load Balancer, Azure Application Gateway, AKS, Azure Web Apps, Azure Storage.
Prisma Cloud - Find Azure Resource by FQDN v2Find Azure resources by FQDN using Prisma Cloud inventory.
Supported services: Azure VM, Azure Load Balancer, Azure Application Gateway, AKS, Azure Web Apps, Azure Storage.
Prisma Cloud - Find Azure Resource by Public IPDeprecated. Use Prisma Cloud - Find Azure Resource by Public IP v2 instead.
Find Azure resources by Public IP using Prisma Cloud inventory.
Supported services: Azure VM, Azure Load Balancer, Azure Application Gateway, Azure Web Apps.
Prisma Cloud - Find Azure Resource by Public IP v2Find Azure resources by Public IP using Prisma Cloud inventory.
Supported services: Azure VM, Azure Load Balancer, Azure Application Gateway, Azure Web Apps.
Prisma Cloud - Find GCP Resource by FQDNDeprecated. Use Prisma Cloud - Find GCP Resource by FQDN v2 instead.
Find GCP resources by FQDN using Prisma Cloud inventory.
Supported services: Cloud DNS.
Prisma Cloud - Find GCP Resource by FQDN v2Find GCP resources by FQDN using Prisma Cloud inventory.
Supported services: Cloud DNS.
Prisma Cloud - Find GCP Resource by Public IPDeprecated. Use Prisma Cloud - Find GCP Resource by Public IP v2 instead.
Find GCP resources by Public IP using Prisma Cloud inventory.
Supported services: GCE, Load Balancing, GKE.
Prisma Cloud - Find GCP Resource by Public IP v2Find GCP resources by Public IP using Prisma Cloud inventory.
Supported services: GCE, Load Balancing, GKE.
Prisma Cloud - Find Public Cloud Resource by FQDNFind Public Cloud resources by FQDN using Prisma Cloud inventory
Prisma Cloud - Find Public Cloud Resource by Public IPFind Public Cloud resource by Public IP using Prisma Cloud inventory
Prisma Cloud - Find Public Cloud Resource by Public IP v2Find Public Cloud resource by Public IP using Prisma Cloud inventory
Prisma Cloud - Get Account OwnerRetrieves the details of the owner of a given cloud account from the following playbooks:
- Get Cloud Account Owner - Generic
- Prisma Cloud - Get Owner By Namespace
Prisma Cloud - Get Owner By NamespaceThis playbook will retrieve the potential owners of a runtime audit alert.
This is done using the "Namespace" value of the incident in order to query associated resource lists and user roles with associated users.
Eventually the playbook returns a list of user objects (if found).
Prisma Cloud - Network API and Anomaly IncidentsThis playbook handles incidents of internet exposed services and detect potential risky configurations that can make your cloud environment vulnerable to attacks, and
incidents of unusual network and user activity for all users, and are especially critical for privileged users and assumed roles where detecting unusual activity may indicate the first steps in a potential misuse or account compromise.
Prisma Cloud - RQL ExecutionThis playbook enables Prisma Cloud RQL Execution from the alert layout.
Prisma Cloud - VM Alert PrioritizationThis playbook handles incidents related to dozens of Prisma Cloud public VM alerts.
It determines the severity of the ingested alert based on data returned from Cortex XSOAR commands interacting with the Prisma Cloud API and creates new issues in either Slack or Jira, with all of the relevant information.
The playbook updates the Cortex XSOAR incident’s layout with information the analyst can use to investigate the alert. It also extracts and enriches indicators using existing configured integrations and then closes the investigation.

The flow of this playbook is as following:
1) Check the CSP type.
2) Check whether there's a public IP associated to the instance. In case there is, it will continue to other steps, if not, it will set the severity of the incident to "Low" and will close the incident.
3) Check if there are any vulnerabilities or findings related to the instance.
4) Check if there are any IAM permissions associated to the instance.
5) Set the incident severity based on the results:
- Low - No public IP was found.
- Medium - Public IP was found, other checks didn't return results.
- High - Public IP was found and also one of the other checks returned results.
- Critical - Public IP was found and both of the other checks returned results.
6) Notifications and ticketing with 3rd party systems.
7) Close the incident.

This playbook will run when a new incident is created with the Prisma Cloud - VM Alert Prioritization incident type which also includes a dedicated layout.
Prisma Cloud Compute - Audit AlertDeprecated. Use "Prisma Cloud Compute - Audit Alert v3" instead. Default playbook for parsing Prisma Cloud Compute audit alerts
Prisma Cloud Compute - Audit Alert Compliance EnrichmentThis is a sub-playbook of the "Prisma Cloud Compute - Audit Alert v2" playbook.
Retrieves the following information:
- Alert profiles.
- Container WAAS policies.
- Image compliance issues.
Prisma Cloud Compute - Audit Alert EnrichmentThis is a sub-playbook of the "Prisma Cloud Compute - Audit Alert v2" playbook.
It does the following:
- Runs the "Prisma Cloud - Get Account Owner" playbook in order to retrieve potential owners for the alert.
- Sets the incident link to the layout.
- Pulls image details and alerts
- Pulls host scan results.
Prisma Cloud Compute - Audit Alert v2Deprecated. Use "Prisma Cloud Compute - Audit Alert v3" instead. Default playbook for parsing and enrichment of Prisma Cloud Compute audit alerts.
Prisma Cloud Compute - Audit Alert v3Default playbook for parsing and enrichment of Prisma Cloud Compute audit alerts.
The playbook has the following sections:
Enrichment:
- Image details
- Similar container events
- Owner details
- Vulnerabilities
- Compliance details
- Forensics
- Defender logs.

Remediation:
- Block Indicators - Generic v3
- Cloud Response - Generic
- Manual Remediation.

Currently, the playbook supports incidents created by Runtime and WAAS triggers.
Prisma Cloud Compute - Audit Alert Vulnerabilities EnrichmentThis is a sub-playbook of the "Prisma Cloud Compute - Audit Alert v2" playbook.
It creates CVE indicators based on image or host vulnerabilities.
Prisma Cloud Compute - Cloud Discovery AlertDefault playbook for parsing Prisma Cloud Compute Cloud Discovery alerts
Prisma Cloud Compute - Compliance AlertDeprecated. Use Prisma Cloud Compute - Compliance Alert v2 instead.
Prisma Cloud Compute - Compliance Alert Container Enrichment LoopThis is a sub-playbook of the "Prisma Cloud Compute - Compliance Alert v2" playbook.
It will loop through all of the given compliance issue IDs and will retrieve the following information for each affected container based on the compliance issue ID:
- Container ID
- Compliance Issues
- Compliance Distribution
- Hostname
- Image Name
- Cloud MetaData

The enriched information will be displayed in the layout in a dedicated table under the "Container Compliance Information" tab.
Prisma Cloud Compute - Compliance Alert Host Enrichment LoopThis is a sub-playbook of the "Prisma Cloud Compute - Compliance Alert v2" playbook.
It will loop through all of the given compliance issue IDs and will retrieve the following information for each affected host based on the compliance issue ID:
- Hostname
- Compliance Issues
- Compliance Distribution
- Cloud MetaData

The enriched information will be displayed in the layout in a dedicated table under the "Host Compliance Information" tab.
Prisma Cloud Compute - Compliance Alert Image Enrichment LoopThis is a sub-playbook of the "Prisma Cloud Compute - Compliance Alert v2" playbook.
It will loop through all of the given compliance issue IDs and will retrieve the following information for each affected image based on the compliance issue ID:
- Image ID
- Compliance Issues
- Compliance Distribution
- Hosts
- Image Instances
- Cloud MetaData

The enriched information will be displayed in the layout in a dedicated table under the "Image Compliance Information" tab.
Prisma Cloud Compute - Compliance Alert v2Playbook for enriching Prisma Cloud Compute compliance alerts.
It will handle hosts, images and container compliance alerts.
Each sub-playbook in this playbook is dedicated to a specific resource type: host, container or image, and will loop through all of the retrieved Compliance Issue IDs in order to retrieve enriched information about each of the resources.
The enriched information will be displayed in the layout under dedicated tabs and includes resources information like hostnames, container ID, image ID, cloud provider info, enriched compliance issue details and more.

In addition, the playbook can create and update external ticketing systems for each compliance issue automatically with the relevant enriched information. In order to do so, fill the relevant playbook inputs.
Prisma Cloud Compute - Container ForensicsThis is a sub-playbook of the "Prisma Cloud Compute - Audit Alert v2" playbook.
Gets the container profile and forensics.
Prisma Cloud Compute - Get Container EventsThis is a sub-playbook of the "Prisma Cloud Compute - Audit Alert v2" playbook.
- Get container runtime or WAAS events and set it in the layout.
Prisma Cloud Compute - Get Defender LogsThis is a sub-playbook of the “Prisma Cloud Compute - Audit Alert v2” playbook.
- Gets defender logs and sets them to layout
- Downloads defender logs
- Gets defender backups
Prisma Cloud Compute - Jira Compliance IssueThis playbook is a sub-playbook of the "Prisma Cloud Compute - Compliance Alert Host Enrichment Loop" playbook.
It creates a new Jira issue or updates an existing Jira issue for each compliance ID retrieved in the original Prisma Cloud compliance alert, with enriched data for each resource (host, image or container).
Prisma Cloud Compute - Jira Ticket (Markdown Table)This playbook is a sub-playbook of the "Prisma Cloud Compute - Jira Compliance Issue" playbook.
It creates a new Jira issue or updates an existing Jira issue with a markdown table for the given compliance ID retrieved from the parent playbook, with enriched data for each resource (host, image or container).
Prisma Cloud Compute - Jira Ticket (XLSX)This playbook is a sub-playbook of the "Prisma Cloud Compute - Jira Compliance Issue" playbook.
It creates a new Jira issue or updates an existing Jira issue with an XLSX file for the given compliance ID retrieved from the parent playbook, with enriched data for each resource (host, image or container).
Prisma Cloud Compute - ServiceNow Compliance TicketThis playbook is a sub-playbook of the "Prisma Cloud Compute - Compliance Alert Host Enrichment Loop" playbook.
It creates a new ServiceNow ticket or updates an existing ServiceNow ticket for each compliance ID retrieved in the original Prisma Cloud compliance alert, with enriched data for each resource (host, image or container).
Prisma Cloud Compute - ServiceNow Ticket (HTML Table)This playbook is a sub-playbook of the "Prisma Cloud Compute - ServiceNow Compliance Ticket" playbook.
It creates a new ServiceNow ticket or updates an existing ServiceNow ticket with an HTML table for the given compliance ID retrieved from the parent playbook, with enriched data for each resource (host, image or container).
Prisma Cloud Compute - ServiceNow Ticket (XLSX)This playbook is a sub-playbook of the "Prisma Cloud Compute - ServiceNow Compliance Ticket" playbook.
It creates a new ServiceNow ticket or updates an existing ServiceNow ticket with an XLSX file for the given compliance ID retrieved from the parent playbook, with enriched data for each resource (host, image or container).
Prisma Cloud Compute - Vulnerability AlertDefault playbook for parsing Prisma Cloud Compute vulnerability alerts
Prisma Cloud Compute Vulnerability and Compliance ReportingDeprecated. No available replacement.
Prisma Cloud Correlate AlertsDeprecated. Use Prisma Cloud Correlate Alerts v2 instead. Search alerts in Prisma Cloud for a specific asset ID and, if present in XSOAR, link them.
Prisma Cloud Correlate Alerts v2Search alerts in Prisma Cloud for a specific asset ID and, if present in Cortex XSOAR, link them.
Prisma Cloud Remediation - AWS CloudTrail is not Enabled on the AccountAWS Cloudtrail is a service which provides event history of your AWS account activity, including actions taken through the AWS Management Console, AWS SDKs, command line tools, and other AWS services. To remediate Prisma Cloud Alert "CloudTrail is not enabled on the account", this playbook creates an S3 bucket to host Cloudtrail logs and enable Cloudtrail (includes all region events and global service events).
Prisma Cloud Remediation - AWS CloudTrail MisconfigurationDeprecated. Use Prisma Cloud Remediation - AWS CloudTrail Misconfiguration v2 instead.
This playbook remediates Prisma Cloud AWS CloudTrail alerts. It calls sub-playbooks that perform the actual remediation steps.

Remediation:
- AWS CloudTrail Trail Log Validation Is Not Enabled In All Regions
- AWS CloudTrail is not enabled in all regions
- AWS CloudTrail Trail Is Not Integrated With CloudWatch Logs
- AWS CloudTrail is not enabled on the account
Prisma Cloud Remediation - AWS CloudTrail Misconfiguration v2This playbook remediates Prisma Cloud AWS CloudTrail alerts. It calls sub-playbooks that perform the actual remediation steps.

Remediation:
- AWS CloudTrail Trail Log Validation Is Not Enabled In All Regions
- AWS CloudTrail is not enabled in all regions
- AWS CloudTrail Trail Is Not Integrated With CloudWatch Logs
- AWS CloudTrail is not enabled on the account.
Prisma Cloud Remediation - AWS CloudTrail Trail MisconfigurationThis playbook remediates the following Prisma Cloud AWS CloudTrail alerts.

Prisma Cloud policies remediated:

- AWS CloudTrail Trail Log Validation Is Not Enabled In All Regions
- AWS CloudTrail is not enabled in all regions.
Prisma Cloud Remediation - AWS EC2 Instance MisconfigurationDeprecated. Use Prisma Cloud Remediation - AWS EC2 Instance Misconfiguration v2 instead.
This playbook remediates Prisma Cloud AWS EC2 alerts. It calls the following sub-playbooks to perform the remediation:
- AWS Default Security Group Does Not Restrict All Traffic
- AWS Security Groups Allow Internet Traffic
- AWS Security Groups With Inbound Rule Overly Permissive To All Traffic
- AWS Security Groups allow internet traffic from internet to FTP-Data port (20)
- AWS Security Groups allow internet traffic from internet to FTP port (21)
- AWS Security Groups allow internet traffic to SSH port (22)
- AWS Security Group allows all traffic on SSH port (22)
- AWS Security Groups allow internet traffic from internet to Telnet port (23)
- AWS Security Groups allow internet traffic from internet to SMTP port (25)
- AWS Security Groups allow internet traffic from internet to DNS port (53)
- AWS Security Groups allow internet traffic from internet to Windows RPC port (135)
- AWS Security Groups allow internet traffic from internet to NetBIOS port (137)
- AWS Security Groups allow internet traffic from internet to NetBIOS port (138)
- AWS Security Groups allow internet traffic from internet to CIFS port (445)
- AWS Security Groups allow internet traffic from internet to SQLServer port (1433)
- AWS Security Groups allow internet traffic from internet to SQLServer port (1434)
- AWS Security Groups allow internet traffic from internet to MYSQL port (3306)
- AWS Security Groups allow internet traffic from internet to RDP port (3389)
- AWS Security Groups allow internet traffic from internet to MSQL port (4333)
- AWS Security Groups allow internet traffic from internet to PostgreSQL port (5432)
- AWS Security Groups allow internet traffic from internet to VNC Listener port (5500)
- AWS Security Groups allow internet traffic from internet to VNC Server port (5900)
Prisma Cloud Remediation - AWS EC2 Instance Misconfiguration v2This playbook remediates Prisma Cloud AWS EC2 alerts. It calls the following sub-playbooks to perform the remediation:
- AWS Default Security Group Does Not Restrict All Traffic (policy id: 2378dbf4-b104-4bda-9b05-7417affbba3f)
- AWS Security Group allows all traffic on SSH port (22) (policy id: 617b9138-584b-4e8e-ad15-7fbabafbed1a)
- AWS Security Groups allow internet traffic from internet to RDP port (3389) (policy id: b82f90ce-ed8b-4b49-970c-2268b0a6c2e5).
Prisma Cloud Remediation - AWS EC2 Security Group MisconfigurationThis playbook remediates the Prisma Cloud AWS EC2 alerts generated by the following policies:
- AWS Default Security Group Does Not Restrict All Traffic
- AWS Security Group allows all traffic on SSH port (22).
Prisma Cloud Remediation - AWS IAM Password Policy MisconfigurationThis playbook remediates the following Prisma Cloud AWS IAM password policy alerts.

Prisma Cloud policies remediated:
- AWS IAM password policy allows password reuse
- AWS IAM password policy does not expire in 90 days
- AWS IAM password policy does not have a lowercase character
- AWS IAM password policy does not have a minimum of 14 characters
- AWS IAM password policy does not have a number
- AWS IAM password policy does not have a symbol
- AWS IAM password policy does not have a uppercase character
- AWS IAM password policy does not have password expiration period
- AWS IAM Password policy is insecure
Prisma Cloud Remediation - AWS IAM Policy MisconfigurationDeprecated. Use Prisma Cloud Remediation - AWS IAM Policy Misconfiguration v2 instead. This playbook remediates Prisma Cloud AWS IAM policy alerts. It uses sub-playbooks that perform the remediation steps.
Prisma Cloud Remediation - AWS IAM Policy Misconfiguration v2This playbook remediates Prisma Cloud AWS IAM policy alerts. It uses sub-playbooks that perform the remediation steps.
Prisma Cloud Remediation - AWS Inactive Users For More Than 30 DaysTo increase the security of your AWS account, it is recommended to find and remove IAM user credentials (passwords, access keys) that have not been used within a specified period of time.

To remediate Prisma Cloud Alert Inactive users for more than 30 days, this playbook deactivates the user by disabling the access keys (marking them as inactive) as well as resetting the user console password.
Prisma Cloud Remediation - AWS Security Groups Allows Internet Traffic To TCP PortThis playbook extracts the TCP public Security Groups rule and provides manual/automatic options to have the rules revoked.
Prisma Cloud Remediation - Azure AKS Cluster MisconfigurationThis playbook remediates the following Prisma Cloud Azure AKS cluster alerts.

Prisma Cloud policies remediated:

- Azure AKS cluster monitoring not enabled
- Azure AKS cluster HTTP application routing enabled
Prisma Cloud Remediation - Azure AKS MisconfigurationDeprecated. Use Prisma Cloud Remediation - Azure AKS Misconfiguration v2 instead.
This playbook remediates Prisma Cloud Azure AKS alerts. It calls sub-playbooks that perform the actual remediation steps.

Remediation:
- Azure AKS cluster monitoring not enabled
- Azure AKS cluster HTTP application routing enabled
Prisma Cloud Remediation - Azure AKS Misconfiguration v2This playbook remediates Prisma Cloud Azure AKS alerts. It calls sub-playbooks that perform the actual remediation steps.

Remediation:
- Azure AKS cluster monitoring not enabled
- Azure AKS cluster HTTP application routing enabled
Prisma Cloud Remediation - Azure Network MisconfigurationDeprecated. Use Prisma Cloud Remediation - Azure Network Misconfiguration v2 instead.
This playbook remediates Prisma Cloud Azure Network alerts. It calls sub-playbooks that perform the actual remediation steps.

Remediation:

- Azure Network Security Group (NSG) having Inbound rule overly permissive to allow all traffic from any source on any protocol
- Azure Network Security Group (NSG) having Inbound rule overly permissive to allow all traffic from any source on TCP protocol
- Azure Network Security Group (NSG) having Inbound rule overly permissive to allow all traffic from any source on UDP protocol
- Azure Network Security Group (NSG) allows SSH traffic from internet on port 22
- Azure Network Security Group (NSG) allows traffic from internet on port 3389
- Azure Network Security Group allows DNS (TCP Port 53)
- Azure Network Security Group allows FTP (TCP Port 21)
- Azure Network Security Group allows FTP-Data (TCP Port 20)
- Azure Network Security Group allows MSQL (TCP Port 4333)
- Azure Network Security Group allows MySQL (TCP Port 3306)
- Azure Network Security Group allows Windows RPC (TCP Port 135)
- Azure Network Security Group allows Windows SMB (TCP Port 445)
- Azure Network Security Group allows PostgreSQL (TCP Port 5432)
- Azure Network Security Group allows SMTP (TCP Port 25)
- Azure Network Security Group allows SqlServer (TCP Port 1433)
- Azure Network Security Group allows Telnet (TCP Port 23)
- Azure Network Security Group allows VNC Listener (TCP Port 5500)
- Azure Network Security Group allows all traffic on ICMP (Ping)
- Azure Network Security Group allows CIFS (UDP Port 445)
- Azure Network Security Group allows NetBIOS (UDP Port 137)
- Azure Network Security Group allows NetBIOS (UDP Port 138)
- Azure Network Security Group allows SQLServer (UDP Port 1434)
- Azure Network Security Group allows DNS (UDP Port 53)
Prisma Cloud Remediation - Azure Network Misconfiguration v2This playbook remediates Prisma Cloud Azure Network alerts. It calls sub-playbooks that perform the actual remediation steps.

Remediation:

- Azure Network Security Group (NSG) having Inbound rule overly permissive to allow all traffic from any source on any protocol
- Azure Network Security Group (NSG) having Inbound rule overly permissive to allow all traffic from any source on TCP protocol
- Azure Network Security Group (NSG) having Inbound rule overly permissive to allow all traffic from any source on UDP protocol
- Azure Network Security Group (NSG) allows SSH traffic from internet on port 22
- Azure Network Security Group (NSG) allows traffic from internet on port 3389
- Azure Network Security Group allows DNS (TCP Port 53)
- Azure Network Security Group allows FTP (TCP Port 21)
- Azure Network Security Group allows FTP-Data (TCP Port 20)
- Azure Network Security Group allows MSQL (TCP Port 4333)
- Azure Network Security Group allows MySQL (TCP Port 3306)
- Azure Network Security Group allows Windows RPC (TCP Port 135)
- Azure Network Security Group allows Windows SMB (TCP Port 445)
- Azure Network Security Group allows PostgreSQL (TCP Port 5432)
- Azure Network Security Group allows SMTP (TCP Port 25)
- Azure Network Security Group allows SqlServer (TCP Port 1433)
- Azure Network Security Group allows Telnet (TCP Port 23)
- Azure Network Security Group allows VNC Listener (TCP Port 5500)
- Azure Network Security Group allows all traffic on ICMP (Ping)
- Azure Network Security Group allows CIFS (UDP Port 445)
- Azure Network Security Group allows NetBIOS (UDP Port 137)
- Azure Network Security Group allows NetBIOS (UDP Port 138)
- Azure Network Security Group allows SQLServer (UDP Port 1434)
- Azure Network Security Group allows DNS (UDP Port 53).
Prisma Cloud Remediation - Azure Network Security Group MisconfigurationThis playbook remediates the following Prisma Cloud Azure Network security group alerts.

Prisma Cloud policies remediated:

- Azure Network Security Group (NSG) having Inbound rule overly permissive to allow all traffic from any source on any protocol
- Azure Network Security Group (NSG) having Inbound rule overly permissive to allow all traffic from any source on TCP protocol
- Azure Network Security Group (NSG) having Inbound rule overly permissive to allow all traffic from any source on UDP protocol
- Azure Network Security Group (NSG) allows SSH traffic from internet on port 22
- Azure Network Security Group (NSG) allows traffic from internet on port 3389
- Azure Network Security Group allows DNS (TCP Port 53)
- Azure Network Security Group allows FTP (TCP Port 21)
- Azure Network Security Group allows FTP-Data (TCP Port 20)
- Azure Network Security Group allows MSQL (TCP Port 4333)
- Azure Network Security Group allows MySQL (TCP Port 3306)
- Azure Network Security Group allows Windows RPC (TCP Port 135)
- Azure Network Security Group allows Windows SMB (TCP Port 445)
- Azure Network Security Group allows PostgreSQL (TCP Port 5432)
- Azure Network Security Group allows SMTP (TCP Port 25)
- Azure Network Security Group allows SqlServer (TCP Port 1433)
- Azure Network Security Group allows Telnet (TCP Port 23)
- Azure Network Security Group allows VNC Listener (TCP Port 5500)
- Azure Network Security Group allows all traffic on ICMP (Ping)
- Azure Network Security Group allows CIFS (UDP Port 445)
- Azure Network Security Group allows NetBIOS (UDP Port 137)
- Azure Network Security Group allows NetBIOS (UDP Port 138)
- Azure Network Security Group allows SQLServer (UDP Port 1434)
- Azure Network Security Group allows DNS (UDP Port 53)
Prisma Cloud Remediation - Azure SQL Database MisconfigurationThis playbook remediates the following Prisma Cloud Azure SQL database alerts.

Prisma Cloud policies remediated:

- Azure SQL database auditing is disabled
- Azure SQL Database with Auditing Retention less than 90 days
- Azure Threat Detection on SQL databases is set to Off
- Azure SQL Database with Threat Retention less than or equals to 90 days
Prisma Cloud Remediation - Azure SQL MisconfigurationDeprecated. Use Prisma Cloud Remediation - Azure SQL Misconfiguration v2 instead.
This playbook remediates Prisma Cloud Azure SQL alerts. It calls sub-playbooks that perform the actual remediation steps.

Remediation:

- Azure SQL database auditing is disabled
- Azure SQL Database with Auditing Retention less than 90 days
- Azure Threat Detection on SQL databases is set to Off
- Azure SQL Database with Threat Retention less than or equals to 90 days
Prisma Cloud Remediation - Azure SQL Misconfiguration v2This playbook remediates Prisma Cloud Azure SQL alerts. It calls sub-playbooks that perform the actual remediation steps.

Remediation:

- Azure SQL database auditing is disabled
- Azure SQL Database with Auditing Retention less than 90 days
- Azure Threat Detection on SQL databases is set to Off
- Azure SQL Database with Threat Retention less than or equals to 90 days
Prisma Cloud Remediation - Azure Storage Blob MisconfigurationThis playbook remediates the following Prisma Cloud Azure Storage blob alerts.

Prisma Cloud policies remediated:

- Azure storage account has a blob container with public access
- Azure storage account logging for blobs is disabled
Prisma Cloud Remediation - Azure Storage MisconfigurationDeprecated. Use Prisma Cloud Remediation - Azure Storage Misconfiguration v2 instead.
This playbook remediates Prisma Cloud Azure Storage alerts. It calls sub-playbooks that perform the actual remediation steps.

Remediation:

- Azure storage account has a blob container with public access
- Azure storage account logging for blobs is disabled
- Azure Storage Accounts without Secure transfer enabled
- Azure storage account logging for queues is disabled
- Azure storage account logging for tables is disabled #95
Prisma Cloud Remediation - Azure Storage Misconfiguration v2This playbook remediates Prisma Cloud Azure Storage alerts. It calls sub-playbooks that perform the actual remediation steps.

Remediation:

- Azure storage account has a blob container with public access
- Azure storage account logging for blobs is disabled
- Azure Storage Accounts without Secure transfer enabled
- Azure storage account logging for queues is disabled
- Azure storage account logging for tables is disabled
Prisma Cloud Remediation - GCP Compute Engine MisconfigurationDeprecated. Use Prisma Cloud Remediation - GCP Compute Engine Misconfiguration v2 instead.
This playbook remediates Prisma Cloud GCP Compute Engine alerts. It calls sub-playbooks that perform the actual remediation steps.

Remediation:
- GCP VM instances have serial port access enabled
- GCP VM instances have block project-wide SSH keys feature disabled
- GCP VM instances without any custom metadata information
Prisma Cloud Remediation - GCP Compute Engine Misconfiguration v2This playbook remediates Prisma Cloud GCP Compute Engine alerts. It calls sub-playbooks that perform the actual remediation steps.

Remediation:
- GCP VM instances have serial port access enabled
- GCP VM instances have block project-wide SSH keys feature disabled
- GCP VM instances without any custom metadata information.
Prisma Cloud Remediation - GCP Kubernetes Engine Cluster MisconfigurationThis playbook remediates the following Prisma Cloud GCP Kubernetes Engine Cluster alerts.

Prisma Cloud policies remediated:

GCP Kubernetes Engine Clusters Basic Authentication is set to Enabled
GCP Kubernetes Engine Clusters have HTTP load balancing disabled
GCP Kubernetes Engine Clusters have Legacy Authorization enabled
GCP Kubernetes Engine Clusters have Master authorized networks disabled
GCP Kubernetes Engine Clusters have Network policy disabled
GCP Kubernetes Engine Clusters have Stackdriver Logging disabled
GCP Kubernetes Engine Clusters have Stackdriver Monitoring disabled
GCP Kubernetes Engine Clusters have binary authorization disabled
GCP Kubernetes Engine Clusters web UI/Dashboard is set to Enabled
GCP Kubernetes cluster intra-node visibility disabled
Prisma Cloud Remediation - GCP Kubernetes Engine MisconfigurationDeprecated. Use Prisma Cloud Remediation - GCP Kubernetes Engine Misconfiguration v2 instead.
This playbook remediates Prisma Cloud GCP Kubernetes Engine alerts. It calls sub-playbooks that perform the actual remediation steps.

Remediation:
GCP Kubernetes Engine Clusters Basic Authentication is set to Enabled
GCP Kubernetes Engine Clusters have HTTP load balancing disabled
GCP Kubernetes Engine Clusters have Legacy Authorization enabled
GCP Kubernetes Engine Clusters have Master authorized networks disabled
GCP Kubernetes Engine Clusters have Network policy disabled
GCP Kubernetes Engine Clusters have Stackdriver Logging disabled
GCP Kubernetes Engine Clusters have Stackdriver Monitoring disabled
GCP Kubernetes Engine Clusters have binary authorization disabled
GCP Kubernetes Engine Clusters web UI/Dashboard is set to Enabled
GCP Kubernetes cluster intra-node visibility disabled
Prisma Cloud Remediation - GCP Kubernetes Engine Misconfiguration v2This playbook remediates Prisma Cloud GCP Kubernetes Engine alerts. It calls sub-playbooks that perform the actual remediation steps.

Remediation:
GCP Kubernetes Engine Clusters Basic Authentication is set to Enabled
GCP Kubernetes Engine Clusters have HTTP load balancing disabled
GCP Kubernetes Engine Clusters have Legacy Authorization enabled
GCP Kubernetes Engine Clusters have Master authorized networks disabled
GCP Kubernetes Engine Clusters have Network policy disabled
GCP Kubernetes Engine Clusters have Stackdriver Logging disabled
GCP Kubernetes Engine Clusters have Stackdriver Monitoring disabled
GCP Kubernetes Engine Clusters have binary authorization disabled
GCP Kubernetes Engine Clusters web UI/Dashboard is set to Enabled
GCP Kubernetes cluster intra-node visibility disabled.
Prisma Cloud Remediation - GCP VPC Network Firewall MisconfigurationThis playbook remediates the following Prisma Cloud GCP VPC Network Firewall alerts.

Prisma Cloud policies remediated:

- GCP Firewall rule allows internet traffic to FTP port (21)
- GCP Firewall rule allows internet traffic to HTTP port (80)
- GCP Firewall rule allows internet traffic to MongoDB port (27017)
- GCP Firewall rule allows internet traffic to MySQL DB port (3306)
- GCP Firewall rule allows internet traffic to Oracle DB port (1521)
- GCP Firewall rule allows internet traffic to PostgreSQL port (5432)
- GCP Firewall rule allows internet traffic to RDP port (3389)
- GCP Firewall rule allows internet traffic to SSH port (22)
- GCP Firewall rule allows internet traffic to Telnet port (23)
- GCP Firewall rule allows internet traffic to DNS port (53)
- GCP Firewall rule allows internet traffic to Microsoft-DS port (445)
- GCP Firewall rule allows internet traffic to NetBIOS-SSN port (139)
- GCP Firewall rule allows internet traffic to POP3 port (110)
- GCP Firewall rule allows internet traffic to SMTP port (25)
- GCP Default Firewall rule should not have any rules (except http and https)
- GCP Firewall with Inbound rule overly permissive to All Traffic
Prisma Cloud Remediation - GCP VPC Network MisconfigurationDeprecated. Use Prisma Cloud Remediation - GCP VPC Network Misconfiguration v2 instead.
This playbook remediates Prisma Cloud GCP VPC Network alerts. It calls sub-playbooks that perform the actual remediation steps.

Remediation:

- GCP project is using the default network
- GCP Firewall rule allows internet traffic to FTP port (21)
- GCP Firewall rule allows internet traffic to HTTP port (80)
- GCP Firewall rule allows internet traffic to MongoDB port (27017)
- GCP Firewall rule allows internet traffic to MySQL DB port (3306)
- GCP Firewall rule allows internet traffic to Oracle DB port (1521)
- GCP Firewall rule allows internet traffic to PostgreSQL port (5432)
- GCP Firewall rule allows internet traffic to RDP port (3389)
- GCP Firewall rule allows internet traffic to SSH port (22)
- GCP Firewall rule allows internet traffic to Telnet port (23)
- GCP Firewall rule allows internet traffic to DNS port (53)
- GCP Firewall rule allows internet traffic to Microsoft-DS port (445)
- GCP Firewall rule allows internet traffic to NetBIOS-SSN port (139)
- GCP Firewall rule allows internet traffic to POP3 port (110)
- GCP Firewall rule allows internet traffic to SMTP port (25)
- GCP Default Firewall rule should not have any rules (except http and https)
- GCP Firewall with Inbound rule overly permissive to All Traffic
Prisma Cloud Remediation - GCP VPC Network Misconfiguration v2This playbook remediates Prisma Cloud GCP VPC Network alerts. It calls sub-playbooks that perform the actual remediation steps.

Remediation:

- GCP project is using the default network
- GCP Firewall rule allows internet traffic to FTP port (21)
- GCP Firewall rule allows internet traffic to HTTP port (80)
- GCP Firewall rule allows internet traffic to MongoDB port (27017)
- GCP Firewall rule allows internet traffic to MySQL DB port (3306)
- GCP Firewall rule allows internet traffic to Oracle DB port (1521)
- GCP Firewall rule allows internet traffic to PostgreSQL port (5432)
- GCP Firewall rule allows internet traffic to RDP port (3389)
- GCP Firewall rule allows internet traffic to SSH port (22)
- GCP Firewall rule allows internet traffic to Telnet port (23)
- GCP Firewall rule allows internet traffic to DNS port (53)
- GCP Firewall rule allows internet traffic to Microsoft-DS port (445)
- GCP Firewall rule allows internet traffic to NetBIOS-SSN port (139)
- GCP Firewall rule allows internet traffic to POP3 port (110)
- GCP Firewall rule allows internet traffic to SMTP port (25)
- GCP Default Firewall rule should not have any rules (except http and https)
- GCP Firewall with Inbound rule overly permissive to All Traffic
Prisma Cloud Remediation - GCP VPC Network Project MisconfigurationThis playbook remediates the following Prisma Cloud GCP VPC Network Project alerts.

Prisma Cloud policies remediated:

- GCP project is using the default network
Prisma SASE - Add IPs to Static Address GroupThis playbook appends a Static Address Group with provided IPs.
Prisma SASE - Block IPThis playbook assists in blocking communication with the provided IPs in the Prisma SASE policy.
If a group name is provided, the IPs will be added to the mentioned static address group (there should be a rule associated with the group name to block communication with that group).
And if the group name is not provided, a new group will be created with a dedicated rule to block communication with those IPs.
Prisma SASE - Block URLThe playbook will handle the operation of blocking a URL within the organization.
If a category is provided, the URL will be added to the list.
If not, a new URL category will be created, and a new security rule that blocks that category.
Prisma SASE - Create a security pre-rule for EDLThis playbook helps to create a security rule to block indicators from an EDL. This playbook should run only once to setup the EDL object and its rule.
Prisma SASE - Create Address ObjectThis playbook creates new address objects in the Prisma SASE Object section. Those objects can be used later on in other objects such as Security Rules.
Prisma SASE - Create or Edit EDL objectThis playbook helps to create an EDL object within the Prisma SASE Objects section.
Prisma SASE - Create or Edit Security Policy RuleThis playbook handles the creation or editing of the Security Policy Rule for Prisma SASE integration.
Prisma SASE - Quarantine a SentinelOne Host With Active Threat## Goal
This playbook is designed to automatically quarantine a SentinelOne host in response to a new threat incident trigger using Prisma SASE.

## Playbook Flow
- Trigger: The playbook activates upon the creation of a new SentinelOne Threat incident.
- Process:
1. Retrieves the Host ID from Cortex Data Lake.
2. Loads detailed information about the agent.
3. If the Host ID is found and the agent is not decommissioned, it initiates quarantine through Prisma SASE.

## Dependencies and Configuration
- This playbook requires being set as the default in the SentinelOne instance configuration.
- It specifically responds to events categorized as 'Threats'.
- Ensure that the Prisma SASE, Cortex Data Lake and SentinelOne integrations are properly configured and operational for seamless execution of this playbook.
Proactive Threat HuntingThis playbook is the main playbook of the 'Proactive Threat Hunting' pack. It automatically runs during a new hunting session and guides the threat hunter through the session based on the selected hunting method. The available hunting methods are:

- SDO Hunt: Constructs the hunting hypothesis based on SDO indicators (Campaign, Malware, Intrusion Set).
- Freestyle Hunt: Allows the threat hunter to provide their own queries and IOCs for hunting.
Proactive Threat Hunting - Block AccountThis playbook will be executed from the "Proactive Threat Hunting" layout button with the objective of blocking a user specified by the analyst.
Proactive Threat Hunting - Block IndicatorsThis playbook will be executed from the "Proactive Threat Hunting" layout button with the objective of blocking indicators specified by the analyst.
Proactive Threat Hunting - Endpoint IsolationThis playbook will be executed from the "Proactive Threat Hunting" layout button with the objective of isolating a host specified by the analyst.
Proactive Threat Hunting - Entity EnrichmentThis playbook will be executed from the "Proactive Threat Hunting" layout button with the objective of enriching information on hosts and users specified by the analyst.
Proactive Threat Hunting - Execute QueryThis playbook will be executed from the "Proactive Threat Hunting" layout button with the objective of executing a query that will be provided by the analyst. The playbook supports executing a query using the following integrations:

- Cortex XDR XQL Engine
- Microsoft Defender For Endpoint
Proactive Threat Hunting - Quarantine FileThis playbook will be executed from the “Proactive Threat Hunting” layout button with the objective of quarantining a file specified by the analyst. The following integration is supported:
- Cortex XDR IR
Proactive Threat Hunting - SDO Threat HuntingThis playbook will be executed when the analyst chooses to perform SDO hunting.
The playbook receives an SDO type indicator and executes the following steps:

- Searches IOCs related to the SDO indicator - IPs, Hashes, Domains, URLs.
- Hunts for the found IOCs using the "Threat Hunting - Generic" sub-playbook.
- Searches attack patterns that are related to the SDO indicator.
- Searches LOLBAS tools that are related to the found attack patterns.
- Hunts for LOLBin executions command-line arguments that are similar to LOLBAS malicious commands patterns.
Process Email - Add custom fieldsDeprecated. We recommend using Process Email - Generic playbook instead. Process email - Add email data to a phishing incident's custom fields
Process Email - CoreDeprecated. Use Process Email - Core v2 instead.
Process Email - Core v2This playbook adds email details to the relevant context entities and handles the case where original emails are attached.
Process Email - EWSProcess an EWS email
Process Email - GenericDeprecated. Use Process Email - Generic v2 instead.
Process Email - Generic v2This playbook adds email details to the relevant context entities and handles original email attachments.

The v2 playbook enables parsing email artifacts more efficiently, including:
- Using incident fields and not incident labels.
- Providing separate paths to "Phishing Alerts".
- Using the new "Get Original Email - Generic v2" playbook to retrieve original emails as EML files from the following integrations:
EWS v2
Microsoft Graph Mail integration
Gmail
FireEye EX and FireEye CM
Proofpoint Protection Server
Agari Phishing Defense (EWS v2, MSGraph Mail, Gmail)
* Mimecast.
Process Incident - Vectra XDRThis playbook is used to initiate the processing of an incident. This playbook runs when a pending incident is selected for investigation. It will change the state from pending to active and it will list the available users in Vectra and request the user ID to use for assignment. Once the data collection is complete, it will call the Dispatch Incident - Vectra XDR playbook.
Process Microsoft's Anti-Spam HeadersThis playbook stores the SCL, BCL, and PCL scores if they exist to the associated incident fields (Phishing SCL Score, Phishing PCL Score, and Phishing BCL Score).
It also does the following:
1) Sets the email classification to "spam" if the SCL score is equal to or greater than 5.
2) Sets the incident severity according to the playbook inputs (default is: PCL/BCL - Medium, SCL - Low). The severity of the incident is set only when one (or more) of the following occurs:
- PCL (Phishing Confidence Level) For a score between and including 4-8: The message content is likely to be phishing.
- BCL (Bulk Complaint Level) For a score between and including 4-7: The message is from a bulk sender that generates a mixed number of complaints.
For a score between and including 8-9: The message is from a bulk sender that generates a high number of complaints.
- SCL (Spam Confidence Level) For a score between and including 5-6: Spam filtering marks the message as spam.
For a score of 9: Spam filtering marks the message as high confidence spam. See anti-spam stamps.
Process QWatch Alert - QintelExtracts exposure records from a QWatch alert
Process Survey ResponseNote: This is a beta playbook, which lets you implement and test pre-release software. Since the playbook is in beta, it might contain bugs. Updates to the playbook during the beta phase might include non-backward compatible features. We appreciate your feedback on the quality and usability of the playbook to help us identify issues, fix them, and continually improve. This playbook processes the survery responses. It updates that the employee responded to the survey and what their health status is. If necessary, it opens IT or HR incidents, and updates the process survey tracker.
Proofpoint TAP - Event EnrichmentThis playbook enriches Proofpoint Targeted Attack Protection (TAP) incidents with forensic evidence.
By utilizing the 'proofpoint-get-forensics' command, the playbook retrieves forensic evidence based on the campaign ID and threat ID detected in the Proofpoint TAP incidents.
PS Remote Get File Sample From PathThis playbook leverages the Windows built-in PowerShell and WinRM capabilities to connect to a Windows host to acquire a file as forensic evidence for further analysis.
PS-Remote Acquire Host ForensicsThis playbook allows the user to gather multiple forensic data from a Windows endpoint including network traffic, MFT (Master File Table), and registry export by using the PS Remote automation which enables connecting to a Windows host without the need to install any 3rd-party tools using just native Windows management tools.
PS-Remote Get MFTThis playbook leverages the Windows built-in PowerShell and WinRM capabilities to connect to a Windows host to acquire and export the MFT (Master File Table) as forensic evidence for further analysis.
PS-Remote Get Network TrafficThis playbook leverages the Windows built-in PowerShell and WinRM capabilities to connect to a Windows host. It then connectst to the Netsh tool to create an ETL file which is the equivalent of a Wireshark PCAP file by using the PS-Remote integration. After receiving the resultant ETL, XSOAR will be able to convert the ETL to a PCAP file to be parsed and enriched later. Review the Microsoft documentation for how to use ETL filters (https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/jj129382(v=ws.11)#using-filters-to-limit-etl-trace-file-details).
PS-Remote Get RegistryThis playbook leverages the Windows built-in PowerShell and WinRM capabilities to connect to a Windows host to acquire and export the registry as forensic evidence for further analysis. The capture can be for the entire registry or for a specific hive or path.
Pull Request Creation - AzureDevOpsThis playbook creates a pull request using the AzureDevOps integration.
Pull Request Creation - BitbucketThis playbook creates a pull request using Bitbucket integration.
Pull Request Creation - GenericThis playbook creates a pull request from the content zip file.
Pull Request Creation - GithubThis playbook creates a pull request using Github integration.
Pull Request Creation - GitLabThis playbook creates a pull request using GitLab integration.
QRadar - Get offense correlationsDeprecated. Use the `QRadar - Get offense correlations v2` instead.\"\nRun on a QRadar offense to get more information\n\n Get all correlations relevant to the offense\n Get all logs relevant to the correlations (not done by default, set "GetCorrelationLogs\" to \"True\")\n\nInputs-\n GetCorrelationLogs (default - False)\n MaxLogsCount (default - 20)
QRadar - Get offense correlations v2Deprecated. Use the "QRadar - Get Offense Logs" playbook instead.
Run on a QRadar offense to get more information:

Get all correlations relevant to the offense
Get all logs relevant to the correlations (not done by default - set "GetCorrelationLogs" to "True")

Inputs:
GetCorrelationLogs (default: False)
MaxLogsCount (default: 20)
QRadar - Get Offense LogsWorks for QRadar integration version 3, v1 and v2 are deprecated.

Note: You can use the integration to fetch the events with the offense however it will fetch the events according to the specified limit defined in the instance settings. By using this playbook you can define an additional search to query a larger number of logs.

Default playbook inputs use the QRadar incident fields such as idoffense, starttime. These fields can be replaced but need to point to relevant offense ID and starttime fields.
QRadar Build Query and SearchThe QRadar Build Query and Search playbook creates an AQL query for the QRadar SIEM using the QRadarCreateAQLQuery automation queries. Complex queries take into consideration several inputs and allow including or excluding each of the values as well as performing a full or partial search. Each of the values can be searched across several fields.

The playbook supports 3 separate conditions to be evaluated.
For example, in the first condition, inputs will evaluate several user names that may or may not exist in several fields. The second input, can for example, evaluate for IP addresses in several fields that may or may not exist in several fields, and a third value can search for an event ID that may or may not exist in several fields. The results of all of the inputs will create an AQL query that covers all of the inputs combining all of the different conditions.

Each of the inputs is validated so in case the inputs are not set correctly, the user can review and run them again.
Also, populated inputs will be combined, meaning by populating the first and second values the resulting AQL query will be a combination of all of the values and not 3 separate searches. In addition, make sure to populate the inputs in order according to the indexed fields in QRadar (indexed fields should be provided before non indexed ones).
QRadar GenericThe QRadar Generic playbook is executed for the QRadar Generic incident type. It performs all the common parts of the investigation, including notifying the SOC, enriching data for indicators and users, calculating severity, assigning incidents, and notifying the SIEM admin about false positives.
QRadar Get Hunting ResultsThis playbook is used to sort the QRadar search results to display the IP addresses, assets, and usernames that the search provided. In addition, the results allow you to differentiate between internal and external IP addresses as well as query the QRadar assets API in order to get the assets details from the IP addresses. You can provide the QRadar fields names and the organizations' IP ranges in order to properly sort the data. The end result of the playbook will be the internal and external IP addresses detected as well as the assets and users.
QRadar Indicator Hunting V2The Playbook queries QRadar SIEM for indicators such as file hashes, IP addresses, domains, or urls.
QRadarCorrelationLogDeprecated. Use the "QRadar - Get Offense Logs"\ \ playbook instead. This playbook retrieves the correlation logs of multiple QIDs.
QRadarFullSearchDeprecated.Use the following command instead `qradar-search-retrieve-results`.
This playbook runs a QRadar query and return its results to the context.
Quarantine Device in Cisco ISE - PANW IoT 3rd Party IntegrationPlaybook to handle incident triggered from PANW Iot (Zingbox) UI to quarantine a device in Cisco ISE.
Query Cisco Stealthwatch FlowsThis playbook runs a query on Cisco Stealthwatch flows and return its results to the context.
Ransomware Advanced AnalysisThis playbook detects the ransomware type and searches for available decryptors.

The playbook uses the ID-Ransomware service, which allows you to detect the ransomware using multiple methods.
Ransomware Enrich and ContainThis playbook is responsible for ransomware alert data enrichment and response.
The playbook executes the following:

1.Checks if the initiator is a remote attacker and allows isolating the remote host, if possible.

2.Retrieves the WildFire sandbox report and extract the indicators within it.
* The playbook tries to retrieve the report, but if there is no report available, the playbook tries to fetch the ransomware file for detonation.

3.Hunts for the ransomware alert indicators from the alert table, searches for endpoints that have been seen with them, and allows containing the identified endpoints.
Ransomware Exposure - RiskSenseThe ransomware exposure playbook reveals an organization's exposure to the specific vulnerabilities that are being exploited to launch ransomware attacks.
Ransomware Playbook - ManualMaster playbook for ransomware incidents. This playbook is a manual playbook.
Ransomware ResponseThis playbook handles ransomware alerts based on the Cortex XDR Traps module signature 'Suspicious File Modification'

Attacker’s Goals:

An attacker is attempting to encrypt the victim files for either extortion or destruction purposes.

Investigative Actions:

Investigate the executed process image and verify if it is malicious using:

XDR trusted signers

VT trusted signers

VT detection rate

NSRL DB

Response Actions:

The playbook’s first response action is a remediation plan which includes two sub-playbooks, Containment Plan and Eradication Plan, which is based on the initial data provided within the alert. In that phase, the playbooks will execute:

Auto endpoint isolation

Auto block indicators

Auto file quarantine

Auto user disable

Auto process termination

Next, the playbook executes an enrichment and response phase which includes two sub-playbooks, Ransomware Enrich and Contain & Account Enrichment - Generic v2.1.
The Ransomware Enrich and Contain playbook does the following:

1.Checks if the initiator is a remote attacker and allows isolating the remote host, if possible.

2.Retrieves the WildFire sandbox report and extracts the indicators within it. * The playbook tries to retrieve the report, but if there is no report available, the playbook tries to fetch the ransomware file for detonation.

3.Hunts for the ransomware alert indicators from the alert table, searches for endpoints that have been seen with them, and allows containing the identified endpoints.

Next, an advanced analysis playbook, which is currently done mostly manually, will be executed. This sub-playbook, Ransomware Advanced Analysis allows the analyst to upload the ransomware note and for the ransomware identification. Using the ID-Ransomware service, the analyst will be able to get the ransomware type and the decryptor if available.

When the playbook executes, it checks for additional activity using the Endpoint Investigation Plan playbook, and another phase, which includes the Containment Plan sub-playbook, is executed.

This phase will execute the following containment actions:

Manual block indicators

Manual file quarantine

Auto endpoint isolation

Finally, the recovery phase is executed. If the analysts decides to continue with the investigation rather than recover and close the alert, a manual task with CISA official ransomware investigation checklist is provided for further investigation.

External resources:

MITRE Technique T1486

CISA Ransomware Guide
Rapid Breach Response - Set Incident InfoThis playbook is responsible for setting up the Rapid Breach Response Incident Info tab in the layout.
Rapid IOC Hunting PlaybookDeprecated. Use the Hunt File Hash playbook instead. Playbook to quickly react to discovery of new IOCs. Receive a list of IOCs as attached text / csv files, extract IOCs using regular expressions and hunt rapidly across the infrastructure using various integrations. Also supports attaching multiple files.
Rapid ransomware containment - IllumioIsolate one or more workloads based on traffic flows to a given port/protocol.

Rapid7 - Nexpose - EnrichmentGiven an IP address, this playbook searches Rapid7 Nexpose assets for an asset with the associated IP address to retrieve asset information and proceeds to return all associated tags with it.
Rapid7 InsightIDR - Execution Flow Indicators HuntingThis playbook queries Rapid7 InsightIDR SIEM for execution flow indicators, including registry values, registry keys, registry hives, commands, processes name, and applications.

Note that multiple search values should be separated by commas only (without spaces or any special characters).
Rapid7 InsightIDR - File Indicators HuntingThis playbook queries Rapid7 InsightIDR SIEM for file indicators, including MD5 hashes, SHA256 hashes, SHA1 hashes, file names, file types, and file paths.

Note that multiple search values should be separated by commas only (without spaces or any special characters).
Rapid7 InsightIDR - HTTP Requests Indicators HuntingThis playbook queries Rapid7 InsightIDR SIEM for indicators associated with HTTP requests, including HTTP request methods, user agents, URIs, and Ja3.

Note that multiple search values should be separated by commas only (without spaces or any special characters).
Rapid7 InsightIDR - Indicators HuntingThis playbook facilitates threat hunting and detection of IOCs within Rapid7 InsightIDR SIEM logs utilizing four sub-playbooks. The sub-playbooks query Rapid7 InsightIDR SIEM for different indicators including files, traffic, HTTP requests, and execution flows indicators.

Note that multiple search values should be separated by commas only (without spaces or any special characters).

Supported IOCs for this playbook:
- MD5
- SHA1
- SHA256
- IP Address
- URLDomain
- Registry Value
- Registry Key
- Registry Hives
- Command Line
- File Name
- Process Name
- HTTP Request Methods
- User Agent
- Port Number
- File Path
- Geolocation
- Email Address
- CIDR
- URI
- Ja3
- FileType
Rapid7 InsightIDR - Traffic Indicators HuntingThis playbook queries Rapid7 InsightIDR SIEM for traffic indicators, including URLs, domains, ports, IP addresses, IP ranges (CIDR), email addresses, and geolocations.

Note that multiple search values should be separated by commas only (without spaces or any special characters).
RDP Bitmap Cache - Detect and Hunt## Playbook: Automated Collection and Forensic Analysis of RDP Sessions Cache Data

This playbook automates the collection and forensic analysis of RDP sessions cache data. It involves the following steps:

### Step 1: Collect Cache Files and Convert to Image

The first step is to collect the cache files from RDP sessions and convert them into an image format.

### Step 2: Extract Readable Text from the Image

Once the cache files are converted into an image, the playbook extracts readable text from the image to facilitate analysis.

### Step 3: Build Indicators of Compromise (IOCs) from Text

In this step, the extracted text is used to build indicators of compromise (IOCs) for further investigation and threat hunting.

### Step 4: Enrich Extracted Indicators for Further Hunting

Finally, the playbook enriches the extracted indicators by adding additional context and information, enhancing their usefulness for further hunting and analysis.

> Note: It is important to customize and adapt this playbook to fit specific use cases and environments. Additionally, ensure compliance with legal and privacy requirements when collecting and analyzing data.

Feel free to modify and enhance this playbook according to your requirements.
Reco - Reduce Risk - Google Publicly Exposed FilesThe "Reco - Reduce Risk - Google Publicly Exposed Files" playbook aims to identify and mitigate the risk associated with publicly exposed sensitive files on Google Drive. It follows a sequence of tasks to detect such files, analyze their locations, and remove the "anyone with link" permission to enhance data security.
Reco Build String MessageBuild a string message from list of files (file name, link)
Reco Google Drive AutomationAutomate Google Drive alert remediation with our solution that revokes over-access permissions and shares file details and links with end-users via Slack. Reco workflow seamlessly integrates with Palo Alto Networks' Demisto platform to resolve the alert and streamline your organization's security operations. By automating remediation, you can ensure that sensitive data is protected and that end-users are promptly notified of any changes to their file access. With our solution, you can close alerts in Demisto and improve your organization's security posture with minimal effort.
Reco-Google-Drive-Revoke-PermissionsThis workflow enables you to easily list the permissions of files stored in Google Drive, giving you visibility into who has access to your organization's data. If a file's permission is publicly exposed, the workflow restricts access to the file to prevent unauthorized use. Similarly, if a file's permission is set to accessible by all org users and shared with internal users, access to the file is restricted to authorized users only. Using the Google Drive API and built-in conditional logic, this workflow helps you secure sensitive data and streamline your organization's data management.
Recorded Future - Threat Actor SearchTemplate playbook to initiate an Automated Threat Hunt based on the Threat Map in Recorded Future. The Playbook fetches links related to the Threat Actors part of the Threat Map from Recorded Future and launches a hunt in the SIEM for any detections within the environment.
Recorded Future CVE IntelligenceCVE enrichment using Recorded Future intelligence
Recorded Future CVE ReputationCVE reputation with Recorded Future SOAR enrichment
Recorded Future Detailed Alert example
Recorded Future Domain AbuseThis playbook was developed as a template to handle the ingestion of Recorded Future Domain Abuse playbook alerts.
Recorded Future Domain IntelligenceDomain enrichment using Recorded Future intelligence
Recorded Future Domain ReputationDomain reputation using Recorded Future SOAR enrichment
Recorded Future Entity EnrichmentTemplate playbook to incorporate Recorded Future enrichment for IPs, Hashes, Domains, URLs into your current workflows. Playbook also shows how to look up available 'Links' data for IOCs.
Recorded Future External UsecaseImplements an external usecase for Recorded Future Identity Data
Recorded Future File IntelligenceFile enrichment using Recorded Future intelligence
Recorded Future File ReputationFile reputation using Recorded Future SOAR enrichment
Recorded Future Identity - Create Incident (sub)This playbook was developed as a sub-playbook to generate incidents for each exposed identity found in the Recorded Future Identity - Lookup Identities (parent) playbook.
Recorded Future Identity - Identity Found (incident)This playbook was developed as a template response when an Identity has been found and a Recorded Future Identity Incident has been created.
Recorded Future Identity - Lookup Identities (parent)This playbook was developed as a template to look up exposed identities and generate incidents if they exist; it can be used within a job.
Recorded Future IOC ReputationEntity Reputation using sub-playbooks
Recorded Future IP IntelligenceIP Address Enrichment using Recorded Future Intelligence
Recorded Future IP ReputationIP address reputation using Recorded Future SOAR enrichment
Recorded Future Leaked Credential Alert HandlingTemplate playbook showing suggested steps to triage leaked credential alerts. Classifier/Mapper are available to ingest Recorded Future Leaked Credential Alerts.
Recorded Future List ManagementManage, view, and edit your lists in Recorded Future.
Recorded Future Playbook Alert DetailsA default playbook to fetch details of Playbook alert that does not yet have mapping made by Recorded Future
Recorded Future SandboxTemplate playbook utilizing Hatching.io to sandbox a given file and generate an analysis report. Indicators from the given report are then extracted and enriched with Recorded Future data.
Recorded Future Threat AssessmentThreat Assessment using the Recorded Future SOAR Triage API and the context Phishing.
Recorded Future Typosquat Alert HandlingTemplate playbook showing suggested steps to triage typo squat alerts. Classifier/Mapper are available to ingest Recorded Future Typo squat Alerts.
Recorded Future URL IntelligenceURL Enrichment using Recorded Future intelligence
Recorded Future URL ReputationURL reputation using Recorded Future SOAR enrichment
Recorded Future VulnerabilityThis playbook was developed as a template to handle the ingestion of Recorded Future Cyber Vulnerability playbook alerts.
Recorded Future Vulnerability Alert HandlingTemplate playbook showing suggested steps to triage new critical vulnerability alerts. Playbook include New and Critical CVEs. Classifier/Mapper are available to ingest Recorded Future New, Critical or Pre NVD Vulnerability Alerts.
Recorded Future Workforce UsecaseImplements an workforce usecase for Recorded Future Identity Data
Recovery PlanThis playbook handles all the recovery actions available with Cortex XSIAM, including the following tasks:
Unisolate endpoint
Restore quarantined file

Note: The playbook inputs enable manipulating the execution flow; read the input descriptions for details.
Registry Parse Data AnalysisThis playbook leverages the RegistryParse automation to perform registry analysis and extract forensic artifacts. The automation includes common registry objects to extract which are useful for analyzing registry, or a user provides registry path to parse.
Remediate Message - Agari Phishing DefenseRemediates a given message id.
Remote PsExec with LOLBIN command execution alertThe "Remote PsExec-like LOLBIN Command Execution" playbook is designed to address and respond to alerts indicating suspicious activities related to remote PsExec-like LOLBIN command execution from an unsigned non-standard source.
The playbook aims to efficiently:

- Check if the execution is blocked. If not will terminate the process (Manually by default).
- Enrich any entities and indicators from the alert and find any related campaigns.
- Perform command analysis to provide insights and verdict for the executed command.
- Perform further endpoint investigation using XDR.
- Checks for any malicious verdict found to raise the severity of the alert.
- Perform Automatic/Manual remediation response by blocking any malicious indicators found.

The playbook is designed to run as a sub-playbook in ‘Cortex XDR Incident Handling - v3 & Cortex XDR Alerts Handling’.
It depends on the data from the parent playbooks and can not be used as a standalone version.
Remove Employees from Departing Employee WatchlistLoops through Departing Employee watchlist entries from Code42 Incydr and removes employees based on specified criteria.
Remove Employees from New Hire WatchlistLoops through New Hire watchlist entries from Code42 Incydr and removes employees based on specified criteria.
Report Categorization - Cofense Triage v3Report Categorization playbook investigates reports that are unprocessed or uncategorized on Cofense Triage as incident alerts in XSOAR and categorizes them based on the severity of the incident.
Reset User Password via ChatbotThis playbook resets the password of an Active Directory or Okta user. The process is as follows:
1. A user requests a password reset using a chatbot in Slack or in Microsoft Teams.
2. The playbook optionally seeks approval to reset the user's password from the relevant stakeholder, or from the user's manager. The request will be available for approval/disapproval for 1 hour. If not processed within that time, it will be disapproved.
3. If the reset was approved, the playbook optionally verifies the user using 2-factor authentication, from the user's available 2FA methods on Okta.
4. If the reset is verified, a new password will be created while meeting the complexity requirements of the organization.
5. The user's password will be reset and set to the newly generated password. The user will be forced to change their password on next login.
6. The new user's password will be placed inside a password-protected ZIP (protected by a different password).
7. The encrypted ZIP file that contains the new password for the user will be sent to the user via email.
8. The password for the ZIP file that contains the new user's password, will be sent to the requesting user through Slack or Teams.

This playbook is intended for use with Slack or Teams. In order to use it, please make sure that you have a classifier and mapper in place. The classifier should create a Password Reset via Chatbot incident, while the mapper should map the email of the user to the Reporter Email Address field.
This playbook assumes that the user requesting the password reset has the same email in Slack / Teams, and in Active Directory / Okta.
Residents Notification - Breach NotificationThis playbook is triggered by a breach notification playbook and is responsible for the resident notification process.
Retrieve Alert Attachments - Rapid7 ThreatCommandThis playbook is used by default for the Rapid7 ThreatCommand alerts being ingested as XSOAR incidents. This playbook retrieves attachments (CSV file and images) using the Alert ID incident field.
Retrieve Alerts For IOCs - Dataminr PulseThis playbook is used to fetch alerts from Dataminr Pulse, which will be based on the given input text. First, it will extract indicators from the input text, then it will use extracted indicators to retrieve alerts from Dataminr Pulse. After that, it will store related alerts in the context.
Retrieve Asset Details - LansweeperGet contextual information of asset based on IP/MAC from Lansweeper.
Retrieve Email Data - Agari Phishing DefenseRetrieve Email Data from one of the Integrations of Gmail, Mail Listener v2, EWS O365, Microsoft Graph Mail.
Retrieve File from Endpoint - GenericDeprecated. Use `Retrieve File from Endpoint - Generic V3` instead.
This playbook retrieves a file sample from an endpoint using the following playbooks:
- Get File Sample From Path - Generic
- Get File Sample By Hash - Generic v2
Retrieve File from Endpoint - Generic V2Deprecated. Use `Retrieve File from Endpoint - Generic V3` instead.
'This playbook retrieves a file sample from an endpoint using the following playbooks:'
- Get File Sample From Path - Generic v2.
- Get File Sample By Hash - Generic v3.
Retrieve File from Endpoint - Generic V3'This playbook retrieves a file sample from an endpoint using the following playbooks:'
- Get File Sample From Path - Generic v2.
- Get File Sample By Hash - Generic v3.
Retrieve Related Alerts - Dataminr PulseThis playbook is used to run the Default playbook from XSOAR and to fetch related alerts for Dataminr Pulse. The information required to fetch related alerts will be used from the incident s alert ID for which the playbook is going to run. After that, it will store them in the context.
RiskIQAsset Basic Information Enrichment - RiskIQ Digital FootprintThis playbook receives indicators from its parent playbook and enriches the basic information and the detected CVEs for the "RiskIQAsset" type of indicators. This playbook needs to be used with caution as it might use up the integrations' API license when running for large amounts of indicators.
Supported Integrations:
- RiskIQ Digital Footprint
- VulnDB
- CVE Search
- IBM X-Force
RiskIQAsset Enrichment - RiskIQ Digital FootprintEnriches the "RiskIQAsset" type of indicators with basic information and CVEs detected for the asset, performs a vulnerability scan for "Host" and "IP Address" type of assets, and enriches received information in the context as well as provides the user to add to allow list a list of "IP Address" type of assets. This playbook also enriches the detected CVEs. To select the indicators you want to enrich, go to playbook inputs, choose "from indicators" and set your query. For example type:RiskIQAsset etc. The default playbook query is "type:RiskIQAsset". In case indicators with specific "riskiqassettype" are to be enriched, the query must be edited accordingly. This playbook needs to be used with caution as it might use up the integrations' API license when running for large amounts of indicators.
Supported integrations:
- RiskIQ Digital Footprint
- Tenable.io
- Google Cloud Compute
- AWS - EC2
- Okta v2
RSS Create Indicators From ReportThe playbook:
1. Extracts indicators from Threat intel reports.
2. Creates relationships between the extracted indicators and the report.
3. Runs enrich indicators command on the extracted indicators.

Cortex XSOAR recommends that you configure a job to execute this playbook.

1. Configure a job that will run the RSS Create Indicators From Report playbook.
1. Select the Triggered by delta in feed option.
2. Select the feed on which to run the job.


2. Configure input to the RSS Create Indicators From Report playbook:

- From the context data input: Tag name - the indicator will be tagged with this value when the playbook finishes processing and all the indicators are extracted and relationships created.

- From the indicators: Create a query to include only new report indicators that were not processed yet. Recommended query: "type:Report -tags:{Tag name configured from the context data input} -tags:in_process".
The playbook tags all indicators with the "in_process" tag when it starts running, and removes the tag when the playbook ends.
If you want the playbook to run on a specific instance (a specific feed), add the following filter to the query: sourceInstances:"{the selected instance}".

Note that if you selected the Triggered by delta in feed option when configuring the Job, the “Run only on new and modified indicators” playbook option is automatically selected.
Rubrik Anomaly Incident Response - Rubrik PolarisThis playbook will investigate an anomaly incident ingested by the integration "RubrikPolaris", enrich its data, and perform a remediation according to the incident's object type.
Rubrik Data Object Discovery - Rubrik PolarisData discovery of the object available in the incident.
Rubrik File Context Analysis - Rubrik PolarisThis playbook fetches file context information for the provided file, folder, or file share name and the object ID to get the policy hits.
Rubrik Fileset Ransomware Discovery - Rubrik PolarisThis playbook performs IOC Scan on fileset object. It also creates tickets on ServiceNow using "ServiceNow v2" integration.
Supported integrations:
- RubrikPolaris
- ServiceNow v2
Rubrik IOC Scan - Rubrik PolarisThis playbook starts an IOC Scan with the provided IOC values. It can be looped until recoverable snapshots are obtained or the limit to loop is reached.
Rubrik List Snapshots - Rubrik PolarisList snapshots for all objects.
Rubrik Object Context Analysis - Rubrik PolarisThis playbook will investigate based on the object type from the Rubrik Anomaly incident to retrieve the policy hits of the files related to the object.
Rubrik Polaris - Anomaly AnalysisMonitor the progress of a Rubrik Radar anomaly event and use Rubrik Sonar to check for data classification hits.
Rubrik Poll Async Result - Rubrik PolarisPoll async result for any asynchronous request made to rubrik.
Rubrik Ransomware Discovery and File Recovery - Rubrik PolarisThis playbook performs an IOC Scan based on the provided inputs, search the recoverable snapshot and performs recovery on the searched recoverable snapshot. This playbook also creates tickets on ServiceNow using "ServiceNow v2" integration.
Supported integrations:
- RubrikPolaris
- ServiceNow v2
Rubrik Ransomware Discovery and VM Recovery - Rubrik PolarisUse this playbook to recover a virtual machine using the "RubrikPolaris" integration by either exporting or live-mounting a backup snapshot. This playbook also creates tickets on ServiceNow using "ServiceNow v2" integration.
Supported integrations:
- RubrikPolaris
- ServiceNow v2
Rubrik Retrieve Anomaly Result - Rubrik Security CloudThis playbook retrieves the list of anomaly files for the provided snapshot ID (or activity series ID) and generates the downloadable links for the file path(s).
Rubrik Retrieve User Access Information - Rubrik PolarisThis playbook retrieves User Intelligence information for the provided username or email, which includes the user's risk level and the types of analyzer hits.
Rubrik User Access Analysis - Rubrik PolarisThis playbook fetches User Intelligence information for the provided username or email, and then increases the incident severity based on the user risk levels.
Run Panorama Best Practice Assessment (Deprecated)Deprecated. Use Palo Alto Networks AIops instead, run aiops-bpa-report-generate command.
Rundeck-job-execute-GenericThis playbook executes a job and exits when it successfully finishes.
Saas Security - Incident ProcessorThis playbook notifies incidents owner and provides remediation options to Saas Security admin for resolving incidents.
SaaS Security - Remediate an AssetTake a remediation action over an asset:
Use this playbook as a sub-playbook to take a remediation action on an asset. Available remediation actions are 1) Remove public sharing, 2) Quarantine, and 3) Restore.
This playbook implements polling by continuously running the `saas-security-remediation-status-get`
command to get the remediation status for a given asset ID, until the operation completes.

The remote action should have the following structure:
1. Initiate the operation - provide the Asset ID and the remediation action.
2. Poll to check if the operation completed.
3. Get the results of the operation.
Saas Security - Take Action on the IncidentThis sub-playbook will send email notification to the Saas Security Admin for taking remediation action on the incident.
SafeBreach - Compare and Validate Insight IndicatorsDeprecated. No available replacement.
SafeBreach - Create Incidents per Insight and Associate IndicatorsDeprecated. No available replacement.
SafeBreach - Process Non-Behavioral Insights FeedDeprecated. No available replacement.
SafeBreach - Rerun InsightsDeprecated. No available replacement.
SafeBreach - Rerun Single InsightDeprecated. No available replacement.
SafeNet Trusted Access - Add to Unusual Activity GroupThis playbook adds the user to a group that was created to identify unusual activity. SafeNet Trusted Access policies can be configured to take this into account and provide stronger protection when handling access events from users who are members of the group. The user is added to this group for a configurable period of time.
SafeNet Trusted Access - Terminate User SSO SessionsThis playbook terminates user SSO sessions so that upon the next login attempt following the unlocking of the account, authentication is required.
SailPoint IdentityIQ Disable User Account AccessChecks if the risk score of an identity exceeds a set threshold of 500 and disables the accounts.
Sanitize File - CDR - ThreatZoneSanitize one file using the ThreatZone CDR integration.
Returns relevant reports to the War Room and file reputations to the context data.
CDR Scan Extensions: doc, docm, docx, dotm, ppt, pptm, pptx, xls, xlsm, pdf, odc, odt, ott, odp, otp, ods, ots, rtf, tiff, jpeg, png, gif, bmp, webp, jpx, svg, zip, xml, ics, html, lnk, xlsx.
SANS - Incident Handler's Handbook TemplateThis playbook contains the phases for handling an incident as they are described in the SANS Institute ‘Incident Handler's Handbook’ by Patrick Kral.

https://www.sans.org/reading-room/whitepapers/incident/incident-handlers-handbook-33901

***Disclaimer: This playbook does not ensure compliance to SANS regulations.
SANS - Incident Handlers ChecklistThis playbook follows the "Incident Handler's Checklist" described in the SANS Institute ‘Incident Handler’s Handbook’ by Patrick Kral.

https://www.sans.org/reading-room/whitepapers/incident/incident-handlers-handbook-33901

***Disclaimer: This playbook does not ensure compliance to SANS regulations.
SANS - Lessons LearnedThis playbook assists in post-processing an incident and facilitates the lessons learned stage, as presented by SANS Institute ‘Incident Handler’s Handbook’ by Patrick Kral.

https://www.sans.org/reading-room/whitepapers/incident/incident-handlers-handbook-33901

***Disclaimer: This playbook does not ensure compliance to SANS regulations.
Scan and Isolate - XM CyberAn example of playbook using data from XM Cyber to help decide about scanning and isolating a threat
Scan Assets - NexposeDeprecated. Use the "Scan Site - Nexpose" playbook instead.
Scan Site - NexposeStarts a Nexpose scan by site id and waits for the scan to finish by polling its status in pre-defined intervals.
Schedule Task and PollThis playbook will schedule a specified command and monitor for completion by looking for output in context. Make the playbook context shared globally if you have a command that returns to Context automatically and you have a specific key to monitor. The key monitored must be a single field value and not an array.
Search all mailboxes - Gmail with pollingThis playbook searches Gmail records for all Google users, designed for large companies with over 2500 Google users.
Search And Block Software - GenericThis playbook will search a file or process activity of a software by a given image file name. The analyst can then choose the files to block.
The following integrations are supported:

- Cortex XDR XQL Engine
- Microsoft Defender For Endpoint
Search and Compare Process Executions - GenericThis playbook is a generic playbook that receives a process name and a command-line argument. It searches for the given process executions and compares the command-line argument from the results to the command-line argument received from the playbook input. The playbook supports searching process executions using the following integrations:

- Cortex XDR XQL Engine
- Cortex XDR IR(Search executions inside XDR alerts)
- Microsoft Defender For Endpoint

Note: Under the "Processes" input, the playbook should receive an array that contains the following keys:
- value: process name
- commands: command-line arguments
Search And Delete Emails - EWSThis playbook searches EWS to identify and delete emails with similar attributes of a malicious email.
Search And Delete Emails - GenericDeprecated. Use `Search And Delete Emails - Generic v2` instead. This playbook searches and delete emails with similar attributes of a malicious email.
Search And Delete Emails - Generic v2This playbook searches and deletes emails with similar attributes of a malicious email using one of the following integrations: EWS Office 365 Gmail Agari Phishing Defense.
Search And Delete Emails - GmailThis playbook searches Gmail to identify and delete emails with similar attributes to the malicious email.
Search Endpoint by CVE - GenericHunt for assets with a given CVE using available tools
Search Endpoints By Hash - Carbon Black ProtectionHunt for endpoint activity involving hash IOCs, using Carbon Black Protection.
Search Endpoints By Hash - Carbon Black ResponseDeprecated. Use the Search Search Endpoints By Hash - Carbon Black Response V2 playbook instead. Hunt for malicious indicators using Carbon Black.
Search Endpoints By Hash - Carbon Black Response V2Hunt for malicious indicators using Carbon Black
Search Endpoints By Hash - CrowdStrikeDeprecated. Use CrowdStrike Falcon instead.
Search Endpoints By Hash - CybereasonHunt for endpoint activity involving hash, using Cybereason.
Search Endpoints By Hash - GenericDeprecated. Use the Search Endpoints By Hash - Generic V2 playbook instead. Hunt using available tools
Search Endpoints By Hash - Generic V2Hunt using available tools
Search Endpoints By Hash - TIEHunt for sightings of MD5, SHA1 and/or SHA256 hashes on endpoints, using McAfee TIE (requires ePO as well).

Input:
Hash (default, takes all deferent hashes from context)

Output:
All agents that files with "Hash" has been executed on (TIE)
* Enrich Agents info from ePO
Search For Hash In Sandbox - GenericThis playbook searches for a specific hash in the supported sandboxes. If the hash is known, the playbook provides a detailed analysis of the sandbox report. Currently, supported sandboxes are Falcon Intelligence Sandbox, Wildfire and Joe Sandbox.
Search in mailboxes Gmail (Loop) with pollingThis playbook should only run as a sub-playbook for the Search-all-mailboxes - Gmail playbook, it should not run alone.
Search LOLBAS Tools By NameThis playbook searches for LOLBAS tools by their name, and returns the tool command from LOLBAS.
Send Indicators - Cofense Triage v3Send Indicators playbook is used to create or update threat indicators in Cofense Triage that have been identified as malicious or suspicious by the analysis.
Send Investigation Summary ReportsThis playbook iterates over closed incidents, generates a summary report for each closed incident, and emails the reports to specified users.
Send Investigation Summary Reports JobYou should run this playbook as a scheduled job, whicn should run at an interval of once every 15 minutes. This playbook functions by calling the sub-playbook: "Send Investigation Summary Reports", and closes the incident. By default, the playbook will search all incidents closed within the last hour. If you want to run the playbook more frequently, you should adjust the search query of the child playbook: "Send Investigation Summary". Reports.
Sentinel One - Endpoint data collectionDeprecated. No available replacement.
Sentinel One - Query EndpointsRuns Query on Endpoints for SHA1 values
ServiceNow - Ticket Management`ServiceNow - Ticket Management` allows you to open a new ticket or comment on an existing ticket.
ServiceNow Change ManagementIf you are using a PAN-OS/Panorama firewall and ServiceNow as a ticketing system this playbook is a perfect match for your change management for firewall process.
This playbook is triggered by a fetch from ServiceNow and will help you manage and automate your change management process.
ServiceNow CMDB SearchSubplaybook for finding CI records in ServiceNow CMDB.
ServiceNow Ticket State PollingUse ServiceNow Incident State Polling as a sub-playbook when required to pause the execution of a master playbook until the ServiceNow ticket state is either resolved or closed.
This playbook implements polling by continuously running the servicenow-get-ticket command until the state is either resolved or closed.
Set RaDark Grid For Compromised AccountsSet grid for RaDark - Compromised Accounts incidents.
Set RaDark Grid For Credit CardsSet grid for RaDark - Credit Cards incidents.
Set RaDark Grid For Hacking DiscussionsSet grid for RaDark - Hacking Discussions incidents.
Set RaDark Grid For Leaked CredentialsSet grid for RaDark - Leaked Credentials incidents.
Set RaDark Grid For Network VulnerabilitiesSet grid for RaDark - Network Vulnerabilities incidents.
Set RDP Bitmap Cache Overall ScoreThis playbook sets the RDP bitmap cache overall score
Set Team MembersThis playbook will accept a CSV of usernames and / or a CSV of role names (of which to enumerate for usernames) to add to the incidents team members.

The playbook will determine the existing owner and ensure that they are replaced as the owner once complete.
Set up a Shift handover meetingThis playbook is used to create an online meeting for shift handover. Currently, this playbook supports Zoom.
Shift handoverThis playbook is used to set up shift handover meetings with all the accompanying processes such as creating an online meeting, creating a notification in a integrated chat app (for example Slack), creating a SOC manager briefing, and creating a display of the active incidents, team members who are on-call, and team members who are out of the office.
By modifying the playbook inputs you can decide whether to activate the Assign Active Incidents to Next Shift and whether a user who is out of the office will be taken into consideration.
SIEM - Search for Failed loginsThis playbook searches for failed logon on a specific user by querying logs from different sources.

Supported Integrations:
-Splunk
-QRadar
-Azure Log Analytics.
Slack - General Failed Logins v2.1Investigates a failed login event. The playbook interacts with the user via the Slack integration, checks whether the logins were a result of the user's attempts or an attack, raises the severity, and expires the user's password according to the user's replies.
SlackBlockBuilderResponseExampleThis is an example of how to use the SlackBlockBuilder within a playbook.
Social Engineering Domain EnrichmentEnrich a domain and compare against your registered domain for potential social engineering against your organization.
Social Engineering Domain InvestigationEnrich and Investigate domains which may present a social engineering threat to your organization. Review before blocking potentially dangerous indicators.
SOCRadar IncidentPerforms indicator extraction and enrichment from the incident content, calculates the severity level, assigns the incident to a particular analyst, notifies SOCRadar platform for the incident response (to mark it as false positive or resolved) and generates investigation summary report just before closing the investigation in the end. This playbook is executed for the SOCRadar Generic incident type.
SolarStorm and SUNBURST Hunting and Response PlaybookThis playbook does the following:
- Collect indicators to aid in your threat hunting process.
- Retrieve IOCs of SUNBURST (a trojanized version of the SolarWinds Orion plugin).
- Retrieve C2 domains and URLs associated with Sunburst.
- Discover IOCs of associated activity related to the infection.
- Generate an indicator list to block indicators with SUNBURST tags.
- Hunt for the SUNBURST backdoor
- Query firewall logs to detect network activity.
- Search endpoint logs for Sunburst hashes to detect presence on hosts.
If compromised hosts are found:
- Notify security team to review and trigger remediation response actions.
- Run sub-playbooks to isolate/quarantine infected hosts/endpoints and await further actions from the security team.

Sources:
https://www.fireeye.com/blog/threat-research/2020/12/evasive-attacker-leverages-solarwinds-supply-chain-compromises-with-sunburst-backdoor.html
https://unit42.paloaltonetworks.com/fireeye-solarstorm-sunburst/3/
https://www.splunk.com/en_us/blog/security/sunburst-backdoor-detections-in-splunk.html
Spear Phishing InvestigationThe "Spear Phishing Investigation" playbook is designed to detect patterns that indicates a spear phishing attempt by the attacker.
Splunk GenericThis is a generic playbook to be executed for the Splunk Notable Generic incident type. The playbook performs all the common parts of the investigation, including notifying the SOC, enriching the data for indicators and users, calculating the severity, assigning the incident, notifying the SIEM admin for false positives and more.
Splunk Indicator HuntingThis playbook queries Splunk for indicators such as file hashes, IP addresses, domains, or urls. It outputs detected users, ip addresses, and hostnames related to the indicators.
Spring Core and Cloud Function SpEL RCEsOn March 29, 2022, information about a 0-day vulnerability in the popular Java library Spring Core appeared on Twitter.

Spring Framework is an extremely popular framework used by Java developers to build modern applications. If you rely on the Java stack, it is very likely that your development teams use Spring. In some cases, a single specially crafted request is enough to exploit the vulnerability.

Later, it was discovered that these are two separate vulnerabilities, one in Spring Core and the other in Spring Cloud Function:

CVE-2022-22965 - RCE in "Spring Core" is a severe vulnerability, aka Spring4Shell

CVE-2022-22963 - RCE in "Spring Cloud Function SpEL"

CVE-2022-22947 - RCE in "Spring Cloud Gateway"

Spring Core vulnerability requirements:

JDK 9 or higher
Apache Tomcat as the Servlet container
Packaged as WAR
spring-webmvc or spring-webflux dependency
Spring Framework versions 5.3.0 to 5.3.17, 5.2.0 to 5.2.19, and older versions

Spring Cloud Function unaffected versions:

3.1.7
3.2.3

This playbook will provide you with a first response kit which includes:

Hunting
Panorama
Prisma Cloud Compute
XDR XQL queries - set the playbook input RunXQLHuntingQueries to 'True' if you would like the XQL to be executed via the playbook.
XDR Alerts - Search for new incidents including one or more of Spring RCEs dedicated Cortex XDR signatures
Remediation
Mitigations

Note: You can execute this playbook using the Incidents view by creating a new incident or by using a dedicated job to schedule the playbook execution.

Additional resources:

Spring Framework RCE

CVE-2022-22965: Spring Core Remote Code Execution Vulnerability Exploited In the Wild

SpyCloud - Breach InvestigationSpyCloud Breach playbook gets executed on the occurrence of the incident SpyCloud Breach Data type.
SpyCloud - Malware Incident EnrichmentSpyCloud Malware Playbook executes the spycloud-compass-device-data command when any incident of the SpyCloud Malware Data type is created, and sets the corresponding incident field.
SSL_Certificate_VerificationDemo playbook - takes list of addresses from an XSOAR list, process the status of each SSL certificate, and generate war room and email summary outputs.
Stamus Networks - Get Extra DataGet Extra Information from a Declaration of Compromise
Strata Logging Service - File Indicators HuntingThis playbook queries Strata Logging Service (SLS) for file indicators, including SHA256 hashes, file names, and file types.

Note that multiple search values should be separated by commas only (without spaces or any special characters).
Strata Logging Service - Indicators HuntingThe playbook facilitates threat hunting and detection of IOCs within Strata Logging Service logs. The playbook and sub-playbooks query Strata Logging Service for files, traffic, HTTP requests, and execution flows indicators.

Note that multiple search values should be separated by commas only (without spaces or any special characters).

Supported IOCs for this playbook:
- SHA256
- IP Addresses
- Geolocation
- URLDomain
- Port Number
- File Name
- File Type
- URI
- Application

Separate searches are conducted for each type of indicator in the playbook.
Strata Logging Service - Traffic Indicators HuntingThis playbook queries Strata Logging Service (SLS) for traffic indicators, including IP addresses, geolocations, URLs, domains, and ports.

Note that multiple search values should be separated by commas only (without spaces or any special characters).
Sumo Logic Cloud SIEM - Link Signal IncidentsPlaybook to link Sumo Logic Signal Incidents to the corresponding Insight Incident
Suspicious Domain Hunting Incident HandlingThis playbook process "Suspicious Domain Hunting" incidents generated by the CertStream integration.
SX - PC - PingCastle ReportThis playbook runs when a new report is sent from PingCastle. It then parses it to json and renders a table. It also puts a download link to the xml report in the war room.
Symantec block EmailThis playbook will block email address at your email gateway.
T1036 - MasqueradingThis playbook handles masquerading alerts based on the MITRE T1036 technique.
An attacker might leverage Microsoft Windows well-known image names to run malicious processes without being caught.

Attacker's Goals:

An attacker is attempting to masquerade as standard windows images by using a trusted name to execute malicious code.

Investigative Actions:

Investigate the executed process image and verify if it is malicious using:

XDR trusted signers
VT trusted signers
VT detection rate
NSRL DB

Response Actions

The playbook's first response action is a containment plan which is based on the initial data provided within the alert. In that phase, the playbook will execute:

Auto block indicators
Auto file quarantine
Manual endpoint isolation

When the playbook executes, it checks for additional activity using the Endpoint Investigation Plan playbook, and another phase, which includes containment and eradication, is executed.

This phase will execute the following containment actions:

Manual block indicators
Manual file quarantine
Auto endpoint isolation

And the following eradication actions:

Manual process termination
Manual file deletion
* Manual reset of the user’s password

External resources:

MITRE Technique T1036

Possible Microsoft process masquerading
T1059 - Command and Scripting InterpreterThis playbook handles command and scripting interpreter alerts based on the MITRE T1059 technique.
An attacker might abuse command and script interpreters to execute commands, scripts, or binaries.
Most systems come with some kind of built-in command line interface and scripting capabilities. For example, macOS and Linux distributions include some form of Unix Shell while Windows installations include the Windows Command Shell and PowerShell.


Attacker's Goals:

An attacker can abuse these technologies in various ways as a means of executing arbitrary commands. Commands and scripts can be embedded in initial access payloads delivered to victims as lure documents or as secondary payloads downloaded from an existing C2. An attacker may also execute commands through interactive terminals/shells, as well as utilize various remote services to achieve remote execution.

Analysis

Due to the nature of this technique and the usage of built-in command line interfaces, the first step of the playbook is to analyze the command line.
The command line analysis does the following:
- Checks and decodes base64
- Extracts and enriches indicators from the command line
- Checks specific arguments for malicious usage

Investigative Actions:
The playbook checks for additional activity using the 'Endpoint Investigation Plan' playbook and utilizes the power of insight alerts.

Response Actions

After analyzing the data, the playbook's first response action is to contain the threat based on the initial data provided within the alert. In this phase, the playbook will:

Isolate the endpoint based on playbook inputs.

When the playbook proceeds, it checks for additional activity using the 'Endpoint Investigation Plan' playbook. It then continues with the next stage, which includes, containment and eradication.

This phase executes the following containment actions:

Automatically isolates the endpoint

It then continues with the following eradication actions:

* process termination
Tag massive and internal IOCs to avoid EDL listingThis playbook tags internal assets and massive IOCs (TLD wildcards and CIDRs) to be avoided by the EDL. The playbook does the following according to indicator type:

CIDRs - If the CIDR prefix is larger than the set max prefix it tags it as a `Massive_CIDR` and also with `skip_edl`.

TLD Wildcards - If a domainglob is a TLD wildcard (for example, *.net) it will be tagged as `TLD_Wildcard` and also with `skip_edl`.

Internal IPs - If an IP is internal and also part of the CIDR configured by the user in the "Internal Assets" list it will be checked as `internal` and tagged with `skip_edl`.

Internal Domains - If a domain is a subdomain of the domains configured in the "Internal Assets" list it is checked as `internal` and tagged with `skip_edl`.
Tanium - Ask QuestionThis playbook used generic polling to gets question result.
Tanium - Get Saved Question ResultThis playbook used generic polling to gets saved question result.
Tanium Demo PlaybookDeprecated. No available replacement. This playbook shows how to use automation scripts to interact with Tanium.
Tenable.io ScanRun a Tenable.io scan
Threat Hunting - ChronicleUse this playbook to investigate and remediate suspicious IOC domain matches with recent activity found in the enterprise. This playbook also creates indicators for the entities fetched, as well as investigating and enriching them.
Supported Integrations:
- Chronicle
- Whois
Threat Hunting - GenericThis playbook enables threat hunting for IOCs in your enterprise. It currently supports the following integrations:
- Splunk
- Qradar
- Pan-os
- Cortex Data Lake
- Autofocus
- Microsoft 365 Defender
Ticket Management - Generic`Ticket Management - Generic` allows you to open new tickets or update comments to the existing ticket in the following ticketing systems:
-ServiceNow
-Zendesk
using the following sub-playbooks:
-`ServiceNow - Ticket Management`
-`Zendesk - Ticket Management`
TIE - IOC HuntHunt for sightings of MD5, SHA1 and/or SHA256 hashes on endpoints, using McAfee TIE (requires ePO as well).

Input:
Hash (default, takes all deferent hashes from context)

Output:
All agents that files with "Hash" has been executed on (TIE)
* Enrich Agents info from ePO
TIM - Add All Indicator Types To SIEMThis playbook runs sub playbooks that send indicators to your SIEM. To select the indicators you want to add, go to playbook inputs, choose “from indicators” and set your query. For example tags:approved_black, approved_white etc. The purpose of the playbook is to send to SIEM only indicators that have been processed and tagged accordingly after an automatic or manual review process. The default playbook query is"
(type:ip or type:file or type:Domain or type:URL) -tags:pending_review and (tags:approved_black or tags:approved_white or tags:approved_watchlist)"
In case more indicator types need to be sent to the SIEM, the query must be edited accordingly.
TIM - Add Bad Hash Indicators To SIEMThis playbook recives indicators from its parent playbook
and provides the indicators as inputs for the sub-playbooks that push the indicators
to the SIEM.
TIM - Add Domain Indicators To SIEMThis playbook receives indicators from its parent playbook and provides the indicators as inputs for the sub-playbooks that push the indicators to the SIEM.
TIM - Add IP Indicators To SIEMTIM playbook - This playbook receives indicators from its parent playbook
and provides the indicators as inputs for the sub-playbooks that push the indicators
to your SIEM.
TIM - Add Url Indicators To SIEMTIM playbook - This playbook receives indicators from its parent playbook
and provides the indicators as inputs for the sub-playbooks that push the indicators
to your SIEM.
TIM - ArcSight Add Bad Hash IndicatorsThis playbook queries indicators based on a pre-defined query or results from a parent playbook, and adds the resulting indicators to an ArcSight Active List. The Active List ID should be defined in the playbook inputs, as well as the field name in the Active list to which to add the indicators.
TIM - ArcSight Add Domain IndicatorsThis playbook queries indicators based on a pre-defined query or results from a parent playbook, and adds the resulting indicators to an ArcSight Active List. The Active List ID should also be defined in the playbook inputs, as well as the field name in the Active list to add to.
TIM - ArcSight Add IP IndicatorsThis playbook receives indicators from its parent playbook and provides the indicators as inputs for the sub-playbooks that push the indicators to SIEM.
TIM - ArcSight Add Url IndicatorsThis playbook queries indicators based on a pre-defined
query or results from a parent playbook and adds the resulting indicators to an ArcSight
Active List. The Active List ID should also be defined in the playbook inputs as well as the field name in the Active list to add to.
TIM - Indicator Auto ProcessingThis playbook uses several sub playbooks to process and tag indicators, which is used to identify indicators that shouldn't be added to block list. For example IP indicators that belong to business partners or important hashes we wish to not process. Additional sub playbooks can be added for improving the business logic and tagging according to the user's needs. This playbook doesn't have its own indicator query as it processes indicators provided by the parent playbook query. To enable the playbook, provide the relevant list names in the sub playbook indicators, such as the ApprovedHashList, OrganizationsExternalIPListName, BusinessPartnersIPListName, etc. Also be sure to append the results of additional sub playbooks to Set indicators to Process Indicators for the additional playbooks results to be in the outputs.
TIM - Indicator Relationships AnalysisThis playbook is designed to assist with a security investigation by providing an analysis of indicator relationships. The following information is included:
- Indicators of compromise (IOCs) related to the investigation.
- Attack patterns related to the investigation.
- Campaigns related to the investigation.
- IOCs associated with the identified campaigns.
- Reports containing details on the identified campaigns.
TIM - Indicators Exclusion By Related IncidentsThis playbooks allows you to exclude indicators according to the number of incidents the indicator is related to. The indicator query is "investigationsCount:>=X" where X is the number of related incidents to the indicator that you set. Excluded indicators are located in the Cortex XSOAR exclusion list and are removed from all of their related incidents and future ones. The purpose of excluding these indicators is to reduce the amount internal and common indicators appearing in many incidents and showing only relevant indicators. Creating exclusions can also accelerate performance.
TIM - Intel TrackingTrack threat actors and campaigns by uploading threat intelligence in the form of briefs and IOCs. Add notes and find IOCs in related incidents.
TIM - Process AWS indicatorsThis playbook handles the tagging of AWS indicators. Specify the tag to apply to these indicators in the playbook inputs. An example tag will be approved_white. If no inputs are specified, the indicators will be tagged for manual review. The user can specify whether a manual review incident is required.
TIM - Process Azure indicatorsThis playbook handles the tagging of Azure indicators. Specify the tag to apply to these indicators in the playbook inputs. An example tag will be approved_white. If no inputs are specified, the indicators will be tagged for manual review. The user can specify whether a manual review incident is required.
TIM - Process CIDR Indicators By SizeThis playbook processes CIDR indicators of both IPV4 and IPV6. By specifying in the inputs the maximum number of hosts allowed per CIDR, the playbook tags any CIDR that exceeds the number as pending_review. If the maximum CIDR size is not specified in the inputs, the playbook does not run.
TIM - Process Domain Age With WhoisThis playbook compares the domain creation time against a provided time value such as one month ago. The period can be configured within the playbook inputs MinimumAgeOfDomainMonths or MinimumAgeOfDomainHours. The playbook calculates the timestamp for the relevant period and compares it to the domain creation time value provided by Whois. The domains are outputted accordingly if they were created before or after the compared time, respectively.
TIM - Process Domain Registrant With WhoisThis playbook compares the domain registrant against the Cortex XSOAR list of approved registrants provided in the inputs. A registrant is the company or entity that owns the domain.
TIM - Process Domains With WhoisThis playbook uses several sub playbooks to process and tag indicators based on the results of the Whois tool.
TIM - Process File Indicators With File Hash TypeThis playbook processes file indicator by tagging them with the relevant file hash type tag, such as Sha256, Sha1, and Md5.
TIM - Process Indicators - Fully AutomatedThis playbook tags indicators ingested from high reliability feeds. The playbook is triggered due to a Cortex XSOAR job. The indicators are tagged as approved_white, approved_black, approved_watchlist. The tagged indicators will be ready for consumption for 3rd party systems such as SIEM, EDR etc.
TIM - Process Indicators - Manual ReviewThis playbook tags indicators ingested by feeds that require manual approval. The playbook is triggered due to a job. The indicators are tagged as requiring a manual review. The playbook optionally concludes with creating a new incident that includes all of the indicators that the analyst must review.
To enable the playbook, the indicator query needs to be configured. An example query is a list of the feeds whose ingested indicators should be manually reviewed. For example, sourceBrands:"Feed A" or sourceBrands:"Feed B".
TIM - Process Indicators Against Approved Hash ListThis playbook checks if file hash indicators exist in a Cortex XSOAR list. If the indicators exist in the list, they are tagged as approved_hash.
TIM - Process Indicators Against Business Partners Domains ListThis playbook processes indicators to check if they exist in a Cortex XSOAR list containing the business partner domains, and tags the indicators accordingly.
TIM - Process Indicators Against Business Partners IP ListThis playbook processes indicators to check if they exist in a Cortex XSOAR list containing business partner IP addresses, and tags the indicators accordingly.
TIM - Process Indicators Against Business Partners URL ListThis playbook processes indicators to check if they exist in a Cortex XSOAR list containing business partner urls, and tags the indicators accordingly. To enable the playbook, provide a Cortex XSOAR list name containing business partner urls.
TIM - Process Indicators Against Organizations External IP ListThis playbook processes indicators to check if they exist in a Cortex XSOAR list containing the organizational External IP addresses or CIDR, and tags the indicators accordingly.
TIM - Process Office365 indicatorsThis playbook handles the tagging of Office365 indicators. Specify the tag to apply to these indicators in the playbook inputs. An example tag will be approved_white. If no inputs are specified, the indicators will be tagged for manual review. The user can specify whether a manual review incident is required.
TIM - QRadar Add Bad Hash IndicatorsThis playbook queries indicators based on a pre-defined query or results from a parent playbook, and adds the resulting indicators to a QRadar Reference Set. The Reference Set name must be defined in the playbook inputs.
TIM - QRadar Add Domain IndicatorsThis playbook queries indicators based on a pre-defined query or results from a parent playbook, and adds the resulting indicators to a QRadar Reference Set. The Reference Set name must be defined in the playbook inputs.
TIM - QRadar Add IP IndicatorsThis playbook queries indicators based on a pre-defined query or results from a parent playbook, and adds the resulting indicators to a QRadar Reference Set. The Reference Set name must be defined in the playbook inputs.
TIM - QRadar Add Url IndicatorsThis playbook queries indicators based on a pre-defined query or results from a parent playbook, and adds the resulting indicators to a QRadar Reference Set. The Reference Set name must be defined in the playbook inputs.
TIM - Review Indicators ManuallyThis playbook helps analysts manage the manual process of reviewing indicators. The playbook indicator query is set to search for indicators that have the 'pending review' tag. The playbook's layout displays all of the related indicators in the summary page. While reviewing the indicators, the analyst can go to the summary page and tag the indicators accordingly with tags 'such as, 'approved_black', 'approved_white', etc. Once the analyst completes their review, the playbook can optionally send an email with a list of changes done by the analyst which haven't been approved. Once complete, the playbook removes the 'pending review' tag from the indicators.
TIM - Review Indicators Manually For WhitelistingThis playbook helps analysts manage the manual process of adding indicators from cloud providers, apps, services etc. to an allow list. The playbook indicator query is set to search for indicators that have the 'whitelist_review' tag. The playbooks layout displays all of the related indicators in the summary page. While reviewing the indicators, the analyst can go to the summary page and tag the indicators accordingly with tags such as, 'approved_black', 'approved_white', etc. Once the analyst completes the review, the playbook can optionally send an email with a list of changes done by the analyst which haven't been approved. Once complete, the playbook removes the 'whitelist review' tag from the indicators.
TIM - Run Enrichment For All Indicator TypesThis playbook performs enrichment on indicators
based on playbook query, as specified in the playbook
inputs. This playbook needs to be used with caution as it might use up the user
enrichment integration's API license when running enrichment for large amounts of
indicators. Example queries can be "tags:example_tag" for indicators with a specific tag. For a specific feed name"
the query will be "sourceBrands:example_feed". For a specifc reputation the query will be "reputation:None" etc.
TIM - Run Enrichment For Domain IndicatorsThis playbook processes indicators by enriching indicators based on the indicator feed's reputation, as specified in the playbook inputs. This playbook needs to be used with caution as it might use up the user enrichment integration's API license when running enrichment for large amounts of indicators.
TIM - Run Enrichment For Hash IndicatorsThis playbook processes indicators by enriching indicators
based on the indicator feed's reputation, as specified in the playbook
inputs. This playbook needs to be used with caution as it might use up the user
enrichment integration's API license when running enrichment for large amounts of
indicators.
TIM - Run Enrichment For IP IndicatorsThis playbook processes indicators by enriching indicators
based on the indicator feed's reputation, as specified in the playbook
inputs. This playbook needs to be used with caution as it might use up the user
enrichment integration's API license when running enrichment for large amounts of
indicators.
TIM - Run Enrichment For Url IndicatorsThis playbook processes indicators by enriching indicators
based on the indicator feed's reputation, as specified in the playbook
inputs. This playbook needs to be used with caution as it might use up the user
enrichment integration's API license when running enrichment for large amounts of
indicators.
TIM - Update Indicators Organizational External IP TagThis playbook checks if an indicator with a tag of organizational_external_ip has been updated and keeps/removes the tag according to the check results.
Traps Blacklist FileDeprecated. Use CortexXDR instead.
Traps Isolate EndpointDeprecated. Use CortexXDR instead.
Traps Quarantine EventDeprecated. Use CortexXDR instead.
Traps Retrieve And Download FilesDeprecated. Use CortexXDR instead.
Traps Scan EndpointDeprecated. Use CortexXDR instead.
Trend Micro CAS - Indicators HuntingIn this playbook, the 'trendmicro-cas-email-sweep' command is used to automatically hunt for and detect IOCs within email messages protected by Cloud App Security (CAS).

Note that multiple search values should be separated by commas only (without spaces or any special characters).

Supported IOCs for this playbook:
- IP Addresses
- CIDR
- File Name
- File Type
- SHA1
- URL
- Domain
- Email Addresses

Separate searches are conducted for each type of indicator in the playbook.
TrendMicro Malware Alert PlaybookDeprecated. No available replacement.
Tufin - Enrich IP Address(es)Enrich a single IP using SecureTrack. Returns information such as the associated zones, network objects and policies for the address, and if the address is network device.
Tufin - Enrich Source & Destination IP InformationEnrich source and destination IP information using SecureTrack. Returns information such as the associated zones, network objects and policies for the addresses, if the addresses are network devices, and a topology map from source to destination.
Tufin - Get Application Information from SecureAppSearch SecureApp by application name and retrieve basic application information and all application connections.
Tufin - Get Network Device Info by IP AddressUse a device's IP address to gather information about the device, including basic device information, USP zone(s), and policies related to the device.
Tufin - Investigate Network AlertExample Playbook utilizing the Tufin integration to enrich a network alert and perform containment, if needed.

Requires the following incident details: Source IP, Destination IP, Destination Ports
Un-quarantine Device in Cisco ISE - PANW IoT 3rd Party IntegrationHandles incidents triggered from PANW Iot (Zingbox) UI to un-quarantine a device in Cisco ISE.
Uncover Unknown Malware Using SSDeepThis playbook leverages the case management and TIM aspects of XSOAR to uncover unknown malware.
The playbook does the following:
- Gets the SSDeep hash of a known malicious MD5 or SHA256 hash by enriching the hash via VirusTotal, and attempting to retrieve the related file from an endpoint.
- Creates relationships between otherwise unknown indicators - based on their correspondence to the SSDeep that was deemed similar to the original SSDeep of the malicious hash.
- Links incidents that had any of the indicators which were found related based on the SSDeep hash similarity.
- Enriches the original hash to get the threat actor, malware family and VirusTotal community comments.
- Finds endpoints where occurences of any of the similar hashes exists.
- Sets detected similar hashes and original hash as malicious, if one of them is detected as malicious.
- Remediates the incident by blocking all the malicious hashes in the organization (with user approval).

These steps allow the analyst to find new files, incidents and endpoints which could be related to the the original hash that was searched simply based on the similarity of SSDeep hashes.
Unisolate Endpoint - CybereasonThis playbook unisolates a machine based on the hostname provided.
Unisolate Endpoint - GenericThis playbook unisolates endpoints according to the endpoint ID or host name provided in the playbook.
It currently supports the following integrations:
- Carbon Black Response
- Cortex XDR
- Crowdstrike Falcon
- FireEye HX
- Cybereason
- Microsoft Defender For Endpoint.
UnitTestTopLevel
Unzip FileThis playbook checks whether a file has an extension that supports unzipping, and unzips the file.
Update enforcement mode - IllumioUpdate the enforcement mode for one or more workloads.
Update Incident Status And Fetch Attachments - SecuronixThis playbook fetches the attachments for the incident. Also, it updates the state of the Securonix incident based on the configuration provided in integration configuration.
Update Or Remove Assets - RiskIQ Digital FootprintUsing various user inputs, this playbook checks if the user wants to update or remove an asset, and performs the respective actions.
Supported integration:
- RiskIQ Digital Footprint
Upload Vulnerability Report to AutomoxThis sub-playbook takes the entryId of a vulnerability report CSV file and uploads it to Automox for remediation.
Uptycs - Bad IP IncidentGet information about processes which open connections to known Bad IP's
Uptycs - Outbound Connection to Threat IOC IncidentGet information about connections from IOC incidents.
URL Enrichment - GenericDeprecated. Use "URL Enrichment - Generic v2" playbook instead. Enrich URL using one or more integrations.

URL enrichment includes:
Verify URL SSL
Threat information
URL reputaiton
Take URL screenshot
URL Enrichment - Generic v2Enrich URLs using one or more integrations.

URL enrichment includes:
SSL verification for URLs.
Threat information.
Providing of URL screenshots.
URL Reputation using !url.
URL Enrichment - RST Threat FeedEnrich URLs using one or more integrations.

URL enrichment includes:
SSL verification for URLs
Threat information
* Providing of URL screenshots
URL Reputation - ReversingLabs TitaniumCloudGet reputation data for the submitted URL.
Required TitaniumCloud API rights:

TCA-0403
US - Breach NotificationThis playbook is triggered by a breach notification incident and then proceeds to the breach notification playbook for the relevant state.

DISCLAIMER: Please consult with your legal team before implementing this playbook.
User Investigation - GenericThis playbook performs an investigation on a specific user, using queries and logs from SIEM, Identity management systems, XDR, and firewalls.

Supported Integrations:
-Okta
-Splunk
-QRadar
-Azure Log Analytics
-PAN-OS
-XDR / Core By Palo Alto Networks.
Vulnerability Handling - NexposeManage vulnerability remediation using Nexpose data, and optionally enrich data with 3rd-party tools.

Before you run this playbook, run the "Vulnerability Management - Nexpose (Job)" playbook.
Vulnerability Handling - QualysDeprecated. Manage vulnerability remediation using Qualys data, and optionally enrich data with 3rd-party tools.

Before you run this playbook, run the "Vulnerability Management - Qualys (Job)" playbook.
Vulnerability Handling - Qualys - Add custom fields to default layoutDeprecated. Add information about the vulnerability and asset from the "Vulnerability Handling - Qualys" playbook data to the default "Vulnerability" layout.
Vulnerability Management - Nexpose (Job)Deprecated. No available replacement. Manage assets vulnerabilities using Nexpose.

This playbook runs as a job, and by default creates incidents of type "Vulnerability" based on assets and vulnerabilities.
The incidents are created by querying Nexpose for the input assets vulnerability list.
You can define the minimum severity (minSeverity) that incidents are created for.
Duplicate incidents are not created for the same asset ID and the Nexpose ID.

This playbook is a part of a series of playbooks for Nexpose vulnerability management and remediation.
For this series of playbooks to run successfully, create a Job and do the following:
1. Assign this playbook to the Job
2. Enter the relevant assets' hostnames in the playbook inputs (comma separated list).
3. Associate the "Vulnerability" type incident to the "Vulnerability Handling - Nexpose" playbook.
Vulnerability Management - Qualys (Job)Deprecated. Use the `Vulnerability Management - Qualys (Job) - V2` playbook instead.
Use the latest Qualys report to manage vulnerabilities.

This playbook runs as a job, and by default creates incidents of type "Vulnerability" based on assets and vulnerabilities.
The incidents are created from the latest version of the report determined by the report timestamp.
You can define the minimum severity (minSeverity) that incidents are created for.
Duplicate incidents are not created for the same asset ID and QID.

This playbook is a part of a series of playbooks for Qualys vulnerability management and remediation.
For this series of playbooks to run successfully, create a Job and do the following:
1. Assign this playbook to the Job
2. Enter the Qualys XML report name into the "Details" field
3. Associate the "Vulnerability" type incident to the "Vulnerability Handling - Qualys" playbook.
Vulnerability Management - Qualys (Job) - V2Use the latest Qualys report to manage vulnerabilities.

This playbook runs as a job, and by default creates incidents of type "Vulnerability" based on assets and vulnerabilities.
The incidents are created from the latest version of the report determined by the report timestamp.
You can define the minimum severity (minSeverity) that incidents are created for.
Duplicate incidents are not created for the same asset ID and QID.

This playbook is a part of a series of playbooks for Qualys vulnerability management and remediation.
For this series of playbooks to run successfully, create a Job and do the following:
1. Assign this playbook to the Job
2. Enter the Qualys XML report name into the "Details" field
3. Associate the "Vulnerability" type incident to the "Vulnerability Handling - Qualys" playbook.
Vulnerability Scan - RiskIQ Digital Footprint - Tenable.ioPerforms a vulnerability scan for an asset of type "Host" and "IP Address" using Tenable.io integration.
Supported integration:
- Tenable.io
Wait Until DatetimePauses execution until the date and time that was specified in the plabyook input is reached.
WhisperGate and HermeticWiper & CVE-2021-32648- On January 14th, 2022, reports began on a malware operation dubbed "WhisperGate" targeting multiple -organizations in Ukraine.

- On February 23, 2022, a new wiper malware known as "HermeticWiper" was disclosed by several cybersecurity researchers. The new wiper "HermeticWiper" was also being used against organizations in Ukraine.

CVE-2021-32648 vulnerability has a CVSS score of 9.1 and was found in octobercms, which is a CMS platform based on the Laravel PHP Framework.
In affected versions of the october/system package an attacker can request an account password reset and then gain access to the account using a specially crafted request.
The issue has been patched in Build 472 and v1.1.5.

The playbook includes the following tasks:
- Collect related known indicators from Unit 42, CISA and Malware News blog.
- Search for possible vulnerable servers using Xpanse.
- Indicators and exploitation patterns hunting using PAN-OS, Cortex XDR and SIEM products.
- Block indicators automatically or manually.

Mitigations:
October CMS security recommendations
Deploy YARA detection Rules.

More information:
UNIT42 Blog - Ongoing Russia and Ukraine Cyber Conflict
Russia-Ukraine Cyberattacks: How to Protect Against Related Cyberthreats Including DDoS, HermeticWiper, Gamaredon and Website Defacement
Microsoft Blog
CVE-2021-32648 NVD

Note: This is a beta playbook, which lets you implement and test pre-release software. Since the playbook is beta, it might contain bugs. Updates to the pack during the beta phase might include non-backward compatible features. We appreciate your feedback on the quality and usability of the pack to help us identify issues, fix them, and continually improve.
WhisperGate and HermeticWiper & CVE-2021-32648- On January 14th, 2022, reports began on a malware operation dubbed "WhisperGate" targeting multiple -organizations in Ukraine.

- On February 23, 2022, a new wiper malware known as "HermeticWiper" was disclosed by several cybersecurity researchers. The new wiper "HermeticWiper" was also being used against organizations in Ukraine.

CVE-2021-32648 vulnerability has a CVSS score of 9.1 and was found in octobercms, which is a CMS platform based on the Laravel PHP Framework.
In affected versions of the october/system package an attacker can request an account password reset and then gain access to the account using a specially crafted request.
The issue has been patched in Build 472 and v1.1.5.

The playbook includes the following tasks:
- Collect related known indicators from Unit 42, CISA and Malware News blog.
- Search for possible vulnerable servers using Xpanse.
- Indicators and exploitation patterns hunting using PAN-OS, Cortex XDR and SIEM products.
- Block indicators automatically or manually.

Mitigations:
October CMS security recommendations
Deploy YARA detection Rules.

More information:
UNIT42 Blog - Ongoing Russia and Ukraine Cyber Conflict
Russia-Ukraine Cyberattacks: How to Protect Against Related Cyberthreats Including DDoS, HermeticWiper, Gamaredon and Website Defacement
Microsoft Blog
CVE-2021-32648 NVD

Note: This is a beta playbook, which lets you implement and test pre-release software. Since the playbook is beta, it might contain bugs. Updates to the pack during the beta phase might include non-backward compatible features. We appreciate your feedback on the quality and usability of the pack to help us identify issues, fix them, and continually improve.
WildFire - Detonate fileDeprecated. Use WildFire - Detonate file v2 instead.
WildFire - Detonate file v2Detonate one or more files using the Wildfire v2 integration. This playbook
returns relevant reports to the War Room and file reputations to the context data.
The detonation supports the following file types -
APK, JAR, DOC, DOCX, RTF, XLS, XLSX, PPT, PPTX, OOXML, PE32, PE, PDF, DMG, PKG, RAR, 7Z, JS, ELF, HTA, LNK, VBS, PS1, PERL, PYTHON, SHELL.

Note: Base64 encoded files are currently not supported.
Wildfire Detonate and Analyze FileThis playbook uploads, detonates, and analyzes files for the Wildfire sandbox.
WildFire MalwareThis playbook handles WildFire Malware alerts.
It performs enrichment on the different alert entities and establishes a verdict.
For a possible true positive alert, the playbook performs further investigation for related IOCs and executes a containment plan.
XCloud Alert EnrichmentThis playbook is responsible for data collection and enrichment.

The playbook collects or enriches the following data:

- Account enrichment


- Network enrichment

-Attacker IP

-Geolocation

-ASN
XCloud CryptojackingInvestigates a Cortex XDR incident containing Cloud Cryptojacking related alert.
The playbook supports AWS, Azure, and GCP and executes the following:

- Cloud enrichment:

-Collects info about the involved resources

-Collects info about the involved identities

-Collects info about the involved IPs


- Verdict decision tree


- Verdict handling:

-Handle False Positives

-Handle True Positives

-Cloud Response - Generic sub-playbook.

- Notifies the SOC if a malicious verdict was found
XCloud Cryptojacking - Set VerdictThis playbook sets the alert's verdict as malicious if one of the following conditions is true:
1. If the source IP address is malicious
2. If the incident includes both "Unusual allocation of multiple cloud compute resources" AND "Cloud identity reached a throttling API rate" (medium/high severity)
3. If the incident includes both "Unusual allocation of multiple cloud compute resources" AND "Suspicious heavy allocation of compute resources - possible mining activity"
4. If the incident includes "Unusual allocation of multiple cloud compute resources" with medium/high severity, the source ASN isn't known, and the source IP isn't known as well.
5. If the incident includes both "Unusual allocation of multiple cloud compute resources" AND "A cloud compute instance was created in a dormant region"

If none of the conditions is true, the playbook will wait for an analyst's decision.
XDR Best Practice AssessmentThis playbook covers an XDR Best Practice Assessment for existing XDR deployments. It provides surveys for each domain of the assessment.

The assessment covers the following domains: Configurations, Agent Management, Policy and Profiles, Profile Extensions, Incident Management, and Incident Response.
xMatters - Example Conditional ActionsExample playbook showing how to use the Trigger and Wait sub-playbook to fire an event to xMatters and wait for a response from a user. This playbook then inspects the user's chosen response and branches accordingly.
xMatters - Wait for ResponseTrigger an xMatters workflow to notify a user for a response.
Xpanse - Alert EnrichmentAdditional enrichment via cloud service providers and other applicable IT and security tools.
Xpanse - Alert HandlerDefault alert handling for Cortex Xpanse alerts.
Xpanse - Alert Self-EnrichmentEnrichment on the alert itself using Cortex Xpanse APIs.
Xpanse - NMap - Detect ServicePlaybook that uses NMap to do a validation scan.
Xpanse Incident Handling - GenericA generic playbook for handling Xpanse issues.
The logic behind this playbook is to work with an internal exclusions list which will help the analyst to get to a decision or, if configured, close incidents automatically.
The phases of this playbook are:
1) Check if assets (IP, Domain or Certificate) associated with the issue are excluded in the exclusions list and optionally, close the incident automatically.
2) Optionally, enrich indicators and calculate the severity of the issue, using sub-playbooks.
3) Optionally, allow the analyst to add associated assets (IP, Domain or Certificate) to the exclusions list.
4) Tag associated assets.
5) Update the status of the issue.
xsoar-data-collection-response-trackingThis playbook tracks the user responses and resends the emails to recipients who have not responded
xsoarwebserver-email-acknowledgementPlaybook to demonstrate the features of XSOAR-Web-Server. It sends an html email to a set of users up to 2 times. The email can contain multiple html links, that the users can click and the response will be available in the context. This playbook sets up the webserver to handle http get requests
xsoarwebserver-email-data-collectionPlaybook to demonstrate the features of XSOAR-Web-Server. It sends an html email to a set of users up to 2 times. The email can contain multiple html links, that the users can click and the response will be available in the context
YARA - File ScanA playbook to run YARA scan against uploaded file.
To run the playbook, provide the YARA rule content and the entry ID of the file you intend to scan.
Zendesk - Ticket Management`Zendesk - Ticket Management` allows you to open a new ticket or comment on an existing ticket.
ZTAP AlertThis playbok is triggered by fetching escalated ZTAP Alerts.
The playbook fetches newly escalated alerts.
Then, the playbook performs enrichment on the incident's indicators.
Lastly, it adds comments/logs as Evidence.

Scripts#

NameDescription
A1000FinalClassificationCalculates A1000 final classification based on A1000 classification and A1000 full reports.
AbuseIPDBPopulateIndicatorsExtracts IP addresses on block lists from AbuseIPDB, and Populates Indicators accordingly.
ActiveUsersD2Get active users from a D2 agent and parsed them into context
AddDBotScoreToContextAdd DBot score to context for indicators with custom vendor, score, reliability, and type.
AddDomainRiskScoreToContextSets average risk score to context for pivot result.
AddEvidenceAdds 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)
AddKeyToListAdds/Replaces a key in key/value store backed by an XSOAR list.
AddUserToIncidentTeamAdds an XSOAR User to the Incident, this automation can be used as part of a playbook task.
ADGetUserDeprecated. Use the ad-get-user command in the Active Directory v2 integration instead.account['Groups'] = demisto.get( Use Active Directory to retrieve detailed information about a user account. The user can be specified by name, email or as an Active Directory Distinguished Name (DN).
If no filter is provided, the result will show all users.
AfterRelativeDateChecks the given datetime has occured after the provided relative time.
AlgosecCreateTicketCreates a new FireFlow change request.
AlgosecGetApplicationsFind applications containing network objects related to IP address using BusinessFlow.
AlgosecGetNetworkObjectFind network objects related to IP address.
AlgosecGetTicketRetrieves a FireFlow change request by its ID
AlgosecQueryPerforms a batch traffic simulation query using Firewall Analyzer.
AnalyzeMemImageUse Volatility to run common memory image analysis commands
AnalyzeOSXGet file and url reputation for osxcollector result.
will use VirusTotal for Url checks, and IBM XForce for MD5 checks.
maxchecks : for
system : system name to run agent on.
section : the type check that OSXCollector should run.
AnyMatchReturns all elements from the left side that have a substring that is equal to an element from the right side. Note: This filter is case-insensitive.
E.g -AnyMatch left=baby right=A will return baby. For more examples see the filter's Readme.
AppendIfNotEmptyAppend item(s) to the end of the list if they are not empty.
AppendindicatorFieldWrapperA 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.
AquatoneDiscoveraquatone-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.
AquatoneDiscoverV2aquatone-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.
ArcannaFeedbackPostProcessingArcanna.Ai post-processing script for sending feedback back to Arcanna about the closed incident. Additional modification might be required depending on each Cortex setup.
This script is intended to be used as a sample or in conjunction with the Arcanna-Generic-Investigation playbook.
ArcherCreateIncidentExampleThis script is an example script of how to create Incident in Archer. The script generates the create incident data in JSON format and execute the command archer-create-record.
AreValuesEqualCheck whether the values provided in arguments are equal. If either of the arguments are missing, no is returned.
ArrayToCSVConverts a simple Array into a textual comma separated string
AssignAnalystToIncidentAssign 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.
AssignAnalystToIncidentOOOAssigns analysts who are not out of the office to the shift handover incident.
Use the ManageOOOusers automation to add or remove analysts from the out-of-office list.

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-XSOAR/6.10/Cortex-XSOAR-Administrator-Guide/Automations
AssignToMeButtonAssigns the current Incident to the Cortex XSOAR user who clicked the button
AssignToNextShiftRandomly assigns the incidents to users on call (requires shift management) and users on call.
https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.10/Cortex-XSOAR-Administrator-Guide/Shift-Management#idf554fd0f-f93b-40cd-9111-1393bf25ac6e
Incident Ids should be passed in as a comma separated list.

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-XSOAR/6.10/Cortex-XSOAR-Administrator-Guide/Automations
AssignToNextShiftOOORandomly assigns the active incidents to on call analysts (requires shift management).
This automation works with the other out-of-office automations to ensure only available analysts are assigned to the active incidents.

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-XSOAR/6.10/Cortex-XSOAR-Administrator-Guide/Automations
AssociateIndicatorsToIncidentAssociate Indicators to an Incident.
ATDDetonateDetonate File or URL through McAfee ATD.
AWSAccountHierarchyDetermine AWS account hierarchy by looking up parent objects until the organization level is reached.
AwsCreateImageDeprecated. This script is deprecated. Use the AWS-EC2 integration instead.
AwsCreateVolumeSnapshotDeprecated. This script is deprecated. Use the AWS-EC2 integration instead.
AwsEC2GetPublicSGRulesFind Security Group rules which allows ::/0 (IPv4) or 0.0.0.0/0.
AwsEC2SyncAccountsUpdate an AWS - EC2 instance with a list of accounts in an AWS organization, which will allow EC2 commands to run in all of them.
AwsGetInstanceInfoDeprecated. Get AWS EC2 instance details
AWSRecreateSGAutomation to determine which interface on an EC2 instance has an over-permissive security group, determine which security groups have over-permissive rules, and replace them with a copy of the security group that has only the over-permissive portion removed. Over-permissive is defined as sensitive ports (SSH, RDP, etc) being exposed to the internet via IPv4.
AwsRunInstanceDeprecated. This script is deprecated. Use the AWS-EC2 integration instead.
AwsStartInstanceDeprecated. This script is deprecated. Use the AWS-EC2 integration instead.
AwsStopInstanceDeprecated. This script is deprecated. Use the AWS-EC2 integration instead.
AzureFindAvailableNSGPrioritiesThis script takes in a list of numbers that represent Azure priorities for NSG rules, a target priority number, and a number available priorities to return available priorities from the provided list.
Base64DecodeDecodes an input in Base64 format.
Base64EncodeWill encode an input using Base64 format.
Base64EncodeV2Encodes an input to Base64 format.
Base64ListToFileConverts Base64 file in a list to a binary file and upload to warroom
BaseScript[Enter a description of the script, including what function it performs and any important information users need to know, for example required permissions.]
BatchDataThis Automation takes in a string of comma separated items and returns a dictionary of with the defined chunk size.
BetweenDatesWhether value is within a date range.
BetweenHoursChecks whether the given value is within the specified time (hour) range.
BinarySearchPyDeprecated. No available replacement. Search for a binary on an endpoint using Carbon Black
BlockIPDeprecated. Blocks IP in configured firewall
BMCHelixRemedyforceCreateIncidentThis script is used to simplify the process of creating the incident in BMC Helix Remedyforce. The Script will consider the ID over the name of the argument when both are provided. Example: client_id is considered when both client_id and client_user_name are provided.
BMCHelixRemedyforceCreateServiceRequestThis script is used to simplify the process of creating a service request in BMC Helix Remedyforce. The script will consider the ID over the name of the argument when both are provided. Example: client_id is considered when both client_id and client_user_name are provided.
BMCToolParse RDP bitmap cache data into a single collage image file.
BrandImpersonationDetectionAnalyzes the forensic data to detect brand impersonation attacks. This script uses the HMRC brand as an example, please modify the attributes associated with your company’s brand.
BreachConfirmationHTML
BuildEWSQueryReturns an EWS query according to the automation's arguments.
BuildSlackBlocksFromIndexExtracts the index.zip and filters new packs since the last run.
Builds the slack message for new packs.
CalculateEntropyCalculates the entropy for the given data.
CalculateGeoDistanceCompute the distance between two sets of coordinates, in miles.
CalculateTimeDifferenceCalculate the time difference, in minutes
CalculateTimeSpanCalculates the time span between two dates using Powershell's `New-TimeSpan` command.

A timespan with a start date of "2022-04-02T15:42:48" and end date of "2022-04-12T16:55:07" would return the following:

Days : 10
Hours : 1
Minutes : 12
Seconds : 19
Milliseconds : 0
Ticks : 8683390000000
TotalDays : 10.0502199074074
TotalHours : 241.205277777778
TotalMinutes : 14472.3166666667
TotalSeconds : 868339
TotalMilliseconds : 868339000
CaseMgmtAnalystToolsDynamic display script to display a list of useful Analyst Tools on an Incident layout.

Create an XSOAR list called "Case Management Analyst Tools", and add a markdown table to provide your own list.
CaseMgmtDisplayLabelsDynamic section that will display the Labels for an Incident in a markdown table.
CaseMgmtIncidentTypesByRoleRestricts the Incident Types a user can create manually, based on their assigned XSOAR Role(s).

Requirements - Create an XSOAR List called IncidentTypeRBAC with the following structure, the names must match exactly to the names in the Incident Types under Settings!

Example List:
{
"Default":["Case","Job","Unclassified"],
"Analyst":["Phishing","Malware"],
"ThreatHunters":["Hunt"]
}
CaseMgmtIncidentTypesDisplayRestricts the Incident Types a user can create manually based on an XSOAR list, and prevents changing the Incident Type manually once it is created.

Requirements - Create an XSOAR List called IncidentTypesFromList a list of comma separated Incident Types

Incident Type 1,Incident Type 2, Incident Type 3
CaseMgmtResponseProcessDynamic display script to display a response process on an Incident layout. The response process display can change depending on the Incident Type.
CBAlertsGet the list of Alerts from Carbon Black Enterprise Response. Supports the same arguments as the cb-alerts command.
CBEventsReturns all events associated with a process query
CBFindIPSearch Carbon Black for connection to specified IP addresses.
CBLiveFetchFilesDeprecated. Use CBLiveGetFile_V2 instead. Live.
CBLiveGetFile_V2This automation translates an endpoints hostname/IP to the Carbon Black sensor ID.
It then opens a session to the endpoint to download the given file paths and closes the session.
CBLiveProcessListDeprecated. No available replacement.
CBPApproveHashDeprecated. Use the cbp-fileRule-createOrUpdate command instead.
CBPBanHashDeprecated. Use the cbp-fileRule-createOrUpdate command instead.
CBPCatalogFindHashSearch the CBP/Bit9 file catalog for an md5 hash.
CBPFindComputerFind a computer in CBEP/Bit9.
CBPFindRuleFind the rule state for a hash value in CBEP/Bit9.
CBSensorsList Carbon Black sensors
CBSessionsList Carbon Black sessions
CBWatchlistsDisplay all watchlists and their details, queries, etc.
CEFParserParse 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.
CertificateExtractExtract fields from a certificate file and return the standard context.
CertificateReputationEnrich and calculate the reputation of a certificate indicator.
CertificatesTroubleshootExports all certificate-related information from the Python Docker container and decodes it using RFC. It also retrieves the certificate located in the specified endpoint.
ChangeContextEnables 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.
ChangeRemediationSLAOnSevChangeChanges the remediation SLA once a change in incident severity occurs.
This is done automatically and the changes can be configured to your needs.
CheckContextValueThis 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.
CheckDockerImageAvailableCheck if a docker image is available for performing docker pull. Script simulates the docker pull flow but doesn't actually pull the image. Returns an entry with 'ok' if all is good otherwise will return an error.
CheckEmailAuthenticityChecks the authenticity of an email based on the email's SPF, DMARC, and DKIM.
CheckFieldValueThis 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.
CheckIfSubdomainChecks whether a given domain is a subdomain of one of the listed domains.
CheckIndicatorValueCheck if indicators exist in the Threat Intel database.
CheckLastEnrichmentCheck if DomainTools Data is in Need of Enrichment.
CheckPanosVersionAffectedChecks if the given PAN-OS version number is affected by the given list of vulnerabilties from the pan-advisories-get-advisories command.
CheckPivotableDomainsChecks for guided pivots for a given domain.
CheckPointDownloadBackupDeprecated. Use ssh command instead. Downloads the Check Point policy backup to the Cortex XSOAR War Room.
CheckpointFWBackupStatusDeprecated. Use ssh command instead. Connect to a CheckPoint firewall appliance using SSH and retrieve the status for backup tasks. The user account being used to access the device must be set to use the SSH shell and not the built-in CheckPoint CLI. For more information, consult the CheckPoint documentation.
CheckpointFWCreateBackupDeprecated. Use ssh command instead. Connect to a Check Point firewall appliance using SSH and trigger a task to create a configuration backup of the device. The user account being used to access the device must be set to use the SSH shell and not the built-in Check Point CLI. For more information, consult the CheckPoint documentation.
CheckSenderFor phishing incidents, check the sender of the email via Pipl search
CheckSenderDomainDistanceGet the string distance for the sender from our domain
CheckTagsCheck DomainTools domain tags and if a tag is found mark incident as high severity.
checkValueGets 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.
CherwellCreateIncidentThis script is an example script of how to create an incident in Cherwell. The script wraps the create business object command in the cherwell integration. When writing your own script to create a business object, follow the instructions in the configuration part, but do not change the execution section.
CherwellGetIncidentThis script is an example script of how to retrieve an incident from Cherwell. The script wraps the cherwell-get-business-object command of the cherwell integration. When writing your own script to get a business object, follow the instructions found in the configuration section of the script, but do not change the execution section.
CherwellIncidentOwnTaskThis script is an example script of how to link an incident to a task in Cherwell. The script wraps the cherwell-link-business-object command of the cherwell integration. When writing your own script to link business objects, follow the instructions found in the configuration section of the script, but do not change the execution section.
CherwellIncidentUnlinkTaskThis script is an example script of how to unlink a task from an incident in Cherwell. The script wraps the cherwell-unlink-business-object command of the cherwell integration. When writing your own script to unlink business objects, follow the instructions found in the configuration section of the script, but do not change the execution section.
CherwellQueryIncidentsThis script is an example script of how to query incidents from Cherwell. The script wraps the cherwell-query-business-object command of the cherwell integration. When writing your own script to query business objects, follow the instructions found in the configuration section of the script, but do not change the execution section.
CherwellUpdateIncidentThis script is an example script of how to update an incident in Cherwell. The script wraps the update-business-object command of the cherwell integration. When writing your own script to update a business object, follow the instructions found in the configuration section of the script, but do not change the execution section.
ChronicleAssetEventsForHostnameWidgetScriptDisplays the list of events fetched for an asset identified as a "ChronicleAsset" type of indicator, when its hostname is passed as an asset identifier.
ChronicleAssetEventsForIPWidgetScriptDisplays the list of events fetched for an asset identified as a "ChronicleAsset" type of indicator, when its IP address is passed as an asset identifier.
ChronicleAssetEventsForMACWidgetScriptDisplays the list of events fetched for an asset identified as a "ChronicleAsset" type of indicator, when its MAC address is passed as an asset identifier.
ChronicleAssetEventsForProductIDWidgetScriptDisplays the list of events fetched for an asset identified as a "ChronicleAsset" type of indicator, when its product ID is passed as an asset identifier.
ChronicleAssetIdentifierScriptCollect all asset identifiers - Hostname, IP address and MAC address in the context.
ChronicleDBotScoreWidgetScriptShows the DBot Score and reputation of the Domain.
ChronicleDomainIntelligenceSourcesWidgetScriptShows the details of sources in the Chronicle Domain Intelligence Sources section of the incident.
ChronicleIsolatedHostnameWidgetScriptNotifies if the hostname associated with the ChronicleAsset is isolated or not.
ChronicleIsolatedIPWidgetScriptNotifies if the IP address associated with the ChronicleAsset is isolated or not.
ChronicleListDeviceEventsByEventTypeWidgetScriptDisplays a pie chart of the number of events, categorized by its event type, fetched for all the identifiers of the ChronicleAsset.
ChroniclePotentiallyBlockedIPWidgetScriptNotifies if the IP address associated with the ChronicleAsset is potentially blocked or not.
CIDRBiggerThanPrefixChecks whether a given CIDR prefix is bigger than the defined maximum prefix.
ClassifierNotifyAdminDeprecated. This script is deprecated. See https://xsoar.pan.dev/docs/reference/playbooks/d-bot-create-phishing-classifier-v2 for more information.
CloseInvestigationAsDuplicateClose the current investigation as duplicate to other investigation.
CloseLinkedIncidentsPostProcessingPost Processing Script that will close linked Incidents when the Incident is closed. Will set the same close code as the parent, and add closing notes from the parent.
CloseTaskSetContextClose a task with the closeComplete command, but then also add the "comments" to the incident context.
Code42FileEventsToMarkdownTableFormats Code42 File Events as a markdown table for display in Code42 Alert Incidents.
CofenseTriageReportDownloadDownload all reports associated with the email address.
CofenseTriageThreatEnrichmentEnhancement automation for type indicator, to enrich the value from Cofense Triage.
CollectCampaignRecipientsCollect the recipients from all campaign incidents.

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-XSOAR/6.10/Cortex-XSOAR-Administrator-Guide/Automations
CollectPacksDataThis script collects the data of packs with updates.
commentsToContextTakes 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.
CommitFilesThis script gets content files as input from the context, commits the files in the correct folder and creates the pull request text.
CommonD2Common code that will be merged into each D2 agent script when it runs
CommonServerUserPowerShell
CommonServerUserPython
CommonUserServer
CompareIncidentsLabelsCompares 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:
https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.10/Cortex-XSOAR-Administrator-Guide/Automations
CompareIndicatorsFind the differences between two indicators lists.
CompareListCompares two lists.
CompareListsCompare two lists and put the differences in context.
CompleteTaskOnTimerBreachThis is an SLA breach script that will complete playbook tasks tagged with 'timerbreach' when the SLA breaches.

This can be used to complete tasks waiting for manual input when a timer breaches its SLA, and move the playbook along.
ConcatFormatReturns a string concatenated with given a prefix and suffix which supports DT expressions.
ConferIncidentDetailsDeprecated. Display the incident details retrieved from Confer in a readable format
ConferSetSeverityDeprecated. Set incident severity according to indicators found in an confer alert
ConfigureAzureApplicationAccessPolicyThis script grants a user the permissions needed to create a Teams meeting. It connects to MS Teams, creating an application access policy to a chosen application and then grants a user permissions.
ConflueraDetectionsCountLogs detections count
ConflueraDetectionsDataLogs detections data ( detection vs risk-contribution )
ConflueraDetectionsDataWarroomLogs detections data ( detection vs risk-contribution )
ConflueraDetectionsSummaryLogs detections data ( categories of detections )
ConflueraDetectionsSummaryWarroomLogs detections data ( categories of detections )
ConflueraProgressionsCountLogs progressions count
ConflueraProgressionsDataLogs progressions data ( progression vs risk-score )
ConflueraProgressionsDataWarroomLogs progressions data ( progression vs risk-score )
ContainsCreditCardInfoCheck if a given value is true. Will return 'no' otherwise
ContentPackInstallerContent packs installer from marketplace.
ContextContainsThis script searches for a value in a context path.
ContextFilterFilter 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.
ContextGetEmailsGets all email addresses in context, excluding ones given.
ContextGetHashesGets hashes (MD5,SHA1,SHA256) from context.
ContextGetIpsGets all IP addresses in context, excluding ones given.
ContextGetMACAddressesGets all MAC addresses in context, excluding ones given.
ContextGetPathForStringSearches for string in context and returns context path, returns null if not found.
ContextSearchForStringSearches for string in a path in context. If path is null, string will be searched in full context.
ConvertAllExceptConvert all chosen values but exceptions.
ConvertCountryCodeCountryNameConvert 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" }.
ConvertDatetoUTCConverts a date from a different timezone to UTC timezone.
ConvertDictOfListToListOfDictConverts dictionary of lists to list of dictionaries.
ConvertDomainToURLsConverts Domain(s) to URL(s).
ConvertEnrichmentsToTableThis script is used to convert CrowdStrike IOA enrichments response elements to a table.
ConvertFileConverts 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
ConvertKeysToTableFieldFormatConvert object keys to match table keys.
Use when mapping object/collection to table (grid) field.
(Array of objects/collections is also supported).
Example:
Input: { "Engine": "val1", "Max Results": 13892378, "Key_With^Special (characters)": true }
Output: { "engine": "val1", "maxresults": 13892378, "keywithspecialcharacters": true }
ConvertRequestParametersToTableThis script is used to convert CrowdStrike IOA request parameters to a table.
ConvertResourceAttributesToTableThis script is used to convert CrowdStrike IOM resource attributes to a table.
ConvertResponseElementsToTableThis script is used to convert CrowdStrike IOA response elements to a table.
ConvertTableToHTMLConverts a given array to an HTML table
ConvertTimezoneFromUTCTakes 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
ConvertToSingleElementArrayConverts a single string to an array of that string.
ConvertUserIdentityToTableThis script is used to convert CrowdStrike IOA user identity response elements to a table.
ConvertXmlFileToJsonConverts XML file entry to JSON format
ConvertXmlToJsonConverts XML string to JSON format
CopyContextToFieldCopy 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:
https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.10/Cortex-XSOAR-Administrator-Guide/Automations
CopyFileD2Copy a file from an entry to the destination path on the specified system. This uses the dissolvable agent's HTTPS communication channel rather than scp or other out-of-band methods.
Example usage: !CopyFileD2 destpath=/home/sansforensics/collectedbinaries/inv8_suspiciousPE1.exe.evil entryid=21@8 system=Analyst1
CopyLinkedAnalystNotesCopies the anaylst notes from the integrations and incidents grid.

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-XSOAR/6.10/Cortex-XSOAR-Administrator-Guide/Automations
CopyNotesToIncidentCopy all entries marked as notes from current incident to another incident.
CortexXDRAdditionalAlertInformationWidgetThis script retrieves additional original alert information from the context.
CortexXDRCloudProviderWidgetThis script returns an HTML result of the cloud providers in the incident. The result will be displayed in the following font colors: AWS - red, GCP - green, Azure - blue.
CortexXDRIdentityInformationWidgetThis widget displays Cortex XDR identity information.
CortexXDRInvestigationVerdictThis widget displays the incident verdict based on the 'Verdict' field.
CortexXDRRemediationActionsWidgetThis widget displays Cortex XDR remediation action information.
CountArraySizeCount an array size
CreateArrayWill create an array object in context from given string input
CreateArrayWithDuplicatesWill create an array object in context from a given string input , allowing for duplicate values to be retained

Output is to ContextKey.array as JSON does not permit duplicate key names

e.g., ContextKey.array.value1, ContextKey.array.value2, ContextKey.array.value3, etc.
CreateCertificateCreates a public key (.cer file), a private key (.pfx) file, and a Base64 encoded private key to use to authenticate the EWS Extension Online Powershell v2 integration.
CreateChannelWrapperCreates a channel in Slack v2 or in Microsoft Teams. If both Slack v2 and Microsoft Teams are available, it creates the channel in both Slack v2 and Microsoft Teams.
CreateEDLInstanceUse this automation to create an EDL instance on XSOAR.
CreateEmailHtmlBodyThis script allows sending an HTML email, using a template stored as a list item under Lists (Settings -> Advanced -> Lists).
Placeholders are marked in DT format (i.e. ${incident.id} for incident ID).
Available placeholders for example:
- ${incident.labels.Email/from}
- ${incident.name}
- ${object.value}
See incident Context Data menu for available placeholders

Note: Sending emails require an active Mail Sender integration instance.
CreateFileFromPathObjectThis automation is being executed by the "GetFilePathPreProcessing" pre-processing script that collects the paths and names of attachments of an incoming incident, then passes it to this automation that reads the files and creates them in an existing incident
CreateHashCreating a hash of a given input, support sha1, sha256, sha512, md5 and blake. Wrapper for https://docs.python.org/3/library/hashlib.html.
CreateHashIndicatorWrapperThis is a wrapper to allow or block hash lists from Cortex XDR, MSDE or CrowdStrike.
CreateIndicatorRelationshipThis automation creates a relationship between indicator objects.
CreateIndicatorsFromSTIXCreates 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.
CreateNewIndicatorsOnlyCreate 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.
CreatePlbkDocPurpose: This automation will produce docx file detailing the tasks in the given playbook. It can produce a table or paragraph format of the report.

Author: Mahmood Azmat

Input1: Name of the playbook (Mandatory)
Input2: Format type needed. Table or Paragraph. Paragraph is default.
Input3: Name of the docx file that will be produced. Give the full name including the ".docx" extension. (Mandatory)

Requirements: This automation requires "Core REST API" integration enabled and connected to the XSOAR itself. Automation uses it to read the objects of the playbook.
CreatePrismaCloudComputeComplianceReportButtonGenerate a compliance report via button.
CreatePrismaCloudComputeLinkThis script creates a link back to the Prisma Cloud Compute instance.
CreatePrismaCloudComputeResourceComplianceReportButtonGenerate a compliance report for Prisma Cloud resources - host, container or image.
CreateYARARuleIndicators
CrowdStrikeApiModuleCommon CrowdStrike code that will be appended to each CrowdStrike integration when it is deployed to enable oauth2 authentication automatically.
CrowdStrikeStreamingPreProcessingPre processing script for CrowdStrike Streaming, will not duplicate incidents(detection events) that have same Host.
Will add entry to duplicate(older) incident notifying a duplicate incident was ignored.

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-XSOAR/6.10/Cortex-XSOAR-Administrator-Guide/Automations
CrowdStrikeUrlParseDeprecated. Use CrowdStrike Falcon instead.
CryptoCurrenciesFormatVerifies that a crypto address is valid and only returns the address if it is valid.
CSVFeedApiModuleCommon code that will be appended into each CSV feed integration when it's deployed
CuckooDetonateFileDeprecated. Use the 'cuckoo-create-task-from-file' command instead.
CuckooDetonateURLDeprecated. Use 'cuckoo-create-task-from-url' instead.
CuckooDisplayReportDisplay the contents of a Cuckoo report file from a war room entry.
CuckooGetReportDeprecated. Use the 'cuckoo-get-task-report' command instead.
CuckooGetScreenshotDeprecated. Use 'cuckoo-task-screenshot' command instead.
CuckooTaskStatusDeprecated. Use the 'cuckoo-view-task' command instead.
CustomContentBundleWizardryThis automation accepts an XSOAR custom content bundle, and either returns a list of file names, or the files you want to the war room.
CustomPackInstallerCustom Packs Installer for the Content Management pack.
CutCut a string by delimiter and return specific fields.
Example
=================
input: "A-B-C-D-E"
delimiter: "-"
fields: "1,5"

return: "A-E".
cveReputationDeprecated. Use CveReputationV2 (in CommonScripts) instead.
cveReputationV2Provides the severity of the CVE based on the CVSS score where available.
cvss_colorThis dynamic automation parses the CVSS score of a CVE and presents it in the layout in color according to its score.
CVSSCalculatorThis 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.
CybereasonPreProcessingExamplePreprocessing script to run when fetching Cybereason malops.
Will check if malop was already fetched, and will then update the existing incident, otherwise will create a new incident.
CybersixgillActionableAlertStatusUpdateUpdates the Actionable alert status.
CyCognitoGetEndpointsGenerates a deep link to the CyCognito platform using the incident context.
CYFileRepDeprecated. This script is deprecated. Use the Cylance integration instead.
Cyren-Find-Similar-IncidentsFinds similar incidents by Cyren Case ID

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-XSOAR/6.10/Cortex-XSOAR-Administrator-Guide/Automations
Cyren-Show-Threat-IndicatorsDisplays threat indicators in readable format

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-XSOAR/6.10/Cortex-XSOAR-Administrator-Guide/Automations
CyrenCountryLookupTranslates a country code provided by Cyren products to a full country name (English). Uses ISO 3166-1 alpha-2 for the lookup.
CyrenThreatInDepthRandomHuntThis script will take a random Cyren Threat InDepth feed indicator and its relationships and create a threat hunting incident for you.

The main query parameters for the resulting, internal indicator query are:

1. Seen for the first time by the feed source within the last 7 days.
2. No investigation on it yet.
3. Must have relationships to other indicators.
CyrenThreatInDepthRelatedWidgetShows feed relationship data in a table with the ability to navigate
CyrenThreatInDepthRelatedWidgetQuickShows limited feed relationship data in a table with the ability to navigate
CyrenThreatInDepthRenderRelatedShows feed relationship data in a table with the ability to navigate
D2ActiveUsersShow local accounts
D2AutorunsUsed by the server-side script "Autoruns".
Uses d2 agent on endpoint to run SysInternals Autoruns.
D2DropDrop a file to a target system by providing its path on the server. Use CopyFileD2 instead in most cases.
This is a utility agent script to be used inside server scripts. See CopyFileD2 for an example.
D2ExecExecute the command and pack the output back to server
D2ExecuteCommandRun a D2 built-in command on a D2 agent
D2GetFileGet a file from a system using D2 agent.
D2GetSystemLogCopy a log file. Works on Windows and Unix (differently - take a peek at the script itself to see how).
D2HardwareShow system information
D2O365ComplianceSearchAssign a 'Mailbox Import Export' management role to a user. This script runs through the agent on a Windows machine, pulls and executes a PowerShell script - which talks to the Exchange server.
D2O365SearchAndDeleteAssign a 'Mailbox Import Export' management role to a user. This script runs through the agent on a Windows machine, pulls and executes a PowerShell script - which talks to the Exchange server.
D2PEDumpExecute PE Dump on a file that is under /tmp somewhere. Used internally by StaticAnalyze
D2ProcessesShow running processes
D2RegQueryUse the D2 agent to retrieve the value of the given registry key.
D2RekallUse the D2 agent to execute Rekall on a system (usually a forensics workstation) and analyze a memory dump file located on that system.
D2ServicesShow system services
D2UsersShow local accounts
D2WinpmemUse the D2 agent to carry the winpmem binary to a system and return the memory dump file to the war room. This usually takes a while, depending on amount of RAM in the target system.
DamSensorDownPre processing script for Emails from Mcafee DAM, about sensor disconnected.
Will ignore second notification, but will process first notification into incidents.
DataDomainReputationDeprecated. Evaluate reputation of a URL and Domain and return a score between 0 and 3 (0 - unknown, 1 - known good, 2 - suspicious, 3 - known bad). If the indicator reputation was manually set, the manual value will be returned.
DataminrPulseDisplayRelatedAlertsShows the related alerts fetched for this alert id.
DataminrPulseTransformExtractedIndicatorsToListScript used to transform result received from the extractIndicators (Builtin) script from the dictionary of indicators to a list of indicators.
DateStringToISOFormatThis is a thin wrapper around the `dateutil.parser.parse` function. It will parse a string containing a date/time stamp and return it in ISO 8601 format.
DateTimeNowToEpochReturns the current datetime as an epoch value for use in timestamp comparisons.
DateTimeToADTimeConverts unix time to AD Integer8 time. This is used in many AD date fields like pwdLastSet
DateToTimeStampConverts a date to timestamp.
DBotAverageScoreThe script calculates the average DBot score for each indicator in the context.
DBotBuildPhishingClassifierCreate a phishing classifier using machine learning technique, based on email content.
DBotClosedIncidentsPercentageData output script for populating dashboard pie graph widget with the percentage of incidents closed by DBot vs. incidents closed by analysts.
DBotFindSimilarIncidentsFinds past similar incidents based on incident fields' similarity. Includes an option to also display indicators similarity.
Note: For the similarity calculation, at least one field must be provided in one of the "similarTextField", "similarCategoricalField", or "similarJsonField" arguments.
DBotFindSimilarIncidentsByIndicatorsFinds similar incidents based on indicators' similarity. Indicators' contribution to the final score is based on their scarcity.
DBotGroupXDRIncidentsTrain clustering model on Cortex XDR incident type.
DBotPredictOutOfTheBoxV2Predict phishing incidents using the out-of-the-box pre-trained model.
DBotPredictPhishingEvaluationDeprecated. This script is deprecated. See https://xsoar.pan.dev/docs/reference/playbooks/d-bot-create-phishing-classifier-v2 for more information.
DBotPredictPhishingWordsPredict text label using a pre-trained machine learning phishing model, and get the most important words used in the classification decision.
DBotPredictTextLabelDeprecated. This script is deprecated. See https://xsoar.pan.dev/docs/reference/playbooks/d-bot-create-phishing-classifier-v2 for more information.
DBotPredictURLPhishingPredict phishing URLs using a pre-trained model.
DBotPreparePhishingDataDeprecated. This script is deprecated. See https://xsoar.pan.dev/docs/reference/playbooks/d-bot-create-phishing-classifier-v2 for more information.
DBotPreProcessTextDataPre-process text data for the machine learning text classifier.
DBotShowClusteringModelInfoShow clustering model information - model summary and incidents in specific cluster.
DBotTrainTextClassifierDeprecated. This script is deprecated. See https://xsoar.pan.dev/docs/reference/playbooks/d-bot-create-phishing-classifier-v2 for more information.
DBotTrainTextClassifierV2Train a machine learning text classifier.
DBotUpdateLogoURLPhishingAdd, remove, or modify logos from the URL Phishing model.
DecodeMimeHeaderDecode MIME base64 headers.
DedupByThis transformer will remove elements of the array that contain an identical combination of values for the keys given.
DeduplicateValuesbyKeyGiven 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.
DefaultIncidentClassifierDeprecated. Classify an incident from mail.
delete_expired_indicator_with_exlusiondeletes expired indicators.
DeleteAndExcludeIndicators
DeleteContentDelete content to keep XSOAR tidy.
DeleteContextDelete 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:
https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.10/Cortex-XSOAR-Administrator-Guide/Automations
DeleteIndicatorRelationshipsThis automation allows to delete a relationship between indicator objects based on the relationship id.
DeleteReportedEmailUse this script to delete a reported phishing email from the mailbox it was reported to
DemistoCreateListCreate a new list.
DemistoGetIncidentTasksByStateDeprecated. Use GetIncidentTasksByState instead.
DemistoLeaveAllInvestigationsDeprecated. No available replacement.
DemistoLinkIncidentsDeprecated. No available replacement.
DemistoLogsBundleDeprecated. No available replacement.
DemistoSendInviteDeprecated. No available replacement.
DemistoUploadFileDeprecated. Use DemistoUploadFile instead.
DemistoUploadFileToIncidentDeprecated. Use the DemistoUploadFileV2 script instead. Copies a file from this incident to the specified incident. The file is uploaded as an attachment to the specified incident’s Summary page, and recorded as an entry in the War Room.
DemistoUploadFileV2Deprecated. Use UploadFile instead.
DemistoVersionReturn the Demisto server version.
DigDNS lookup utility to provide 'A' and 'PTR' record
DisableUserWrapperThis script allows disabling a specified user using one or more of the following integrations: SailPointIdentityIQ, ActiveDirectoryQuery, Okta, MicrosoftGraphUser, and IAM.
displayCloudIndicatorsDisplay the Cloud indicators found in a dynamic-section
DisplayCVEChartScriptDisplay bar chart based on cves count and trending cves count with the different colors.
DisplayEmailHtmlDisplays the original email in HTML format.
DisplayEmailHtmlThreadDynamic-section script for 'Email Threads' layout.
This script renders all email messages with the thread number specified in the "Email Selected Thread" field and outputs them as a single HTML output.
DisplayHTMLDisplay HTML in the War Room.
DisplayHTMLWithImagesDisplay HTML with embedded images.
DisplayIndicatorReputationContentDisplay the indicator context object in markdown format in a dynamic section layout
displaySiteCategoryThis dynamic automation retrieves the category of a website and displays it in the layout.
DisplayTaggedWarroomEntriesDisplay warroom entries in a dynamic section which are tagged with 'report'
displayUtilitiesResultsThis script displays the execution results of the tab's buttons in an HTML table format.
DlpAskFeedbackSends a message via Slack or MS Teams to the user whose activity violated DLP policies and triggered the incident.
DockerHardeningCheckChecks if the Docker container running this script has been hardened according to the recommended settings at: https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.10/Cortex-XSOAR-Administrator-Guide/Docker-Hardening-Guide
DomainExtractAndEnrichResolves a URL or fully qualified domain name (FQDN) and looks up a complete profile of the domain on the DomainTools Iris Enrich API.
DomainExtractAndInvestigateResolves a URL or fully qualified domain name (FQDN) and looks up a complete profile of the domain on the DomainTools Iris Investigate API.
DomainReputationA context script for Domain entities
DomainToolsIrisDetectStatusUpdateUpdates the DomainTools Iris Detect Domain state.
DrawRelatedIncidentsCanvasDraw incidents and indicators on the canvas to map and visualize their connections.
DsSearchQueryArrayCombines an array of queries to as few as possible whilst staying under the maximum term count.
DTThis automation allows the usage of DT scripts within playbooks transformers
DumpJSONDumps a json from context key input, and returns a json object string result
EditServerConfigEdit the server configuration (under settings/troubleshooting). You can either add a new configuration or update and remove an existing one.
EmailAskUserAsk a user a question via email and process the reply directly into the investigation.
EmailAskUserResponseExtract 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.
EmailDomainBlacklistAccepts an array of domains as a block list, and a list of email addresses. The script then filters out any email address whose domain is in the block list. The filtered list will be returned as an array.
EmailDomainSquattingReputationCheck if an email address's domain is trying to squat other domain using Levenshtein distance algorithm.
EmailDomainWhitelistAccepts an array of domains as an allow list, and a list of email addresses. The script then filters out any email address whose domain is not in the allow list. The filtered list will be returned as an array.
emailFieldTriggeredSends email to incident owner when selected field is triggered.
EmailReputationA context script for Email entities.
EmailSLABreachThis is used to complete the Scheduled command if the either/both the users respond in time. The time is configured on the EmailUserSLA.
EncodeToAsciiInput Text Data to Encode as ASCII (Ignores any chars that aren't interpreted as ASCII)
EntryWidgetCoAHandledEntry widget that shows the number of techniques that were already handled by the CoA playbooks.
EntryWidgetCoATechniquesListEntry widget that shows the number of techniques that were not yet handled by the CoA playbooks.
EntryWidgetNumberHostsXDREntry widget that returns the number of hosts in a Cortex XDR incident.
EntryWidgetNumberRegionsXCLOUDEntry widget that returns the number of regions in a Cortex XDR incident.
EntryWidgetNumberResourcesXCLOUDEntry widget that returns the number of resources in a Cortex XDR incident.
EntryWidgetNumberUsersXDREntry widget that returns the number of users that participated in a specified Cortex XDR incident.
EntryWidgetPieAlertsXDREntry widget that returns a pie chart of alerts for a specified Cortex XDR incident by alert severity (low, medium, and high).
EntryWidgetPortBasedRulesEntry widget that returns the number of port based rules found by PAN-OS policy optimizer.
EntryWidgetRegionNameXCLOUDEntry widget that returns the region involved in the alert.
EntryWidgetResourceTypeXCLOUDEntry widget that returns the resource type involved in the alert.
EntryWidgetUnusedApplicationsEntry widget that returns the number of rules with unused applications found by PAN-OS policy optimizer.
EntryWidgetUnusedRulesEntry widget that returns the number of unused rules found by PAN-OS policy. optimizer.
EnumerateRolesThe script will enumerate any provided role names and output the list of users for each role.
EPOFindSystemDeprecated. Use the "McAfe ePO v2 integration command epo-find-system" instead.

Return system info
EsmExampleDeprecated. Example of using McAfee ESM (Nitro) with advanced filters
Etl2PcapReceives an ETL file and converts it to a PCAP file.
ExampleJSScriptThis is only an example script, to showcase how to use and write JavaScript scripts
ExchangeAssignRoleDeprecated. This script is deprecated. Please use the Exchange 2016 Compliance Search integration instead.
ExchangeDeleteMailDeprecated. This script is deprecated. Please use the Exchange 2016 Compliance Search integration instead.
ExchangeSearchMailboxDeprecated. This script is deprecated. Please use the Exchange 2016 Compliance Search integration instead.
ExifReadRead image files metadata and provide Exif tags
ExistsCheck if a given value exists in the context. Will return 'no' for empty empty arrays. To be used mostly with DQ and selectors.
ExpanseAggregateAttributionCIAggregate entries from ServiceNow CMDB into AttributionCI.
ExpanseAggregateAttributionDeviceAggregate entries from multiple sources into AttributionDevice.
ExpanseAggregateAttributionIPAggregate entries from multiple sources into AttributionIP.
ExpanseAggregateAttributionUserAggregate entries from multiple sources into AttributionUser.
ExpanseEnrichAttributionThis script can be used to enrich context generated by ExpanseAggregateAttribution* scripts with additional details
ExpanseEvidenceDynamicSectionDynamic Section script used in Expanse Issue layout to display the Latest Evidence structure.
ExpanseGenerateIssueMapWidgetScriptThis widget script generates a map of the Open Expanse Issue Incidents with provider On Prem.
The map is generated as a static PNG file embedded in Markdown.

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-XSOAR/6.10/Cortex-XSOAR-Administrator-Guide/Automations
ExpansePrintSuggestionsGenerates and prints a report in markdown format containing useful suggestions for the Analyst to attribute an Expanse Issue to an owner.
ExpanseRefreshIssueAssetsScript to refresh tags and attribution reasons of assets inside Expanse Issue. The script should be used inside the Expanse Issue incident context.
ExportAuditLogsToFileUses the Core REST API integration to query the server audit trail logs, and return back a CSV or JSON file.
ExportContextToJSONFileExports the Context for the current Incident to a JSON file in the war room.
ExportIncidentsToCSVThis automation uses the Core REST API Integration to batch export Incidents to CSV and return the resulting CSV file to the war room.
ExportIndicatorsToCSVThis automation uses the Core REST API Integration to batch export Indicators to CSV and return the resulting CSV file to the war room.
ExportMLModelExports an existing ML model to a file.
ExportToCSVExport given array to csv file
ExportToXLSXExports context data to a Microsoft Excel Open XML Spreadsheet (XLSX) file.
ExposeIncidentOwnerExpose the incident owner into IncidentOwner context key
ExtendQueryBasedOnPhishingLabelsA helper script for the DBot Create Phishing Classifier V2 playbook. This script extends the query based on the phishingLabels argument.
ExtFilterAdvanced Filter. It enables you to make filters with complex conditions.
ExtractAttackPatternExtract 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.
ExtractDomainAndFQDNFromUrlAndEmailExtracts domains and FQDNs from URLs and emails.
ExtractDomainFromIOCDomainMatchResExtracts domain and its details from the Chronicle IOC Domain match response.
ExtractDomainFromUrlAndEmailExtract Domain(s) from URL(s) and/or Email(s)
ExtractEmailTransformerExtracts email addresses from the given value.
ExtractEmailV2Verifies that an email address is valid and only returns the address if it is valid.
ExtractFQDNFromUrlAndEmailExtracts FQDNs from URLs and emails.
ExtractHTMLTablesFind 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...
ExtractHyperlinksFromOfficeFilesExtracts hyperlinks from office files. Supported file types are: xlsx, docx, pptx.
ExtractInbetweenExtract a string from an existing string.
ExtractIndicators-CloudLoggingThis script will extract indicators from a given AWS CloudTrail or GCP Logging event.
ExtractIndicatorsFromTextFileExtract 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:
https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.10/Cortex-XSOAR-Administrator-Guide/Automations
ExtractIndicatorsFromWordFileUsed 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:
https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.10/Cortex-XSOAR-Administrator-Guide/Automations
ExtraHopTrackIncidentsLinks an incident investigation back to the ExtraHop Detection that created it.
FailedInstancesExecutes a test for all integration instances available and returns detailed information about succeeded and failed integration instances.
FeedCyCognitoGetAssetEndpointGenerates a deep link to the CyCognito platform using the indicator context.
FeedIntegrationErrorWidgetReturns a table widget of enabled feed integration instances that errors out on indicators fetch.
FeedRelatedIndicatorsWidgetWidget script to view information about the relationship between an indicator, entity and other indicators and connect to indicators, if relevant.