<?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=Session_Management_Framework</id>
		<title>Session Management Framework - Revision history</title>
		<link rel="self" type="application/atom+xml" href="https://wiki.owasp.org/index.php?action=history&amp;feed=atom&amp;title=Session_Management_Framework"/>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Session_Management_Framework&amp;action=history"/>
		<updated>2026-04-26T02:54:02Z</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=Session_Management_Framework&amp;diff=169620&amp;oldid=prev</id>
		<title>Ari Elias-Bachrach: created a start</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Session_Management_Framework&amp;diff=169620&amp;oldid=prev"/>
				<updated>2014-03-07T03:44:34Z</updated>
		
		<summary type="html">&lt;p&gt;created a start&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;=Session Management Framework=&lt;br /&gt;
==Overview==&lt;br /&gt;
Session management is an important underlying function in modern web applications. Keeping sessions secure is one of the most important things a framework must do to ensure that applications built on that framework do not suffer from security flaws.&lt;br /&gt;
&lt;br /&gt;
==Session Data==&lt;br /&gt;
Session data should be stored server-side and never transmitted to the client unless necessary. The framework should also provide a simple and easy way for the developer to access, add, delete, or modify session data.&lt;br /&gt;
&lt;br /&gt;
==Session ID==&lt;br /&gt;
===Generating===&lt;br /&gt;
The session ID should always be generated by the framework, and no other party should be able to manually select a session ID. The ID should be generated in a crytographically strong fashion. The session ID should always be generated based on random numbers, and it should never be created with any session specific or environment specific data.&lt;br /&gt;
&lt;br /&gt;
===Storage===&lt;br /&gt;
The Session ID should be stored in a cookie which the client then submits to the server with every request. This cookie should have the HTTPONLY and SECURE flags set by default.&lt;br /&gt;
&lt;br /&gt;
The framework should also provide an easy way for the developer to change the name of the session ID cookie to a custom value to avoid fingerprinting. &lt;br /&gt;
&lt;br /&gt;
===Cookie rewriting===&lt;br /&gt;
URL rewriting is not recommended.&lt;br /&gt;
&lt;br /&gt;
==Ending a session==&lt;br /&gt;
The framework should provide a simple method for a developer to remove a session. When that function is called, the session data itself should be purged from server memory, the session ID should no longer be kept as a valid ID, and the cookie should be removed from the client browser.&lt;/div&gt;</summary>
		<author><name>Ari Elias-Bachrach</name></author>	</entry>

	</feed>