Skip Headers
Oracle® Beekeeper Online Help
Release 1 (1.5)

Part Number E14838-01
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Feedback page
Contact Us

Go to previous page
View PDF


audit policy

Created from one audit template and one audit scope.

audit template

A collection of auditable event types, configured and maintained by the audit administrator, that the auditor wants to capture and record. Once you create an audit template, it may be referenced by a particular audit policy.

audit record

The stored immutable data of an audited event. Audit records are verifiable; their integrity can be tested at any time to ensure that they are accurate and unchanged from the time of their creation.

audited event

Any auditable event that is actively being audited.

auditable event

Generated by any activity in the Oracle Beehive system that is capable of being audited. Sending an e-mail, changing the state of a document, and changing a service configuration are all examples of auditable events.

audit trail

A selection of audit records that are related based on a given context. For example, the audit trail of a lost business transaction consists of all the related audit records (stored events) that led up to the problem.

audit repository

A secure, immutable storage space for audit records.

audit scope

The logical area of effect of an audit policy, defined as a hierarchy of artifact containers (organizations, workspaces, and folders).

hard quota

The maximum disk space allowed for a workspace, organization, or enterprise. Once the hard quota is reached, no further create or update operations will be allowed until the quota violation is resolved.

soft quota

The disk space limit at which a warning event is created. Essentially, reaching your soft quota triggers a warning that you are approaching your hard quota