|
|
SOX Report Specifics | Abnormal or Unauthorized Changes to Data Report (AUC) |
Abnormal or Unauthorized Changes to Data Report (AUC)
AUC Report Sample
COBIT Objectives and Setup Requirements
Objective |
| FortiDB MA Module |
Number(s) | Objective Description | Setup Requirement |
|
|
|
AI2.3 | Unauthorized changes to data by | UBM: Object policies, |
| accounts are tracked and reviewed by IT | since this will focus on |
| Management on a quarterly basis. | data changes in specific |
|
| tables containing financial |
|
| information. |
|
|
|
1.
Report Body Columns
The following columns are displayed in the report body:
Column | Description |
|
|
User ID | The ID of the database user that conducted the flagged activity. |
|
|
Object | The name and owner of the database object that was directly manipulated by |
| the flagged activity |
|
|
Time Stamp | The exact time the flagged activity was conducted. |
|
|
Terminal Name | The terminal IP address or name. |
|
|
Origin Application | The name, or other identifier, for the originating application, if the activity |
| originated from an external application or from an application server. |
|
|
Action Type | The type of action successfully enacted by the User ID. |
|
|
| Note: By default, all actions are considered unauthorized. If you want, for |
| example, to only mark UPDATEs as unauthorized actions, use an Action Type |
| filter in the Settings dialog in order to filter out the other action types You can also |
| distinguish (un)authorized users by defining a User ID filter in the Settings dialog. |
FortiDB Version 3.2 Utilities | User Guide |
45 |