A web data isolation protection method based on hot plug security session

Abstract

The application discloses a kind of Web data isolation protection methods based on hot plug security session, based on WebTeleporter implementation, this method adds a new independent parallel Web session between the device trusted by user and WebTeleporter outside original Web session of user and application, and the original Web session is initiated by the device that user does not trust, and the carrier of parallel Web session is the device that user trusts.User can freely select sensitive data, so that it is not transmitted on original Web session, but on parallel session, so as to achieve the effect of protecting user privacy.The application does not need to modify the original code of application to add trusted device, but by deploying WebTeleporter layer in application server, it is a plug-and-play implementation.The application is a lightweight method, and the implementation method is simple, the means is flexible, and the privacy protection of user can be significantly guaranteed.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer network security, and particularly relates to a Web data isolation protection method based on a hot plug security session. BACKGROUND

[0002] Internet has achieved great success in the past few decades, which provides a brand-new platform for people to exchange and accept information. Its wide popularity promotes the development and application of network technology. However, the huge network also exposes some security problems, such as the problem of user privacy leakage. When the user accesses and transmits information to the application on an untrusted device, the user's sensitive information may be leaked.

[0003] Many methods have been proposed to solve the problem of possible privacy leakage of sensitive information transmitted by the user on an untrusted device. A common approach is to add a trusted device to transmit sensitive information. However, the methods of this approach proposed before have some problems.

[0004] Firstly, they need to modify the original business code of the application to integrate the trusted device into the application. For the application, this is not transparent enough, and the business logic of the application will be messy. Secondly, they also need the developer to mark which data is sensitive information in advance. After marking, if it needs to be changed, the developer needs to add it. For the user, this is not flexible enough, and the user cannot choose which information is sensitive information that needs to be protected. Thirdly, some methods can only protect sensitive information from being leaked at the user login stage, but cannot protect the transmission of all sensitive information in the subsequent stage. SUMMARY

[0005] The present application aims at the deficiencies of the prior art, and provides a Web data isolation protection method based on a hot plug security session.

[0006] The purpose of the present application is achieved by the following technical solutions.

[0007] A Web data isolation protection method based on a hot plug security session, the method is implemented based on WebTeleporter, and the WebTeleporter is composed of three components, namely a response filter, a request interceptor and a forwarder.

[0008] The response filter is used for injecting the code of the WebTeleporter into the Web data, namely the response, transmitted to the application by the application;

[0009] The request interceptor intercepts the Web data, namely the request, transmitted from the trusted device and the untrusted device, and integrates them into a submission and then sends them to the application;

[0010] The repeater transmits the sensitive input in the untrusted device browser to the mobile browser and maintains a table of correspondence between the tSSID belonging to the trusted device and the token belonging to the untrusted device; tSSID and token are two strings of characters for identity authentication, and WebTeleporter is deployed in the server between the application layer and the transport layer.

[0011] The method of the present application further comprises the following steps:

[0012] Step one: the user initiates a request to the browser application on the untrusted device, the request is intercepted by the request interceptor of WebTeleporter, and then forwarded to the application by the request interceptor;

[0013] Step two: after the application accepts the request, the user's request content is sent to the user, and the response filter of WebTeleporter processes the response sent back to the user's browser by the browser application, injects the JavaScript code required for a new independent secure parallel Web session, and sends it to the user;

[0014] Step three: after the user accepts the response, the browser will display the UI rendered by the code injected by WebTeleporter in addition to the request content, the UI consists of three buttons: two-dimensional code, selection box and send key, the user clicks the two-dimensional code button in the UI, and uses the trusted device to scan the two-dimensional code to establish a parallel Web session;

[0015] Step four: after the parallel Web session is successfully established, the user clicks the selection box on the untrusted device to select the sensitive information that needs to be transmitted in the parallel Web session, and clicks the send key to submit;

[0016] Step five: the keywords of the selected sensitive information are received by the repeater of WebTeleporter and forwarded to the trusted device, and the input box of the sensitive information is displayed on the trusted device;

[0017] Step six: the user inputs the sensitive information on the trusted device and clicks the send key;

[0018] Step seven: the user inputs other information on the untrusted device and clicks the send key;

[0019] Step eight: the request interceptor of WebTeleporter intercepts the information sent by the user, and integrates the information of the two Web sessions into one Web session before sending it to the application;

[0020] Step nine: the application sends a response to the user after receiving the request, and returns the request content.

[0021] As a further improvement, the step three of the present application is implemented by the following sub-steps:

[0022] (3.1) At the same time of injecting the code in step two, the forwarder of WebTeleporter gives a new tSSID, which is saved by the untrusted device's browser, and the tSSID is the basis to make the basic Web session between the untrusted device and the application and the parallel session between the trusted device and the WebTeleporter work properly;

[0023] (3.2) After the trusted device scans the two-dimensional code given by the WebTeleporter on the untrusted device, the trusted device sends a request to the WebTeleporter to establish a parallel Web session;

[0024] (3.3) The forwarder gives the trusted device a token according to the tSSID saved by the untrusted device scanned by the trusted device, and maintains a table of tSSID and token correspondence;

[0025] (3.4) The trusted device receives the response of the forwarder, and the parallel Web session is successfully established;

[0026] (3.5) The parallel Web session is terminated by clicking the button with the word detach on the trusted device.

[0027] As a further improvement, the step five of the present application is implemented by the following sub-steps:

[0028] (5.1) After the user selects the sensitive information to be transmitted in the parallel Web session, the injected WebTeleporter JavaScript code scans the information to be input on the webpage, and sends the keywords to the forwarder;

[0029] (5.2) The input box for sensitive information on the untrusted device becomes an input state;

[0030] (5.3) The forwarder gives the trusted device a token according to the tSSID saved by the untrusted device scanned by the trusted device, and maintains a table of tSSID and token correspondence; The forwarder stores the tSSID and the token of the trusted device corresponding to the parallel Web session, and is responsible for rendering the input UI of these sensitive information on the trusted device, and the communication protocol between the forwarder and the trusted device is selected as HTTPS and WebSockets.

[0031] As a further improvement, the step eight of the present application is implemented by the following sub-steps:

[0032] (8.1)WebTeleporter's request interceptor intercepts the request, the order of step six and step seven can be interchanged, the request interceptor saves the request in the session first, waits for the request of another session to arrive, and verifies whether the two sessions are the same user's request by relying on the table of tSSID and token combination maintained by the teleporter;

[0033] (8.2)After the requests of the two sessions are intercepted, the request interceptor extracts the input of sensitive information from the parallel Web session, and finds the position of the original sensitive information in the original Web session according to the keyword of the sensitive information, and fills the extracted sensitive information into the corresponding position after finding;

[0034] (8.3)At this time, the Web session has been integrated from two sessions into one session, and the request interceptor sends the integrated session to the application, and the application always sees only one session.

[0035] The beneficial effects of the application are:

[0036] The application discloses a Web data isolation protection method based on hot plug security session, and is realized based on WebTeleporter; the method adds a new independent parallel Web session between a user trusted device and a WebTeleporter outside an original Web session of the user and an application; the original Web session is initiated by a device not trusted by the user, and a carrier of the parallel Web session is the user trusted device. The user can freely select sensitive data, so that the sensitive data is not transmitted on the original Web session, but is transmitted on the parallel session, so that the effect of protecting user privacy is achieved. The application does not need to modify the original code of the application to add the trusted device, but deploys a WebTeleporter layer on an application server, is a plug-and-play implementation, and the parallel Web session is established between the user and the WebTeleporter; the application always considers that there is only one original Web session between the application and the user. The two points realize sufficient transparency to the application. The application can select which information is sensitive information by the user, and the sensitive information needs to be transmitted on the safe parallel Web session, so that the user has certain flexibility. The application can provide protection when the application establishes a session with the untrusted device, instead of only providing information protection in the login stage, so that the user can transmit information on the untrusted device more safely. The application is a lightweight method, the implementation method is simple, the means is flexible, and the privacy protection of the user can be significantly guaranteed. BRIEF DESCRIPTION OF DRAWINGS

[0037] Figure 1 It is a Web data isolation protection method flow chart based on hot plug security session. Detailed Implementation

[0038] The technical solution of the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0039] This invention relates to a Web data isolation and protection method based on hot-pluggable secure sessions, which is implemented using WebTeleporter. WebTeleporter consists of three components: a response filter, a request interceptor, and a forwarder.

[0040] Response filters are used to inject WebTeleporter code into the web data (response) sent by the application;

[0041] The request interceptor intercepts web data requests coming from trusted and untrusted devices and integrates them into a single submission before sending it to the application.

[0042] The repeater transmits sensitive input from the browser on an untrusted device to the mobile browser and maintains a table mapping tSSIDs belonging to trusted devices to tokens belonging to untrusted devices; tSSID and token are two strings of characters used for authentication. WebTeleporter is deployed on the server between the application layer and the transport layer.

[0043] Includes the following steps:

[0044] Step 1: The user initiates a request to the browser application from an untrusted device. An untrusted device refers to a device whose security of information transmission is unknown to the user, such as a public computer in a library. We will use "public computer" to represent an untrusted device in the following explanation. The request is intercepted by WebTeleporter's request interceptor, which then forwards it to the application.

[0045] Step 2: After the application receives the request, it sends the requested content to the user. WebTeleporter's response filter processes the application's response, injects the JavaScript code required to create a new independent and secure parallel web session, and sends it to the user.

[0046] Step 3: After the user accepts the response, in addition to the requested content, the browser will display the WebTeleporter UI. The user scans the QR code provided in the UI using a trusted device to establish a parallel web session. A trusted device refers to a device that the user is confident in is secure in transmitting information, such as the user's own mobile phone. The following explanation will use a mobile phone to represent a trusted device.

[0047] This step is divided into the following sub-steps.

[0048] 1) During step 2, while injecting code into the response, the WebTeleporter forwarder will provide a new tSSID, which is then stored by the browser on the public computer. The tSSID is the identity identifier of the public computer. It is the foundation for the basic web session between the public computer and the application, and the parallel session between the mobile phone and WebTeleporter to function properly.

[0049] 2) After scanning the QR code provided by WebTeleporter on the public computer with a mobile phone, the mobile phone will send a request to WebTeleporter to establish a parallel web session.

[0050] 3) The repeater assigns a token to the phone based on the tSSID stored on the public computer scanned by the phone, and maintains a table mapping tSSIDs to tokens. The token and tSSID are the identity identifiers of the phone and the public computer, respectively. Any pair of tokens and tSSIDs in the table can identify a unique parallel session. This achieves the effect of identity verification.

[0051] 4) The mobile phone receives the response from the repeater, and the parallel web session is successfully established.

[0052] 5) Parallel conversations can be terminated by clicking the button with the word "detach" on the phone.

[0053] Step 4: After the parallel web session is successfully established, the user clicks the selection box button in the lower right corner on the public computer, then selects the sensitive information to be transmitted in the parallel web session, and clicks the send button in the lower right corner to submit.

[0054] Step 5: The selected sensitive information keywords are received by the WebTeleporter's relay and forwarded to the mobile phone, where the sensitive information input box is displayed.

[0055] This step is divided into the following sub-steps.

[0056] 1) After the user selects the sensitive information to be transmitted on the parallel web session, the injected JavaScript code of WebTeleporter will scan the webpage to see which information that needs to be entered has been selected and send its keywords to the forwarder.

[0057] 2) The input box for selected sensitive information on public computers will become unreadable.

[0058] 3) Because the repeater stores the tSSID and the token of the corresponding trusted device for the parallel web session, the repeater needs to verify whether the received tSSID and token exist. If they do, it is responsible for rendering the input boxes for these sensitive information on the mobile phone. The communication protocol between the repeater and the mobile phone can be HTTPS or WebSockets.

[0059] Step Six: The user enters sensitive information on their mobile phone and sends it.

[0060] Step 7: The user enters all information except for sensitive information on a public computer and sends it.

[0061] Step 8: WebTeleporter's request interceptor intercepts the information sent by the user, and combines the information from the two web sessions into one web session before sending it to the application.

[0062] This step is divided into the following sub-steps.

[0063] 1) WebTeleporter’s request interceptor intercepts the request. The order of steps six and seven can be interchanged. The request interceptor saves the request from the first session and waits for the request from the other session to arrive. Verifying whether the two sessions are from the same user relies on a table of tSSID and token combinations maintained by the forwarder.

[0064] 2) After the requests of both sessions are intercepted, the request interceptor will extract the input of sensitive information from the parallel web session, and search for the original location of the sensitive information in the original web session based on the keywords of the sensitive information. After finding it, the extracted sensitive information will be filled into the corresponding position.

[0065] 3) At this point, the web session has been merged from two sessions into one. The request interceptor sends the merged session to the application, and the application always sees only one session.

[0066] Step 9: After receiving the request, the application sends a response to the user, returning the requested content.

[0067] The above embodiments are used to explain and illustrate the present invention, but not to limit the present invention. Any modifications and changes made to the present invention within the spirit and scope of the claims shall fall within the protection scope of the present invention.

Claims

1. A Web data isolation and protection method based on hot-pluggable secure sessions, characterized in that, The method described is based on WebTeleporter, which consists of three components: a response filter, a request interceptor, and a forwarder. The aforementioned response filter is used to inject WebTeleporter code into the Web data, i.e., the response, sent out by the application; The request interceptor intercepts web data requests coming from trusted and untrusted devices and integrates them into a single submission before sending it to the application. The relay transmits sensitive input from the browser on an untrusted device to the mobile browser and maintains a table mapping tSSIDs belonging to trusted devices to tokens belonging to untrusted devices; the tSSID and token are two strings of characters used for authentication. WebTeleporter is deployed on the server between the application layer and the transport layer; the method includes the following steps: Step 1: The user sends a request to the browser application on an untrusted device. The request is intercepted by WebTeleporter's request interceptor and then forwarded to the application. Step 2: After the application receives the request, it sends the requested content to the user. WebTeleporter's response filter processes the response sent back to the user's browser by the browser application, injects the JavaScript code required to create a new independent and secure parallel web session, and sends it to the user. Step 3: After the user accepts the response, in addition to the requested content, the browser will also display a UI rendered by the code injected by the newly added WebTeleporter in the lower right corner of the interface. The UI consists of three buttons: a QR code, a selection box, and a send button. The user clicks the QR code button in the UI and uses a trusted device to scan the QR code to establish a parallel web session. Step 4: After the parallel web session is successfully established, the user clicks the selection box button in the lower right corner on the untrusted device, then selects the sensitive information to be transmitted in the parallel web session, and clicks the send button in the lower right corner to submit; Step 5: The selected sensitive information keywords are received by the WebTeleporter's forwarder and forwarded to the trusted device, where the sensitive information input box is displayed. Step Six: The user enters sensitive information on the trusted device and clicks send; Step 7: The user enters additional information on the untrusted device and clicks send; Step 8: WebTeleporter's request interceptor intercepts the information sent by the user, and combines the information from two web sessions into one web session before sending it to the application; Step 9: After receiving the request, the application sends a response to the user, returning the requested content.

2. The Web data isolation and protection method based on hot-pluggable secure sessions according to claim 1, characterized in that, Step three is achieved through the following sub-steps: (3.1) While injecting code into the response in step two, the WebTeleporter forwarder will give a new tSSID. At this time, the tSSID is saved by the browser of the untrusted device. The tSSID is the basis for the basic web session between the untrusted device and the application and the parallel session between the trusted device and the WebTeleporter to work properly. (3.2) After the trusted device scans the QR code given by WebTeleporter on the untrusted device, the trusted device will send a request to WebTeleporter to establish a parallel web session. (3.3) The repeater will give a token to the trusted device based on the tSSID stored on the untrusted device scanned by the trusted device, and maintain a table of the correspondence between tSSID and token; (3.4) The trusted device receives the response from the repeater, and the parallel web session is successfully established; (3.5) Parallel web sessions are terminated by clicking a button on the trusted device that displays the word "detach".

3. The Web data isolation and protection method based on hot-pluggable secure sessions according to claim 2, characterized in that, Step five is achieved through the following sub-steps: (5.1) After the user selects the sensitive information to be transmitted on the parallel web session, the injected JavaScript code of WebTeleporter will scan which information that needs to be entered on the webpage has been selected and send its keywords to the forwarder. (5.2) Input fields for sensitive information on the device will become unreadable if the input field is not trusted. (5.3) The forwarder assigns a token to the trusted device based on the tSSID stored on the untrusted device scanned by the trusted device, and maintains a table of the correspondence between tSSID and token; the forwarder stores the tSSID and the token of the trusted device of the corresponding parallel Web session, and is responsible for rendering the input UI of these sensitive information on the trusted device. The communication protocol between the forwarder and the trusted device is HTTPS and WebSockets.

4. The Web data isolation and protection method based on hot-pluggable secure sessions according to claim 3, characterized in that, Step eight is achieved through the following sub-steps: (8.1) The WebTeleporter’s request interceptor intercepts the request. The order of steps six and seven can be interchanged. The request interceptor saves the request from the first session and waits for the request from the other session to arrive. Verifying whether the two sessions are from the same user relies on a table of tSSID and token combinations maintained by the forwarder. (8.2) After the requests of both sessions are intercepted, the request interceptor will extract the input of sensitive information from the parallel Web session and search for the original location of the sensitive information in the original Web session based on the keywords of the sensitive information. After finding it, the extracted sensitive information will be filled into the corresponding position. (8.3) At this point, the web session has been merged from two sessions into one session. The request interceptor sends the merged session to the application, and the application always sees only one session.

Images