Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Endpoint //


11:35 AM
Keith Graham
Keith Graham

Moving Beyond 2-Factor Authentication With ‘Context’

2FA isn't cheap or infallible -- in more ways than two.

What’s the best way to protect your proprietary business secrets or financial data? One common recommendation is to implement two-factor authentication. As you undoubtedly know, two-factor authentication limits the usefulness of any credentials that attackers may have acquired or created, restricting their ability to move laterally within the organization or access your VPN to log back in remotely and attempt to gain ever more powerful credentials.

Unfortunately, two-factor authentication isn’t cheap -- in more ways than one (or even two). Not only can it be costly to implement, it also disrupts legitimate user activity, increasing frustration and hurting productivity. Moreover, two-factor authentication isn’t infallible, as we now know thanks to the reports on the Operation Emmental attacks on Swiss and German banks, in which attackers scraped SMS one-time passwords off customers’ Android phones. 

Fortunately, there is another way keep attackers inside your network from getting what they want: context-based authentication. With context-based authentication, your organization can create rules that determine, pre-authentication, whether and how a given authentication process should proceed based on context.

What do I mean by context? Well, context can include information such as:

Device registration and fingerprinting
Device fingerprinting is typically a two-stage process: On first-time authentication, the solution registers an endpoint, and on subsequent authentications it validates the endpoint against the stored device fingerprint. The device fingerprint comprises a set of characteristics about that endpoint, such as:

  • Web browser configuration
  • Language
  • Installed fonts
  • Browser plug-ins
  • Device IP address
  • Screen resolution
  • Browser cookie settings
  • Time zone

Source IP reputation data
Your organization can deny authentication if the IP address of a user’s machine is part of the Tor anonymity network, a known botnet, or an IP or subnet associated with known bad actors.

Identity store lookup
In addition to stealing existing user credentials, attackers often create new ones. However, they often fail to create those users correctly, with appropriate group membership and attributes. Therefore, by comparing a user’s current information with the corresponding information kept in a directory or user store, you can thwart attackers attempting to use credentials they have created.

Context-based authentication can compare a user’s current geographical location against known good or bad locations and act accordingly. For example, users on a campus location can be approved while users attempting to authenticate from outside the campus can be denied.

Context-based authentication can also base decisions on a geographical area or a virtual barrier -- if the user’s location is outside of a certain proximity, then assign additional risk or deny the authentication attempt.

Using a user’s geo-location and login history together can also help prevent malicious access. For example, if a user logged in at 2 p.m. PST in California, it is reasonable to consider a logon attempt at 4 p.m. PST from the East Coast as an “improbable travel event” and deny the request.

Behavioral analysis
Over time, a solution can gather information about the way that a given user interacts with the device (such as keystroke dynamics, mouse movements, gesture and touch, and motion patterns). Later authentication attempts that fall outside the established behavior patterns can be denied.

Any of these techniques on its own could be circumvented, of course. But combining several or all of them offers a promising solution. Layering multiple contextual factors pre-authorization enables you to build a risk profile that can be used to determine whether to allow a user to proceed to actual authentication, deny the user's continuing with the authentication process, or “step up” to two-factor authentication. For example, if geo-fencing data, together with behavioral analysis, raises sufficient suspicion about a particular authentication request, rather than simply denying the request outright, the system can require the user to provide a second factor.

Context-based authentication can be tailored to your organization’s risk tolerance, enabling you to balance security with a better user experience. Users are unaware of the context-based authentication processes and are not burdened by two-factor authentication unless a login is deemed to involve a certain level of risk.

Attackers will get past even the most fortified perimeter, as newspapers remind us every day. But context-based authentication can help you keep them from them reaching the Holy Grail of your proprietary business secrets or financial data -- and keep your organization out of the headlines.


Keith Graham is the chief technology officer at SecureAuth. With 17 years in security, product management, product development and consulting, Graham is recognized as an industry leader in developing adaptive identity security and access control solutions. Today as CTO, he ... View Full Bio
Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
<<   <   Page 2 / 2
Keith Graham
Keith Graham,
User Rank: Author
12/6/2014 | 7:48:09 AM
Re: A Green Thumb
Joe - The article refers to device fingerprinting, not fingerprinting in the Biometric sense of the term. I agree that would be an entire other topic for debate!
Joe Stanganelli
Joe Stanganelli,
User Rank: Ninja
12/6/2014 | 6:32:16 AM
A Green Thumb
Fingerprinting, FWIW, has fast become notoriously meaningless as a second factor (and especially as an alternative factor unto itself).

Cryptography professor Matthew Green's 7-year-old son is the latest example in the news; Green recently reported that his son took Green's phone while he was sleeping and pressed the sleeping Green's thumb against it.
<<   <   Page 2 / 2
Data Leak Week: Billions of Sensitive Files Exposed Online
Kelly Jackson Higgins, Executive Editor at Dark Reading,  12/10/2019
Intel Issues Fix for 'Plundervolt' SGX Flaw
Kelly Jackson Higgins, Executive Editor at Dark Reading,  12/11/2019
Register for Dark Reading Newsletters
White Papers
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
New Best Practices for Secure App Development
New Best Practices for Secure App Development
The transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2019-12-14
There is an improper authentication vulnerability in Huawei smartphones (Y9, Honor 8X, Honor 9 Lite, Honor 9i, Y6 Pro). The applock does not perform a sufficient authentication in a rare condition. Successful exploit could allow the attacker to use the application locked by applock in an instant.
PUBLISHED: 2019-12-14
Some Huawei smart phones have a null pointer dereference vulnerability. An attacker crafts specific packets and sends to the affected product to exploit this vulnerability. Successful exploitation may cause the affected phone to be abnormal.
PUBLISHED: 2019-12-13
There is an information disclosure vulnerability in certain Huawei smartphones (Mate 10;Mate 10 Pro;Honor V10;Changxiang 7S;P-smart;Changxiang 8 Plus;Y9 2018;Honor 9 Lite;Honor 9i;Mate 9). The software does not properly handle certain information of applications locked by applock in a rare condition...
PUBLISHED: 2019-12-13
Huawei CloudUSM-EUA V600R006C10;V600R019C00 have an information leak vulnerability. Due to improper configuration, the attacker may cause information leak by successful exploitation.
PUBLISHED: 2019-12-13
Certain Huawei products (AP2000;IPS Module;NGFW Module;NIP6300;NIP6600;NIP6800;S5700;SVN5600;SVN5800;SVN5800-C;SeMG9811;Secospace AntiDDoS8000;Secospace USG6300;Secospace USG6500;Secospace USG6600;USG6000V;eSpace U1981) have an out-of-bounds read vulnerability. An attacker who logs in to the board m...