Five points about database security

For telecom enterprises, database security is crucial. Imagine what will happen to the Recharge System? What will happen to system problems when mobile phone users query bills at the end of the month? The following are some experiences of database O & M personnel of a telecom enterprise in terms of database security, as well as the suggestions provided by the database security experts of Starling. I hope you can learn from them.

I. database version and component selection

1. the database uses a high, more stable database version, to avoid some bugs triggered business impact, such as a ORA-04031, caused the settlement system into the pool error, resulting in application link failure.

2. When creating a database, specify the Oracle components required for the production database, and select only the minimum component set that meets the requirements of the use environment.

Ii. Table Management

1. Backup tables, temporary tables, and standardized Mode Management.

2. Use an independent mode to store independent business objects.

3. Creating a backup or temporary object using DDL indicates that there is a risk in the change management and the change management needs to be strengthened.

4. In a schema, all tables are stored to complete a system or module. Tables of other purposes cannot be stored together in this schema.

5. store and manage temporary tables and backup tables in an independent schema to separate backup tables and temporary tables, and avoid space fragmentation and performance impact on business data storage, this effectively reduces the impact of data backup and cleanup operations on business operations.

3. user permission security

1. Remove unnecessary users from the database. For example, if Scott is an Oracle testing user, delete the user and related objects in the production environment or transfer the user to the testing environment.

2. for Oracle built-in users that have been LOCKED, we need to assess whether to use them in the production environment. If you do not need to use them, you can delete related components and users.

3. Strictly manage user roles to prevent excessive permission granting, revoke the resource roles of users, and create custom roles with stricter permission restrictions.

4. Revoke unnecessary roles from users.

Iv. Access Security

1. Standardize database management software and standardize and unify management software.

2. Check the security of all connected database programs to prevent database security risks caused by backdoors in applications connected to the database. You can use portal monitoring to log on to the database. Direct operations on the database are prohibited.

3. Standardize and unify the connected IP network segments, review permissions on a quarterly basis, and sort out the permissions of the system's IP addresses and users. Conducts security training for employees, enhances their system security concepts, and implements careful operations.

4. Check whether the database access host is a known user. Use a dedicated maintenance host to connect to the database. Do not use public dblink to directly operate the database. The system maintenance personnel received a complaint one day and found that there were fewer columns in a table. Fortunately, it was a Status column. They manually inserted the column and then looked for the cause, it is found that the application staff connected to the production database when using dblink to link the test database. This shows how important database security is.

5. Audit SYSDBA operations.

6. All queries and other actions on important business tables are audited.

V. Backup Security

1. establishes a backup mechanism, builds Backup management software such as NBU, DP, and DSG for critical business systems, and creates appropriate backup policies based on business conditions, system pressure, and database resources, in this unit, full backup is performed once a week during idle hours, with one additional backup per day, and the operating system has a crontab or the main directory that comes with tape backup.

2. for key business systems, you can use the current mainstream disaster tolerance software technologies such as Oracle Goldengate, DG, and Quest Shareplex. During peak business hours, for example, when the business of our system is busy, the CPU idle is 1% or 0% every day. At this time, it is necessary to consider using synchronous replication to create a slave machine and migrate the business during the accounting period to the slave database without affecting the business of the master database.

Venus star database security expert comments

The author thinks about database security comprehensively, including not only version management, database table management, permission restriction, but also security considerations for external access, it includes client program management, application system security check, Client IP control, and even DBAs and important operation audits and data backup. Of course, database security covers a wide range of areas. Other security measures such as intrusion prevention, access identity authentication, and data encryption should also be considered. If a security administrator takes these factors into account from the beginning of database construction, the risk of data leakage or tampering is greatly reduced.

Database risks mainly come from two aspects: one is external attacks and the other is illegal operations (intentionally or unintentionally) by internal personnel (Authorized personnel, that is, misoperations by authorized personnel. To eliminate the risks caused by such operations, in addition to strict permission control, the Operation Audit for High-Permission users is also very important. At the same time, we must back up data, in case of any problem, remedial measures can be taken.

It is worth noting that database security measures should take into account both performance impact and security effect. For example, many organizations purchase independent database Audit products rather than simply enabling their own database audit functions. In addition to meeting the requirements of third-party audits, they also aim to protect the database performance from being affected by the opening of their own audit modules.