1. System level
The system level needs to pay attention to the following aspects:
1. User management. Different users have different permissions. You can set users with only read permissions and read-write permissions as needed. Special users (similar to the root user under Linux) can start and stop the system. Read-write users are mainly used for daily operations. maintenance work.
2. File management. That is, some important files require special protection, which needs to be implemented in cooperation with the user.
3. Password management. Passwords need to be changed regularly, and too many attempts cannot be made, otherwise the password will be frozen.
4. System log. The importance of system logs to the system is self-evident, and many problems can be solved through logs.
2. Database level
Every DBRM system has security control functions. The principle of permission allocation is role-based permission control: grant different permissions to different roles, assign different users to different groups, and finally assign different roles to different groups. This should be a more common approach.
3. Third-party database audit products
The database itself has the audit function. The reason why it is abandoned is that its performance has a greater impact on the system. , so we chose third-party products. Database audit products can audit database behaviors such as select and update. If abnormal behavior is found in the database, relevant information can be found through this product.
In fact, the current problems facing database security are largely not external factors, but that some users see or modify data beyond their permissions, that is, user information is leaked. This is worthy of attention. The method we adopt is to clearly define rights and responsibilities: the permissions of application personnel and operation and maintenance personnel are separated, and permissions are controlled from the two dimensions of system and application, and are gradually refined from the above three levels.
On the whole, database security does not have much new ideas. I have not found any serious security problems in two years of work. Despite this, we still have a response plan. The idea is to start with the system logs, then locate the user, and find the user's related behaviors through the user to locate the real problem.
The above is the detailed content of What are the three levels of database security?. For more information, please follow other related articles on the PHP Chinese website!