Log auditing model determination method and device applied to data security auditing
By displaying log audit scenario information and automatically extracting target log data and detection models, the problems of large error, high cost and poor generality in the existing technology are solved, and efficient and accurate log audit model generation is achieved.
Patent Information
- Application Number
- CN202411157581.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-22
- Publication Date
- 2024-11-29
AI Technical Summary
The existing log audit method is based on a single-dimensional threshold strategy or manual setting, resulting in large errors, high costs, poor versatility, and low efficiency and accuracy.
By displaying log audit scenario information, extracting target log data and associated log data detection models, automatically generating log audit models, and pre-configuring a variety of log audit scenarios and detection models, users can operate automatically modeling in a simple way.
It improves the development cost and versatility of the log audit model, and improves the efficiency and accuracy of log audit.
Smart Images

Figure CN119046950A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of information technology, and in particular to a method and device for determining a log audit model applied to data security audit. Background Art
[0002] Processing various businesses based on Internet technology will accumulate a large amount of log data, such as interface interaction logs, business operation logs, database access logs, etc. These logs are of great significance to the security and stability of the system. Log auditing is to review and analyze the logs in the system or network to monitor, review and report potential abnormal behaviors or attacks. It can be seen that log auditing plays a vital role in the field of information technology.
[0003] At present, the log data of different dimensions are usually audited based on the threshold strategy of a single dimension, or a corresponding log audit model is developed for a specific log audit requirement to meet the log audit requirement.
[0004] However, the first log audit method usually sets the threshold based on manual experience, which has the problem of large log audit errors. The second log audit method has the problem of high log audit model development cost and poor versatility, which leads to low efficiency and poor accuracy of log audit work. Summary of the invention
[0005] The present invention provides a method and device for determining a log audit model applied to data security audit, so as to automatically model different log data sources and log audit scenarios through simple operations of users, thereby reducing the development cost of the log audit model and improving the efficiency and accuracy of the log audit.
[0006] In a first aspect, an embodiment of the present invention provides a method for determining a log audit model applied to data security auditing, the method comprising:
[0007] Upon receiving a log audit model generation request, display at least one log audit scenario information;
[0008] In response to a trigger operation for any log audit scenario information, target log data under at least one target field corresponding to the triggered log audit scenario information is extracted from a predetermined historical log data table, and at least one log data detection model information associated with the triggered log audit scenario information is displayed; wherein the historical log data table includes log data under at least one field;
[0009] In response to a triggering operation on any log data detection model information, a target log audit model is obtained based on the target log data and the triggered log data detection model information.
[0010] In a second aspect, an embodiment of the present invention further provides a log audit model determination device applied to data security audit, the device comprising:
[0011] An audit scenario information display module, used to display at least one log audit scenario information when receiving a log audit model generation request;
[0012] A model data determination module, configured to extract target log data under at least one target field corresponding to the triggered log audit scenario information from a predetermined historical log data table in response to a trigger operation for any log audit scenario information, and display at least one log data detection model information associated with the triggered log audit scenario information; wherein the historical log data table includes log data under at least one field;
[0013] The audit model determination module is used to obtain a target log audit model based on the target log data and the triggered log data detection model information in response to a trigger operation on any log data detection model information.
[0014] In a third aspect, an embodiment of the present invention further provides an electronic device, the electronic device comprising:
[0015] one or more processors;
[0016] a storage device for storing one or more programs,
[0017] When one or more programs are executed by one or more processors, the one or more processors implement a log audit model determination method for data security auditing as described in any of the embodiments of the present invention.
[0018] In a fourth aspect, an embodiment of the present invention further provides a storage medium comprising computer executable instructions, which, when executed by a computer processor, are used to execute a log audit model determination method for data security auditing as described in any of the embodiments of the present invention.
[0019] The technical solution of the embodiment of the present invention, in the case of receiving a log audit model generation request, displays at least one log audit scenario information, and then, in response to a trigger operation for any log audit scenario information, extracts target log data under at least one target field corresponding to the triggered log audit scenario information from a predetermined historical log data table, and displays at least one log data detection model information associated with the triggered log audit scenario information, wherein the historical log data table includes log data under at least one field, thereby, in response to a trigger operation for any log data detection model information, based on the target log data and the triggered log data detection model information, a target log audit model is obtained. The technical solution of the present invention pre-configures a variety of log audit scenarios and log data detection models for different log audit requirements, and can automatically model different log data sources and log audit scenarios through simple operations of the user, effectively improving the development cost of the log audit model, and having universality, thereby improving the efficiency and accuracy of the log audit. BRIEF DESCRIPTION OF THE DRAWINGS
[0020] In order to more clearly illustrate the technical solutions of the exemplary embodiments of the present invention, the following briefly introduces the drawings required to describe the embodiments. Obviously, the drawings introduced are only drawings of a part of the embodiments to be described in the present invention, rather than all the drawings. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.
[0021] Figure 1 A flow chart of a method for determining a log audit model for data security auditing provided by an embodiment of the present invention;
[0022] Figure 2 A schematic diagram of a display process of at least one log audit scenario information involved in an embodiment of the present invention;
[0023] Figure 3 A schematic diagram of a display process of at least one log data detection model information involved in an embodiment of the present invention;
[0024] Figure 4 A flow chart of another method for determining a log audit model for data security auditing provided by an embodiment of the present invention;
[0025] Figure 5 A schematic diagram of the structure of a log audit model determination device applied to data security auditing provided by an embodiment of the present invention;
[0026] Figure 6 The present invention is a schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION
[0027] The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the present invention, rather than to limit the present invention. It should also be noted that, for ease of description, only parts related to the present invention, rather than all structures, are shown in the accompanying drawings.
[0028] Embodiment 1
[0029] Figure 1 A flow chart of a method for determining a log audit model for data security auditing provided in an embodiment of the present invention is provided. This embodiment is applicable to situations where a log audit model needs to be generated. The method can be executed by a log audit model determination device for data security auditing. The device can be implemented in the form of software and / or hardware. The hardware can be an electronic device, such as a mobile terminal, a PC, or a server.
[0030] like Figure 1 As shown, the method for determining the log audit model applied to data security audit includes:
[0031] S110: When receiving a log audit model generation request, display at least one log audit scenario information.
[0032] The log audit model generation request is a request signal generated when a log audit model needs to be generated.
[0033] In this embodiment, different log audit scenarios correspond to different log audit requirements. For example, the log audit scenario may include a log audit scenario of a high-frequency operation exception audit type, or a log audit scenario of an unconventional time operation exception audit type. Each type may include multiple log audit scenarios for different audit subjects. Based on this, multiple log audit scenarios may be predefined. The log audit scenario information is the display information of different log audit scenarios in the user display page. The number of log audit scenario information may be one or more.
[0034] In the specific application process, the technical solution provided by this embodiment can be integrated into an application or a client page. Based on this, a log audit model generation request can be generated in the following two situations. The first is when the user triggers the start control of the application, a log audit model generation request is generated; the second is when the user triggers the start control of the client page, or triggers the link control of the client page, a log audit model generation request is generated. When a log audit model generation request is generated, the background can receive this log audit model generation request, thereby displaying at least one log audit scenario information in the user's display page.
[0035] For example, the present solution is integrated into an application program. For a schematic diagram of the display process of at least one log audit scenario information, see Figure 2 ,like Figure 2 The rectangular box in the user display screen in (A) represents the log audit model generation application (Applications, APP). When the user triggers the display icon of the APP, a log audit model generation request is generated. At this time, multiple log audit scenario information can be displayed in the user's display screen, such as Figure 2 As shown in (B), these log audit scenario information may include: log audit scenario information A1, log audit scenario information A2, log audit scenario information A3, ..., log audit scenario information AN.
[0036] S120. In response to a trigger operation for any log audit scenario information, extract target log data under at least one target field corresponding to the triggered log audit scenario information from a predetermined historical log data table, and display at least one log data detection model information associated with the triggered log audit scenario information.
[0037] The historical log data table is a summary table corresponding to the log data generated in the historical period, and the historical log data table includes log data under at least one field. For example, at least one field may include: the time of the operation, the resources and data involved, the type and result of the operation, the user account, the IP address, the interface call information, and other corresponding fields.
[0038] In this embodiment, fields corresponding to different log audit scenarios can be defined. If you want to obtain a log audit model corresponding to a log audit scenario, you need to first obtain the log data under the fields corresponding to the log audit scenario. These fields corresponding to the log audit scenario are the target fields. The log data content under the target field is the target log data.
[0039] Among them, the log data detection model is a model that can perform anomaly detection or classification on log data. For example, the log data detection model can be a data detection model based on statistics, such as a data detection model based on a box plot, a data detection model based on three standard deviations, etc.; the log data detection model can also be a machine learning classification model, such as an isolated random forest model, etc.
[0040] In this embodiment, a variety of different log audit scenarios may be predefined, and at least one log data detection model and a target field corresponding to each log audit scenario are defined for each log audit scenario. The definition process of these log audit scenarios, log data detection models, and target fields may specifically include:
[0041] (1) Based on the log audit type and at least one dimension of audit subject information, define at least one log audit scenario and record the scenario identifier of the log audit scenario.
[0042] In this embodiment, different log audit types correspond to different log audit purposes. For example, the log audit type may include an abnormal audit type for high-frequency operations and an abnormal audit type for operations during irregular time periods. The abnormal audit type for high-frequency operations mainly audits the frequency of a certain type of operation within a specific time period to determine whether there is an abnormal risk of high-frequency operations; the abnormal audit type for operations during irregular time periods mainly detects special operations that are different from most other operations within a specific time period to determine whether there are abnormal operations during irregular time periods, for example, within the set working hours, detects whether there are operations corresponding to non-working hours.
[0043] The audit subject information is used to indicate what kind of log data content is audited. For example, in the case of high-frequency operation abnormality audit, the interface call information, account number and / or IP address can be used as the audit subject information. The scenario identifier is the unique identification information corresponding to different log audit scenarios.
[0044] In this embodiment, for different log audit types, one or more log audit scenarios may be defined according to audit subject information of at least one dimension, and a unique scenario identification information may be allocated to each log audit scenario.
[0045] Exemplarily, the log audit scenario may include at least one of the interface high-frequency call audit scenario, account high-frequency operation audit scenario, and IP address high-frequency access audit scenario corresponding to the high-frequency operation abnormal audit type. The log audit scenario may also include at least one of the interface unconventional time call audit scenario, account unconventional time operation audit scenario, and IP address unconventional time access audit scenario corresponding to the unconventional time operation abnormal audit type.
[0046] In particular, when defining log audit scenarios, it can also be considered that different business modules correspond to different log audit scenarios, and different regional information corresponds to different log audit scenarios.
[0047] It should be noted that the log audit scenario in this embodiment can be abstracted from common audit scenarios in the industry, has a certain scope of reuse, and can be considered as a standardized scenario template.
[0048] (2) For each log audit scenario, determine the target field corresponding to the audit subject information, so that when a triggering operation on any log audit scenario information is detected, extract the target log data under the target field corresponding to the triggered log audit scenario information from a predetermined historical log data table.
[0049] In this embodiment, since different log audit scenarios can correspond to different audit subject information, and these audit subject information correspond to certain data columns or certain data rows in the log data table, the target field can understand the column header information or row header information corresponding to these data columns or data rows.
[0050] Specifically, corresponding target fields can be pre-defined for each log audit scenario. When the log audit scenario information corresponding to a log audit scenario is triggered, the target log data corresponding to the triggered log audit scenario information can be extracted from the predetermined historical log data table through these target fields.
[0051] (3) Determine at least one log data detection model that is adapted to the log audit scenario, and record the model identifier of the log data detection model.
[0052] The model identifier is the unique identification information corresponding to the log data detection model.
[0053] In this embodiment, one or more log data detection models that can realize the audit function can be determined for each log audit scenario, and the model identifier of each log data detection model is recorded. It should be noted that the log data detection model associated with each log audit scenario is verified and determined.
[0054] Based on the above exemplary embodiments, the log data detection model associated with the interface high-frequency call audit scenario may include at least one of a box plot-based data detection model, a three standard deviation-based data detection model, and / or an isolated random forest model.
[0055] (4) A mapping relationship is established between each scenario identifier and each corresponding model identifier, so that when a triggering operation on any log audit scenario information is detected, the log data detection model information corresponding to each log data detection model associated with the triggered log audit scenario is determined and displayed based on the mapping relationship and the scenario identifier corresponding to the triggered log audit scenario information.
[0056] In this embodiment, for each log audit scenario, a mapping relationship between the scenario identifier and the corresponding model identifiers can be constructed. When the log audit scenario information corresponding to a log audit scenario is triggered, the model identifiers corresponding to the triggered log audit scenario information can be determined based on the mapping relationship and the scenario identifier corresponding to the triggered log audit scenario information. Therefore, based on each model identifier, the log data detection model information corresponding to each log data detection model associated with the triggered log audit scenario can be displayed.
[0057] Specifically, the user can obtain the historical log data table of offline data types from the local storage space in advance, or obtain the historical log data table of online data types from the database system through the interface call information. When the user triggers a certain log audit scenario information, the target field corresponding to the triggered log audit scenario information is determined. Based on this, the specific implementation method of determining the target log data can include at least the following two methods. The first method is that the user selects the target log data corresponding to each target field from the historical log data table according to the target field; the second method is that the background matches the data content in the historical log data table according to the data expression format corresponding to the target field. For example, it can be implemented by regular expressions, and the background uses the matched data content as the target log data corresponding to each target field. When the user triggers a certain log audit scenario information, at this time, at least one log data detection model information associated with the triggered log audit scenario information can also be determined, so that each log data detection model information can be displayed in the user's display page.
[0058] For example, in Figure 2 Based on at least one log data detection model information display process diagram, see Figure 3 ,like Figure 3 In (A), the user triggers the log audit scenario information A1 in the display screen, such as Figure 3 As shown in (B), at this time, multiple log data detection model information associated with the log audit scenario information A1 can be displayed in the user's display screen, namely, log data detection model information B1, log data detection model information B2 and log data detection model information B3.
[0059] S130 . In response to a trigger operation on any log data detection model information, a target log audit model is obtained based on the target log data and the triggered log data detection model information.
[0060] Among them, the target log audit model is the final generated log audit model.
[0061] In this embodiment, when the user triggers any log data detection model information, at this time, the log data detection model corresponding to the triggered log data detection model information can be retrieved and loaded according to the triggered log data detection model information. Furthermore, if the log data detection model is a machine learning classification model, these target log data can be preprocessed first, and the preprocessing process can be implemented through multiple processing operators such as deduplication and interpolation, and then each log data in the target log data is processed into a target data feature that is compatible with the log data detection model. This processing process can be implemented through multiple processing operators such as feature conversion, aggregation and / or normalization. Furthermore, the log data detection model can be trained based on the target data features to optimize the model parameters of the log data detection model, and the target log audit model can be obtained after the model optimization is completed.
[0062] Based on the above embodiment, if the log data detection model is a statistical data detection model, the target log data can be input into the log data detection model to obtain a data processing report corresponding to the log data detection model, wherein the data processing report may include but is not limited to a modeling process report, an input data report, a model analysis result report, etc., so that the user can decide whether to determine this log data detection model as the target log audit model based on these data processing reports.
[0063] On the basis of obtaining the target log audit model, the files associated with the target log audit model can be saved, which may include: saving the model structure, saving the modeling features, saving the model parameters, etc., so that the target log audit model can be deployed locally or on other servers.
[0064] It should be noted that the acquisition, storage, use, and processing of data in the technical solution of this application are in compliance with the relevant provisions of national laws and regulations. For example, network requests are intercepted and processed with the authorization of the user.
[0065] The technical solution of the embodiment of the present invention, by displaying at least one log audit scenario information when receiving a log audit model generation request, and then, in response to a trigger operation for any log audit scenario information, extracting target log data under at least one target field corresponding to the triggered log audit scenario information from a predetermined historical log data table, and displaying at least one log data detection model information associated with the triggered log audit scenario information, wherein the historical log data table includes log data under at least one field, thereby, in response to a trigger operation for any log data detection model information, based on the target log data and the triggered log data detection model information, a target log audit model is obtained. The technical solution of the present invention pre-configures a variety of log audit scenarios and log data detection models for different log audit requirements, and can automatically model different log data sources and log audit scenarios through simple operations of the user, effectively improving the development cost of the log audit model, and having universality, thereby improving the efficiency and accuracy of the log audit.
[0066] Embodiment 2
[0067] Figure 4 This is a schematic diagram of a method for determining a log audit model for data security auditing provided by an embodiment of the present invention. Based on the above embodiment, S110-S130 are described in detail. The specific implementation method can refer to the technical solution of this embodiment. The technical terms that are the same or corresponding to the above embodiment are not repeated here.
[0068] like Figure 4 As shown, the method specifically comprises the following steps:
[0069] S210: Obtain a historical log data source table according to source data interface information and / or source data storage address information.
[0070] The source data interface information is the interface information corresponding to the online database. The source data storage address information is the storage location corresponding to the offline data table. The historical log data source table refers to the table format used to store and organize historical original log data.
[0071] In this embodiment, the historical log data source table can be obtained from an online database system, for example, the online database system can be an open source relational database management system (MySQL), a distributed document database (Elasticsearch, ES), etc.; the historical log data source table can also be obtained from an offline data storage unit. Specifically, the historical log data source table can be obtained from an online database system according to the source data interface information corresponding to the online database system; the historical log data source table can also be obtained from a storage unit according to the source data storage address information.
[0072] S220. Determine a target parser from at least one pre-configured parser based on the data format of the historical log data source table.
[0073] The parser is used to convert the data format in the historical log data source table to obtain log data in a unified format. In this embodiment, multiple parsers are pre-configured, and different parsers are used to parse and process data tables with different data formats. The target parser is a parser that is compatible with the data format of the historical log data source table.
[0074] In this embodiment, the data format of the historical log data source table can be an online database format, a csv data format, a json data format, etc. Different data formats need to be processed by different parsers, so the target parser can be determined from a plurality of pre-configured parsers according to the data format of the historical log data source table.
[0075] S230 , converting the data format of the historical log data source table based on the target parser to obtain a historical log data table in a standard data format.
[0076] In this embodiment, a target parser is used to convert the data format of the historical log data source table, so that the data content in the historical log data source table can be converted into a historical log data table in a standard data format, so that log data in various data formats can be effectively utilized.
[0077] S240: In response to a triggering operation on any log audit scenario information, display at least one log data detection model information associated with the triggered log audit scenario information.
[0078] S250: Extract target log data under at least one target field corresponding to the triggered log audit scenario information from a predetermined historical log data table.
[0079] In this embodiment, a specific implementation method of extracting target log data under at least one target field corresponding to the triggered log audit scenario information from a predetermined historical log data table may include:
[0080] (1) For each target field, obtain a preset regular expression corresponding to the current target field.
[0081] Among them, regular expressions are tools for describing, matching, and manipulating strings. They are patterns composed of a series of characters and special symbols, and are used to search and extract strings that meet a specific pattern in text. The basic idea is to define a pattern to describe a class of strings that meet certain rules. This pattern consists of common characters and special characters. Special characters are used to represent some specific characters or character sets.
[0082] In this embodiment, each log audit scenario can correspond to multiple target fields, and each target field can be configured with a corresponding preset regular expression. When a user triggers a certain log audit scenario information, the preset regular expressions corresponding to the triggered log audit scenario information can be obtained. Furthermore, the specific method of determining the target log data corresponding to each target field is consistent, and the current target field is used as an example for explanation.
[0083] (2) Perform data matching processing on the preset regular expression based on each field in the historical log data table to determine the matching result.
[0084] In this embodiment, each field in the historical log data table can be matched with the preset regular expression one by one. If a field matches the preset regular expression, the matching result is a hit; if a field does not match the preset regular expression, the matching result is a rejection.
[0085] (3) The data content corresponding to the field with the matching result being a hit is determined as the target log data corresponding to the current target field.
[0086] In this embodiment, the data content corresponding to the field with the matching result being a hit is the target log data corresponding to the current target field. Based on the same processing method, the target log data corresponding to each target field can be obtained. In this way, the target log data under each target field corresponding to the triggered log audit scenario information can be determined quickly and efficiently.
[0087] S260 . In response to a triggering operation on any log data detection model information, load a log data detection model corresponding to the triggered log data detection model information.
[0088] In this embodiment, when the user triggers any log data detection model information, the log data detection model corresponding to the triggered log data detection model information can be retrieved and loaded into the background.
[0089] Specifically, the log data detection model includes at least one machine learning classification model and / or at least one statistically based data detection model. If the retrieved log data detection model is a machine learning classification model, execute S270; if the retrieved log data detection model is a statistically based data detection model, execute S280.
[0090] S270. If the log data detection model is a machine learning classification model, the log data detection model is trained based on the target log data to adjust the model parameters of the log data detection model. After the model training is completed, the target log audit model is obtained.
[0091] In this embodiment, if the retrieved log data detection model is the initial model, the model parameters in the model need to be adjusted. Based on this, the log data detection model can be trained based on the target log data to optimize the model parameters of the log data detection model. After the model optimization is completed, the target log audit model can be obtained.
[0092] S280. If the log data detection model is a statistically based data detection model, determine the data processing report corresponding to the log data detection model based on the target log data and the log data detection model; and determine whether to determine the log data detection model as the target log audit model based on the data processing report.
[0093] In this embodiment, if the log data detection model is a statistical data detection model, the target log data can be input into the log data detection model to obtain a data processing report corresponding to the log data detection model. The user can decide whether to determine this log data detection model as the target log audit model based on these data processing reports.
[0094] The technical solution of the embodiment of the present invention can obtain the historical log data source table based on the source data interface information and / or the source data storage address information, thereby determining the target parser from at least one pre-configured parser based on the data format of the historical log data source table, and then, based on the target parser, converting the data format of the historical log data source table to obtain a historical log data table in a standard data format, which can effectively utilize log data in various data formats, thereby improving the versatility of the log audit model. Furthermore, by using regular expressions, the target log data under at least one target field corresponding to the triggered log audit scenario information can be extracted from the predetermined historical log data table, which can quickly and efficiently determine the target log data under each target field corresponding to the triggered log audit scenario information, further improving the development cost of the log audit model. Finally, in response to a trigger operation for any log data detection model information, the log data detection model corresponding to the triggered log data detection model information is loaded; if the log data detection model is a machine learning classification model, the log data detection model is trained based on the target log data to adjust the model parameters of the log data detection model. After the model training is completed, the target log audit model is obtained; if the log data detection model is a data detection model based on statistics, the data processing report corresponding to the log data detection model is determined based on the target log data and the log data detection model, so as to determine whether to determine the log data detection model as the target log audit model based on the data processing report. Through simple user operations, different log data sources and log audit scenarios can be automatically modeled, which effectively improves the development cost of the log audit model, thereby improving the efficiency and accuracy of the log audit.
[0095] Embodiment 3
[0096] Figure 5 A structural diagram of a log audit model determination device for data security auditing provided by an embodiment of the present invention, the device includes: an audit scenario information display module 310, a model data determination module 320 and an audit model determination module 330.
[0097] The audit scenario information display module 310 is used to display at least one log audit scenario information when receiving a log audit model generation request;
[0098] The model data determination module 320 is used to extract target log data under at least one target field corresponding to the triggered log audit scenario information from a predetermined historical log data table in response to a trigger operation for any log audit scenario information, and display at least one log data detection model information associated with the triggered log audit scenario information; wherein the historical log data table includes log data under at least one field;
[0099] The audit model determination module 330 is used to obtain a target log audit model based on the target log data and the triggered log data detection model information in response to a trigger operation on any log data detection model information.
[0100] Based on the above device, optionally, the log audit model determination device applied to data security audit further includes: a log data determination module; the log data determination module specifically includes:
[0101] A log data source acquisition unit, used to acquire a historical log data source table according to source data interface information and / or source data storage address information;
[0102] A parser matching unit, configured to determine a target parser from at least one pre-configured parser based on a data format of a historical log data source table;
[0103] The data format conversion module is used to convert the data format of the historical log data source table based on the target parser to obtain a historical log data table in a standard data format.
[0104] Based on the above device, optionally, the log audit model determination device applied to data security audit further includes: a scenario model configuration module; the scenario model configuration module specifically includes:
[0105] A scenario definition unit, used to define at least one log audit scenario according to the log audit type and the audit subject information of at least one dimension, and record the scenario identifier of the log audit scenario;
[0106] The target field definition unit is used to determine the target field corresponding to the audit subject information for each log audit scenario, so as to extract the target log data under the target field corresponding to the triggered log audit scenario information from the predetermined historical log data table when a triggering operation on any log audit scenario information is detected;
[0107] A model configuration unit, used to determine at least one log data detection model adapted to the log audit scenario, and record a model identifier of the log data detection model;
[0108] A mapping relationship determination unit is used to establish a mapping relationship between each scenario identifier and the corresponding model identifier, so that when a triggering operation on any log audit scenario information is detected, the log data detection model information corresponding to each log data detection model associated with the triggered log audit scenario is determined and displayed based on the mapping relationship and the scenario identifier corresponding to the triggered log audit scenario information.
[0109] Based on the above device, optionally, the log audit scenario includes at least one of a high-frequency operation abnormality audit scenario and an unconventional time operation abnormality audit scenario.
[0110] Based on the above device, optionally, the model data determination module 320 further includes: a log data extraction unit; the log data extraction unit specifically includes:
[0111] The regular expression acquisition subunit is used to acquire, for each target field, a preset regular expression corresponding to the current target field;
[0112] The regular expression matching subunit is used to perform data matching processing on the preset regular expression based on each field in the historical log data table to determine the matching result;
[0113] The log data determination subunit is used to determine the data content corresponding to the field with a hit matching result as the target log data corresponding to the current target field.
[0114] Based on the above device, optionally, the log data detection model includes at least one machine learning classification model and / or at least one statistically based data detection model, and the audit model determination module 330 specifically includes:
[0115] A detection model loading unit, configured to load a log data detection model corresponding to the triggered log data detection model information in response to a triggering operation on any log data detection model information;
[0116] The first audit model determination unit is used to perform model training on the log data detection model based on the target log data if the log data detection model is a machine learning classification model, so as to adjust the model parameters of the log data detection model, and obtain the target log audit model after the model training is completed;
[0117] The second audit model determination unit is used to determine the data processing report corresponding to the log data detection model based on the target log data and the log data detection model if the log data detection model is a statistically based data detection model; and determine whether to determine the log data detection model as the target log audit model based on the data processing report.
[0118] The technical solution of the embodiment of the present invention, by displaying at least one log audit scenario information when receiving a log audit model generation request, and then, in response to a trigger operation for any log audit scenario information, extracting target log data under at least one target field corresponding to the triggered log audit scenario information from a predetermined historical log data table, and displaying at least one log data detection model information associated with the triggered log audit scenario information, wherein the historical log data table includes log data under at least one field, thereby, in response to a trigger operation for any log data detection model information, based on the target log data and the triggered log data detection model information, a target log audit model is obtained. The technical solution of the present invention pre-configures a variety of log audit scenarios and log data detection models for different log audit requirements, and can automatically model different log data sources and log audit scenarios through simple operations of the user, effectively improving the development cost of the log audit model, and having universality, thereby improving the efficiency and accuracy of the log audit.
[0119] The device for determining a log audit model for data security audit provided by an embodiment of the present invention can execute the method for determining a log audit model for data security audit provided by any embodiment of the present invention, and has functional modules and beneficial effects corresponding to the execution method.
[0120] It is worth noting that the various units and modules included in the above system are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the protection scope of the embodiments of the present invention.
[0121] Embodiment 4
[0122] Figure 6 The present invention is a schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. Figure 6 A block diagram of an exemplary electronic device 40 suitable for implementing exemplary embodiments of the present invention is shown. Figure 6 The electronic device 40 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.
[0123] like Figure 6 As shown, the electronic device 40 is in the form of a general computing device. The components of the electronic device 40 may include but are not limited to: one or more processors or processing units 401, a system memory 402, and a bus 403 connecting different system components (including the system memory 402 and the processing unit 401).
[0124] Bus 403 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor or a local bus using any of a variety of bus structures. For example, these architectures include but are not limited to Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MAC) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus and Peripheral Component Interconnect (PCI) bus.
[0125] The electronic device 40 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by the electronic device 40, including volatile and non-volatile media, removable and non-removable media.
[0126] System memory 402 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 404 and / or cache memory 405. Electronic device 40 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, storage system 406 may be used to read and write non-removable, non-volatile magnetic media ( Figure 6 not shown, usually called a "hard drive"). Although Figure 6 Not shown in the figure, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk"), and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, a DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to bus 403 via one or more data medium interfaces. Memory 402 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of various embodiments of the present invention.
[0127] A program / utility 408 having a set (at least one) of program modules 407 may be stored, for example, in memory 402, such program modules 407 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment. Program modules 407 generally perform the functions and / or methods of the embodiments described herein.
[0128] The electronic device 40 may also communicate with one or more external devices 409 (e.g., keyboards, pointing devices, displays 810, etc.), may communicate with one or more devices that enable a user to interact with the electronic device 40, and / or may communicate with any device that enables the electronic device 40 to communicate with one or more other computing devices (e.g., a network card, a modem, etc.). Such communication may be performed via an input / output (I / O) interface 411. Furthermore, the electronic device 40 may also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) via a network adapter 412. As shown, the network adapter 412 communicates with other modules of the electronic device 40 via the bus 403. It should be understood that although Figure 6 Not shown, other hardware and / or software modules may be used in conjunction with the electronic device 40, including but not limited to microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.
[0129] The processing unit 401 executes various functional applications and page processing by running the programs stored in the system memory 402, for example, implementing the log audit model determination method for data security audit provided by the embodiment of the present invention.
[0130] Embodiment 5
[0131] An embodiment of the present invention further provides a storage medium containing computer executable instructions, which, when executed by a computer processor, is used to execute a log audit model determination method applied to data security auditing, the method comprising:
[0132] Upon receiving a log audit model generation request, display at least one log audit scenario information;
[0133] In response to a trigger operation for any log audit scenario information, target log data under at least one target field corresponding to the triggered log audit scenario information is extracted from a predetermined historical log data table, and at least one log data detection model information associated with the triggered log audit scenario information is displayed; wherein the historical log data table includes log data under at least one field;
[0134] In response to a trigger operation for any log data detection model information, a target log audit model is obtained based on the target log data and the triggered log data detection model information.
[0135] The computer storage medium of the embodiment of the present invention can adopt any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this document, a computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.
[0136] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, which carry computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.
[0137] Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
[0138] Computer program code for performing the operation of embodiments of the present invention may be written in one or more programming languages or a combination thereof, including object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as an independent software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).
[0139] Note that the above are only preferred embodiments of the present invention and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims
1. A method for determining a log audit model for data security auditing, characterized in that: include: Upon receiving a log audit model generation request, display at least one log audit scenario information; In response to a trigger operation for any log audit scenario information, target log data under at least one target field corresponding to the triggered log audit scenario information is extracted from a predetermined historical log data table, and at least one log data detection model information associated with the triggered log audit scenario information is displayed; wherein the historical log data table includes log data under at least one field; In response to a triggering operation on any log data detection model information, a target log audit model is obtained based on the target log data and the triggered log data detection model information.
2. The method according to claim 1, characterized in that The method further comprises: Obtain a historical log data source table based on source data interface information and / or source data storage address information; Based on the data format of the historical log data source table, determining a target parser from at least one pre-configured parser; The target parser performs data format conversion on the historical log data source table to obtain a historical log data table in a standard data format.
3. The method according to claim 1, characterized in that: The method further comprises: Defining at least one log audit scenario based on the log audit type and the audit subject information of at least one dimension, and recording the scenario identifier of the log audit scenario; For each of the log audit scenarios, a target field corresponding to the audit subject information is determined, so that when a triggering operation on any log audit scenario information is detected, target log data under the target field corresponding to the triggered log audit scenario information is extracted from a predetermined historical log data table; Determine at least one log data detection model adapted to the log audit scenario, and record a model identifier of the log data detection model; A mapping relationship is established between each of the scenario identifiers and the corresponding model identifiers, so that when a triggering operation on any log audit scenario information is detected, the log data detection model information corresponding to each of the log data detection models associated with the triggered log audit scenario is determined and displayed based on the mapping relationship and the scenario identifier corresponding to the triggered log audit scenario information.
4. The method according to claim 3, characterized in that The log audit scenario includes at least one of a high-frequency operation exception audit type and an unconventional time operation exception audit type.
5. The method according to claim 1, characterized in that The step of extracting target log data under at least one target field corresponding to the triggered log audit scenario information from a predetermined historical log data table includes: For each of the target fields, obtaining a preset regular expression corresponding to the current target field; Performing data matching processing on the preset regular expression based on each field in the historical log data table to determine a matching result; The data content corresponding to the field with the matching result as a hit is determined as the target log data corresponding to the current target field.
6. The method according to claim 1, characterized in that The log data detection model includes at least one machine learning classification model and / or at least one statistically based data detection model, and the response to the trigger operation for any log data detection model information is based on the target log data and the triggered log data detection model information to obtain the target log audit model, including: In response to a triggering operation on any log data detection model information, loading a log data detection model corresponding to the triggered log data detection model information; If the log data detection model is a machine learning classification model, model training is performed on the log data detection model based on the target log data to adjust the model parameters of the log data detection model. After the model training is completed, the target log audit model is obtained.
7. The method according to claim 6, characterized in that The method further comprises: If the log data detection model is a data detection model based on statistics, then based on the target log data and the log data detection model, determining a data processing report corresponding to the log data detection model; Based on the data processing report, it is determined whether to determine the log data detection model as a target log audit model.
8. A log audit model determination device applied to data security audit, characterized in that: include: An audit scenario information display module, used to display at least one log audit scenario information when receiving a log audit model generation request; A model data determination module, configured to extract target log data under at least one target field corresponding to the triggered log audit scenario information from a predetermined historical log data table in response to a trigger operation for any log audit scenario information, and display at least one log data detection model information associated with the triggered log audit scenario information; wherein the historical log data table includes log data under at least one field; The audit model determination module is used to obtain a target log audit model based on the target log data and the triggered log data detection model information in response to a trigger operation on any log data detection model information.
9. An electronic device, characterized in that: The electronic device comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the log audit model determination method applied to data security auditing described in any one of claims 1-7.
10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the log audit model determination method for data security auditing described in any one of claims 1 to 7 when executed.
Citation Information
Cited By
Method and device for determining auditing model and electronic equipment
CN114662822A
Method, device and electronic device for determining audit model
CN114662822B
Method and device for detecting illegal external connection of terminal and storage medium
CN119316226A
