Skip to main content

Palo Alto Cortex XSOAR Post-Installation Health Check.

After Installing Palo Alto Cortex XSOAR, it is recommended to perform a post-installation health check. As per Palo Alto documentation, the following tests has to be performed.

1) Check the Docker Sub-system

  •  /docker_images : Verify that either a list of Docker images or an empty list is returned. Can run this command from the playground.
    cortex xsoar health check jaacostan

  •  !py script="demisto.results('hello world')" : Verify that hello world is returned, if not, there may be issues with your docker installation. Can run this command from the playground.
    cortex xsoar health check jaacostan

  •     sudo docker info : Check for warnings or errors.
    cortex xsoar health check jaacostan

2) Verify Integration Tests

Create an instance of each of the following integrations and test each of these integrations by clicking the Test button in the integration instance. You can also optionally run associated commands in the playground. Sample integration installation of ipinfo is shown below.

palo alto cortex xsoar updates jaacostan
  •     ipinfo
  •     PhishTank
  •     OpenPhish
  •     Rasterize

Also, run !FailedInstances in the playground to test all configured integrations and check outputs to see that there are no errors returned.

cortex xsoar health check jaacostan

3) Run Commands in the Playground

Note that if the above mentioned integrations are not done, then the following commands cannot be executed.

!url url=""

cortex xsoar health check jaacostan

!ip ip=""
cortex xsoar health check jaacostan

!rasterize url=""
!rasterize-email htmlBody="<h1>hello world</h1>"

cortex xsoar health check jaacostan

!Ping address=
cortex xsoar health check jaacostan

4) Run any report and verify that the PDF output resolves correctly.
cortex xsoar health check jaacostan
5) Verify that your content is up to date. 

palo alto cortex xsoar updates jaacostan

6) Verify that you see automation scripts in the Automation section.
7) Verify that you see playbooks in the Playbooks section.
8) Verify that you see dashboard widgets in the My Dashboards section.

Read more posts on Palo Alto Cortex XSOAR here. 👆

PCSAE exam questions


Reference :

Popular posts from this blog

Cisco ASA: Disable SSLv3 and configure TLSv1.2.

For configuring TLS v1.2, the ASA should run software version 9.3(2) or later. In earlier versions of ASA, TLS 1.2 is not supported.If you are running the old version, it's time to upgrade. But before that i will show you the config prior to the change. I am running ASA version 9.6.1 Now ,set the server-version to tlsv1.2, though ASA supports version tlsv1.1, its always better to configure the connection to more secure. Server here in the sense, the ASA will be act as the server and the client will connect to the ASA.     #ssl server-version tlsv1.2 set the client-version to tlsv1.2, if required.     #ssl client-version tlsv1.2 ssl cipher command in ASA offers 5 predefined security levels and an additional custom level.     #ssl cipher tlsv1.2 high we can see the setting of each cipher levels using #show ssl cipher command. Now set the DH group to 24, which is the strongest offered as of now in the ASA.     #ssl dh-group group24 An

How to Install Netmiko on Windows?

Netmiko, developed by kirk Byers is an open source python library  based on Paramiko which simplifies SSH management to network devices and is primarily used for network automation tasks. Installing Netmiko in linux is a matter o f one single command but if you need to use Netmiko in your Windows PC, follow this process. 1) Install the latest version of Python. 2) Install Anaconda, which is an opensource distribution platform that you can install in Windows and other OS's ( 3) From the Anaconda Shell, run “ conda install paramiko ”. 4) From the Anaconda Shell, run “ pip install scp ”. 5) Now Install the Git for Windows. ( . Git is required for downloading and cloning all the Netmiko library files from Github. 6) From Git Bash window, Clone Netmiko using the following command git clone         7) Once the installation is completed, ch

RUST error: linker `link.exe` not found

While compiling Rust program in a windows environment, you may encounter the error : linker `link.exe` not found. This is because of the absence of the C++ build tools in your machine. For compiling Rust programs successfully, one of the prerequisites is the installation of the Build Tools for Visual Studio 2019.   Download the Visual Studio 2019 Build tools from the Microsoft website. After the download, while installing the Build tools, make sure that you install the required components (highlighted in Yellow) This will download around 1.2GB of required files. Once everything is successfully installed, reboot and re-run your rust program and it will compile successfully.   Read More on RUST Hello World Rust Program : Code explained RUST Cargo Package Manager Explained Data Representation in Rust.

What is a Gratuitous ARP? How is it used in Network attacks?

Many of us encountered the word "Gratuitous" while exploring the network topic on ARP, The Address Resolution Protocol. Before explaining Gratuitous ARP, here is a quick review on how ARP works. ARP provides IP communication within a Layer 2 broadcast domain by mapping an IP address to a MAC address.For example, Host B wants to send information to Host A but does not have the MAC address of Host A in its ARP cache. Host B shoots a broadcast message for all hosts within the broadcast domain to obtain the MAC address associated with the IP address of Host A. All hosts within the same broadcast domain receive the ARP request, and Host A responds with its MAC address. We can see the ARP entries on our computers by entering the command arp -a . So, back to the topic on what is a Gratuitous reply, here is a better explanation. Gratuitous arp is when a device will send an ARP packet that is not a response to a request. Ideally a gratuitous ARP request is an ARP request packe

Recovery Procedure: Alcatel-Lucent Omni-Switch not booting AOS: Going to Mini-boot prompt.

Problem: Switch not booting AOS; Going to Mini-boot prompt. Model: Alcatel-Lucent OS6850 [Note:The same procedure might be applicable for different models of Omni-Switches, However, for this illustration, i have used OS-6850 ] Reason: This problem may occurs due to corrupt AOS image files or misconfigured boot parameters. Hence switch cannot boot the images properly and will go to Mini-boot prompt.  Work Around: [Note: This zmodem procedure consumes a lot to time to finish the process.] 1.) Power off your OS6850 2.) When you switched it back on, stop it before the Miniboot (there is some counter counting down from 4). Press Enter to break. 3.) You will have the following prompt " => " 4.) Enter " setenv baudrate 115200 ”. Increasing baudrate helps to increase the data transfer speed using zmodem. 5.) Enter " saveenv " 6.) Enter " boot " 7.) The switch should run now in baud rate 115200 (so you have to change your clients ter