Patent Description:
With the development of information technology, acquiring information from the Internet has become an important information acquisition means for people, wherein a major means includes sending an HTTP page request to a server by using a browser on a client terminal, such that the server responds to the HTTP request and returns requested page information to the client terminal, for a user of the client terminal to browse.

A page returned by the server usually includes sensitive information related to the user, such as an account name, a mailing address, a mobile phone number, and identity card information of the user. An illegal user can acquire sensitive information in the page easily by viewing the source code of the page, crawling web data packets on the web, and the like, leading to leakage of user information. For example, information after "mailto:" or information in front of and after "@" may be extracted from the page information by using a network tool, to achieve the objective of extracting Email information in the page.

In the conventional techniques, common methods for processing sensitive information include processing methods such as encrypting and masking sensitivity by using a JavaScript script embedded in the page, or preventing an illegal user from capturing packets in the page returned by the server. For example, email sensitive information may be transformed into an ASCII coded character string, and then written into the page by using a document. write method in the scripting language of JavaScript, thus completing processing on the email sensitive information.

However, in the conventional techniques, sensitive information in the page returned by the server is usually original sensitive information without procession by JavaScript scripting, and further, even if JavaScript scripting has been performed on the sensitive information in the page, an illegal user can still acquire the sensitive information in the page by low-difficulty means such as deleting the JavaScript script on the client terminal or stopping running of the corresponding JavaScript script. Therefore, the common methods for processing page sensitive information in the conventional techniques cause low security of the sensitive information in the page.

Example systems and methods for protecting sensitive content are described in the following documents.

In <CIT>, a computer implemented method, apparatus, and computer usable program product for protecting sensitive content is disclosed. In response to receiving a selection of content, the process determines whether the content is of a sensitive content type based on a policy. The process then designates the content as the sensitive content in response to the content being of a sensitive content type. Thereafter, the process generates a sensitive content reference for publication and stores the sensitive content in a data structure, wherein the data structure associates the sensitive content with the sensitive content reference. Subsequently, in response to receiving a request from a requester for the sensitive content reference, the process obfuscates the sensitive content using a selected obfuscation algorithm to form obfuscated content, and returns the obfuscated content to the requester.

In <CIT>, a mechanism is provided for secure data storage in a distributed computing system by a client of the distributed computing system. A gateway device intercepts a data file from at least a portion of stream data during transmission. If the destination of the data file is the storage, the gateway device selects a set of analysis algorithms to determine whether the data file comprises sensitive data.

In <CIT>, a user interface framework is based on a Model View Controller architectural pattern. An additional controller, a server controller, is included in the server part of the user interface framework runtime. A client controller is running at the client side of the user interface framework runtime. The client controller and the server controller form one logical synchronized controller. The server controller ensures that all needed controller calculations, which would lead to additional roundtrips between the client side and the server side, can be done on the server side. Therefore, an exact one roundtrip between client side and backend for every user interaction and transporting only the bare minimum of data needed to render the current user interface state is achieved.

An objective of the present application is to provide a sensitive information processing method, device and server, and a security determination system, which may improve the security of sensitive information in a page.

The present invention provides a sensitive information processing method, including:.

The present invention further provides a device for implementing sensitive information processing, comprising: one or more processors; and one or more memories having stored thereon computer-readable instructions, which when executed, cause the one or more processors to perform acts comprising:.

The present application provides a sensitive information processing method and device. To-be-processed information may be acquired on a page server terminal, and it is determined, according to a predetermined sensitive information identification strategy, whether the to-be-processed information is sensitive information. When the to-be-processed information is sensitive information, the sensitive information is processed according to a preset sensitive information processing strategy, and then the processed sensitive information is returned to a page, forming a page with the processed sensitive information. The page received by a client terminal is the page in which sensitive information has been processed on the server terminal, and an illegal user of the client terminal cannot acquire real sensitive information in the page even by capturing data packets or deleting a JavaScript script; in this way, the security of the sensitive information in the page is improved.

To describe the technical solutions in the embodiments of the present application or the conventional techniques more clearly, accompanying drawings needed for describing the embodiments or the conventional techniques will be introduced briefly below. Apparently, the accompanying drawings in the following description are merely some embodiments in the present application, and those of ordinary skill in the art may obtain other drawings according to these accompanying drawings without creative efforts.

To enable those skilled in the art to better understand the technical solutions in the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Apparently, the described embodiments are only some but not all of the embodiments of the present application. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present application without creative efforts shall fall in the protection scope of the present application.

An MVC framework is a web application design and creation mode commonly used by a Web server, in which software service logic, data, and interface display are separated by using Model View Controller (MVC), wherein the Model may be used for encapsulating data related to service logic of an application and a data processing method, and generally has a privilege of directly accessing data, for example, accessing a database. The View may be used for displaying data, and generally is a part, which is related to a user interface, in an application, for example, a page interface that a user can browse and interact with. Generally, the view may be created according to the model data. The Controller functions to organize different levels, and may be used for processing an event and making a response. The three modules of the MVC framework mode may be independent of each other, changing one of them may not affect the other two, and one model can be repeatedly used by different views. For example, user A wants to receive and send emails through a browser, and also wants to access an email box through a mobile phone. An MVC framework design mode may be employed on a server terminal, the model may respond to a request of the user and return response data, the view may format data and may present the formatted data to an Internet interface and a WAP interface of a user page.

<FIG> is a schematic flow chart of interaction between a user and a server, where the server uses an MVC framework page structure. As shown in <FIG>, the user may send an HTTP request to the server through a browser of a client terminal. When the Web server using the MVC framework mode acquires the HTTP request sent by the user through the browser, the Web server generates a corresponding page model according to the HTTP request, and then renders the generated page model. The page model generally may be a page template (ModelMap) designed in advance by page design developers or stored in a system. The page template may include variable information. The rendering of the page model may include finding the variable information in the page template by using the Controller, and substituting a variable in the page module with corresponding real data according to the HTTP request of the user. After completing rendering of the page template (ModelMap), the server may return the rendered page to the user, and the view module (View) may control a display interface of the rendered page on the client terminal of the user.

The present application provides a sensitive information processing method, which can process sensitive information of a user before a server returns a page to the user, such that sensitive information included in the page received by a client terminal of the user is sensitive information that has been correspondingly processed on a server terminal. <FIG> is a method flow chart of an embodiment of a sensitive information processing method according to the present application. As shown in <FIG>, the sensitive information processing method may include:
S <NUM>: To-be-processed information in a page is acquired.

The to-be-processed information may be set according to a framework structure of a page server. The to-be-processed information in this embodiment may include variable information in a ModelMap in an MVC framework structure of a page server. When receiving an HTTP request sent by a user terminal, the page server may create a blank ModelMap page template. The page template ModelMap may be a storage structure in the MVC framework structure, and may be used for storing information, in the page, that needs to be returned to the user terminal. In the above description, the page template ModelMap may include a variable, and a data format of the variable is generally a map (key: value) key-value pair data format including a variable name (key) and a value, wherein the variable value "value" generally may employ a null value or a default character string to represent an initial value. In a Controller phase, data may be put into the variable in the ModelMap by using a ModelMap. put() operation. For example, a variable set in the ModelMap is (name1: value), a value "Zhang san" of the variable "name1" may be put into the variable "name1" in the ModelMap by means of such an operation as ModelMap. put("name1", "Zhang san").

In this embodiment, after data is put into the variable in the ModelMap, data of the ModelMap may be acquired, which, in this embodiment, may refer to acquiring variable information in the ModelMap in the MVC framework structure of the page server, and using the variable information in the ModelMap as the to-be-processed information in the page. It should be noted that, in the sensitive information processing method in the present application, the variable information may be acquired while the page server is putting data into variables in the page, or the variable information in the page may be acquired after the page server finishes putting data into all variables in the page. In this embodiment, in the page server using the MVC framework structure, the variable information may be acquired after the MVC framework finishes putting data of all variables into the ModelMap, and the variable information is used as the to-be-processed information.

In another embodiment of the present application, <FIG> is a schematic flow chart of another embodiment of the sensitive information processing method according to the present application. As shown in <FIG>, in the sensitive information processing method, the acquiring to-be-processed information in a page may include acquiring variable information in an MVC framework by using a postHandle processing program of an interceptor and using the acquired variable information as the to-be-processed information. Specifically, this may include:
In a Controller phase of the MVC framework, the page server puts variable information, in the form of (variable name: value), into a variable in the ModelMap. After finishing putting variable information into all variables in the ModelMap, the MVC framework may send ModelMap data to the interceptor, and the postHandle processing program of the interceptor receives the ModelMap data sent by the MVC framework. The postHandle processing program may traverse the variable information in the ModelMap to acquire the variables in the ModelMap, and use the acquired variable information as the to-be-processed information.

The interceptor may be generally used for intercepting an access source before an execution step or a field of an application is accessed, and may perform a particular processing step before or after the interception. In the MVC framework structure, the interceptor may include three processing methods:.

Generally, the processing methods of the interceptor may be implemented by corresponding processing units, for example, the preHandle processing phase may be implemented by a physical device preHandler of the interceptor, and certainly, the postHandle processing phase may be implemented by a physical device postHandler of the interceptor.

As shown in <FIG>, generally in the preHandle phase, no data has been put into the ModelMap, and therefore, the to-be-processed information, namely, the variable information in the ModelMap in the MVC framework structure in this embodiment, can be acquired in the postHandle or afterCompletion phase. In this embodiment, a preferred manner is as follows: after the Controller in the MVC framework structure is invoked and before the view is rendered, the to-be-processed information in the page may be acquired by using the interceptor, to intervene in sensitive information discrimination processing. Specifically, in this embodiment, after variable data is put into the ModelMap, the postHandle processing program of the interceptor may acquire the variable information in the ModelMap. Certainly, the to-be-processed information in the page may also be acquired by using the interceptor after rendering (Velocity) in the MVC framework structure is invoked, that is, the to-be-processed information is acquired in the afterCompletion phase of the interceptor.

It should be noted that, in this embodiment, the method of acquiring and subsequently modifying the variable information in the ModelMap by using the interceptor is applicable to other framework structures based on the MVC framework, such as a webx framework structure. There may be different interceptors for different page server frameworks. In this embodiment, in the framework structure based on the MVC, the to-be-processed information may be acquired and processed by the corresponding interceptor before the page rendering (Velocity) and after the Controller is invoked, or the to-be-processed information may also be acquired and processed by the corresponding interceptor after the page rendering (Velocity). A preferred implementation is to acquire and process the to-be-processed information by the corresponding interceptor before the page rendering (Velocity) and after the Controller is invoked.

The variable information in the ModelMap in the MVC framework structure of the page server is acquired, and the variable information is used as the to-be-processed information in the page.

S2: It is determined whether the to-be-processed information is sensitive information according to a preset sensitive information identification strategy.

The sensitive information identification strategy may be a set of preset discrimination rules or methods for determining whether the acquired to-be-processed information is sensitive information. For example, when the to-be-processed information is variable information in the ModelMap in the MVC framework structure of the page server, the sensitive information identification strategy may include a sensitive information library that store sensitive information. The determining whether the to-be-processed information is sensitive information according to a preset sensitive information identification strategy may include:.

In this embodiment, a sensitive information library including predefined sensitive information may be set. For example, a user name, a phone number, an email, and identity card number information of a user may be predefined as sensitive information, and their corresponding variable names (keys) "User", "Tel_Num", "E-Mail", and "ID_Num" in the ModelMap may be pre-stored in the sensitive information library. After the variable name of the variable information in the ModelMap is acquired, the acquired variable name may be compared with the sensitive information stored in the sensitive information library. If the sensitive information library includes sensitive information the same as the acquired variable name, it may indicate that the to-be-processed information is sensitive information, i.e., it may indicate that the variable information in the ModelMap corresponding to the variable name is sensitive information in this embodiment; if the comparison result is that the sensitive information library does not include sensitive information the same as the acquired variable name, it may indicate that the to-be-processed information is not sensitive information, i.e., it may indicate that the variable information in the ModelMap corresponding to the variable name is not sensitive information in this embodiment.

The sensitive information stored in the sensitive information library may be added, deleted, or modified as required.

Certainly, when the framework structure of the page server is of another framework mode, the acquired to-be-processed information may be of another data format corresponding to the framework structure of the server, and the sensitive information identification strategy may also be correspondingly set according to the to-be-processed information and the server framework, for example, it may be directly determined whether the whole data in the to-be-processed information is sensitive information or it may be determined, based on specified data, whether the to-be-encrypted information is sensitive information.

In the MVC-based framework structure in this embodiment, it is determined whether the to-be-processed information is sensitive information according to the preset sensitive information identification strategy.

S3: When it is determined that the to-be-processed information is sensitive information, processing may be performed according to a preset sensitive information processing strategy, to form processed sensitive information.

When the determination result is that the to-be-processed information is sensitive information, the to-be-processed information may be processed according to the preset sensitive information processing strategy. The sensitive information processing strategy may include a set of preset rules or methods for processing the to-be-processed information determined as sensitive information. In this embodiment, when the to-be-processed information is of a data format of a variable (variable name: value) in the ModelMap, the performing processing according to a preset sensitive information processing strategy may include processing a value corresponding to the variable name in the variable information. Specifically, the sensitive information processing strategy may include at least one of the followings:
non-processing, display of a predetermined part, complete masking, privilege-based masking, display after transformation, and misinformation.

The non-processing may include not performing processing such as masking, transformation, and substitution on the value corresponding to the variable name, and the value corresponding to the variable name does not change.

The display of a predetermined part may include displaying a particular field of the value corresponding to the variable name according to a predetermined display rule. For example, when the to-be-processed information is (Tel_Num: <NUM>), the predetermined display rule may include substituting the fourth to eighth digits of the value corresponding to the variable name "Tel: Num" with characters "*". After the to-be-processed information (Tel_Num: <NUM>) is processed according to the foregoing processing strategy of displaying a predetermine field , processed sensitive information may be formed, which is (Tel_Num: <NUM>*****<NUM>).

The complete masking may include masking all fields of the value corresponding to the variable name according to a predetermined masking rule. For example, a value corresponding to a variable name "Tel: Num" may be substituted with one or more characters "*", and formed processed sensitive information may be (Tel_Num: *) or (Tel_Num: ***********).

The privilege-based masking may include processing the value corresponding to the variable name according to a privilege of a specified field. For example, the known field is an acquired user name of a user of a client terminal, and corresponding processing methods may be set according to privileges of different domain groups to which the user name belongs. Specifically, as shown in Table <NUM> below, the sensitive information may be processed according to a received privilege of a user of a client terminal that sends an HTTP request. Specifically, for example, when a received user name for sending the HTTP request belongs to a super administrator domain group, it may be set that none of sensitive information is processed; when the user name for sending the HTTP request belongs to an administrator domain group, it may be set that specified sensitive information is partially masked; and when the user name for sending the HTTP request belongs to a user domain group, it may be set that specified sensitive information is completely masked or partially masked.

The display after transformation may include transforming the value corresponding to the variable name according to a predetermined transformation rule, and using the transformed value as the value of the variable name. For example, the value "evil" of the fourth variable (Name4: evil) in the ModelMap is transformed into "live" according to the predetermined rule and then is used as the processed value of the fourth variable, that is, the processed sensitive information may be (Name4: live).

The misinformation may be expressed as performing no processing operation on the value corresponding to the variable name when a sensitive information identification rule is abnormal or the identified sensitive information does not conform to a sensitive information determination standard that is set according to another condition, and in this case, a misinformation log may be generated. The misinformation log may store and record the number of generated misinformation as well as a target source (such as an original variable name and value) of each misinformation, cause of misinformation, a log generation time, and the like. In this embodiment, the generated misinformation log may be stored, and may be used for subsequent behavioral statistics.

During specific implementation, the sensitive information processing strategy may be set in a combined or nested manner as required. For example, the performing processing according to a preset sensitive information processing strategy may include:.

In a specific example, a user name, a phone number, an email, and identity card number information of a user may be predefined as sensitive information, and their corresponding variable names (keys) in the ModelMap are "User", "Tel_Num", "E-Mail", and "ID_Num". During setting of the sensitive information processing strategy, in accordance with preset security levels of the sensitive information, only first two characters of a value corresponding to the variable name "User" of the user name may be displayed according to the processing strategy of displaying a predetermined part, while the rest are substituted with characters "*"; only the character "@" and characters after "@" in a value corresponding to the variable name "E-Mail" of the user's email are displayed according to the processing strategy of displaying a predetermined part. For the identity card number of the user, which is relatively important, all of the value corresponding to the variable name "ID_Num" of the identity card number may be substituted with <NUM> characters "*" according to the processing strategy of complete masking.

Certainly, in another implementation, in a same variable of the variable information, a sensitive information processing strategy may also be set for a value corresponding to the same variable name according to a preset privilege of specified field information. The specified field may include information about a particular field in the acquired page, for example, a user name of a user who sends an HTTP request. Specifically, for example, the sensitive information may be processed according to an acquired privilege of the user who sends the HTTP request. For example, when the user who sends the HTTP request has administrator privileges, the value corresponding to the variable name "Tel_Num" of the phone number of the user may not be processed, and the administrator can view complete phone number information in the finally returned page. If the user who sends the HTTP request is a regular member, only the first and last three phone number digits of the value corresponding to the variable name "Tel_Num" of the phone number of the user may be displayed according to the predetermined display rule, and the rest are substituted with characters "*".

When it is determined that the to-be-processed information is sensitive information, processing may be performed according to at least one preset sensitive information processing strategy, to form processed sensitive information.

S4: The corresponding to-be-processed information in the page is substituted with the processed sensitive information, to form a page with the processed sensitive information.

After the processed sensitive information is formed from the to-be-processed information acquired in the page, the processed sensitive information may be sent to a corresponding position of the corresponding to-be-processed information in the page, to substitute the original to-be-processed information in the page. For example, in this embodiment, after the value corresponding to the variable name is substituted according to the sensitive information processing strategy, a variable after the value substation may be returned to the ModelMap in the MVC server framework structure, and the page is rendered by using the variable after the value substitution in the MVC framework. Specifically, for example, during rendering of a VM page template, a value in variable information, whose variable name is the same as the variable name of the processed sensitive information, among variable information in the ModelMap may be substituted with a value corresponding to the variable name in the processed sensitive information. For example, the value "Li si" of the variable (Name2: Li si) in the ModelMap may be substituted with the value "Li*" of the processed sensitive information (Name2: Li*). Certainly, when it is determined that the to-be-encrypted information is not sensitive information or the processing strategy for the sensitive information is non-processing or misinformation, the to-be-encrypted information may not need to be processed. Specifically, in this embodiment, the value of the variable in the ModelMap may not be substituted.

After the page is rendered by using the processed sensitive information to form a page with the processed sensitive information, the page with the processed sensitive information may be returned to the browser of the client terminal. After receiving the page with the processed sensitive information, the client terminal displays the page with the processed sensitive information to the user. For example, in a module display area for displaying a current login user name, the user name "Li si" is originally displayed, and after the sensitive information is processed, a user name displayed to the user of the client terminal may be "Li*".

In the sensitive information processing method provided by this embodiment, to-be-processed information may be acquired at a page server terminal, and it is determined whether the to-be-processed information is sensitive information according to a preset sensitive information identification strategy. When the to-be-processed information is sensitive information, the sensitive information may be processed according to a preset sensitive information processing strategy, and then the processed sensitive information is returned to the page, so that a page with the processed sensitive information can be formed. The sensitive information included in the page with the processed sensitive information is information that has been correspondingly processed on the server terminal, and an illegal user of a client terminal cannot acquire the real sensitive information in the page even by capturing data packets or deleting a JavaScript script; in this way, the security of the sensitive information in the page is improved
An HTTP request page sent by the user of the client terminal may include multiple pieces of sensitive information to be identified and processed, and these pieces of sensitive information may appear at different locations in different request pages, and may also correspond to different variables in the ModelMap of the MVC framework structure, which increases the difficulty of identifying sensitive information in subsequent sensitive information processing. Different MVC framework-based page servers or different design and development personnel may set different variable names in the ModelMap for same sensitive information such as an email or an identity card number of the user. For example, in the ModelMap of one page request, a variable name corresponding to the identity card number variable information is "ID_Num", while in another page request, a variable name corresponding to the identity card number variable information may be "Num _001" in the ModelMap. The present application provides another embodiment of a dynamic sensitive information processing method, and in this embodiment, the sensitive information identification strategy can be dynamically adjusted according to a preset sensitive information monitoring strategy. Specifically, the sensitive information processing method may further include:.

In this embodiment, it may be determined, according to the preset sensitive information monitoring strategy, whether the value of the variable information in the ModelMap is to-be-processed sensitive information. In a specific implementation application, the sensitive information generally has a particular data structure format, for example, a mobile phone number generally may be a combination of <NUM> digits starting with a non-zero digit, an email generally may include the character "@". In this case, the sensitive information monitoring strategy may determine, by means of regular matching, whether the value of the variable information in the ModelMap conforms to the preset number combination of <NUM> digits, or determine whether the value of the variable information in the ModelMap includes the character "@" and whether there is at least one non-null character in front of "@", or the like. If it is determined, according to the sensitive information monitoring strategy, that the value of the variable information in the ModelMap is to-be-processed sensitive information, a variable name "Phone_Num" or "First_Contact" corresponding to the value of the variable information may be sent to the sensitive information library. The sensitive information library may receive the variable name "Phone_Num" or "First_Contact" corresponding to the value of the variable information, and compare to see whether the sensitive information library has stored sensitive information the same as the variable name. If there is no sensitive information the same as the variable name in the sensitive information library, the variable name, which is not included in the sensitive information library but the value corresponding to which is the to-be-processed sensitive information, may be stored into the sensitive information library as newly-added sensitive information. In this way, if the newly-added sensitive information "Phone_Num" or "First_Contact" is not stored in the sensitive information library currently, by means of the sensitive information monitoring strategy, the to-be-processed sensitive information whose variable name is "Phone_Num" or "First_Contact" may be added to the sensitive information library as newly-added sensitive information. Next time an HTTP request of the user is responded to, sensitive information whose variable name is "Phone_Num" or "First_Contact" may be identified, and the value corresponding to the variable name "Phone_Num" or "First_Contact" may be processed according to the sensitive information processing strategy.

Corresponding to the to-be-processed sensitive information identified in S5 above, a corresponding to-be-processed sensitive information log may further be generated. The to-be-processed sensitive information log may include the number of the to-be-processed sensitive information, a value of the to-be-processed sensitive information, a variable name corresponding to the value, whether the to-be-processed sensitive information has been sent to the sensitive information library, a processing time of each piece of the to-be-processed sensitive information, a generation time of the to-be-processed sensitive information log, and the like, which can be used for data processing during subsequent system security determination.

Corresponding to the newly-added sensitive information stored in the sensitive information library, a corresponding newly-added sensitive information log may further be generated. The newly-added sensitive information log may include the number of the newly-added sensitive information, a value of the newly-added sensitive information, a variable name corresponding to the value, whether the newly-added sensitive information has been stored in the sensitive information library as well as a storage time, a generation time of the newly-added sensitive information log, and the like, which can be used for data processing during subsequent system security determination.

A sensitive information processing method including a sensitive information monitoring strategy of the present application can implement dynamic update of a sensitive information library, and can more accurately identify sensitive information in to-be-processed information, complete processing the sensitive information, and improve the security of sensitive information in a page.

Based on the idea of the present application, the present application provides a device for implementing sensitive information processing. <FIG> is a modular schematic structural diagram of an embodiment of a device for implementing sensitive information processing according to the present application. As shown in <FIG>, the device may include:.

In a specific embodiment, the to-be-processed information acquired by the information acquisition unit <NUM> may include:
variable information in a ModelMap in an MVC framework structure of a page server.

During specific processing, the sensitive information processing strategy stored by the processing strategy unit <NUM> may include:.

<FIG> is a modular schematic structural diagram of an embodiment of the sensitive information identification unit <NUM> in the device for implementing sensitive information processing according to the present application. As shown in <FIG>, the sensitive information identification unit <NUM> may include:.

In the foregoing first determination unit <NUM>, if the comparison result of the comparison unit <NUM> is that the variable name is the same as the sensitive information stored in the sensitive information library <NUM>, the first determination unit <NUM> determines that the to-be-processed information acquired by the information acquisition unit <NUM> is sensitive information; correspondingly. If the comparison unit <NUM> does not find sensitive information the same as the variable name after traversing the sensitive information stored in the sensitive information library <NUM>, the comparison result is that the variable name is not the same, and in this case, the first determination unit <NUM> determines that the to-be-processed information acquired by the information acquisition unit <NUM> is not sensitive information.

<FIG> is a modular schematic structural diagram of an embodiment of the processing strategy unit in the device for implementing sensitive information processing according to the present application. As shown in <FIG>, the processing strategy unit <NUM> may include at least one of the following units:.

The device for implementing sensitive information processing in this embodiment may obtain to-be-processed information in a page, and determine whether the to-be-processed information is sensitive information according to a preset sensitive information identification strategy. If yes, the device may process the to-be-processed information according to a preset sensitive information processing strategy, to complete identification and processing of the sensitive information.

In another preferred embodiment of the present application, the device for implementing sensitive information processing may further include a unit for maintaining the sensitive information in the sensitive information library. <FIG> is a modular schematic structural diagram of another embodiment of the device for implementing sensitive information processing according to the present application, and as shown in <FIG>, the device may include:.

Correspondingly, the sensitive information library <NUM> receives the variable name corresponding to the value of the variable information, and compares to see whether sensitive information the same as the variable name is stored in the sensitive information library <NUM>. If there is no sensitive information the same as the variable name in the sensitive information library <NUM>, the variable name may be stored.

<FIG> is another embodiment of the device for implementing sensitive information processing according to the present application. As shown in <FIG>, the device may include:
a substitution unit <NUM>, which substitutes the corresponding to-be-processed information in the page with the processed sensitive information.

In this embodiment, the device for implementing sensitive information processing substitutes, in the device, the corresponding to-be-processed information in the page with the processed sensitive information. In another implementation, the processed sensitive information is sent to the server, and the server substitutes the corresponding to-be-processed information in the page with the processed sensitive information, to form a page with the processed sensitive information. <FIG> is another embodiment of the device for implementing sensitive information processing according to the present application, and as shown in <FIG>, the device may further include:
a returning unit <NUM>, which directly sends the processed sensitive information to a server or to a processed sensitive information receiving unit of the server by using an interceptor.

The present application further provides a server for implementing sensitive information processing, and the server may include any one of the devices for implementing sensitive information processing described above.

Without using an interceptor, the server for implementing sensitive information processing provided by the present application may include:.

<FIG> is a modular schematic structural diagram of another embodiment of the server for implementing sensitive information processing according to the present application. The server may include an MVC framework structure. The server for implementing sensitive information processing in the present application may include any one of the foregoing devices for implementing sensitive information processing, and may include an interceptor in a preferred implementation. Specifically, as shown in <FIG>, the server may include:.

The foregoing MVC target system <NUM> may specifically include:.

The interceptor generally may include a preHandler (<NUM>), a postHandler (<NUM>), and an afterCompletion (<NUM>). In the server for implementing sensitive information processing of the present application, the acquiring, by the interceptor <NUM>, to-be-processed information in the page template ModelMap may include:
acquiring the to-be-processed information in the page template ModelMap by using a postHandle or afterCompletion processing program of the interceptor.

In the MVC target system, the to-be-processed information may include variable information in the ModelMap.

In the foregoing server for implementing sensitive information processing, the first processing strategy unit includes at least one of the following units:.

In the foregoing server for implementing sensitive information processing, the first sensitive information identification unit includes:.

In a preferred embodiment, the foregoing server for implementing sensitive information processing may further include:.

In a server for implementing sensitive information processing provided by the present application, when the MVC target system <NUM> receives an HTTP request of a user, the ModelMap module may generate a page template ModelMap, and then after the Controller module <NUM> in the MVC target system transmits information into a variable in the generated ModelMap, a postHandle processing program in postHandler of the interceptor <NUM> may acquire variable information in the ModelMap. Further, the interceptor may send the acquired variable information to the sensitive information processing module <NUM>, and the sensitive information processing module <NUM> may determine whether the variable information is sensitive information and process the sensitive information according to a preset sensitive information processing strategy, to form processed sensitive information. The MVC target system may receive the processed sensitive information sent by the sensitive information processing module <NUM> and may substitute corresponding to-be-processed information in the page template ModelMap with the processed sensitive information, to complete rendering of the page. Then the server may return the page with the processed sensitive information to a client terminal of the user by using the returning module <NUM>.

The MVC framework in the present application includes various spring mvc frameworks of a web application mode which are designed and created based on Model View Controller (MVC), for example, mvc framework structures such as sofa2, sofa3, and webx.

In a server for implementing sensitive processing provided by the present application, identification of sensitive information may be implemented on a server terminal, and information determined as sensitive information is processed on the server terminal according to a preset sensitive information processing strategy, such that sensitive information included in a page sent by the server to a browser on a client terminal of a user is processed sensitive information. An illegal user cannot acquire real sensitive information by means of data interception, local webpage modification, and the like, thus providing the security of sensitive information in a page.

According to the idea of identifying and processing the sensitive information in the sensitive information processing method, device and server of the present application, the present application further provides a security determination system, which may be used for determining whether a page server is secure and determining security performance of the page server, and may be further used for security comparison among multiple server systems and maintenance of a less secure server in time, to improve the security of the server. <FIG> is a modular schematic structural diagram of the security determination system according to the present application. As shown in <FIG>, the security determination system may include:.

The first security determination unit <NUM> may include at least one of the following units:.

Specifically, for example, when the security level of the first target system is determined according to the number of the newly-added sensitive information in the first time window, the numbers of newly-added sensitive information corresponding to different security levels may be predefined. For example, the number of the newly-added sensitive information may be less than <NUM> pieces in the fourth security level, may be <NUM> to <NUM> pieces in the third security level, may be <NUM> to <NUM> pieces in the second security level, and may be more than <NUM> pieces in the first security level. In another implementation, the security level of the first target system may be determined according to the ratio of the number of the newly-added sensitive information to the number of the to-be-processed sensitive information in the second time window. A larger value of the ratio, which indicates that more to-be-processed sensitive information in newly founded to-be-processed sensitive information has been processed or that to-be-processed sensitive information in newly founded to-be-processed sensitive information is processed more timely, which may be used to represent higher security of the system. Correspondingly, a smaller value of the ratio, which may indicate more to-be-processed sensitive information that has not been processed in the to-be-processed sensitive information, may represent lower security of the system. Certainly, corresponding security levels may be defined according to the ratio, and for details, reference may be made to other embodiments above.

<FIG> is a modular schematic structural diagram of another preferred embodiment of the security determination system according to the present application. As shown in <FIG>, the security determination system may further include a multi-system determination unit <NUM>, which compares the security level of the first target system with that of a second target system according to the preset determination rule. Correspondingly, the first security determination unit <NUM> may acquire data in the newly-added sensitive information log or the to-be-processed sensitive information log or the second sensitive information library of the second target system.

The multi-system determination unit <NUM> may include at least one of the following units:.

Specifically, for example, if it is obtained according to statistics that the number of the newly-added sensitive information of the first target system is greater than the number of the newly-added sensitive information of the second target system in one week, it may indicate that the security of the second target system is higher than that of the first target system. Certainly, if the ratio of the number of the newly-added sensitive information of the first target system to the number of the to-be-processed sensitive information is greater than the ratio of the number of the newly-added sensitive information of the second target system to the number of the to-be-processed sensitive information in a statistical cycle, it indicates that the first target processes the sensitive information in time and has higher security. It should be noted that, in the two manners above, the security level of the system is determined from different dimensions, for example, one system may include more newly-added sensitive information but the ratio is larger, which may indicate that initial security of the system is relatively low, but the security improves significantly due to timely maintenance.

A security determination system provided in the present application breaks away from the manner of determining whether a system is secure and a security level according to system vulnerabilities, the number of patches needing to be updated, and the like in the conventional techniques. The system for determining system security from the perspective of sensitive information provided in the present application can determine security performance of a target system according to sensitive information data that can be identified in the target system and whether the identified sensitive information is processed in time, and can make a more accurate security determination for the target system from the perspective of the essence of system security assessment. For example, if the target system can identify and process all sensitive information among a total of <NUM>,<NUM> pieces of sensitive information, or <NUM> among <NUM> pieces of newly found to-be-processed sensitive information are added to the second sensitive information library by means of an operation, even though it is determined in the conventional techniques that the target system has low security because there are M patches to be applied or N vulnerabilities in the target system, from the perspective of the essence of sensitive information identification and processing, the target system substantially is highly secure. By using the security determination system of the present application, the security of the target system can be determined more accurately. By using the present application, security of different target systems may be compared from different latitudes, and sensitive information of a less secure target system may be processed in time or other measures may be taken to maintain the target system, to improve the security of the system.

Although descriptions about protocols including HTTP are mentioned in the content of the present application, the present application is not limited to the case where the protocols including HTTP need to be completely standard. Some transmission mechanisms obtained after slight modifications on the protocol may also be used to implement the solutions of the foregoing embodiments of the present application, for example, a transmission protocol of HTTPS or HTTP release <NUM>. Certainly, even without using the HTTP protocol but using a private protocol, the same application can still be implemented as long as the protocol conforms to the page information interaction and information determination feedback manner in the foregoing embodiments of the present application; details are not described herein again.

The device or module illustrated in the foregoing embodiments may be specifically implemented by a computer chip or an entity, or implemented by a product with a particular function. For ease of description, the description of the device is divided, based on functions, into descriptions about various modules respectively. Certainly, in implementation of the present application, functions of the modules may be implemented in one or more pieces of software and/or hardware, or a module implementing one function may be implemented by a combination of multiple sub-modules or sub-units.

Those skilled in the art are also aware that, in addition to implementing the controller by using pure computer readable program code, logic programming may be performed on the methods and steps such that the controller implements the same function in the form of a logic gate, a switch, an application specific integrated circuit, a programmable logic controller, and an embedded microcontroller. Therefore, this kind of controller is deemed as a hardware component; and a device, which is included in the controller, for implementing various functions may also be deemed as an inner structure of the hardware component. Or even, the device for implementing various functions may be deemed as a software module for implementing the method, and deemed as an inner structure of the hardware component as well.

The present application may be described in the general context of computer executable instructions executed by a computer, for example, a program module. Generally, the program module includes a routine, a program, an object, a component or a data structure, a class, and the like for executing specific tasks or implementing specific abstract data types. The present application may also be realized in distributed computer environments. In such distributed computer environments, the tasks are executed by a remote processing device connected via a communications network. In the distributed computer environments, the program module may be located in local and remote computer storage media including a storage device.

Through the foregoing description of the foregoing implementations, those skilled in the art can clearly understand that the present application can be implemented by software plus a necessary universal hardware platform. Based on such understanding, the technical solution of the present application essentially, or the portion contributing to the conventional techniques may be embodied in the form of a software product. The software product may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, or an optical disc, and include several instructions that enable a computer device (which may be a personal computer, a mobile terminal, a server, or a network device) to execute the method in the embodiments or certain portions of the embodiments of the present application.

Claim 1:
A sensitive information processing method comprising:
acquiring (S1) to-be-processed information in a page requested by a user, the to-be-processed information including a variable information comprising a variable name and a value corresponding to the variable name;
determining (S2) that the to-be-processed information is sensitive information according to the variable name;
performing (S3) processing according to a preset sensitive information processing strategy to form processed sensitive information, the performing including setting the preset sensitive information processing strategy according to a privilege of a domain group to which a user name of the user belongs, different privileges corresponding to different preset sensitive information processing strategies for the value corresponding to the variable name; and
substituting (S4) the to-be-processed information in the page with the processed sensitive information, to form a page with the processed sensitive information.