<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://wiki.owasp.org/index.php?action=history&amp;feed=atom&amp;title=User_talk%3AJamie_Fisher</id>
		<title>User talk:Jamie Fisher - Revision history</title>
		<link rel="self" type="application/atom+xml" href="https://wiki.owasp.org/index.php?action=history&amp;feed=atom&amp;title=User_talk%3AJamie_Fisher"/>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User_talk:Jamie_Fisher&amp;action=history"/>
		<updated>2026-04-13T00:58:14Z</updated>
		<subtitle>Revision history for this page on the wiki</subtitle>
		<generator>MediaWiki 1.27.2</generator>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=User_talk:Jamie_Fisher&amp;diff=21629&amp;oldid=prev</id>
		<title>Jamie Fisher: New page: The intention of the OWASP Application Security Requirements project is to assemble a comprehensive list of generic (document) application security requirements that could be used in most ...</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User_talk:Jamie_Fisher&amp;diff=21629&amp;oldid=prev"/>
				<updated>2007-09-10T13:41:37Z</updated>
		
		<summary type="html">&lt;p&gt;New page: The intention of the OWASP Application Security Requirements project is to assemble a comprehensive list of generic (document) application security requirements that could be used in most ...&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;The intention of the OWASP Application Security Requirements project is to assemble a comprehensive list of generic (document) application security requirements that could be used in most projects.&lt;br /&gt;
&lt;br /&gt;
The output of the guide is intended to help all involved in application security, whether its project management, risk assessment, development, testing, etc.&lt;br /&gt;
&lt;br /&gt;
The reason for this project is that while security requirements are sometimes captured well and defined clearly, I feel there are other times when they may not, for any number of reasons.&lt;br /&gt;
&lt;br /&gt;
OWASP believe that clearly articulating an application security requirements guide detailing both high-level and specific requirements is the best way to ensure that a strong, robust yet workable guide can become default in all aspects of application security.&lt;/div&gt;</summary>
		<author><name>Jamie Fisher</name></author>	</entry>

	</feed>