<?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 Blocking traffic initiated from Trusted Zone - AWS in Prisma Access Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/prisma-access-discussions/blocking-traffic-initiated-from-trusted-zone-aws/m-p/566689#M628</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Looking for some guidance before I start going down the wrong route. We use Prisma SASE - Panorama managed. We have an STS VPN Connection (service connection) into our AWS Estate. We have a security policies allowing traffic from Trust to Trust.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In the world of prisma all the mobile users and everything on the other end of the service connection are in the same zone.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;TABLE class="table colsep rowsep  table-striped"&gt;
&lt;TBODY class="tbody"&gt;
&lt;TR class="row rowsep"&gt;
&lt;TD class="entry"&gt;
&lt;DIV&gt;
&lt;DIV class="p"&gt;
&lt;DIV&gt;Trust&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/TD&gt;
&lt;TD class="entry relcol"&gt;
&lt;DIV&gt;
&lt;DIV class="p"&gt;
&lt;DIV&gt;Zone containing all trusted and on-boarded IP addresses, service connections, or mobile users within the corporate network.&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So in this case we allow traffic initiated from mobile users to our AWS estate and given these are stateful sessions the return traffic is allowed also . However I would like to block traffic initiated from the AWS estate to our mobile users , so for a basic example I'm happy for a mobile user to be able to ping a server in AWS , but I don't traffic initiated from the AWS Server to reach mobile users.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;My logic is that in the event a machine is compromised in AWS I don't want a bad actor to be able initiate connections to our mobile users.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In my mind I would just create a deny policy specifying trust as the source and destination and then specify the AWS subnets as the source , is this the correct approach or is there a better way?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you!&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 22 Nov 2023 11:55:55 GMT</pubDate>
    <dc:creator>jbusby</dc:creator>
    <dc:date>2023-11-22T11:55:55Z</dc:date>
    <item>
      <title>Blocking traffic initiated from Trusted Zone - AWS</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-access-discussions/blocking-traffic-initiated-from-trusted-zone-aws/m-p/566689#M628</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Looking for some guidance before I start going down the wrong route. We use Prisma SASE - Panorama managed. We have an STS VPN Connection (service connection) into our AWS Estate. We have a security policies allowing traffic from Trust to Trust.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In the world of prisma all the mobile users and everything on the other end of the service connection are in the same zone.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;TABLE class="table colsep rowsep  table-striped"&gt;
&lt;TBODY class="tbody"&gt;
&lt;TR class="row rowsep"&gt;
&lt;TD class="entry"&gt;
&lt;DIV&gt;
&lt;DIV class="p"&gt;
&lt;DIV&gt;Trust&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/TD&gt;
&lt;TD class="entry relcol"&gt;
&lt;DIV&gt;
&lt;DIV class="p"&gt;
&lt;DIV&gt;Zone containing all trusted and on-boarded IP addresses, service connections, or mobile users within the corporate network.&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So in this case we allow traffic initiated from mobile users to our AWS estate and given these are stateful sessions the return traffic is allowed also . However I would like to block traffic initiated from the AWS estate to our mobile users , so for a basic example I'm happy for a mobile user to be able to ping a server in AWS , but I don't traffic initiated from the AWS Server to reach mobile users.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;My logic is that in the event a machine is compromised in AWS I don't want a bad actor to be able initiate connections to our mobile users.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In my mind I would just create a deny policy specifying trust as the source and destination and then specify the AWS subnets as the source , is this the correct approach or is there a better way?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you!&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 22 Nov 2023 11:55:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-access-discussions/blocking-traffic-initiated-from-trusted-zone-aws/m-p/566689#M628</guid>
      <dc:creator>jbusby</dc:creator>
      <dc:date>2023-11-22T11:55:55Z</dc:date>
    </item>
  </channel>
</rss>

