Unable to get container defender to detect denied IP address on host

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

Unable to get container defender to detect denied IP address on host

L2 Linker

For some reason I am unable to see any events being generated for denied IP addresses when running a container defender on one of our hosts.

 

Did the following:

  • installed a container defender on a linux host.
  • created a host policy that targets the host where the container defender runs.
  • Added google dns (8.8.8.8) to list of denied IP addresses in the host policy.
  • Tried to run ping/curl against that IP address.

Based on the above I expected to see host audit events alerting me to the denied IP address under Admin->Compute->Monitor->Events. But there is no activity. 

 

If I do the exact same steps, but instead of adding an IP i add a port (e.g. 80,443) to the denied ports list, then I start to see activity in Monitor->Events immediately. So looks like the defender is able to detect some things from the host, but not IP connectivity for some reason.

 

Anybody have an idea of what is going on? And perhaps how to debug the issue? Or is there something fundamental I don't understand with host protection and container defenders.

 

 

 

But for some reason I don't see any events/alerts being generated when I try to ping or curl an IP that

3 REPLIES 3

L3 Networker

Hi JensWegar,

 

To block dns at the host level, please install host defender on your linux host, and create a host policy. 

 

Here is the documentation of runtime defense for hosts:

https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-compute/runtime_defense/run...

 

And to install host defender please refer to the following documentation:

https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-compute/install/install_def...

 

Regards,

Umer Sheikh | Technical Support Engineer - Prisma Cloud Compute | PCCSE, AWS - Associate Architect

Thanks for your reply, USheikh. My understanding of the container defender vs host defender is that the container defender does everything that the host defender does, so if a host runs the docker daemon then one should install a container defender (https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-compute/install/defender_ty...). But based on your answer, do I have to install both a container defender AND host defender to get full protection on the host?

L3 Networker

Hi JensWegar,

 

Yes, they are very similar. The key difference is host protection is more geared towards the system services/apps that reside on the hosts - typically they need to be systemd services

 

Regards,

Umer Sheikh | Technical Support Engineer - Prisma Cloud Compute | PCCSE, AWS - Associate Architect
  • 1381 Views
  • 3 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!