<?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=AppSecEU08_Security_framework_is_not_in_the_code</id>
		<title>AppSecEU08 Security framework is not in the code - Revision history</title>
		<link rel="self" type="application/atom+xml" href="https://wiki.owasp.org/index.php?action=history&amp;feed=atom&amp;title=AppSecEU08_Security_framework_is_not_in_the_code"/>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=AppSecEU08_Security_framework_is_not_in_the_code&amp;action=history"/>
		<updated>2026-04-26T04:53:19Z</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=AppSecEU08_Security_framework_is_not_in_the_code&amp;diff=29442&amp;oldid=prev</id>
		<title>Sammyrulez: New page: The speech will focus on how a Security management framework effects the life-cycle of a web application and how to put developers and functional analysts in control of a security risk man...</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=AppSecEU08_Security_framework_is_not_in_the_code&amp;diff=29442&amp;oldid=prev"/>
				<updated>2008-05-16T06:31:27Z</updated>
		
		<summary type="html">&lt;p&gt;New page: The speech will focus on how a Security management framework effects the life-cycle of a web application and how to put developers and functional analysts in control of a security risk man...&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;The speech will focus on how a Security management framework effects&lt;br /&gt;
the life-cycle of a web application and how to put developers and&lt;br /&gt;
functional analysts in control of a security risk management&lt;br /&gt;
framework. In the first part there will be a quick overview of what a&lt;br /&gt;
Security management framework is, best practice on how to deal with it&lt;br /&gt;
and the role played in the architectural design phase, the development&lt;br /&gt;
phase, the test phase and the enhancement phase. The second part is&lt;br /&gt;
more about tools and behaviours that could lead to a set of data that&lt;br /&gt;
can be evaluated to fulfill a security risk management in web&lt;br /&gt;
application development. The&lt;br /&gt;
objective is to demonstrate that security management can be plugged in&lt;br /&gt;
in both classical and agile development life-cycle in a unintrusive&lt;br /&gt;
manner.&lt;/div&gt;</summary>
		<author><name>Sammyrulez</name></author>	</entry>

	</feed>