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

alibasyaeb — Wed, 03 Aug 2022 19:28:34 GMT

Hi, I've learned 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

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

RPrasadi — Thu, 28 Jul 2022 18:26:05 GMT

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,
Avery

topic Networking runtime policy failed to detect traffic to ec2 meta-data IP address in Prisma Cloud Discussions

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

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