Method for automatically verifying security of communication software
By building communication software equipment topology diagrams, analyzing security protocols and operation logs, detecting malicious links, associating leaked data with authentication, and optimizing device risk connection topology diagrams, the problem of insufficient attack resistance of traditional automated verification methods is solved, and more efficient Safety risk assessment and management.
Patent Information
- Application Number
- CN202411251452.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-07
- Publication Date
- 2024-12-03
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
Traditional communication software automation verification methods are insufficient in the face of advanced persistent threats or targeted attacks. Attackers can bypass the automated verification system by imitating the behavior of normal users or social engineering methods, resulting in security protection measures. Ineffective.
By obtaining communication software device port data, building a device topology diagram, analyzing security protocol data to divide risk connections, extracting and analyzing operation logs and communication link data, detecting malicious links, associating identity verification and protection for automated authentication and authentication, and optimizing device risk connection topology Figure, uploaded to the management platform to perform security tasks.
It realizes comprehensive security risk assessment and optimization of communication software, enhances the anti-attack capability of the automated identity verification system, improves network security and management efficiency, and reduces manual intervention and errors.
Smart Images

Figure CN119071073A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of information security technology, and in particular to a method for automatically verifying the security of communication software. Background Art
[0002] With the rapid development of information technology and the popularization of the Internet, communication software has become an indispensable part of people's daily life and work. Whether it is instant messaging, video calls or file sharing, communication software has greatly facilitated people's communication. However, the accompanying security risks are also becoming increasingly prominent. Cyber attacks, data leaks, identity theft and other incidents occur frequently, seriously threatening users' personal privacy and data security. Therefore, it is particularly important to improve the security of communication software, especially automated verification methods. Although traditional automated verification methods can improve the security of identity authentication, they are not able to resist attacks when facing advanced persistent threats or targeted attacks. Attackers bypass the automated verification system by imitating the behavior of normal users or using social engineering methods, thereby causing security protection measures to fail. Summary of the invention
[0003] Based on this, it is necessary for the present invention to provide a method for automated security verification of communication software to solve at least one of the above technical problems.
[0004] To achieve the above purpose, a method for automatically verifying the security of communication software includes the following steps:
[0005] Step S1: Acquire communication software device port data, and construct a communication software device topology structure based on the communication software device port data, thereby obtaining a communication software device topology map; acquire communication software security protocol data; divide the communication software device topology map into risk connections based on the communication software security protocol data, thereby obtaining a communication software device risk connection topology map;
[0006] Step S2: obtaining the communication software operation log, and extracting the identity authentication data according to the communication software operation log data, thereby obtaining the identity authentication data; performing identity authentication risk analysis according to the identity authentication data, thereby obtaining the identity authentication risk data;
[0007] Step S3: extracting communication link data according to the communication software log data, thereby obtaining communication link data; performing malicious link detection according to the communication link data, thereby obtaining malicious link data; performing identity authentication information leakage analysis on the identity authentication data according to the malicious link data, thereby obtaining identity authentication leakage data;
[0008] Step S4: performing correlation analysis based on the identity authentication leakage data and the identity authentication risk data, thereby obtaining the identity authentication leakage risk data; performing automated identity authentication protection based on the identity authentication leakage risk data, thereby obtaining automated identity authentication protection data;
[0009] Step S5: Optimize the identity authentication security risk of the communication software device risk connection topology map based on the automated identity verification protection data, thereby obtaining identity authentication security risk optimization data, and upload it to the communication software management platform to execute the automated identity authentication optimization task.
[0010] The present invention can fully understand the connection status of each device in the network by acquiring the port data of the communication software device, so as to construct a complete communication software device topology map. This topology map can help identify the communication relationship and data flow path between devices. The topology map is divided into risky connections using security protocol data, and it can be clear which connections have security risks. In this way, high-risk areas in the network can be identified and evaluated in advance, providing a basis for subsequent security protection measures. By analyzing the operation log of the communication software, data related to identity authentication can be extracted. This is the basis for understanding user identity authentication behavior and mode. Risk analysis based on the extracted identity authentication data can identify existing identity authentication risks, such as abnormal login behavior or frequent identity authentication failures. This helps to discover potential security threats in advance. By analyzing the communication software log data, all communication link information can be extracted. These data are crucial to understanding data exchange and its security in the network. Malicious link detection on the communication link can identify malicious behavior or attack attempts, thereby preventing malicious links from causing damage to users. By detecting malicious links and analyzing their association with identity authentication data, identity authentication information leakage paths can be discovered, helping to further improve the security of the system. Correlating and analyzing identity authentication leakage data with identity authentication risk data can more accurately assess the security risks in the user identity authentication process and identify the scenarios where leakage occurs. Based on the leakage risk data, the system can automatically adjust the verification method to improve security. This dynamic protection measure can more effectively respond to advanced threats and enhance the anti-attack capabilities of the automated identity authentication system. Based on the automated verification of identity protection data, the risk connection topology of the communication software equipment is further optimized to improve the security of the overall network. This process ensures the security and reliability of identity authentication. Uploading the optimized data to the communication software management platform can automatically perform related security tasks, realize closed-loop management of security protection, reduce manual intervention and errors, and improve the security and management efficiency of the entire system.
[0011] Optionally, step S1 specifically includes:
[0012] Step S11: Acquire communication software device port data, and extract device port number data and communication flow direction data according to the communication software device port data, thereby obtaining device port number data and communication flow direction data;
[0013] Step S12: constructing a communication topology node according to the device port number data, thereby obtaining communication topology node data;
[0014] Step S13: performing communication topology connection on the communication topology nodes according to the communication flow direction data, thereby obtaining communication topology connection data;
[0015] Step S14: constructing a communication software topology structure according to the communication topology node data and the communication topology connection data, thereby obtaining a communication software device topology diagram;
[0016] Step S15: Acquire the communication software security protocol data, and extract the digital certificate data according to the communication software security protocol data, thereby obtaining the digital certificate data;
[0017] Step S16: dividing the communication software device topology map into risky connections according to the digital certificate data, thereby obtaining a communication software device risky connection topology map.
[0018] The present invention can accurately identify the port usage of each device in the network by acquiring the port data of the device and extracting the port number information. This helps to discover open ports and identify potential security vulnerabilities. By analyzing the communication flow data, the flow path of data in the network can be determined, which helps to understand the communication relationship and data transmission between devices and provide basic data for the subsequent topological structure construction. Using the extracted device port number data, a communication topology node can be constructed. Each node represents a device or communication terminal in the network. This is the first step in establishing a network topology map and is also the basis for subsequent communication connection analysis. Through this method, a clear network node map can be formed to help network managers understand the composition and node distribution of the entire network. According to the communication flow data, the constructed topological nodes are connected to form communication topological connection data. This process can clarify the actual communication path and connection relationship in the network. Through this connection data, the communication relationship between each device can be intuitively displayed, helping to identify bottlenecks, potential security threats and abnormal traffic. The topological node data and communication connection data are integrated to finally form a complete communication software device topology map. This diagram can fully display the structure and data flow of the entire network. It is a core tool for network security analysis and management. Through this topology diagram, network administrators can better understand the entire network architecture, discover potential security risks, and provide reference for the deployment of protective measures. By analyzing the security protocol data of the communication software, the relevant information of the digital certificate is extracted. This information is very important for understanding the security authentication and encryption of each node in the network. The digital certificate data can provide the authentication status of each node, which helps to ensure that every communication node in the network is verified, thereby improving the security of the entire network. According to the digital certificate data, the generated communication software device topology diagram is divided into risky connections, and connections with security risks can be identified. These risks come from insecure communication protocols, expired or untrusted certificates, etc. The generated risk connection topology diagram can help network administrators intuitively see which connections have security issues and take corresponding protective measures. This method can significantly improve network security and reduce the risk of data leakage and attacks.
[0019] Optionally, step S2 specifically includes:
[0020] Step S21: obtaining the communication software operation log, and extracting the identity authentication data according to the communication software operation log data, thereby obtaining the identity authentication data;
[0021] Step S22: classifying the verification type according to the identity verification data, thereby obtaining knowledge feature verification data and biometric feature verification data;
[0022] Step S23: performing identity authentication anomaly detection on the knowledge feature type verification data, thereby obtaining knowledge feature type anomaly verification data;
[0023] Step S24: performing identity authentication anomaly detection on the biometric verification data, thereby obtaining biometric abnormality verification data;
[0024] Step S25: integrating identity authentication exception data according to the knowledge feature type exception verification data and the biometric feature type exception verification data, thereby obtaining identity authentication exception data;
[0025] Step S26: Perform identity authentication risk assessment based on the identity authentication abnormality data to obtain identity authentication risk data.
[0026] The present invention can extract data related to user identity authentication by analyzing the operation log of the communication software. These data are the basis for understanding user behavior and verification process, and can provide important information for subsequent security analysis. The extracted identity authentication data lays the foundation for subsequent verification type classification and abnormal detection, ensuring the comprehensiveness and accuracy of the data. The identity authentication data is divided into two categories: knowledge feature type (such as password, security question) and biometric feature type (such as fingerprint, facial recognition), which can more accurately analyze and process different types of verification methods. The classified data enables the system to take more targeted security measures according to the characteristics of different verification types, and improve the effectiveness and security of verification. Through the abnormal detection of knowledge feature type verification data (such as password input), abnormal behaviors such as frequent failed attempts, unusual time or place can be found, thereby identifying potential security threats. This detection method can provide early warning for the system, and timely discover and respond to attack attempts (such as brute force cracking). Biometric authentication (such as fingerprint or facial recognition) is usually more reliable, but it is still subject to attacks (such as forged biometrics). Anomaly detection of this data can identify abnormal biometric input and prevent forgery or illegal use. By detecting anomalies in biometric data, the security of the identity authentication system can be further enhanced to ensure that only legitimate users can pass the authentication. Integrating knowledge feature-based and biometric-based abnormal authentication data can form a comprehensive identity authentication abnormality data report. This integration helps to fully understand the security threats facing the system and formulate more comprehensive protection measures. The integrated data can provide system administrators with a broader perspective to help them identify multi-level and multi-dimensional attack patterns and potential risks. Risk assessment based on integrated identity authentication abnormality data can quantify the security risks faced by the system and help determine which authentication methods or user behaviors pose higher security threats. The results of risk assessment can guide the optimization of security policies, such as increasing vigilance against high-risk authentication behaviors or adjusting the authentication mechanism to enhance the overall security of the system.
[0027] Optionally, step S23 is specifically:
[0028] Step S231: extracting verification position features and verification time series features from the knowledge feature type verification data, thereby obtaining knowledge feature type verification position data and knowledge feature type verification time series data;
[0029] Step S232: performing verification position statistics on the knowledge feature type verification position data, thereby obtaining low-frequency verification position data;
[0030] Step S233: performing verification time interval statistics on the knowledge feature type verification time series data, thereby obtaining short-interval verification data;
[0031] Step S234: performing a verification anomaly intersection operation according to the short-interval verification data and the low-frequency verification position data, thereby obtaining verification anomaly data;
[0032] Step S235: Acquire knowledge feature type historical verification data;
[0033] Step S236: clustering the knowledge feature type historical verification data according to the verification abnormality data, thereby obtaining knowledge feature type abnormal verification data.
[0034] The present invention can help identify the location where the user usually performs verification by extracting verification location data from knowledge feature-based verification data. By recording and analyzing these location features, the system can establish the user's normal behavior pattern, and extracting verification time series data can identify the user's verification behavior habits in different time periods. By analyzing these time series features, abnormal time behaviors can be captured, such as overly frequent or irregular verification attempts. Statistical analysis of the verification location data can identify the user's commonly used verification locations and low-frequency use locations. Low-frequency verification locations prompt users to verify at abnormal locations, or indicate that the verification request comes from unfamiliar or potentially dangerous locations. After identifying low-frequency locations, the system can pay special attention to these locations to prevent attackers from using uncommon locations to make malicious verification attempts. Statistical verification of the time interval between verification operations can help identify unreasonable short-interval behaviors. Abnormally short time intervals indicate that some automated tools are trying to crack by force. By identifying these short time intervals, the system can respond to potential security threats more promptly and prevent attackers from making multiple attempts quickly. By performing an intersection operation on low-frequency verification location data and short-interval verification data, abnormal verification attempts that are performed at low-frequency locations and in a short period of time can be identified. Such behaviors are often more aggressive and therefore require special attention. This intersection operation helps to prioritize the identification and processing of the most risky abnormal behaviors, optimize the allocation of security resources, and improve the overall security of the system. Obtaining historical verification data with knowledge characteristics can provide a reference for current abnormal verification behaviors. Historical data can help the system understand the user's long-term behavior patterns, so as to more accurately determine whether the current behavior is abnormal. By integrating historical data, the system can analyze on a larger scale and improve the accuracy of anomaly detection. Clustering analysis of historical verification data based on verification anomaly data can classify similar abnormal behaviors, which helps to identify attack patterns or recurring abnormal behaviors, helping the system to better understand and respond to complex attacks. The clustered data can be further classified to help identify which types of abnormal behaviors are the most dangerous and need to be processed first. This process can improve the response efficiency of the system and reduce the potential impact of security threats.
[0035] Optionally, step S24 is specifically:
[0036] Step S241: extracting iris verification features from the biometric verification data to obtain iris verification data;
[0037] Step S242: Obtaining iris historical verification data;
[0038] Step S243: performing iris texture verification matching on the iris verification data according to the iris historical verification data, thereby obtaining iris texture verification data;
[0039] Step S244: extracting abnormal verification data according to the iris texture verification data, thereby obtaining iris texture abnormal verification data;
[0040] Step S245: performing verification time distribution statistics according to the historical iris verification data, thereby obtaining verification time distribution data;
[0041] Step S246: performing a time range comparison on the iris texture abnormality verification data according to the verification time distribution data, thereby obtaining the iris texture abnormality verification time data;
[0042] Step S247: performing abnormal clustering on the biometric verification data according to the iris texture abnormal verification time data, thereby obtaining biometric abnormal verification data.
[0043] The present invention can obtain the user's iris image and its unique texture features by extracting iris verification features from biometric verification data. This high-precision biometric data provides extremely high security for identity authentication. Iris features are unique and stable. By extracting these features, the accuracy of verification can be greatly improved and identity forgery can be prevented. Acquiring historical iris verification data can provide an important historical benchmark for current verification behavior. By comparing the current iris verification data with historical data, the legality of the verification behavior can be better judged. The accumulation and analysis of historical data helps to identify abnormal verification behaviors, such as iris patterns that do not conform to conventional or verification attempts that are inconsistent with historical records. By performing texture matching between the current iris verification data and the historical iris data, the uniqueness and authenticity of the user's identity can be ensured. This matching can effectively prevent unauthorized access. The texture matching process can detect tiny differences and prevent attackers from using forged iris images to attempt to pass verification. By performing anomaly detection on the matched iris texture data, it is possible to identify verification behaviors that are inconsistent with normal situations, such as large texture differences or abnormally increased number of verification failures. This detection can provide early warnings for the system and promptly detect potential security threats, such as malicious access or identity theft attempts. By statistically analyzing the time distribution of historical iris verification data, it is possible to identify the time periods when users usually perform verifications. This analysis helps to establish the user's time behavior pattern, and the statistical results can help identify abnormal verification times, such as verification attempts made during unusual time periods, thereby further improving security detection capabilities. Comparing iris texture abnormal verification data with verification time distribution data can identify abnormal verification behaviors that occur during unusual time periods. This comparison can help the system better detect potential security issues. Through cross-validation in the time dimension, it is possible to more accurately identify those abnormal verification behaviors that really pose risks, thereby improving the system's protection capabilities. Cluster analysis of biometric verification data based on abnormal verification data within a time range can classify similar abnormal behaviors, which helps to identify attack patterns, especially those repeated or multiple attack behaviors attempted in different time periods. The results of cluster analysis can help formulate more targeted security strategies, prioritize high-risk abnormal behaviors, and further improve the overall security of communication software.
[0044] Optionally, step S3 specifically includes:
[0045] Step S31: extracting communication link data according to the communication software log data, thereby obtaining communication link data;
[0046] Step S32: classifying link characteristics according to the communication link data, thereby obtaining link structure characteristic data and link behavior characteristic data;
[0047] Step S33: performing malicious link structure analysis on the link structure feature data, thereby obtaining malicious link structure data;
[0048] Step S34: performing malicious link behavior analysis on the link behavior feature data, thereby obtaining malicious link behavior data;
[0049] Step S35: integrating malicious link data according to the malicious link structure data and the malicious link behavior data, thereby obtaining malicious link data;
[0050] Step S36: Perform identity authentication information leakage analysis on the identity authentication data according to the malicious link data, thereby obtaining identity authentication leakage data.
[0051] The present invention can fully grasp the detailed information of all network communications, including source IP address, target IP address, communication time, data volume, etc., by extracting communication link data from the log of communication software, which provides basic data for subsequent analysis. This extraction can record and monitor communication activities in real time, timely discover abnormal or suspicious links, and provide forward-looking data support for system security protection. The communication link data is classified into link structure feature data and link behavior feature data, and the topological structure and behavior pattern of each link can be analyzed respectively. This classification makes the detection of malicious links more accurate and efficient. The classified data can be deeply analyzed in two dimensions of structure and behavior, which helps to identify complex attack patterns, such as malicious links hidden by specific behaviors. By analyzing the link structure features, topological structures or patterns similar to known malicious links can be found, such as abnormal network nodes or link paths. In this way, potential threats hidden in normal communications can be effectively identified, and structural analysis can identify complex or hidden malicious link structures, reduce misjudgments and omissions, and improve the accuracy of the overall security system. By analyzing the characteristics of link behavior, abnormal communication behaviors can be found, such as abnormally high-frequency access requests, abnormal data packet size, or communication in abnormal time periods. This behavior analysis can timely detect and prevent malicious behaviors. Behavior analysis provides the system with real-time monitoring capabilities. When abnormal behavior is detected, defensive measures can be taken immediately to reduce potential security risks. By integrating structural and behavioral data, a more complete malicious link feature portrait can be constructed. Through this comprehensive analysis, the system can better identify complex threats that are difficult to detect in a single dimension. The integrated malicious link data provides a unified information source for security management, which facilitates further threat tracking and disposal. By analyzing the association between malicious links and authentication data, it is possible to identify whether malicious links have led to the leakage of user authentication information, which helps to understand the attacker's strategy and approach, thereby improving protection measures. By detecting and analyzing the leakage of authentication information, the system can adjust and optimize the verification mechanism in real time to prevent user information leakage caused by malicious links and improve the overall authentication security.
[0052] Optionally, step S33 is specifically:
[0053] Step S331: extracting link path feature data according to the link structure feature data, thereby obtaining link path feature data;
[0054] Step S332: extracting malicious link history data according to the communication software operation log, thereby obtaining malicious link history data;
[0055] Step S333: setting a path parameter quantity threshold value and a path length threshold value according to the malicious link history data, thereby obtaining path parameter quantity threshold data and path length threshold data;
[0056] Step S334: screening the link path feature data for special character structures, thereby obtaining character abnormal link structure data;
[0057] Step S335: performing parameter structure threshold comparison on the link path feature data according to the path parameter quantity threshold data, thereby obtaining parameter abnormal link structure data;
[0058] Step S336: performing a length structure threshold comparison on the link path feature data according to the path length threshold data, thereby obtaining length abnormal link structure data;
[0059] Step S337: performing malicious link structure intersection and merging according to the character abnormal link structure data, the parameter abnormal link structure data, and the length abnormal link structure data, thereby obtaining malicious link structure data.
[0060] The present invention can capture the path information of each communication link in detail by extracting link path feature data, including the complexity of the path, the number of forwarding nodes, path parameters, etc., which provides detailed basic data for subsequent malicious link analysis. The extraction of link path feature data increases the analysis dimension, so that the system can not only detect from the behavioral or structural level, but also judge the security of the link from the path feature. By extracting the malicious link historical data in the operation log of the communication software, the system can identify the malicious link features that have been marked or detected before. This process helps to establish a feature library of malicious links, which is convenient for subsequent detection. The accumulation and extraction of malicious link historical data can accelerate the detection process of new links. By comparing with historical data, malicious links can be quickly identified to reduce potential threats. According to the historical malicious link data, the path parameter number threshold and the path length threshold are set to establish a clear detection standard. These standards can be used to determine whether a new link has malicious features. Through the setting and adjustment of the threshold, the system can flexibly respond to different security requirements and risk levels to enhance the overall defense capability. By screening the structure of special characters in the link path, malicious links that use obfuscation techniques can be identified. These special characters are often used to bypass security detection mechanisms. Therefore, this step can improve the system's ability to resist advanced attacks. By screening specific character structures, normal links can be avoided from being misjudged as malicious links, thereby reducing false positives and improving the accuracy of detection. By comparing with the path parameter quantity threshold data, the system can detect link parameters that exceed the normal range. These abnormal parameters are often associated with malicious links. Early identification can prevent potential attacks. The comparison of parameter structure thresholds enables the detection mechanism to accurately locate malicious links, reducing false positives while improving the overall security protection capabilities of the system. By comparing the path length threshold, links with abnormal path lengths can be detected. Paths that are too long or too short are often used by attackers to hide malicious intentions. Early identification helps prevent attacks. The application of length structure thresholds can effectively filter out links that are obviously longer than the normal length, making the system more targeted and effective during the detection process. By intersecting and merging abnormal data in multiple dimensions such as character anomalies, parameter anomalies, and length anomalies, the system can comprehensively evaluate the maliciousness of the link. Such multi-dimensional intersection analysis improves the accuracy and effectiveness of detection. Through the malicious link structure data obtained after intersection and merging, the system can more accurately identify real malicious links, reduce false positives and missed positives, and provide users with a safer communication environment.
[0061] Optionally, step S34 is specifically:
[0062] Step S341: extracting redirection behavior data from link behavior feature data, thereby obtaining redirection behavior data;
[0063] Step S342: performing redirection frequency statistics according to the redirection behavior data, thereby obtaining high-frequency redirection behavior data;
[0064] Step S343: performing redirection website reputation statistics according to the redirection behavior data, thereby obtaining low-reputation website data;
[0065] Step S344: performing malicious redirection behavior intersection operation according to the high-frequency redirection behavior data and the low-reputation website data, thereby obtaining malicious redirection behavior data;
[0066] Step S345: extracting malicious redirection link features according to the malicious redirection behavior data, thereby obtaining malicious redirection link data;
[0067] Step S346: Perform phishing behavior detection based on the malicious redirection link data to obtain malicious link behavior data.
[0068] The present invention can understand in detail whether the link involves a redirection operation by extracting redirection behavior data from link behavior feature data. This helps to identify potential malicious redirection behaviors. This process can collect comprehensive data on link redirection and provide a detailed information source for subsequent analysis. By counting the frequency of redirection behaviors, links that are frequently redirected can be found. High-frequency redirection is usually one of the characteristics of malicious links, for example, used to bypass detection or deceive users. Frequency statistics help the system identify those abnormally high-frequency redirection behaviors, which hide malicious intentions and improve the sensitivity of detection. By counting the reputation of redirection websites, websites with low reputation can be identified. These low-reputation websites are often the source of malicious activities or the target of jumps. Reputation statistics enable the system to focus on those websites with low reputation, reduce false positives for normal websites, and improve detection efficiency. By performing intersection operations on high-frequency redirection behavior data and low-reputation website data, malicious redirection behaviors can be accurately identified. This comprehensive analysis helps filter out real malicious redirection links. The intersection operation can exclude normal redirection behaviors and focus on redirections with malicious characteristics, thereby improving the accuracy of detection. By extracting link features from malicious redirection behavior data, we can reveal the specific features of these links, such as URL structure, target domain name, etc. This helps to analyze and identify malicious links more deeply. The extracted feature data can be used to create a feature library of malicious links and improve the system's ability to identify similar malicious behaviors. By performing phishing behavior detection based on malicious redirection link data, we can find malicious links that attempt to steal user information through deceptive means. These links are usually disguised as legitimate websites to trick users into entering sensitive information. The detection and identification of phishing behavior can effectively prevent users from being defrauded in the network environment and protect users' personal information and data security.
[0069] Optionally, step S4 is specifically:
[0070] Step S41: performing credential leakage time statistics according to the identity authentication leakage data, thereby obtaining credential leakage time data;
[0071] Step S42: performing identity authentication failure frequency statistics according to the identity authentication risk data, thereby obtaining high-frequency identity authentication failure data;
[0072] Step S43: performing time statistics according to the high-frequency identity authentication failure data, thereby obtaining high-frequency identity authentication failure time data;
[0073] Step S44: Calculate the time distribution overlap according to the credential leakage time data and the high-frequency identity authentication failure time data, so as to obtain the identity authentication leakage time data;
[0074] Step S45: performing risk assessment according to the identity authentication leakage time data, thereby obtaining identity authentication leakage risk assessment data;
[0075] Step S46: Perform automated identity verification protection according to the identity verification leakage risk assessment data, thereby obtaining automated identity verification protection data.
[0076] The present invention can track the specific time point of leakage by counting the time of credential leakage. This helps to determine the window of leakage event, thereby providing information of time dimension for subsequent analysis. Statistical time data of credential leakage can reveal the time pattern of leakage event. By counting the frequency of identity authentication failure, those frequently occurring failure events can be identified, which usually indicate potential security issues, such as brute force attack or account abuse. High-frequency identity authentication failure data can help set security thresholds, such as triggering alarms or locking accounts after a certain number of failures to prevent malicious attacks. By counting the time of high-frequency identity authentication failure events, the specific time period when the attack occurs can be identified, which helps to analyze the attack pattern and evaluate whether there is a specific time point that is more vulnerable to attack. By understanding the time distribution of failure events, the system can optimize security policies, such as increasing monitoring or strengthening identity authentication measures in high-risk time periods. By calculating the time distribution overlap of credential leakage time data and high-frequency identity authentication failure time data, the existing correlation can be identified, which helps to discover the potential relationship between leakage events and identity authentication failures. The overlap calculation can reveal whether there are overlapping time windows, which usually indicates that the system is facing the risk of credential leakage and authentication failure at the same time in a specific time period. Based on the authentication leakage time data, risk assessment can comprehensively consider the time correlation and risk level to assess the specific leakage risk. This assessment helps to understand the severity and scope of the leakage incident. Through the risk assessment results, the system can formulate targeted response strategies, such as strengthening monitoring in specific time periods, enhancing the authentication mechanism, and improving the overall security of the system. Automated authentication protection based on authentication leakage risk assessment data can adjust and optimize authentication strategies in real time, which ensures that when risks are detected, the system can take immediate action to protect user account security. Automated protection measures can reduce reliance on manual intervention, improve response speed, and ensure rapid adaptation and defense in the face of ever-changing security threats.
[0077] Optionally, step S46 is specifically:
[0078] Step S461: setting a risk assessment threshold according to the identity authentication leakage risk assessment data, thereby obtaining risk assessment threshold data;
[0079] Step S462: extracting user login behavior features according to the communication software operation log, thereby obtaining user login behavior data;
[0080] Step S463: constructing an automated login monitoring model according to the risk assessment threshold data and the user login behavior data, thereby obtaining an automated login monitoring model;
[0081] Step S464: Login monitoring is performed on the user login behavior data according to the automated login monitoring model, thereby obtaining automated login monitoring data;
[0082] Step S465: extracting login high risk score features according to the automated login monitoring data, thereby obtaining login high risk score data;
[0083] Step S466: Performing a user alarm protection notification according to the login high risk score data, thereby obtaining user alarm protection notification data;
[0084] Step S467: performing temporary account protection locking according to the login high risk score data, thereby obtaining account temporary protection locking data;
[0085] Step S468: integrating the automatic verification identity protection data according to the user alarm protection notification data and the account temporary protection lock data, thereby obtaining the automatic verification identity protection data.
[0086] The present invention sets a threshold value according to the risk assessment data of identity authentication leakage, and can clarify under which conditions identity authentication is considered to be high risk. This helps to respond quickly when encountering similar situations. Setting a suitable risk threshold can effectively prevent excessive alarms and missed reports, and ensure that the system can detect and handle potential risks in a timely manner when action is really needed. Extracting user login behavior features can help the system understand the login mode and behavior of normal users. These features include login time, frequency, location, etc. By analyzing these features, the system can establish a baseline for normal behavior, thereby effectively identifying abnormal behavior and enhancing the accuracy of risk detection. An automated login monitoring model is constructed based on risk assessment thresholds and user login behavior data, which can monitor user login behavior in real time and automatically identify potential high-risk activities. The model can be dynamically adjusted based on real-time data to improve the system's detection capability and response speed for abnormal login behavior. Using an automated login monitoring model to monitor user login behavior in real time, abnormal login behavior can be discovered immediately and measures can be taken to enhance the security of the system. Real-time monitoring can effectively identify and prevent malicious logins, reduce the risk of account attacks, and protect user account security. By extracting the high-risk login score features, the risk level of each login behavior can be quantified. These scores can help the system assess the risk level of each login attempt. The high-risk score features can help the system prioritize the most dangerous login behaviors and ensure that the most stringent protection measures are taken for high-risk activities. By issuing user alert notifications based on the login high-risk score data, users can be informed of the security risks of their accounts in a timely manner, so that users can take timely measures, such as changing passwords or making other security settings. The notification can enhance users' security awareness and prompt them to take proactive precautions when abnormal situations are found, thereby improving overall account security. Temporary protection and locking of accounts based on login high-risk score data can prevent further malicious attacks or unauthorized access. Temporary locking measures can limit access to accounts before risk assessment is fully confirmed, thereby reducing potential security threats. By integrating user alert protection notification data and account temporary protection and lock data, a comprehensive automated identity verification protection solution can be created. This integration ensures multi-level security protection measures. The integrated data can provide a more comprehensive risk management solution, automatically handle various risks in identity authentication, and improve the system's defense efficiency and responsiveness. BRIEF DESCRIPTION OF THE DRAWINGS
[0087] Other features, objects and advantages of the present invention will become more apparent from the detailed description of non-limiting embodiments thereof made with reference to the following drawings:
[0088] Figure 1 A schematic diagram of the steps of the automated security verification method for communication software of the present invention;
[0089] Figure 2 Detailed step flow diagram of step S1 in the present invention;
[0090] Figure 3 Detailed step flow diagram of step S2 in the present invention.
[0091] The realization of the purpose, functional features and advantages of the present invention will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION
[0092] The following is a clear and complete description of the technical method of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by technicians in this field without creative work are within the scope of protection of the present invention.
[0093] In addition, the accompanying drawings are only schematic illustrations of the present invention and are not necessarily drawn to scale. The same reference numerals in the figures represent the same or similar parts, and their repeated description will be omitted. Some of the block diagrams shown in the accompanying drawings are functional entities and do not necessarily correspond to physically or logically independent entities. The functional entities can be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and / or processor methods and / or microcontroller methods.
[0094] It should be understood that, although the terms "first", "second", etc. may be used herein to describe various units, these units should not be limited by these terms. These terms are used only to distinguish one unit from another unit. For example, without departing from the scope of the exemplary embodiments, the first unit may be referred to as the second unit, and similarly the second unit may be referred to as the first unit. The term "and / or" used herein includes any and all combinations of one or more of the listed associated items.
[0095] To achieve this, please refer to Figures 1 to 3 The present invention provides a method for automatically verifying the security of communication software, the method comprising the following steps:
[0096] Step S1: Acquire communication software device port data, and construct a communication software device topology structure based on the communication software device port data, thereby obtaining a communication software device topology map; acquire communication software security protocol data; divide the communication software device topology map into risk connections based on the communication software security protocol data, thereby obtaining a communication software device risk connection topology map;
[0097] In this embodiment, the communication software device port data is extracted from the network device. This data is usually obtained through a network scanning tool (such as Nmap) or extracted from the network configuration file of the device. The port data includes the port number open on the device and its status (open, closed, filtered, etc.). The topological structure of the communication software device is constructed through these data. The specific operation is to regard each device as a node in the topological map, and draw the connection relationship between the devices according to the device port data. Next, the security protocol data of the communication software is obtained, which can be obtained by analyzing the communication protocol document, configuration file or security policy guide. These protocol data are analyzed to extract digital certificate information and encryption standards. Based on these security protocol data, the constructed device topology map is divided into risk connections, and the risk level of the connection is marked. The risk connection division is determined based on security features such as encryption strength and authentication method in the protocol. For example, connections using outdated encryption standards are marked as high risk. Finally, the communication software device risk connection topology map formed clearly shows the connection risk between each device, which is helpful for subsequent risk management and optimization.
[0098] Step S2: obtaining the communication software operation log, and extracting the identity authentication data according to the communication software operation log data, thereby obtaining the identity authentication data; performing identity authentication risk analysis according to the identity authentication data, thereby obtaining the identity authentication risk data;
[0099] In this embodiment, the communication software operation log data is obtained, which can be obtained from the system log, application log or server log. These logs record the user's login activities, system operations and identity authentication events. By parsing these log data, information related to identity authentication is extracted, such as the time of each user login, the login result (successful or failed), and the authentication method used. Next, an identity authentication risk analysis is performed, and the analysis method includes counting the failure rates of different authentication methods, identifying high-frequency login failure events, and detecting abnormal login patterns. This process involves using statistical tools or writing scripts to calculate the frequency and pattern of identity authentication failures, and determining which authentication methods or user behaviors are at higher risk. Finally, all analysis results are integrated into identity authentication risk data, providing a detailed view of authentication risks for subsequent security decisions and protective measures.
[0100] Step S3: extracting communication link data according to the communication software log data, thereby obtaining communication link data; performing malicious link detection according to the communication link data, thereby obtaining malicious link data; performing identity authentication information leakage analysis on the identity authentication data according to the malicious link data, thereby obtaining identity authentication leakage data;
[0101] In this embodiment, communication link data is extracted from the communication software log data. These data may include information such as source IP address, target IP address, data packet size, communication protocol, etc. The extraction method involves using a log analysis tool (such as ELKStack) to process and parse the log. After extracting the communication link data, malicious link detection is performed. The detection process includes applying a rule engine or algorithm to identify abnormal traffic patterns, such as unauthorized data traffic or abnormal communication behavior. For example, by comparing traffic patterns with known malicious behavior feature libraries, potential malicious links are detected. The detected malicious links are further analyzed to determine whether they involve the leakage of authentication information. For example, check whether there are unauthorized access attempts or abnormal login activities. Finally, authentication leakage data is generated to describe the specific leakage situation and its potential impact on the system, providing a basis for subsequent risk management.
[0102] Step S4: performing correlation analysis based on the identity authentication leakage data and the identity authentication risk data, thereby obtaining the identity authentication leakage risk data; performing automated identity authentication protection based on the identity authentication leakage risk data, thereby obtaining automated identity authentication protection data;
[0103] In this embodiment, correlation analysis is performed based on identity authentication leakage data and identity authentication risk data. The analysis process can use data association technology to identify potential risk points by matching the information in the leakage data with the abnormal patterns in the risk data. Specific operations include applying data analysis tools (such as data mining software or custom scripts) to compare leakage events with risk data to find out the root causes of leakage events and their impacts. For example, identify which leakage events lead to high-risk identity authentication failures. Automated identity verification protection is performed based on the analysis results. Specific measures include setting trigger conditions to automatically enable additional identity authentication steps (such as multi-factor authentication) when a specific type of identity authentication risk is detected. The generated automated identity verification protection data will show the protection measures taken and their effects, providing support for improving the security of the system.
[0104] Step S5: Optimize the identity authentication security risk of the communication software device risk connection topology map based on the automated identity verification protection data, thereby obtaining identity authentication security risk optimization data, and upload it to the communication software management platform to execute the automated identity authentication optimization task.
[0105] In this embodiment, the risk connection topology map of the communication software device is optimized based on the automated verification identity protection data. The specific operation includes adjusting the risk connections in the topology map according to the automated verification protection measures. For example, based on the improvement suggestions in the protection data, the risk level of the connection is re-evaluated and marked, such as increasing the identity authentication level or changing the security policy of the connection. The optimized data will generate new identity authentication security risk optimization data, which reflects the impact of the optimization measures on the risk connection of the device. Finally, the optimized data is uploaded to the communication software management platform, and the platform performs automated identity authentication optimization tasks based on the uploaded data. This includes automatically adjusting security policies, updating access control rules, or strengthening identity authentication mechanisms, thereby improving the overall security of the system.
[0106] Optionally, step S1 specifically includes:
[0107] Step S11: Acquire communication software device port data, and extract device port number data and communication flow direction data according to the communication software device port data, thereby obtaining device port number data and communication flow direction data;
[0108] In this embodiment, communication software device port data is collected from network devices. Use network scanning tools (such as Nmap or Masscan) to scan network devices and record the open ports and their status (open, closed, filtered) on each device. These tools provide detailed port information, including port numbers and protocol types. Then, extract device port number data and communication flow data from the scan results. The port number data represents the open ports on each device, while the communication flow data records the direction and end point device of the data flow. The extraction of communication flow data can be completed by analyzing network traffic monitoring tools (such as Wireshark) or network traffic logs. These data help to understand the interaction mode between devices and determine the flow path of data.
[0109] Step S12: constructing a communication topology node according to the device port number data, thereby obtaining communication topology node data;
[0110] In this embodiment, the communication topology node is constructed based on the extracted device port number data. Each device is regarded as a node in the network topology, and its port number data is used as the attribute of the node. Use a network drawing tool (such as Graphviz or Gephi) to visualize these nodes, and attach the device port number as a label to the node. The communication topology node data constructed in this way shows each device and its port number in the network. Each node represents a device in the topology map, and the attributes of the node include its port number information, which lays the foundation for the subsequent topology structure construction.
[0111] Step S13: performing communication topology connection on the communication topology nodes according to the communication flow direction data, thereby obtaining communication topology connection data;
[0112] In this embodiment, the communication topology nodes are connected in a communication topology according to the communication flow direction data. Each data flow in the communication flow direction data is regarded as an edge in the topology diagram, and the source device and the target device are regarded as the two endpoints of the edge. These connections are created using a network visualization tool (such as Cytoscape) to display the communication relationship between devices. Each edge represents a data flow from a source device to a target device. In the drawn topology diagram, the attributes of the connection line can include information such as traffic volume and protocol type, thereby constructing comprehensive communication topology connection data.
[0113] Step S14: constructing a communication software topology structure according to the communication topology node data and the communication topology connection data, thereby obtaining a communication software device topology diagram;
[0114] In this embodiment, a communication software topology is constructed based on communication topology node data and communication topology connection data. Use a network drawing tool (such as Visio) to integrate node and connection information to form a complete communication software device topology diagram. Each node represents a device, and the connection of the nodes represents the communication path between the devices. The construction of the topology structure requires combining the device port number data and the communication flow data to ensure that the attributes of each connection line accurately reflect the data flow and protocol. Finally, the communication software device topology diagram obtained shows the interconnection and data flow path of the devices in the network, providing a visual basis for subsequent risk analysis and optimization.
[0115] Step S15: Acquire the communication software security protocol data, and extract the digital certificate data according to the communication software security protocol data, thereby obtaining the digital certificate data;
[0116] In this embodiment, the communication software security protocol data is obtained, including protocol specifications, encryption standards, and authentication methods. These data are extracted by analyzing the configuration files, protocol documents, or network security audit reports of the communication software. Special attention is paid to the data extraction of digital certificates. Tools (such as OpenSSL) are used to analyze certificate files to obtain information such as the issuing authority, validity period, and encryption algorithm of the certificate. Digital certificate data provides security information for communication between devices for subsequent risk assessment. All extracted data will be organized into structured information, including detailed attributes of the certificate and the implementation of the security protocol.
[0117] Step S16: dividing the communication software device topology map into risky connections according to the digital certificate data, thereby obtaining a communication software device risky connection topology map.
[0118] In this embodiment, the communication software device topology map is divided into risky connections based on the extracted digital certificate data. The encryption strength, certificate authority and its validity period in the digital certificate data are analyzed to determine the security level of each connection. Use risk assessment tools (such as Qualys or Nessus) to assign a risk level to each device connection based on this security information. Mark the risk level in the topology map, using different colors or labels to represent high-risk and low-risk connections. For example, connections that use outdated encryption algorithms or self-signed certificates are marked as high risk. The resulting communication software device risk connection topology map shows the security risks of each device connection, providing a basis for further risk management and optimization measures.
[0119] Optionally, step S2 specifically includes:
[0120] Step S21: obtaining the communication software operation log, and extracting the identity authentication data according to the communication software operation log data, thereby obtaining the identity authentication data;
[0121] In this embodiment, data is obtained from the communication software operation log. These log data usually record all users' login attempts, identity authentication events, and related timestamps and operation details. Use log parsing tools (such as Logstash in ELKStack) to extract the identity authentication information in the log. This process includes screening log entries related to identity authentication, such as user ID, login time, identity authentication method (such as password, two-factor authentication), and verification result (success or failure). The parsed data will be organized into structured identity authentication data, recording the details of each identity authentication, and providing the original data basis for subsequent analysis.
[0122] Step S22: classifying the verification type according to the identity verification data, thereby obtaining knowledge feature verification data and biometric feature verification data;
[0123] In this embodiment, the identity authentication data extracted from the communication software operation log is classified by verification type. Verification types include knowledge feature type (such as user name and password) and biometric type (such as fingerprint recognition, iris scanning). The identity authentication data is processed using a data classification algorithm (such as a decision tree or a rule engine) to classify the data according to the verification type. Each record is marked as knowledge feature type or biometric verification data according to its verification method. The classification results will be integrated into two types of data sets, which will be used for subsequent anomaly detection steps.
[0124] Step S23: performing identity authentication anomaly detection on the knowledge feature type verification data, thereby obtaining knowledge feature type anomaly verification data;
[0125] In this embodiment, authentication anomaly detection is performed on knowledge feature-based verification data. Common abnormal patterns are monitored, such as an abnormal increase in the number of incorrect password inputs or login attempts from abnormal IP addresses. Knowledge feature-based verification data is analyzed using anomaly detection tools (such as Splunk or a custom anomaly detection script). By setting a threshold (such as multiple incorrect login attempts), the detected abnormal data will be marked as knowledge feature-based abnormal verification data. Abnormal user behavior and its frequency of occurrence are recorded to provide detailed information for subsequent integration and risk assessment.
[0126] Step S24: performing identity authentication anomaly detection on the biometric verification data, thereby obtaining biometric abnormality verification data;
[0127] In this embodiment, identity authentication anomaly detection is performed on biometric verification data. Biometric verification data includes biometric information such as fingerprints and irises. Biometric data analysis tools (such as the built-in analysis function of the biometric system) are used to detect abnormal behavior, such as abnormal fingerprint recognition failure rate or iris scanning recognition errors. Abnormal biometric data will be recorded during the detection process to determine whether there are signs of forgery or illegal access. Abnormal data will be marked and recorded as biometric abnormal verification data, providing a basis for integration and further analysis.
[0128] Step S25: integrating identity authentication exception data according to the knowledge feature type exception verification data and the biometric feature type exception verification data, thereby obtaining identity authentication exception data;
[0129] In this embodiment, the knowledge feature type abnormal verification data and the biometric feature type abnormal verification data are integrated. This process involves merging the two types of abnormal data sets to fully understand the identity authentication anomalies. Use data integration tools (such as ETL tools) to integrate the two types of data into a unified data set. During the integration process, information such as the timestamp of the abnormal behavior, user ID, and abnormal type is integrated into a data table. The final identity authentication anomaly data set shows all detected anomalies, including all abnormal situations in the two types of verification methods, providing comprehensive data for subsequent risk assessment.
[0130] Step S26: Perform identity authentication risk assessment based on the identity authentication abnormality data to obtain identity authentication risk data.
[0131] In this embodiment, risk assessment is performed based on the integrated identity authentication anomaly data. A risk assessment tool (such as RiskLens or a custom assessment algorithm) is used to analyze the impact of the anomaly data. The assessment process includes calculating the frequency, impact range, and potential risk level of abnormal events. The analysis results will generate identity authentication risk data, identifying high-risk users and high-risk behavior patterns. The risk assessment results are used to formulate corresponding security policies to reduce risks and potential security threats in the identity authentication process. The final identity authentication risk data will help identify and respond to potential security issues and improve the overall security of the system.
[0132] Optionally, step S23 is specifically:
[0133] Step S231: extracting verification position features and verification time series features from the knowledge feature type verification data, thereby obtaining knowledge feature type verification position data and knowledge feature type verification time series data;
[0134] In this embodiment, verification location feature extraction and verification time series feature extraction are performed on the knowledge feature-based verification data. Verification location feature extraction involves identifying and recording the specific location where the user authenticates their identity from the verification data, such as the IP address or device identification of the login location. Use log analysis tools (such as Logstash in the ELK Stack) to extract and classify these location data. Verification time series feature extraction includes extracting timestamp information from each identity authentication and recording the time series of user logins. Use time series analysis tools (such as Prometheus) to process these timestamp data and generate time series feature data. Ultimately, the extracted knowledge feature-based verification location data and knowledge feature-based verification time series data will be organized into two data sets to provide detailed location information and time series information for subsequent analysis.
[0135] Step S232: performing verification position statistics on the knowledge feature type verification position data, thereby obtaining low-frequency verification position data;
[0136] In this embodiment, verification position statistics are performed on the knowledge feature type verification position data. This process includes counting the frequency of occurrence of each verification position and determining the number of verifications for each position. Use data analysis tools (such as Pandas or SQL database aggregation queries) to calculate the frequency of occurrence of each verification position. The statistical results will show which verification positions have a low frequency of occurrence. Low-frequency verification position data refers to those verification positions whose frequency of occurrence is lower than the set threshold. These low-frequency verification position data will be extracted and stored as the basis for identifying potential abnormal behavior.
[0137] Step S233: performing verification time interval statistics on the knowledge feature type verification time series data, thereby obtaining short-interval verification data;
[0138] In this embodiment, verification time interval statistics are performed on the knowledge feature-based verification time series data. During the statistical process, the time interval between each identity authentication is first calculated, that is, the time difference between consecutive user login attempts. Use a time interval calculation tool (such as a custom script or statistical analysis software) to process the time series data and divide the time interval into different intervals. Short interval verification data refers to verification events with a time interval less than a set threshold. For example, if a user attempts to log in multiple times within a few seconds, these events will be marked as short interval verification data. The statistical results will show repeated verification attempts in a short period of time, providing clues for subsequent anomaly detection.
[0139] Step S234: performing a verification anomaly intersection operation according to the short-interval verification data and the low-frequency verification position data, thereby obtaining verification anomaly data;
[0140] In this embodiment, a verification anomaly intersection operation is performed based on the short-interval verification data and the low-frequency verification position data. The short-interval verification data and the low-frequency verification position data are intersected to identify verification events that have both abnormal characteristics. Use data processing tools (such as the Pandas library in Python) to implement the intersection operation. Match the short-interval verification data with the low-frequency verification position data to find those multiple verification attempts in a short period of time at low-frequency locations. The verification anomaly data obtained in this way will show potential abnormal behavior patterns, such as frequent attempts at specific locations.
[0141] Step S235: Acquire knowledge feature type historical verification data;
[0142] In this embodiment, knowledge feature type historical verification data is obtained. Data related to knowledge feature type verification is extracted from historical records, such as past login records and identity authentication attempts. These historical data can be obtained from a long-term storage log system (such as a historical database or data warehouse). Ensure that the extracted data covers a wide range of time ranges and user groups to provide sufficient samples for subsequent anomaly detection and cluster analysis. Data extraction tools (such as ETL tools) will be used to process and organize these historical verification data.
[0143] Step S236: clustering the knowledge feature type historical verification data according to the verification abnormality data, thereby obtaining knowledge feature type abnormal verification data.
[0144] In this embodiment, the knowledge feature type historical verification data is clustered according to the verification abnormal data. The abnormal verification data is grouped using a clustering algorithm (such as K-means or DBSCAN). First, the abnormal verification data is used as a sample to perform cluster analysis on the historical verification data to identify abnormal patterns and behaviors. By analyzing these clustering results, the common features of the abnormal verification data are identified, and knowledge feature type abnormal verification data is generated. The clustering results will show which types of abnormal behaviors are most common and help identify potential security threats.
[0145] Optionally, step S24 is specifically:
[0146] Step S241: extracting iris verification features from the biometric verification data to obtain iris verification data;
[0147] In this embodiment, iris verification feature extraction is performed on the biometric verification data. The user iris image is extracted from the biometric verification data. An image processing tool (such as OpenCV) is used to segment the iris area so as to accurately obtain the characteristic area of the iris. Then a specific iris feature extraction algorithm (such as Daugman's 2D Gabor filter) is applied to extract unique texture features from the iris area. These features include the texture pattern, shape, and other identification features of the iris. The extracted iris verification data includes the encoding of these texture features for subsequent verification and matching steps.
[0148] Step S242: Obtaining iris historical verification data;
[0149] In this embodiment, historical iris verification data is obtained. Data records related to iris verification are extracted from the historical database. These data usually include the user's past iris images, iris feature codes, and related verification timestamps. These historical records are retrieved from the data warehouse using a database query language (such as SQL). Ensure that the acquired data covers all users' past verification records, and export these records into a processable format (such as a CSV or JSON file) to provide basic data for subsequent matching and analysis.
[0150] Step S243: performing iris texture verification matching on the iris verification data according to the iris historical verification data, thereby obtaining iris texture verification data;
[0151] In this embodiment, iris texture verification matching is performed on iris verification data according to iris historical verification data. First, the iris texture features extracted previously are used for matching operation. An iris recognition algorithm (such as Hamming distance or Euclidean distance) is used to calculate the matching degree between the current iris verification data and the historical iris data. The iris texture verification data is a representation of these matching results, including matching scores and recognition results. The matching scores are used to evaluate the consistency between the current iris features and the historical data, and to identify whether it is the same user or a potential abnormal situation.
[0152] Step S244: extracting abnormal verification data according to the iris texture verification data, thereby obtaining iris texture abnormal verification data;
[0153] In this embodiment, abnormal verification data extraction is performed based on iris texture verification data. The iris texture verification data is analyzed to identify verification records with a matching degree lower than a set threshold. A data analysis tool (such as NumPy and Pandas in Python) is used to calculate the matching score of each verification record. For those records with a matching score lower than a preset abnormal threshold, they are marked as iris texture abnormal verification data. These abnormal verification data indicate the forgery of iris images, the failure of iris recognition equipment, or other potential security issues.
[0154] Step S245: performing verification time distribution statistics according to the historical iris verification data, thereby obtaining verification time distribution data;
[0155] In this embodiment, verification time distribution statistics are performed based on historical iris verification data. Timestamp data are extracted from historical verification records and statistically analyzed. Time series analysis tools (such as Python's Statsmodels or R's time series package) are used to process the timestamp data to generate distribution statistics of verification time. These statistical results include frequency distribution of verification activities, time period distribution, etc. This data helps to understand the user's verification behavior pattern and provides basic data for subsequent time range comparisons.
[0156] Step S246: performing a time range comparison on the iris texture abnormality verification data according to the verification time distribution data, thereby obtaining the iris texture abnormality verification time data;
[0157] In this embodiment, the time range comparison of the iris texture anomaly verification data is performed based on the verification time distribution data. First, the timestamp of the iris texture anomaly verification data is compared with the verification time distribution data to check whether the abnormal verification records are concentrated in certain specific time periods. A data comparison tool (such as the SciPy library in Python) is used to calculate the degree of overlap of the time range. The obtained iris texture anomaly verification time data shows whether the abnormal behavior occurs in a specific time window, which helps to further analyze the pattern and potential causes of the abnormal behavior.
[0158] Step S247: performing abnormal clustering on the biometric verification data according to the iris texture abnormal verification time data, thereby obtaining biometric abnormal verification data.
[0159] In this embodiment, the biometric verification data is clustered according to the iris texture abnormal verification time data. A clustering algorithm (such as DBSCAN or K-means) is used to perform cluster analysis on the iris texture abnormal verification time data. The time data and texture feature data of the abnormal verification record are used as input for cluster analysis. The clustering algorithm will identify the common features and patterns of the abnormal verification data and generate biometric abnormal verification data. These clustering results help identify potential security threats and group and classify abnormal verification activities.
[0160] Optionally, step S3 specifically includes:
[0161] Step S31: extracting communication link data according to the communication software log data, thereby obtaining communication link data;
[0162] In this embodiment, the communication link data is extracted from the communication software log data. The log files generated by the access communication software are usually detailed records of user communication sessions, port usage, and connection status. These log files are parsed using log analysis tools (such as Splunk or Elasticsearch) to extract the communication link data. The specific operation includes: filtering out events that record communication establishment and disconnection from the log, and extracting relevant fields such as source IP address, target IP address, connection time, and port number through regular expressions. The extraction results will form a structured communication link data set for subsequent analysis.
[0163] Step S32: classifying link characteristics according to the communication link data, thereby obtaining link structure characteristic data and link behavior characteristic data;
[0164] In this embodiment, link feature classification is performed based on the extracted communication link data. The extracted communication link data is input into a feature classification system, and the system analyzes each link data. By analyzing the structure (such as IP address pairs, port numbers, connection frequency) and behavior (such as data transmission volume, session duration) of the link data, the data is divided into link structure feature data and link behavior feature data. The link structure feature data includes the physical characteristics of the connection, such as network nodes and port information; the link behavior feature data includes the mode and behavior characteristics of the communication, such as communication frequency and data flow. The classification results help to identify different types of link features.
[0165] Step S33: performing malicious link structure analysis on the link structure feature data, thereby obtaining malicious link structure data;
[0166] In this embodiment, the link structure feature data is subjected to malicious link structure analysis. The link structure feature data is compared using a predefined malicious link feature library (including known malicious IPs, port numbers and their combinations). By applying static rules and dynamic detection techniques, such as blacklist comparison and anomaly detection algorithms, it is identified whether there are suspicious network structure features. The comparison results will generate malicious link structure data, including IP pairs, port combinations and their communication modes marked as malicious. These data help identify existing network attacks or illegal activities.
[0167] Step S34: performing malicious link behavior analysis on the link behavior feature data, thereby obtaining malicious link behavior data;
[0168] In this embodiment, malicious link behavior analysis is performed on the link behavior feature data. By analyzing the link behavior feature data, it is identified whether there is abnormal behavior in the communication pattern. The specific operation includes: checking whether there are frequent connection attempts, abnormal data transmission volume, or abnormal session duration. Anomaly detection algorithms (such as isolation forest or statistical analysis methods) are applied to analyze the communication behavior to identify abnormal patterns. The malicious link behavior data generated as a result includes identified abnormal connection behaviors, such as high-frequency redirection or abnormal data transmission volume, which indicate potential malicious activities.
[0169] Step S35: integrating malicious link data according to the malicious link structure data and the malicious link behavior data, thereby obtaining malicious link data;
[0170] In this embodiment, the malicious link structure data and malicious link behavior data are integrated. The identified malicious link structure feature data and malicious link behavior feature data are merged to form a comprehensive malicious link data set. This process includes matching and fusing the structure feature data and the behavior feature data to ensure that the joint impact of the two types of features is comprehensively considered. For example, malicious link data is generated by combining malicious IP addresses and port numbers with abnormal communication patterns. The integrated data reveals malicious link activities and provides a more comprehensive security analysis view.
[0171] Step S36: Perform identity authentication information leakage analysis on the identity authentication data according to the malicious link data, thereby obtaining identity authentication leakage data.
[0172] In this embodiment, authentication data is analyzed for authentication information leakage based on the generated malicious link data. The malicious link data is compared with the authentication data to identify whether there is authentication information leaked through the malicious link. This includes checking whether sensitive authentication data (such as usernames and passwords) has been stolen through malicious links. Traffic data is analyzed using data leakage detection tools (such as network intrusion detection systems) to detect signs of leakage. Ultimately, authentication leakage data is generated, containing detailed records of leakage events and affected user information, which helps to take further protection measures.
[0173] Optionally, step S33 is specifically:
[0174] Step S331: extracting link path feature data according to the link structure feature data, thereby obtaining link path feature data;
[0175] In the present embodiment, link path feature data is extracted from link structure feature data. Link structure feature data is read using a data processing tool (such as Python's Pandas library), which includes information such as the source and target IP addresses, port numbers, and connection duration of the communication. A path extraction algorithm (such as the shortest path algorithm in graph theory) is applied to identify the specific path from the source IP to the target IP. For each link path, each node (IP address) and edge (connection) on the path are extracted to form link path feature data. The data contains the structural information of the path, including the specific nodes of the path and the order of the connection, which provides basic data for subsequent abnormal analysis.
[0176] Step S332: extracting malicious link history data according to the communication software operation log, thereby obtaining malicious link history data;
[0177] In this embodiment, malicious link history data is extracted from the communication software operation log. The operation log of the communication software is accessed and parsed, and these logs record past communication events, including successful and failed connection attempts. Use log analysis tools (such as Logstash in ELK Stack) to filter and extract log entries containing malicious activities. According to known malicious link patterns (such as IP blacklists and abnormal port numbers), filter out data in historical records that meet the characteristics of malicious activities. The malicious link history data finally generated includes information about malicious link events that have been identified in the past, which is used for subsequent threshold setting and anomaly detection.
[0178] Step S333: setting a path parameter quantity threshold value and a path length threshold value according to the malicious link history data, thereby obtaining path parameter quantity threshold data and path length threshold data;
[0179] In this embodiment, the path parameter number threshold setting and the path length threshold setting are performed. The distribution of the path parameter number and the path length is analyzed according to the malicious link history data. Use statistical analysis tools (such as the ggplot2 package in the R language) to draw a distribution diagram of the number of parameters and the path length to determine the common threshold range. Set the path parameter number threshold (such as the number of nodes on the path exceeds 10, which is abnormal) and the path length threshold (such as the path length exceeds 20 hops, which is abnormal). These thresholds will be used as standards in subsequent detections to screen and identify abnormal link path features.
[0180] Step S334: screening the link path feature data for special character structures, thereby obtaining character abnormal link structure data;
[0181] In this embodiment, the link path feature data is screened for special character structures. A regular expression tool (such as the re module in Python) is used to check the path parameters in the link path feature data to screen for special characters (such as "%20", "$", etc.). These special characters indicate potential malicious activities in the path. The path parameters are analyzed one by one, and the paths containing special characters are marked as abnormal, generating character abnormal link structure data. These data are helpful in identifying URL injection or other forms of path attacks.
[0182] Step S335: performing parameter structure threshold comparison on the link path feature data according to the path parameter quantity threshold data, thereby obtaining parameter abnormal link structure data;
[0183] In this embodiment, the parameter structure threshold comparison is performed on the link path feature data according to the path parameter quantity threshold data. The link path feature data is compared using the set path parameter quantity threshold (such as the number of nodes on the path exceeding the preset threshold is abnormal). Use data processing tools (such as SQL queries or Python scripts) to filter out link paths whose path parameter quantity exceeds the threshold. Mark these paths as parameter abnormality link structure data. These data can identify abnormal path structures, such as overly long chains or abnormal path complexity, and further assist in security analysis.
[0184] Step S336: performing a length structure threshold comparison on the link path feature data according to the path length threshold data, thereby obtaining length abnormal link structure data;
[0185] In this embodiment, the link path feature data is compared with the length structure threshold according to the path length threshold data. The link path feature data is screened using the set path length threshold (e.g., a path length exceeding 20 hops is abnormal). The path length is measured using a path analysis tool (e.g., Graphviz) and compared with the set threshold. Paths with lengths exceeding the threshold are screened out and marked as length abnormal link structure data. These data help identify overly long path chains, indicating the presence of complex network attacks or abnormal activities.
[0186] Step S337: performing malicious link structure intersection and merging according to the character abnormal link structure data, the parameter abnormal link structure data, and the length abnormal link structure data, thereby obtaining malicious link structure data.
[0187] In this embodiment, malicious link structure intersection and merging are performed based on character abnormal link structure data, parameter abnormal link structure data, and length abnormal link structure data. First, the screened character abnormality, parameter abnormality, and length abnormality link structure data are subjected to intersection operations, and set operation tools (such as set operations in Python or JOIN queries in databases) are used to find the common parts of these abnormal features. These common parts are merged to generate malicious link structure data. These data will reveal link paths with multiple abnormal features, which will help identify more complex malicious link patterns and further enhance the security of communication software.
[0188] Optionally, step S34 is specifically:
[0189] Step S341: extracting redirection behavior data from link behavior feature data, thereby obtaining redirection behavior data;
[0190] In this embodiment, the redirection behavior data is extracted from the link behavior feature data. Log data containing link behaviors is accessed and parsed, and these logs record each link clicked by the user and its target. The redirection behavior of the link is extracted using a data processing tool (such as Python's Pandas library). Links that point to third-party websites or are redirected multiple times are identified through a screening mechanism. The extracted redirection behavior data includes the number of redirections and the target website, which will be used for subsequent frequency statistics and reputation evaluation.
[0191] Step S342: performing redirection frequency statistics according to the redirection behavior data, thereby obtaining high-frequency redirection behavior data;
[0192] In this embodiment, redirection frequency statistics are performed to obtain high-frequency redirection behavior data. The redirection behavior data extracted in step S341 is processed using a statistical analysis tool (such as the NumPy library in Python). The frequency of occurrence of each redirection link is counted, and the number of redirections of each link is calculated. A frequency threshold is set, and links whose redirection times exceed this threshold are filtered out and marked as high-frequency redirection behavior data. By generating a frequency distribution chart, the frequency of redirection behavior is intuitively displayed, which helps identify potential abnormal behavior.
[0193] Step S343: performing redirection website reputation statistics according to the redirection behavior data, thereby obtaining low-reputation website data;
[0194] In this embodiment, the reputation of the redirected website is counted based on the redirection behavior data to obtain low-reputation website data. First, a blacklist or reputation database containing known low-reputation websites is obtained. The database is used to query the redirection target URLs to verify whether these URLs are in the low-reputation list. The number of occurrences of low-reputation URLs is counted, and these data are marked as low-reputation website data. A reputation scoring tool (such as Web of Trust or Google SafeBrowsing API) is used to assist in verifying the reputation of the website to ensure accuracy.
[0195] Step S344: performing malicious redirection behavior intersection operation according to the high-frequency redirection behavior data and the low-reputation website data, thereby obtaining malicious redirection behavior data;
[0196] In this embodiment, an intersection operation of high-frequency redirection behavior data and low-reputation website data is performed to obtain malicious redirection behavior data. First, the high-frequency redirection behavior data and low-reputation website data are imported into a set operation tool (such as a set operation in Python). A set intersection operation is performed to identify links that appear in both the high-frequency redirection data and the low-reputation website data. These links are marked as malicious redirection behavior data. These data represent high-frequency redirection behaviors pointing to low-reputation websites, which are usually associated with malicious activities.
[0197] Step S345: extracting malicious redirection link features according to the malicious redirection behavior data, thereby obtaining malicious redirection link data;
[0198] In this embodiment, malicious redirection link feature extraction is performed based on malicious redirection behavior data. A data extraction tool (such as the BeautifulSoup library in Python) is used to analyze and extract the features of malicious redirection links, including the domain name, path, query parameters, etc. of the target website. These features are summarized as malicious redirection link data. These data include characteristic patterns of malicious links, which help identify common malicious redirection strategies such as phishing or malware distribution.
[0199] Step S346: Perform phishing behavior detection based on the malicious redirection link data to obtain malicious link behavior data.
[0200] In this embodiment, phishing behavior detection is performed on malicious redirection link data to obtain malicious link behavior data. First, phishing detection tools (such as PhishTank API) are applied to detect malicious redirection links. Use these tools to check whether the link meets known phishing attack characteristics, such as fake login pages or pages disguised as legitimate websites. The detection results are marked as phishing behavior, and malicious link behavior data is finally obtained. This data will show which malicious redirection links are used for phishing attacks, further strengthening security protection measures.
[0201] Optionally, step S4 is specifically:
[0202] Step S41: performing credential leakage time statistics according to the identity authentication leakage data, thereby obtaining credential leakage time data;
[0203] In this embodiment, the credential leakage time statistics are performed to obtain the credential leakage time data. The timestamp of the leakage event is extracted from the identity authentication leakage data. These timestamps are sorted and counted using data processing tools (such as Python's Pandas library). By summarizing the timestamps, the frequency of credential leakage events is calculated, and the distribution of leakage events in different time periods is analyzed. Finally, the credential leakage time data is generated, showing the number of credential leakage events that occurred at each time point or time period. These data help to understand the time pattern of leakage events and potential attack peaks.
[0204] Step S42: performing identity authentication failure frequency statistics according to the identity authentication risk data, thereby obtaining high-frequency identity authentication failure data;
[0205] In this embodiment, the frequency of identity authentication failure is counted based on the identity authentication risk data to obtain high-frequency identity authentication failure data. The time and reason for each failed attempt are extracted from the identity authentication risk data. The frequency of occurrence of each identity authentication failure is calculated using statistical tools (such as the NumPy library in Python). A frequency threshold is set to mark frequently occurring identity authentication failure attempts as high-frequency identity authentication failure data. By generating a frequency distribution graph and table to show the frequency of occurrence of each failure mode, it helps to identify abnormally frequent identity authentication failure attempts.
[0206] Step S43: performing time statistics according to the high-frequency identity authentication failure data, thereby obtaining high-frequency identity authentication failure time data;
[0207] In this embodiment, high-frequency identity authentication failure data is subjected to time statistics to obtain high-frequency identity authentication failure time data. The timestamp of each failure event is extracted from the high-frequency identity authentication failure data obtained in step S42. These timestamps are plotted and analyzed using a time series analysis tool (such as the Matplotlib library in Python). The time intervals of high-frequency identity authentication failure events are counted to identify the time period in which these events occur in large numbers. High-frequency identity authentication failure time data is generated to analyze whether these failure events have an obvious clustering trend within a specific time period, thereby identifying potential attack time periods.
[0208] Step S44: Calculate the time distribution overlap according to the credential leakage time data and the high-frequency identity authentication failure time data, so as to obtain the identity authentication leakage time data;
[0209] In this embodiment, the time distribution overlap of the credential leakage time data and the high-frequency identity authentication failure time data is calculated to obtain the identity authentication leakage time data. The credential leakage time data and the high-frequency identity authentication failure time data are imported into a time overlap analysis tool (such as the SciPy library in Python). The time overlap of the two sets of data is calculated to analyze whether there is a high overlap frequency in the same time period. Finally, the identity authentication leakage time data is generated to show the time relationship between the credential leakage event and the high-frequency identity authentication failure event, so as to identify potential security risk patterns.
[0210] Step S45: performing risk assessment according to the identity authentication leakage time data, thereby obtaining identity authentication leakage risk assessment data;
[0211] In this embodiment, risk assessment is performed based on the identity authentication leakage time data to obtain identity authentication leakage risk assessment data. A risk assessment model (such as a rule-based assessment tool) is applied to analyze the identity authentication leakage time data. The assessment model combines the time pattern, frequency and potential impact of the leakage event to calculate the risk level of each time period. By analyzing the risk level, high-risk time periods and event patterns are identified. The identity authentication leakage risk assessment data is generated to evaluate and quantify the security risks of different time periods, thereby providing a basis for formulating corresponding protective measures.
[0212] Step S46: Perform automated identity verification protection according to the identity verification leakage risk assessment data, thereby obtaining automated identity verification protection data.
[0213] In this embodiment, automated verification of identity protection is performed based on the identity authentication leakage risk assessment data, thereby obtaining automated verification of identity protection data. Based on the identity authentication leakage risk assessment data, an automated verification protection system (such as a rule-based automated protection system) is configured. Protection rules are set, such as strengthening identity authentication measures during high-risk time periods, or real-time monitoring of abnormal activities. The system automatically performs identity protection operations based on these rules, such as adding additional verification steps or triggering alarms. Automated verification of identity protection data is generated to record the execution and effectiveness of automated protection measures to ensure the security of the identity authentication process.
[0214] Optionally, step S46 is specifically:
[0215] Step S461: setting a risk assessment threshold according to the identity authentication leakage risk assessment data, thereby obtaining risk assessment threshold data;
[0216] In this embodiment, a risk assessment threshold is set according to the identity authentication leakage risk assessment data to obtain risk assessment threshold data. First, all relevant risk indicators are extracted from the identity authentication leakage risk assessment data, such as the frequency of leakage events, the sensitivity of leakage, and the attack path. Use statistical analysis tools (such as Python's SciPy library) to analyze these data and set the threshold range. The process of setting the risk assessment threshold includes: performing statistical analysis on historical data, determining the distribution of risk levels, and setting thresholds according to predetermined risk levels. Through the set thresholds, the risk assessment data is classified into different levels such as low, medium, and high, and risk assessment threshold data is generated to ensure that potential security risks can be effectively detected.
[0217] Step S462: extracting user login behavior features according to the communication software operation log, thereby obtaining user login behavior data;
[0218] In this embodiment, user login behavior features are extracted based on the communication software operation log to obtain user login behavior data. First, information related to user login is extracted from the communication software operation log, including login time, login IP address, device type, successful and failed login records, etc. Use data processing tools (such as Python's Pandas library) to clean and organize these log data. The extracted features include login time intervals, device change frequency, abnormal login locations, etc. Generate user login behavior data, including user login patterns, abnormal behaviors, and login frequencies. These features will be used for subsequent login monitoring and risk assessment.
[0219] Step S463: constructing an automated login monitoring model according to the risk assessment threshold data and the user login behavior data, thereby obtaining an automated login monitoring model;
[0220] In this embodiment, an automated login monitoring model is constructed based on risk assessment threshold data and user login behavior data to obtain an automated login monitoring model. First, an automated monitoring model is designed in combination with risk assessment threshold data and user login behavior data. Model training is performed using a decision tree algorithm or a rule-based model (such as Python's Scikit-learn library). During model training, the risk threshold is used as a decision rule, and the login behavior features are used as input to establish a judgment model to identify high-risk login behaviors. The constructed automated login monitoring model can monitor the user's login behavior in real time and identify potential abnormal or high-risk login events.
[0221] Step S464: Login monitoring is performed on the user login behavior data according to the automated login monitoring model, thereby obtaining automated login monitoring data;
[0222] In this embodiment, the user login behavior data is logged in and monitored according to the automated login monitoring model, thereby obtaining automated login monitoring data. The automated login monitoring model is deployed in the actual environment to receive real-time user login behavior data. The model is used to analyze the login behavior data in real time, and the risk level of each login is identified and recorded according to the set risk assessment threshold and feature extraction rules. Automated login monitoring data is generated, including the risk score of each login, abnormal behavior records and related alarm information. These data will be used for further risk analysis and implementation of protection measures.
[0223] Step S465: extracting login high risk score features according to the automated login monitoring data, thereby obtaining login high risk score data;
[0224] In this embodiment, the login high risk score feature extraction is performed based on the automated login monitoring data to obtain the login high risk score data. The automated login monitoring data is analyzed to extract features related to high risk, such as the number of failed logins, abnormal IP addresses, frequent login attempts in a short period of time, etc. These features are scored using statistical analysis tools (such as Python's Statsmodels library) to calculate the high risk score for each login event. Login high risk score data is generated to display the risk level of each login event to identify security threats.
[0225] Step S466: Performing a user alarm protection notification according to the login high risk score data, thereby obtaining user alarm protection notification data;
[0226] In this embodiment, user alert protection notification is performed based on the login high risk score data, thereby obtaining user alert protection notification data. Based on the high risk score data, user login events with high risk scores are identified. An alert is sent to the user using a notification system (such as an email or SMS API) to inform him that there is a potential security risk in his account. The notification content should include detailed information about the login event, a description of the potential risk, and recommended security measures. The sending of all alert notifications and the user's response are recorded to generate user alert protection notification data to track and verify the implementation effect of the alert.
[0227] Step S467: performing temporary account protection locking according to the login high risk score data, thereby obtaining account temporary protection locking data;
[0228] In this embodiment, the account is temporarily protected and locked according to the high-risk login score data, thereby obtaining the account temporary protection lock data. The high-risk score data is analyzed to determine whether temporary protection measures need to be implemented on the account of the high-risk user. An account management system (such as a database operation tool) is used to temporarily lock the high-risk account to restrict the account login and access rights. The account temporary protection lock data is generated, including information such as the locked account ID, lock time, and lock reason. By implementing temporary locking measures, potential security threats are reduced and the security of the account is ensured.
[0229] Step S468: integrating the automatic verification identity protection data according to the user alarm protection notification data and the account temporary protection lock data, thereby obtaining the automatic verification identity protection data.
[0230] In this embodiment, the automated identity verification protection data integration is performed based on the user alarm protection notification data and the account temporary protection lock data, thereby obtaining the automated identity verification protection data. The user alarm protection notification data and the account temporary protection lock data are aggregated into the data integration system. The two data sets are merged and analyzed using data processing tools (such as Python's Pandas library). The integrated data includes the sending records of user alarms, the implementation of account locks, and their impact on security. Automated identity verification protection data is generated to evaluate the effectiveness of the entire protection measure and provide data support for further security optimization.
[0231] Therefore, the embodiments should be regarded as illustrative and non-restrictive from all points, and the scope of the present invention is limited by the appended claims rather than the above description, and it is therefore intended that all changes falling within the meaning and range of equivalent elements of the application documents are included in the present invention.
[0232] The above description is only a specific embodiment of the present invention, so that those skilled in the art can understand or implement the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but should conform to the widest scope consistent with the principles and novel features invented herein.
Claims
1. A method for automated security verification of communication software, characterized in that: The following steps are involved: Step S1: Acquire communication software device port data, and construct a communication software device topology structure according to the communication software device port data, thereby obtaining a communication software device topology map; Acquire communication software security protocol data; divide the communication software device topology map into risky connections according to the communication software security protocol data, thereby obtaining a communication software device risky connection topology map; Step S2: obtaining the communication software operation log, and extracting the identity authentication data according to the communication software operation log data, thereby obtaining the identity authentication data; performing identity authentication risk analysis according to the identity authentication data, thereby obtaining the identity authentication risk data; Step S3: extracting communication link data according to the communication software log data, thereby obtaining communication link data; performing malicious link detection according to the communication link data, thereby obtaining malicious link data; performing identity authentication information leakage analysis on the identity authentication data according to the malicious link data, thereby obtaining identity authentication leakage data; Step S4: performing correlation analysis based on the identity authentication leakage data and the identity authentication risk data, thereby obtaining the identity authentication leakage risk data; Performing automated identity verification protection based on identity verification leakage risk data, thereby obtaining automated identity verification protection data; Step S5: Optimize the identity authentication security risk of the communication software device risk connection topology map based on the automated identity verification protection data, thereby obtaining identity authentication security risk optimization data, and upload it to the communication software management platform to execute the automated identity authentication optimization task.
2. The method for automated security verification of communication software according to claim 1, characterized in that: Step S1 is specifically as follows: Step S11: Acquire communication software device port data, and extract device port number data and communication flow direction data according to the communication software device port data, thereby obtaining device port number data and communication flow direction data; Step S12: constructing a communication topology node according to the device port number data, thereby obtaining communication topology node data; Step S13: performing communication topology connection on the communication topology nodes according to the communication flow direction data, thereby obtaining communication topology connection data; Step S14: constructing a communication software topology structure according to the communication topology node data and the communication topology connection data, thereby obtaining a communication software device topology diagram; Step S15: Acquire the communication software security protocol data, and extract the digital certificate data according to the communication software security protocol data, thereby obtaining the digital certificate data; Step S16: dividing the communication software device topology map into risky connections according to the digital certificate data, thereby obtaining a communication software device risky connection topology map.
3. The method for automated security verification of communication software according to claim 1, characterized in that: Step S2 is specifically as follows: Step S21: obtaining the communication software operation log, and extracting the identity authentication data according to the communication software operation log data, thereby obtaining the identity authentication data; Step S22: classifying the verification type according to the identity verification data, thereby obtaining knowledge feature verification data and biometric feature verification data; Step S23: performing identity authentication anomaly detection on the knowledge feature type verification data, thereby obtaining knowledge feature type anomaly verification data; Step S24: performing identity authentication anomaly detection on the biometric verification data, thereby obtaining biometric abnormality verification data; Step S25: integrating identity authentication exception data according to the knowledge feature type exception verification data and the biometric feature type exception verification data, thereby obtaining identity authentication exception data; Step S26: Perform identity authentication risk assessment based on the identity authentication abnormality data to obtain identity authentication risk data.
4. The method for automated security verification of communication software according to claim 3, characterized in that: Step S23 is specifically as follows: Step S231: extracting verification position features and verification time series features from the knowledge feature type verification data, thereby obtaining knowledge feature type verification position data and knowledge feature type verification time series data; Step S232: performing verification position statistics on the knowledge feature type verification position data, thereby obtaining low-frequency verification position data; Step S233: performing verification time interval statistics on the knowledge feature type verification time series data, thereby obtaining short-interval verification data; Step S234: performing a verification anomaly intersection operation according to the short-interval verification data and the low-frequency verification position data, thereby obtaining verification anomaly data; Step S235: Acquire knowledge feature type historical verification data; Step S236: clustering the knowledge feature type historical verification data according to the verification abnormality data, thereby obtaining knowledge feature type abnormal verification data.
5. The method for automated security verification of communication software according to claim 3, characterized in that: Step S24 is specifically as follows: Step S241: extracting iris verification features from the biometric verification data to obtain iris verification data; Step S242: Obtaining iris historical verification data; Step S243: performing iris texture verification matching on the iris verification data according to the iris historical verification data, thereby obtaining iris texture verification data; Step S244: extracting abnormal verification data according to the iris texture verification data, thereby obtaining iris texture abnormal verification data; Step S245: performing verification time distribution statistics according to the historical iris verification data, thereby obtaining verification time distribution data; Step S246: performing a time range comparison on the iris texture abnormality verification data according to the verification time distribution data, thereby obtaining the iris texture abnormality verification time data; Step S247: performing abnormal clustering on the biometric verification data according to the iris texture abnormal verification time data, thereby obtaining biometric abnormal verification data.
6. The method for automated security verification of communication software according to claim 1, characterized in that: Step S3 is specifically as follows: Step S31: extracting communication link data according to the communication software log data, thereby obtaining communication link data; Step S32: classifying link characteristics according to the communication link data, thereby obtaining link structure characteristic data and link behavior characteristic data; Step S33: performing malicious link structure analysis on the link structure feature data, thereby obtaining malicious link structure data; Step S34: performing malicious link behavior analysis on the link behavior feature data, thereby obtaining malicious link behavior data; Step S35: integrating malicious link data according to the malicious link structure data and the malicious link behavior data, thereby obtaining malicious link data; Step S36: Perform identity authentication information leakage analysis on the identity authentication data according to the malicious link data, thereby obtaining identity authentication leakage data.
7. The method for automated security verification of communication software according to claim 6, characterized in that: Step S33 is specifically as follows: Step S331: extracting link path feature data according to the link structure feature data, thereby obtaining link path feature data; Step S332: extracting malicious link history data according to the communication software operation log, thereby obtaining malicious link history data; Step S333: setting a path parameter quantity threshold value and a path length threshold value according to the malicious link history data, thereby obtaining path parameter quantity threshold data and path length threshold data; Step S334: screening the link path feature data for special character structures, thereby obtaining character abnormal link structure data; Step S335: performing parameter structure threshold comparison on the link path feature data according to the path parameter quantity threshold data, thereby obtaining parameter abnormal link structure data; Step S336: performing a length structure threshold comparison on the link path feature data according to the path length threshold data, thereby obtaining length abnormal link structure data; Step S337: performing malicious link structure intersection and merging according to the character abnormal link structure data, the parameter abnormal link structure data, and the length abnormal link structure data, thereby obtaining malicious link structure data.
8. The method for automated security verification of communication software according to claim 6, characterized in that: Step S34 is specifically as follows: Step S341: extracting redirection behavior data from link behavior feature data, thereby obtaining redirection behavior data; Step S342: performing redirection frequency statistics according to the redirection behavior data, thereby obtaining high-frequency redirection behavior data; Step S343: performing redirection website reputation statistics according to the redirection behavior data, thereby obtaining low-reputation website data; Step S344: performing malicious redirection behavior intersection operation according to the high-frequency redirection behavior data and the low-reputation website data, thereby obtaining malicious redirection behavior data; Step S345: extracting malicious redirection link features according to the malicious redirection behavior data, thereby obtaining malicious redirection link data; Step S346: Perform phishing behavior detection based on the malicious redirection link data to obtain malicious link behavior data.
9. The method for automated security verification of communication software according to claim 1, characterized in that: Step S4 is specifically as follows: Step S41: performing credential leakage time statistics according to the identity authentication leakage data, thereby obtaining credential leakage time data; Step S42: performing identity authentication failure frequency statistics according to the identity authentication risk data, thereby obtaining high-frequency identity authentication failure data; Step S43: performing time statistics according to the high-frequency identity authentication failure data, thereby obtaining high-frequency identity authentication failure time data; Step S44: Calculate the time distribution overlap according to the credential leakage time data and the high-frequency identity authentication failure time data, so as to obtain the identity authentication leakage time data; Step S45: performing risk assessment according to the identity authentication leakage time data, thereby obtaining identity authentication leakage risk assessment data; Step S46: Perform automated identity verification protection according to the identity verification leakage risk assessment data, thereby obtaining automated identity verification protection data.
10. The method for automated security verification of communication software according to claim 9, characterized in that: Step S46 is specifically as follows: Step S461: setting a risk assessment threshold according to the identity authentication leakage risk assessment data, thereby obtaining risk assessment threshold data; Step S462: extracting user login behavior features according to the communication software operation log, thereby obtaining user login behavior data; Step S463: constructing an automated login monitoring model according to the risk assessment threshold data and the user login behavior data, thereby obtaining an automated login monitoring model; Step S464: Login monitoring is performed on the user login behavior data according to the automated login monitoring model, thereby obtaining automated login monitoring data; Step S4 65: Extract login high risk score features according to the automated login monitoring data, thereby obtaining login high risk score data; Step S466: Performing a user alarm protection notification according to the login high risk score data, thereby obtaining user alarm protection notification data; Step S467: performing temporary account protection locking according to the login high risk score data, thereby obtaining account temporary protection locking data; Step S468: integrating the automatic verification identity protection data according to the user alarm protection notification data and the account temporary protection lock data, thereby obtaining the automatic verification identity protection data.
Citation Information
Patent Citations
Risk control method, device and equipment based on identity verification
CN110276178A
Terminal open source software security detection and early warning method, system and device and terminal
CN116186712A
Management software security maintenance method and system based on Internet information technology
CN117349843A
Safety management method and system for encryption equipment
CN117390656A
Zero-trust network security dynamic evaluation system and method
CN117527430A
Cited By
User identity verification method and system for communication software
CN119903501A
User authentication method and system for a communication software
CN119903501B
Information data secure transmission method and system
CN120017388A
Method and system for secure transmission of information data
CN120017388B
