Management and control method for database fields in power grid data

Abstract

The invention provides a management and control method and device for database fields in power grid data, equipment and a medium, and belongs to the technical field of power grid data security. The management and control method comprises the following steps: configuring a sensitive level for each field in a database in power grid data; field operation authorities for different sensitive levels are distributed to the user; when the user operates the database, hyper-authority operation of the user on the field is intercepted according to the field operation authority of the user; according to the responsibility change of the user, updating the field operation authority of the user; and updating the sensitivity level of the related field according to the change of the data type in the database. According to the method, corresponding operation authorities are set according to reading, writing, modifying and deleting operations of a user on different sensitive level fields, control over data reading can be achieved, control over data writing, modifying and deleting can also be achieved, and the user experience is improved through operation control over the field level. And it can be ensured that only users with corresponding permissions can execute necessary operations.

Description

Technical Field

[0001] The present invention belongs to the technical field of power grid data security, and specifically relates to a control method, a control device, an electronic device and a storage medium for a power grid data middle station database field. Background Art

[0002] The power grid data center is a unified data platform built on the basis of big data, cloud computing and other technologies in the power system. It integrates various types of data inside and outside the power enterprise to provide unified data services and application support. With the further strengthening of data use in the data center, the flow of data involves more and more complex scenarios and a variety of access roles, which brings new challenges to the data protection of the data center.

[0003] As more and more power data is gathered in the data center, the data in the center shows the characteristics of rapid increase in data volume, large user scale, and wide coverage. The relevant data gathered by power include marketing, power grid, materials, finance and other data, some of which may be sensitive or should not be accessed by specific users or applications. However, the current coarse-grained management and control strategy is difficult to take into account the data security of the power grid data center database operation process. Summary of the invention

[0004] In view of the deficiencies in the prior art, the present invention provides a control method, a control device, an electronic device and a storage medium for a power grid data center database field.

[0005] In order to solve one, part or all of the above technical problems, the technical solution adopted by the present invention is: A method for controlling fields in a power grid data middle-end database comprises: configuring a sensitivity level for each field in the power grid data middle-end database; allocating field operation permissions for different sensitivity levels to users; when a user operates the database, intercepting the user's super-authorized operation on the field according to the user's field operation permissions; updating the user's field operation permissions according to changes in user responsibilities; and updating the sensitivity level of related fields according to changes in data types in the database.

[0006] Furthermore, the sensitivity levels include, from low to high, a public field, an internal field, a sensitive field, and a highly sensitive field.

[0007] Furthermore, the method of assigning field operation permissions for different sensitivity levels to users includes: using the numbers 1, 2, 4, and 8 to represent the read, write, modify, and delete operation permissions of database fields, respectively; expressing the permission value for the field in hexadecimal form of the sum of the numbers represented by the corresponding operation permissions; configuring the user's operation permissions for public fields, internal fields, sensitive fields, and highly sensitive fields, respectively, and obtaining the corresponding permission values, respectively; concatenating the user's permission values ​​for public fields, internal fields, sensitive fields, and highly sensitive fields into a string, and using the string as the user's field operation permissions for different sensitivity levels.

[0008] Furthermore, when the permission value is 0, it means that all operations on the field are prohibited.

[0009] A control device for fields in a power grid data middle-end database, comprising a field sensitivity level configuration module, a user authority configuration module, and a field control module; the field sensitivity level configuration module is used to configure a sensitivity level for each field in the power grid data middle-end database, and is used to update the sensitivity level of related fields after the data type in the database changes; the user authority configuration module is used to assign field operation permissions for different sensitivity levels to users, and is used to update their field operation permissions after the user's responsibilities change; the field control module is used to intercept a user's super-authority operation on a field based on the user's field operation permissions.

[0010] Furthermore, the sensitivity levels include, from low to high, a public field, an internal field, a sensitive field, and a highly sensitive field.

[0011] Furthermore, the field operation permission is a 4-bit string, each character of which is a hexadecimal character from 0 to F; the characters from left to right represent the permission values ​​for public fields, internal fields, sensitive fields and highly sensitive fields respectively; the permission value is the hexadecimal sum of the corresponding permissions in the numbers 1, 2, 4, and 8 corresponding to the field read, write, modify and delete operation permissions; when the permission value is 0, it means that all operations on the field are prohibited.

[0012] An electronic device comprises a processor and a memory; the memory is used to store executable instructions, and the processor is used to execute the instructions to implement the control method.

[0013] A computer-readable storage medium stores instructions, and when the instructions are executed, the control method is implemented.

[0014] Compared with the prior art, the present invention has the following beneficial effects: The present invention provides a field-level refined access control strategy for the power grid data middle-end database, which can realize refined access control of permissions of the power grid data middle-end database, meet the requirements of data privacy compliance and data security, and ensure the effective use of data.

[0015] The present invention can be applied to the power industry and energy management field to ensure the security and privacy of the power grid data center database while allowing appropriate data access and sharing. The present invention has the potential to play an important role in the fields of smart grid, power distribution and monitoring systems, and improve the efficiency of data management and the protection level of data privacy.

[0016] The present invention sets corresponding operation permissions for users' reading, writing, modifying and deleting operations on fields of different sensitivity levels, which can not only realize the control over data reading, but also realize the control over data writing, modification and deletion. Through field-level operation control, it can ensure that only users with corresponding permissions can perform necessary operations. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The present invention is further described in detail below in conjunction with the accompanying drawings.

[0018] Figure 1 : Flow chart of embodiment 1 of the present invention; Figure 2 : A schematic diagram of Embodiment 2 of the present invention; Figure 3 : Schematic diagram of embodiment 3 of the present invention. DETAILED DESCRIPTION

[0019] In order to better understand the present invention, the content of the present invention is further clearly described below in conjunction with the embodiments and the accompanying drawings, but the protection content of the present invention is not limited to the following embodiments. In the following description, a large number of specific details are provided to provide a more thorough understanding of the present invention. However, it is obvious to those skilled in the art that the present invention can be implemented without one or more of these details.

[0020] Example 1: See Figure 1 The purpose of this embodiment is to provide a method for controlling the fields of a power grid data center database. The method includes: S1. Configure the sensitivity level for each field in the power grid data center database.

[0021] The power grid data center database contains multiple data tables, each of which contains different fields. In the existing technology, the management and control of databases is mostly based on data tables, but different fields in the same database may also have different sensitivity levels, and fields with different sensitivity levels must also adopt different management methods.

[0022] This step configures the corresponding sensitivity level for each field in the power grid data center database. The sensitivity levels from low to high include public fields, internal fields, sensitive fields, and highly sensitive fields.

[0023] Public fields are data that do not require any restrictions, and public sharing will not have a negative impact on grid operations or any individual. Internal fields are for internal use only, and leakage may have a certain impact on grid operations. Sensitive fields involve key grid operations, customer information or trade secrets, and leakage will have a significant impact on grid operations or related parties. Highly sensitive fields involve national security, critical infrastructure or confidential information, and leakage will cause serious or even catastrophic consequences.

[0024] S2. Assign field operation permissions of different sensitivity levels to users.

[0025] According to the user's access role, responsibilities, and business needs in the power grid data center, corresponding operation permissions are assigned to the user.

[0026] Specifically, the operations on the fields in the database include reading, writing, modifying and deleting, which are represented by permission numbers 1, 2, 4 and 8 respectively, and the hexadecimal sum of these numbers represents the user's field operation permission value. For example, if the operation permission value of a field is represented as D, the hexadecimal D can only be the sum of the numbers 1, 4 and 8, so D means that the user has read, modify and delete permissions for the field.

[0027] The corresponding relationship between the permission value and the specific operation permission is shown as follows: 0: all prohibited; 1: read, 2: write, 4: modify, 8: delete; 3: Read + Write, 5: Read + Modify, 9: Read + Delete, 6: Write + Modify, A: Write + Delete, C: Modify + Delete; 7: Read + Write + Modify, B: Read + Write + Delete, D: Read + Modify + Delete, E: Write + Modify + Delete; F: Read + Write + Modify + Delete.

[0028] Then, in the order of sensitivity levels, the user's operation permissions for public fields, internal fields, sensitive fields, and highly sensitive fields are configured respectively, and the corresponding permission values ​​are obtained respectively. The user's permission values ​​for public fields, internal fields, sensitive fields, and highly sensitive fields are concatenated into a 4-digit string, which is the user's field operation permission.

[0029] For example, if a user's field operation permission is F710, the permission value for public fields is F (permissions are read + write + modify + delete), the permission value for internal fields is 7 (permissions are read + write + modify), the permission value for sensitive fields is 1 (permission is read), and the permission value for highly sensitive fields is 0 (permission is all prohibited).

[0030] S3. When a user operates the database, the user's super-authorized operations on the fields are intercepted according to the user's field operation permissions.

[0031] When a user operates the database, the user's field operation permissions are obtained, and the relevant fields specifically operated when operating the database are traversed. According to the sensitivity level of the field, it is determined whether the user's operation on the field meets the requirements of the operation permissions, and the operations that meet the permission requirements are released, and the super-permission operations that do not meet the permission requirements are intercepted.

[0032] S4. Update field operation permissions according to changes in user responsibilities; update the sensitivity level of related fields according to changes in data types in the database.

[0033] When a user's position or responsibilities change, their field operation permissions should be updated synchronously. When the data type in the database changes, its sensitivity level may also change. At this time, the sensitivity level of the involved fields needs to be updated synchronously.

[0034] Example 2: See Figure 2 The purpose of this embodiment is to provide a control device for a field of a power grid data center database, which is used to execute the control method of embodiment 1. The control device includes: a field sensitivity level configuration module, a user authority configuration module, and a field control module.

[0035] The field sensitivity level configuration module is used to configure the sensitivity level for each field in the power grid data center database, and is used to update the sensitivity level of the relevant field after the data type in the database changes. In combination with Example 1, the acquisition module is used to execute steps S1 and S4.

[0036] The user authority configuration module is used to allocate field operation permissions for different sensitivity levels to users, and is used to update the field operation permissions of users after their responsibilities change. In combination with embodiment 1, the correction module is used to execute steps S2 and S4.

[0037] The field control module is used to intercept the user's super-authorized operation on the field according to the user's field operation authority. In combination with embodiment 1, the pre-processing module is used to execute step S3.

[0038] Regarding the device in this embodiment, the specific manner in which each unit or module performs operations has been described in detail in Example 1 and will not be elaborated here.

[0039] Those skilled in the art should understand that for the convenience and simplicity of description, the present application only uses the division of the above-mentioned functional modules or units as examples in the device embodiments. In actual applications, the above-mentioned functions can be assigned to different functional modules or units as needed, that is, the internal structure of the device can be divided into different functional modules or units to complete all or part of the functions described above.

[0040] Example 3: See Figure 3 The purpose of this embodiment is to provide an electronic device, including at least one processor and one or more memories for storing instructions executable by the processor. The processor is used to execute instructions in the memory to implement the control method described in Example 1.

[0041] The electronic device can be a desktop computer, a portable computer, a network server, a mobile phone, a tablet computer, a wireless terminal, an embedded device, a chip system or a Figure 3 In addition, Figure 3 The components shown in the figure do not constitute a limitation on the terminal device, except Figure 3 In addition to the components shown, the electronic device may include more or fewer components than shown, or combine certain components, or arrange the components differently.

[0042] Embodiment 4: The purpose of this embodiment is to provide a computer-readable storage medium.

[0043] All or part of the processes in the above method embodiments can be completed by computer instructions to instruct relevant hardware. The program can be stored in the computer-readable storage medium. When the program is executed, it can implement the management and control method described in Example 1.

[0044] The computer-readable storage medium may be an internal storage unit of the electronic device of Embodiment 3, or an external storage device of the electronic device. Further, the computer-readable storage medium may include both an internal storage unit of the electronic device and an external storage device. The computer-readable storage medium is used to store computer programs and other programs and data required by the electronic device. The computer-readable storage medium may also be used to temporarily store data that has been output or is to be output.

[0045] In conjunction with the several embodiments provided in this application, it should be understood that the provided devices and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the assessment of the modules or units is only a logical function assessment. There may be other assessment methods in actual implementation, such as multiple modules or units or components can be combined or integrated into another device, or some features can be ignored or not executed.

[0046] In addition, in the embodiment of the device of the present application, each functional module or unit can be integrated into one unit, or each module or unit can exist physically separately, or two or more modules or units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional modules.

[0047] If the above-mentioned integrated unit is implemented in the form of a software function module and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard drives, ROM, RAM, magnetic disks or optical disks.

[0048] Finally, it should be noted that the above embodiments are only used to illustrate the technical solution of the present invention rather than to limit it. Other writing or equivalent substitution of the technical solution of the present invention made by ordinary technicians in this field should be included in the scope of the claims of the present invention as long as they do not depart from the spirit and scope of the technical solution of the present invention.

Claims

1. A method for controlling fields in a power grid data center database, characterized in that: include: Configure the sensitivity level for each field in the power grid data center database; Assign users field operation permissions based on different sensitivity levels; When a user operates the database, the user's super-authorized operations on the fields are intercepted according to the user's field operation permissions; Update field operation permissions based on changes in user responsibilities; Update the sensitivity level of related fields according to changes in data types in the database.

2. The method for controlling the fields of the power grid data center database according to claim 1 is characterized in that: Methods for assigning field operation permissions to users at different sensitivity levels include: The numbers 1, 2, 4, and 8 represent the read, write, modify, and delete permissions for database fields. The permission value for the field is expressed in hexadecimal as the sum of the numbers represented by the corresponding operation permissions; Configure the user's operation permissions for public fields, internal fields, sensitive fields, and highly sensitive fields, and obtain the corresponding permission values ​​respectively; The user's permission values ​​for public fields, internal fields, sensitive fields, and highly sensitive fields are concatenated into a string, and the string is used as the user's field operation permission for different sensitivity levels.

3. The method for controlling the fields of the power grid data center database according to claim 1 is characterized in that: The sensitivity levels include, from low to high, public fields, internal fields, sensitive fields, and highly sensitive fields.

4. The method for controlling the fields of the power grid data middle station database according to claim 2 is characterized in that: When the permission value is 0, it means that all operations on the field are prohibited.

5. A control device for a field of a power grid data center database, characterized in that: Including field sensitivity level configuration module, user permission configuration module, and field control module; The field sensitivity level configuration module is used to configure the sensitivity level of each field in the power grid data center database, and is used to update the sensitivity level of the relevant field after the data type in the database changes; The user authority configuration module is used to assign field operation permissions for different sensitivity levels to users and to update their field operation permissions after the user's responsibilities change; The field control module is used to intercept the user's super-authorized operations on the field according to the user's field operation permissions.

6. The control device for power grid data middle station database field according to claim 5, characterized in that: The sensitivity levels include, from low to high, public fields, internal fields, sensitive fields, and highly sensitive fields.

7. The control device for power grid data middle station database field according to claim 5, characterized in that: The field operation permission is a 4-bit string, each character of which is a hexadecimal character from 0 to F; the characters from left to right represent the permission values ​​for public fields, internal fields, sensitive fields and highly sensitive fields respectively; the permission value is the hexadecimal sum of the corresponding permissions in the numbers 1, 2, 4, and 8 corresponding to the field read, write, modify and delete operation permissions; when the permission value is 0, it means that all operations on the field are prohibited.

8. An electronic device, characterized in that: It includes a processor and a memory; the memory is used to store executable instructions, and the processor is used to execute the instructions to implement the management and control method described in any one of claims 1 to 4.

9. A computer-readable storage medium, characterized in that: The readable storage medium stores instructions, and when the instructions are executed, the control method described in any one of claims 1 to 4 is implemented.

Images