Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Web-App-Sec
[Top] [All Lists]

Re: best practices

Subject: Re: best practices
Date: Fri, 15 Sep 2006 16:31:10 +0800
hi,
The basic rule of thumb is that never rely on session control
mechanism at the client side such as using javascript because all the
client side implementations are subject to malicious users' control.
Normally server-side invalidation of session ID after a specific
period of idle time  is a recommended practice. The exact length of
this idle time is really subject to the sensitivity and security
requirement of the application.

regards,
Rick Zhong


On 9/15/06, Matteo Nava <ilnava@gmail.com> wrote:
Hi,

Normally in web application, when a user end his session, not logging
out, but simply closing the browser, the session token stay valid
until the session timed out, and so it's potentially reusable.

In my opinion it's recommendable that some kind of a mechanism is
implemented for invalidate the session token when user close the
browser, for example, with a client side javascript code using the
onunload event to invalidate the session token. But I haven't found a
best practices or any other discussion about this problem.

Best Regards,

Matteo Nava

-------------------------------------------------------------------------
Sponsored by: Watchfire

Securing a web application goes far beyond testing the application using
manual processes, or by using automated systems and tools. Watchfire's
"Web Application Security: Automated Scanning or Manual Penetration
Testing?" whitepaper examines a few vulnerability detection methods -
specifically comparing and contrasting manual penetration testing with
automated scanning tools. Download it today!

https://www.watchfire.com/securearea/whitepapers.aspx?id=701500000008Vmm
--------------------------------------------------------------------------



------------------------------------------------------------------------- Sponsored by: Watchfire

Securing a web application goes far beyond testing the application using manual processes, or by using automated systems and tools. Watchfire's "Web Application Security: Automated Scanning or Manual Penetration Testing?" whitepaper examines a few vulnerability detection methods - specifically comparing and contrasting manual penetration testing with automated scanning tools. Download it today!

https://www.watchfire.com/securearea/whitepapers.aspx?id=701500000008Vmm
--------------------------------------------------------------------------

<Prev in Thread] Current Thread [Next in Thread>