《Oracle数据库安全》PPT课件.ppt

Implementing Oracle Database Security,Objectives,After completing this lesson, you should be able to do the following: Describe your DBA responsibilities for security Implement security by applying the principle of least privilege Manage default user accounts Implement standard password security features Describe database auditing Describe Virtual Private Database (VPD),Industry Security Requirements,Legal: Sarbanes-Oxley Act (SOX) Health Information Portability and Accountability Act (HIPAA) California Breach Law UK Data Protection Act Auditing,Security Requirements Full Notes Page,Separation of Responsibilities,Users with DBA privileges must be trusted. Consider: Abuse of trust Audit trails protect the trusted position. DBA responsibilities must be shared. Accounts must never be shared. The DBA and the system administrator must be different people. Separate operator and DBA responsibilities.,Database Security,A secure system ensures the confidentiality of the data that it contains. There are several aspects of security: Restricting access to data and services Authenticating users Monitoring for suspicious activity,Database Security Full Notes Page,Principle of Least Privilege,Install only required software on the machine. Activate only required services on the machine. Give OS and database access to only those users that require access. Limit access to the root or administrator account. Limit access to the SYSDBA and SYSOPER accounts. Limit users access to only the database objects required to do their jobs.,REVOKE EXECUTE ON UTL_SMTP, UTL_TCP, UTL_HTTP, UTL_FILE FROM PUBLIC;,O7_DICTIONARY_ACCESSIBILITY=FALSE,REMOTE_OS_AUTHENT=FALSE,Applying the Principle of Least Privilege,Protect the data dictionary: Revoke unnecessary privileges from PUBLIC: Restrict the directories accessible by users. Limit users with administrative privileges. Restrict remote database authentication:,Apply the Principle of Least Privilege Full Notes Page,Managing Default User Accounts,DBCA expires and locks all accounts, except: SYS SYSTEM SYSMAN DBSNMP For a manually created database, lock and expire any unused accounts.,User,Password aging and expiration,Password complexity verification,Setting up profiles,Implementing Standard Password Security Features,Password history,Account locking,Password Security Full Notes Page,Supplied Password Verification Function: VERIFY_FUNCTION,The supplied password verification function enforces these password restrictions: The minimum length is four characters. The password cannot be the same as the username. The password must have at least one alphabetic, one numeric, and one special character. The password must differ from the previous password by at least three letters. Tip: Use this function as a template to create your own customized password verification.,Creating a Password Profile,Assigning Users to a Password Profile,Select Administration Schema Users & Privileges Users.,Where We Are,Comparing security aspects Applying the principle of least privilege Managing default user accounts Implementing standard password security features Creating and using password profiles Auditing Virtual Private Database (VPD),Monitoring for Suspicious Activity,Monitoring or auditing must be an integral part of your security procedures. Review the following: Mandatory auditing Standard database auditing Value-based auditing Fine-grained auditing (FGA) DBA auditing,Enterprise Manager Audit Page,Audit trail,Parameter file,(2) Specify audit options.,Generate audit trail.,(3) Review audit information. (4) Maintain audit trail.,Standard Database Auditing,DBA,User,Enable database auditing.,executes command.,Database,OS or XML audit trail,Audit options,Server process,Uniform Audit Trails,DBA_AUDIT_TRAIL,DBA_FGA_AUDIT_TRAIL,DBA_COMMON_AUDIT_TRAIL,EXTENDED_TIMESTAMP, PROXY_SESSIONID, GLOBAL_UID, INSTANCE_NUMBER, OS_PROCESS, TRANSACTIONID, SCN, SQL_BIND, SQL_TEXT,STATEMENTID, ENTRYID,AUDIT_TRAIL=DB,EXTENDED,Enhanced Enterprise User Auditing,Standard audit USERNAME GLOBAL_UID,Fine-grained audit DB_USER GLOBAL_UID,Standard audit USERNAME,Fine-grained audit DB_USER,Exclusive schema,Shared schema,Value-Based Auditing,Users change is made.,Trigger fires.,Audit record is created by the trigger.,And it is inserted into an audit trail table.,A user makes a change.,Value-Based Auditing Full Notes Page,Fine-Grained Auditing,Monitors data access on the basis of content Audits SELECT, INSERT, UPDATE, DELETE, and MERGE Can be linked to a table or view, to one or more columns May fire a procedure Is administered with the DBMS_FGA package,employees,Policy: AUDIT_EMPS_SALARY,SELECT name, salary FROM employees WHERE department_id = 10;,FGA Policy,dbms_fga.add_policy ( object_schema = HR, object_name = EMPLOYEES, policy_name = audit_emps_salary, audit_condition= department_id=10, audit_column = SALARY, handler_schema = secure, handler_module = log_emps_salary, enable = TRUE, statement_types = SELECT );,SELECT name, job_id FROM employees;,SELECT name, salary FROM employees WHERE department_id = 10;,SECURE.LOG_ EMPS_SALARY,employees,Defines: Audit criteria Audit action Is created with DBMS_FGA .ADD_POLICY,FGA Policy Full Notes Page,Audited DML Statement: Considerations,Records are audited if FGA predicate is satisfied and relevant columns are referenced. DELETE statements are audited regardless of any specified columns. MERGE statements are audited with the underlying INSERT or UPDATE generated statements.,UPDATE hr.employees SET salary = 10 WHERE commission_pct = 90;,UPDATE hr.employees SET salary = 10 WHERE employee_id = 111;,FGA Guidelines,To audit all statements, use a null condition. Policy names must be unique. The audited table or view must already exist when you create the policy. If the audit condition syntax is invalid, an ORA-28112 error is raised when the audited object is accessed. If the audited column does not exist in the table, no rows are audited. If the event handler does not exist, no error is returned and the audit record is still created.,DBA Auditing,Users with the SYSDBA or SYSOPER privileges can connect when the database is closed: Audit trail must be stored outside the database. Connecting as SYSDBA or SYSOPER is always audited. Enable additional auditing of SYSDBA or SYSOPER actions with audit_sys_operations. Control audit trail with audit_file_dest.,Maintaining the Audit Trail,The audit trail should be maintained. Follow best practice guidelines: Review and store old records Prevent storage problems Avoid loss of records,Quiz: What Is Audited?,Match the following text, “A” to “What is Audited?”, and “T” to “What is in the Audit Trail?”. A1: Data changed by DML statements A2: SQL statements (insert, update, delete, select, and merge) based on content) A3: Privilege use including object access T1: Fixed set of data including the SQL statement T2: Fixed set of data T3: N/A,Where We Are,Comparing security aspects Applying the principle of least privilege Managing default user accounts Implementing standard password security features Describing auditing: Mandatory auditing Standard database auditing Value-based auditing Fine-grained auditing DBA auditing Virtual Private Database (VPD),Virtual Private Database: Overview,Virtual Private Database (VPD) consists of: Fine-grained access control Secure application context VPD uses policies to add conditions to SQL statements that protect sensitive data. VPD provides row-level access control. Application attributes defined inside an application context are used by fine-grained access policies.,VPD Example,Business rule: Employees outside the HR department are only allowed to see their own EMPLOYEES record. A salesman enters the following query: SELECT * FROM EMPLOYEES; The function implementing the security policy returns the predicate employee_id=my_emp_id and the database rewrites the query and executes the following: SELECT * FROM EMPLOYEES WHERE employee_id=my_emp_id;,Creating a Column-Level Policy,BEGIN dbms_rls.add_policy(object_schema = hr, object_name = employees, policy_name = hr_policy, function_schema =hr, policy_function = hrsec, statement_types =select,insert, sec_relevant_cols=salary,commission_pct); END; /,Column-Level VPD: Example,Statements are not always rewritten. Consider a policy protecting the SALARY and COMMISSION_PCT columns of the EMPLOYEES table. The fine-grained access control is: Not enforced for this query: Enforced for these queries:,SQL SELECT last_name, salary 2 FROM employees;,SQL SELECT last_name FROM employees;,SQL SELECT * FROM employees;,Security Updates,Oracle posts security alerts on the Oracle Technology Network Web site at: /technology/