CN101588363B - Method for estabilishing Web service security analysis model based on program slice - Google Patents

Abstract

The invention relates to software construction technology and network security, especially a method for establishing a program slicing-based Web service security analysis model. The present invention proposes a method for establishing a web service security analysis model based on program slicing, so as to protect key information and common messages in network services from inside and outside, and improve network service security. The technical solutions adopted in the present invention are: 1. ) Establish a slicer module to obtain information flow abstraction in Web service implementation code; 2) Establish a network service analysis module to discover security violations where key information is leaked to Internet users through the current service interface, including the security of independent network services Analysis and security analysis of the network service network; 3) Establish a security report module, which is used to generate a corresponding security report based on the model analysis results, combined with the existing web service security specifications and security measures proposed in the process. The present invention is mainly used to provide Web service security.

Description

A Method of Establishing a Web Service Security Analysis Model Based on Program Slicing

technical field

The invention relates to software construction technology and network security, in particular to the software architecture of the Web service security analysis model based on program slicing, and the method for establishing the program slicing-based Web service security analysis model.

Background technique

Web Service (Web Service) is a service based on Extensible Markup Language XML and HTTPS (full name: Hypertext Transfer Protocol over Secure Socket Layer, Hypertext Transfer Protocol with secure process communication mechanism layer), and its communication protocol is mainly based on simple object access The protocol SOAP, the service description is through the web service description language WSDL, and the unified description, discovery and integration protocol UDDI is used to discover and obtain the metadata of the service.

The unique advantages of Web services in shielding the complexity of the system and exchanging information between heterogeneous platforms make it widely used. At the same time, the security holes in Web services also lead to unsatisfactory application status. The security of Web services can be considered from two perspectives: 1) The security situation in the independent Web service; 2) The security situation in the Web service network. Research topics related to the security of independent Web services mainly include: standard-setting organizations and groups jointly publish Web service security specifications to ensure the security of information in the process of network transmission; introduction of programming skills, including security course training and code review for the development team Etc. Propose the security model and process that should be followed in the software development process.

Through the implementation of security specifications and security technologies, it has a positive effect on the development of secure Web services, but various security specifications and processes have high requirements on the security budget of the development organization and the security knowledge of developers during the implementation process, which is not conducive to the development of Web services. Widely implemented in all web service development. More importantly, although the encryption and signature measures for SOAP messages can effectively protect the confidentiality and integrity of the message transmission process, when a web service implementation itself has potential flaws, the flaws can be exploited by attackers. Information disclosure security breaches caused by exploitation cannot be mitigated by a single external security measure. In fact, if there is no effective mechanism to analyze the security flaws in the implementation of Web services, this type of security loopholes may always exist until they are broken by attackers and cause huge damage to the system. From the software itself, research on the discovery and mitigation of security loopholes in Web services is a powerful measure to improve product security.

Program slicing is the abstraction of programs. By extracting the abstraction of information flow, the slicing theory is applied to the process of information flow acquisition. By analyzing the information flow transmitted during the access process of web services, check whether the key information that needs to be protected is leaked to external users in this information flow, find the security loopholes of key information leakage, and ensure that key information is not illegally accessed. Improve the protection of key information and improve the security of individual web services.

In the Web service network, the proliferation of security holes brings huge impact and loss to the system and users. At present, the formation of the service network is mainly due to the popularity of SOA (Service-Oriented Architecture, service-oriented architecture). SOA models the business process as a workflow. In the workflow, BPEL (Business Process Execution Language, Business Process Execution Language) is used to process multiple Web service interaction processes. Each Web service completes an independent function, and the functional interface is defined as WSDL (Web Service Description Language, web service description language) description, the message passing process between services is completed through SOAP. That is to say, a workflow contains several Web service nodes, and different workflows are connected through interaction, so that all nodes form a web service network. When one of the nodes (that is, Web service) has a security vulnerability, the security vulnerability will be spread through the interaction between nodes in the network, which will bring greater harm to the system. In order to discover the current situation of vulnerability proliferation in the service network, the security situation in the independent web service is used as the working basis, and the information leakage and vulnerability diffusion in the service network are studied by tracking the transfer process of key information or sensitive data among multiple web services , Improving network security is a problem that needs to be solved urgently.

Contents of the invention

In order to overcome the deficiencies of the prior art, the purpose of the present invention is to: propose a method for establishing a Web service security analysis model based on program slicing, and how to combine the analysis results of this model with the existing Web service security specifications and processes Combining the security measures proposed, the key information and general information in Web services are protected internally and externally, and the security of Web services is improved. The technical solution adopted by the present invention is: the method for establishing the Web service security analysis model based on program slicing, comprising the following steps:

Establish a slicer module, which is used to: calculate slices of Java programs by specifying reasonable slice configuration attributes, and provide functional interfaces for calls by the Web service analysis module in this model to obtain the program abstraction related to the slice criteria, that is, the information flow of the program ;

Establish a Web service analysis module for:

(1) Security analysis of independent web services: the first step is to analyze the WSDL protocol to obtain specific information described in web services, including abstract definitions of operations, specific protocols bound to these operations, a bound network endpoint specification, and The network endpoint for the operation; the second step is to call the function interface of the slicer module that has been built, and use the obtained service interface as the slice configuration to slice the source code of the Web service to obtain the information flow of the external interface; the third step is to view the information that needs to be protected Whether the key information exists in the interface information flow, judge whether the information is leaked, and complete the security analysis of the independent Web service;

(2) Security analysis of the Web service network: Based on the slice results and the security analysis results of independent Web services, analyze the information transfer process, check whether key information is leaked between two Web services, and judge the spread of security vulnerabilities in the service network question;

Establish a security report module for: designing the structure of the security report, including interfaces with security vulnerabilities, leaked key information, and studying the content of the mitigation plan from the perspectives of internal measures and external measures. Internal measures include modifying network web services Source code, setting the corresponding method as private and changing the method name to realize the shielding of dangerous interfaces; external measures include adding a security control module to implement signature and encryption, and adding a security management module to implement identity verification and access control.

In the establishment of the slicer module, the slicer module includes the following 3 submodules:

(1) Slicer engine: read in the configuration file, call the open source program dependency analysis framework/library provider program dependency analysis function interface to build the system dependency graph, use the iteration-based slicing algorithm to collect the statements belonging to the current slice in the source program, and form a slice ;

(2) Slicing criteria: It belongs to the composition structure of the configuration file that executes slicing. In the slicing criteria, specify the slice type type, scope and specific statement criteria as the slice center;

(3) The slice result processing unit is the post processor: through the post processor, the mapping conversion from the jimple result to the Java statement is completed. Java is a programming language, and jimple is an intermediate expression form of the Java programming language.

The establishment of the Web service analysis module, wherein the independent service security analysis is to use the source code of the Web service and the key information to be protected as input, and the output is a report on whether there is a security vulnerability for key information disclosure, including:

1) Analyze the WSDL protocol. WSDL is a Web Service Description Language Web service description language to obtain external interface information. The information that can be obtained includes target namespace, service name, port name, operation name, and input and output parameters. The workflow of the WSDL document parser: First obtain the root node definitions of the service in the WSDL document, obtain the service name by calling the definiton.getServices method that returns the service array, obtain the service port by calling the service.getPorts method that returns the service port array, and bind the port call to return the binding The port port.getBinding, through a cycle, for each selected operation name, use the analysisOperation method to call the analysis operation and return the specific information of the operation to obtain the names and types of input parameters and output parameters respectively. After the analysis process is completed, you will get All information of the file is written to the file object File specified by the user for other modules to read;

2) According to the obtained interface name and parameter type, the interface is converted into a legal Java statement as the input of the slicer, and other configurations required by the slicer are completed, including specifying the slice range and type, and calling the slice calculation function to the source program Execute slicing and obtain interface-related information flow from the slicing result;

3) Match the key information to be protected with the interface information flow. If the two overlap, it is judged that there are security holes in the current Web service.

The described Web service network security analysis is to analyze the inter-service interface calls, using two Web service calls as representatives, the analysis process is to determine whether the call address Endpoint of the target Web service and the sequence of target operations, and the order of occurrence To achieve the purpose of judging whether the target Web service calls the target operation in another Web service, when analyzing the dangerous interface calls between services, the input is the analyzed Web service source file and the security vulnerability information file. The aforementioned information files are provided by the slicer module. Generated, the security vulnerability information file provides the service URI containing the security vulnerability, URI is the Universal Resource Identifier resource identifier, and the corresponding dangerous operation, through the matching between the three, the matching is successful, indicating that the analyzed Web service does call Otherwise, it is considered that this web service has not diffused security vulnerabilities, and for the calling relationship judged to have security vulnerabilities, there is a new security vulnerability in the caller of the network web service, and the It joins the list of new dangerous interfaces.

The established security reporting module, provides solutions to mitigate vulnerabilities from two perspectives:

1. By adding security mechanisms including authorization, identity verification, XML signature, or XML encryption, XML is Extensible Markup Language, to achieve the effect of only allowing clients with specific roles to access the service, which can be adopted Measures include authentication, signatures, optional encryption of SOAP messages, and two-tier access control mechanisms;

2. Unpublish the interfaces with security vulnerabilities, cancel the interfaces with security vulnerabilities in the WSDL file, and make modifications in the source files, including making the method private or changing the method name.

The establishment of the slicer module, the slicer module further specifically includes slice calculation: when implemented, the entire slice calculation process is composed of multiple phases, and phase refers to the entire execution process of the slicer, which is divided into several phases. Perform static analysis or process, and mark the beginning and end of these analyzes or processes. Each major phase is composed of 0 or more minor phases, which are executed sequentially. A process refers to a series of processes that can complete a specific function. Program behavior, the first major phase is the slice calculation phase, which is composed of three minor phases, namely, the object flow analysis phase, the dependency analysis phase, and the slice collection phase; the second major phase is the slice result processing phase, without minor phase, the execution process for:

1) First initialize a slicer object, including specifying the slicer program, slice range, and type;

2) Perform object flow analysis in the slicer engine. After specifying the tag name, loading system environment variables and slice configuration, by performing object flow analysis and dependency analysis, a program dependency graph is generated;

3) Collect slices, driven by the slicer engine, mark the nodes in the AST of the program that are part of the slice with the specified tag name tagName, if the node is marked with the specified tagName, it means that it belongs to the slice and is identified There are two types of nodes: taggedClasses and taggedMethods, two collections. In this way, slices are identified;

4) Process the slicing results, complete the mapping from the jimple statement to the Java statement, identify the statement that belongs to the slice according to the previously specified tagName, and then identify the corresponding Java form in the source program according to the line number information of the source statement in the statement statement to convert the slicing result in the form of jimple statement into a general Java statement.

Beneficial effects of the present invention: the present invention is oriented to the development of secure Web service products, aiming at reducing security loopholes in Web services and improving software quality, and constructs a Web service security analysis model, which can be used to discover information in independent Web services and Web service networks Disclosing the existence and proliferation of security vulnerabilities, specific effects include:

1. Propose a discovery method for information leakage security vulnerabilities in independent Web services, which can analyze whether key information has been leaked to external users, so as to improve the protection of key information and reduce security vulnerabilities;

2. Based on the report of the security situation in the independent Web service, a method for discovering the proliferation of security vulnerabilities in the service network is proposed. For the security loopholes existing in a single web service, by analyzing the spread of the loopholes in the service network, a mitigation plan is proposed to reduce the huge loss caused by the spread of the loopholes;

3. Develop a graphical user interface, provide Web service security analysis module configuration, and perform security analysis functions; provide an API interface to encapsulate the analysis function modules provided by this model, and publish it as a Web service interface that can be called by Internet users, reducing user resource requirements , improve efficiency.

In the actual development process, when the number of interfaces in the Web services released by the service provider is large, by running the security analysis tool provided by this model, these interfaces that operate on sensitive data are found and corresponding measures are taken to improve the security of Web services. At the same time, it can effectively save time and money.

Description of drawings

Figure 1 The overall architecture diagram of the Web service security analysis model.

Figure 2 is the flow chart of the operation of the Web service security analysis model.

Detailed ways

The core problems that the present invention attempts to solve include: based on program slicing, obtain the abstraction of information flow from Web service implementation; in independent Web services, obtain the flow direction and leakage of key information; in web service networks, study key information Whether it is transmitted and leaked leads to the spread of vulnerabilities; and how to combine the analysis results of this model with the security measures proposed in the existing web service security norms and processes to internally and externally monitor key information and common messages in web services Protection, improve web service security.

Aiming at the above-mentioned core problems, the present invention is oriented to the coding stage of secure Web service development, obtains information flow abstraction based on program slices, builds a Web service security analysis model, and finds information leakage security loopholes in the Web service network, which has great theoretical significance and practical application value. The main contents include:

1) Study the core idea of program slicing, and apply it to obtain information flow abstraction in Web service implementation code;

2) To study the method of discovering information leakage security loopholes in independent web services, through the separate acquisition and collaborative matching of service interface information flow and key information statement sets, to discover the security violations of key information leaked to Internet users through the current service interface;

3) Based on the results of the analysis of vulnerabilities in independent web services, study the analysis method for the proliferation of security vulnerabilities in web service networks, analyze the transfer process of key information between different web services by viewing the service interface calls, and judge the transfer process Whether a single web service information leakage security vulnerability is spread to more Internet users in the service network;

4) Based on the model analysis results, combined with the existing web service security specifications and security measures proposed in the process, generate corresponding security reports, and provide reasonable mitigation solutions from both internal and external perspectives.

The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments.

The present invention includes a slicer module, a web service analysis module and a safety report module, and the composition and interaction of each module are as shown in Figure 1:

1. Slicer module

This module is an independent functional module, which calculates slices of Java programs by specifying reasonable slice configuration properties. A functional interface is provided for the web service analysis module in this model to call to obtain the program abstraction related to the slicing criterion (that is, the information flow of the program). Features reuse and can be used in other projects with appropriate modification. The slicer module consists of the following three submodules.

(1) Slicer engine: read in the configuration file, call the open source program dependency analysis framework (library) to provide the program dependency analysis API to build the system dependency graph, and use the iteration-based slicing algorithm to collect the statements belonging to the current slice in the source program, Make up slices.

(2) Slicing criterion: it belongs to the composition structure of the configuration file for performing slicing, and in the slicing criterion, type (slicing type), scope (scope) and criteria (specific statement as the slicing center) are specified.

(3) Slicing result processing (i.e. post processor): In the execution process of the slicer engine module, since the static analysis library API is directly used for calculation, the obtained slice result is Jimple (intermediate expression form of java, provided by the soot framework from Java to jimple conversion) statement is not conducive to reading and understanding, so it needs to be converted into java statement after proper processing. Through the post processor, the mapping conversion from the jimple result to the java statement is completed.

2. Web service analysis module

(1) Security analysis of independent web services: the first step is to analyze the WSDL protocol to obtain specific information described in web services, including abstract definitions of operations, specific protocols bound to these operations, a bound network endpoint specification, and The network endpoint for operation; the second step is to call the function interface of the slicer module that has been built, and use the obtained service interface as a slice configuration to slice the source code of the web service to obtain the information flow of the external interface; the third step is to view the information that needs to be protected Whether the key information exists in the interface information flow, judge whether the information is leaked, and complete the security analysis of the independent web service;

(2) Security analysis of web service network: Different web services form a service network through interface calls, and various information is transmitted during the interface call process. When a security vulnerability occurs in a web service, and other web services call the web service to complete new functions and publish it as a new interface, the security vulnerability is diffused, and the information is analyzed based on the slice results and the security analysis results of independent web services During the transmission process, check whether the key information is transmitted and leaked between two web services, and judge the problem of the spread of security vulnerabilities in the service network,

3. Security report module

Design the composition structure of the security report, including interfaces with security vulnerabilities and leaked key information. The content of the mitigation plan is studied from two angles of internal measures and external measures. Internal measures include modifying the source code of the web service, making the corresponding method private and changing the method name, etc., to realize the shielding of dangerous interfaces; external measures include adding a security control module to implement signature and encryption, adding a security management module to implement identity verification and access control, etc. .

Two ways of use: 1) Develop a graphical user interface and complete security analysis locally; 2) Encapsulate the functions of each module into an interface API and publish it as a web service for remote calls by Internet users, reducing user resource consumption and providing a higher level users provide services.

Beneficial effects of the present invention: the present invention is oriented to the development of secure Web service products, aiming at reducing security loopholes in Web services and improving software quality, and constructs a web service security analysis model, which can be used to discover information in independent web services and web service networks Disclosure of the existence and proliferation of security vulnerabilities, with specific outcomes including:

1. Propose a method for discovering information leakage security vulnerabilities in independent web services, which can analyze whether key information has been leaked to external users, so as to improve the protection of key information and reduce security vulnerabilities;

2. Based on the report of the security situation in the independent web service, a method for discovering the proliferation of security vulnerabilities in the service network is proposed. For a security vulnerability existing in a single web service, by analyzing the spread of the vulnerability in the service network, a mitigation plan is proposed to reduce the huge loss caused by the spread of the vulnerability;

3. Develop a graphical user interface, provide web service security analysis module configuration, and perform security analysis functions; provide an API interface to encapsulate the analysis function module provided by this model, and publish it as a web service interface that can be called by Internet users to reduce user resource requirements , improve efficiency.

In the actual development process, when the number of interfaces in the web service released by the service provider is large, by running the security analysis tool provided by this model, these interfaces that operate on sensitive data are found and corresponding measures are taken to improve the security of web services. At the same time, it can effectively save time and money.

Each module in the present invention will be further described below in conjunction with the drawings and embodiments.

1. Slice calculation

During implementation, the entire slice calculation process consists of multiple Phases. Phase refers to the entire execution process of the slicer, which is divided into several phases. Static analyzes or procedures are performed in phase, and the start and end of these analyzes or procedures can be marked. Each major phase (big phase) is composed of 0 or more minor phases (small phases), which are executed sequentially.

1) First initialize a slicer (slicer) object, including specifying the program to be sliced, slice range, and type;

2) Perform object flow analysis in the slicer engine. After specifying the tag (label) name, loading system environment variables and slice configuration, by performing object flow analysis and dependency analysis, a program dependency graph is generated;

3) Collect slices, driven by the slicer engine, and mark the nodes that are part of the slice in the AST of the program with the specified tagName (tag name), that is, if the node is marked with the specified tagName, it means that it belongs to the slice Components, the identified nodes have two types (taggedClasses (label class) and taggedMethods (label method) two collections (collection)), in this way, identify slices.

4) Process the slicing result and complete the mapping from the jimple statement to the java statement. Identify the statement that belongs to the slice according to the previously specified tagName, and then identify the corresponding statement in the form of java in the source program according to the line number information of the source statement in the statement, and realize the conversion of the slice result in the form of jimple statement into a general java statement function.

2. Independent web service security analysis

In this process, the source code of the web service and the key information to be protected are used as input, and the output is a report on whether there is a security vulnerability for key information leakage.

1) Analyze the WSDL protocol to obtain external interface information. The information that can be obtained includes target namespace, service name, port name, operation name, and input and output parameters. The developed WSDL document parser workflow: first obtain the definitions of the service (the root node of the service) in the WSDL document, obtain the service name through the definition.getServices method (calling this method returns an array of services), and pass service. The method returns an array of service ports) method to get the service port, bind the port port.getBinding (use this method to return the bound port), through a loop, for each selected operation name, use the analysisOperation method (call this method to analyze operation, returns the specific information of the operation) to obtain the names and types of input parameters and output parameters respectively. After the parsing process is over, write all the obtained information into the File (file object) specified by the user for other modules to read.

2) According to the obtained interface name and parameter type, the interface is converted into a legal Java statement as the input of the slicer, and after completing other configurations required by the slicer (specifying the slice range, type, etc.), call the slice calculation function to The source program executes slicing, and obtains the interface-related information flow from the slicing result;

3) Match the key information to be protected with the interface information flow. If the two overlap, it is judged that there are security vulnerabilities in the current web service.

3. Web service network security analysis

Analyze interface calls between services. Taking two web service calls as representatives, the analysis process judges whether the target web service calls another web service by judging whether the Endpoint (the calling address of the web service) of the target web service appears, the order of the target operations, and the order of occurrence The purpose of the target operation

When analyzing dangerous interface calls between services, the input is the analyzed web service source file and security vulnerability information file (generated by the slicer module). The security vulnerability information file provides the service URI (UniversalResource Identifier, resource identifier) containing the security vulnerability and the corresponding dangerous operation. Through the matching between the three, if the matching is successful, it means that the analyzed web service does call the operation containing the security vulnerability, which leads to the proliferation of the security vulnerability; otherwise, it is considered that the web service has not diffused the security vulnerability.

For the calling relationship judged to have a security hole, there is a new security hole in the web service caller, which should be added to the new list of dangerous interfaces.

4. Safety report

For the discovered potential security vulnerabilities, the security report provides corresponding mitigation measures to eliminate threats for users and provide auxiliary suggestions for improving the security of web services. Combined with different needs of users, solutions are provided from two perspectives to alleviate vulnerabilities:

1. When the developer really needs to release the service to a specific user group, by adding security mechanisms (such as authorization, authentication, XML (Extensible Markup Language, Extensible Markup Language) signature, XML encryption, etc.), To achieve the effect of only allowing clients with specific roles to access the service, the measures that can be taken include identity verification, signature, selective encryption of SOAP messages, and two-layer access control mechanisms.

2. Unpublish interfaces with security vulnerabilities. This mitigating measure applies to the situation when the developer exposes the operation interface of sensitive information in an unintentional situation (such as a WSDL file automatic generation tool). At this point, it should not be used by any external clients, so the interface needs to be canceled in the WSDL file and modified in the source file (such as making the method private, changing the method name, etc.).

In practice, these mitigating measures can be used in conjunction with each other to produce the best results.

The following briefly describes the operation process of the security analysis model: As can be seen from Figure 2, when users perform security analysis on their own Web services, they need to provide the following information: Web service source code and key information to be protected. The functions completed by the slicer module include: extracting the key statement set from the web service source code according to the key information for subsequent use; using the obtained slicing criteria to calculate slices; on the basis of the previous two steps, process the slicing results and determine the security The existence of vulnerabilities. The web service protocol analysis module completes two functions: first, obtain and process the external user interface exposed by the web service, generate the slicing criteria required in the previous step, call the slicer module to perform slicing of the source program, and determine the security vulnerability Existence; second, according to the calculation results of the slicer module, combined with the interface call relationship between different services in the web service network, analyze the key information transmission problems involved in the information flow transmission process, and determine the spread of security vulnerabilities.

Claims (5)

1. A method for setting up a Web service security analysis model based on program slicing, characterized in that it comprises the following steps: Establish a slicer module, which is used to: calculate slices of Java programs by specifying reasonable slice configuration attributes, and provide functional interfaces for calls by the network web service analysis module in this model to obtain program abstractions related to slice criteria, that is, program information flow; Establish a Web service analysis module for: (1) Security analysis of independent Web services: the first step is to analyze the WSDL protocol. WSDL is a Web Service Description Language Web service description language to obtain specific information described in Web services, including abstract definitions of operations, and specific protocols bound to these operations , a bound network endpoint specification and the network endpoint for operation; the second step calls the constructed slicer module function interface, uses the obtained service interface as slice configuration, slices the source code of the Web service, and obtains the information of the external interface The third step is to check whether the key information to be protected exists in the interface information flow, judge whether the information is leaked, and complete the security analysis of the independent Web service; (2) Security analysis of the Web service network: Based on the slice results and the security analysis results of independent Web services, analyze the information transfer process, check whether key information is leaked between two Web services, and judge the spread of security vulnerabilities in the service network question; Establish a security report module for: designing the structure of the security report, including interfaces with security vulnerabilities, leaked key information, and studying the content of the mitigation plan from the perspectives of internal measures and external measures. Internal measures include modifying network web services Source code, setting the corresponding method as private and changing the method name to realize the shielding of dangerous interfaces; external measures include adding a security control module to implement signature and encryption, and adding a security management module to implement identity verification and access control. 2. A method of establishing a program slicing-based Web service security analysis model according to claim 1, characterized in that, in the described establishment of a slicer module, the slicer module includes the following 3 submodules: (1) Slicer engine: read in the configuration file, call the open source program dependency analysis framework/library provider program dependency analysis function interface to build the system dependency graph, use the iteration-based slicing algorithm to collect the statements belonging to the current slice in the source program, and form a slice ; (2) Slicing criteria: It belongs to the composition structure of the configuration file that executes slicing. In the slicing criteria, specify the slice type type, scope and specific statement criteria as the slice center; (3) The slice result processing unit is the post processor: through the post processor, the mapping conversion from the jimple result to the Java statement is completed. Java is a programming language, and jimple is an intermediate expression form of the Java programming language. 3. A method for establishing a program slicing-based Web service security analysis model according to claim 1, wherein said establishment of a Web service analysis module, wherein the independent Web service security analysis is based on Web service source code and The key information that needs to be protected is used as the input, and the output is a report on whether there is a key information leakage security vulnerability, including: 1) Parse the WSDL protocol and obtain external interface information. The available information includes the target namespace, service name, port name, operation name, and input and output parameters. The workflow of the WSDL document parser: first obtain the root node of the service in the WSDL document definitions, obtain the service name by calling the definiton.getServices method that returns the service array, obtain the service port by calling the service.getPorts method that returns the service port array, and call the bound port port.getBinding to return the bound port. For a selected operation name, use the analysisOperation method to call the analysis operation and return the specific information of the operation to obtain the name and type of the input parameters and output parameters respectively. After the analysis process is completed, write all the obtained information into the file object File specified by the user , for other modules to read; 2) According to the obtained interface name and parameter type, the interface is converted into a legal Java statement as the input of the slicer, and other configurations required by the slicer are completed, including specifying the slice range and type, and calling the slice calculation function to the source program Execute slicing and obtain interface-related information flow from the slicing result; 3) Match the key information to be protected with the interface information flow. If the two overlap, it is determined that there are security vulnerabilities in the current Web service; The described Web service network security analysis is to analyze the inter-service interface calls, using two Web service calls as representatives, the analysis process is to determine whether the call address Endpoint of the target Web service and the sequence of target operations, and the order of occurrence To achieve the purpose of judging whether the target Web service calls the target operation in another Web service, when analyzing the dangerous interface calls between services, the input is the analyzed Web service source file and the security vulnerability information file. The aforementioned information files are provided by the slicer module. Generated, the security vulnerability information file provides the service URI containing the security vulnerability, URI is the Universal Resource Identifier resource identifier, and the corresponding dangerous operation, through the matching between the three, the matching is successful, indicating that the analyzed Web service does call Otherwise, it is considered that this web service has not diffused security vulnerabilities, and for the calling relationship judged to have security vulnerabilities, there is a new security vulnerability in the caller of the network web service, and the It joins the list of new dangerous interfaces. 4. A method of establishing a program slicing-based Web service security analysis model according to claim 1, wherein said establishment of a security report module provides solutions from two perspectives to alleviate vulnerabilities: (1) By adding security mechanisms including authorization, identity verification, XML signature, or XML encryption, XML is Extensible Markup Language, to achieve the effect of only allowing clients with specific roles to access the service. Measures taken include authentication, signatures, optional encryption of SOAP messages, and two-tiered access control mechanisms; (2) Unpublish the interfaces with security vulnerabilities, cancel the interfaces with security vulnerabilities in the WSDL file, and make modifications in the source files, including making the method private or changing the method name. 5. A method for establishing a program slicing-based Web service security analysis model according to claim 1 or 2, characterized in that said establishment of a slicer module, the slicer module further specifically includes slice calculation: when implemented , the entire slice calculation process consists of multiple phases. A phase refers to the entire execution process of the slicer, which is divided into several phases. Static analysis or processes are performed in phases, and the start and end of these analyzes or processes can be marked. Each large The major phase is composed of 0 or more minor phases, which are executed sequentially. A process refers to a series of program behaviors that can complete a specific function. The first major phase is the slice calculation phase, which consists of 3 minor phases. That is, the object flow analysis phase, the dependency analysis phase, and the slice collection phase; the second major phase is the slice result processing phase, without a minor phase, and the execution process is as follows: 1) First initialize a slicer object, including specifying the slicer program, slice range, and type; 2) Perform object flow analysis in the slicer engine. After specifying the tag name, loading system environment variables and slice configuration, by performing object flow analysis and dependency analysis, a program dependency graph is generated; 3) Collect slices, driven by the slicer engine, mark the nodes in the AST of the program that are part of the slice with the specified tag name tagName, AST is the abbreviation of Abstract Syntax Tree, which means the abstract syntax tree, if the node is specified by the tagName Annotation means that it belongs to the slice. There are two types of marked nodes, namely taggedClasses and taggedMethods. In this way, the slice is identified; 4) Process the slicing results, complete the mapping from the jimple statement to the Java statement, identify the statement that belongs to the slice according to the previously specified tagName, and then identify the corresponding Java form in the source program according to the line number information of the source statement in the statement statement to convert the slicing result in the form of jimple statement into a general Java statement.

Images