Skip Navigation Links | |
Exit Print View | |
![]() |
Oracle Identity Analytics 11gR1 Database Administrator's Guide |
3. Resource Types Metadata Module
This chapter describes the tables that make up the Identity Audit module.
|
|
The Identity Audit (IDA) module identifies policy violations and the IDA_POLICES table stores a collection of rules defined by the RULE_SETS table. Every policy stored in this table has an OWNER and a REMEDIATOR.
PK_IDA_POLICIES - primary key on column ID
None
IX_IDA_POLICY_NAMES - unique index on column POLICY_NAME
|
|
The IDA_POLICY_VIOLATIONS table holds information about policy violations detected by an identity audit scan. Each entry has a unique ID and the following fields: IDA_POLICY_ID, USER_ID, LASTDATE_DETECTED, DETECTION_COUNT, POLICY_VIOLATION_STATE, SEVERITY (1-High, 2-Medium, 3-Low), CREATEDATE, and UPDATEDATE. The POLICY_VIOLATION_STATE stores the state of the violation in the form of an integer that can have the following values: 1-Open, 2-Closed, 3-Remediated, or 4-Mitigated.
PK_IDA_POLICY_VIOLATIONS - primary key on column ID
None
None
|
|
The IDA_POLICY_VIOLATION_CAUSES table holds information about the causes behind policy violations as detected by an identity audit scan. Each entry has a unique ID. The IDA_POLICY_VIOLATION_ID field is derived from the IDA_POLICY_VIOLATION table. The IDA_RULE_ID and IDA_RULE_VERSION_ID fields contain information about the rule set that the policy was run against, whereas the RBACX_OBJECT_ID and RBACX_OBJECT_TYPE fields store information about the Oracle Identity Analytics object against which the policy violation was detected. Additional information, such as the DESCRIPTION of the policy violation cause and the policy violation STATUS are also stored in this table.
PK_IDA_POLICY_VIOLATION_CAUSES - primary key on column ID
None
None
|
|
The IDA_SCANS table saves information about the audit scans that are run in Oracle Identity Analytics. Every scan is identified by a unique ID from the IDA_SCANS table. This table also saves information like NAME, SCAN_TYPE, STATUS_ID, and DESCRIPTION. The RESULT_APPLIED field indicates if the scan was executed (run) or just previewed. When the scan is scheduled to run periodically, information is maintained in this table in the following fields: CREATE_USER, CREATE_DATE, UPDATE_DATE, RUN_COMPLETE_DATE, and NEXT_RUN_DATE. The USER_COUNT field contains the number of users that were scanned, whereas the VIOLATION_COUNT field contains the number of violations detected as a result of the scan run. The configuration information regarding each scan is saved as XML in the CONFIGURATION_XML field, and the scan data information is saved in the DATA_XML field.
PK_IDA_SCANS - primary key on column ID
None
None
|
|
The IDA_POLICY_VIOLATIONS_TRAILS table stores the steps taken by an actor (that is, the Oracle Identity Analytics user) to resolve a policy violation detected during an identity audit scan.
PK_IDA_POLICY_VIOLATIONS_TRAILS - primary key on column ID
None
None
|
|
The IDA_POLICY_VIOLATION_PREVIEWS table saves violation information that the user can preview without running the actual scan. Each entry has the following fields: IDA_POLICY_VIOLATION_ID, IDA_POLICY_ID, USER_ID, POLICY_VIOLATION_STATE, SEVERITY (1-High, 2-Medium, 3-Low), CREATEDATE, and CREATE_SCAN_ID. The POLICY_VIOLATION_STATE field stores the state of the violation in the form of an integer that can have the following values: 1-Open, 2-Closed, 3-Remediated, or 4-Mitigated.
PK_IDA_VIOLATION_PREVIEWS - primary key on column ID
None
None
|
|
The IDA_VIOLATION_PREVIEW_CAUSES table saves information about the causes behind policy violations as detected during identity audit policy previews. Each entry has a unique ID. The IDA_POLICY_VIOLATION_ID field is derived from the IDA_POLICY_VIOLATION_PREVIEW table. The IDA_RULE_ID and IDA_RULE_VERSION_ID fields contain information about the rule set that the policy was run against, whereas the RBACX_OBJECT_ID and RBACX_OBJECT_TYPE fields give information about the Oracle Identity Analytics object against which the policy violation was detected. Additional information, such as the DESCRIPTION of the policy violation cause and the STATUS of the policy violation, is also stored in this table.
PK_IDA_VIOLATION_PREVIEW_CAUSES - primary key on column ID
None
None