<?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>JDS Australia &#187; WebInspect</title>
	<atom:link href="http://www.jds.net.au/tag/webinspect/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jds.net.au</link>
	<description>Expert consulting services with HP Software</description>
	<lastBuildDate>Thu, 24 Jun 2010 06:36:44 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Detect malicious HTML/JavaScript payloads with WebInspect (e.g. ASPROX, Gumblar, Income Iframe)</title>
		<link>http://www.jds.net.au/tech-tips/wi-malicious-payloads-checks/</link>
		<comments>http://www.jds.net.au/tech-tips/wi-malicious-payloads-checks/#comments</comments>
		<pubDate>Fri, 22 May 2009 04:18:51 +0000</pubDate>
		<dc:creator>Linden Darling</dc:creator>
				<category><![CDATA[Tech Tips]]></category>
		<category><![CDATA[web security]]></category>
		<category><![CDATA[WebInspect]]></category>

		<guid isPermaLink="false">http://www.jds.net.au/?p=1624</guid>
		<description><![CDATA[JDS Australia has developed a set of Custom Checks for WebInspect that aim to detect malicious HTML/JavaScript related to automated attacks being carried out across the Internet that infect Web Applications. These malicious payloads connect to domains under the control of the attacker that deliver attacks against known vulnerabilities in commonly installed applications (e.g. Adobe [...]]]></description>
		<wfw:commentRss>http://www.jds.net.au/tech-tips/wi-malicious-payloads-checks/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HP Software Trial License Periods</title>
		<link>http://www.jds.net.au/tech-tips/hp-demo-license-duration/</link>
		<comments>http://www.jds.net.au/tech-tips/hp-demo-license-duration/#comments</comments>
		<pubDate>Thu, 08 Jan 2009 04:38:45 +0000</pubDate>
		<dc:creator>Stuart Moncrieff</dc:creator>
				<category><![CDATA[Tech Tips]]></category>
		<category><![CDATA[BAC]]></category>
		<category><![CDATA[HP Diagnostics]]></category>
		<category><![CDATA[licensing]]></category>
		<category><![CDATA[Quality Center]]></category>
		<category><![CDATA[QuickTest Pro]]></category>
		<category><![CDATA[SiteScope]]></category>
		<category><![CDATA[WebInspect]]></category>

		<guid isPermaLink="false">http://www.jds.net.au/?p=731</guid>
		<description><![CDATA[HP software tools all have have different trial licensing periods. This is a short list of the demo license details for the major products.

Functional Testing

QuickTest Pro: 14 days. Single seat license with all default add-ins.
Quality Center: 10 days. 5 concurrent users only.

Performance Testing

LoadRunner: 10 days. 25 vusers with all protocols and all monitors.Note that VuGen [...]]]></description>
		<wfw:commentRss>http://www.jds.net.au/tech-tips/hp-demo-license-duration/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
