<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<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>Mon, 18 Feb 2008 10:56:25 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<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>
