A cloud-based government affair information management method

Abstract

The application relates to the technical field of government information management, in particular to a government information management method based on a cloud, which comprises the following steps: S1, adding a sensitivity label to each piece of government data in a cloud storage layer; S2, extracting data from a government database and generating a dynamic data view with permission marks; S3, establishing a mapping relationship table of a routing key and a data source address; S4, obtaining a request department function code, a business scene code and a target data identifier; S5, matching a target data source, performing a desensitization operation on a sensitive field based on the permission marks in the dynamic data view; and S6, if a genetic mark bit of original data is true, superimposing a data security level in an original label and a current security level to form a new label. Through the construction of the sensitivity label and the dynamic permission control mechanism, the application realizes the safe inheritance and accurate access of government data in cross-department circulation, and significantly improves the security and compliance of data management.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of government information management, and particularly relates to a government information management method based on a cloud. BACKGROUND

[0002] With the acceleration of the process of digital government, a large amount of cross-department and multi-level government data is converged to a cloud platform for unified management and shared calling. In order to improve the data use efficiency and business response speed, government units at all levels generally rely on centralized government databases under the cloud computing architecture to call, process and share data resources in multi-business scenarios. Because the data types are various, the sources are diverse, and sensitive information such as privacy, finance and identity is involved, how to ensure data availability while realizing dynamic control of data access permission and effective protection of sensitive content has become one of the core challenges in the design of current government information management systems.

[0003] The existing technology generally has the following problems: 1) lacking a fine-grained data permission control mechanism, which cannot accurately limit the field-level read-write permission according to the department function and specific business scenario of the visitor; 2) lacking a transmission and inheritance logic of sensitivity labels in the data flow process, resulting in the loss of original secret level protection of sensitive information after multiple transcriptions; 3) the data desensitization operation usually adopts a static strategy and cannot be dynamically adjusted according to the access permission, which has the problem of over or under desensitization. Therefore, there is an urgent need for a government information management method based on a cloud to solve the above problems. SUMMARY

[0004] In order to achieve the above purpose, the present application provides a government information management method based on a cloud.

[0005] A government information management method based on a cloud, comprising the following steps:

[0006] S1: adding a sensitivity label to each piece of government data in a cloud storage layer, the sensitivity label comprising a data secret level and a genetic marker bit;

[0007] S2: extracting data from a government database according to the department function code and the current business scenario code of the requesting department and generating a dynamic data view with permission labels;

[0008] S3: combining the department function code and the business scenario code into a routing key, and establishing a mapping relationship table of the routing key and the data source address;

[0009] S4: obtaining the department function code, the business scenario code and the target data identifier of the requesting party;

[0010] S5: According to the department function code and business scenario code of S4, the mapping relationship table of S3 is queried to match the target data source; at the same time, when reading data from the target data source, based on the permission mark in the dynamic data view generated by S2, desensitization operation is performed on sensitive fields;

[0011] S6: When data is written by a new department, a new sensitivity label is generated according to the secret level of the writing department, and if the genetic mark bit of the original data is true, the data secret level in the original label is superimposed with the current secret level to form a new label.

[0012] Optionally, S1 specifically comprises:

[0013] S11: When the government data is first stored in the cloud storage layer, the initial data secret level is determined by the data source department, and the initial data secret level is selected from a predefined secret level enumeration set, including public level L1, internal level L2, and confidential level L3;

[0014] S12: Set the genetic mark bit according to the data theme type, and the genetic mark bit is a Boolean type identifier , the expression is: ;

[0015] Among them, is the genetic mark bit, and when the Boolean value is 1, it means true, and 0 means false.

[0016] Optionally, S2 specifically comprises:

[0017] S21: Generate an initial query condition according to the request department function code and business scenario code, and initiate a data query request to the government database through a database query engine;

[0018] S22: Return the original data set meeting the query condition from the government database, and temporarily store the original data set in a temporary cache area;

[0019] S23: Retrieve the field-level permission control rule matched with the request department function code and business scenario code from the permission control strategy library, and the permission control rule defines the read-write permission of each field;

[0020] S24: Traverse the original data set in the temporary cache area, and generate a readable or writable permission mark for each field according to the field-level permission control rule obtained by S23;

[0021] S25: The processed original data set and the corresponding field permission mark are integrated to form a dynamic data view.

[0022] Optionally, S23 specifically comprises:

[0023] S231: Based on the request department function code and business scenario code, generate the permission policy query key by combining the following expression: ,in, This is the key for querying permission policies; The departmental function code for the requesting department; Code for the current business scenario; The string concatenation operator;

[0024] S232: Query key using permission policy The system retrieves the access control policy library by key-value matching to obtain the corresponding access control rule index.

[0025] S233: Based on the access control rule index, locate the field-level access control rule record in the access control policy library, load the read permission value and write permission value of each data field defined in the record, and form an access control rule.

[0026] Optionally, S3 specifically includes:

[0027] S31: Obtain the unique data source address identifier for each government data source from the pre-configured government database registry;

[0028] S32: Based on the functional code of the department to which each data source belongs and the serviceable business scenario code, a routing key is formed by combining and concatenating them in a predefined order. The specific expression is as follows: ,in, Indicates the generated routing key; This indicates the departmental function code corresponding to the data source; Indicates the business scenario code to which the data source applies; This represents a string concatenation operation;

[0029] S33: Based on the routing key generated in S32, map it one by one with the corresponding data source address identifier to generate a key-value pair mapping table with the routing key as the retrieval index and the data source address as the mapping result;

[0030] S34: Store the key-value pair mapping table generated in S33 to the cloud configuration center.

[0031] Optionally, S4 specifically includes:

[0032] S41: Receive data access requests submitted by the requester through the government service interface, including the requester's departmental authentication credentials, business call context information, and data target parameters;

[0033] S42: Parse the identity authentication credentials submitted by the requester, and extract the department function code after successful authentication by combining the verification results of the unified identity authentication platform;

[0034] S43: Extract the business scene code from the business call context information, including the current operation type, the government affair process node or the triggering method;

[0035] S44: Extract the target data identifier from the data target parameter set, including the data table number, the data object primary key or the label attribute;

[0036] S45: Use the extracted department function code, business scene code and target data identifier as structured request meta-information.

[0037] Optionally, the S5 specifically includes:

[0038] S51: Combine the department function code and the business scene code obtained in S4 into a request routing key according to a predetermined splicing order, and query the routing key and data source address mapping relationship table generated in S3 to determine the target data source address;

[0039] S52: Establish a data connection channel according to the target data source address, and read the original data from the target data source based on the target data identifier provided in S4;

[0040] S53: Load the original data obtained from the target data source into the dynamic data view generated in S2, and identify the read-write permission of the sensitive field according to the permission mark corresponding to each field;

[0041] S54: According to the predefined desensitization strategy, perform corresponding desensitization processing on the sensitive field identified as only readable or unreadable in S53 to obtain a desensitized data view;

[0042] S55: Output the desensitized data view for the requester to access.

[0043] Optionally, the S54 specifically includes:

[0044] S541: Traverse the dynamic data view in S53, and check the permission mark of each sensitive field one by one to filter out the sensitive field with read permission mark of 0 or write permission mark of 0, and mark it as a field to be desensitized;

[0045] S542: According to the field type and permission mark of the field to be desensitized, retrieve the corresponding desensitization rule from the predefined desensitization strategy library, including the replacement method, the length of the intercepted or the mask format of the defined field value;

[0046] Specifically, if the desensitization rule is mask replacement, the field value is replaced according to the predefined mask format;

[0047] If the desensitization rule is character interception, the field value is intercepted with a fixed length;

[0048] If the desensitization rule is a null replacement, the field value is directly set to null;

[0049] S543: update the field value after desensitization to the dynamic data view, and complete the desensitization operation.

[0050] Optionally, the S6 specifically comprises:

[0051] S61: when a new department performs a data write operation on the government database, the department secret level corresponding to the new department is obtained as the initial secret level of the current data write operation;

[0052] S62: judge the value of the genetic marker bit in the original sensitivity label of the data to be written; if the value of the genetic marker bit is true, proceed to the next step, otherwise directly use the secret level of the new department as the final secret level of the new sensitivity label;

[0053] S63: if the genetic marker bit is true, extract the data secret level in the original data label, compare it with the current department secret level, and sort them in order from high to low according to the sensitivity level;

[0054] S64: select the highest secret level from the S63 sorting result as the final secret level of the superimposed new sensitivity label;

[0055] S65: based on the final secret level determined in S64, update the sensitivity label of the data, and complete the data write operation.

[0056] Optionally, the S63 specifically comprises:

[0057] S631: obtain the secret level value of the current write department and the secret level value in the original data label from the sensitivity level enumeration set, respectively;

[0058] S632: based on the pre-defined sensitivity level value mapping table, convert the obtained secret level into the corresponding level value, specifically, the public level L1 corresponds to the level value 1, the internal level L2 corresponds to the level value 2, and the confidential level L3 corresponds to the level value 3;

[0059] S633: according to the two level values obtained in S632, compare the numerical values, and determine the level with the larger numerical value as the secret level value of the new label;

[0060] S634: reverse map the level value determined in S633 back to the corresponding sensitivity level enumeration as the secret level of the final new sensitivity label.

[0061] The beneficial effects of the present application are:

[0062] The application adds a sensitivity label containing a secret level and a genetic attribute to each piece of government data in the cloud storage layer, realizes label inheritance and secret level superposition of data during circulation between different departments, ensures that sensitive information is not downgraded during multiple writing or sharing processes, and fundamentally improves the security and controllability of the data full life cycle.

[0063] The application dynamically generates data access permission labels by combining department function codes and business scenario codes, and performs differentiated desensitization processing at the field level, so that the data can accurately output visible content according to the access permission during reading, effectively solving the problems of extensive permission configuration and static desensitization strategy in the current government system. BRIEF DESCRIPTION OF DRAWINGS

[0064] In order to more clearly illustrate the technical solutions in the present application or prior art, the following will briefly introduce the drawings needed to be used in the embodiments or prior art description. Obviously, the drawings in the following description only illustrate the present application, and other drawings can also be obtained by those skilled in the art without creative effort.

[0065] Fig. 1 The figure is a schematic diagram of the government information management method of the embodiment of the present application.

[0066] Fig. 2 The figure is a schematic diagram of the flow of superimposed new label formation of the embodiment of the present application. DETAILED DESCRIPTION

[0067] The present application will be described in detail below in combination with the drawings and specific embodiments. It should be noted that in order to make the embodiments more detailed, the following embodiments are the best, preferred embodiments, and other alternative ways can also be used by those skilled in the art to implement them; and the drawings are only used to more specifically describe the embodiments, and are not intended to specifically limit the present application.

[0068] It should be noted that in the specification, "one embodiment", "embodiment", "exemplary embodiment", "some embodiments" and the like indicate that the described embodiments can include a specific feature, structure or property, but not necessarily every embodiment includes the specific feature, structure or property. In addition, when a specific feature, structure or property is described in combination with an embodiment, it should be within the knowledge of those skilled in the related art to realize this feature, structure or property in combination with other embodiments (whether or not explicitly described).

[0069] Generally, terms can be understood at least in part from the context. For example, the term "one or more" as used herein, depending at least in part upon the context, can be used to describe any feature, structure, or characteristic in a singular sense or can be used to describe combinations of features, structures or characteristics in a plural sense. Additionally, the term "based on" can be understood as not necessarily intended to convey an exclusive set of factors, but instead can allow for existence of additional factors not necessarily expressly described.

[0070] As shown in Figs. 1-2 , a cloud-based government information management method comprises the following steps:

[0071] S1: adding a sensitivity label to each piece of government data in the cloud storage layer, the sensitivity label including a data security level and a genetic marker bit; the genetic marker bit is used to indicate the inheritance state of the sensitivity label in the data flow process;

[0072] S2: extracting data from the government database according to the department function code of the requesting department and the current business scenario code, and generating a dynamic data view with permission markers; the permission markers include field-level read / write identifiers;

[0073] S3: combining the department function code and the business scenario code into a routing key, and establishing a mapping relationship table between the routing key and the data source address;

[0074] S4: obtaining the department function code, the business scenario code and the target data identifier of the requesting party;

[0075] S5: querying the mapping relationship table of S3 according to the department function code and the business scenario code of S4 to match the target data source; at the same time, when reading data from the target data source, based on the permission markers in the dynamic data view generated in S2, perform desensitization operation on sensitive fields;

[0076] S6: when data is written by a new department, a new sensitivity label is generated according to the security level of the writing department, and if the genetic marker bit of the original data is true, the data security level in the original label is superimposed with the current security level to form a new label.

[0077] S1 specifically includes:

[0078] S11: when the government data is first stored in the cloud storage layer, the initial data security level is determined by the data source department, and the initial data security level is selected from a predefined security level enumeration set, including public level L1, internal level L2 and confidential level L3;

[0079] S12: setting the genetic marker bit according to the data theme type, the genetic marker bit being a Boolean type identifier , the expression of which is: ;

[0080] wherein, is a genetic marker, and when the Boolean value is 1, it represents true, and 0 represents false; the cross-department strong association type includes household registration, social security, or tax; the department exclusive type includes internal approval records or temporary statistical reports; the above steps set clear security levels and genetic properties by combining data source departments and theme types in the initial stage of data warehousing, not only guaranteeing the hierarchical management and inheritance control mechanism of government data, but also providing a structured basis for subsequent dynamic permission control and label superposition.

[0081] S2 specifically includes:

[0082] S21: generating an initial query condition according to the request department function code and the business scenario code, and initiating a data query request to the government database through a database query engine;

[0083] S22: returning a raw data set meeting the query condition from the government database, and temporarily storing the raw data set in a temporary cache area;

[0084] S23: retrieving a field-level permission control rule matched with the request department function code and the business scenario code from the permission control strategy library, and defining the read-write permission of each field in the permission control rule;

[0085] S24: traversing the raw data set in the temporary cache area, generating a readable or writable permission mark for each field according to the field-level permission control rule obtained in S23, and the permission mark is represented in the form of a binary tuple:

[0086] wherein, is the permission mark of the field; is the read permission of the field, and the value is a Boolean value, 1 representing readable and 0 representing unreadable; is the write permission of the field, and the value is a Boolean value, 1 representing writable and 0 representing unwritable;

[0087] S25: integrating the processed raw data set and the corresponding field permission mark to form a dynamic data view, and passing the dynamic data view to the subsequent step for use; the above steps generate dynamic permission marks by accurately matching department functions and business scenarios, realize fine and scenario-based permission control of government data, effectively prevent unauthorized access and unauthorized modification of data, and significantly enhance data security and management efficiency.

[0088] S23 specifically includes:

[0089] S231: Based on the request department function code and the business scenario code, the permission policy query key is generated by combination, and the generation method of the permission policy query key is to splice the department function code and the business scenario code in a predetermined order, and the expression is: , wherein, is the permission policy query key; is the department function code of the requesting department; is the current business scenario code; is the string splicing operator;

[0090] S232: Using the permission policy query key , the permission control policy library is retrieved in a key-value matching manner to obtain the corresponding permission control rule index;

[0091] S233: According to the permission control rule index, the field-level permission control rule record in the permission control policy library is located, the read permission value and the write permission value of each data field defined in the record are loaded, and the permission control rule is formed; the above-mentioned step quickly and accurately retrieves the permission control rule through the explicit key-value index mechanism, effectively improves the accuracy and response efficiency of the government data access permission management, and avoids the data security risk caused by permission mismatch.

[0092] Table 1: Permission control policy library example

[0093]

[0094] In the above table 1, the policy ID is a unique identifier for each group of permission policy rules, which is used for internal indexing; the department function code indicates the requesting department function code applicable to the permission policy; the business scenario code indicates the specific business use scenario corresponding to the permission policy; the field name is an identifier of the controlled data field in the government database; the readable permission indicates whether the field can be read by the current department in the current business scenario, 1 indicating readable and 0 indicating unreadable; the writable permission indicates whether the field can be written by the current department in the current business scenario, 1 indicating writable and 0 indicating unwritable.

[0095] S3 specifically includes:

[0096] S31: Obtain the unique data source address identifier of each government data source from the pre-configured government database registry;

[0097] S32: According to the function code of the department to which each data source belongs and the serviceable business scenario code, the routing key is formed by combination and splicing in a predefined order, and the specific expression is: , wherein, represents the generated routing key; represents the department function code corresponding to the data source; a code representing a business scenario applicable to the data source; a code representing a string concatenation operation;

[0098] S33: According to the routing key generated in S32, it is one by one mapped with the corresponding data source address identifier, and a key-value pair mapping relationship table is generated with the routing key as the retrieval index and the data source address as the mapping result;

[0099] S34: The key-value pair mapping relationship table generated in S33 is stored in the cloud configuration center, so as to quickly retrieve the target data source in subsequent data request operations; the above steps significantly improve the efficiency of data request positioning data source, simplify the data access path, and guarantee the timeliness and accuracy of data interaction through the explicit data source and routing key mapping relationship table.

[0100] Table 2 Key-value pair mapping relationship table

[0101]

[0102] In the above table 2, the routing key is a unique identification string spliced by the department function code and the business scenario code, which is used as the retrieval key for querying the data source address; the department function code is the department responsibility type code for identifying the initiator of the data request; the business scenario code is the business processing scenario code for identifying the current data access; the data source address represents the cloud database access address or API endpoint for identifying the actual storage of government data, which is the target path for actual data pulling.

[0103] S4 specifically includes:

[0104] S41: Receiving the data access request submitted by the request party through the government service interface, including the request party department identity authentication credentials, business call context information and data target parameters;

[0105] S42: Analyzing the identity authentication credentials submitted by the request party, combining with the unified identity authentication platform verification result, extracting the department function code after authentication;

[0106] S43: Extracting the business scenario code from the business call context information, including the current operation type, the government process node or the triggering method, which is used to identify the business processing scenario to which the request belongs;

[0107] S44: Extracting the target data identifier from the data target parameter set, including the data table number, the data object primary key or the label attribute, which is used to uniquely identify the data unit accessed by this request;

[0108] S45: The extracted department function code, business scenario code and target data identifier are used as structured request meta-information, and are passed to subsequent steps for routing and permission processing; the above steps realize structured identification and standard extraction of the request party data access target by combining the identity authentication platform, business context information and request parameter set, ensure the source is credible, the scene is clear, the target is controllable in the data access process, and improve the security and accuracy of system data processing.

[0109] S5 specifically includes:

[0110] S51: The department function code and the business scenario code obtained in S4 are combined into a request routing key according to a predetermined splicing order, and the request routing key is used as an index key to query the routing key and data source address mapping relationship table generated in S3 to determine the target data source address;

[0111] S52: A data connection channel is established according to the target data source address, and raw data is read from the target data source based on the target data identifier provided in S4;

[0112] S53: The raw data obtained from the target data source is loaded into the dynamic data view generated in S2, and the read and write permissions of sensitive fields are identified according to the permission marks corresponding to each field;

[0113] S54: For the sensitive fields identified as only readable or unreadable in S53, corresponding desensitization processing is performed according to the predefined desensitization strategy to obtain a desensitized data view;

[0114] S55: The desensitized data view is output for the request party to access, so as to ensure that the data access meets the department permission requirements and the security policy requirements; the above steps realize the safe transmission and accurate access control of sensitive government data through clear routing positioning and accurate desensitization processing based on permission marks, significantly reduce the risk of sensitive information leakage, and improve the security and compliance of government information.

[0115] S54 specifically includes:

[0116] S541: Traverse the dynamic data view in S53, check the permission marks of each sensitive field one by one, filter out the sensitive fields with read permission mark 0 or write permission mark 0 in the permission mark, and mark them as desensitization fields;

[0117] S542: According to the field type and permission mark of the desensitization field, the corresponding desensitization rule is retrieved from the predefined desensitization strategy library, including the replacement mode, the length of the intercepted field value or the mask format;

[0118] Specifically, if the desensitization rule is mask replacement, the field value is replaced according to the predefined mask format, and the mask replacement rule is represented as: ; wherein, is the field mask after desensitization; is the mask character; is the original length of the field value;

[0119] If the desensitization rule is character truncation, the field value is truncated by fixed length, and the truncation rule is represented as: , wherein, is the field value after desensitization; is the original field value; is the length of the reserved character after truncation;

[0120] If the desensitization rule is null value replacement, the field value is directly replaced with a null value;

[0121] S543: update the field value after desensitization to the dynamic data view, complete the desensitization operation; the above steps implement accurate processing of sensitive data by fine execution of corresponding desensitization strategies for different permission scenarios, prevent unauthorized information leakage, and improve the security and privacy protection level in the process of accessing government data.

[0122] S6 specifically includes:

[0123] S61: when a new department performs a data write operation on the government database, the department secret level corresponding to the new department is obtained as the initial secret level of the current data write operation;

[0124] S62: judge the value of the genetic marker bit in the original sensitivity label of the data to be written; if the value of the genetic marker bit is true, go to the next step, otherwise directly take the new department secret level as the final secret level of the new sensitivity label;

[0125] S63: if the genetic marker bit is true, extract the data secret level in the original data label, compare it with the current department secret level, and sort them in order from high to low according to the sensitivity level;

[0126] S64: select the highest secret level from the S63 sorting result as the final secret level of the superimposed new sensitivity label;

[0127] S65: based on the final secret level determined by S64, update the sensitivity label of the data, and complete the data write operation; the above steps effectively ensure the continuity and accuracy of the sensitivity label of government data in the process of circulation by clearly judging the genetic properties of the original label and reasonably superimposing the department secret level, avoid improper downgrading of data, and improve the security and standardization in the process of data sharing.

[0128] S63 specifically includes:

[0129] S631: respectively acquire the secret level value of the current writing department and the secret level value in the original data label from the sensitivity level enumeration set;

[0130] S632: based on the pre-defined sensitivity level value mapping table, convert the acquired secret level to the corresponding level value, specifically, the public level L1 corresponds to the level value 1, the internal level L2 corresponds to the level value 2, and the confidential level L3 corresponds to the level value 3;

[0131] S633: according to the two level values obtained in S632, compare the numerical values, and determine the level with the larger value as the secret level value of the new label;

[0132] S634: the level value determined in S633 is reversely mapped back to the corresponding sensitivity level enumeration as the final secret level of the new sensitivity label; the above steps realize the inheritance and reasonable superposition of the data secret level through the numerical secret level comparison, guarantee the continuity and safety of the sensitivity in the data flow process, and prevent the sensitivity degradation risk of the data.

[0133] The present application encompasses any substitution, modification, equivalent method and scheme made on the essence and scope of the present application. In order to make the public have a thorough understanding of the present application, specific details are described in the following preferred embodiments of the present application, and the present application can also be fully understood without the description of these details to those skilled in the art. In addition, in order to avoid unnecessary confusion to the essence of the present application, well-known methods, processes, procedures, elements and circuits are not described in detail.

[0134] The above is only the preferred embodiment of the present application, and it should be pointed out that for ordinary skilled in the art, without departing from the principle of the present application, a number of improvements and refinements can be made, and these improvements and refinements should be regarded as the protection scope of the present application.

Claims

1. A cloud-based government information management method, characterized by, The method comprises the following steps: S1: adding a sensitivity label to each piece of government data in a cloud storage layer, the sensitivity label comprising a data confidentiality level and a genetic marker bit; The S1 specifically comprises: S11: when the government data is first stored in the cloud storage layer, an initial data confidentiality level is determined by the data source department, the initial data confidentiality level being selected from a predefined confidentiality level enumeration set, comprising a public level L1, an internal level L2, and a confidential level L3; S12: setting a genetic mark bit according to a data subject type, the genetic mark bit being a Boolean type identifier The expression is: ； wherein, is a genetic marker bit, where a Boolean value of 1 indicates true and 0 indicates false; S2: extracting data from a government database and generating a dynamic data view with permission markers according to the department function code and the current business scenario code of the requesting department; S3: combining the department function code and the business scenario code into a routing key, and establishing a mapping relationship table of the routing key and the data source address; S4: obtaining the department function code, the business scenario code, and the target data identifier of the requesting party; S5: querying the mapping relationship table of S3 according to the department function code and the business scenario code of S4 to match the target data source; while reading data from the target data source, performing desensitization operations on sensitive fields based on the permission markers in the dynamic data view generated in S2; S6: when the data is written by a new department, a new sensitivity label is generated according to the confidentiality level of the writing department, and if the genetic marker bit of the original data is true, the data confidentiality level in the original label and the current confidentiality level are superimposed to form a new label.

2. The cloud-based government information management method of claim 1, wherein, The S2 specifically comprises: S21: generating an initial query condition according to the department function code and the business scenario code of the requesting department, and initiating a data query request to the government database through a database query engine; S22: returning a set of original data satisfying the query condition from the government database, and temporarily storing the set of original data in a temporary cache area; S23: retrieving a field-level permission control rule matching the department function code and the business scenario code of the requesting department from a permission control policy library, the permission control rule defining the read and write permissions of each field; S24: traversing the set of original data in the temporary cache area, and generating a readable or writable permission marker for each field according to the field-level permission control rule obtained in S23; S25: integrating the set of original data processed and the permission markers of the corresponding fields to form a dynamic data view.

3. The cloud-based government information management method of claim 2, wherein, The S23 specifically comprises: S231: Based on the request department function code and the business scenario code, the permission policy query key is combined and generated, and the expression is: Wherein, K is the permission policy query key; D is the department function code of the request department; B is the current business scenario code; is a string concatenation operator; S232: using a permission policy query key K to retrieve the permission control policy library in a key-value matching manner to obtain a corresponding permission control rule index; S233: locating to the field-level permission control rule record in the permission control policy library according to the permission control rule index, loading the read and write permission values of each data field defined in the record, and forming the permission control rule.

4. The cloud-based government information management method of claim 1, wherein, The S3 specifically comprises: S31: obtaining the unique data source address identifier of each government data source from a preconfigured government database registry; S32: According to the function code of the department to which each data source belongs and the serviceable business scenario code, combine and splice in a predefined order to form a routing key, and the specific expression is: Wherein, represents the generated routing key; D represents the department function code corresponding to the data source; B represents the business scenario code applicable to the data source; represents the string splicing operation; S33: mapping the routing key generated in S32 with the corresponding data source address identifier one by one to generate a key-value pair mapping relationship table taking the routing key as the retrieval index and the data source address as the mapping result; S34: storing the key-value pair mapping relationship table generated in S33 to a cloud configuration center.

5. The cloud-based government information management method of claim 1, wherein, The S4 specifically comprises: S41: receiving a data access request submitted by a requestor through a government service interface, including requestor department identity authentication credentials, business call context information, and data target parameters; S42: analyzing the identity authentication credentials submitted by the requestor, combining the unified identity authentication platform verification result, and extracting the department function code after authentication; S43: extracting the business scenario code from the business call context information, including the current operation type, the government process node or the triggering method; S44: extracting the target data identifier from the data target parameter set, including the data table number, the data object primary key or the label attribute; S45: using the extracted department function code, business scenario code and target data identifier as structured request meta information for standby.

6. The cloud-based government information management method of claim 1, wherein, The S5 specifically includes: S51: combining the department function code and the business scenario code obtained in S4 into a request routing key according to a predetermined splicing order, and using the request routing key as an index key to query the routing key and data source address mapping relationship table generated in S3 to determine the target data source address; S52: establishing a data connection channel according to the target data source address, and reading the original data from the target data source based on the target data identifier provided in S4; S53: loading the original data obtained from the target data source into the dynamic data view generated in S2, and identifying the read-write permissions of sensitive fields according to the permission marks corresponding to each field in the dynamic data view; S54: performing corresponding desensitization processing on the sensitive fields identified as only readable or not readable in S53 according to the predefined desensitization strategy to obtain a desensitized data view; S55: outputting the desensitized data view for the requestor to access.

7. The cloud-based government information management method of claim 6, wherein, The S54 specifically includes: S541: traversing the dynamic data view in S53, checking each sensitive field permission mark one by one, filtering out the sensitive fields with read permission mark 0 or write permission mark 0 in the permission mark, and marking them as desensitization fields; S542: retrieving the corresponding desensitization rules from the predefined desensitization strategy library according to the field type and permission mark of the desensitization field, including the replacement method, the length of the intercepted data, or the mask format of the defined field value; Specifically, if the desensitization rule is mask replacement, the field value is replaced according to the predefined mask format; If the desensitization rule is character truncation, the field value is truncated to a fixed length; If the desensitization rule is null value replacement, the field value is directly replaced by null value; S543: updating the field value after desensitization to the dynamic data view to complete the desensitization operation.

8. The cloud-based government information management method of claim 1, wherein, The S6 specifically includes: S61: when a new department performs a data write operation on the government database, obtaining the department secret level corresponding to the new department as the initial secret level of the current data write operation; S62: judging the value of the genetic marker bit in the original sensitivity label of the data to be written; if the value of the genetic marker bit is true, proceed to the next step, otherwise directly use the new department secret level as the final secret level of the new sensitivity label; S63: if the genetic marker bit is true, extract the data secret level in the original data label, compare it with the current department secret level, and sort them in order from high to low according to the sensitivity level. S64: selecting the highest confidentiality level from the sorting result of S63 as the final confidentiality level of the new sensitivity label after superposition; S65: updating the sensitivity label of the data based on the final confidentiality level determined in S64, and completing the data writing operation.

9. The cloud-based government information management method of claim 8, wherein, The S63 specifically includes: S631: obtaining the confidentiality level value of the current writing department and the confidentiality level value in the original data label from the sensitivity level enumeration set respectively; S632: converting the obtained confidentiality level to the corresponding level value based on the pre-defined sensitivity level value mapping table, specifically, the public level L1 corresponds to the level value 1, the internal level L2 corresponds to the level value 2, and the confidential level L3 corresponds to the level value 3; S633: comparing the two level values obtained in S632 according to the number value, and determining the level with the larger number value as the confidentiality level value of the new label; S634: reversely mapping the level value determined in S633 back to the corresponding sensitivity level enumeration as the final confidentiality level of the new sensitivity label.

Images