Oracle Database Security Strategy http://www.fanqiang.com (2001-05-14 03:28:00)
Database security issues have always been the nightmare of database administrators, the loss of database data and the intrusion of database data, which makes the database administrator are exhausted. This article puts some security strategies around the security issues of the database, I hope to help the database administrator and no longer night. Database security issues should include two parts: First, the security it should be able to ensure that when the database data storage medium is broken when the database data storage medium is broken, the database data information is not lost when the database data storage medium is broken and when the database user is wrong. Second, the database system is not invaded by illegal users to block the potential various vulnerabilities as much as possible to prevent illegal users from using them to invade the database system. For security issues for database data, the database administrator can refer to the data on the system dual-standing hot backup function and database backup and recovery. The following is further elaborated on the database system from invading this issue by illegal users. Group and Security: Creating a user group under the operating system is an effective way to ensure database security. Oracle program is generally divided into two categories for security purposes: all users can execute, and another class only DBA can be executed. The configuration files set in the UNIX environment are / etc / group, about how this file is configured, see the relevant manuals for UNIX, the following is a few ways to ensure security: (1) Creating Database Management before installing Oracle Server Corporate group (DBA) and assign the user ID of the root and Oracle software owner to this group. The program that DBA can perform only 710 permissions. SQL * DBA system permission commands are automatically assigned to the DBA group during installation. (2) Allow a portion of the UNIX users to restrict access to the Oracle server system, add a group of Oracle groups from authorized user groups to ensure that the Oracle Server utility example Oracle group ID, the public executable, such as SQL * Plus, SQL * FO RMS, etc., should be executed by this group, then the permissions of this utility routine are 710, which will allow the same group of users to execute, while other users cannot. (3) Change the permissions of programs that do not affect database security are 711. Note: In our system, the default password for two users in the Oracle database in the Oracle database is Manager. For your database system security, we strongly recommend that you will drop the password of these two users, Type the following: ALTER USER SYS INDENTIFIED by password; alter user system indentified by password; where Password is for you The password set by the user. The security of the Oracle server utility: The following is a few suggestions that protect the Oracle server from illegal users: (1) Make sure the ownership of all programs in the $ oracle_home / bin directory is owned by Oracle software owners; (2) Give all user practical files (SQIPLUS, SQIFORMS, EXP, IMP, etc.) 711 power, enabling all users on the server to access the Oracle server; (3) Give all DBA utility routines (such as SQL * DBA) 700 permissions .
When the Oracle server and UNIX are access to the local server, you can use the security of the UNIX management server by mapping the role of the Oracle server under the operating system, which is adapted to local access. The format of the Oracle server role in UNIX is as follows: ORA_SID_ROLE [_DLA] where the SID is the Oracle_SID of your Oracle database; Role is the name of the role in the Oracle server; D (optional) means that this role is default; A (optional) ) Indicates that this role comes with a with admin option, you can only grant this role to other roles, and cannot be other users. The following is an example set in the / etc / group file: ORA_TEST_OSOPER_D: None: 1: Jim, Narry, Scott ORA_TEST_OSDBA_A: NONE: 3: Pat Ora_test_Role1: None: 4: Bob, Jane, Tom, Mary, Jim bin: None: 5: root, oracle, DBA root: None: 7: root phrase "ora_test_osoper_d" indicates the name of the name; the phrase "none" means the password of this group; the number 1 represents the ID of this group; next is the member of this group . The front two lines are examples of Oracle server roles, using Test as the name of the Oracle server role as SID, OSOPER, and OSDBA. Osoper is the default role assigned to the user, and OSDBA has a with admin option. In order to make these database roles, you must shutdown your database system, set the Oracle database parameter file inToRacle_sid.ora, the os_roles parameter is true, and then restart your database. If you want these characters with Connect Internal permissions, run ORAPWD to set a password for these roles. When you try Connect Internal, the password you typed indicates the permissions corresponding to the role. SQL * DBA command security: If you don't have a SQL * Plus application, you can also use SQL * DBA as SQL check-off commands that can only be assigned to Oracle software owners and DBA groups, because these commands are A special system permission is awarded. (1) STARTUP (2) SHUTDOWN (3) Connect Internal Database File Security: Oracle Software The owner of Oracle Software should be these database files ($ ORACLE_HOME / DBS / *. DBF) Settings the right limit of these files 0600: The user can be readwritten, the same group and other groups of privileges are not written. Oracle Software owners should have a directory containing database files, in order to increase security, it is recommended to recover readable permissions for these files to collaborate with other groups of users. Network Security: When processing network security, the following is a few questions to consider. (1) Use the password on the network to type the password by encryption or not encrypted, when you type a password with a password without encryption, it is likely to be intercepted by illegal users, resulting in destroying the system Safety.
(2) DBA permission control on the network You can control DBA permissions on the network in the following two ways: a set to reject remote DBA access; b Set special passwords to DBA through ORAPWD. Establishing a security policy: System Security Policy (1) Managing Database User Database Users are access to Oracle database information, so you should maintain the security of the management database user. According to the size of the database system and the workload required to manage database users, database security managers may just have a special user of CREATE, ALTER, or DROP database, or a group of users who have these permissions, should be noted. Only those who are worth trustworthy should have permission to manage database users. (2) User identity confirmation database users can confirm with the operating system, network service, or database, and the advantages of user identity authentication through the host operating system are: A users can connect into the database faster, more convenient to enter the database; The system is confirmed to confirm the user's identity: If the operating system is consistent with the database user information, Oracle does not need to store and manage usernames and passwords; C users enters database and operating system audit information. (3) Operating system security A database administrator must have operating system permissions for Create and Delete files; B General database users should not have CREATE or DELETE and database-related file operating system permissions; C If the operating system can be database users Assign roles, then security managers must have operating system permissions to modify the operating system account security zone. Data security strategy: The management of data should be based on the importance of data. If the data is not very important, then the data is securely relaxed. However, if the data is important, there should be a cautious security policy that uses it to maintain the effective control of data object access. User Security Policy: (1) General User's security A password security If the user is confirmed by the database through the database, it is recommended to use the password encryption to connect to the database. The setting method of this method is as follows: Set the ORA_ENCRYPT_LOGIN number in the client's Oracle.ini file; set the dbling_encypt_login parameter to TRUE in the server-side inToRaCle_sid.ora file. B Permission Management For databases that are many users, applications and data objects are rich in databases, you should make full use of the convenience of the "role" mechanism to effectively manage the permissions. For complex system environments, "role" can greatly simplify the management of rights. (2) Security of end users You must develop security policies for end users.
For example, for a large-scale database with many users, security managers can determine user group classification, create user roles for these user groups, and grant the required permissions and application roles to each user role, and assign users The corresponding user role. When dealing with special application requirements, security managers must also clearly grant some specific permissions to users. You can use the "role" to control the end user. Database Manager Security Policy: (1) Protecting the connection as a Sys and System users When the database is created, change the SYS and SYSTEM users with administrative privileges to prevent illegal users from accessing the database. When serving as SYS and SYSTEM users into the database, users have powerful permissions to modify the database in a variety of ways. (2) Contributors and database connections should only be brought into databases with administrators, without any restrictions on SYSDBA or Startup, Shutdown, and Recover or database objects (such as CREATE, DROP, and DELETE, etc.) Operation. (3) Using roles to manage application developers for managers privileges: (1) Application developers and their privilege database application developers are the only type of database that requires special permission groups to do their jobs user. Developers need system privileges such as Create Table, Create Procedure, however, in order to limit the developer's operation of the database, only some specific system privileges should be granted to developers. (2) Application developers' environment A program developers should not compete with end users; B use program developers from harming other application products for databases. (3) Free and Controlled Application Developers have two privileges: a Free Development application developer allows you to create new mode objects, including Table, INDEX, Procedure, Package, etc., which allows application developers to develop Independent on other objects of other objects. B Controlled Development Application Developers do not allow you to create a new mode object. All required Table, InDes Procedure, etc. are created by database managers, which guarantees that database managers fully control the use of data space and access database information. But sometimes application developers also need mixing of these two privileges. (4) Application developers' roles and permissions database security managers can create roles to manage the permission requirements of typical application developers. A CREATE system authority is often awarded to application developers to create his data objects. The B data object role is hardly granted to the role used by the application developer.
