<?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: Control android and other smartphones in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/control-android-and-other-smartphones/m-p/4775#M3522</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The iPhone/iPad custom signature is based on a pattern match.&amp;nbsp; It looks for the User-Agent header HTTP requests to contain the string that identifies it as an iPhone/iPad.&amp;nbsp; That header contains the value "iPad" so it's pretty easy to identify.&amp;nbsp; So to answer your question about how to do it for other smart phones, the answer is yes you can use this method, provided you know what the request headers look like.&amp;nbsp; If the request headers, such as the User-Agent header, has an identifiable value (something like say "Android"), then you can plug that in and use it.&amp;nbsp; I don't know what these might be for the various mobile devices, so you might have to do some research on this, or take some packet captures and view them for yourself.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If it helps you, I found this outside link showing a list of user agents for mobile devices:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://en.wikipedia.org/wiki/List_of_user_agents_for_mobile_phones"&gt;http://en.wikipedia.org/wiki/List_of_user_agents_for_mobile_phones&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As far controlling by IP ranges, you can create a policy that has a source of the IP range that you desire, traffic type you desire (e.g., web-browsing) and apply your custom vulnerability profile with your custom signature to that policy.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 28 Jan 2011 16:44:05 GMT</pubDate>
    <dc:creator>spolo</dc:creator>
    <dc:date>2011-01-28T16:44:05Z</dc:date>
    <item>
      <title>Control android and other smartphones</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/control-android-and-other-smartphones/m-p/4774#M3521</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I managed to use the setup for blockin iphone/ipad trafic. &lt;/P&gt;&lt;P&gt;&lt;A class="active_link" href="https://live.paloaltonetworks.com/docs/DOC-1503"&gt;https://live.paloaltonetworks.com/docs/DOC-1503&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Some questions... &lt;/P&gt;&lt;P&gt;How do we do this for other smartphones?&lt;/P&gt;&lt;P&gt;And is it possible to control this with IP range for instance? Or other methods?&lt;/P&gt;&lt;P&gt;Thinking about allowing it on some locations and drop packets on other?&lt;/P&gt;&lt;P&gt;I have not been successful on this yet&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sincerely&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Jan 2011 11:42:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/control-android-and-other-smartphones/m-p/4774#M3521</guid>
      <dc:creator>oddmbjer</dc:creator>
      <dc:date>2011-01-28T11:42:58Z</dc:date>
    </item>
    <item>
      <title>Re: Control android and other smartphones</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/control-android-and-other-smartphones/m-p/4775#M3522</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The iPhone/iPad custom signature is based on a pattern match.&amp;nbsp; It looks for the User-Agent header HTTP requests to contain the string that identifies it as an iPhone/iPad.&amp;nbsp; That header contains the value "iPad" so it's pretty easy to identify.&amp;nbsp; So to answer your question about how to do it for other smart phones, the answer is yes you can use this method, provided you know what the request headers look like.&amp;nbsp; If the request headers, such as the User-Agent header, has an identifiable value (something like say "Android"), then you can plug that in and use it.&amp;nbsp; I don't know what these might be for the various mobile devices, so you might have to do some research on this, or take some packet captures and view them for yourself.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If it helps you, I found this outside link showing a list of user agents for mobile devices:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://en.wikipedia.org/wiki/List_of_user_agents_for_mobile_phones"&gt;http://en.wikipedia.org/wiki/List_of_user_agents_for_mobile_phones&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As far controlling by IP ranges, you can create a policy that has a source of the IP range that you desire, traffic type you desire (e.g., web-browsing) and apply your custom vulnerability profile with your custom signature to that policy.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Jan 2011 16:44:05 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/control-android-and-other-smartphones/m-p/4775#M3522</guid>
      <dc:creator>spolo</dc:creator>
      <dc:date>2011-01-28T16:44:05Z</dc:date>
    </item>
  </channel>
</rss>

