MySQL access auditing method and system, storage medium and terminal

Abstract

The invention provides a MySQL access auditing method and system, a storage medium and a terminal. The MySQL access auditing method comprises the following steps: setting a connection information module so that the connection information module can be executed when a user is connected with a MySQL server, wherein the connection information module is used for recording connection log information ofthe user; acquiring the connection log information based on the connection information module; obtaining operation log information corresponding to the user operation; and performing behavior tracking based on the connection log information and the operation log information, and confirming the user to realize access auditing. On the basis of the connection information module provided by the MySQLcommunity edition, the binlog log information of the MySQL database is combined, so that the auditing function of the MySQL database can be realized; and the connection information module is only executed when the user is connected with the MySQL server, so that the performance of the MySQL database is not greatly influenced, and the performance loss of the MySQL database is very small when the auditing function is started.

Description

technical field [0001] The invention belongs to the field of database auditing, in particular to a method, system, storage medium and terminal for MySQL access auditing. Background technique [0002] MySQL has an enterprise edition and a community edition. If only from the perspective of learning, there is no essential difference between the two. Only when official commercial services are needed will there be a big difference. The community edition will add many new technical aspects that have not been strictly The characteristics of the test are to get feedback and corrections from the majority of community users. The source code of the community version is irregular, and many community users can supplement and correct it. The community version has not been stress tested and performance tested by various proprietary system platforms. There may be technical risks in the compatibility of the developed software and hardware systems. The community version can be regarded as the...

AI Technical Summary

Problems solved by technology

[0003] MySQL itself has provided a detailed SQL execution record - general binlog, but enabling it has the following disadvantages: no matter whether the SQL has grammatical errors or not, as long as it is executed, there will be records, resulting in a large amount of useless information being recorded, making it difficult to filter later; When the amount of SQL concurrency is large, the log records will have a certain impact on the disk, which will reduce the efficiency of the MySQL database; the log file is easy to expand rapidly, and if it is not handled properly, it will have a certain impact on the disk space

Since the key to auditing lies in DML statements, and all DML statements can be recorded through binlog, but currently only the connection ID that generated this record is recorded in binlog, which is not helpful for auditing

Some audit plug-ins are provided in the prior art to monitor the access status of the MySQL database in the production environment, monitor and record various operating behaviors on the MySQL database, and analyze the access to the MySQL database in real time and intelligently by analyzing network data. Various operations are recorded in the audit database for future query, analysis, and filtering to realize monitoring and auditing of user operations in the target database system, such as the audit plug-in and audit audit plug-in provided by oracle, but this audit function is only available to enterprises The existing MySQL database of the community edition does not have the auditing function, and the MySQL database of the enterprise edition will lose the performance of the database when the auditing function is enabled.

Images