<?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 Re: Monitoring and Blocking eMail in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/monitoring-and-blocking-email/m-p/22203#M16177</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN&gt;When (currently) logging in to Gmail a POST is made towards &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://accounts.google.com/ServiceLoginAuth"&gt;https://accounts.google.com/ServiceLoginAuth&lt;/A&gt;&lt;SPAN&gt; :&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;POST /ServiceLoginAuth HTTP/1.1&lt;/P&gt;&lt;P&gt;Host: accounts.google.com&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;which in the payload contains (among other things):&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;amp;Email=username%40gmail.com&amp;amp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So I guess that part should be doable.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That is create a custom app that depends on the gmail-base (or whatever) but triggers on http-method=POST and payload contains &amp;amp;Email=(.*)%40domain.ec&amp;amp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Put this custom appid as action=allow (along with url=accounts.google.com). While another security rule acting on url=accounts.google.com (and appid=any) is put directly after the previous allowing security rule as action=deny. This way you should be able to login with &lt;/SPAN&gt;&lt;A class="jive-link-email-small" href="mailto:xxx@domain.ec"&gt;xxx@domain.ec&lt;/A&gt;&lt;SPAN&gt; but not with any other domain (or username without domain).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In order for the above to work you need to have ssl-termination (ssl-decrypt) active.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The risks is that the user might have already been authenticated elsewhere in the google stratosphere and by that perhaps doesnt need to go the route through accounts.google.com. But also if the authentication can be done through GET instead of POST (because then you need expand your custom appid to cover that aswell). I have also no idea how IMAP (that is gmail app in android and such) can be blocked if you wish to block that aswell (the above was verified with firefox running live http header to look into the ssl session).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And as for your second question Im sorry but dont fully understand what you are asking for?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 04 Apr 2013 00:02:02 GMT</pubDate>
    <dc:creator>mikand</dc:creator>
    <dc:date>2013-04-04T00:02:02Z</dc:date>
    <item>
      <title>Monitoring and Blocking eMail</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/monitoring-and-blocking-email/m-p/22202#M16176</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want to know how I can do the following questions:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;1.- How can I block in gmail application the access to all the mails like this &lt;/SPAN&gt;&lt;A class="jive-link-email-small" href="mailto:xxxx@gmail.com"&gt;xxxx@gmail.com&lt;/A&gt;&lt;SPAN&gt;, but allow the access to emalis like this &lt;/SPAN&gt;&lt;A class="jive-link-email-small" href="mailto:xxxx@domain.ec"&gt;xxxx@domain.ec&lt;/A&gt;&lt;SPAN&gt; that also are associated with Gmail.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2.- How to monitor the users who access to public mails and know what are the access account and the destination account of a specific email.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Apr 2013 16:22:50 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/monitoring-and-blocking-email/m-p/22202#M16176</guid>
      <dc:creator>Angel</dc:creator>
      <dc:date>2013-04-03T16:22:50Z</dc:date>
    </item>
    <item>
      <title>Re: Monitoring and Blocking eMail</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/monitoring-and-blocking-email/m-p/22203#M16177</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN&gt;When (currently) logging in to Gmail a POST is made towards &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://accounts.google.com/ServiceLoginAuth"&gt;https://accounts.google.com/ServiceLoginAuth&lt;/A&gt;&lt;SPAN&gt; :&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;POST /ServiceLoginAuth HTTP/1.1&lt;/P&gt;&lt;P&gt;Host: accounts.google.com&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;which in the payload contains (among other things):&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;amp;Email=username%40gmail.com&amp;amp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So I guess that part should be doable.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That is create a custom app that depends on the gmail-base (or whatever) but triggers on http-method=POST and payload contains &amp;amp;Email=(.*)%40domain.ec&amp;amp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Put this custom appid as action=allow (along with url=accounts.google.com). While another security rule acting on url=accounts.google.com (and appid=any) is put directly after the previous allowing security rule as action=deny. This way you should be able to login with &lt;/SPAN&gt;&lt;A class="jive-link-email-small" href="mailto:xxx@domain.ec"&gt;xxx@domain.ec&lt;/A&gt;&lt;SPAN&gt; but not with any other domain (or username without domain).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In order for the above to work you need to have ssl-termination (ssl-decrypt) active.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The risks is that the user might have already been authenticated elsewhere in the google stratosphere and by that perhaps doesnt need to go the route through accounts.google.com. But also if the authentication can be done through GET instead of POST (because then you need expand your custom appid to cover that aswell). I have also no idea how IMAP (that is gmail app in android and such) can be blocked if you wish to block that aswell (the above was verified with firefox running live http header to look into the ssl session).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And as for your second question Im sorry but dont fully understand what you are asking for?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Apr 2013 00:02:02 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/monitoring-and-blocking-email/m-p/22203#M16177</guid>
      <dc:creator>mikand</dc:creator>
      <dc:date>2013-04-04T00:02:02Z</dc:date>
    </item>
  </channel>
</rss>

