Advice, security specification calls for using system login to do login to web application

Advice, security specification calls for using system login to do login to web application

Secure Home | Search | About
 General Computer Security    Post an article   get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content add this group's latest topics to your Google content
Subject Author Date
Advice, security specification calls for using system login to do login to web application pantagruel 08-28-2007
Posted by pantagruel on August 28, 2007, 8:19 am
If you were  Registered and logged in, you could reply and use other advanced thread options
Hi,

I am reading over a governmental security specification that applies
to a type of governmental knowledge management application that is
invariably ran over https.
According to the specification it supposes that login to the
application will be done by using the users login to their operating
system, invariably assumed to be Windows.


Now from the few bits of security theory I can remember this seems
like a really bad idea, because it means that an attack on the
application can now be achieved by :

1. attacking the application and finding a flaw in how it gets the
login information
2. Attacking windows, controlling a process and then attacking the
application with the hidden process. That hidden process should then
have the users login credentials. For example start a hidden IE and
control its navigation.
3. Attacking the ACL system on Windows.

Anyway I guess the main thing irritating me about this spec is it
seems to assume that have authentication done automatically by using
the OS authentication is inherently more secure than other methods.

Anyone have any comments on this? Am I off base on my feeling that
this is more insecure than other methods?


Posted by Ari on August 30, 2007, 12:44 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
What do you care? It's their spec, let them deal with it.

On Tue, 28 Aug 2007 12:19:35 -0000, pantagruel wrote:

> Hi,
>
> I am reading over a governmental security specification that applies
> to a type of governmental knowledge management application that is
> invariably ran over https.
> According to the specification it supposes that login to the
> application will be done by using the users login to their operating
> system, invariably assumed to be Windows.
>
> Now from the few bits of security theory I can remember this seems
> like a really bad idea, because it means that an attack on the
> application can now be achieved by :
>
> 1. attacking the application and finding a flaw in how it gets the
> login information
> 2. Attacking windows, controlling a process and then attacking the
> application with the hidden process. That hidden process should then
> have the users login credentials. For example start a hidden IE and
> control its navigation.
> 3. Attacking the ACL system on Windows.
>
> Anyway I guess the main thing irritating me about this spec is it
> seems to assume that have authentication done automatically by using
> the OS authentication is inherently more secure than other methods.
>
> Anyone have any comments on this? Am I off base on my feeling that
> this is more insecure than other methods?


--
"You can't trust code that you did not totally create yourself"
Ken Thompson "Reflections on Trusting Trust"
http://www.acm.org/classics/sep95/

Posted by Sebastian G. on August 30, 2007, 3:04 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
pantagruel wrote:

> Hi,
>
> I am reading over a governmental security specification that applies
> to a type of governmental knowledge management application that is
> invariably ran over https.
> According to the specification it supposes that login to the
> application will be done by using the users login to their operating
> system, invariably assumed to be Windows.


No, this invariably assumes NTLM authentication which is not just limited to
Windows, but is not a part of the HTTP specification.

> Anyway I guess the main thing irritating me about this spec is it
> seems to assume that have authentication done automatically by using
> the OS authentication is inherently more secure than other methods.


It is. A mandatory authentication which pretty much shields the credentials
from being abused by the user or being entered into a spoofed dialogue.

Similar ThreadsPosted
Auto Proxy Login?? Please help March 14, 2005, 4:39 am
how to log or block login attempts on OS X? August 18, 2006, 5:04 pm
Bank login not using https March 9, 2007, 11:46 pm
windows xp professional login problems June 2, 2005, 3:52 pm
Deny non-ssl access for login web pages May 28, 2006, 11:12 pm
how to handle failed login attempts? September 8, 2006, 6:57 pm
Chicken and egg issue with Cookie based login? April 6, 2005, 4:39 am
How to enhance login/password weak authentication ? January 18, 2007, 6:17 am
Re: Deleting names from Skype login window dropdown list September 6, 2007, 1:17 am
Advice pls on what is happening on my system December 9, 2005, 5:14 am

The site map in XML format XML site map

Contact Us | Privacy Policy