<?xml version="1.0" encoding="UTF-8"?><!-- generator="WordPress/2.8.5" -->
<rss version="0.92">
<channel>
	<title>Secure By Default</title>
	<link>http://www.securebydefault.info</link>
	<description>Designing, building and testing software for better security</description>
	<lastBuildDate>Tue, 10 Nov 2009 12:24:51 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>HTTP Fingerprinting tool</title>
		<description><![CDATA[A promising HTTP fingerprinting tool: http://useofwords.blogspot.com/2009/11/introducing-htrosbif.html
]]></description>
		<link>http://www.securebydefault.info/2009/11/10/http-fingerprinting-tool/</link>
			</item>
	<item>
		<title>Security Gap Analysis of Struts2</title>
		<description><![CDATA[http://www.owasp.org/images/b/be/A_Gap_Analysis_of_Application_Security_in_Struts2.pdf
]]></description>
		<link>http://www.securebydefault.info/2009/05/11/security-gap-analysis-of-struts2/</link>
			</item>
	<item>
		<title>PCI scoring contradiction</title>
		<description><![CDATA[Risk ratings in a PCI security assessment are directly based on CVSS v2 scores, here&#8217;s an extract from CVSS v2 scoring guide:
SCORING TIP #2: When scoring a vulnerability, consider the direct impact to the target host only. For example, consider a cross-site scripting vulnerability: the impact to a user&#8217;s system could be much greater than [...]]]></description>
		<link>http://www.securebydefault.info/2009/04/20/pci-scoring-contradiction/</link>
			</item>
	<item>
		<title>Digg like security news site</title>
		<description><![CDATA[Steve at Mandalorian has created a Diggesque website for security news.  Looks spanky.
http://news.mandalorian.com/
]]></description>
		<link>http://www.securebydefault.info/2008/09/09/digg-like-security-news-site/</link>
			</item>
	<item>
		<title>Seam Remoting&#8217;s default allow</title>
		<description><![CDATA[Stumbled on another difference in approach between security types and developer types in the Seam remoting functionality.
Remoting makes it a doddle to easily access your Seam server side beans on the client side&#8230; including domain objects.  E.g. if you had a server side bean called User.java:

@Entity
public class User {
    private String [...]]]></description>
		<link>http://www.securebydefault.info/2008/09/08/seam-remotings-default-allow/</link>
			</item>
	<item>
		<title>Integrating security into QA testing</title>
		<description><![CDATA[I wrote about this some time ago.

Fortify are now doing a webinar on this topic.
]]></description>
		<link>http://www.securebydefault.info/2008/02/18/integrating-security-into-qa-testing/</link>
			</item>
	<item>
		<title>Security Testing with Watij</title>
		<description><![CDATA[Watij is a tool designed for functional web testing. It&#8217;s effectively a Java API which drives an instance of Internet Explorer. You can then use your favourite unit testing framework to structure tests and make assertions of the results. Like similar functional testing tools, watij can be used to script security defects in web applications. [...]]]></description>
		<link>http://www.securebydefault.info/2008/02/15/testing-with-watij/</link>
			</item>
	<item>
		<title>Defining security requirements</title>
		<description><![CDATA[The vast majority of security assessments I&#8217;ve worked on have used &#8220;best practice&#8221; to define the security requirements of the application under test.  Clients are content to rely on security assessment firms to decide what should and shouldn&#8217;t be tested, and this is usually OK for bug hunting.  But apart from the well known [...]]]></description>
		<link>http://www.securebydefault.info/2008/01/12/defining-security-requirements/</link>
			</item>
</channel>
</rss>
