The remote system you are connecting to, must support the relevant 2FA technology (certificate, biometric signature etc.)
Connecting to a Windows file share doesn’t support 2FA. From: [email protected] [mailto:[email protected]] On Behalf Of James Rankin Sent: Tuesday, 13 January 2015 9:30 PM To: [email protected] Subject: [NTSysADM] 2FA scope I've recently done some work at a place where they've seen occasional use of hardware keyloggers attached to USB keyboard ports to capture usernames and passwords. Naturally, the first thought to mitigate against this possible threat (as securing the ports themselves is not feasible) is to look at implementing two-factor authentication. If the user's password is compromised, the lack of availability of the token will make the scope of the compromise much smaller. However - I did wonder how 2FA stacks up with functions such as "Run As Different User"? If I steal someone's username and password, and then log on to a machine and do "run as different user" on Outlook.exe or even supply the hijacked credentials for a drive mapping to a share, will I be allowed to access information I otherwise wouldn't have had access to? Or does 2FA also come into play when authenticating via these methods as well? I've never thought about this before, just wondering if anyone who has implemented 2FA knows the answer? TIA,
