Browse Prior Art Database

Selective designation of security requirements on individual bookmarks in a web browser

IP.com Disclosure Number: IPCOM000014375D
Original Publication Date: 2002-Mar-28
Included in the Prior Art Database: 2003-Jun-19
Document File: 1 page(s) / 37K

Publishing Venue

IBM

Abstract

Selective designation of security requirements on individual bookmarks in a web browser There is a standardized security protocol used within http transactions called the Secure Socket Layer (SSL). This is the basis of almost all secure transactions between client and servers on the internet. Typically, when a server site decides that the user is entering an area where data security is required, it will turn on the SSL protocol for the future transactions. This is shown via a padlock showing up on portions of most browsers. Another alternative is the user can initiate and demand all transactions with a server be conducted in SSL format. This is done by hitting the security button on a client's browsers. However, the drawback is ALL transactions from that point regardless of the web site or page visited, it is now done with the SSL turned on. This is a performance drain on a system as more encoding and decoding must take place. The proposed idea is to let the user designate certain bookmarks as requiring SSL security when a user chooses a site via the bookmarks. If the server site does not or cannot support SSL at the time of the connection attempt, the connection attempt will be terminated by the client browser. There are some users who are nervous or very protective of any data and thus want to have SSL engaged at the very first instance. When the user picks another web site that does not have SSL designation in the bookmark, the security requirements are dropped. This is typically some web site, such as a news site, which is public and has no private data to be entered.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 65% of the total text.

Page 1 of 1

Selective designation of security requirements on individual bookmarks in a web

browser

There is a standardized security protocol used within http transactions called the Secure Socket Layer (SSL). This is the basis of almost all secure transactions between client and servers on the internet. Typically, when a server site decides that the user is entering an area where data security is required, it will turn on the SSL protocol for the future transactions. This is shown via a padlock showing up on portions of most browsers. Another alternative is the user can initiate and demand all transactions with a server be conducted in SSL format. This is done by hitting the security button on a client's browsers. However, the drawback is ALL transactions from that point regardless of the web site or page visited, it is now done with the SSL turned on. This is a performance drain on a system as more encoding and decoding must take place.

The proposed idea is to let the user designate certain bookmarks as requiring SSL security when a user chooses a site via the bookmarks. If the server site does not or cannot support SSL at the time of the connection attempt, the connection attempt will be terminated by the client browser. There are some users who are nervous or very protective of any data and thus want to have SSL engaged at the very first instance. When the user picks another web site that does not have SSL designation in the bookmark, the security requirements are droppe...