A user account information security processing method of a power grid system software

Abstract

The application relates to a user account information processing method of a power grid system software. The method comprises the following steps: acquiring user account basic information, user account characteristic information and a false software record list; generating a user account identifier and user account portrait information; in the case of logging in the power grid system software through the user account identifier, sending the user account identifier and the user account portrait information to a running database to obtain a registered user account; comparing software attribute information in each false software list with software attribute information in the power grid system software to be detected; in the case of a first comparison result meeting a preset condition, taking the power grid system software to be detected as target power grid system software; encrypting user account information based on the user account identifier and the user account portrait information, and logging in through the target power grid system software to access target secure user account information. The method can improve the security of user account information of the software.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method for securely processing user account information in power grid system software. Background Technology

[0002] With the development of computer technology, information security technology has emerged. With the advancement of smartphone technology, more and more software has become almost an essential part of end-users' lives. It can be said that the security and convenience of software use directly affect users' daily lives. On the one hand, a wide variety of software has improved people's convenience, but on the other hand, software also affects people's lives due to various problems. 1. The need for real-name registration when using software can lead to the leakage of user information. 2. Users often encounter pop-up prompts that require permissions from some applications during the use of software.

[0003] Generally, users grant software all permissions directly. However, indiscriminate granting can lead to unnecessary privacy leaks. For example, the "app spying incident" occurred because a user granted camera permissions to an app. Furthermore, granting malicious software access to one's contacts poses a risk of privacy breaches. Location permissions, for instance, allow malicious software to easily deduce a user's company, school, home address, and frequented locations, and then analyze their occupation, income, lifestyle habits, and other personal information. On the one hand, users are increasingly reliant on the convenience and speed offered by software; on the other hand, they must also bear the various inconveniences associated with using software and independently discern whether the tasks performed while using it are necessary and whether they pose information security risks, resulting in low information security when using software. Summary of the Invention

[0004] Therefore, it is necessary to provide a method, apparatus, computer equipment, computer-readable storage medium, and computer program product for processing user account information in power grid system software that can improve the security of user account information, in response to the above-mentioned technical problems.

[0005] Firstly, this application provides a method for securely processing user account information in power grid system software. The method includes: acquiring basic user account information and user account feature information corresponding to the basic user account information; acquiring a list of fake software records corresponding to at least one power grid system software; generating a corresponding user account identifier based on the basic user account information, and generating user account profile information corresponding to each user account basic information based on each user account feature information and the corresponding user account identifier; when logging into the power grid system software through the user account identifier, sending the user account identifier and the user account profile information to the operating database corresponding to the power grid system software to obtain the registered user account corresponding to the user account, wherein the registered user account has recorded the user account identifier and the user account profile information in the operating database; comparing the software attribute information in each of the fake software lists with the software attribute information in the power grid system software to be detected, and determining a first comparison result; if the first comparison result meets the preset conditions, using the power grid system software to be detected as the target power grid system software; encrypting the user account information based on the user account identifier and user account profile information in the registered user account, and logging in through the target power grid system software to access the target secure user account information.

[0006] Secondly, this application also provides a user account information security processing device for power grid system software. The device includes: an account data acquisition module, used to acquire basic user account information and user account feature information corresponding to the basic user account information; and to acquire at least one list of fake software records corresponding to the power grid system software; an account information generation module, used to generate a corresponding user account identifier based on the basic user account information, and to generate user account profile information corresponding to each of the basic user account information according to each of the user account feature information and the corresponding user account identifier; and a registered account obtaining module, used to send the user account identifier and the user account profile information to the operating database corresponding to the power grid system software when logging into the power grid system software through the user account identifier, thereby obtaining the user account pair. The system includes: a registered user account, wherein the registered user account records the user account identifier and user account profile information in the running database; a comparison result determination module, used to compare the software attribute information in each of the fake software lists with the software attribute information in the power grid system software to be detected, and determine a first comparison result; a comparison result judgment module, used to select the power grid system software to be detected as the target power grid system software if the first comparison result meets preset conditions; and an account information access module, used to encrypt the user account information based on the user account identifier and user account profile information in the registered user account, and log in through the target power grid system software to access the target secure user account information.

[0007] Thirdly, this application also provides a computer device. The computer device includes a memory and a processor. The memory stores a computer program, and the processor, when executing the computer program, performs the following steps: obtaining basic user account information and user account feature information corresponding to the basic user account information; obtaining a list of fake software records corresponding to at least one power grid system software; generating a corresponding user account identifier based on the basic user account information, and generating user account profile information corresponding to each user account basic information based on each user account feature information and the corresponding user account identifier; and, when logging into the power grid system software through the user account identifier, sending the user account identifier and the user account profile information to the power grid system software. The system software's corresponding operating database is used to obtain the registered user accounts corresponding to the user accounts. The registered user accounts are those for which the operating database records the user account identifier and the user account profile information. The software attribute information in each of the fake software lists is compared with the software attribute information in the power grid system software to be detected to determine a first comparison result. If the first comparison result meets the preset conditions, the power grid system software to be detected is selected as the target power grid system software. The user account information is encrypted based on the user account identifier and user account profile information in the registered user accounts, and login is performed through the target power grid system software to access the target secure user account information.

[0008] Fourthly, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, performs the following steps: obtaining basic user account information and user account feature information corresponding to the basic user account information; obtaining at least one list of fake software records corresponding to power grid system software; generating a corresponding user account identifier based on the basic user account information, and generating user account profile information corresponding to each user account basic information based on each user account feature information and the corresponding user account identifier; and, when logging into the power grid system software through the user account identifier, sending the user account identifier and the user account profile information to the power grid system software. The system obtains the registered user account corresponding to the user account from the corresponding running database. The registered user account records the user account identifier and user account profile information in the running database. The system compares the software attribute information in each of the fake software lists with the software attribute information in the power grid system software to be detected to determine the first comparison result. If the first comparison result meets the preset conditions, the power grid system software to be detected is selected as the target power grid system software. The user account information is encrypted based on the user account identifier and user account profile information in the registered user account, and the system logs in through the target power grid system software to access the target secure user account information.

[0009] Fifthly, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, performs the following steps: obtaining basic user account information and user account feature information corresponding to the basic user account information; obtaining a list of fake software records corresponding to at least one power grid system software; generating a corresponding user account identifier based on the basic user account information, and generating user account profile information corresponding to each user account basic information based on each user account feature information and the corresponding user account identifier; and, when logging into the power grid system software using the user account identifier, sending the user account identifier and the user account profile information to the corresponding power grid system software. The system operates a database to obtain the registered user accounts corresponding to the user accounts. The registered user accounts are those for which the database records the user account identifier and the user account profile information. The system compares the software attribute information in each of the fake software lists with the software attribute information in the power grid system software to be detected to determine a first comparison result. If the first comparison result meets the preset conditions, the power grid system software to be detected is selected as the target power grid system software. The system encrypts the user account information based on the user account identifier and user account profile information in the registered user accounts and logs in through the target power grid system software to access the target secure user account information.

[0010] The aforementioned method, apparatus, computer equipment, storage medium, and computer program product for processing user account information of power grid system software involves: acquiring basic user account information and corresponding user account feature information; acquiring at least one list of fake software records corresponding to the power grid system software; generating a corresponding user account identifier based on the basic user account information; generating user account profile information corresponding to each user account's basic information based on each user account feature information and the corresponding user account identifier; when logging into the power grid system software using the user account identifier, sending the user account identifier and user account profile information to the operating database corresponding to the power grid system software to obtain the registered user account corresponding to the user account, where the registered user account has recorded the user account identifier and user account profile information in the operating database; comparing the software attribute information in each fake software list with the software attribute information in the power grid system software to be tested to determine a first comparison result; if the first comparison result meets preset conditions, using the power grid system software to be tested as the target power grid system software; encrypting the user account information based on the user account identifier and user account profile information in the registered user account, and logging in through the target power grid system software to access the target secure user account information.

[0011] By leveraging the real-name authentication of account holders within the power grid system, user information is inevitably acquired and stored. This allows for the provision of user account identifiers, one-to-one with account holders, to software operators within the power grid system to protect the information of authenticated users from leakage. Furthermore, user profiles, each corresponding to a user account identifier, are provided to software operators to ensure their security. When a user downloads software, the attributes of the downloading software are matched against those in the list of fraudulent software. If the similarity exceeds a certain threshold, the user is alerted to a potential risk. This approach provides users with more accurate and convenient services while ensuring that software operators do not suffer data loss. It eliminates the need for software operators to process data and generate user profiles. Moreover, the identification of fraudulent software effectively reduces the technical impact of illegal software use, improving the security of user account information during software usage. Attached Figure Description

[0012] Figure 1 This is an application environment diagram of a user account information processing method for power grid system software in one embodiment.

[0013] Figure 2 This is a flowchart illustrating a user account information processing method for power grid system software in one embodiment;

[0014] Figure 3 This is a flowchart illustrating the method for obtaining the size range of fake software data packets and the set of requested permissions in one embodiment;

[0015] Figure 4 This is a flowchart illustrating a method for adding candidate power grid system software to a normal software database in one embodiment.

[0016] Figure 5 This is a flowchart illustrating a method for selecting target power grid system software in one embodiment;

[0017] Figure 6 This is a flowchart illustrating a software dimension scoring method for a power grid system in one embodiment;

[0018] Figure 7 This is a flowchart illustrating a method for obtaining software permissions in a candidate power grid system in one embodiment;

[0019] Figure 8 This is a schematic diagram of user account profile information in one embodiment;

[0020] Figure 9 This is a structural block diagram of a user account information processing device for power grid system software in one embodiment;

[0021] Figure 10 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0022] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0023] The user account information processing method for power grid system software provided in this application embodiment can be applied to, for example... Figure 1 In the application environment shown, terminal 102 acquires data, server 104 receives the data from terminal 102 in response to the terminal 102's instructions, performs calculations on the acquired data, and transmits the calculation results back to terminal 102 for display. Terminal 102 communicates with server 104 via a network. A data storage system can store the data that server 104 needs to process. The data storage system can be integrated onto server 104 or placed in the cloud or on other network servers. Server 104 obtains basic user account information and corresponding user account feature information from terminal 102; and obtains a list of fake software records corresponding to at least one power grid system software; generates a corresponding user account identifier based on the basic user account information, and generates user account profile information corresponding to each user account's basic information based on each user account feature information and the corresponding user account identifier; when logging into the power grid system software through the user account identifier, the user account identifier and user account profile information are sent to the operating database corresponding to the power grid system software to obtain the registered user account corresponding to the user account, and the registered user account records the user account identifier and user account profile information in the operating database; the software attribute information in each fake software list is compared with the software attribute information in the power grid system software to be detected to determine the first comparison result; if the first comparison result meets the preset conditions, the power grid system software to be detected is used as the target power grid system software; the user account information is encrypted based on the user account identifier and user account profile information in the registered user account, and the user account information is accessed by logging into the target power grid system software. The terminal 102 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, and smart in-vehicle systems. Portable wearable devices can include smartwatches, smart bracelets, and head-mounted devices. The server 104 can be implemented using a standalone server or a server cluster consisting of multiple servers.

[0024] In one embodiment, such as Figure 2 As shown, a method for processing user account information in power grid system software is provided, which is applied to... Figure 1 Taking the server in the example, the following steps are included:

[0025] Step 202: Obtain basic user account information and user account feature information corresponding to the basic user account information; and obtain a list of fake software records corresponding to at least one power grid system software.

[0026] Among them, the basic information of a user account can be the inherent information that represents the user account, such as: name, mobile phone number and ID card number.

[0027] Among them, user account feature information can be all information authorized by the user, which may include basic user feature information and extended user feature information, or it may only include basic user feature information.

[0028] In this context, power grid system software can refer to various programming languages ​​used by users within the power grid system, as well as a collection of applications written in those languages. It is divided into application software packages and user programs. Application software packages are collections of programs designed to solve specific types of problems using computers, and are provided to users.

[0029] The fake software record list can be a list of confirmed fake software information provided by illegal intelligence service providers or recorded by relevant departments' anti-illegal systems.

[0030] Specifically, when a user completes real-name authentication as the account holder, the system requests authorization from the user to generate a user profile based on their information. Upon obtaining authorization, it collects basic and extended user account characteristics. Basic characteristics include gender, email address, age, address, workplace, and job title. Extended characteristics include hobbies, brand preferences, attribute preferences, and monthly spending levels. Simultaneously, it records the user's pre-set universal password for logging into the software. Furthermore, it obtains a list of confirmed (or recorded in relevant departments' anti-illegal systems) fake software information provided by illegal intelligence service providers (such as Security Company A or Security Company B), including information such as software name, description, reviews, illegal type, all download links, data package size, requested permissions, and illegal records.

[0031] Step 204: Generate corresponding user account identifiers based on user account basic information, and generate user account profile information corresponding to the basic information of each user account based on the feature information of each user account and the corresponding user account identifiers.

[0032] Among them, the user account identifier can be a unique identity identifier for each user, also known as the user account identifier, which is used to identify the correspondence between the account and the user.

[0033] User account profiling can involve categorizing and tagging users, such as... Figure 8 As shown, for example: gender, place of residence, work and rest schedule, etc.

[0034] Specifically, a user account identifier is generated one-to-one with each user based on their basic account information (name, mobile phone number, and ID card number). Then, user account profile information corresponding to the user account identifier is generated based on the collected user account feature information. Finally, the generated user account identifier and the corresponding user account profile information are stored in the user's power SIM card. The user profile is not a true profile; it's a categorization and tagging of users based on needs. These tags help operators understand users and provide targeted services. The power SIM card is a SIM card generated using power-related software, and its functions are similar to those of a regular SIM card.

[0035] Step 206: When logging into the power grid system software using a user account identifier, send the user account identifier and user account profile information to the corresponding operating database of the power grid system software to obtain the registered user account corresponding to the user account.

[0036] The operating database can be a server used to operate the power grid system software and record the corresponding data of the power grid system software.

[0037] Among them, the registered user account can be the user account whose user account identifier and user account profile information are recorded in the running database.

[0038] Specifically, firstly, by monitoring the operation of the software through the SDK embedded in the power grid system, when the user logs into the software for the first time, the system detects and determines whether the user's SIM card stores a user account identifier. If so, a pop-up window prompts the user to log in to the software through the user account identifier, and also prompts the user that "logging into the software through the user account identifier is considered as agreeing to the software obtaining the user account profile information corresponding to the user account identifier."

[0039] Secondly, after detecting the user's selection instruction to log in to the software through the user account identifier, the generated user account identifier and user account profile information are sent to the software operator's database so that the software operator can record the corresponding user as a registered user account.

[0040] Finally, the generated user account identifier is directly written into the login interface, combined with the pre-set software login password and the verification code sent to the pre-set mobile phone number in the user account to verify the user's identity (facial recognition collection may be added according to the software operator's policy to facilitate subsequent login and enable the software operator to execute the pre-defined security verification policy); the software operator may ask or require the user to change the software login password according to the predetermined policy, but since this does not affect the user's information security, it will not make any requests or interfere.

[0041] Step 208: Compare the software attribute information in each fake software list with the software attribute information in the power grid system software to be tested, and determine the first comparison result.

[0042] Among them, software attribute information can be information describing the writing or usage of the software, such as download links, names, and promotion channels in the software's history.

[0043] Among them, the power grid system software to be tested can be a collection of various programming languages ​​provided to users in the power grid system, as well as applications written in various programming languages ​​that are not tested by the system or correspond to user experience, and is divided into application software packages to be tested and user programs to be tested.

[0044] Specifically, firstly, the received software attribute information identified as fraudulent is categorized into multiple illegal databases based on its type of illegality. Each illegal database includes a name database, a description database, a review database, a link database, and a fraud record database. For example, the databases can be divided into five categories: investment inducement database, pornographic enticement database, mobile Trojan horse database, counterfeit brand database, and fraudulent loan database. Each of these five categories then has five sub-databases: a name database, a description database, a review database, a link database, and a fraud record database.

[0045] Second, based on the received attribute information that is determined to be fake software, the illegal type of the fake software is identified, and then the received fake software attribute information is stored in the corresponding category database. For example, the attribute information of fake software imitating "Taobao" will be stored in the fake brand category database, the fake software name in the received information will be stored in the name database, the fake software description will be stored in the description database, user reviews during the existence of the fake software will be stored in the review database, all download links of the fake software will be stored in the link database, and fraud cases of the fake software will be stored in the fraud record database.

[0046] Third, based on the received confirmed fake software attribute information, the capacity range of each type of fake software data packet and the set of requested permissions are statistically analyzed. When the platform determines whether a certain software is fake software, it can compare the software attribute information in each fake software list with the software attribute information in the power grid system software to be detected to determine the first comparison result.

[0047] Step 210: If the first comparison result meets the preset conditions, the power grid system software to be tested is selected as the target power grid system software.

[0048] Among them, the target power grid system software can be a collection of various programming languages ​​provided to users in the power grid system, as well as applications written in various programming languages ​​that have been tested by the detection system or used by the user. It is divided into target detection application software packages and target detection user programs.

[0049] Specifically, if the preset conditions are that the software does not fall within the capacity range of fake software data packets and the request permission set is normal, then if the first comparison result is that the software does not fall within the capacity range of fake software data packets and the request permission set, the software to be detected is taken as the target software. If the preset conditions are that the software does not fall within the capacity range of fake software data packets and the request permission set is abnormal, then if the first comparison result is that the software falls within the capacity range of fake software data packets and the request permission set, the software to be detected is taken as the target software.

[0050] Step 212: Encrypt the user account information based on the user account identifier and user account profile information in the registered user account, and log in through the target power grid system software to access the target secure user account information.

[0051] The target security user account information can be target information accessed through encrypted means and verified power grid system software.

[0052] Specifically, the registered user account, which has been encrypted in steps 204 and 206, and the target power grid system software, which has been detected in steps 208 and 210, are used to log in and access the target secure user account information in the server.

[0053] In the aforementioned method for processing user account information of power grid system software, the following steps are taken: First, basic user account information and corresponding user account feature information are obtained. Second, a list of fake software records corresponding to at least one power grid system software is obtained. Third, a corresponding user account identifier is generated based on the basic user account information, and user account profile information corresponding to each user account's basic information is generated based on each user account feature information and its corresponding user account identifier. Fourth, when logging into the power grid system software using the user account identifier, the user account identifier and user account profile information are sent to the operating database corresponding to the power grid system software to obtain the registered user account corresponding to the user account. The registered user account records the user account identifier and user account profile information in the operating database. Fifth, the software attribute information in each fake software list is compared with the software attribute information in the power grid system software to be detected to determine the first comparison result. Sixth, if the first comparison result meets the preset conditions, the power grid system software to be detected is used as the target power grid system software. Seventh, the user account information is encrypted based on the user account identifier and user account profile information in the registered user account, and the user account information is accessed by logging into the target power grid system software.

[0054] By leveraging the real-name authentication of account holders within the power grid system, user information is inevitably acquired and stored. This allows for the provision of user account identifiers, one-to-one with account holders, to software operators within the power grid system to protect the information of authenticated users from leakage. Furthermore, user profiles, each corresponding to a user account identifier, are provided to software operators to ensure their security. When a user downloads software, the attributes of the downloading software are matched against those in the list of fraudulent software. If the similarity exceeds a certain threshold, the user is alerted to a potential risk. This approach provides users with more accurate and convenient services while ensuring that software operators do not suffer data loss. It eliminates the need for software operators to process data and generate user profiles. Moreover, the identification of fraudulent software effectively reduces the technical impact of illegal software use, improving the security of user account information during software usage.

[0055] In one embodiment, such as Figure 3 As shown, before the step of using the power grid system software to be tested as the target power grid system software, provided that the first comparison result meets the preset conditions, the following steps are also included:

[0056] Step 302: Classify the fake software information corresponding to the power grid system software according to the software anomaly category to obtain the software anomaly database corresponding to the software anomaly category.

[0057] Among them, the software anomaly category can be a software category with common characteristics formed according to a preset rule after classifying the power grid system software for anomalies.

[0058] The software anomaly database can be a server used to record software with anomalies in the power grid system and the data generated by the software with anomalies in the power grid system.

[0059] Specifically, the received software attribute information identified as fraudulent is categorized into multiple illegal databases based on its type of illegality. Each illegal database includes a name database, a description database, a review database, a link database, and a fraud record database. For example, the databases can be divided into five categories: investment inducement database, pornographic enticement database, mobile Trojan horse database, counterfeit brand database, and fraudulent loan database. Each of these five categories then has five sub-databases: name database, description database, review database, link database, and fraud record database.

[0060] Step 304: Based on the fake software information in the abnormal database, determine the size range of the fake software data packets and the set of requested permissions corresponding to the software abnormal database.

[0061] Among them, the fake software data packet capacity range can be used to define whether the power grid system software has an abnormal capacity range. That is, a preset capacity range is set, and it is normal if it falls into the range or not.

[0062] The requested permission set can be a set of permissions that the software requires the terminal to provide in the abnormal database. This set of permissions can be abnormal permissions required by the software or normal permissions required by the software. Different sets are used depending on the determination method.

[0063] Specifically, based on the received attribute information that is determined to be fake software, the illegal type of the fake software is identified, and then the received fake software attribute information is stored in the corresponding class database. For example, the attribute information of fake software imitating "Taobao" will be stored in the fake brand database, the fake software name in the received information will be stored in the name database, the fake software description will be stored in the description database, user reviews during the existence of the fake software will be stored in the review database, all download links of the fake software will be stored in the link database, and fraud cases of fake software will be stored in the fraud record database. Based on the received confirmed fake software attribute information, the data packet size range and the set of requested permissions for each type of fake software are calculated.

[0064] In this embodiment, by establishing a software anomaly database and classifying the types of fake software installations in the database, the corresponding fake software data packet size range and requested permission set are obtained. This can improve the efficiency of judging fake power grid system software by matching the data packet size and requested permissions.

[0065] In one embodiment, such as Figure 4 As shown, after determining the size range of fake software data packets and the set of requested permissions corresponding to the software anomaly database based on the fake software information in the anomaly database, the process also includes:

[0066] Step 402: Construct a list of legal system software corresponding to the candidate power grid system software.

[0067] The list of legitimate system software can be a collection of various programming languages ​​provided to users in the power grid system, as well as applications written in various programming languages ​​that are prepared for testing by the system under test or for user experience, and a corresponding whitelist is established for the collection of these applications.

[0068] Specifically, first, the system receives a list of functions, permissions, and installation packages for candidate power grid system software provided by partner operators. Second, through static code scanning, it obtains the set of static permissions requested and used in the code of the candidate power grid system software. It then runs the installation package of the candidate power grid system software and monitors its dynamic operation through a sandbox, obtaining the set of dynamic permissions requested and used during the software's execution. The static and dynamic permission sets are merged to form the request permission set. The sandbox system can monitor over 100 behaviors of the candidate power grid system software during operation, including reading files, writing files, obtaining application processes, and reading system configurations. The system analyzes the behavior entities through the function call stack, filters the behavior of candidate power grid system software or SDKs, specifically identifies violators, and locates the code that triggers the behavior. Finally, by analyzing the functions mentioned in the privacy policy, it identifies the set of declared permissions contained in the candidate power grid system software. The static, dynamic, and declared permission sets are combined to obtain a list of legitimate system software corresponding to the power grid system software.

[0069] Step 404: Compare the software functions corresponding to the candidate power grid system software with the permission lists in the legitimate system software. If the second comparison result shows that the candidate power grid system software has excessive permission requests, then prompt the user to modify the software functions corresponding to the candidate power grid system software.

[0070] Among them, software functions can be a certain thing that can be completed in the power grid system software after receiving an instruction and going through a series of actions, or they can be a set of permissions required to complete a certain thing.

[0071] The second comparison result can be the result output after comparing the software function corresponding to the candidate power grid system software with the list of permissions in the legal system software. The comparison result can be either excessive permissions or insufficient permissions.

[0072] Specifically, firstly, the software functions corresponding to the candidate power grid system software are compared with the permission lists of legitimate system software to determine whether the candidate power grid system software has any unauthorized permissions (if the candidate power grid system software requests several permissions from the Android platform, but some of these permissions are not explicitly disclosed to the user in the privacy policy, these undisclosed permissions are considered unauthorized permissions). Then, the industry to which the candidate power grid system software belongs is identified, and it is mapped to the minimum permission set for that industry. The declared permission set is compared with the minimum permission set; if the declared permission set is greater than the minimum permission set, the candidate power grid system software has a permission abuse problem. If the candidate power grid system software has excessive permission requests, a prompt is made to modify the corresponding software functions.

[0073] Step 406: Re-execute the modified candidate power grid system software to compare the software functions corresponding to the candidate power grid system software with the permission lists in the legal system software until the second comparison result shows that the functions and permissions match. Then write the candidate power grid system software into the normal software database.

[0074] The normal software database can be obtained by comparing the software functions corresponding to candidate power grid system software with the permission lists of legitimate system software, and the output result is a set of permissions that are not excessive, which is the whitelist of power grid system software.

[0075] Specifically, the modified candidate power grid system software will be re-executed as follows: First, the software functions corresponding to the candidate power grid system software will be compared with the permission lists of legitimate system software to determine whether the candidate power grid system software has any unauthorized permissions (if the candidate power grid system software requests several permissions from the Android platform, but some of these permissions are not explicitly disclosed to the user in the privacy policy, the undisclosed permissions are unauthorized permissions). Then, the industry to which the candidate power grid system software belongs will be identified and matched with the minimum permission set of the industry. The declared permission set will be compared with the minimum permission set. If the declared permission set is greater than the minimum permission set, the candidate power grid system software has a permission abuse problem. If the candidate power grid system software has excessive permission requests, a prompt will be made to modify the corresponding software functions. After confirming that the candidate power grid system software does not have any unauthorized permissions or permission abuse problems, the candidate power grid system software will be defined as a whitelisted power grid system software and added to the whitelist of power grid system software, which is the normal software database. Optionally, if the second comparison result shows that the candidate power grid system software has excessive permission requests, the software can be directly modified by "defining the candidate power grid system software to be selected as whitelisted power grid system software and adding it to the whitelist of power grid system software".

[0076] In this embodiment, by monitoring the permission list of candidate power grid system software, the legality of the permission list of candidate power grid system software is ensured. This achieves the technical effect that users do not need to independently determine whether to allow permission requests from power grid system software when using normal software databases, and reduces fraudulent power grid system software scams.

[0077] In one embodiment, such as Figure 5 As shown, the method also includes:

[0078] Step 502: Determine whether the candidate power grid system software is recorded in the normal software database. If the first determination result is negative, continue to determine whether the data packet capacity and request permissions corresponding to the candidate power grid system software conform to the data packet capacity range and request permission set of the fake software corresponding to each software anomaly database.

[0079] The first judgment result may indicate whether the candidate power grid system software is recorded in the normal software database.

[0080] Specifically, when a candidate power grid system software downloaded by a user is detected, the name, link, and brief description of the downloaded candidate power grid system software are obtained to determine whether it belongs to the normal software database. If the first determination result is negative, the system continues to determine whether it belongs to an abnormal single power grid system software. If so, the user is prompted that the downloaded candidate power grid system software has been identified as illegal power grid system software (or fake power grid system software), and the illegal category of the candidate power grid system software is marked. If it does not belong to the whitelist of power grid system software or the illegal list of power grid system software, it is defined as an unknown candidate power grid system software, and the function of the unknown candidate power grid system software is analyzed based on the brief description information of the downloaded candidate power grid system software.

[0081] Step 504: If the second judgment result is normal, based on the software functions corresponding to the candidate power grid system software, traverse the software functions corresponding to the normal software database, and select the power grid system software with a software function matching degree greater than the preset matching degree from the normal software database as the target power grid system software.

[0082] The second judgment result may be whether the data packet capacity and request permissions corresponding to the candidate power grid system software conform to the data packet capacity range and request permission set of the fake software corresponding to each software anomaly database.

[0083] Specifically, if the second judgment result is normal, the functions of the power grid system software in the normal software database are traversed, and power grid system software from the software database with functions that are the same or partially the same as the candidate power grid system software downloaded by the user is selected (for example, if the candidate power grid system software downloaded by the user has 5 functions, and power grid system software 1 in the normal software database has 2 functions that are the same or similar to it, power grid system software 2 in the normal software database has 2 functions that are the same or similar to it, and power grid system software 3 in the normal software database has 2 functions that are the same or similar to it, then the names of the power grid system software from these 3 normal software databases and the functions that are the same or similar to the downloaded candidate power grid system software are listed and a pop-up window is displayed for the user to select). If the user chooses to download the power grid system software from the normal software database, the user's operation is received and an installation package is provided to the user, and power grid system software with a software function matching degree greater than a preset matching degree is selected from the normal software database as the target power grid system software. (During the installation process, a pop-up window prompts the user that "the functions and permissions requested by the power grid system software in this whitelist have been verified. The specific functions are Function 1 (requires permission 1), Function 2 (requires permission 1), and Function 3 (requires permissions 2 and 3))".

[0084] In this embodiment, by employing a scheme that matches and recommends power grid system software of the same type from the normal software database based on the type of unknown candidate power grid system software downloaded by the user when the user downloads unknown candidate power grid system software that is neither from the software anomaly database nor from the normal software database power grid system software, the technical effect of ensuring user information security can be achieved.

[0085] In one embodiment, such as Figure 6 As shown, the method also includes:

[0086] Step 602: Obtain the power grid software operation data corresponding to each power grid system software.

[0087] Among them, power grid software operation data can be data generated by monitoring the operation of power grid system software.

[0088] Specifically, the SDK periodically collects operational data of the power grid system software, including technical indicators across multiple dimensions: 1. User behavior data: average operation time under view categories, user tolerance time limit, total number of users, number of affected users, and number of users experiencing power grid system software errors, etc.; 2. Operational data data: response time trends for different access methods, request error rate trends, user change trends, etc.; 3. Power grid system software crash data data: crash rate under different application versions, details of crashed users, number of crashes, and regions affected by crashes; 4. Lag data data: lag rate under different application versions, details of lagging users, number of lags, and regions affected by lags; 5. Network hijacking data data: access volume of hijacked network domains, number of hijacks, and percentage of hijacked domains.

[0089] Step 604: Process the power grid software operation data corresponding to each power grid system software to obtain each processed operation data, and establish the correspondence between each power grid system software and each processed operation data.

[0090] The processed operational data can be data obtained by using data warehouse technology to calculate the operational data of the power grid software corresponding to the power grid system software.

[0091] Specifically, data warehouse technology is used to process the power grid software operation data corresponding to each power grid system software collected. After obtaining the processed operation data, the correspondence between the power grid system software and the processed operation data is further established, and the processed operation data is stored in a distributed database based on a full-text retrieval framework.

[0092] Step 606: Based on the correspondence between each power grid system software and each processed operational data, and according to the dimensions of the power grid software data, perform single-dimensional scoring and comprehensive-dimensional scoring on each power grid system software corresponding to each processed operational data.

[0093] Among them, the dimensions of power grid software data can be user behavior, operation data, power grid system software crash data, lag data, and network hijacking data.

[0094] Specifically, based on the correspondence between each power grid system software and each processed operational data, the power grid system software is scored in a single dimension for any operational data and in a comprehensive dimension for multiple operational data, according to each processed operational data. The design of the weight of the data value in each single dimension score is analyzed on a case-by-case basis, and the formula for the comprehensive dimension score is designed based on the weight of each single dimension score.

[0095] The methods for single-dimensional and comprehensive performance evaluation of power grid system software are analyzed from the following perspectives:

[0096] 1. Analyze user behavior from a performance perspective: Analyze the users affected by each action in the power grid system software, including users with slow response, users who encounter errors, and users who experience crashes. Then, analyze the specific problems of each type of user with poor experience.

[0097] 2. In-depth end-to-end tracing: First, based on the requested service items, a list of slow interaction issues (interaction time exceeding a threshold) is identified, and request performance analysis is performed. Specifically, for slow interaction issues, each code is analyzed to determine the total time consumption, time percentage, and number of calls when responding to the user's requested service items, thus identifying the problematic backend code.

[0098] 3. Analyze the impact from the perspective of an individual user: As soon as a user complaint occurs, quickly locate the affected user based on the user account identifier, discover all relevant performance issues of that user, quickly provide feedback and resolve the problems encountered by the user, and improve the user experience.

[0099] 4. Mobile application crash analysis: Provides overall statistical analysis of mobile application crashes, code stack location and trajectory information, tracks crash stacks and processes, etc., to quickly locate and resolve problems, and supports decoding of Java Crash and Native Crash information.

[0100] 5. H5 Page (Webview) Performance Analysis: The performance analysis of H5 page loading is carried out from the dimensions of response time, JS errors, and AJAX performance, including execution time, number of executions, time consumption, white screen time, throughput, number and types of JS errors, number and types of Ajax errors, etc., and provides time consumption analysis for each stage of page loading.

[0101] 6. Lag & ANR Issue Analysis: By capturing ANR information and iOS lag information, we conduct in-depth tracking and analysis of related threads, trace files, and information to discover the causes of lag & ANR. By optimizing application performance, we improve user experience. We also provide lag & ANR details to the power grid system software operator, including basic software and hardware information of the APP, lag & ANR threads, all threads, ANR & lag trace files, and ANR & lag message information.

[0102] 7. Backend Request Performance Analysis: (1) HTTP Request Analysis: Statistics on request response time, errors, and network failures from multiple dimensions such as region, carrier, and network; (2) Socket Request Analysis: View the slowest responding host and the host with the most exceptions. View the details of a single connection by host IP, including detailed device parameters, connection time, DNS resolution time, and the time and byte change trend when writing or reading to the server. Socket Exception Analysis: Exception information that occurs during communication. View more detailed analysis through the summary, including the trend of exception frequency, device distribution, operating system distribution, and exception stack.

[0103] 8. In-depth analysis of request snapshots to achieve end-to-end tracing: Locate problematic HTTP requests, analyze trends in request response time, throughput, HTTP error rate, and network failure rate to further understand the details of the problem; deeply analyze the causes of performance issues, accurately locate individual requests through snapshots, analyze backend tracking, and achieve end-to-end tracing.

[0104] In this embodiment, by monitoring the real user experience of mobile devices from the user's perspective, analyzing user behavior from a performance perspective, conducting in-depth end-to-end tracing, analyzing the impact from the perspective of a single user, analyzing mobile device code crashes, analyzing Webview performance, analyzing ANR and lag issues, analyzing backend request performance, conducting in-depth analysis of request snapshots, and analyzing performance issues through a multi-dimensional combination, it is possible to promptly monitor the single-dimensional and comprehensive scores of the power grid system software and improve the operating efficiency of the power grid system software.

[0105] In one embodiment, such as Figure 7As shown, after constructing the list of legal system software corresponding to the candidate power grid system software, which includes at least one permission list step, the following steps are also included:

[0106] Step 702: Obtain the application actions and set of static permissions corresponding to the power grid system software code of the candidate power grid system software through static code scanning.

[0107] Static code scanning can be a method where, after the source code is written, it is scanned directly using scanning tools without being compiled by a compiler to find solutions for semantic defects and security vulnerabilities in the code.

[0108] Specifically, by using static code scanning to find vulnerabilities in the power grid system software that correspond to static permission sets, the static permission sets requested and used in the code of the candidate power grid system software to be selected are obtained. The static permission set is one of the elements that constitute the request permission set.

[0109] Step 704: By running the installation package of the candidate power grid system software and monitoring the dynamic operation of the candidate power grid system software through a sandbox, obtain the set of dynamic permissions requested and used during the operation of the power grid system software code of the candidate power grid system software.

[0110] Specifically, the installation packages of the shortlisted candidate power grid system software are run, and their dynamic operation is monitored through a sandbox. After identifying vulnerabilities related to dynamic permission sets within the software, the dynamic permission sets requested and used during the software's code execution are obtained. The static permission sets and dynamic permission sets are then merged to form the request permission set. The sandbox system can monitor over 100 behaviors of the candidate power grid system software during operation, including reading files, writing files, obtaining application processes, and reading system configurations. The behavior entities are analyzed through the function call stack to filter candidate power grid system software or SDK behaviors, specifically identifying violators and pinpointing the code locations that trigger these behaviors.

[0111] Step 706: By analyzing the functions of the privacy terms corresponding to the candidate power grid system software, the set of declared permissions contained in the candidate power grid system software is obtained.

[0112] Specifically, by analyzing the functions mentioned in the privacy clauses corresponding to the various permissions to be applied for in the candidate power grid system software, the set of declared permissions contained in the candidate power grid system software to be selected is analyzed.

[0113] In this embodiment, the static permission set, dynamic permission set, and declared permission set of the candidate power grid system software to be selected are obtained by static code scanning, sandbox monitoring, and privacy policy declaration permission set, respectively. This enables permission monitoring of the candidate power grid system software to be added to the normal software database, ensuring the security of the normal software database and improving the system's identification efficiency.

[0114] It should be understood that although the steps in the flowcharts of the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0115] Based on the same inventive concept, this application also provides a user account information processing device for power grid system software to implement the aforementioned user account information processing method. The solution provided by this device is similar to the implementation described in the above method. Therefore, the specific limitations of one or more user account information processing device embodiments of power grid system software provided below can be found in the limitations of the user account information processing method for power grid system software described above, and will not be repeated here.

[0116] In one embodiment, such as Figure 9 As shown, a user account information processing device for power grid system software is provided, comprising: an account data acquisition module 902, an account information generation module 904, a registered account acquisition module 906, a comparison result determination module 908, a comparison result judgment module 910, and an account information access module 912, wherein:

[0117] The account data acquisition module 902 is used to acquire basic information of user accounts and user account feature information corresponding to the basic information of user accounts; and to acquire a list of fake software records corresponding to at least one power grid system software.

[0118] The account information generation module 904 is used to generate corresponding user account identifiers based on the basic information of user accounts, and to generate user account profile information corresponding to the basic information of each user account based on the characteristic information of each user account and the corresponding user account identifiers.

[0119] The registration account module 906 is used to send the user account identifier and user account profile information to the corresponding operation database of the power grid system software when logging into the power grid system software through the user account identifier, so as to obtain the registered user account corresponding to the user account. The registered user account records the user account identifier and user account profile information in the operation database.

[0120] The comparison result determination module 908 is used to compare the software attribute information in each fake software list with the software attribute information in the power grid system software to be detected, and determine the first comparison result;

[0121] The comparison result determination module 910 is used to select the power grid system software to be tested as the target power grid system software when the first comparison result meets the preset conditions.

[0122] The account information access module 912 is used to encrypt user account information based on the user account identifier and user account profile information in the registered user account, and to log in through the target power grid system software to access the target secure user account information.

[0123] In one embodiment, the comparison result determination module 908 is further configured to: classify the fake software information corresponding to the power grid system software according to the software anomaly category to obtain a software anomaly database corresponding to the software anomaly category; and determine the fake software data packet capacity range and request permission set corresponding to the software anomaly database based on the fake software information in the anomaly database, wherein the fake software data packet capacity range and request permission set are used to determine whether the candidate power grid system software is abnormal.

[0124] In one embodiment, the comparison result determination module 908 is further configured to: construct a list of legal system software corresponding to the candidate power grid system software, wherein the list of legal system software includes at least one permission list; compare the software function corresponding to the candidate power grid system software with each permission list in the legal system software; if the second comparison result indicates that the candidate power grid system software has excessive permission requests, then prompt the modification of the software function corresponding to the candidate power grid system software; re-execute the comparison of the software function corresponding to the candidate power grid system software with each permission list in the legal system software with the modified candidate power grid system software until the second comparison result shows that the function and permission match, and write the candidate power grid system software into the normal software database.

[0125] In one embodiment, the comparison result determination module 910 is further configured to: determine whether the candidate power grid system software is recorded in the normal software database; if the first determination result is negative, continue to determine whether the data packet capacity and request permissions corresponding to the candidate power grid system software conform to the fake software data packet capacity range and request permission set corresponding to each software anomaly database; if the second determination result is normal, according to the software function corresponding to the candidate power grid system software, traverse the software functions corresponding to the normal software database, and select power grid system software with a software function matching degree greater than a preset matching degree from the normal software database as the target power grid system software.

[0126] In one embodiment, the power grid software monitoring module is configured to: acquire power grid software operation data corresponding to each power grid system software, wherein the power grid software operation data includes at least one power grid software data dimension; process the power grid software operation data corresponding to each power grid system software to obtain processed operation data, and establish a correspondence between each power grid system software and each processed operation data; based on the correspondence between each power grid system software and each processed operation data, and according to the power grid software data dimension, perform single-dimensional scoring and comprehensive-dimensional scoring on each power grid system software corresponding to each processed operation data.

[0127] In one embodiment, the comparison result determination module 908 is further configured to: obtain the set of static permissions and requests corresponding to the power grid system software code of the candidate power grid system software through static code scanning; obtain the set of dynamic permissions and requests during the operation of the power grid system software code of the candidate power grid system software by running the installation package of the candidate power grid system software and monitoring the dynamic operation of the candidate power grid system software through a sandbox; and obtain the set of declared permissions contained in the candidate power grid system software by analyzing the functions of the privacy terms corresponding to the candidate power grid system software.

[0128] Each module in the user account information processing device of the aforementioned power grid system software can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device in hardware form, or stored in the memory of a computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0129] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 10As shown, the computer device includes a processor, memory, and a network interface connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The database stores server data. The network interface communicates with external terminals via a network connection. When executed by the processor, the computer program implements a user account information processing method for power grid system software.

[0130] Those skilled in the art will understand that Figure 10 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0131] In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.

[0132] In one embodiment, a computer-readable storage medium is provided storing a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0133] In one embodiment, a computer program product or computer program is provided, the computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and executes the computer instructions, causing the computer device to perform the steps in the above method embodiments.

[0134] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0135] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0136] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0137] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for processing user account information in power grid system software, characterized in that, The method includes: Obtain basic user account information and corresponding user account feature information; and obtain a list of fake software records corresponding to at least one power grid system software. Based on the user account basic information, a corresponding user account identifier is generated, and based on each user account feature information and the corresponding user account identifier, user account profile information corresponding to each user account basic information is generated; When logging into the power grid system software using the user account identifier, the user account identifier and the user account profile information are sent to the operating database corresponding to the power grid system software to obtain the registered user account corresponding to the user account. The registered user account is the one for which the operating database records the user account identifier and the user account profile information. The software attribute information in each of the fake software record lists is compared with the software attribute information in the power grid system software to be tested, and the first comparison result is determined. The fake software information corresponding to the power grid system software is classified according to software anomaly categories to obtain a software anomaly database corresponding to each software anomaly category. Based on the fake software information in the anomaly database, the capacity range of fake software data packets and the set of requested permissions corresponding to the software anomaly database are determined. The capacity range of fake software data packets and the set of requested permissions are used to determine whether the candidate power grid system software is abnormal. If the first comparison result meets the preset conditions, the power grid system software to be detected is selected as the target power grid system software. A list of legal system software corresponding to the candidate power grid system software is constructed, and the list of legal system software includes at least one permission list. The software function corresponding to the candidate power grid system software is compared with each of the permission lists in the legal system software. If the second comparison result indicates that the candidate power grid system software has excessive permission requests, a prompt is made to modify the software function corresponding to the candidate power grid system software. The modified candidate power grid system software is re-executed to compare the software function corresponding to the candidate power grid system software with each of the permission lists in the legal system software until the second comparison result shows that the function and permissions match. The candidate power grid system software is then written to the normal software database. The second comparison result indicates either excessive permissions or no excessive permissions. The user account information is encrypted based on the user account identifier and user account profile information in the registered user account, and then logged in through the target power grid system software to access the target secure user account information.

2. The method according to claim 1, characterized in that, The method further includes: If the candidate power grid system software is not recorded in the normal software database, and the first determination result is negative, it is further determined whether the data packet capacity and request permissions corresponding to the candidate power grid system software conform to the fake software data packet capacity range and request permission set corresponding to each software abnormal database. If the second judgment result is normal, based on the software functions corresponding to the candidate power grid system software, the software functions corresponding to the normal software database are traversed, and the power grid system software with a software function matching degree greater than a preset matching degree is selected from the normal software database as the target power grid system software.

3. The method according to claim 2, characterized in that, The method further includes: Obtain power grid software operation data corresponding to each of the power grid system software, wherein the power grid software operation data includes at least one power grid software data dimension; Data processing is performed on the power grid system software corresponding to each of the power grid system software to obtain each processed operating data, and a correspondence between each of the power grid system software and each of the processed operating data is established; Based on the correspondence between each of the power grid system software and each of the processed operating data, and according to the data dimensions of the power grid software, each of the power grid system software corresponding to each of the processed operating data is scored in a single dimension and in a comprehensive dimension.

4. The method according to claim 1, characterized in that, Following the step of constructing the list of legitimate system software corresponding to the candidate power grid system software, the method further includes: By static code scanning, the application actions and the set of static permissions used corresponding to the power grid system software code of the candidate power grid system software are obtained; By running the installation package of the candidate power grid system software and monitoring the dynamic operation of the candidate power grid system software through a sandbox, the dynamic permission set of the power grid system software code during the operation of the candidate power grid system software is obtained; By analyzing the functionality of the privacy terms corresponding to the candidate power grid system software, the set of declared permissions contained in the candidate power grid system software is obtained.

5. A user account information processing device for power grid system software, characterized in that, The device includes: The account data acquisition module is used to acquire basic information of user accounts and user account feature information corresponding to the basic information of user accounts; and to acquire a list of fake software records corresponding to at least one power grid system software. The account information generation module is used to generate a corresponding user account identifier based on the user account basic information, and to generate user account profile information corresponding to each user account basic information according to each user account feature information and the corresponding user account identifier. The registration account acquisition module is used to send the user account identifier and the user account profile information to the running database corresponding to the power grid system software when logging into the power grid system software through the user account identifier, so as to obtain the registered user account corresponding to the user account. The registered user account records the user account identifier and the user account profile information in the running database. The comparison result determination module is used to compare the software attribute information in each of the fake software record lists with the software attribute information in the power grid system software to be detected, and determine the first comparison result; The comparison result determination module is used to classify the fake software information corresponding to the power grid system software according to the software anomaly category, thereby obtaining a software anomaly database corresponding to the software anomaly category; based on the fake software information in the anomaly database, it determines the fake software data packet capacity range and request permission set corresponding to the software anomaly database, wherein the fake software data packet capacity range and the request permission set are used to determine whether the candidate power grid system software is abnormal; if the first comparison result meets the preset conditions, the power grid system software to be detected is selected as the target power grid system software; a list of legitimate system software corresponding to the candidate power grid system software is constructed, wherein the list of legitimate system software is... The system includes at least one permission list; the software functions corresponding to the candidate power grid system software are compared with the permission lists of the legal system software. If the second comparison result indicates that the candidate power grid system software has excessive permission requests, a prompt is made to modify the software functions corresponding to the candidate power grid system software; the modified candidate power grid system software is then re-executed to compare the software functions corresponding to the candidate power grid system software with the permission lists of the legal system software until the second comparison result shows that the functions and permissions match, at which point the candidate power grid system software is written to the normal software database; the second comparison result indicates either excessive permissions or no excessive permissions. The account information access module is used to encrypt the user account information based on the user account identifier and user account profile information in the registered user account, and to log in through the target power grid system software to access the target secure user account information.

6. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 4.

7. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 4.

8. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 4.

Images