<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Fri, 24 May 2013 21:28:59 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Christian Wenz's Blog: SANS Top-20 Internet Security Attack Targets (2006 Annual Update)]]></title>
      <guid>http://www.phpdeveloper.org/news/6772</guid>
      <link>http://www.phpdeveloper.org/news/6772</link>
      <description><![CDATA[<p>
In a new post on his blog, <i>Christian Wenz</i> mentions <a href="http://www.hauser-wenz.de/s9y/index.php?/archives/217-SANS-Top-20-Internet-Security-Attack-Targets-2006-Annual-Update.html">the latest results</a> of the SANS Institute's <a href="http://www.sans.org/top20/">Top 20 Internet Security Attack Targets list</a> which both includes a new entry ("Users") and several mentions of PHP and PHP-related applications.
</p>
<blockquote>
Of course you can debate how such a Top list came together and what the real value behind that is, but there are two specific points in this year's list that I found quite interesting.
</blockquote>
<p>
There's two targets for the PHP community to worry about - sysadmin/hosting and things developers need to keep in mind. Items on these lists include:
<ul>
<li>Always test and deploy patches and new versions of PHP as they are released
<li>Use Intrusion Prevention/Detection Systems to block/alert on malicious HTTP requests. Consider using Apache's mod_security to block known PHP attacks
<li>If you use PHP, migrate your application to PHP 5.2 as a matter of urgency.
<li>Encode all output using htmlentities() or a similar mechanism to avoid XSS attacks
</ul>
You can check out the full information over on <a href="http://www.sans.org/top20/">the SANS Institute website</a>.
</p>]]></description>
      <pubDate>Mon, 27 Nov 2006 10:03:00 -0600</pubDate>
    </item>
  </channel>
</rss>
