Fix security issues correctly - Revision history

MediaWiki spam cleanup: Reverting to last version not containing links to www.textolocc4t.com

2009-05-27T18:28:10Z

Reverting to last version not containing links to www.textolocc4t.com

Deleted user at 14:56, 22 May 2009

2009-05-22T14:56:07Z

KirstenS at 22:20, 7 April 2009

2009-04-07T22:20:22Z

KirstenS at 18:54, 5 September 2008

2008-09-05T18:54:58Z

Cduffey346: Template conformity

2008-06-08T21:03:04Z

Template conformity

Jeff Williams at 15:06, 14 June 2006

2006-06-14T15:06:08Z

New page

{{Template:Principle}}

{{Template:Stub}}

==Summary==

Once a security issue has been identified, it is important to develop a test for it, and to understand the root cause of the issue. When design patterns are used, it is likely that the security issue is widespread amongst all code bases, so developing the right fix without introducing regressions is essential.

For example, a user has found that they can see another user’s balance by adjusting their cookie. The fix seems to be relatively straightforward, but as the cookie handling code is shared amongst all applications, a change to just one application will trickle through to all other applications. The fix must therefore be tested on all affected applications.

[[Category:Principle]]

@@ Line 1: / Line 1: @@
 {{Template:Principle}}
@@ Line 16: / Line 15: @@
 ===Integration Testing===
-: A user has found that they can see another userâs balance by adjusting their cookie. The fix seems to be relatively straightforward, but as the cookie handling code is shared amongst all applications, a change to just one application will trickle through to all other applications. The fix must therefore be tested on all affected applications.
+: A user has found that they can see another user’s balance by adjusting their cookie. The fix seems to be relatively straightforward, but as the cookie handling code is shared amongst all applications, a change to just one application will trickle through to all other applications. The fix must therefore be tested on all affected applications.

@@ Line 1: / Line 1: @@
 {{Template:Principle}}
@@ Line 15: / Line 16: @@
 ===Integration Testing===
-: A user has found that they can see another user’s balance by adjusting their cookie. The fix seems to be relatively straightforward, but as the cookie handling code is shared amongst all applications, a change to just one application will trickle through to all other applications. The fix must therefore be tested on all affected applications.
+: A user has found that they can see another userâs balance by adjusting their cookie. The fix seems to be relatively straightforward, but as the cookie handling code is shared amongst all applications, a change to just one application will trickle through to all other applications. The fix must therefore be tested on all affected applications.

← Older revision		Revision as of 22:20, 7 April 2009
Line 5:		Line 5:
	<br>		<br>
	[[Category:OWASP ASDR Project]]		[[Category:OWASP ASDR Project]]
−	~~[[ASDR Table of Contents]]__TOC__~~

← Older revision		Revision as of 18:54, 5 September 2008
Line 2:		Line 2:

	{{Template:Stub}}		{{Template:Stub}}
		+
		+	<br>
		+	[[Category:OWASP ASDR Project]]
		+	[[ASDR Table of Contents]]__TOC__
		+

	==Description==		==Description==

@@ Line 3: / Line 3: @@
 {{Template:Stub}}
-==Summary==
+==Description==
 Once a security issue has been identified, it is important to develop a test for it, and to understand the root cause of the issue. When design patterns are used, it is likely that the security issue is widespread amongst all code bases, so developing the right fix without introducing regressions is essential.
-For example, a user has found that they can see another user’s balance by adjusting their cookie. The fix seems to be relatively straightforward, but as the cookie handling code is shared amongst all applications, a change to just one application will trickle through to all other applications. The fix must therefore be tested on all affected applications.
 [[Category:Principle]]