Re: concurrent logins

["DavidMeans833 () air-watch com" <DavidMeans833 () air-watch com>]

It depends upon what the security goals are.  As an initial brain-storming
idea generator I consider the problem in terms of the security triad and
determine where and what is the confidential information I need to secure,
what are the integrity vectors, and are there any availability concerns?

I then consider the problem again, but from the perspective of the user:
how are they expecting that confidentiality, integrity and availability
will be maintained in this system?

I then throw the Five Pillars of Security into the mix and reconsider the
problem - both from the enterprise and consumer perspectives.  Use any
other appropriate exercise, but the goals are to identify and classify
information and secondly, empathize with the user.

Once the security goals and objectives have been defined for the given
system, we can then determine the appropriate controls. One  system might
warrant a message that more than one users are logged in, while others
would strictly prohibit such a scenario.

David



On 11/19/14, 5:30 AM, "Robin Wood" <robin@digi.ninja> wrote:

> What are peoples opinions on allowing concurrent logins to web apps? I
> suppose it depends on what the app is used for - forum, admin suite
> etc - but do the protections from it add more problems that allowing
> it?
>
> Solutions I can see are:
>
> 1. Allow concurrent logins
> 2. Allow concurrent logins but report that someone else is logged it -
> like Gmail does
> 3. Don't allow them and kick out any logged in user when a new one logs in
> 4. Don't allow them and lock out all new logins till old ones have logged
> out
> 5. Give a warning popup when logging in to say the account is in use
> elsewhere as well
> 6. Allow but report back to an admin or log tracker or similar
>
> 1 is the default in most cases.
> 2 is a good idea but really, how many people look at the little thing
> in Gmail which says where else the account is logged in from, I don't
> and I'm sure normal users don't even know it exists.
> 3. Good but if an attacker gets creds or a reliable session hijack
> then they can use them to DoS legit users by keep logging them out.
> 4. Good but if an attacker gets in they can keep the account active
> and so DoS the real user by never letting them log in.
> 5. Maybe the best option but only works in the legit user logs in
> second otherwise the attacker gets the warning and ignores it.
> 6. Good one if people are watching the logs and can act on them.
>
> What other options are there? Can it be done in a good way that makes
> if of any use?
>
> Robin
>
>
>
> This list is sponsored by Cenzic
> --------------------------------------
> Let Us Hack You. Before Hackers Do!
> It's Finally Here - The Cenzic Website HealthCheck. FREE.
> Request Yours Now!
> http://www.cenzic.com/2009HClaunch_Securityfocus
> --------------------------------------




This list is sponsored by Cenzic
--------------------------------------
Let Us Hack You. Before Hackers Do!
It's Finally Here - The Cenzic Website HealthCheck. FREE.
Request Yours Now!
http://www.cenzic.com/2009HClaunch_Securityfocus
--------------------------------------