<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic For outbound rules for instances that need access to external APIs in Prisma Cloud Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/prisma-cloud-discussions/for-outbound-rules-for-instances-that-need-access-to-external/m-p/531168#M897</link>
    <description>&lt;P&gt;We use the cloud service AWS.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The following issue has been detected in Prisma Cloud.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;gt; This policy detects security groups where network 0.0.0.0/0 and ::0/0 are used. This policy detects security groups where network 0.0.0.0/0 and ::0/0 are used.&lt;BR /&gt;&amp;gt; Select "outbound rules" and click "edit outbound rules"&lt;BR /&gt;&amp;gt; Locate rules containing 0.0.0.0/0 or ::/0 and delete them by selecting "x" icon&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The ECS assigned to this security group must have access to the Twitter API.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The problem is that the IP of the Twitter API can change.&lt;/P&gt;
&lt;P&gt;If the IP of the Twitter API is assigned to a security group outbound, it will be inaccessible when the IP changes.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have come up with the following solution to this problem.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If ECS tries to access the Twitter API and cannot&lt;BR /&gt;The DNS server is queried for the Twitter IP and the outbound security group is updated.&lt;/P&gt;
&lt;P&gt;However, this method may not be updated in time and may cause errors in high traffic situations.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is there another better solution ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;How do you all respond to such alerts ?&lt;/P&gt;</description>
    <pubDate>Wed, 15 Feb 2023 02:07:19 GMT</pubDate>
    <dc:creator>iwata2023</dc:creator>
    <dc:date>2023-02-15T02:07:19Z</dc:date>
    <item>
      <title>For outbound rules for instances that need access to external APIs</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-cloud-discussions/for-outbound-rules-for-instances-that-need-access-to-external/m-p/531168#M897</link>
      <description>&lt;P&gt;We use the cloud service AWS.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The following issue has been detected in Prisma Cloud.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;gt; This policy detects security groups where network 0.0.0.0/0 and ::0/0 are used. This policy detects security groups where network 0.0.0.0/0 and ::0/0 are used.&lt;BR /&gt;&amp;gt; Select "outbound rules" and click "edit outbound rules"&lt;BR /&gt;&amp;gt; Locate rules containing 0.0.0.0/0 or ::/0 and delete them by selecting "x" icon&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The ECS assigned to this security group must have access to the Twitter API.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The problem is that the IP of the Twitter API can change.&lt;/P&gt;
&lt;P&gt;If the IP of the Twitter API is assigned to a security group outbound, it will be inaccessible when the IP changes.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have come up with the following solution to this problem.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If ECS tries to access the Twitter API and cannot&lt;BR /&gt;The DNS server is queried for the Twitter IP and the outbound security group is updated.&lt;/P&gt;
&lt;P&gt;However, this method may not be updated in time and may cause errors in high traffic situations.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is there another better solution ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;How do you all respond to such alerts ?&lt;/P&gt;</description>
      <pubDate>Wed, 15 Feb 2023 02:07:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-cloud-discussions/for-outbound-rules-for-instances-that-need-access-to-external/m-p/531168#M897</guid>
      <dc:creator>iwata2023</dc:creator>
      <dc:date>2023-02-15T02:07:19Z</dc:date>
    </item>
    <item>
      <title>Re: For outbound rules for instances that need access to external APIs</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-cloud-discussions/for-outbound-rules-for-instances-that-need-access-to-external/m-p/532001#M898</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/273876"&gt;@iwata2023&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Given&lt;/STRONG&gt; twitter's API endpoint IPs are changing and that twitter is assigned a class A, B or C address range,&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Then&lt;/STRONG&gt; why don't you use CIDR notation for the AWS Scecrity Group's outbound rule?&lt;/P&gt;
&lt;P&gt;See&amp;nbsp;&lt;A href="https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing" target="_blank" rel="noopener"&gt;https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;As an example, if you enter 199.167.52.5/32, only one IP address is allowed. If you enter 199.167.52.0/24, it allows all IP addresses within the range of 199.167.52.0 to 199.167.52.255.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In that way, you won't have to detect and remediate twitter API endpoint address(es) in your security group(s).&amp;nbsp; Rather, you trust the range of IP addresses that twitter's API endpoints may occupy.&lt;/P&gt;</description>
      <pubDate>Thu, 23 Feb 2023 13:46:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-cloud-discussions/for-outbound-rules-for-instances-that-need-access-to-external/m-p/532001#M898</guid>
      <dc:creator>TommyHunt</dc:creator>
      <dc:date>2023-02-23T13:46:06Z</dc:date>
    </item>
  </channel>
</rss>

