WO2016034068A1 - 一种敏感信息处理方法、装置、服务器及安全判定*** - Google Patents

一种敏感信息处理方法、装置、服务器及安全判定*** Download PDF

Info

Publication number
WO2016034068A1
WO2016034068A1 PCT/CN2015/088214 CN2015088214W WO2016034068A1 WO 2016034068 A1 WO2016034068 A1 WO 2016034068A1 CN 2015088214 W CN2015088214 W CN 2015088214W WO 2016034068 A1 WO2016034068 A1 WO 2016034068A1
Authority
WO
WIPO (PCT)
Prior art keywords
sensitive information
information
processed
unit
variable
Prior art date
Application number
PCT/CN2015/088214
Other languages
English (en)
French (fr)
Inventor
张翔
吕建平
陈峥嵘
杨科
徐会卿
牟玮
王心刚
孙超
于晓雪
蒋琴飞
肖含笑
Original Assignee
阿里巴巴集团控股有限公司
张翔
吕建平
陈峥嵘
杨科
徐会卿
牟玮
王心刚
孙超
于晓雪
蒋琴飞
肖含笑
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司, 张翔, 吕建平, 陈峥嵘, 杨科, 徐会卿, 牟玮, 王心刚, 孙超, 于晓雪, 蒋琴飞, 肖含笑 filed Critical 阿里巴巴集团控股有限公司
Priority to JP2017512318A priority Critical patent/JP6626095B2/ja
Priority to SG11201701586RA priority patent/SG11201701586RA/en
Priority to EP15837690.5A priority patent/EP3190765A4/en
Publication of WO2016034068A1 publication Critical patent/WO2016034068A1/zh
Priority to US15/448,504 priority patent/US10505934B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • H04L63/0281—Proxies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
    • H04L2209/04—Masking or blinding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]

Definitions

  • the present application belongs to the field of information communication, and in particular relates to a sensitive information processing method, device, server and security determination system for computer page information interaction.
  • the main method includes sending an HTTP page request to the server through the client browser, and the server responds to the HTTP request and returns the requested page information to the client for browsing by the client user.
  • the page returned by the server often contains sensitive information related to the user, such as the user's account name, communication address, mobile phone number, ID card information, and the like.
  • the illegal user can obtain sensitive information on the page by viewing the source code of the page, the network capture packet, and the like, and the user information is leaked.
  • the information behind the "mailto:" in the page information or the information before and after the "@” can be extracted by the network tool to achieve the purpose of extracting the email information in the page.
  • a commonly used method for processing sensitive information includes encrypting, masking, or blocking an illegal user from capturing a page returned by a server by embedding a JavaScript script in a page.
  • the email sensitive information can be converted into an ASCII encoded string form, and then written into the page by the document.write method in the JavaScript scripting language to complete the processing of the sensitive information of the email.
  • the sensitive information in the page returned by the server is often the original sensitive information that has not been processed by the JavaScript script. Further, even if the sensitive information in the page is processed by the JavaScript script, the illegal user can pass the client. It is difficult to remove sensitive information in the page by deleting JavaScript scripts or preventing the corresponding JavaScript script from running. Therefore, the method for processing page sensitive information commonly used in the prior art leads to low security of sensitive information in the page.
  • the purpose of the present application is to provide a method, device, server and security determination system for sensitive information processing, which can improve the security of sensitive information in a page.
  • a method of sensitive information processing comprising:
  • processing is performed according to a preset sensitive information processing policy to form processed sensitive information
  • the processed sensitive information is replaced with corresponding pending information in the page to form a page after the sensitive information is processed.
  • An apparatus for implementing sensitive information processing comprising:
  • An information acquiring unit configured to acquire information to be processed in the page
  • a sensitive information base for storing sensitive information
  • a sensitive information identifying unit configured to determine, according to the sensitive information stored in the sensitive information base, whether the to-be-processed information is sensitive information
  • An information processing unit configured to: when the sensitive information identifying unit determines that the to-be-processed information is sensitive information, process the to-be-processed information based on a sensitive information processing policy stored by the processing policy unit to form processed sensitive information .
  • a server for implementing sensitive information processing comprising:
  • the MVC target system is configured to receive an HTTP request sent by the client, and generate a page template ModelMap according to the HTTP request; and further, send the to-be-processed information to the generated page template ModelMap, and complete the HTTP request phase And corresponding to the rendering of the page; the method is further configured to: send the rendered page to the client; and receive the processed sensitive information sent by the sensitive information processing module, and replace the processed sensitive information with the page template Corresponding pending information;
  • An interceptor configured to acquire the to-be-processed information in the page template ModelMap, and send the to-be-processed information to the sensitive information processing module; and further, receive the processed sensitive information sent by the sensitive information processing module, and The processed sensitive information is sent to the MVC target system;
  • the sensitive information processing module is configured to receive and determine whether the to-be-processed information is sensitive information, and is further configured to process the to-be-processed that is determined to be sensitive information according to a preset sensitive information processing policy, to form processed sensitive information;
  • the sensitive information processing module includes:
  • An information receiving unit configured to receive information to be processed
  • a first sensitive information base for storing sensitive information
  • a first sensitive information identifying unit configured to determine, according to the sensitive information stored in the first sensitive information database, whether the to-be-processed information is sensitive information
  • a first processing policy unit configured to store a sensitive information processing policy
  • a first information processing unit configured to: when the first sensitive information identifying unit determines that the to-be-processed information is sensitive information, process the to-be-processed information based on a sensitive information processing policy stored by the first processing policy unit Forming processed sensitive information;
  • the first backhaul unit is configured to send the processed sensitive information to the interceptor.
  • a security determination system comprising:
  • a second sensitive information base for storing sensitive information; and configured to receive a variable name sent by the second to-be-processed sensitive information unit, and determine whether the stored variable information includes the received variable name; If the result of the determination is that the variable name is not included in the sensitive information database, the variable name is stored as newly added sensitive information;
  • a second sensitive information identifying unit configured to acquire information to be processed in the page; and configured to determine, according to the sensitive information stored in the second sensitive information database, whether the to-be-processed information is sensitive information;
  • a second information processing unit configured to store a sensitive information processing policy, and configured to: when the second sensitive information identifying unit determines that the to-be-processed information is sensitive information, based on the stored sensitive information processing policy Processing information for processing to form processed sensitive information;
  • a monitoring unit configured to store a pre-set sensitive information monitoring policy; and configured to determine, according to the stored sensitive information monitoring policy, whether the value of the variable information of the ModelMap in the MVC framework structure of the page server is sensitive information to be processed; When determining that the value of the variable information is sensitive information to be processed, sending a variable name corresponding to the value of the variable information to the second sensitive information database;
  • the sensitive information log unit is configured to generate a log of the sensitive information to be processed, where the to-be-processed sensitive information log includes the number of sensitive information to be processed that is determined by the monitoring unit;
  • a first security determining unit configured to acquire the newly added sensitive information log of the first target system or the data of the to-be-processed sensitive information log or the second sensitive information database, and determine the according to a predetermined determination rule The security level to which the first target system belongs.
  • the method, device, server and security determination system for sensitive information processing can obtain information to be processed on the page server side, and determine whether the to-be-processed information is sensitive information according to a predetermined sensitive information identification policy.
  • the sensitive information may be processed according to a preset sensitive information processing policy, and then the processed sensitive information is returned to the page to form a page after the sensitive information is processed.
  • the page received by the client is a page that is processed by sensitive information on the server side. Even if the illegal user of the client uses the capture data packet or deletes the JavaScript script, the real sensitive information on the page cannot be obtained, and the security of the sensitive information in the page is improved. .
  • FIG. 1 is a schematic diagram of an interaction process between a user and a server in which the server of the present application adopts an MVC frame page structure
  • FIG. 2 is a flowchart of a method of an embodiment of a method for processing sensitive information according to the present application
  • FIG. 3 is a schematic flow chart of another embodiment of a method for processing sensitive information according to the present application.
  • FIG. 4 is a schematic structural diagram of a module for implementing an embodiment of a sensitive information processing apparatus according to the present application
  • FIG. 5 is a schematic structural diagram of a module for implementing a sensitive information identifying unit in a sensitive information processing apparatus according to the present application
  • FIG. 6 is a schematic structural diagram of a module for implementing a processing policy unit in a sensitive information processing apparatus according to the present application
  • FIG. 7 is a schematic structural diagram of a module of another embodiment of an apparatus for implementing sensitive information processing according to the present application.
  • FIG. 8 is a schematic structural diagram of a module of another apparatus for implementing sensitive information processing according to the present application.
  • FIG. 9 is a schematic structural diagram of a module of another embodiment of an apparatus for implementing sensitive information processing according to the present application.
  • FIG. 10 is a schematic structural diagram of a module of another embodiment of a server for implementing sensitive information processing according to the present application.
  • FIG. 11 is a block diagram showing the structure of an embodiment of a security determination system of the present application.
  • FIG. 12 is a block diagram showing another embodiment of a security determination system of the present application.
  • the MVC framework is a design creation mode of a web application commonly used by a web server to separate software business logic, data, and interface display using MVC (Model View Controller Model-View-Controller).
  • the Model can be used to encapsulate the data related to the business logic of the application and the processing method of the data, usually having direct access to the data, such as access to the database.
  • Views can be used for the display of data, usually the parts of the application that are relevant to the user interface, such as the page interface that users can browse and interact with.
  • the view can be created from the model data.
  • the Controller acts as an organization between different layers and can be used to handle events and respond.
  • the three modules of the MVC framework mode can be independent of each other, and one of them can be changed.
  • the MVC framework design pattern can be adopted on the server side.
  • the model can respond to the user's request and return response data.
  • the view can format the data and can be presented to the user interface's Internet interface and WAP interface.
  • FIG. 1 is a schematic diagram of an interaction process between a user and a server using a page structure of an MVC framework.
  • the user can send an HTTP request to the server through the client's browser.
  • the web server adopting the MVC framework mode When obtaining the HTTP request sent by the user through the browser, the web server adopting the MVC framework mode generates a corresponding page model according to the HTTP request, and then renders the generated page model.
  • the page model can generally be a pre-designed or system-stored page template (ModelMap), which can include variable information in the page template.
  • the rendering of the page model may include finding a variable information in the page template by a controller, and replacing the variable in the page module with the corresponding real data according to the HTTP request of the user.
  • the rendered page can be transmitted back to the user, and the view module can control the rendered interface on the display interface of the user client.
  • the present invention provides a method for processing sensitive information, which can process sensitive information of a user before the server returns a page to the user, so that the sensitive information contained in the page received by the user client is corresponding to the server. Handling sensitive information.
  • 2 is a flow chart of a method of an embodiment of a method for processing sensitive information according to the present application. As shown in FIG. 2, the method for processing sensitive information may include:
  • the to-be-processed information may be set according to a frame structure of the page server.
  • the to-be-processed information in this embodiment may include variable information of the ModelMap in the MVC framework structure of the page server.
  • the page server may create an empty ModelMap page template when receiving the HTTP request sent by the client.
  • the page template ModelMap can be a storage structure in the MVC framework structure, and can be used to store information that needs to be returned to the client in the page.
  • the page template ModelMap may include a variable, and the data format of the variable is usually a map (key: value) key-value pair data format including a variable name (key) and a value, wherein the value of the variable “value” is generally The null value or the default string is used to represent the initial value.
  • a variable set in ModelMap is (name1:value), and the value of the variable can be stored in the "name1" variable in the ModelMap by an operation such as ModelMap.put("name1", "Zhangsan”). three".
  • the data of the ModelMap can be obtained.
  • the variable information of the ModelMap in the MVC frame structure of the page server can be obtained, and the variable information in the ModelMap is obtained.
  • the variable information can be obtained while the page server stores the data in the variable in the page, or the variable information in the page can be obtained after the page server stores all the variables in the page.
  • the variable information may be obtained after the MVC framework stores the data of all the variables in the ModelMap, and the variable information is used as the information to be processed.
  • FIG. 3 is a schematic flowchart of another embodiment of a method for processing sensitive information according to the present application.
  • the obtaining information to be processed in the page in the method for processing sensitive information may include acquiring variable information in an MVC framework by using a postHandle handler of the interceptor, and the obtained variable information is to be processed. information. Specific can include:
  • the page server stores variable information in variables of ModelMap in the form of (variable name: value).
  • the MVC framework can send the ModelMap data to the interceptor, and the PostHandle handler of the interceptor receives the ModelMap data sent by the MVC framework.
  • the postHandle handler may traverse the variable information in the ModelMap, obtain a variable in the ModelMap, and use the acquired variable information as the information to be processed.
  • the interceptor can generally include means for intercepting an access source before an execution step or field of the application is accessed, and performing specific processing steps before or after the interception.
  • the interceptor can include three processing methods:
  • preHandle()--called before the Controller is called can be used to initialize the operation or pre-process the request;
  • postHandle()--called before rendering the view after the Controller is called can be used to process model data or views;
  • afterCompletion()--called after the view is rendered can be used for resource cleanup.
  • each processing method of the interceptor may be implemented by a corresponding processing unit.
  • the preHandle processing stage may be implemented by an entity device preHandler of the interceptor.
  • the postHandle processing stage may be implemented by an entity device postHandler of the interceptor.
  • the to-be-processed information that is, the variable information in the MVC frame structure ModelMap in this embodiment may be acquired in the postHandle or afterCompletion stage.
  • the preferred mode in this embodiment is that the information to be processed in the page can be acquired by the interceptor after the Controller is called in the MVC framework structure, and the discrimination processing of the sensitive information is involved.
  • the variable information in the ModelMap can be obtained by the interceptor's postHandle handler.
  • the information to be processed in the page may also be acquired by the interceptor after the rendering (Velocity) call in the MVC framework structure, that is, in the afterCompletion stage of the interceptor. Obtaining the to-be-processed information.
  • the method for acquiring and subsequently modifying the variable information in the ModelMap by the interceptor in this embodiment is applicable to other framework structures based on the MVC framework, such as a webx framework structure.
  • the corresponding interceptor may acquire and process the page before the page rendering (Velocity) and after the Controller is called.
  • the information to be processed may also be acquired and processed by the corresponding interceptor after the page rendering (Velocity).
  • a preferred embodiment is that the to-be-processed information is acquired and processed by the corresponding interceptor before the page is rendered (Velocity) and after the Controller is called.
  • variable information in the ModelMap in the page server MVC frame structure is obtained, and the variable information is used as the to-be-processed information in the page.
  • S2 Determine whether the to-be-processed information is sensitive information according to a preset sensitive information identification policy.
  • the sensitive information identification policy may be a preset set of discriminative rules or methods for determining whether the acquired information to be processed is sensitive information.
  • the sensitive information identification policy may include setting a sensitive information base for storing sensitive information.
  • the determining whether the to-be-processed information is sensitive information according to the pre-set sensitive information identification policy may include:
  • S202 Compare the variable name of the variable information in the acquired ModelMap with the sensitive information stored in the sensitive information base, and determine whether the variable name is in the sensitive information base;
  • S203 Determine whether the to-be-processed information is sensitive information according to whether the variable name is in the sensitive information database.
  • a sensitive information base including pre-defined sensitive information can be set.
  • the user's username, phone number, email, and ID number information may be pre-defined as sensitive information, and the corresponding variable names (User), "Tel_Num", and "" in the ModelMap may be used. E-Mail" and "ID_Num” are stored in advance in a sensitive information base.
  • the obtained variable name may be compared with the sensitive information stored in the sensitive information base. If the sensitive information database includes the same sensitive information as the obtained variable name, the information to be processed may be represented as sensitive information, that is, the variable information in the ModelMap corresponding to the variable name in the embodiment may be represented.
  • the information to be processed is not sensitive information, that is, it can be represented in the embodiment.
  • the variable information in the ModelMap corresponding to the variable name is not sensitive information.
  • the sensitive information stored in the sensitive information base described above can be added or deleted or modified according to requirements.
  • the acquired to-be-processed information may be other data formats corresponding to the server framework structure, and the sensitive information identification policy may also be based on the to-be-processed information and the server.
  • the framework performs corresponding settings, for example, whether the entire data of the to-be-processed information is sensitive information or whether the information to be encrypted is sensitive information based on the specified data.
  • the determining whether the to-be-processed information is sensitive information according to a preset sensitive information identification policy.
  • the information may be processed according to a preset sensitive information processing policy to form processed sensitive information.
  • the information to be processed may be processed according to a preset sensitive information processing policy.
  • the sensitive information processing policy may include a preset set of processing rules or methods for the information to be processed that are determined to be sensitive information.
  • the processing according to the preset sensitive information processing policy may include corresponding to the variable name in the variable information.
  • the value is processed.
  • the specific sensitive information processing strategy may include at least one of the following:
  • the non-processing may include not masking, transforming, or replacing the value corresponding to the variable name, and the value corresponding to the variable name is changed.
  • the predetermined portion of the presentation may include displaying a particular field of the value corresponding to the variable name according to a predetermined presentation rule.
  • a predetermined presentation rule For example, when the to-be-processed information is (Tel_Num: 15912344321), the predetermined display rule may include replacing the fourth to eighth bits of the value corresponding to the variable name "Tel: Num" with the character "*".
  • the above-mentioned to-be-processed information (Tel_Num: 15912344321) can be processed according to the processing strategy shown in the above predetermined part to form the processed sensitive information (Tel_Num: 159*****321).
  • the full masking may include masking all fields of the value corresponding to the variable name according to a predetermined masking rule.
  • the value corresponding to the variable name "Tel:Num” can be replaced by one or more "*" characters, and the processed sensitive information can be (Tel_Num:*) or (Tel_Num:******** ***).
  • the masking by the permission may include processing the value corresponding to the variable name according to the authority of the specified field.
  • the known field is the obtained user name of the client user, and the corresponding processing method may be set according to the permission of the different domain group where the user name is located.
  • the sensitive information may be processed according to the received authority of the user of the client that sent the HTTP request. For example, when the user name of the received HTTP request belongs to the super administrator domain group, all the sensitive information may not be processed; when the user name of the HTTP request belongs to the administrator domain group, the specified sensitive information may be set. Partially masked; the username for sending an HTTP request belongs to the user When you are in a domain group, you can set all or part of the specified sensitive information to be masked.
  • Table 1 Schematic diagram of the policy for processing policies by permission
  • variable name value Domain group Processing strategy Processed value Name1 Zhang San Super administrator Not processed Zhang San Name2 Li Si administrator Partial display Li* Name3 Wang Wu user shield ** Tel_Num 15912344321 user Partial display 159*****321 E-Mail [email protected] user Partial display Use**@163.com ID_Num 320322198708081234 administrator shield 320**** Add_ID Hangzhou, Zhejiang user Partial display Zhejiang province Gender Female user Not processed Female
  • the transformed display may include transforming a value corresponding to the variable name according to a predetermined transformation rule, and using the transformed value as the value of the variable name.
  • a predetermined transformation rule For example, the value "evil” in the fourth variable (Name4:evil) in the ModelMap is converted to "live” according to a predetermined rule as the value of the processed fourth variable, that is, the processed sensitive information can be (Name4:live).
  • the false alarm may be expressed as an abnormality in the identification rule of the sensitive information or the determined sensitive information does not meet the sensitivity information determination standard set according to other conditions, and the value corresponding to the variable name is not processed.
  • a false positive log can be generated.
  • the false alarm log may store the number of times the false alarm is generated and the target source of each false alarm (for example, the original variable name and value), the cause of the false alarm, the log generation time, and the like. In the embodiment, the generated false alarm log may be stored, which may be used for subsequent behavior statistics.
  • the sensitive information processing strategy may be set or nested according to requirements.
  • the processing according to the preset sensitive information processing policy may include:
  • a sensitive information processing policy is set on the value corresponding to the same variable name according to the authority of the specified field information in the same variable name of the variable information.
  • the user name, phone number, email, and ID number information of the user may be pre-defined as sensitive information, and the corresponding variable names (User), "Tel_Num” in the ModelMap, "E-Mail", "ID_Num”.
  • the value corresponding to the variable name "User” of the user name may be displayed according to the predetermined part of the processing policy setting according to the security level of the pre-set sensitive information, and only the first two characters are displayed, and the rest is used.
  • *" character substitution display the value corresponding to the variable name "E-Mail” of the user's email address according to the predetermined part
  • the processing policy setting only displays characters after the characters "@" and "@”.
  • the value corresponding to the variable name "ID_Num” of the ID number can be replaced by the 4-digit "*" character according to the full masking processing policy.
  • the sensitive information processing policy may also be set to the corresponding value of the same variable name according to the authority of the specified field information set in the same variable of the variable information.
  • the specified field may include specific field information in the acquired page, such as the username of the user who sent the HTTP request.
  • the sensitive information may be processed according to the acquired authority of the user who sends the HTTP request. For example, when the user who sends the HTTP request is an administrator authority, the value corresponding to the variable name "Tel_Num" of the user's phone number can be left unprocessed, and the administrator can view the complete phone number information in the final returned page.
  • the value corresponding to the variable name "Tel_Num" of the user's phone number may be displayed only according to the predetermined display rule, and only the first three digits and the last three digits of the phone number are displayed. The "*" character is substituted.
  • the information may be processed according to at least one sensitive information processing policy set in advance to form processed sensitive information.
  • the processed sensitive information may be sent to a corresponding location of the to-be-processed information corresponding to the page, replacing the original in the page. Pending information.
  • the value-replaced variable may be returned to the ModelMap of the MVC server framework structure, and the value is replaced in the MVC framework.
  • the variables are rendered on the page. Specifically, for example, when the VM page template is rendered, the value of the variable name of the variable information in the ModelMap and the variable information of the processed sensitive information variable name may be replaced with the variable name of the processed sensitive information. Value.
  • the value "Li*" of the processed sensitive information can be replaced by the value "Li Si" of the variable (Name2: Li Si) in the ModelMap.
  • the information to be encrypted may not need to be processed. Specifically, it may not be needed in this embodiment. Replace the value of the variable in the ModelMap.
  • the sensitive information processed page can be transmitted back to the client browser.
  • the client receives the sensitive information processed page, it displays to the user a page that has processed sensitive information. For example, in the module display area displaying the currently logged-in user name, the user name "Li Si" originally to be displayed may be displayed as "Li*" after the sensitive information is processed to the client user.
  • the method for processing sensitive information may obtain the information to be processed on the page server side, and determine whether the to-be-processed information is sensitive information according to a predetermined sensitive information identification policy. Sensitive to the information to be processed When the information is sensed, the sensitive information can be processed according to the pre-set sensitive information processing strategy, and then the processed sensitive information is returned to the page, and the sensitive information processed page can be formed.
  • the sensitive information included in the processed page after the sensitive information is the corresponding processed information on the server side, and even if the illegal user of the client uses the captured data packet or deletes the JavaScript script, the real sensitive information in the page cannot be obtained, and the improved information is improved. The security of sensitive information on the page.
  • the HTTP request page sent by the client user may include multiple sensitive information to be identified and processed.
  • the sensitive information may appear in different locations of different request pages, and may also correspond to different variables in the MVC framework structure ModelMap.
  • the sensitive information processing increases the difficulty of identifying sensitive information.
  • Different page servers or different design developers based on the MVC framework can set different variable names in the ModelMap for the same sensitive information, such as the user's email address and ID number.
  • the variable corresponding to the ID number variable information is named “ID_Num”
  • the variable name corresponding to the ID number variable information in the ModelMap may be “Num_001”.
  • the present application provides another embodiment of a dynamic sensitive information processing method.
  • the sensitive information identification policy can be dynamically adjusted according to a preset sensitive information monitoring policy.
  • the method for processing sensitive information may further include:
  • variable name corresponding to the value of the variable information is sent to the sensitive information database.
  • whether the value of the variable information in the ModelMap is sensitive information to be processed may be determined according to a preset sensitive information monitoring policy.
  • the sensitive information usually has a certain data structure format.
  • the mobile phone number can usually be a combination of numbers of 11 digits starting with a non-zero, and the email address can include the "@" character.
  • the sensitive information monitoring strategy may match whether the value of the variable information in the ModelMap conforms to a preset number combination of 11 digits by a regular matching method, or determine whether the value of the variable information in the ModelMap contains the “@” character. And there is at least one non-empty character before "@".
  • the variable name “Phone_Num” or “First_Contact” corresponding to the value of the variable information may be sent to the sensitive In the information library.
  • the sensitive information base may receive the variable name "Phone_Num” or “First_Contact” corresponding to the value of the variable information, and compare whether the sensitive information in the sensitive information base is the same as the variable name. If the sensitive information database does not have the same sensitive information as the variable name, the variable name not included in the sensitive information database but corresponding to the sensitive information to be processed may be stored as new sensitive information. In the sensitive information base.
  • variable name “Phone_Num” or “First_Contact” may be used by the sensitive information monitoring policy.
  • Handling sensitive information Add new sensitive information to the sensitive repository. The next time the user HTTP request is responded, the sensitive information with the variable name "Phone_Num” or “First_Contact” can be identified, and the value corresponding to the variable name "Phone_Num” or "First_Contact” can be processed according to the sensitive information processing policy. .
  • a corresponding log of sensitive information to be processed may also be generated.
  • the to-be-processed sensitive information log may include the number of sensitive information to be processed, the value of the sensitive information to be processed, the variable name corresponding to the value, whether it has been sent to the sensitive information database, and the processing time of each sensitive information to be processed. Handling sensitive information log generation time, etc., can be used for data processing in subsequent system security decisions.
  • the corresponding new sensitive information log may also be generated.
  • the newly added sensitive information log may include the number of newly added sensitive information, the value of the newly added sensitive information, the variable name corresponding to the value, whether it is already stored in the sensitive information base, and the storage time, adding sensitive information. Log generation time, etc., can be used for data processing in subsequent system security decisions.
  • a sensitive information processing method including a sensitive information monitoring process can implement dynamic update of a sensitive information base, which can more accurately identify sensitive information in the information to be processed, complete processing of sensitive information, and improve page sensitivity. Information security.
  • FIG. 4 is a schematic structural diagram of a module for implementing an embodiment of a sensitive information processing apparatus according to the present application. As shown in FIG. 4, the apparatus may include:
  • the information obtaining unit 101 may be configured to acquire information to be processed in the page;
  • the sensitive information base 102 can be used to store sensitive information
  • the sensitive information identifying unit 103 may be configured to determine, according to the sensitive information stored in the sensitive information base 102, whether the to-be-processed information is sensitive information;
  • the processing policy unit 104 can be configured to store a sensitive information processing policy.
  • the information processing unit 105 may be configured to process the to-be-processed information based on the sensitive information processing policy stored by the processing policy unit 104 when the sensitive information identifying unit 103 determines that the to-be-processed information is sensitive information. Sensitive information has been processed.
  • the information to be processed acquired by the information acquiring unit 101 may include:
  • ModelMap in the page server MVC framework structure.
  • the specific information processing policy that the processing policy unit 104 stores may include:
  • a sensitive information processing policy is set on the value corresponding to the same variable name according to the authority of the specified field information in the same variable name of the variable information.
  • FIG. 5 is a block diagram showing a structure of an embodiment of a sensitive information identifying unit 103 in a sensitive information processing apparatus according to the present application.
  • the sensitive information identifying unit 103 may include:
  • the key value obtaining unit 1031 may be configured to obtain a variable name of the variable information in the page server MVC frame structure ModelMap;
  • the comparing unit 1032 is configured to compare whether the variable name of the variable information in the acquired ModelMap is the same as the sensitive information stored in the sensitive information base 102;
  • the first determining unit 1033 may be configured to determine, according to the comparison result of the comparing unit 1032, whether the to-be-processed information is sensitive information.
  • the first determining unit 1033 may determine the information acquiring unit 101.
  • the obtained information to be processed is sensitive information.
  • the comparison unit 1032 traverses the sensitive information stored in the sensitive information base 102 and does not query the same sensitive information as the variable name, the comparison result is different.
  • the first determining unit 1033 may determine that the to-be-processed information acquired by the information acquiring unit 101 is not sensitive information.
  • FIG. 6 is a schematic structural diagram of a module of an embodiment of a processing policy unit in an apparatus for implementing sensitive information processing according to the present disclosure.
  • the processing policy unit 104 may include at least one of the following units:
  • the predetermined part display unit 1041 may be configured to display a specific field of the value corresponding to the variable name according to a predetermined display rule
  • the full masking unit 1042 can be configured to mask all fields of the value corresponding to the variable name according to a predetermined masking rule
  • the privilege masking unit 1043 may be configured to process the value corresponding to the variable name according to the privilege of the specified field. Specifically, for example, the user with high authority may be unmasked or partially shielded from the specified sensitive information, and the user with relatively low authority may be partially shielded or completely shielded from the specified sensitive information.
  • the transformation display unit 1044 may be configured to transform the value corresponding to the variable name according to a predetermined transformation rule, and use the transformed value as the value of the variable name.
  • the false alarm unit 1045 may be configured to: when an abnormality occurs in any one of the structural modules in the sensitive information processing device or the sensitive information determined by the sensitive information identifying unit 103 does not meet the sensitive information determination standard set by the third party module, The value corresponding to the variable name is not processed, and a false alarm log is generated.
  • the third-party module setting may include other modules disposed in or outside the sensitive information processing device to determine whether the to-be-processed information is sensitive information. If the method for identifying sensitive information by the device for implementing sensitive information processing conflicts with the method for identifying sensitive information by other modules, the sensitive information may be set as a false alarm, and the data processing of the sensitive information may not be performed.
  • the character “@” is included to determine that the corresponding to-be-processed information is the sensitivity of the user's email.
  • the information is sensed, and according to the third-party module, the information to be processed corresponding to the variable is determined to be a comment of the seller input by the user in the text box, which is not the set sensitive information.
  • the false alarm unit 1045 of the sensitive information processing apparatus may perform processing such as masking, transforming, and the like on the to-be-processed information, and may record the log of the false alarm.
  • the apparatus for implementing sensitive information processing in the embodiment may obtain the to-be-processed information in the page, and determine whether the to-be-processed information is sensitive information according to a preset sensitive information identification policy. If yes, the to-be-processed information may be processed according to a preset sensitive information processing policy, and the identification and processing of the sensitive information is completed.
  • the apparatus for implementing sensitive information processing may further include means for maintaining sensitive information in the sensitive information base.
  • FIG. 7 is a schematic structural diagram of another embodiment of an apparatus for implementing sensitive information processing according to the present application. As shown in FIG. 7, the apparatus may include:
  • the monitoring policy unit 106 can be configured to store a preset sensitive information monitoring policy.
  • the to-be-processed sensitive information unit 107 may be configured to determine, according to a preset sensitive information monitoring policy, whether the value of the variable information of the ModelMap in the MVC framework structure of the page server is sensitive information to be processed;
  • the sending unit 108 may be configured to: when the to-be-processed sensitive information unit 107 determines that the value of the variable information is the sensitive information to be processed, send a variable name corresponding to the value of the variable information to the sensitive information base 102. .
  • the sensitive information base 102 can receive a variable name corresponding to the value of the variable information, and compare whether the sensitive information in the sensitive information base 102 is the same as the variable name. If the sensitive information base 102 does not have the same sensitive information as the variable name, the variable name may be stored.
  • FIG. 8 is another embodiment of a device for implementing a sensitive information according to the present application. As shown in FIG. 8, the device may further include:
  • the replacing unit 109 may replace the corresponding pending information in the page with the processed sensitive information.
  • the device for implementing sensitive information processing may replace the processed sensitive information in the device with corresponding pending information in the page.
  • the processed sensitive information may be sent to a server, and the processed sensitive information is replaced by the server to replace the corresponding pending information in the page to form a page after the sensitive information is processed.
  • FIG. 9 is another embodiment of a device for implementing a sensitive information according to the present application. As shown in FIG. 9, the device may further include:
  • the backhaul unit 110 can be configured to send the processed sensitive information to the server or to the processed sensitive information receiving unit of the server through the interceptor.
  • the present application further provides a server for implementing sensitive information processing, and the server may include the apparatus for implementing sensitive information processing according to any one of the above embodiments.
  • a server for implementing sensitive information processing may include:
  • a first MVC target system configured to receive an HTTP request sent by the client, and according to the HTTP request Generating a page template ModelMap; can also be used to pass the to-be-processed information to the generated page template ModelMap, complete rendering of the HTTP request page; and can also be used to send the rendered page to the client; And receiving the processed sensitive information sent by the sensitive information processing module, and replacing the processed sensitive information with the corresponding pending information in the page template ModelMap;
  • the first sensitive information processing module may be configured to obtain the to-be-processed information in the page template ModelMap, and determine whether the to-be-processed information is sensitive information according to a preset sensitive information identification policy; When the processing information is sensitive information, it is processed according to a preset sensitive information processing policy to form processed sensitive information; and may also be used to send the processed sensitive information to the MVC target system.
  • FIG. 10 is a schematic structural diagram of a module of another embodiment of a server for implementing sensitive information processing according to the present application.
  • the server may include an MVC framework structure.
  • a server for implementing sensitive information processing as described in the present application may include the implementation of the sensitive information processing apparatus according to any one of the preceding claims, and the preferred embodiment may include an interceptor.
  • the server may include:
  • the MVC target system 1 may be configured to receive an HTTP request sent by the client, and generate a page template ModelMap according to the HTTP request, and may further be configured to: pass the to-be-processed information into the generated page template ModelMap, and complete the The rendering of the HTTP request page; can also be used to send the rendered page to the client; and can also be used to receive the processed sensitive information sent by the sensitive information processing module, and replace the processed sensitive information with the page template ModelMap Corresponding pending information;
  • the interceptor 2 is configured to obtain the to-be-processed information in the page template ModelMap, and send the to-be-processed information to the sensitive information processing module 3; and may also be configured to receive the processed sensitive information sent by the sensitive information processing module 3, And sending the processed sensitive information to the MVC target system 1;
  • the sensitive information processing module 3 can be configured to receive and determine whether the to-be-processed information is sensitive information, and is further configured to process the to-be-processed information that is determined to be sensitive information according to a preset sensitive information processing policy, to form a processed sensitive information.
  • the sensitive information processing module may include:
  • An information receiving unit configured to receive information to be processed
  • a first sensitive information base that can be used to store sensitive information
  • the first sensitive information identifying unit may be configured to determine, according to the sensitive information stored in the first sensitive information database, whether the to-be-processed information is sensitive information;
  • the first processing policy unit can be used to store a sensitive information processing strategy
  • the first information processing unit may be configured to: when the first sensitive information identifying unit determines that the to-be-processed information is sensitive information, perform the to-be-processed information based on a sensitive information processing policy stored by the first processing policy unit Processing to form processed sensitive information;
  • the first backhaul unit can be configured to send the processed sensitive information to the interceptor.
  • the MVC target system 1 described above may specifically include:
  • the ModelMap module 11 can be configured to receive an HTTP request sent by the client, and generate a page template ModelMap according to the HTTP request;
  • the controller module 12 may be configured to: forward the to-be-processed information to the generated page template ModelMap; and may further be configured to receive the processed sensitive information sent by the interceptor;
  • the Velocity module 12 may be configured to replace the processed sensitive information received by the Controller module 12 with the corresponding pending information in the page template ModelMap; and may also be used to complete rendering of the corresponding page of the HTTP request;
  • the passback module 14 can be used to send the rendered page to the client.
  • the interceptor can typically include preHandler (21), postHandler (22), and afterCompletion (23).
  • the interceptor 2 obtains the to-be-processed information in the page template ModelMap, which may include:
  • the to-be-processed information in the page template ModelMap is obtained by the postHandle or afterCompletion handler of the interceptor.
  • the to-be-processed information may include variable information of the ModelMap.
  • the first processing policy unit includes at least one of the following units:
  • a first predetermined part display unit configured to display a specific field of a value corresponding to the variable name according to a predetermined display rule
  • a first complete masking unit configured to mask all fields of the value corresponding to the variable name according to a predetermined masking rule
  • the first authority screening unit may be configured to process the value corresponding to the variable name according to the authority of the specified field;
  • a first transformation display unit configured to convert a value corresponding to the variable name according to a predetermined transformation rule, and use the transformed value as a value of the variable name
  • the first false alarm unit may be configured to: when an abnormality occurs in any one of the structural modules in the sensitive information processing device or the sensitive information determined by the sensitive information identifying unit does not meet the sensitive information judgment standard set by the third party module, The value corresponding to the variable name is not processed, and a false alarm log is generated.
  • the server for implementing sensitive information processing, the first sensitive information identifying unit includes:
  • a first key value obtaining unit configured to acquire a variable name of the variable information in the ModelMap in the MVC target system
  • a first comparison unit configured to compare whether a variable name of the variable information in the acquired ModelMap is the same as a sensitive information stored in the first sensitive information repository
  • the second determining unit may be configured to determine, according to the comparison result of the first comparing unit, whether the to-be-processed information is sensitive information.
  • the server that implements the sensitive information processing described above may further include:
  • the first monitoring policy unit can be used to store a preset sensitive information monitoring policy
  • the first to-be-processed sensitive information unit may be configured to determine, according to a preset sensitive information monitoring policy, whether the value of the variable information of the ModelMap in the MVC target system is sensitive information to be processed;
  • the first sending unit may be configured to: when the first to-be-processed sensitive information unit determines that the value of the variable information is the sensitive information to be processed, send a variable name corresponding to the value of the variable information to the first Sensitive information base.
  • the MVC target system 1 can generate a page template ModelMap by the ModelMap module after receiving the HTTP request of the user, and then the Controller module 12 in the MVC target system generates the template.
  • the variable information in the ModelMap can be obtained by the postHandle handler in the postHandler of the interceptor 2. Further, the interceptor may send the acquired variable information to the sensitive information processing module 3, and the sensitive information processing module 3 may determine whether the variable information is sensitive information, and process the sensitive information according to a predetermined sensitive information processing policy. Forming processed sensitive information.
  • the MVC target system may receive the processed sensitive information sent by the sensitive information processing module 3, and replace the processed sensitive information with the corresponding pending information in the page template ModelMap to complete rendering of the page.
  • the server can then pass the sensitive information processed page back to the user's client through the backhaul module 14.
  • the MVC framework described in this application includes various spring mvc frameworks for creating web application patterns based on MVC (Model View Controller Model-View-Controller) design, such as mvc framework structures such as sofa2, sofa3 or webx.
  • MVC Model View Controller Model-View-Controller
  • the server for implementing sensitive processing can implement the identification of sensitive information on the server side, and process the information determined to be sensitive information on the server side according to the preset sensitive information processing policy, so that the server sends the information to the user.
  • the sensitive information included in the client browser's page is sensitive information that has been processed. Illegal users cannot obtain real sensitive information through data interception, local web page modification, etc., and provide security for sensitive information on the page.
  • the method for identifying and processing the sensitive information the application further provides a security determination system, which can be used to determine whether the page server is secure and determine the page.
  • Server security performance can also be used to compare security between multiple server systems, maintain servers with lower security in time, and improve server security.
  • 11 is a block diagram of a security judgment system according to the present application. As shown in FIG. 11, the security determination system may include:
  • the second sensitive information database 201 may be configured to store the sensitive information; and may be further configured to receive the variable name sent by the second to-be-processed sensitive information unit 205, and determine whether the stored variable information includes the received variable name; The method may further be configured to store the variable name as the newly added sensitive information when the determination result is that the received variable name is not included in the sensitive information base;
  • the second sensitive information identifying unit 202 may be configured to obtain the to-be-processed information in the page; and may be further configured to determine, according to the sensitive information stored in the second sensitive information database 201, whether the to-be-processed information is sensitive information;
  • the second information processing unit 203 may be configured to store the sensitive information processing policy, and may be further configured to: when the second sensitive information identifying unit 202 determines that the to-be-processed information is sensitive information, based on the stored sensitive information processing strategy Processing the to-be-processed information to form processed sensitive information;
  • the monitoring unit 204 may be configured to store a pre-set sensitive information monitoring policy.
  • the method may further be configured to determine, according to the stored sensitive information monitoring policy, whether the value of the variable information of the ModelMap in the MVC framework structure of the page server is sensitive information to be processed. And when it is determined that the value of the variable information is to be processed sensitive information, the variable name corresponding to the value of the variable information is sent to the second sensitive information database 201;
  • the new sensitive information log unit 205 may be configured to generate a new sensitive information log, where the newly added sensitive information log may include the number of the newly added sensitive information in the second sensitive information database 201;
  • the to-be-processed sensitive information log unit 206 may be configured to generate a to-be-processed sensitive information log, where the to-be-processed sensitive information log may include the number of sensitive information to be processed determined by the monitoring unit 204;
  • the first security determining unit 207 may be configured to obtain the newly added sensitive information log of the first target system or the data of the to-be-processed sensitive information log or the second sensitive information database, and determine according to a predetermined determination rule. The security level to which the first target system belongs.
  • the first security determining unit 207 may include at least one of the following units:
  • the first number determining unit may be configured to determine a security level of the first target system according to the number of the newly added sensitive information in the first time window/the number of sensitive information stored in the second sensitive information database;
  • the first ratio determining unit may determine the security level of the first target system according to a ratio of the number of the newly added sensitive information in the second time window to the number of the sensitive information to be processed.
  • the security level of the first target system 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 number of new sensitive information corresponding to different security levels may be pre-division, for example, the fourth.
  • the security level includes 100 or less.
  • the third security level can be 100 to 1000.
  • the second security level can be 100 to 5000.
  • the first security level is 5000 or more.
  • the security level of the first target system may be determined according to a ratio of the number of the newly added sensitive information in the second time window to the number of the sensitive information to be processed.
  • the ratio the more sensitive information to be processed in the newly discovered sensitive information to be processed More or more timely, it can be used to indicate that the security of the system is higher; correspondingly, the smaller the ratio, the more sensitive information that can be processed without being processed, the lower the security of the system can be expressed.
  • the corresponding security level may be divided according to the ratio.
  • FIG. 12 is a schematic structural diagram of another preferred embodiment of a security determination system according to the present application.
  • the security determination system may further include a multi-system determination unit 208, and may also be used according to FIG.
  • the predetermined determination rule compares the security levels of the first target system and the second target system; correspondingly, the first security determining unit 207 may obtain the newly added sensitive information log of the second target system or the to-be-processed Sensitive information log or data in the second sensitive information base.
  • the multi-system determination unit 208 can include at least one of the following units:
  • the second number determining unit may be configured to compare the number of new sensitive information of the first target system and the second target system/the number of sensitive information stored in the second sensitive information database in the first time window.
  • the second ratio determining unit may compare the first target system with the ratio of the number of new sensitive information of the first target system and the second target system to the number of the sensitive information to be processed in the second time window.
  • the security level of the second target system may be used to determine whether the second target system has a security level.
  • the number of new sensitive information added by the first target system in one week is greater than the number of new sensitive information in the second target system, which may indicate that the security of the second target system is higher than the first A target system.
  • the ratio of the number of new sensitive information added by the first target system to the number of sensitive information to be processed in the statistical period is greater than the number of new sensitive information in the second target system and the sensitivity to be processed.
  • the ratio of the number of information may indicate that the first target processes the sensitive information in time and has higher security. It should be noted that the above two methods are to determine the security level of the system from different dimensions. For example, the same system may include more new sensitive information but the ratio is larger, which may indicate that the initial security of the system is lower. However, due to timely maintenance, the safety growth is higher.
  • the security determination system provided by the present application discards the system vulnerabilities existing in the target system and the number of patches that need to be updated in the prior art to determine whether the system is safe and high.
  • the system for determining system security from the perspective of sensitive information provided by the present application can determine the security performance of the target system from the sensitive information data that can be identified in the target system and the processing of the identified sensitive information in time. From the nature of assessing the security of the system, a more accurate security decision is made on the target system.
  • the target system can identify and process all of the total sensitive information of 100,000 pieces of sensitive information, or 99 of the newly discovered 100 pieces of pending sensitive information are added to the second sensitive information base by operation, Even in the prior art, since the target system has M patches that are not hit or there are N vulnerabilities, the security of the target system is low, but the target system is determined from the essential level of the identification and processing of sensitive information.
  • the security of the target system described above is high. Utilizing a security determination system described in the present application More accurate determination of the security of the target system. With this application, the security of different target systems can be compared from different latitudes. For a target system with lower security, the sensitive information can be processed in time or other measures can be taken to maintain the target system, which can improve the security of the system.
  • the present application is not limited to the case of a protocol which must be a fully compliant HTTP.
  • the slightly modified transmission mechanism based on some protocols may also implement the above embodiments of the present application, such as HTTPS or HTTP 2.0 version transmission protocol.
  • HTTPS HyperText Transfer Protocol
  • HTTP 2.0 version transmission protocol a protocol which must be a fully compliant HTTP.
  • the same application can be implemented as long as the page information interaction and the information judgment feedback mode are consistent with the foregoing embodiments of the present application, and details are not described herein again.
  • the apparatus or module illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product having a certain function.
  • the above devices are described as being separately divided into various modules by function.
  • the functions of the modules may be implemented in the same software or software and/or hardware when implementing the present application, or the modules implementing the same functions may be implemented by multiple sub-modules or a combination of sub-units.
  • the controller can be logically programmed by means of logic gates, switches, ASICs, programmable logic controllers, and embedding.
  • the application can be described in the general context of computer-executable instructions executed by a computer, such as a program module.
  • program modules include routines, programs, objects, components, data structures, classes, and the like that perform particular tasks or implement particular abstract data types.
  • the present application can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are connected through a communication network.
  • program modules can be located in both local and remote computer storage media including storage devices.
  • the present application can be implemented by means of software plus a necessary general hardware platform. Based on such understanding, the technical solution of the present application may be embodied in the form of a software product in essence or in the form of a software product, which may be stored in a storage medium such as a ROM/RAM or a disk. , an optical disk, etc., includes instructions for causing a computer device (which may be a personal computer, mobile terminal, server, or network device, etc.) to perform the methods described in various embodiments of the present application or portions of the embodiments.
  • a computer device which may be a personal computer, mobile terminal, server, or network device, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Storage Device Security (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • User Interface Of Digital Computer (AREA)
  • Telephonic Communication Services (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

一种敏感信息处理方法、装置、服务器及安全判定***。所述方法包括：获取页面中的待处理信息（S1）；根据预先设置的敏感信息识别策略判断所述待处理信息是否为敏感信息（S2）；在所述待处理信息为敏感信息时，按照预先设置的敏感信息处理策略进行处理，形成已处理敏感信息（S3）；将所述已处理敏感信息替换所述页面中相应的待处理信息，形成敏感信息处理后的页面（S4）。利用该方法、装置、服务器及安全判定***可以在服务器端完成对回传给用户的页面中敏感信息的识别、处理，可以提高页面中敏感信息的安全性。

Description

一种敏感信息处理方法、装置、服务器及安全判定*** 技术领域
本申请属于信息通信领域，尤其涉及计算机页面信息交互中一种敏感信息处理方法、装置、服务器及安全判定***。
背景技术
随着信息科技的发展，通过互联网获取信息已经成为人们获取信息的一种重要方式。其中主要的方式中包括通过客户端浏览器发送HTTP页面请求至服务器，由服务器响应HTTP请求并将请求的页面信息返回至客户端，供客户端的用户浏览。
所述服务器返回的页面中常常包含与用户个人有关的敏感信息，例如用户的账号名称、通信地址、手机号码、身份证信息等。而非法用户可以通过查看页面源代码、网络抓取数据包等简单易行的方式获取页面中的敏感信息，导致用户信息泄露。例如可以通过网络工具提取页面信息中“mailto：”后面的信息或者“@”前后的信息达到提取页面中的Email信息的目的。
现有技术中，常用的对敏感信息处理的方法包括通过嵌入页面中JavaScript脚本对敏感进行加密、屏蔽，或者阻止非法用户对服务器返回的页面进行抓包等处理方法。例如可以将Email敏感信息转换成ASCII编码的字符串形式，然后用JavaScript脚本语言中的document.write方法写入到页面中，完成对电子邮箱敏感信息的处理。
但是，现有技术中，服务器返回的页面中的敏感信息常常是未经过JavaScript脚本处理的原始敏感信息，进一步的，即使页面的中的敏感信息通过JavaScript脚本处理，非法用户也可以在客户端通过删除JavaScript脚本或阻止相应的JavaScript脚本的运行等低难度手段获取页面中的敏感信息。因此，现有技术常用的对页面敏感信息的处理方法的导致页面中敏感信息的安全性较低。
发明内容
本申请目的在于提供一种敏感信息处理的方法、装置、服务器及安全判定***，可以提高页面中敏感信息的安全性。
本申请提供的一种敏感信息处理的方法、装置、服务器及安全判定***是这样实现的：
一种敏感信息处理的方法，所述方法包括：
获取页面中的待处理信息；
根据预先设置的敏感信息识别策略判断所述待处理信息是否为敏感信息；
在所述待处理信息为敏感信息时，按照预先设置的敏感信息处理策略进行处理，形成已处理敏感信息；
将所述已处理敏感信息替换所述页面中相应的待处理信息，形成敏感信息处理后的页面。
一种实现敏感信息处理的装置，所述装置包括：
信息获取单元，用于获取页面中的待处理信息；
敏感信息库，用于存储敏感信息；
敏感信息识别单元，用于基于所述敏感信息库中存储的敏感信息判断所述待处理信息是否为敏感信息；
处理策略单元，用于存储敏感信息处理策略；
信息处理单元，用于在所述敏感信息识别单元判断所述待处理信息为敏感信息时，基于所述处理策略单元存储的敏感信息处理策略对所述待处理信息进行处理，形成已处理敏感信息。
一种实现敏感信息处理的服务器，所述服务器包括：
MVC目标***，用于接收客户端发送的HTTP请求，并根据所述HTTP请求生成页面模版ModelMap；还用于向所述生成的页面模版ModelMap中传入待处理信息，完成对所述HTTP请求相对应的页面的渲染；还用于将渲染后的页面发送至客户端；还用于接收敏感信息处理模块发送的已处理敏感信息，并将所述已处理敏感信息替换所述页面模版ModelMap中相对应的待处理信息；
***，用于获取所述页面模版ModelMap中的待处理信息，并将所述待处理信息发送至敏感信息处理模块；还用于接收敏感信息处理模块发送的已处理敏感信息，并将所述已处理敏感信息发送至所述MVC目标***；
敏感信息处理模块，用于接收并判断所述待处理信息是否为敏感信息；还用于按照预先设置的敏感信息处理策略对所述判断为敏感信息的待处理进行处理，形成已处理敏感信息；
所述敏感信息处理模块包括：
信息接收单元，用于接收待处理信息；
第一敏感信息库，用于存储敏感信息；
第一敏感信息识别单元，用于基于所述第一敏感信息库中存储的敏感信息判断所述待处理信息是否为敏感信息；
第一处理策略单元，用于存储敏感信息处理策略；
第一信息处理单元，用于在所述第一敏感信息识别单元判断所述待处理信息为敏感信息时，基于所述第一处理策略单元存储的敏感信息处理策略对所述待处理信息进行处理，形成已处理敏感信息；
第一回传单元，用于将所述已处理敏感信息发送至***。
一种安全判定***，所述***包括：
第二敏感信息库，用于存储敏感信息；还用于接收第二待处理敏感信息单元发送的变量名，并判断所述存储的敏感信息中是否包括所述接收的变量名；还用于在所述判断结果为所述敏感信息库中不包括所述接收的变量名时，将所述变量名作为新增敏感信息进行存储；
第二敏感信息识别单元，用于获取页面中的待处理信息；还用于基于所述第二敏感信息库中存储的敏感信息判断所述待处理信息是否为敏感信息；
第二信息处理单元，用于存储敏感信息处理策略；还用于在所述第二敏感信息识别单元判断所述待处理信息为敏感信息时，基于所述存储的敏感信息处理策略对所述待处理信息进行处理，形成已处理敏感信息；
监控单元，用于存储预先设置的敏感信息监控策略；还用于根据所述存储的敏感信息监控策略判断所述页面服务器MVC框架结构中ModelMap的变量信息的值是否为待处理敏感信息；还用于在判断所述变量信息的值为待处理敏感信息时，将与所述变量信息的值相对应的变量名发送至所述第二敏感信息库；
新增敏感信息日志单元，用于生成新增敏感信息日志，所述新增敏感信息日志包括所述第二敏感信息库中新增敏感信息的数目；
待处理敏感信息日志单元，用于生成待处理敏感信息日志，所述待处理敏信息日志包括监控单元判断的待处理敏感信息的数目；
第一安全判定单元，用于获取第一目标***的所述新增敏感信息日志或所述待处理敏感信息日志或所述第二敏感信息库中的数据，并根据预定的判定规则判定所述第一目标***的所属的安全级别。
本申请提供的一种敏感信息处理的方法、装置、服务器及安全判定***，可以在页面服务器端获取待处理的信息，并按照预定的敏感信息识别策略判断所述待处理信息是否为敏感信息。在所述待处理信息为敏感信息时，可以按照预先设置的敏感信息处理策略对敏感信息进行处理，然后将已处理敏感信息返回至页面中，形成敏感信息处理后的页面。客户端接收的页面为在服务器端经过敏感信息处理的页面，即使客户端的非法用户采用抓取数据包或删除JavaScript脚本等也无法获取页面中真实的敏感信息，提高了页面中敏感信息的安全性。
附图说明
为了更清楚地说明本申请实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请中记载的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1是本申请所述服务器采用MVC框架页面结构的用户与服务器的交互流程示意图；
图2是本申请一种敏感信息处理的方法的一个实施例的方法流程图；
图3是本申请一种敏感信息处理的方法的另一种实施例的流程示意图；
图4是本申请一种实现敏感信息处理装置一种实施例的模块结构示意图；
图5是本申请一种实现敏感信息处理装置中敏感信息识别单元的模块结构示意图；
图6是本申请一种实现敏感信息处理装置中处理策略单元的模块结构示意图；
图7是本申请一种实现敏感信息处理的装置另一种实施例的模块结构示意图；
图8是本申请一种实现敏感信息处理的装置另一种实施例的模块结构示意图；
图9是本申请一种实现敏感信息处理的装置另一种实施例的模块结构示意图；
图10是本申请所述一种实现敏感信息处理的服务器的另一种实施例的模块结构示意图；
图11是本申请一种安全判定***的一种实施例的模块结构示意图；
图12是本申请一种安全判定***的另一种实施例的模块结构示意图。
具体实施方式
为了使本技术领域的人员更好地理解本申请中的技术方案，下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都应当属于本申请保护的范围。
MVC框架是一种Web服务器常用的使用MVC(Model View Controller模型-视图-控制器)将软件业务逻辑、数据、界面显示进行分离的web应用程序的设计创建模式。其中，模型(Model)可以用于封装与应用程序的业务逻辑相关的数据以及对数据的处理方法，通常有对数据的直接访问的权限，例如对数据库的访问。视图(View)可以用于数据的显示，通常是应用程序中与用户界面相关的部分，例如用户可以浏览并与之交互的页面界面。通常情况下视图可以是依据所述模型数据创建的。控制器(Controller)起到不同层面间的组织作用，可以用于处理事件并作出响应。MVC框架模式的三个模块可以相互独立，改变其中一个可以 不影响其他两个，可以使同一个模型被不同的视图重复使用。例如，用户A希望可以通过浏览器收发电子邮件，同时还希望可以通过手机访问电子邮箱。在服务器端可以采用MVC框架设计模式，模型可以响应用户的请求并返回响应数据，视图可以格式化数据并可以呈现给用户页面的Internet界面和WAP界面。
图1为服务器采用MVC框架页面结构的用户与服务器的交互流程示意图。如图1所述，用户可以通过客户端的浏览器向服务器发送HTTP请求。采用MVC框架模式的Web服务器在获取用户通过浏览器发送的HTTP请求时，根据所述HTTP请求生成相应的页面模型，然后对所述生成的页面模型进行渲染。所述页面模型通常可以由页面设计开发人员预先设计或***存储的页面模版(ModelMap)，所述页面模版中可以包括变量信息。所述对页面模型渲染可以包括通过控制器(Controller)找到页面模版中的变量信息，并根据用户的HTTP请求将所述页面模块中的变量替换成相应的真实数据。服务器完成对页面模版(ModelMap)的渲染后，可以将渲染后的页面回传给用户，视图模块(View)可以控制所述渲染后的页面在用户客户端的显示界面。
本申请提供一种敏感信息处理的方法，可以在服务器向用户回传页面之前，对用户的敏感信息进行处理，使用户客户端接收到的页面中所包含的敏感信息为已在服务器端进行相应处理的敏感信息。图2是本申请所述一种敏感信息处理的方法的一个实施例的方法流程图。如图2所示，所述的一种敏感信息处理的方法可以包括：
S1：获取页面中的待处理信息；
所述待处理信息可以根据页面服务器的框架结构进行设定。本实施例中所述待处理信息可以包括页面服务器MVC框架结构中ModelMap的变量信息。所述页面服务器在收到用户端发送的HTTP请求时，可以创建一个空的ModelMap页面模版。该页面模版ModelMap在MVC框架结构中可以是为一个存储结构，可以用于存储页面中需要返回给用户端的信息。前述中，所述页面模版ModelMap可以包括变量，所述变量的数据格式通常为包括变量名(键)与值的map(key：value)键值对数据格式，其中变量的值“value”通常可以采用空值或默认的字符串表示初始值。在Controller阶段，可以通过ModelMap.put()操作向ModelMap中的变量存放数据。例如，ModelMap中设置的一个变量为(name1：value)，可以通过ModelMap.put(”name1”,”张三”)这样的操作向所述ModelMap中的“name1”变量存放该变量的值“张三”。
在本实施例中，在向所述ModelMap中的变量存放数据后，可以获取ModelMap的数据，本实施例中可以指获取页面服务器MVC框架结构中ModelMap的变量信息，以所述ModelMap中的变量信息作为所述页面中的待处理信息。需要说明的，本申请中所述的一种 敏感信息处理的方法中，可以在页面服务器向页面中的变量存放数据的同时获取该变量信息，也可以在页面服务器存放完页面中所有的变量后获取页面中的变量信息。在本实施例在采用MVC框架结构的页面服务器中，可以在MVC框架向所述ModelMap中存放完所有的变量的数据后获取所述变量信息，并将所述变量信息作为待处理信息。
在本申请的另一个实施例中，图3是本申请所述一种敏感信息处理的方法的另一种实施例的流程示意图。如图3所示，所述一种敏感信息处理的方法中所述获取页面中的待处理信息可以包括通过***的postHandle处理程序获取MVC框架中变量信息，所述获取的变量信息作为待处理信息。具体的可以包括：
在MVC框架的Controller阶段，页面服务器以(变量名：值)的形式向ModelMap中的变量存放变量信息。在存放完ModelMap中的所有变量后，MVC框架可以将ModelMap数据发送至***，由***的postHandle处理程序接收所述MVC框架发送的ModelMap数据。所述postHandle处理程序可以遍历所述ModelMap中的变量信息，获取所述ModelMap中的变量，并以所述获取的变量信息作为待处理信息。
所述***，通常可以包括用于在应用程序某个执行步骤或字段被访问之前对访问源进行拦截，可以在拦截之前或之后执行特定的处理步骤。在MVC框架结构中，所述***可以包括三种处理方法：
preHandle()--在Controller被调用之前调用，可以用于初始化操作或对请求进行预处理；
postHandle()--在Controller被调用之后渲染视图之前调用，可以用于对模型数据或视图进行处理；
afterCompletion()--在视图呈现之后调用，可以用于进行资源清理。
通常所述***各个处理方法可以由相应的处理单元实现，例如所述preHandle处理阶段可以由***的实体装置preHandler实现，当然，所述postHandle处理阶段可以由***的实体装置postHandler实现。
如图3所示，通常在preHandle阶段，所述ModelMap中还没有存放数据，因此可以在postHandle或afterCompletion阶段获取所述待处理信息，即本实施例中MVC框架结构ModelMap中的变量信息。本实施例中优选的方式为可以在MVC框架结构中Controller被调用之后、视图渲染之前通过***获取所述页面中的待处理信息，介入对敏感信息的判别处理。具体的在本实施例，向所述ModelMap中存放变量数据之后，可以由***的postHandle处理程序获取ModelMap中的变量信息。当然，也可以在所述MVC框架结构中渲染(Velocity)调用之后通过***获取所述页面中的待处理信息，即在所述***的afterCompletion阶段 获取所述待处理信息。
需要说明的是，本实施例中通过***获取及后续的修改ModelMap中变量信息的方法适用于基于所述MVC框架其他框架结构中，例如webx框架结构等。针对不同的页面服务器框架可以有不同的***，在本实施例在基于所述MVC的框架结构中，可以在页面渲染(Velocity)之前、Controller被调用之后由相应的***获取及处理所述待处理信息，也可以在所述页面渲染(Velocity)之后由相应的***获取及处理所述待处理信息。优选的实施方式为在页面渲染(Velocity)之前、Controller被调用之后由相应的***获取及处理所述待处理信息。
获取页面服务器MVC框架结构中ModelMap中的变量信息，以所述变量信息作为页面中的待处理信息。
S2：根据预先设置的敏感信息识别策略判断所述待处理信息是否为敏感信息。
所述的敏感信息识别策略可以为预先设置的判断所述获取的待处理信息是否为敏感信息的判别规则或方法的集合。例如所述待处理信息为所述页面服务器MVC框架结构中ModelMap的变量信息时，所述敏感信息识别策略可以包括设置用于存储敏感信息的敏感信息库。所述根据预先设置的敏感信息识别策略判断所述待处理信息是否为敏感信息可以包括：
S201：获取页面服务器MVC框架结构ModelMap中变量信息的变量名；
S202：将所述获取的ModelMap中变量信息的变量名与敏感信息库中存储的敏感信息相比较，判断所述变量名是否在所述敏感信息库中；
S203：根据所述变量名是否在所述敏感信息库中的判断结果判断所述待处理信息是否为敏感信息。
在本实施例中，可以设置包括预先定义的敏感信息的敏感信息库。例如，可以将用户的用户名、电话号码、电子邮件、身份证号码信息预先定义为敏感信息，可以将其在所述ModelMap中的对应的变量名(key)“User”、“Tel_Num”、“E-Mail”、“ID_Num”预先存储在敏感信息库中。在获取所述ModelMap中变量信息的变量名后，可以将获取的变量名与所述敏感信息库中存储的敏感信息相比较。如果所述敏感信息库中包括与所述获取的变量名相同的敏感信息，则可以表示所述待处理信息为敏感信息，即可以表示本实施例中所述变量名所对应的ModelMap中的变量信息为敏感信息；如果所述比较的结果为所述敏感信息库中不包括与所述获取的变量名相同的敏感信息，则可以表示所述待处理信息不是敏感信息，即可以表示本实施例中所述变量名所对应的ModelMap中的变量信息不是敏感信息。
上述所述敏感信息库中存储的敏感信息可以根据需求进行增加或删除或修改。
当然，所述业务服务器框架结构为其他架构模式时，所述获取的待处理信息可以为其他与所述服务器框架结构相对应的数据格式，所述敏感信息识别策略也可以根据待处理信息和服务器框架进行相应的设置，例如可以直接判断所述待处理信息整个数据是否为敏感信息或者基于指定的数据判断所述待加密信息是否为敏感信息。
在本实施例基于MVC的框架结构中，所述根据预先设置的敏感信息识别策略判断所述待处理信息是否为敏感信息。
S3：在判断所述待处理信息为敏感信息时，可以按照预先设置的敏感信息处理策略进行处理，形成已处理敏感信息。
在所述待处理信息判断的结果为敏感信息时，可以按照预先设置的敏感信息处理策略对所述待处理信息进行处理。所述敏感信息处理策略可以包括预先设置的对判断为敏感信息的所述待处理信息的处理规则或方法的集合。在本实施例中，所述待处理信息为ModelMap中的变量(变量名：值)的数据格式时，所述按照预先设置的敏感信息处理策略进行处理可以包括对所述变量信息中变量名所对应的值进行处理。具体的所述敏感信息处理策略可以包括下述中的至少一种：
不处理、预定部分展示、完全屏蔽、按权限屏蔽、变换后展示、误报。
所述不处理，可以包括对所述变量名所对应的值不进行屏蔽、变换、替代等处理，所述变量名所对应的值变。
所述预定部分展示，可以包括根据预定的展示规则展示所述变量名所对应的值的特定字段。例如所述待处理信息为(Tel_Num：15912344321)时，所述预定的展示规则可以包括将变量名为“Tel：Num”所对应的值的第四位至第八位用字符“*”代替。上述待处理信息(Tel_Num：15912344321)按照上述预定部分展示的处理策略处理后可以形成已处理敏感信息为(Tel_Num：159*****321)。
所述完全屏蔽，可以包括根据预定的屏蔽规则屏蔽所述变量名所对应的值的所有字段。例如可以将变量名为“Tel：Num”所对应的值用一个或多个“*”字符代替，形成已处理敏感信息可以为(Tel_Num：*)或(Tel_Num：***********)。
所述按权限屏蔽，可以包括根据指定字段的权限对所述变量名所对应的值进行处理。例如，所述知道字段为获取的客户端用户的用户名，可以根据用户名所在不同域组的权限设置相应的处理方法。具体的可以例如下表1中所示，可以根据接收到的发送HTTP请求的客户端的用户的权限对敏感信息进行处理。具体例如接收的发送HTTP请求的用户名属于超级管理员域组时，可以设置对所有敏感信息不进行处理；所述发送HTTP请求的用户名属于管理员域组时，可以设置对指定敏感信息进行部分屏蔽；所述发送HTTP请求的用户名属于用户 域组时，可以设置对指定敏感信息进行全部屏蔽或部分屏蔽。
表1按权限屏蔽处理策略示意表
变量名 值 所属域组 处理策略 处理后值
Name1 张三 超级管理员 不处理 张三
Name2 李四 管理员 部分展示 李*
Name3 王五 用户 屏蔽 **
Tel_Num 15912344321 用户 部分展示 159*****321
E-Mail [email protected] 用户 部分展示 use**@163.com
ID_Num 320322198708081234 管理员 屏蔽 320****
Add_ID 浙江省杭州市 用户 部分展示 浙江省
Gender 女 用户 不处理 女
所述变换后展示，可以包括将所述变量名所对应的值按照预定变换规则进行变换，以所述变换后的值作为所述变量名的值。例如将ModelMap中的第四变量(Name4：evil)中的值“evil”按照预定规则变换为“live”后作为处理后的第四变量的值，即已处理敏感信息可以为(Name4：live)。
所述误报，可以表示为由于敏感信息的识别规则出现异常或所述判断出的敏感信息不符合根据其他条件设置的敏感信息判断标准时，对所述变量名所对应的值不进行处理操作，此时可以生成误报日志。所述误报日志中可以存储记录产生误报的次数以及每次误报的目标源(例如原始的变量名与值)、误报原因、日志产生时间等。在本实施例中可以存储所述生成的误报日志，可以用于后续的行为统计。
在具体的实施过程中，可以根据需求组合或嵌套设置所述敏感信息处理策略。例如所述述按照预先设置的敏感信息处理策略进行处理可以包括：
根据所述变量信息中不同的变量名对所述不同变量名所对应的值设置敏感信息处理策略；
或者，
在所述变量信息的同一变量名中根据指定字段信息的权限对所述同一变量名所对应的值设置敏感信息处理策略。
具体的例子中，可以将用户的用户名、电话号码、电子邮件、身份证号码信息预先定义为敏感信息，其在所述ModelMap中的对应的变量名(key)“User”、“Tel_Num”、“E-Mail”、“ID_Num”。在设置所述敏感信息处理策略时，可以根据预先设置的敏感信息的安全级别将用户名的变量名“User”所对应的值按照预定部分展示处理策略设置只显示前两个字符，其余用“*”字符代替；将用户的电子邮箱的变量名“E-Mail”所对应的值按照预定部分展示 处理策略设置只显示字符“@”及“@”后面的字符。对于相对重要的用户的身份证号码，可以按照完全屏蔽处理策略将身份证号码的变量名“ID_Num”所对应的值全部用4位“*”字符代替。
当然，在另一种实施方式中，也可以对变量信息的同一变量中根据预先设置的指定字段信息的权限对所述同一变量名所属对应的值设置敏感信息处理策略。所述的指定字段可以包括获取的页面中的特定字段信息，例如发送HTTP请求的用户的用户名。具体的例如可以根据获取的发送HTTP请求的用户的权限对所述敏感信息进行处理。例如发送HTTP请求的用户为管理员权限时，可以将用户的电话号码的变量名“Tel_Num”所对应的值不处理，管理员在最终返回的页面中可以查看到完整的电话号码信息。如果所述发送HTTP请求的用户为普通会员，则可以将用户的电话号码的变量名“Tel_Num”所对应的值按照预定的展示规则只显示电话号码的前三位与后三位数字，其余用“*”字符代替。
在判断所述待处理信息为敏感信息时，可以按照预先设置的至少一种敏感信息处理策略进行处理，形成已处理敏感信息。
S4：将所述已处理敏感信息替换所述页面中相应的待处理信息，形成敏感信息处理后的页面。
所述获取的页面中的待处理信息形成所述已处理敏感信息后，可以将所述已处理敏感信息发送至页面中与之相对应的待处理信息的相应位置，替换页面中的原有的待处理信息。例如在本实施例中，按照所述敏感信息处理策略对所述变量名所对应的值进行替换后，可以将值替换后的变量返回至MVC服务器框架结构的ModelMap，在MVC框架中用值替换后的变量对页面进行渲染。具体的例如在VM页面模版渲染时，可以将所述ModelMap中变量信息的变量名与所述已处理敏感信息变量名相同的变量信息中的值替换成所述已处理敏感信息中该变量名所对应的值。例如可以将已处理敏感信息(Name2：李*)的值“李*”替换掉ModelMap中的变量(Name2：李四)的值“李四”。当然，在判断所述待加密信息不是敏感信息或所述对敏感信息的处理策略为不处理或误报时，可以不需要对所述待加密信息进行处理，具体的，在本实施例可以不需要对ModelMap中的变量进行值的替换。
用已处理敏感信息对所述页面进行渲染形成敏感信息处理后的页面后，可以将所述敏感信息处理后的页面回传给客户端的浏览器。客户端收到经过敏感信息处理后的页面后，展示给用户的是已处理敏感信息的页面。例如，在显示当前登录的用户名的模块显示区域中本来要显示的用户名“李四”，在敏感信息处理后展示给客户端用户的用户名可以为“李*”。
本实施例提供的一种敏感信息处理的方法，可以在页面服务器端获取待处理的信息，并按照预定的敏感信息识别策略判断所述待处理信息是否为敏感信息。在所述待处理信息为敏 感信息时，可以按照预先设置的敏感信息处理策略对敏感信息进行处理，然后将已处理敏感信息返回至页面中，可以形成敏感信息处理后的页面。所述敏感信息处理后的页面中所包括的敏感信息为在服务器端经过相应处理的信息，即使客户端的非法用户采用抓取数据包或删除JavaScript脚本也无法获取页面中真实的敏感信息，提高了页面中敏感信息的安全性。
客户端用户发送的HTTP请求页面中可以包括多个待识别和处理的敏感信息，这些敏感信息可以出现在不同请求页面的不同位置，其在MVC框架结构ModelMap中也可以对应不同的变量，在后续的敏感信息处理中增加了敏感信息的识别难度。基于MVC框架的不同页面服务器或不同设计开发人员可以对相同的敏感信息，例如用户的电子邮箱、身份证号码等在ModelMap中设置不同的变量名。例如在一次页面请求的ModelMap中所述身份证号码变量信息对应的变量名为“ID_Num”，而在另一次页面请求中，所述ModelMap中身份证号码变量信息对应的变量名可以为“Num_001”。本申请提供一种动态的敏感信息处理方法的另一种实施例，在该实施例中可以根据预先设置的敏感信息监控策略动态的调整敏感信息识别策略。具体的，所述一种敏感信息处理的方法还可以包括：
S5：根据预先设置的敏感信息监控策略判断所述页面服务器MVC框架结构中ModelMap的变量信息的值是否为待处理敏感信息；
S6：在所述根据敏感信息监控策略判断所述变量信息的值为待处理敏感信息时，将与所述变量信息的值相对应的变量名发送至所述敏感信息库。
在本实施例中，可以根据预先设置的敏感信息监控策略判断所述ModelMap中变量信息的值是否为待处理的敏感信息。在具体的实施应用中，所述的敏感信息通常具有一定的数据结构格式，例如移动电话号码通常可以为11位的非零开头的数字组合，电子邮箱通过可以包括“@”字符。此时所述敏感信息监控策略可以通过正则匹配的方法匹配所述ModelMap中变量信息的值是否符合预先设置的11位的数字组合，或者判断所述ModelMap中变量信息的值是否含有“@”字符并且“@”前至少有一位非空字符等。如果通过所述敏感信息监控策略判断所述ModelMap中变量信息的值为待处理敏感信息，则可以将与所述变量信息的值相对应的变量名“Phone_Num”或“First_Contact”发送至所述敏感信息库中。所述敏感信息库可以接收所述与所述变量信息的值相对应的变量名“Phone_Num”或“First_Contact”，并比较所述敏感信息库中是否存储有与所述变量名相同的敏感信息。如果所述敏感信息库中没有与所述变量名相同的敏感信息，可以将所述敏感信息库中未包含但所对应的值为所述待处理敏感信息的变量名作为新增敏感信息存储在所述敏感信息库中。这样，如果当前所述敏感信息库中没有存储所述新增敏感信息“Phone_Num”或“First_Contact”时，通过所述敏感信息监控策略可以将所述变量名为“Phone_Num”或“First_Contact”的待处理敏感信息 作为新增敏感信息添加到敏感信息库中。在下一次响应用户HTTP请求时，可以识别出变量名为“Phone_Num”或“First_Contact”的敏感信息，可以根据敏感信息处理策略对所述变量名为“Phone_Num”或“First_Contact”所对应的值进行处理。
对应上述S5中识别出的待处理敏感信息，还可以生成相应的待处理敏感信息日志。所述待处理敏感信息日志可以包括待处理敏感信息的个数、以及待处理敏感信息的值、值对应的变量名、是否已发送至敏感信息库以及每个待处理敏感信息的处理时间、待处理敏感信息日志生成时间等，可以用于后续***安全判定时数据的处理。
对应上述所述敏感信息库存储的所述新增敏感信息，还可以生成相应的新增敏感信息日志。所述新增敏感信息日志可以包括新增敏感信息的个数、以及所述新增敏感信息的值、值所对应的变量名、是否已经存储在敏感信息库中以及存储时间、新增敏感信息日志生成时间等，可以用于后续***安全判定时数据的处理。
通过本申请包括敏感信息监控程策略的一种敏感信息处理的方法可以实现对敏感信息库的动态更新，可以更加准确的识别待处理信息中的敏感信息，完成对敏感信息的处理，提高页面敏感信息的安全性。
基于本申请思想，本申请提供一种实现敏感信息处理的装置。图4是本申请所述一种实现敏感信息处理装置一种实施例的模块结构示意图。如图4所示，所述装置可以包括：
信息获取单元101，可以用于获取页面中的待处理信息；
敏感信息库102，可以用于存储敏感信息；
敏感信息识别单元103，可以用于基于所述敏感信息库102中存储的敏感信息判断所述待处理信息是否为敏感信息；
处理策略单元104，可以用于存储敏感信息处理策略；
信息处理单元105，可以用于在所述敏感信息识别单元103判断所述待处理信息为敏感信息时，基于所述处理策略单元104存储的敏感信息处理策略对所述待处理信息进行处理，形成已处理敏感信息。
在具体的一个实施例中，所述信息获取单元101获取的待处理信息可以包括：
页面服务器MVC框架结构中ModelMap的变量信息。
具体的处理过程中，所述处理策略单元104存储的敏感信息处理策略可以包括：
根据所述变量信息中不同的变量名对所述变量名所对应的值设置敏感信息处理策略；
或者，
在所述变量信息的同一变量名中根据指定字段信息的权限对所述同一变量名所对应的值设置敏感信息处理策略。
图5是本申请一种实现敏感信息处理装置中敏感信息识别单元103的一种实施例的模块结构示意图。如图5所示，所述敏感信息识别单元103可以包括：
键值获取单元1031，可以用于获取页面服务器MVC框架结构ModelMap中变量信息的变量名；
比较单元1032，可以用于比较所述获取的ModelMap中变量信息的变量名与所述敏感信息库102存储的敏感信息是否相同；
第一判断单元1033，可以用于根据所述比较单元1032的比较结果判断所述待处理信息是否为敏感信息。
上述所述第一判断单元1033中，如果所述比较单元1032比较所述变量名与敏感信息库102存储的敏感信息的结果为相同，所述第一判断单元1033可以判断所述信息获取单元101获取的待处理信息为敏感信息；相应的，如果所述比较单元1032遍历所述敏感信息库102存储的敏感信息中没有查询到与所述变量名相同的敏感信息，比较结果为不相同，则所述第一判断单元1033可以判断所述信息获取单元101获取的待处理信息不是敏感信息。
图6为本申请所述一种实现敏感信息处理的装置中处理策略单元的一种实施例的模块结构示意图。如图6所示，所述处理策略单元104可以包括下述单元中的至少一种：
预定部分展示单元1041，可以用于根据预定的展示规则展示所述变量名所对应的值的特定字段；
完全屏蔽单元1042，可以用于根据预定的屏蔽规则屏蔽所述变量名所对应的值的所有字段；
权限屏蔽单元1043，可以用于根据指定字段的权限对所述变量名所对应的值进行处理。具体的例如可以对权限高的用户设置对指定敏感信息不屏蔽或部分屏蔽，对权限相对较低的用户设置对指定敏感信息部分屏蔽或完全屏蔽。
变换展示单元1044，可以用于将所述变量名所对应的值按照预定变换规则进行变换，以所述变换后的值作为所述变量名的值。
误报单元1045，可以用于在所述敏感信息处理装置中所述的任意一个结构模块出现异常或所述敏感信息识别单元103所判断的敏感信息不符合第三方模块设置的敏感信息判断标准时，对所述变量名所对应的值不进行处理，并生成误报日志。所述第三方模块设置可以包括设置在所述敏感信息处理装置内或外部的其他判断所述待处理信息是否为敏感信息的模块。如果本申请所述实现敏感信息处理的装置识别敏感信息的方法与其他模块识别敏感信息的方法有冲突，可以设置对此处的敏感信息为误报，可以不进行敏感信息的数据处理。例如根据所述变量名所对应的值中包括字符“@”判断所对应的待处理信息为用户的电子邮件的敏 感信息，同时依据所述第三方模块可以判断该变量所对应的待处理信息为用户在文本框中输入的对卖家的评论，不是设置的敏感信息。此时所述敏感信息处理装置的误报单元1045可以对所述待处理信息不进行处理屏蔽、变换等处理，可以记录此次误报的日志。
本实施例中所述的一种实现敏感信息处理的装置，可以获取页面中的待处理信息，并根据预先设置的敏感信息识别策略判断所述待处理信息是否为敏感信息。如果是，可以根据预先设置的敏感信息处理策略对所述待处理信息进行处理，完成敏感信息的识别和处理。
在本申请另一种优选的实施例中，所述实现敏感信息处理的装置还可以包括用于维护敏感信息库中的敏感信息的单元。图7是本申请所述一种实现敏感信息处理的装置另一种实施例的模块结构示意图，如图7所述，所述装置可以包括：
监控策略单元106，可以用于存储预先设置的敏感信息监控策略；
待处理敏感信息单元107，可以用于根据预先设置的敏感信息监控策略判断所述页面服务器MVC框架结构中ModelMap的变量信息的值是否为待处理敏感信息；
发送单元108，可以用于所述待处理敏感信息单元107判断所述变量信息的值为待处理敏感信息时，将与所述变量信息的值相对应的变量名发送至所述敏感信息库102。
相应的，所述敏感信息库102可以接收与所述变量信息的值相对应的变量名，并比较所述敏感信息库102中是否存储有与所述变量名相同的敏感信息。如果所述敏感信息库102中没有与所述变量名相同的敏感信息，可以存储所述变量名。
图8是本申请所述一种实现敏感信息处理装置的另一种实施例，如图8所示，所述装置还可以包括：
替换单元109，可以用将所述已处理敏感信息替换所述页面中相应的待处理信息。
在本实施例中，所述实现敏感信息处理的装置可以在所述装置中将所述已处理敏感信息替换所述页面中相应的待处理信息。在另一种实施方式中，可以将所述已处理敏感信息发送至服务器，由所述服务器将所述已处理敏感信息替换所述页面中相应的待处理信息，形成敏感信息处理后的页面。图9是本申请所述一种实现敏感信息处理装置的另一种实施例，如图9所示，所述装置还可以包括：
回传单元110，可以用于将所述已处理敏感信息直接发送至服务器或通过***发送至服务器的已处理敏感信息接收单元。
本申请还提供一种实现敏感信息处理的服务器，所述服务器可以包括上述实施例中任意一种所述实现敏感信息处理的装置。
本申请提供的一种实现敏感信息处理的服务器在不使用***时可以包括：
第一MVC目标***，可以用于接收客户端发送的HTTP请求，并根据所述HTTP请求 生成页面模版ModelMap；还可以用于向所述生成的页面模版ModelMap中传入待处理信息，完成对所述HTTP请求页面的渲染；还可以用于将渲染后的页面发送至客户端；还可以用于接收敏感信息处理模块发送的已处理敏感信息，并将所述已处理敏感信息替换所述页面模版ModelMap中相对应的待处理信息；
第一敏感信息处理模块，可以用于获取所述页面模板ModelMap中的待处理信息，并根据预先设置的敏感信息识别策略判断所述待处理信息是否为敏感信息；还可以用于在所述待处理信息为敏感信息时，按照预先设置的敏感信息处理策略进行处理，形成已处理敏感信息；还可以用于将所述已处理敏感信息发送至所述MVC目标***。
图10是本申请所述一种实现敏感信息处理的服务器的另一种实施例的模块结构示意图。所述服务器可以包括MVC框架结构。本申请中所述的一种实现敏感信息处理的服务器可以包括上述任意一项所述的实现敏感信息处理装置，优选实施方式中可以包括***。具体的如图10所示，所述服务器可以包括：
MVC目标***1，可以用于接收客户端发送的HTTP请求，并根据所述HTTP请求生成页面模版ModelMap；还可以用于向所述生成的页面模版ModelMap中传入待处理信息，完成对所述HTTP请求页面的渲染；还可以用于将渲染后的页面发送至客户端；还可以用于接收敏感信息处理模块发送的已处理敏感信息，并将所述已处理敏感信息替换所述页面模版ModelMap中相对应的待处理信息；
***2，可以用于获取所述页面模版ModelMap中待处理信息，并将所述待处理信息发送至敏感信息处理模块3；还可以用于接收敏感信息处理模块3发送的已处理敏感信息，并将所述已处理敏感信息发送至所述MVC目标***1；
敏感信息处理模块3，可以用于接收并判断所述待处理信息是否为敏感信息；还用于按照预先设置的敏感信息处理策略对所述判断为敏感信息的待处理进行处理，形成已处理敏感信息。所述敏感信息处理模块可以包括：
信息接收单元，可以用于接收待处理信息；
第一敏感信息库，可以用于存储敏感信息；
第一敏感信息识别单元，可以用于基于所述第一敏感信息库中存储的敏感信息判断所述待处理信息是否为敏感信息；
第一处理策略单元，可以用于存储敏感信息处理策略；
第一信息处理单元，可以用于在所述第一敏感信息识别单元判断所述待处理信息为敏感信息时，基于所述第一处理策略单元存储的敏感信息处理策略对所述待处理信息进行处理，形成已处理敏感信息；
第一回传单元，可以用于将所述已处理敏感信息发送至***。
上述所述MVC目标***1具体的可以包括：
ModelMap模块11，可以用于接收客户端发送的HTTP请求，并根据所述HTTP请求生成页面模版ModelMap；
Controller模块12，可以用于向所述生成的页面模版ModelMap中传入待处理信息；还可以用于接收***发送的已处理敏感信息；
Velocity模块12，可以用于将所述Controller模块12接收的已处理敏感信息替换所述页面模版ModelMap中相对应的待处理信息；还可以用于完成对所述HTTP请求相应页面的渲染；
回传模块14，可以用于将渲染后的页面发送至客户端。
所述***通常可以包括preHandler(21)、postHandler(22)、afterCompletion(23)。本申请所述的一种实现敏感信息处理的服务器中所述***2获取页面模版ModelMap中的待处理信息可以包括：
通过所述***的postHandle或afterCompletion处理程序获取所述页面模版ModelMap中的待处理信息。
在所述MVC目标***中，所述待处理信息可以包括所述ModelMap的变量信息。
上述所述的一种实现敏感信息处理的服务器，所述第一处理策略单元包括下述单元中的至少一种：
第一预定部分展示单元，可以用于根据预定的展示规则展示所述变量名所对应的值的特定字段；
第一完全屏蔽单元，可以用于根据预定的屏蔽规则屏蔽所述变量名所对应的值的所有字段；
第一权限屏蔽单元，可以用于根据指定字段的权限对所述变量名所对应的值进行处理；
第一变换展示单元，可以用于对所述变量名所对应的值按照预定变换规则进行变换，以所述变换后的值作为所述变量名的值；
第一误报单元，可以用于在所述敏感信息处理装置中所述的任意一个结构模块出现异常或所述敏感信息识别单元所判断的敏感信息不符合第三方模块设置的敏感信息判断标准时，对所述变量名所对应的值不进行处理，并生成误报日志。
上述所述的一种实现敏感信息处理的服务器，所述第一敏感信息识别单元包括：
第一键值获取单元，可以用于获取所述MVC目标***中ModelMap中变量信息的变量名；
第一比较单元，可以用于比较所述获取的ModelMap中变量信息的变量名与所述第一敏感信息库存储的敏感信息是否相同；
第二判断单元，可以用于根据所述第一比较单元的比较结果判断所述待处理信息是否为敏感信息。
上述所述的一种实现敏感信息处理的服务器，优选的实施例中，还可以包括：
第一监控策略单元，可以用于存储预先设置的敏感信息监控策略；
第一待处理敏感信息单元，可以用于根据预先设置的敏感信息监控策略判断所述MVC目标***中ModelMap的变量信息的值是否为待处理敏感信息；
第一发送单元，可以用于所述第一待处理敏感信息单元判断所述变量信息的值为待处理敏感信息时，将与所述变量信息的值相对应的变量名发送至所述第一敏感信息库。
本申请提供的一种实现敏感信息处理的服务器中，所述MVC目标***1在接收用户的HTTP请求可以由ModelMap模块生成页面模版ModelMap，然后所述MVC目标***中的Controller模块12向所述生成的ModelMap中的变量传入信息后，可以由***2的postHandler中的postHandle处理程序获取ModelMap中的变量信息。进一步的所述***可以将获取的变量信息发送至敏感信息处理模块3，可以由敏感信息处理模块3判断所述变量信息是否为敏感信息，并对敏感信息按照预定的敏感信息处理策略进行处理，形成已处理敏感信息。所述MVC目标***可以接收所述敏感信息处理模块3发送的已处理敏感信息，并可以将所述已处理敏感信息替换所述页面模版ModelMap中相应的待处理信息，完成页面的渲染。然后所述服务器可以通过回传模块14将敏感信息处理后的页面回传至用户的客户端。
本申请中所述的MVC框架包括基于MVC(Model View Controller模型-视图-控制器)设计创建web应用程序模式各种spring mvc框架，例如sofa2、sofa3或webx等mvc框架结构。
本申请提供的一种实现敏感处理的服务器，可以在服务器端实现对敏感信息的识别，并对判断为敏感信息的信息在服务器端根据预先设置的敏感信息处理策略进行处理，使服务器发送给用户客户端浏览器的页面中所包括的敏感信息为已处理敏感信息。非法用户无法通过数据截取、本地网页修改等方式获取真实的敏感信息，提供了页面敏感信息的安全性。
根据本申请所述的一种敏感信息处理方法、装置及服务器对所述敏感信息的识别、处理思想，本申请还提供一种安全判定***，可以用于判断页面服务器是否安全以及判定所述页面服务器安全性能，还可以用于多个服务器***之间安全性的比较，及时对安全性较低的服务器进行维护，提高服务器的安全性。图11是本申请所述一种安全判断***的模块结构示意图，如图11所示，所述的一种安全判定***可以包括：
第二敏感信息库201，可以用于存储敏感信息；还可以用于接收第二待处理敏感信息单元205发送的变量名，并判断所述存储的敏感信息中是否包括所述接收的变量名；还可以用于在所述判断结果为所述敏感信息库中不包括所述接收的变量名时，将所述变量名作为新增敏感信息进行存储；
第二敏感信息识别单元202，可以用于获取页面中的待处理信息；还可以用于基于所述第二敏感信息库201中存储的敏感信息判断所述待处理信息是否为敏感信息；
第二信息处理单元203，可以用于存储敏感信息处理策略；还可以用于在所述第二敏感信息识别单元202判断所述待处理信息为敏感信息时，基于所述存储的敏感信息处理策略对所述待处理信息进行处理，形成已处理敏感信息；
监控单元204，可以用于存储预先设置的敏感信息监控策略；还可以用于根据所述存储的敏感信息监控策略判断所述页面服务器MVC框架结构中ModelMap的变量信息的值是否为待处理敏感信息；还用于在判断所述变量信息的值为待处理敏感信息时，将与所述变量信息的值相对应的变量名发送至所述第二敏感信息库201；
新增敏感信息日志单元205，可以用于生成新增敏感信息日志，所述新增敏感信息日志可以包括所述第二敏感信息库201所述新增敏感信息的数目；
待处理敏感信息日志单元206，可以用于生成待处理敏感信息日志，所述待处理敏信息日志可以包括监控单元204判断的待处理敏感信息的数目；
第一安全判定单元207，可以用于获取第一目标***的所述新增敏感信息日志或所述待处理敏感信息日志或所述第二敏感信息库中的数据，并根据预定的判定规则判定所述第一目标***的所属的安全级别。
所述第一安全判定单元207可以包括下述单元中的至少一种：
第一数目判定单元，可以用于根据第一时间窗内所述新增敏感信息的数目/第二敏感信息库中存储的敏感信息数目判定所述第一目标***的安全级别；
第一比值判定单元，可以根据第二时间窗内所述新增敏感信息的数目与所述待处理敏感信息的数目的比值判定所述第一目标***的安全级别。
具体的例如，可以根据第一时间窗内所述新增敏感信息的数目判定所述第一目标***的安全级别时，可以预先划分不同安全级别所对应的新增敏感信息的数目，例如第四安全级别所包括的新增敏感信息可以为100条以下，第三安全级别可以为100～1000条，第二安全解闭可以为1001～5000条，第一安全级别为5000条以上。在另一种实施方式中，可以根据第二时间窗内所述新增敏感信息的数目与所述待处理敏感信息的数目的比值判定所述第一目标***的安全级别。所述比值越大，表示新发现的待处理敏感信息中被处理的待敏感信息越 多或越及时，可以用于表示***的安全性越高；相应的，所述比值越小，可以表示未被处理的待处理敏感信息越多，可以表示***的安全性越低。当然，可以根据所述比值划分相应的安全等级，具体的可以参考上述其他实施例，再次不做赘述。
图12为本申请所述一种安全判定***的另一种优选的实施例的模块结构示意图，如图12所示，所述安全判定***还可以包括多***判定单元208，还可以用于根据预定的判定规则比较所述第一目标***与第二目标***的安全级别；相应的，所述第一安全判定单元207可以获取第二目标***的所述新增敏感信息日志或所述待处理敏感信息日志或所述第二敏感信息库中的数据。
所述多***判定单元208可以包括下述单元中的至少一种：
第二数目判定单元，可以用于根据所述第一时间窗内所述第一目标***与第二目标***的新增敏感信息的数目/第二敏感信息库中存储的敏感信息数目比较所述第一目标***与第二目标***的安全级别；
第二比值判定单元，可以根据第二时间窗内所述第一目标***与第二目标***新增敏感信息的数目与所述待处理敏感信息的数目的比值比较所述第一目标***与第二目标***的安全级别。
具体的，例如统计一周内所述第一目标***新增的敏感信息的数目大于所述第二目标***新增敏感信息的数目，可以表示所述第二目标***的安全性高于所述第一目标***。当然，所述在统计周期内所述第一目标***新增敏感信息的数目与所述待处理敏感信息的数目的比值大于所述第二目标***新增敏感信息的数目与所述待处理敏感信息的数目的比值，则可以表示所述第一目标对敏感信息处理及时，安全性更高。需要说明的是，上述两种方式是从不同的维度来判定***的安全级别，例如同一个***可以包括更多的新增敏感信息但所述比值更大，可以表示该***初始安全性较低，但由于及时维护，安全成长性较高。
本申请提供的一种安全判定***，摒弃了现有技术中通过目标***存在的***漏洞、需要更新的补丁数目等方式来判断***是否安全以及安全性的高低。本申请的提供的从敏感信息的角度来判定***安全性的***，从可以目标***中可以识别出的敏感信息数据以及对识别出的敏感信息的处理是否及时来判定目标***的安全性能，可以从评定***安全性的本质上对目标***做出更加准确的安全性判定。例如，如果所述目标***可以识别并处理总共10万个敏感信息中的全部敏感信息，或者新发现100的个待处理敏感信息中的99个通过操作加入到所述第二敏感信息库中，即使在现有技术中因目标***有M个补丁未打或存在N个漏洞而导致判定目标***的安全性低，但从对敏感信息的识别及处理的本质层面来判定所述目标***，实质上所述目标***的安全性是高的。利用本申请所述的一种安全判定***可以 更加准确的判定目标***的安全性。利用本申请可以从不同纬度比较不同目标***的安全性，对安全性较低的目标***，可以及时对其敏感信息进行处理或采取其他措施对目标***进行维护，可以提高***的安全性。
尽管本申请内容中提到包括HTTP在内的协议之类的描述，但是，本申请并不局限于必须是完全符合规范的HTTP在内的协议的情况。某些协议的基础上略加修改后的传输机制也可以实行上述本申请各实施例的方案，例如HTTPS或者HTTP的2.0版本传输协议。当然，即使不采用上述HTTP协议，而是采用私有协议，只要符合本申请上述各实施例的页面信息交互和信息判断反馈方式，仍然可以实现相同的申请，在此不再赘述。
上述实施例阐明的装置或模块，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。为了描述的方便，描述以上装置时以功能分为各种模块分别描述。当然，在实施本申请时可以把各模块的功能在同一个或多个软件和/或硬件中实现，也可以将实现同一功能的模块由多个子模块或子单元的组合实现。
本领域技术人员也知道，除了以纯计算机可读程序代码方式实现控制器以外，完全可以通过将方法步骤进行逻辑编程来使得控制器以逻辑门、开关、专用集成电路、可编程逻辑控制器和嵌入微控制器等的形式来实现相同功能。因此这种控制器可以被认为是一种硬件部件，而对其内部包括的用于实现各种功能的装置也可以视为硬件部件内的结构。或者甚至，可以将用于实现各种功能的装置视为既可以是实现方法的软件模块又可以是硬件部件内的结构。
本申请可以在由计算机执行的计算机可执行指令的一般上下文中描述，例如程序模块。一般地，程序模块包括执行特定任务或实现特定抽象数据类型的例程、程序、对象、组件、数据结构、类等等。也可以在分布式计算环境中实践本申请，在这些分布式计算环境中，由通过通信网络而被连接的远程处理设备来执行任务。在分布式计算环境中，程序模块可以位于包括存储设备在内的本地和远程计算机存储介质中。
通过以上的实施方式的描述可知，本领域的技术人员可以清楚地了解到本申请可借助软件加必需的通用硬件平台的方式来实现。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品可以存储在存储介质中，如ROM/RAM、磁碟、光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，移动终端，服务器，或者网络设备等)执行本申请各个实施例或者实施例的某些部分所述的方法。
本说明书中的各个实施例采用递进的方式描述，各个实施例之间相同或相似的部分互相 参见即可，每个实施例重点说明的都是与其他实施例的不同之处。本申请可用于众多通用或专用的计算机***环境或配置中。例如：个人计算机、服务器计算机、手持设备或便携式设备、平板型设备、多处理器***、基于微处理器的***、置顶盒、可编程的电子设备、网络PC、小型计算机、大型计算机、包括以上任何***或设备的分布式计算环境等等。
虽然通过实施例描绘了本申请，本领域普通技术人员知道，本申请有许多变形和变化而不脱离本申请的精神，希望所附的权利要求包括这些变形和变化而不脱离本申请的精神。

Claims (24)

  1. 一种敏感信息处理的方法，其特征在于，所述方法包括：
    获取页面中的待处理信息；
    根据预先设置的敏感信息识别策略判断所述待处理信息是否为敏感信息；
    在所述待处理信息为敏感信息时，按照预先设置的敏感信息处理策略进行处理，形成已处理敏感信息；
    将所述已处理敏感信息替换所述页面中相应的待处理信息，形成敏感信息处理后的页面。
  2. 如权利要求1所述的一种敏感信息处理的方法，其特征在于，所述获取页面中的待处理信息包括：
    在MVC框架结构中Controller被调用之后、视图渲染之前通过***获取所述页面中的待处理信息；
    或者，
    在MVC框架结构中Velocity调用之后通过***获取所述页面中的待处理信息。
  3. 如权利要求1所述的一种敏感信息处理的方法，其特征在于，所述待处理信息包括：
    页面服务器MVC框架结构中ModelMap的变量信息。
  4. 如权利要求3所述的一种敏感信息处理的方法，其特征在于，所述根据预先设置的敏感信息识别策略判断所述待处理信息是否为敏感信息包括：
    获取页面服务器MVC框架结构ModelMap中变量信息的变量名；
    将所述获取的ModelMap中变量信息的变量名与敏感信息库中存储的敏感信息相比较，判断所述变量名是否在所述敏感信息库中；
    根据所述变量名是否在所述敏感信息库中的判断结果判断所述待处理信息是否为敏感信息。
  5. 如权利要求4所述的一种敏感信息处理的方法，其特征在于，所述方法还包括：
    根据预先设置的敏感信息监控策略判断所述页面服务器MVC框架结构中ModelMap的变量信息的值是否为待处理敏感信息；
    在所述根据敏感信息监控策略判断所述变量信息的值为待处理敏感信息时，将与所述变量信息的值相对应的变量名发送至所述敏感信息库。
  6. 如权利要求3所述的一种敏感信息处理的方法，其特征在于，所述按照预先设置的敏感信息处理策略进行处理包括：
    根据所述变量信息中不同的变量名对所述不同变量名所对应的值设置敏感信息处理策略；
    或者，
    在所述变量信息的同一变量名中根据指定字段信息的权限对所述同一变量名所对应的值设置敏感信息处理策略。
  7. 如权利要求6所述的一种敏感信息处理的方法，其特征在于，所述敏感信息处理策略包括下述中的至少一种：
    不处理、预定部分展示、完全屏蔽、按权限屏蔽、变换后展示、误报。
  8. 一种实现敏感信息处理的装置，其特征在于，所述装置包括：
    信息获取单元，用于获取页面中的待处理信息；
    敏感信息库，用于存储敏感信息；
    敏感信息识别单元，用于基于所述敏感信息库中存储的敏感信息判断所述待处理信息是否为敏感信息；
    处理策略单元，用于存储敏感信息处理策略；
    信息处理单元，用于在所述敏感信息识别单元判断所述待处理信息为敏感信息时，基于所述处理策略单元存储的敏感信息处理策略对所述待处理信息进行处理，形成已处理敏感信息。
  9. 如权利要求8所述的一种实现敏感信息处理的装置，其特征在于，所述信息获取单元获取的待处理信息可以包括：
    页面服务器MVC框架结构中ModelMap的变量信息。
  10. 如权利要求9所述的一种实现敏感信息处理的装置，其特征在于，所述处理策略单元存储的敏感信息处理策略包括：
    根据所述变量信息中不同的变量名对所述不同变量名所对应的值设置敏感信息处理策略；
    或者，
    在所述变量信息的同一变量名中根据指定字段信息的权限对所述同一变量名所对应的值设置敏感信息处理策略。
  11. 如权利要求9所述的一种实现敏感信息处理的装置，其特征在于，所述处理策略单元包括下述单元中的至少一种：
    预定部分展示单元，用于根据预定的展示规则展示所述变量名所对应的值的特定字段；
    完全屏蔽单元，用于根据预定的屏蔽规则屏蔽所述变量名所对应的值的所有字段；
    权限屏蔽单元，用于根据指定字段的权限对所述变量名所对应的值进行处理；
    变换展示单元，用于将所述变量名所对应的值按照预定变换规则进行变换，以所述变换后的值作为所述变量名的值；
    误报单元，用于在所述敏感信息处理装置中所述的任意一个结构模块出现异常或所述敏感信息识别单元所判断的敏感信息不符合第三方模块设置的敏感信息判断标准时，对所述变量名所对应的值不进行处理，并生成误报日志。
  12. 如权利要求9所述的一种实现敏感信息处理的装置，其特征在于，所述敏感信息识别单元包括：
    键值获取单元，用于获取页面服务器MVC框架结构ModelMap中变量信息的变量名；
    比较单元，用于比较所述获取的ModelMap中变量信息的变量名与所述敏感信息库存储的敏感信息是否相同；
    第一判断单元，用于根据所述比较单元的比较结果判断所述待处理信息是否为敏感信息。
  13. 如权利要求9所述的一种实现敏感信息处理的装置，其特征在于，还包括：
    监控策略单元，用于存储预先设置的敏感信息监控策略；
    待处理敏感信息单元，用于根据预先设置的敏感信息监控策略判断所述页面服务器MVC框架结构中ModelMap的变量信息的值是否为待处理敏感信息；
    发送单元，用于所述待处理敏感信息单元判断所述变量信息的值为待处理敏感信息时，将与所述变量信息的值相对应的变量名发送至所述敏感信息库。
  14. 如权利要求9所述的一种实现敏感信息处理的装置，其特征在于，还包括：
    回传单元，用于将所述已处理敏感信息直接发送至服务器或通过***发送至服务器的已处理敏感信息接收单元。
  15. 如权利要求9所述的一种实现敏感信息处理的装置，其特征在于，还包括：
    替换单元，用于将所述已处理敏感信息替换所述页面中相应的待处理信息。
  16. 一种实现敏感信息处理的服务器，其特征在于，所述服务器包括：
    MVC目标***，用于接收客户端发送的HTTP请求，并根据所述HTTP请求生成页面模版ModelMap；还用于向所述生成的页面模版ModelMap中传入待处理信息，完成对所述HTTP请求相对应的页面的渲染；还用于将渲染后的页面发送至客户端；还用于接收敏感信息处理模块发送的已处理敏感信息，并将所述已处理敏感信息替换所述页面模版ModelMap中相对应的待处理信息；
    ***，用于获取所述页面模版ModelMap中的待处理信息，并将所述待处理信息发送 至敏感信息处理模块；还用于接收敏感信息处理模块发送的已处理敏感信息，并将所述已处理敏感信息发送至所述MVC目标***；
    敏感信息处理模块，用于接收并判断所述待处理信息是否为敏感信息；还用于按照预先设置的敏感信息处理策略对所述判断为敏感信息的待处理进行处理，形成已处理敏感信息；
    所述敏感信息处理模块包括：
    信息接收单元，用于接收待处理信息；
    第一敏感信息库，用于存储敏感信息；
    第一敏感信息识别单元，用于基于所述第一敏感信息库中存储的敏感信息判断所述待处理信息是否为敏感信息；
    第一处理策略单元，用于存储敏感信息处理策略；
    第一信息处理单元，用于在所述第一敏感信息识别单元判断所述待处理信息为敏感信息时，基于所述第一处理策略单元存储的敏感信息处理策略对所述待处理信息进行处理，形成已处理敏感信息；
    第一回传单元，用于将所述已处理敏感信息发送至***。
  17. 如权利要求16所述的一种实现敏感信息处理的服务器，其特征在于，所述***获取所述页面模版ModelMap中的待处理信息包括：
    通过所述***的postHandle或afterCompletion的处理程序获取所述页面模版ModelMap中的待处理信息。
  18. 如权利要求16所述的一种实现敏感信息处理的服务器，其特征在于，所述第一处理策略单元包括下述单元中的至少一种：
    第一预定部分展示单元，用于根据预定的展示规则展示所述变量名所对应的值的特定字段；
    第一完全屏蔽单元，用于根据预定的屏蔽规则屏蔽所述变量名所对应的值的所有字段；
    第一权限屏蔽单元，用于根据指定字段的权限对所述变量名所对应的值进行处理；
    第一变换展示单元，用于对所述变量名所对应的值按照预定变换规则进行变换，以所述变换后的值作为所述变量名的值；
    第一误报单元，用于在所述敏感信息处理装置中所述的任意一个结构模块出现异常或所述敏感信息识别单元所判断的敏感信息不符合第三方模块设置的敏感信息判断标准时，对所述变量名所对应的值不进行处理，并生成误报日志。
  19. 如权利要求16所述的一种实现敏感信息处理的服务器，其特征在于，所述第一敏感信息识别单元包括：
    第一键值获取单元，用于获取所述MVC目标***中ModelMap中变量信息的变量名；
    第一比较单元，用于比较所述获取的ModelMap中变量信息的变量名与所述第一敏感信息库存储的敏感信息是否相同；
    第二判断单元，用于根据所述第一比较单元的比较结果判断所述待处理信息是否为敏感信息。
  20. 如权利要求16所述的一种实现敏感信息处理的服务器，其特征在于，还包括：
    第一监控策略单元，用于存储预先设置的敏感信息监控策略；
    第一待处理敏感信息单元，用于根据预先设置的敏感信息监控策略判断所述MVC目标***中ModelMap的变量信息的值是否为待处理敏感信息；
    第一发送单元，用于所述第一待处理敏感信息单元判断所述变量信息的值为待处理敏感信息时，将与所述变量信息的值相对应的变量名发送至所述第一敏感信息库。
  21. 一种安全判定***，其特征在于，所述***包括：
    第二敏感信息库，用于存储敏感信息；还用于接收第二待处理敏感信息单元发送的变量名，并判断所述存储的敏感信息中是否包括所述接收的变量名；还用于在所述判断结果为所述敏感信息库中不包括所述接收的变量名时，将所述变量名作为新增敏感信息进行存储；
    第二敏感信息识别单元，用于获取页面中的待处理信息；还用于基于所述第二敏感信息库中存储的敏感信息判断所述待处理信息是否为敏感信息；
    第二信息处理单元，用于存储敏感信息处理策略；还用于在所述第二敏感信息识别单元判断所述待处理信息为敏感信息时，基于所述存储的敏感信息处理策略对所述待处理信息进行处理，形成已处理敏感信息；
    监控单元，用于存储预先设置的敏感信息监控策略；还用于根据所述存储的敏感信息监控策略判断所述页面服务器MVC框架结构中ModelMap的变量信息的值是否为待处理敏感信息；还用于在判断所述变量信息的值为待处理敏感信息时，将与所述变量信息的值相对应的变量名发送至所述第二敏感信息库；
    新增敏感信息日志单元，用于生成新增敏感信息日志，所述新增敏感信息日志包括所述第二敏感信息库中新增敏感信息的数目；
    待处理敏感信息日志单元，用于生成待处理敏感信息日志，所述待处理敏信息日志包括监控单元判断的待处理敏感信息的数目；
    第一安全判定单元，用于获取第一目标***的所述新增敏感信息日志或所述待处理敏感信息日志或所述第二敏感信息库中的数据，并根据预定的判定规则判定所述第一目标***的所属的安全级别。
  22. 如权利要求21所述的一种安全判定***，其特征在于，所述第一安全判断单元包括下述单元中的至少一种：
    第一数目判定单元，用于根据第一时间窗内所述新增敏感信息的数目/第二敏感信息库中存储的敏感信息数目判定所述第一目标***的安全级别；
    第一比值判定单元，根据第二时间窗内所述新增敏感信息的数目与所述待处理敏感信息的数目的比值判定所述第一目标***的安全级别。
  23. 如权利要求21或22所述的一种安全判定***，其特征在于，还包括第二多***判定单元，用于根据预定的判定规则比较所述第一目标***与第二目标***的安全级别；相应的，所述第一安全判定单元获取第二目标***的所述新增敏感信息日志或所述待处理敏感信息日志或所述第二敏感信息库中的数据。
  24. 如权利要求23所述的一种安全判定***，其特征在于，所述多***判定单元包括下述单元中的至少一种：
    第二数目判定单元，用于根据所述第一时间窗内所述第一目标***与第二目标***的新增敏感信息的数目/第二敏感信息库中存储的敏感信息数目比较所述第一目标***与第二目标***的安全级别；
    第二比值判定单元，根据第二时间窗内所述第一目标***与第二目标***新增敏感信息的数目与所述待处理敏感信息的数目的比值比较所述第一目标***与第二目标***的安全级别。
PCT/CN2015/088214 2014-09-03 2015-08-27 一种敏感信息处理方法、装置、服务器及安全判定*** WO2016034068A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2017512318A JP6626095B2 (ja) 2014-09-03 2015-08-27 機密情報処理方法、装置、及び、サーバ、ならびに、セキュリティ決定システム
SG11201701586RA SG11201701586RA (en) 2014-09-03 2015-08-27 Sensitive information processing method, device, server and security determination system
EP15837690.5A EP3190765A4 (en) 2014-09-03 2015-08-27 Sensitive information processing method, device, server and security determination system
US15/448,504 US10505934B2 (en) 2014-09-03 2017-03-02 Sensitive information processing method, device and server, and security determination system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410446695.6 2014-09-03
CN201410446695.6A CN105471823B (zh) 2014-09-03 2014-09-03 一种敏感信息处理方法、装置、服务器及安全判定***

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/448,504 Continuation US10505934B2 (en) 2014-09-03 2017-03-02 Sensitive information processing method, device and server, and security determination system

Publications (1)

Publication Number Publication Date
WO2016034068A1 true WO2016034068A1 (zh) 2016-03-10

Family

ID=55439121

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/088214 WO2016034068A1 (zh) 2014-09-03 2015-08-27 一种敏感信息处理方法、装置、服务器及安全判定***

Country Status (6)

Country Link
US (1) US10505934B2 (zh)
EP (1) EP3190765A4 (zh)
JP (2) JP6626095B2 (zh)
CN (1) CN105471823B (zh)
SG (2) SG10201901732UA (zh)
WO (1) WO2016034068A1 (zh)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106487806A (zh) * 2016-11-17 2017-03-08 上海斐讯数据通信技术有限公司 一种mvc架构中页面支持多用户登录的方法和装置
CN108270735A (zh) * 2016-12-31 2018-07-10 ***通信集团陕西有限公司 一种数据防泄漏方法及设备
CN110866108A (zh) * 2019-11-20 2020-03-06 满江(上海)软件科技有限公司 一种敏感数据检测***及其检测方法
CN111832070A (zh) * 2020-06-12 2020-10-27 北京百度网讯科技有限公司 数据的掩码方法、装置、电子设备和存储介质
CN113488127A (zh) * 2021-07-28 2021-10-08 中国医学科学院医学信息研究所 一种人口健康数据集敏感度处理方法及***
CN114745305A (zh) * 2022-06-15 2022-07-12 中邮消费金融有限公司 一种基于用户行为识别的动态交互方法及***

Families Citing this family (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
MA41350A (fr) * 2015-01-14 2017-11-21 Janssen Pharmaceutica Nv Synthèse d'un inhibiteur de la tyrosine kinase de bruton
CN106202562B (zh) * 2016-07-29 2020-01-31 厦门天锐科技股份有限公司 一种降低敏感信息误判率的方法
CN106203145A (zh) * 2016-08-04 2016-12-07 北京网智天元科技股份有限公司 数据脱敏方法及相关设备
CN106295400A (zh) * 2016-08-04 2017-01-04 北京网智天元科技股份有限公司 蒙版式数据脱敏方法及相关设备
CN107766365A (zh) * 2016-08-18 2018-03-06 北京京东尚科信息技术有限公司 网页生成方法和装置
CN106330958B (zh) * 2016-09-29 2020-07-07 上海创功通讯技术有限公司 一种安全访问方法及装置
CN108229968B (zh) * 2016-12-08 2021-11-09 爱信诺征信有限公司 征信数据采集***及方法
CN107665313B (zh) * 2017-05-19 2019-08-09 平安科技（深圳）有限公司 敏感信息展示方法、装置、存储介质和计算机设备
CN107526842A (zh) * 2017-09-22 2017-12-29 深圳互联先锋科技有限公司 一种批量监控多个网站页面方法及装置
CN107798250B (zh) * 2017-10-13 2021-08-24 平安科技（深圳）有限公司 敏感信息屏蔽规则的下发方法、应用服务器及计算机可读存储介质
CN107871086A (zh) * 2017-10-13 2018-04-03 平安科技（深圳）有限公司 敏感信息屏蔽方法、应用服务器及计算机可读存储介质
CN107958161A (zh) * 2017-11-30 2018-04-24 维沃移动通信有限公司 一种多任务显示方法及移动终端
CN108363717B (zh) * 2017-12-29 2021-03-12 天津南大通用数据技术股份有限公司 一种数据安全级别的识别检测方法及装置
CN108829789A (zh) * 2018-06-01 2018-11-16 平安普惠企业管理有限公司 日志处理方法、装置、计算机设备和存储介质
CN109408247A (zh) * 2018-09-17 2019-03-01 天津龙拳风暴科技有限公司 交互数据处理方法及装置
CN109492423A (zh) * 2018-09-26 2019-03-19 中国平安人寿保险股份有限公司 敏感信息过滤的方法、装置、计算机设备及存储介质
CN111241133A (zh) * 2018-11-29 2020-06-05 ***通信集团重庆有限公司 敏感数据识别方法、装置、设备及计算机存储介质
JP7275698B2 (ja) * 2019-03-19 2023-05-18 富士フイルムビジネスイノベーション株式会社 情報処理装置及びプログラム
CN110188578A (zh) * 2019-05-27 2019-08-30 上海上湖信息技术有限公司 一种自动屏蔽信息的方法及设备
CN110377848A (zh) * 2019-06-21 2019-10-25 深圳壹账通智能科技有限公司 页面访问方法、装置、设备及计算机可读存储介质
CN110262787B (zh) * 2019-06-21 2022-12-13 北京搜房科技发展有限公司 语句替换方法、装置和电子设备
CN110460583B (zh) * 2019-07-15 2022-06-03 中国平安人寿保险股份有限公司 一种敏感信息记录方法及装置、电子设备
CN110826319A (zh) * 2019-10-30 2020-02-21 维沃移动通信有限公司 应用信息的处理方法及终端设备
CN111131183B (zh) * 2019-12-05 2022-05-31 任子行网络技术股份有限公司 网络安全监控方法、计算机设备及计算机可读存储介质
CN112052364A (zh) * 2020-09-27 2020-12-08 深圳前海微众银行股份有限公司 敏感信息检测方法、装置、设备与计算机可读存储介质
CN112398860A (zh) * 2020-11-17 2021-02-23 珠海大横琴科技发展有限公司 一种安全控制的方法和装置
CN113783849B (zh) * 2021-08-25 2023-07-11 福建天泉教育科技有限公司 一种敏感信息的检测方法及终端

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101814118A (zh) * 2009-07-02 2010-08-25 西安电子科技大学 基于图片的网页文本保护方法
CN102467628A (zh) * 2010-11-12 2012-05-23 深圳市虹安信息技术有限公司 一种基于浏览器内核拦截技术的数据保护方法
CN102594557A (zh) * 2012-01-10 2012-07-18 深圳市汉普电子技术开发有限公司 对url加密的方法及装置、url验证的方法及装置
CN103929407A (zh) * 2013-01-15 2014-07-16 腾讯科技（深圳）有限公司 一种木马拦截方法、装置和***

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6615258B1 (en) * 1997-09-26 2003-09-02 Worldcom, Inc. Integrated customer interface for web based data management
US20100287458A1 (en) * 2002-02-01 2010-11-11 Providian Financial Corporation Method, system and computer program for furnishing information to customer representatives
US7437752B2 (en) * 2002-09-23 2008-10-14 Credant Technologies, Inc. Client architecture for portable device with security policies
US20040117501A1 (en) * 2002-12-12 2004-06-17 International Business Machines Corporation Apparatus and method for correction of textual information based on locale of the recipient
US8078481B2 (en) * 2003-12-05 2011-12-13 John Steinbarth Benefits administration system and methods of use and doing business
JP2005092891A (ja) * 2004-10-06 2005-04-07 Toyo Commun Equip Co Ltd アクセス制御エージェントシステム、秘匿情報の漏洩及び改竄防止方法、ネットワークシステムプログラム、及び記録媒体
US7979457B1 (en) * 2005-03-02 2011-07-12 Kayak Software Corporation Efficient search of supplier servers based on stored search results
US8347396B2 (en) * 2007-11-30 2013-01-01 International Business Machines Corporation Protect sensitive content for human-only consumption
US20120102414A1 (en) * 2010-10-21 2012-04-26 Hilmar Demant Distributed controller of a user interface framework for web applications
CN102169610A (zh) * 2010-12-24 2011-08-31 广州广电运通金融电子股份有限公司 交易信息的保密显示方法及其显示***
JP5679327B2 (ja) * 2011-05-31 2015-03-04 楽天株式会社 情報処理システム、情報処理方法、情報処理装置、プログラム及び記録媒体
GB2509709A (en) * 2013-01-09 2014-07-16 Ibm Transparent encryption/decryption gateway for cloud storage services
CN106605220A (zh) * 2014-07-02 2017-04-26 道库门特公司Ip信托单位 用于选择性文档修订的方法及***
US10462135B2 (en) * 2015-10-23 2019-10-29 Intel Corporation Systems and methods for providing confidentiality and privacy of user data for web browsers

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101814118A (zh) * 2009-07-02 2010-08-25 西安电子科技大学 基于图片的网页文本保护方法
CN102467628A (zh) * 2010-11-12 2012-05-23 深圳市虹安信息技术有限公司 一种基于浏览器内核拦截技术的数据保护方法
CN102594557A (zh) * 2012-01-10 2012-07-18 深圳市汉普电子技术开发有限公司 对url加密的方法及装置、url验证的方法及装置
CN103929407A (zh) * 2013-01-15 2014-07-16 腾讯科技（深圳）有限公司 一种木马拦截方法、装置和***

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3190765A4 *

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106487806A (zh) * 2016-11-17 2017-03-08 上海斐讯数据通信技术有限公司 一种mvc架构中页面支持多用户登录的方法和装置
CN106487806B (zh) * 2016-11-17 2020-11-03 上海斐讯数据通信技术有限公司 一种mvc架构中页面支持多用户登录的方法和装置
CN108270735A (zh) * 2016-12-31 2018-07-10 ***通信集团陕西有限公司 一种数据防泄漏方法及设备
CN110866108A (zh) * 2019-11-20 2020-03-06 满江(上海)软件科技有限公司 一种敏感数据检测***及其检测方法
CN111832070A (zh) * 2020-06-12 2020-10-27 北京百度网讯科技有限公司 数据的掩码方法、装置、电子设备和存储介质
CN111832070B (zh) * 2020-06-12 2024-02-27 北京百度网讯科技有限公司 数据的掩码方法、装置、电子设备和存储介质
CN113488127A (zh) * 2021-07-28 2021-10-08 中国医学科学院医学信息研究所 一种人口健康数据集敏感度处理方法及***
CN113488127B (zh) * 2021-07-28 2023-10-20 中国医学科学院医学信息研究所 一种人口健康数据集敏感度处理方法及***
CN114745305A (zh) * 2022-06-15 2022-07-12 中邮消费金融有限公司 一种基于用户行为识别的动态交互方法及***
CN114745305B (zh) * 2022-06-15 2022-09-09 中邮消费金融有限公司 一种基于用户行为识别的动态交互方法及***

Also Published As

Publication number Publication date
US20170180376A1 (en) 2017-06-22
JP7018920B2 (ja) 2022-02-14
JP6626095B2 (ja) 2019-12-25
EP3190765A1 (en) 2017-07-12
JP2017532649A (ja) 2017-11-02
CN105471823B (zh) 2018-10-26
CN105471823A (zh) 2016-04-06
EP3190765A4 (en) 2018-05-02
US10505934B2 (en) 2019-12-10
SG11201701586RA (en) 2017-05-30
JP2020030866A (ja) 2020-02-27
SG10201901732UA (en) 2019-03-28

Similar Documents

Publication Publication Date Title
WO2016034068A1 (zh) 一种敏感信息处理方法、装置、服务器及安全判定***
JP7279227B2 (ja) コンピューティング環境における特権ユーザの監視および異常なアクティビティの検出の手法
US11171925B2 (en) Evaluating and modifying countermeasures based on aggregate transaction status
US10193909B2 (en) Using instrumentation code to detect bots or malware
US10496994B2 (en) Enhanced authentication with dark web analytics
US10432644B2 (en) Access control system for enterprise cloud storage
US11907366B2 (en) Introspection driven by incidents for controlling infiltration
JP2018049602A (ja) ネットワークの異常検出システムのためのグラフ・データベース分析
US20140380475A1 (en) User centric fraud detection
US10248797B1 (en) Systems and methods for zero-day DLP protection having enhanced file upload processing
US20210004492A1 (en) Data breach prevention and remediation
US11310282B1 (en) Scoring confidence in user compliance with an organization's security policies
CN111382422B (zh) 在非法访问用户数据的威胁下更改账户记录的密码的***和方法
JP2024521121A (ja) 組織のセキュリティポリシーに対するユーザコンプライアンスの信頼度のスコアリング
US20220067097A1 (en) Evaluation of security policies in real-time for entities using graph as datastore
US11582250B2 (en) Scanning of content in weblink
Kaneko et al. Detection of Cookie Bomb Attacks in Cloud Computing Environment Monitored by SIEM
Latha et al. Secure cloud web application in an industrial environment: a study
Mostafa et al. A Proposed Logical Framework For Enhance Website's Security Fromthe Attacks
Moss Advanced Image Authentication Level: Technical Report
Elbialy et al. A PROPOSED LOGICAL FRAMEWORK FOR ENHANCE WEBSITE'S SECURITY FROM THE ATTACKS.

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15837690

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2017512318

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2015837690

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2015837690

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 11201701586R

Country of ref document: SG