Networking runtime policy failed to detect traffic to ec2 meta-data IP address

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

Networking runtime policy failed to detect traffic to ec2 meta-data IP address

L0 Member

Hi, I've learned Prisma Cloud in the past couple of weeks, and I have an issue with the networking runtime policy that I've been configured. It can't detect traffic to EC2 meta-data IP address whether using alert or block. But when I'm using host runtime policy, it detects the traffic to that address. Any idea what can be done to solve this issue? thanks


L4 Transporter

Greetings Alibasyaeb,
I hope that this message finds you well! With the question you have posed I am going to assume that the original networking runtime policy that you configured is at the container level and that the runtime rule using the host runtime policy is the one that is working and allowing the EC2 metadata IP address to be ingested. Please let me know if I have assumed incorrectly but, if this is the case, I think that the console behavior that you are experiencing is a result of the relative scope of how the console correlates the rule to the traffic ingested from the defenders based on the resources of the scope being at either the container level or the host level. Hopefully this helps you.

Kind Regards,

  • 1 replies
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!