New answers tagged

0

I think you were on the right track with this. What you could do is sequential pattern mining for prepared auth logs. You could group the events, something like: login computer 1, logout computer 1, login computer 2, ..., entering area 1, leaving area 1, entering area 2, ... vpn login, etc. when preparing the data. I would look for the rare sequential ...


2

Do you recommend comparing users' passwords (during registration, password change, or even every successful login) with such a large list? For reasonable security, I recommend to check passwords against a list of 10,000 passwords during registration and password change. Also block passwords that contain the company name, application name, or the user's name....


2

"Every successful login" is pointless waste unless you just implemented the password-checking feature and didn't have it before, in which case it might make sense to check every user's login once. The only other time it would make sense is right after you add a bunch of new passwords. Add a field to your authentication DB that indicates whether ...


Top 50 recent answers are included