<?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: How can Palo Alto protect against JBOSS vulnerability in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/how-can-palo-alto-protect-against-jboss-vulnerability/m-p/14697#M10786</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When you setup your security rule make it as tight as possible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;In this particular case I guess web-browsing would be the proper appid to use (look at &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://apps.paloaltonetworks.com/applipedia/"&gt;http://apps.paloaltonetworks.com/applipedia/&lt;/A&gt;&lt;SPAN&gt; for available appid's unless you have access to a PA-device) along with "application-default" as service (or even better set a manual port/ports for this, such as TCP80), like so:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;appid: web-browsing&lt;/P&gt;&lt;P&gt;service: TCP80&lt;/P&gt;&lt;P&gt;action: allow&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The above is plain SPI (stateful packet inspection, regarding the service option) with the addition of applicationfirewalling (regarding the appid option).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now - for added security you should enable vulnerability protection aswell.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A common setup for vulnprotection is to use following setup:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;critical: block&lt;/P&gt;&lt;P&gt;high: block&lt;/P&gt;&lt;P&gt;medium: block&lt;/P&gt;&lt;P&gt;low: default&lt;/P&gt;&lt;P&gt;informational: default&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can set low and informational to block aswell however default is the recommended in order to lower risk of false-positives (default means that default action (either allow or block) will be applied according to the default specificed by PA themselfs).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;In order to find out if the IDP function of PA-device will be able to spot the vuln you linked to you can search in &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://wwapps.paloaltonetworks.com/ThreatVault/"&gt;http://wwapps.paloaltonetworks.com/ThreatVault/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since your link doesnt have CVE info I can only guess which of the following detectable threats is the one mentioned in your link:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;TABLE id="ListTable"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;P style="width: 20px; display: block; float: left;"&gt;&lt;A href="http://wwapps.paloaltonetworks.com/ThreatVault/Home.aspx/ThreatDetail/34765" target="_blank"&gt;&lt;IMG alt="Detail" src="https://ip1.i.lithium.com/abb187f020892196883a055b61293911f970e420/687474703a2f2f7777617070732e70616c6f616c746f6e6574776f726b732e636f6d2f5468726561745661756c742f436f6e74656e742f496d616765732f44657461696c49636f6e2e676966" title="Detail" /&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;34765&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;JBoss Java Class BeanShellDeployer Directory Traversal Vulnerability&lt;/TD&gt;&lt;TD style="text-transform:capitalize"&gt;high&lt;/TD&gt;&lt;TD&gt;CVE-2006-5750CVE-2010-0738&lt;/TD&gt;&lt;/TR&gt;&lt;TR style="background:none repeat scroll 0% 0% #d6e1e7"&gt;&lt;TD&gt;&lt;P style="width: 20px; display: block; float: left;"&gt;&lt;A href="http://wwapps.paloaltonetworks.com/ThreatVault/Home.aspx/ThreatDetail/34764" target="_blank"&gt;&lt;IMG alt="Detail" src="https://ip1.i.lithium.com/abb187f020892196883a055b61293911f970e420/687474703a2f2f7777617070732e70616c6f616c746f6e6574776f726b732e636f6d2f5468726561745661756c742f436f6e74656e742f496d616765732f44657461696c49636f6e2e676966" title="Detail" /&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;34764&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;JBoss Java Class MainDeployer Directory Traversal Vulnerability&lt;/TD&gt;&lt;TD style="text-transform:capitalize"&gt;high&lt;/TD&gt;&lt;TD&gt;CVE-2006-5750CVE-2010-0738&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P style="width: 20px; display: block; float: left;"&gt;&lt;A href="http://wwapps.paloaltonetworks.com/ThreatVault/Home.aspx/ThreatDetail/34763" target="_blank"&gt;&lt;IMG alt="Detail" src="https://ip1.i.lithium.com/abb187f020892196883a055b61293911f970e420/687474703a2f2f7777617070732e70616c6f616c746f6e6574776f726b732e636f6d2f5468726561745661756c742f436f6e74656e742f496d616765732f44657461696c49636f6e2e676966" title="Detail" /&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;34763&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;JBoss Server 7 Web Management Console War File Deployment&lt;/TD&gt;&lt;TD style="text-transform:capitalize"&gt;medium&lt;/TD&gt;&lt;TD&gt;&lt;BR /&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR style="background:none repeat scroll 0% 0% #d6e1e7"&gt;&lt;TD&gt;&lt;P style="width: 20px; display: block; float: left;"&gt;&lt;A href="http://wwapps.paloaltonetworks.com/ThreatVault/Home.aspx/ThreatDetail/34509" target="_blank"&gt;&lt;IMG alt="Detail" src="https://ip1.i.lithium.com/abb187f020892196883a055b61293911f970e420/687474703a2f2f7777617070732e70616c6f616c746f6e6574776f726b732e636f6d2f5468726561745661756c742f436f6e74656e742f496d616765732f44657461696c49636f6e2e676966" title="Detail" /&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;34509&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;JBoss Java Class Security Bypass Vulnerability&lt;/TD&gt;&lt;TD style="text-transform:capitalize"&gt;high&lt;/TD&gt;&lt;TD&gt;CVE-2010-0738&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P style="width: 20px; display: block; float: left;"&gt;&lt;A href="http://wwapps.paloaltonetworks.com/ThreatVault/Home.aspx/ThreatDetail/33561" target="_blank"&gt;&lt;IMG alt="Detail" src="https://ip1.i.lithium.com/abb187f020892196883a055b61293911f970e420/687474703a2f2f7777617070732e70616c6f616c746f6e6574776f726b732e636f6d2f5468726561745661756c742f436f6e74656e742f496d616765732f44657461696c49636f6e2e676966" title="Detail" /&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;33561&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;JBoss JMX Java Class DeploymentFileRepository Directory Traversal Vulnerability&lt;/TD&gt;&lt;TD style="text-transform:capitalize"&gt;high&lt;/TD&gt;&lt;TD&gt;CVE-2010-0738&lt;/TD&gt;&lt;/TR&gt;&lt;TR style="background:none repeat scroll 0% 0% #d6e1e7"&gt;&lt;TD&gt;&lt;P style="width: 20px; display: block; float: left;"&gt;&lt;A href="http://wwapps.paloaltonetworks.com/ThreatVault/Home.aspx/ThreatDetail/33547" target="_blank"&gt;&lt;IMG alt="Detail" src="https://ip1.i.lithium.com/abb187f020892196883a055b61293911f970e420/687474703a2f2f7777617070732e70616c6f616c746f6e6574776f726b732e636f6d2f5468726561745661756c742f436f6e74656e742f496d616765732f44657461696c49636f6e2e676966" title="Detail" /&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;33547&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;JBoss JMX Console DeploymentFileRepository Directory Traversal Vulnerability&lt;/TD&gt;&lt;TD style="text-transform:capitalize"&gt;high&lt;/TD&gt;&lt;TD&gt;CVE-2010-0738&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P style="width: 20px; display: block; float: left;"&gt;&lt;A href="http://wwapps.paloaltonetworks.com/ThreatVault/Home.aspx/ThreatDetail/33268" target="_blank"&gt;&lt;IMG alt="Detail" src="https://ip1.i.lithium.com/abb187f020892196883a055b61293911f970e420/687474703a2f2f7777617070732e70616c6f616c746f6e6574776f726b732e636f6d2f5468726561745661756c742f436f6e74656e742f496d616765732f44657461696c49636f6e2e676966" title="Detail" /&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;33268&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;JBoss Java Class DeploymentFileRepository Directory Traversal Vulnerability&lt;/TD&gt;&lt;TD style="text-transform:capitalize"&gt;high&lt;/TD&gt;&lt;TD&gt;CVE-2006-5750CVE-2010-0738&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can click on each id to see a more detailed explanation of what the current vuln is about along with references etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then you can take this a few steps further (depending on needs etc).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example only allow identified users to be let through your PA-device (using userid function) or you can allow a particular sourceip (and if connected to internet you can also allow based on country or for that matter block specific countries (note however that geoip isnt foolproof but can be helpful to get rid of most of the bad hosts who tries to connect to your resources).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 23 May 2012 19:18:10 GMT</pubDate>
    <dc:creator>mikand</dc:creator>
    <dc:date>2012-05-23T19:18:10Z</dc:date>
    <item>
      <title>How can Palo Alto protect against JBOSS vulnerability</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/how-can-palo-alto-protect-against-jboss-vulnerability/m-p/14696#M10785</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear all, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we are trying to protect a JBOSS web server against a server default configuration vulnerability. This is described at. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="active_link" href="http://www.articlesbase.com/security-articles/exploitation-and-remediation-of-jboss-application-server-default-configuration-vulnerability-1889469.html"&gt;http://www.articlesbase.com/security-articles/exploitation-and-remediation-of-jboss-application-server-default-configuration-vulnerability-1889469.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How can Palo Alto protect servers against this kind of vulnerability?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Juan Pablo&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 May 2012 10:42:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/how-can-palo-alto-protect-against-jboss-vulnerability/m-p/14696#M10785</guid>
      <dc:creator>COMIP</dc:creator>
      <dc:date>2012-05-23T10:42:22Z</dc:date>
    </item>
    <item>
      <title>Re: How can Palo Alto protect against JBOSS vulnerability</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/how-can-palo-alto-protect-against-jboss-vulnerability/m-p/14697#M10786</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When you setup your security rule make it as tight as possible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;In this particular case I guess web-browsing would be the proper appid to use (look at &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://apps.paloaltonetworks.com/applipedia/"&gt;http://apps.paloaltonetworks.com/applipedia/&lt;/A&gt;&lt;SPAN&gt; for available appid's unless you have access to a PA-device) along with "application-default" as service (or even better set a manual port/ports for this, such as TCP80), like so:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;appid: web-browsing&lt;/P&gt;&lt;P&gt;service: TCP80&lt;/P&gt;&lt;P&gt;action: allow&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The above is plain SPI (stateful packet inspection, regarding the service option) with the addition of applicationfirewalling (regarding the appid option).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now - for added security you should enable vulnerability protection aswell.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A common setup for vulnprotection is to use following setup:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;critical: block&lt;/P&gt;&lt;P&gt;high: block&lt;/P&gt;&lt;P&gt;medium: block&lt;/P&gt;&lt;P&gt;low: default&lt;/P&gt;&lt;P&gt;informational: default&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can set low and informational to block aswell however default is the recommended in order to lower risk of false-positives (default means that default action (either allow or block) will be applied according to the default specificed by PA themselfs).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;In order to find out if the IDP function of PA-device will be able to spot the vuln you linked to you can search in &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://wwapps.paloaltonetworks.com/ThreatVault/"&gt;http://wwapps.paloaltonetworks.com/ThreatVault/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since your link doesnt have CVE info I can only guess which of the following detectable threats is the one mentioned in your link:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;TABLE id="ListTable"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;P style="width: 20px; display: block; float: left;"&gt;&lt;A href="http://wwapps.paloaltonetworks.com/ThreatVault/Home.aspx/ThreatDetail/34765" target="_blank"&gt;&lt;IMG alt="Detail" src="https://ip1.i.lithium.com/abb187f020892196883a055b61293911f970e420/687474703a2f2f7777617070732e70616c6f616c746f6e6574776f726b732e636f6d2f5468726561745661756c742f436f6e74656e742f496d616765732f44657461696c49636f6e2e676966" title="Detail" /&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;34765&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;JBoss Java Class BeanShellDeployer Directory Traversal Vulnerability&lt;/TD&gt;&lt;TD style="text-transform:capitalize"&gt;high&lt;/TD&gt;&lt;TD&gt;CVE-2006-5750CVE-2010-0738&lt;/TD&gt;&lt;/TR&gt;&lt;TR style="background:none repeat scroll 0% 0% #d6e1e7"&gt;&lt;TD&gt;&lt;P style="width: 20px; display: block; float: left;"&gt;&lt;A href="http://wwapps.paloaltonetworks.com/ThreatVault/Home.aspx/ThreatDetail/34764" target="_blank"&gt;&lt;IMG alt="Detail" src="https://ip1.i.lithium.com/abb187f020892196883a055b61293911f970e420/687474703a2f2f7777617070732e70616c6f616c746f6e6574776f726b732e636f6d2f5468726561745661756c742f436f6e74656e742f496d616765732f44657461696c49636f6e2e676966" title="Detail" /&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;34764&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;JBoss Java Class MainDeployer Directory Traversal Vulnerability&lt;/TD&gt;&lt;TD style="text-transform:capitalize"&gt;high&lt;/TD&gt;&lt;TD&gt;CVE-2006-5750CVE-2010-0738&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P style="width: 20px; display: block; float: left;"&gt;&lt;A href="http://wwapps.paloaltonetworks.com/ThreatVault/Home.aspx/ThreatDetail/34763" target="_blank"&gt;&lt;IMG alt="Detail" src="https://ip1.i.lithium.com/abb187f020892196883a055b61293911f970e420/687474703a2f2f7777617070732e70616c6f616c746f6e6574776f726b732e636f6d2f5468726561745661756c742f436f6e74656e742f496d616765732f44657461696c49636f6e2e676966" title="Detail" /&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;34763&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;JBoss Server 7 Web Management Console War File Deployment&lt;/TD&gt;&lt;TD style="text-transform:capitalize"&gt;medium&lt;/TD&gt;&lt;TD&gt;&lt;BR /&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR style="background:none repeat scroll 0% 0% #d6e1e7"&gt;&lt;TD&gt;&lt;P style="width: 20px; display: block; float: left;"&gt;&lt;A href="http://wwapps.paloaltonetworks.com/ThreatVault/Home.aspx/ThreatDetail/34509" target="_blank"&gt;&lt;IMG alt="Detail" src="https://ip1.i.lithium.com/abb187f020892196883a055b61293911f970e420/687474703a2f2f7777617070732e70616c6f616c746f6e6574776f726b732e636f6d2f5468726561745661756c742f436f6e74656e742f496d616765732f44657461696c49636f6e2e676966" title="Detail" /&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;34509&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;JBoss Java Class Security Bypass Vulnerability&lt;/TD&gt;&lt;TD style="text-transform:capitalize"&gt;high&lt;/TD&gt;&lt;TD&gt;CVE-2010-0738&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P style="width: 20px; display: block; float: left;"&gt;&lt;A href="http://wwapps.paloaltonetworks.com/ThreatVault/Home.aspx/ThreatDetail/33561" target="_blank"&gt;&lt;IMG alt="Detail" src="https://ip1.i.lithium.com/abb187f020892196883a055b61293911f970e420/687474703a2f2f7777617070732e70616c6f616c746f6e6574776f726b732e636f6d2f5468726561745661756c742f436f6e74656e742f496d616765732f44657461696c49636f6e2e676966" title="Detail" /&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;33561&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;JBoss JMX Java Class DeploymentFileRepository Directory Traversal Vulnerability&lt;/TD&gt;&lt;TD style="text-transform:capitalize"&gt;high&lt;/TD&gt;&lt;TD&gt;CVE-2010-0738&lt;/TD&gt;&lt;/TR&gt;&lt;TR style="background:none repeat scroll 0% 0% #d6e1e7"&gt;&lt;TD&gt;&lt;P style="width: 20px; display: block; float: left;"&gt;&lt;A href="http://wwapps.paloaltonetworks.com/ThreatVault/Home.aspx/ThreatDetail/33547" target="_blank"&gt;&lt;IMG alt="Detail" src="https://ip1.i.lithium.com/abb187f020892196883a055b61293911f970e420/687474703a2f2f7777617070732e70616c6f616c746f6e6574776f726b732e636f6d2f5468726561745661756c742f436f6e74656e742f496d616765732f44657461696c49636f6e2e676966" title="Detail" /&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;33547&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;JBoss JMX Console DeploymentFileRepository Directory Traversal Vulnerability&lt;/TD&gt;&lt;TD style="text-transform:capitalize"&gt;high&lt;/TD&gt;&lt;TD&gt;CVE-2010-0738&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P style="width: 20px; display: block; float: left;"&gt;&lt;A href="http://wwapps.paloaltonetworks.com/ThreatVault/Home.aspx/ThreatDetail/33268" target="_blank"&gt;&lt;IMG alt="Detail" src="https://ip1.i.lithium.com/abb187f020892196883a055b61293911f970e420/687474703a2f2f7777617070732e70616c6f616c746f6e6574776f726b732e636f6d2f5468726561745661756c742f436f6e74656e742f496d616765732f44657461696c49636f6e2e676966" title="Detail" /&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;33268&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;JBoss Java Class DeploymentFileRepository Directory Traversal Vulnerability&lt;/TD&gt;&lt;TD style="text-transform:capitalize"&gt;high&lt;/TD&gt;&lt;TD&gt;CVE-2006-5750CVE-2010-0738&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can click on each id to see a more detailed explanation of what the current vuln is about along with references etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then you can take this a few steps further (depending on needs etc).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example only allow identified users to be let through your PA-device (using userid function) or you can allow a particular sourceip (and if connected to internet you can also allow based on country or for that matter block specific countries (note however that geoip isnt foolproof but can be helpful to get rid of most of the bad hosts who tries to connect to your resources).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 May 2012 19:18:10 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/how-can-palo-alto-protect-against-jboss-vulnerability/m-p/14697#M10786</guid>
      <dc:creator>mikand</dc:creator>
      <dc:date>2012-05-23T19:18:10Z</dc:date>
    </item>
    <item>
      <title>Re: How can Palo Alto protect against JBOSS vulnerability</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/how-can-palo-alto-protect-against-jboss-vulnerability/m-p/14698#M10787</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mikand, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;good point!!!! thank you very much!!!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Juan Pabo&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 May 2012 13:24:42 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/how-can-palo-alto-protect-against-jboss-vulnerability/m-p/14698#M10787</guid>
      <dc:creator>COMIP</dc:creator>
      <dc:date>2012-05-24T13:24:42Z</dc:date>
    </item>
  </channel>
</rss>

