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.

Perimeter

11/28/2011
12:46 PM
Taher Elgamal
Taher Elgamal
Commentary
50%
50%

SSL's Future

SSL will evolve to meet requirements for e-commerce and mobile

So what will happen to the current e-commerce world based on SSL and all of the new authentication methods under way?

SSL has been the target for a variety of attacks, many of which have been in the news lately. I believe that it will be extremely difficult to fundamentally change the models for e-commerce after 15 years of growth, despite the fraud and threats we know about. The appropriate way to manage fraud better is to work on the existing systems to improve how parties assure themselves of the identities of others involved in transactions.

There is actually more than one way that authentication can be supported within the SSL framework as it stands.

Any strong authentication can simply be used after the one-sided server authentication and encryption session has been established. At this point, the server can request any authentication information from the client, and the authentication can happen within the encrypted session. Each website can choose the authentication method it desires, as long as browser and client support can be established somehow.

Alternatively, the strong authentication method desired could be used to “unlock” a private key with a digital certificate on the client side that can be used to provide the client authentication requested by the SSL server.

Either way, the current infrastructure can, in fact, support multiple authentication methods that will help us mitigate the dependence on user passwords.

I wish that the technical community could collaborate on improving the existing e-commerce infrastructure. Many improvements are needed, for sure, but incremental improvements have always worked better than calling for a new infrastructure that would not be possible to actually put together.

My prediction is that SSL will grow with the e-commerce needs and that new versions and new implementations will meet the expectations for growing e-commerce and mobile commerce requirements.

Recognized in the industry as the "inventor of SSL," Dr. Taher Elgamal led the SSL efforts at Netscape. He also wrote the SSL patent and promoted SSL as the Internet security standard within standard committees and the industry. Dr. Elgamal invented several industry and government standards in data security and digital signatures area, including the DSS government standard for digital signatures. He holds a Ph.D. and M.S. in Computer Science from Stanford University.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Data Privacy Protections for the Most Vulnerable -- Children
Dimitri Sirota, Founder & CEO of BigID,  10/17/2019
Sodinokibi Ransomware: Where Attackers' Money Goes
Kelly Sheridan, Staff Editor, Dark Reading,  10/15/2019
Tor Weaponized to Steal Bitcoin
Dark Reading Staff 10/18/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
2019 Online Malware and Threats
2019 Online Malware and Threats
As cyberattacks become more frequent and more sophisticated, enterprise security teams are under unprecedented pressure to respond. Is your organization ready?
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-16978
PUBLISHED: 2019-10-21
In FusionPBX up to v4.5.7, the file app\devices\device_settings.php uses an unsanitized "id" variable coming from the URL, which is reflected on 2 occasions in HTML, leading to XSS.
CVE-2019-16979
PUBLISHED: 2019-10-21
In FusionPBX up to v4.5.7, the file app\contacts\contact_urls.php uses an unsanitized "id" variable coming from the URL, which is reflected in HTML, leading to XSS.
CVE-2019-16980
PUBLISHED: 2019-10-21
In FusionPBX up to v4.5.7, the file app\call_broadcast\call_broadcast_edit.php uses an unsanitized "id" variable coming from the URL in an unparameterized SQL query, leading to SQL injection.
CVE-2019-16990
PUBLISHED: 2019-10-21
In FusionPBX up to v4.5.7, the file app/music_on_hold/music_on_hold.php uses an unsanitized "file" variable coming from the URL, which takes any pathname (base64 encoded) and allows a download of it.
CVE-2019-16530
PUBLISHED: 2019-10-21
Sonatype Nexus Repository Manager 2.x before 2.14.15 and 3.x before 3.19, and IQ Server before 72, has remote code execution.