<?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>mydailyvowels.com &#187; security testing tips</title>
	<atom:link href="http://mydailyvowels.com/tag/security-testing-tips/feed/" rel="self" type="application/rss+xml" />
	<link>http://mydailyvowels.com</link>
	<description>Journey of sharing fun &#38; knowledge in the QA world!!</description>
	<lastBuildDate>Wed, 04 May 2011 03:12:02 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Lesson 101 : Introduction to Security Testing</title>
		<link>http://mydailyvowels.com/lesson-101-introduction-to-security-testing/</link>
		<comments>http://mydailyvowels.com/lesson-101-introduction-to-security-testing/#comments</comments>
		<pubDate>Fri, 18 Dec 2009 05:20:50 +0000</pubDate>
		<dc:creator>Sachin Srivastava</dc:creator>
				<category><![CDATA[Testing Lessons]]></category>
		<category><![CDATA[security testing tips]]></category>

		<guid isPermaLink="false">http://mydailyvowels.com/?p=97</guid>
		<description><![CDATA[


In broad perspective, security  testing can be divided into six basic concepts: Here is a brief introduction  of them but I would suggest exploring more onto each of them individually.

Availability:    Assuring that for any information system which is there to serve its    purpose, should be available when needed and these information &#38;    communications services are available and maintained for authorized    persons when needed.
Authentication:    Assuring ...]]></description>
			<content:encoded><![CDATA[<address><em><span style="font-family: Times New Roman; font-size: small;"><br />
<a href="http://www.docstoc.com/docs/19677671/Security-Testing-Tips" target="_blank"></a></span></em></address>
<p><img class="aligncenter" title="Security" src="http://farm3.static.flickr.com/2346/2218938901_79112322e9.jpg" alt="" width="500" height="500" /></p>
<p><span style="font-family: Times New Roman; font-size: small;">In broad perspective, security  testing can be divided into six basic concepts: Here is a brief introduction  of them but I would suggest exploring more onto each of them individually.</span></p>
<ul type="DISC">
<li><span style="font-family: Times New Roman; font-size: small;"><strong>Availability</strong>:    Assuring that for any information system which is there to serve its    purpose, should be available when needed and these information &amp;    communications services are available and maintained for authorized    persons when needed.</span></li>
<li><span style="font-family: Times New Roman; font-size: small;"><strong>Authentication</strong>:    Assuring the transaction or communication is happening between two or    more authentic parties. Assuring the validity of any type of originator,    transmission or message.  This also gives confidence that information    is received by a known and validated source.</span></li>
<li><span style="font-family: Times New Roman; font-size: small;"><strong>Authorization</strong>:    Assuring that an intended individual can allow/deny access to a system/service/operation    (e.g. Access control).</span></li>
<li><span style="font-family: Times New Roman; font-size: small;"><strong>Confidentiality</strong>:    Ensuring authorized person or parties only have access to the information    and prevent information disclosure to any party other than the intended    recipients. Often ensured by encoding information using algorithms (cryptography    is one of the common example of that).</span></li>
<li><span style="font-family: Times New Roman; font-size: small;"><strong>Integrity</strong>:    Ensuring received information is preserved successfully with no alteration.</span></li>
<li><span style="font-family: Times New Roman; font-size: small;"><strong>Non-repudiation</strong>:    Ensuring communication or action cannot later be denied </span></li>
</ul>
<p><span style="font-family: Times New Roman; font-size: medium;"><strong>Security Testing Methods</strong>:</span></p>
<p><span style="font-family: Times New Roman; font-size: small;">Basically there are three types  of testing methods which involve various sets of attacks: </span></p>
<p><span style="font-family: Times New Roman; font-size: small;"><strong>1)  Information/system gathering, </strong></span></p>
<p><span style="font-family: Times New Roman; font-size: small;"><strong>2) Logical attack </strong></span></p>
<p><span style="font-family: Times New Roman; font-size: small;"><strong>3) Injection attacks.</strong></span></p>
<p><span style="font-family: Times New Roman; font-size: small;"> Each are used for specific  testing results, however various attacks share the same security concepts,  and are therefore quite similar to one another.</span></p>
<p><span style="font-family: Times New Roman; font-size: small;"><strong>Information gathering (i.e.  system-related) attacks</strong></span></p>
<ul type="DISC">
<li><span style="font-family: Times New Roman; font-size: small;">Client-side source    code analysis</span></li>
<li><span style="font-family: Times New Roman; font-size: small;">Application reconnaissance</span></li>
<li><span style="font-family: Times New Roman; font-size: small;">Error messages analysis</span></li>
<li><span style="font-family: Times New Roman; font-size: small;">Directory traversal</span></li>
</ul>
<p><span style="font-family: Times New Roman; font-size: small;">These methods include various  types of information gathering from a web application/server by means  of source code and error message analysis, exposure of directory structure  or other attacks which results in information exposure. Here they are  in no particular order:</span></p>
<p><span style="font-family: Times New Roman; font-size: small;"><strong>Logical Attacks</strong></span></p>
<ul type="DISC">
<li><span style="font-family: Times New Roman; font-size: small;">Cookie poisoning</span></li>
<li><span style="font-family: Times New Roman; font-size: small;">Parameter tampering</span></li>
<li><span style="font-family: Times New Roman; font-size: small;">Flow bypassing</span></li>
<li><span style="font-family: Times New Roman; font-size: small;">Direct access of    components files</span></li>
<li><span style="font-family: Times New Roman; font-size: small;">Session hijacking</span></li>
<li><span style="font-family: Times New Roman; font-size: small;">Penetration testing</span></li>
<li><span style="font-family: Times New Roman; font-size: small;">Buffer overflow</span></li>
</ul>
<p><span style="font-family: Times New Roman; font-size: small;">These methods may be executed  both manually and via specific tools/scripts and are mainly related  to various logical attacks. Logical attacks are more sophisticated,  and thus, more interesting &amp; challenging to the tester, who needs  to have a good understanding of information technology and specific  knowledge of cookies, POST/GET requests &amp; parameters like that,  etc.</span></p>
<p><span style="font-family: Times New Roman; font-size: small;"><strong>Injection Attacks</strong></span></p>
<ul type="DISC">
<li><span style="font-family: Times New Roman; font-size: small;">SQL injection</span></li>
<li><span style="font-family: Times New Roman; font-size: small;">Cross Site Scripting    (XSS)</span></li>
<li><span style="font-family: Times New Roman; font-size: small;">Scripts injection</span></li>
</ul>
<p><span style="font-family: Times New Roman; font-size: small;">These methods relate to various  scripts &amp; SQL commands injections into web application forms. These  are the most common attacks, yet they are both serious and dangerous.  Detecting such vulnerabilities in the early stages of development can  prevent unnecessary flaws.</span></p>
<p><span style="font-family: Times New Roman; font-size: small;">More on this will come in my  next post.</span></p>
<p><span style="font-family: Times New Roman; font-size: small;">Thanks,</span></p>
<p><span style="font-family: Times New Roman; font-size: small;">Sachin Srivastava.</span></p>
<p><span style="font-family: Times New Roman; font-size: small;">Quality Analyst</span></p>
<p style="text-align: center;"><span style="font-family: Times New Roman; font-size: small;">Dec 17, 2009 Copyright Notice</span></p>
<p style="text-align: center;"><em><span style="font-family: Times New Roman; font-size: small;">This document may be copied in it entirety, or extracts made, if the source is acknowledged.To download a copy of this document, <a href="http://www.docstoc.com/docs/19677671/Security-Testing-Tips" target="_blank">please click here</a></span></em></p>
<p style="text-align: center;"><span style="font-family: Times New Roman; font-size: small;"><a href="http://www.docstoc.com/docs/19677671/Security-Testing-Tips" target="_blank"></a><br />
</span></p>
]]></content:encoded>
			<wfw:commentRss>http://mydailyvowels.com/lesson-101-introduction-to-security-testing/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
	</channel>
</rss>

