I feel like since I'm on the security team, I should find a non-exploit method to actually resolve the policy failure.
...and now I have a project for this weekend.
The naive approach is to look at device ID, but article already talks about copying identification data, and the rest of USB descriptor is trivially copyable as well.
Is the system going to have a rule like "mouse moves same amount of pixels with equally spaced pauses"? But what if they randomize motion commands and intervals between them?
https://docs.microsoft.com/en-us/sysinternals/downloads/proc...
https://docs.microsoft.com/en-us/sysinternals/downloads/proc...
There is no device ID, process ID or binary to match.
If they are stuck on that policy, they should give you a smart card/yubikey heck even a fingerprint reader (You can't rotate these :-p ) to unlock your device.
You will just end up copying and pasting it around. I'd rather avoid that as there's many ways to copy out your clipboard with Javascript or a malware payload that somehow got onto your host.
I hope they also have a 30 day password expiry policy as well. Dont want users to get too comfortable with their password.
Even with a 12 password policy I see most people just using 'MyP@ssword2021', so I guess with 64 characters most people will just use 'MyPassword(012..9){6}'
https://www.my1login.com/resources/password-strength-test/
Along with this:
https://www.random.org/strings/
and I discovered that apparently, a 7 character password of random chars that includes a 0 (zero) is really hard to crack!
I wont be doing that though for my own passwords but it was interesting none-the-less.