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: Login credentials and session id security

Subject: Re: Login credentials and session id security
Date: Wed, 6 Jun 2007 18:58:48 -0400
If you are that concerned about a man in the middle attack, you should
consider two-factor auth.  IMO get vs post there is no security
difference if MITM is your worry.  Also make sure that you implement a
configurable lockout on failed login attempts, both for a specific
userid as well as from a specific IP or even from a whole subnet or
domain if you are truly paranoid of the proxies.  You may want to
display a "Your last successful login was: " and a "Your last failed
login was: " to the user.

As for two-factor, for ease of deployment & management I have been
using the token solution from http://www.mypw.com - it's like a hosted
securid product but at a much lower cost.  If you need contact info,
contact me off-list.

Good luck.

-Scott C. Sanchez, CISSP




On 6/6/07, Vishal Garg <vishal@firstbase.co.uk > wrote:
Hi All,

Can someone please tell what is the most secure way of sending login
credentials to the server. The possible ways that I am familiar with are:

- get method
- post method
- hidden form fields

By using an encrypted connection we cannot sniff the credentials, but
still it is very easy to capture or manipulate these credentials
using a web proxy from any of these methods. So I am looking to find
a method to transport the credentials to the server so that the
security of these credentials can't be compromised even by deploying
a web proxy.

Also once a session id is generated, what is the best way to maintain
the security of a session id.

Any help would be much appreciated.

Regards
Vishal


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

The Twelve Most Common Application-level Hack Attacks
Hackers continue to add billions to the cost of doing business online
despite security executives' efforts to prevent malicious attacks. This
whitepaper identifies the most common methods of attacks that we have seen,
and outlines a guideline for developing secure web applications.
Download today!

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



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

The Twelve Most Common Application-level Hack Attacks
Hackers continue to add billions to the cost of doing business online despite security executives' efforts to prevent malicious attacks. This whitepaper identifies the most common methods of attacks that we have seen, and outlines a guideline for developing secure web applications. Download today!


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

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