<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>BlogSecurity &#187; Reflections</title>
	<atom:link href="http://blogsecurity.net/category/reflections/feed" rel="self" type="application/rss+xml" />
	<link>http://blogsecurity.net</link>
	<description>Always something worth reading...</description>
	<lastBuildDate>Mon, 22 Feb 2010 21:41:28 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>3 Tips to Avoid Dangerous Themes and Plugins</title>
		<link>http://blogsecurity.net/wordpress/3-tips-to-avoid-dangerous-themes-and-plugins</link>
		<comments>http://blogsecurity.net/wordpress/3-tips-to-avoid-dangerous-themes-and-plugins#comments</comments>
		<pubDate>Tue, 10 Feb 2009 02:10:19 +0000</pubDate>
		<dc:creator>DK</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[Reflections]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://blogsecurity.net/?p=413</guid>
		<description><![CDATA[We all love how easy it is to install plugins and themes but how do we know there is no hidden jack in the box waiting to pop out? Viruses, worms and backdoors could be embedded into any theme or plugin and uploaded to the Internet for public consumption.
Here are three easy to use ideas [...]]]></description>
		<wfw:commentRss>http://blogsecurity.net/wordpress/3-tips-to-avoid-dangerous-themes-and-plugins/feed</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>Are Political Blogs More Likely to Get Hacked?</title>
		<link>http://blogsecurity.net/reflections/are-political-blogs-more-likely-to-get-hacked</link>
		<comments>http://blogsecurity.net/reflections/are-political-blogs-more-likely-to-get-hacked#comments</comments>
		<pubDate>Tue, 27 Jan 2009 00:14:19 +0000</pubDate>
		<dc:creator>DK</dc:creator>
				<category><![CDATA[Reflections]]></category>
		<category><![CDATA[hacked]]></category>
		<category><![CDATA[political]]></category>
		<category><![CDATA[web defacement]]></category>

		<guid isPermaLink="false">http://blogsecurity.net/?p=343</guid>
		<description><![CDATA[
A website defacement is an attack on a website that changes the visual appearance of the site. These are typically the work of system crackers, who break into a web server and replace the hosted website with one of their own. &#8211; wikipedia


Web site defacements stretch back to the birth of the Internet and continue [...]]]></description>
		<wfw:commentRss>http://blogsecurity.net/reflections/are-political-blogs-more-likely-to-get-hacked/feed</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>DNS dot DDoS Attack targetting the Internet</title>
		<link>http://blogsecurity.net/reflections/dns-dot-ddos-attack-targetting-the-internet</link>
		<comments>http://blogsecurity.net/reflections/dns-dot-ddos-attack-targetting-the-internet#comments</comments>
		<pubDate>Tue, 20 Jan 2009 10:47:04 +0000</pubDate>
		<dc:creator>DK</dc:creator>
				<category><![CDATA[Reflections]]></category>

		<guid isPermaLink="false">http://blogsecurity.net/?p=323</guid>
		<description><![CDATA[
I was running tcpdump earlier this week when I noticed some odd entries queries to BlogSecurity&#8217;s DNS servers:


$ sudo tcpdump port 53
10:35:29.560870 IP 69.50.142.110.50928 > blogsecurity.domain:  43135+ NS? . (17)
10:35:29.561302 IP blogsecurity.domain > 69.50.142.110.50928:  43135- 13/0/14 NS C.ROOT-SERVERS.NET.,[&#124;domain]
10:35:31.037729 IP 76.9.16.171.10435 > blogsecurity.domain:  58781+ NS? . (17)
10:35:31.038201 IP blogsecurity.domain > 76.9.16.171.10435:  58781- [...]]]></description>
		<wfw:commentRss>http://blogsecurity.net/reflections/dns-dot-ddos-attack-targetting-the-internet/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Acunetix Advanced Web Vulnerability Scanner Review</title>
		<link>http://blogsecurity.net/reflections/acunetix-advanced-web-vulnerability-scanner-review</link>
		<comments>http://blogsecurity.net/reflections/acunetix-advanced-web-vulnerability-scanner-review#comments</comments>
		<pubDate>Mon, 18 Aug 2008 23:27:17 +0000</pubDate>
		<dc:creator>DK</dc:creator>
				<category><![CDATA[Reflections]]></category>

		<guid isPermaLink="false">http://blogsecurity.net/?p=262</guid>
		<description><![CDATA[
As some of you may know, our wp-scanner project looks for common WordPress XSS issues but what about testing more advanced web sites and/or CMS (content management systems)?


Acunetix is one of the leading commercial web applicaton vulnerability scanners on the market. The reason I mention it (other then the fact that they are one of [...]]]></description>
		<wfw:commentRss>http://blogsecurity.net/reflections/acunetix-advanced-web-vulnerability-scanner-review/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Identity Theft 101</title>
		<link>http://blogsecurity.net/reflections/identity-theft-101</link>
		<comments>http://blogsecurity.net/reflections/identity-theft-101#comments</comments>
		<pubDate>Tue, 06 May 2008 21:56:31 +0000</pubDate>
		<dc:creator>DK</dc:creator>
				<category><![CDATA[Reflections]]></category>

		<guid isPermaLink="false">http://blogsecurity.net/reflections/identity-theft-101/</guid>
		<description><![CDATA[
I phoned my bank to activate my card the other day. The automated voice required a date of birth and the number of digits in my Mother&#8217;s maiden name. Lets assume an attacker can get this information, lets be realistic, what could really happen?


Lets explore some ideas of what an attacker could do with enough [...]]]></description>
		<wfw:commentRss>http://blogsecurity.net/reflections/identity-theft-101/feed</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Feedburner Awareness API</title>
		<link>http://blogsecurity.net/reflections/feedburner-awareness-api</link>
		<comments>http://blogsecurity.net/reflections/feedburner-awareness-api#comments</comments>
		<pubDate>Thu, 01 May 2008 13:47:16 +0000</pubDate>
		<dc:creator>DK</dc:creator>
				<category><![CDATA[Reflections]]></category>

		<guid isPermaLink="false">http://blogsecurity.net/reflections/feedburner-awareness-api/</guid>
		<description><![CDATA[
Having fun with FeedBurner Awareness API.


The FeedBurner Awareness API (AwAPI) allows publishers of FeedBurner feeds to reuse the detailed traffic statistics we capture for any of their feeds. Third-party applications and web services that consume feeds can leverage this data to provide useful feed awareness statistics to potential subscribers&#8230; &#8211; awarenessapi


In October 07, BlogSecurity released [...]]]></description>
		<wfw:commentRss>http://blogsecurity.net/reflections/feedburner-awareness-api/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Is Gravatar Secure to Use?</title>
		<link>http://blogsecurity.net/reflections/gravatar-secure-to-use</link>
		<comments>http://blogsecurity.net/reflections/gravatar-secure-to-use#comments</comments>
		<pubDate>Tue, 29 Apr 2008 09:33:13 +0000</pubDate>
		<dc:creator>DK</dc:creator>
				<category><![CDATA[Reflections]]></category>

		<guid isPermaLink="false">http://blogsecurity.net/reflections/gravatar-secure-to-use/</guid>
		<description><![CDATA[
I really love the Gravatar concept. Its simple, useful, powerful and centrally managed, but how secure is it to use on a blog or service?


Regular users may have already seen that we have implemented Gravatars onto BlogSecurity; so its safe to use then, right?


I made a point on our new BlogSec-News service a couple days [...]]]></description>
		<wfw:commentRss>http://blogsecurity.net/reflections/gravatar-secure-to-use/feed</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>When to Upgrade your Software</title>
		<link>http://blogsecurity.net/reflections/when-to-upgrade-your-software</link>
		<comments>http://blogsecurity.net/reflections/when-to-upgrade-your-software#comments</comments>
		<pubDate>Fri, 11 Apr 2008 11:03:18 +0000</pubDate>
		<dc:creator>DK</dc:creator>
				<category><![CDATA[Reflections]]></category>

		<guid isPermaLink="false">http://blogsecurity.net/reflections/when-to-upgrade-your-software/</guid>
		<description><![CDATA[
We got an interesting comment from Dave today that made me reflect on the question of when to update or upgrade your blog software.


Until you folks on this site tell me I’m not doing the update. WP always has some security issues when its released.


It may seem like a fairly simple question, but when should [...]]]></description>
		<wfw:commentRss>http://blogsecurity.net/reflections/when-to-upgrade-your-software/feed</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Facebook IE Users at Risk</title>
		<link>http://blogsecurity.net/reflections/facebook-ie-users-at-risk</link>
		<comments>http://blogsecurity.net/reflections/facebook-ie-users-at-risk#comments</comments>
		<pubDate>Wed, 06 Feb 2008 09:31:25 +0000</pubDate>
		<dc:creator>DK</dc:creator>
				<category><![CDATA[Reflections]]></category>

		<guid isPermaLink="false">http://blogsecurity.net/reflections/facebook-ie-users-at-risk/</guid>
		<description><![CDATA[
Elazar recently released a buffer overflow proof of concept in Aurigma&#8217;s ImageUploader ActiveX plugin.


This ActiveX control is used by Facebook and I have seen it mentioned that MySpace is affected too. The vulnerability is only present for Internet Explorer users.


This vulnerability will allow an attacker to execute commands on your computer via your browser.


This has [...]]]></description>
		<wfw:commentRss>http://blogsecurity.net/reflections/facebook-ie-users-at-risk/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Failing to prepare</title>
		<link>http://blogsecurity.net/reflections/failing-to-prepare</link>
		<comments>http://blogsecurity.net/reflections/failing-to-prepare#comments</comments>
		<pubDate>Mon, 10 Dec 2007 09:45:12 +0000</pubDate>
		<dc:creator>DK</dc:creator>
				<category><![CDATA[Reflections]]></category>

		<guid isPermaLink="false">http://blogsecurity.net/reflections/failing-to-prepare/</guid>
		<description><![CDATA[It seems that security tips for our software often extend to keep up to date with your software. This strategy alone, means two things:

You can trust everyone everywhere to responsibly disclose vulnerabilities to your vendor;
When a new release is made public, the race is on&#8230; will you upgrade before the attacker diff&#8217;s the packages and [...]]]></description>
		<wfw:commentRss>http://blogsecurity.net/reflections/failing-to-prepare/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
