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.


04:15 AM
Connect Directly

Startup Takes Aim at Man-in-the-Middle

KeyID is about to run pilot tests of its new browser plug-in that secures the authentication process

A security startup is about to pilot-test its new browser plug-in technology that protects users from man-in-the-middle and man-in-the-browser attacks as well as from phishing and pharming, Dark Reading has learned.

KeyID , which recently emerged from stealth mode, is currently talking to major banks about testing its so-called SecureOTP technology, which adds a second layer of authentication to existing two-factor authentication methods using one-time passwords (OTPs).

“SecureOTP is an easy-to-deploy solution that works with any OTP device and solves the major challenges to this technology like man-in-the-middle and man-in-the-browser attacks,” says Sunil Ippagunta, president and CEO of KeyID and inventor of the technology. “[It] essentially leverages the existing investment in OTP technology. It can even work with OTP sent to mobile phones.”

KeyID’s patent-pending SecureOTP technology basically adds its own layer of authentication to a bank or organization’s one-time password technology by encapsulating the OTP with the SSL channel. It works at the authentication stage of a transaction, providing a separate, encryption packed with the OTP so an attacker that tries to intercept the transmission cannot read the password information.

“The problem with man-in-the-middle is that there could be two separate SSL channels, one from the customer to the man-in-the-middle and another from the man-in-the-middle to the real server,” Ippagunta says. “SecureOTP ensures that there is no one in the middle between the customer and the real server. Once an SSL channel is established between customer and server, no one else can join.”

There is a “remote” chance for a man-in-the-browser attack even after secure authentication is set up, however, he says. But the attacker wouldn’t be able to read the SecureOTP-secured credentials. “The credentials are only valid for a specific session and channel,” he says, which would stop the attack.

Ippagunta says most security technologies in this space target phishing and pharming, but don’t solve the MITM and MITB attack problems. “The OTP [alone] can solve phishing to some extent, but does not provide any protection against MITM or MITB. Companies resort to various kinds of fraud monitoring services to overcome these problems. These are expensive and never reliable -- there are more false alerts, and a real hacker can always overcome these hurdles.”

Gail Kerr, executive vice president of business development for KeyID, says the company has spread the word on its new technology to PayPal, Bank of America, and CitiBank. Overall, the banks seem interested in SecureOTP, in part because it’s user-friendly. “They are having to add a lot of customer service people to coach customers on how to use other security solutions,” Kerr says.

KeyID plans to begin its pilot tests in the first quarter of next year, and then roll out the product in the second quarter. SecureOTP will be priced under $2 per user for large installations, Ippagunta says. The company also offers SecureCard, another browser plug-in that works with smart cards and adds data encryption, identity verification, and transaction authorization, according to the Wilton, Conn.-based company.

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Recommended Reading:

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Can you smell me now?
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.