Abstract: "Oracle Audit parse [audit]"
The following are the reference documents on the network to write, if error please advise, thank you.
-----------------------------------------------------------------------------------------------------------------
1.Oracle audit: the use of a specific object to certain privileges; for a particular table select, insert, update, delete;
For example: A. Ting use the "Select any table" privileges, access Chemo certain tables, but not through formal authorization.
B. Create Table permission to use
C. Update Ting.medmedf
Auditable content: You can learn OS login account, time oracle account used machine name, audits are triggered, according to the contents of the audit record.
For example: when a user login system; whether the user access to specific data tables.
Advantages: A. Each session will incur an audit transactions; data table, or each access check sum data. The use of resources than the FGA (Fine-grained audit) less.
B. This record can be recorded in the DB or system event viewer. Shortcomings: A. not know the details of the information. For example, the user can not know the exact sum of the data that is accessed by
What SQL, what changed data. ====> can be achieved through the trigger, but only for certain important data sheet.
B. To all the data tables for the audit under the specific objects, you need to set case by case.
C.audit settings need to change the database parameter; you must restart the database in order to change the setting.
2.System triggers: general based on the data table trigger different. This trigger is based on system events; such as login, logout, database open,
关、creation、altering、dropping of schema objects。
AFTER STARTUP
BEFORE SHUTDOWN
AFTER LOGON
BEFORE LOGOFF
AFTER DB_ROLE_CHANGE -- for Data Guard failover and switchover
AFTER SUSPEND
AFTER SERVERERROR
E.g:
CREATE OR REPLACE TRIGGER bcs_trigger
BEFORE LOGON
ON DATABASE
BEGIN
NULL;
END:
2.1 DDL trigger: Triggered when there is ddl transaction Schema
BEFORE / AFTER ALTER
BEFORE / AFTER ANALYZE
BEFORE / AFTER ASSOCIATE STATISTICS
BEFORE / AFTER AUDIT
BEFORE / AFTER COMMENT
BEFORE / AFTER CREATE
BEFORE / AFTER DDL
BEFORE / AFTER DISASSOCIATE STATISTICS
BEFORE / AFTER DROP
BEFORE / AFTER GRANT
BEFORE / AFTER NOAUDIT
BEFORE / AFTER RENAME
BEFORE / AFTER REVOKE
BEFORE / AFTER TRUNCATE
AFTER SUSPEND
E.g:
CREATE OR REPLACE TRIGGER bcs_trigger
BEFORE CREATE
ON SCHEMA
BEGIN
NULL;
END:
3.Update, delete, insert triggers: trigger on the establishment of the data, the user can learn the subtle movement operation; for example, a sum which data is updated, the original data
After the appearance of the sample data can be recorded. Disadvantages: only for particular table records important data.
4.Fine-grained audit: records can be used for a particular data table access, under certain conditions may limit the SQL statement and then will perform the audit of the operation only.
Advantages: A. do not have to restart the database, only to be executed package (dbms_fga)
B. know SQL command operations.
Shortcomings: A. oracle 9i only for select for audit; oracle 10g can be used for auditing select, update, insert, delete the
B. because each job will have a packet of data, so the use of resources and more than Oracle audit.
C. To all the data tables for the audit under the specific objects, you need to set case by case. In the future if new data table, should be set again.
Fine-grained auditing may be useful for specific auditing situations, but is not suggested for daily auditing activities.
5.System log: Event Viewer
The above operation is recommended to be used for a particular purpose, or periodic audits to make clear or to back up data.
Otherwise easy to become a future burden on the system; audit data too difficult to use.
Original: Big Box "Oracle Audit parse [audit]"