Optimizing your two-factor authentication security

Often when discussing cybersecurity threats like phishing and initial points of compromise with clients, we’ll hear something along the lines of, “That looks great, but we have two-factor authentication enabled on that login.” But while enabling two-factor authentication (2FA) is a step in the right direction – Schneider Downs recommends it everywhere – it isn’t foolproof. Traditional two-factor does add an extra layer of protection on top of your accounts, deterring lazy malicious actors, but will not stop attackers dedicated to breaching your organization. What traditional forms of 2FA (SMS, push code) really do is limit attackers to a single login session per compromised account.

How? Because traditional 2FA requires you to type in a code, it can be phished just like usernames and passwords. If an attacker tricks a user into entering credentials on a fake login site (www.schn3iderdowns.com, for example), they can programmatically submit those credentials to the real site (www.schneiderdowns.com), triggering the SMS token or notification, which the user may also then enter on the fake site. These 2FA methods still rely on users to notice red flags like a slightly different domain, URL or sender, which phishing has proven users are susceptible to overlooking.

Enter Universal 2nd Factor (U2F), created by the FIDO alliance, a form of two-factor using public key encryption and involving a small USB device on which the private key is stored. It gets plugged into an open USB port and is able to communicate directly with your web browser, meaning no additional drivers or software needs to be locally installed.

When you login to a site with U2F enabled, the site sends your device an encrypted challenge, which includes the URL of the website asking for the information. If the user has the USB plugged in and approves authentication, the challenge is signed and sent back. Since the exchange included the URL of the inquiring site, the authentication token is only good for that site. This means that an attacker who tricks a user into entering and approving authentication for www.schn3iderdowns.com cannot successfully relay that authentication to www.schneiderdowns.com.

Methods to attack U2F security will likely become a hot topic in the future, but right now, enabling it on a supported service drastically reduces the success rate of attacks that rely on phishing techniques or keyloggers as a means of breaching that service.

U2F authentication deployment is still in early stages, but may be quite common soon. Chrome, Firefox and Opera are the only browsers that currently support it, but some large services like Google, Dropbox, Facebook, Twitter and GitHub have already adopted U2F support. You can find a list of sites and whether they support U2F at https://www.dongleauth.info/#.

our thoughts on

array(1) { [0]=> string(2) "56" }
The Dichotomy of Cybersecurity in Higher Education
New features for enhanced password protection in Azure Active Directory
Using Your Mail Server Against You
California First to Require IoT Security
Better Understanding PCI Penetration Testing Requirements
What is the SEC Looking For in Your Internal Control Environment?

Register to receive our weekly newsletter with our most recent columns and insights.

Have a question? Ask us!

We’d love to hear from you. Drop us a note, and we’ll respond to you as quickly as possible.

Ask us

contact us

Map of Pittsburgh Office

One PPG Place, Suite 1700
Pittsburgh, PA 15222

p:412.261.3644     f:412.261.4876

Map of Columbus Office

65 East State Street, Suite 2000
Columbus, OH 43215

p:614.621.4060     f:614.621.4062