
Before you begin
- Labs create a Google Cloud project and resources for a fixed time
- Labs have a time limit and no pause feature. If you end the lab, you'll have to restart from the beginning.
- On the top left of your screen, click Start lab to begin
This lab was developed with our partner, Palo Alto Networks. Your personal information may be shared with Palo Alto Networks, the lab sponsor, if you have opted in to receive product updates, announcements, and offers in your Account Profile.
This lab provides an introduction to Cortex XSOAR Threat Intelligence Management. You will get hands-on experience using XSOAR to investigate and hunt real-world threats. You will also use XSOAR to consolidate threat intelligence feeds and enrich indicators of compromise (IoC) to streamline incident response workflows.
Palo Alto Networks has partnered with Google Cloud to host this lab. As part of the lab you will be given access to a Cortex XSOAR threat intel management instance.
In this lab, you will perform the following tasks:
To complete the lab, you will need:≈
Read these instructions. Labs are timed and you cannot pause them. The timer, which starts when you click Start Lab, shows how long Google Cloud resources are made available to you.
This hands-on lab lets you do the lab activities in a real cloud environment, not in a simulation or demo environment. It does so by giving you new, temporary credentials you use to sign in and access Google Cloud for the duration of the lab.
To complete this lab, you need:
Click the Start Lab button. If you need to pay for the lab, a dialog opens for you to select your payment method. On the left is the Lab Details pane with the following:
Click Open Google Cloud console (or right-click and select Open Link in Incognito Window if you are running the Chrome browser).
The lab spins up resources, and then opens another tab that shows the Sign in page.
Tip: Arrange the tabs in separate windows, side-by-side.
If necessary, copy the Username below and paste it into the Sign in dialog.
You can also find the Username in the Lab Details pane.
Click Next.
Copy the Password below and paste it into the Welcome dialog.
You can also find the Password in the Lab Details pane.
Click Next.
Click through the subsequent pages:
After a few moments, the Google Cloud console opens in this tab.
In this task, review the XSOAR marketplace and integrations. The marketplace is a storefront for discovering and exchanging prebuilt SOAR content packs, including integrations, playbooks, dashboards, and subscription services.
In this step, familarize yourself with to the XSOAR marketplace and content packs.
Access the XSOAR console.
Key | Value |
---|---|
Console | |
Username | |
Password |
Go to Marketplace → Browse.
Check on Show installed to view the installed marketplace integrations.
Search for the Generic Export Indicators Service
content pack.
Click through the tabs to view more details about the content pack.
In this step, review the Feodo marketplace integration. This integration provides a list of malicious IP addresses from the Feodo Tracker.
Go to Settings → Integrations.
Search for the Feodo
marketplace integration.
Click the gear icon to view the Instance settings of the Feodo Tracker IP Blocklist Feed.
Click Cancel to exit from the integration.
In this task, review the dashboards within XSOAR along with the Threat Intel user interface. Then, learn how to associate indicators from 3rd party integrations with security incidents.
In this step, review Cortex XSOAR's Threat Intel Management (TIM) dashboard. Dashboards provide real-time visualization and analysis of security operations data, enabling comprehensive monitoring and decision-making.
Go to Dashboard & Reports → Threat Intel Management.
Set the Date Range to All times
.
Search for indicators from Palo Alto Networks Unit 42 Threat Resarch team.
(Optional) Explore more into the TIM dashboard by clicking into any of the tiles.
In this step, review the Threat Intel user inteface within Cortex XSOAR. This interface allows you to view critical threat intel information, including the state, type, & reputation of indicators.
In XSOAR, navigate to Threat Intel.
Search for indicators from Unit 42 with the tag intrusion-set
.
Click any of the Indicators to perform further investigation.
Use XSOAR's CLI to associate an indicator from the Feodo integration with a security incident. The XSOAR CLI enables you to run commands to perform different tasks.
In Threat Intel, search for malicious indicators from the Feodo integration.
Select the indicator with the IP Value 146.70.149.32
.
Under Related Incidents, you should see no related incidents for the indicator.
In the XSOAR CLI, associate the indicator with a security incident.
associateIndicatorsToIncident
command associates the indicator _146.70.149.32_ with Incident ID 1
Press enter
to execute the command.
When prompted, click Yes, execute in playground.
You will be redirected to the Playground War Room.
Within the playground, verify the command was executed successfully.
Go to Threat Intel and search for the indicator.
Select the 146.70.149.32
indicator.
Under Related Incidents verify the indicator has been associated with the incident ID 1
.
In this task, familiarize yourself with XSOAR playbooks. Playbooks enable you to automate security processes for consistent and fast response to various events.
Review the playbooks for XSOAR Threat Intel Management (TIM).
In XSOAR, go to Playbooks.
Enter TIM
to search for the Threat Intelligence Management playbooks.
Select the TIM-Automated Indicator Processing Against Business Partners IP List playbook.
Familiarize yourself with the playbook. It will be used to orchestrate response for an incident later in the lab.
In this step, review how XSOAR playbooks automate and standardize security incident response procedures.
Go to Incidents and select the incident #1
.
Under Indicators, the indicator from the previous step is now associated with this incident.
Click the Work Plan tab.
Click the Playbook Triggered task to view the trigger for the playbook.
Go to Settings → Advanced → Lists.
Click BusinessPartnersIPListName to view the list.
Go to Threat Intel and enter the following query to search for all indicators with the business_partner
tag.
(Optional) Click any of the indicators to more information about it.
In this task, use XSOAR to automatically populate an External Dynamic List (EDL). EDLs are used by firewalls to allow or block traffic from specific resources and destinations.
In this step, create an EDL. This EDL can be ingested into a firewall appliances, including all of Palo Alto Networks NGFWs.
Go to Settings → Integrations.
Enter the following into the search bar.
Click Add Instance next to the Generic Export Indicators Service.
Generic Export Indicators Service
integration provides an end device (i.e. NGFW) with a list of indicators as a service.
Configure the instance as follows:
Key | Value |
---|---|
Name | Workshop_EDL |
Update list on demand only | Check ON |
Outbound Format | PAN-OS (text) |
List Size | 2500 |
Refresh Rate | 5 minutes |
Listen Port | 8443 |
Click Test to verify the configuration. Once successful, click Save & exit.
In this step, create a custom report. Although XSOAR provides broad reporting capabilities natively, it also allows you to tailor reports to suit your specific needs.
Go to Settings → Objects Setup → Threat Intel Reports → Types.
Click + New Type to create a new Threat Intel Report.
Configure the new report as follows.
Key | Value |
---|---|
Name | Threat Intel Report Demo |
Layout | Threat Intel Demo Report |
Click Save to create the report.
In this step, use XSOAR TIM to respond to a Log4j security incident. Specifically, use a playbook to retrieve security articles on Log4j and populate the Threat Intel Report created in the previous step.
Go to Incidents.
Select the incident Log4j: Block Threats and Generate Report
.
Click Work Plan:
→ Review the tasks under the Collect and Extract Indicators process.
Open the Tag IP Indicators task:
→ Review what the task does with the collected indicators.
CVE-2021-44228
& log4j
Open the Should we continue blocking indicators? task:
→ Under Complete Task select Yes
→ Click Mark Completed
send-email
integration has not been configured.
Yes
is selected before continuing! By selecting Yes
, you are telling XSOAR to continue blocking the indicators.
Open the Which EDL should we use? task:
→ Copy and paste the EDL URL below into the field.
→ Click Submit Answers
The playbook should complete by generating the custom Threat Intel report and closing the incident.
Verify the incident was closed by the Work Plan, then review the custom Threat Intel Report.
Go to Incidents and open the Log4j
incident.
Within Incident Info, the incident should listed as closed.
Click the EDL URL
Go to Threat Intel → Threat Intel Reports.
Click report #2.
The Threat Intel report contains a summary of the Log4j threat and indicators processed and blocked by the playbook that was executed.
In this lab you learned to use Cortex XSOAR Threat Intel Management. You also learned how to manage customizable Threat Intel pages, associate indicators to incidents, and process indicators against business/partner addresses using playbooks and EDLs.
To learn more, check out the following resources:
...helps you make the most of Google Cloud technologies. Our classes include technical skills and best practices to help you get up to speed quickly and continue your learning journey. We offer fundamental to advanced level training, with on-demand, live, and virtual options to suit your busy schedule. Certifications help you validate and prove your skill and expertise in Google Cloud technologies.
Manual Last Updated August 11, 2024
Lab Last Tested August 11, 2024
Copyright 2025 Google LLC. All rights reserved. Google and the Google logo are trademarks of Google LLC. All other company and product names may be trademarks of the respective companies with which they are associated.
This content is not currently available
We will notify you via email when it becomes available
Great!
We will contact you via email if it becomes available
One lab at a time
Confirm to end all existing labs and start this one