Table of Contents

Search

  1. Preface
  2. Introduction to Dynamic Data Masking Administration
  3. Authentication
  4. Connection Management
  5. JDBC Client Configuration
  6. ODBC Client Configuration
  7. Access Control
  8. Logs
  9. High Availability
  10. Server Control
  11. Performance Tuning
  12. Troubleshooting

Administrator Guide

Administrator Guide

Audit Trail and Detailed Audit Trail

Audit Trail and Detailed Audit Trail

The Dynamic Data Masking general audit trail and detailed audit trail log files contain information that you use to verify whether a user made unauthorized modifications to the Dynamic Data Masking configuration.
The AuditTrail.log file contains general audit information about changes in the Management Console. The AT appender in the auditTrail logger creates the AuditTrail.log file. You can add appenders to the auditTrail logger to create additional audit trail output formats.
The detailed audit file contains comprehensive audit information that is not in the AuditTrail.log file. Dynamic Data Masking names the detailed audit file according to the year and month that it creates the file. For example, if Dynamic Data Masking creates a detailed audit file in April 2013, it names the file 2013_04.at.
The detailed audit file contains the following information on modifications to the Dynamic Data Masking configuration properties:
Property
Modification
Database
Database node changes. You can view the following actions:
  • Add
  • Remove
  • Copy
  • Move
  • Edit
  • Change database name
Security rule set
Security rule set changes. You can view the following actions:
  • Add
  • Remove
  • Copy
  • Move
  • Edit
  • Change security rule name
Service
Dynamic Data Masking service changes. You can view the following actions:
  • Add
  • Remove
  • Edit
Authorization
Authorization changes. You can view the following actions:
  • Set authorizations
Connection rule
Connection rule changes. You can view the following actions:
  • Edit
Server
Dynamic Data Masking Server changes. You can view the following actions:
  • Edit
The entries in the detailed audit file contain the following tags:
Tag
Description
operation
Audit trail operations.
You can view the following operations:
  • Add
  • Change
  • Remove
date
Date and time of the modification.
clientIP
Client IP address or host name.
userName
Client user name. The entry does not contain the userName tag if the user is admin.
status
Status of the operation.
You can view the following statuses:
  • Success
  • Failed
path
Element path in the Management Console tree.
authorizations
Element authorizations such as owner, read privileges, and read and write privileges. If the owner is admin, the authorizations tag is empty.
content
Content of the element.

Sample AuditTrail.log File

The following excerpt is from the general audit trail log:
05/14 19:54:43,199 INFO - [127.0.0.1] [admin] LOGIN: Success! 05/14 20:00:17,093 INFO - [127.0.0.1] [admin] REMOVE NODE (DatabaseNode) Oracle11g (10.10.10.10): Success! 05/14 20:00:37,620 INFO - [127.0.0.1] [admin] ADD NODE (DomainNode) Domain1: Success! 05/14 20:00:40,901 INFO - [127.0.0.1] [admin] MOVE NODE (ServerNode) myServer: Success! 05/14 20:00:46,175 INFO - [127.0.0.1] [admin] REMOVE NODE (DomainNode) Domain1: Cannot remove node Domain1. DDM Server myServer is in branch. 05/14 20:00:49,441 INFO - [127.0.0.1] [admin] MOVE NODE (ServerNode) myServer: Success! 05/14 20:00:58,838 INFO - [127.0.0.1] [admin] EDIT NODE (DomainNode) domain2: Success! 05/14 20:01:06,603 INFO - [127.0.0.1] [admin] EDIT NODE (RuleSetNode) MaskingRuleSet: Success! 05/14 20:01:11,405 INFO - [127.0.0.1] [admin] EDIT NODE (RuleSetNode) MaskingRuleSet: Success! 05/14 20:01:21,679 INFO - [127.0.0.1] [admin] SET SWITCHING RULES: ddmForOracle: Success! 05/14 20:01:25,356 INFO - [127.0.0.1] [admin] SET SWITCHING RULES: ddmForOracle: Success! 05/14 20:01:36,912 INFO - [127.0.0.1] [admin] LOGOUT 05/14 20:01:37,916 INFO - [127.0.0.1] [admin] LOGIN: Authentication failed 05/14 20:01:43,440 INFO - [127.0.0.1] [admin] LOGIN: Success! 05/14 20:02:01,397 INFO - [127.0.0.1] [admin] LOGOUT05/14 20:20:34,104 INFO - [127.0.0.1] [admin] LOGIN: Success! 05/14 20:20:54,006 INFO - [127.0.0.1] [admin] MOVE NODE (DomainNode) domain2: Success! 05/14 20:22:37,829 INFO - [127.0.0.1] [admin] LOGIN: Success! 05/14 20:22:37,831 INFO - [127.0.0.1] [admin] LOGOUT 05/14 20:23:09,070 INFO - [127.0.0.1] [admin] LOGIN: Success! 05/14 20:25:51,918 INFO - [127.0.0.1] [admin] LOGOUT

Sample Detailed Audit File

The following audit file is an example of the detailed audit file:
<?xml version="1.0" encoding="UTF-8" standalone="no" ?> - <XML type="database"> - <content type="ATContent"> - <newContent> <cpuCount>0</cpuCount> - <services type="ArrayList"> - <entry> <serviceName>1</serviceName> </entry> </services> <oracleVersion /> <dbaPassword>GNKEJHAPBJBBMECC</dbaPassword> <dbaUser>1</dbaUser> <name>1</name> - <instances type="ArrayList"> - <entry class="com.activebase.db.oracle.OracleInstance" type="Configurable"> <cpuCount>0</cpuCount> <oracleVersion /> <dbaPassword>GNKEJHAPBJBBMECC</dbaPassword> <instanceName>1</instanceName> <dbaUser>1</dbaUser> <listenerAddress>1</listenerAddress> <hostName /> <listenerPort>1</listenerPort> <infoTimestamp>0</infoTimestamp> </entry> </instances> <infoTimestamp>0</infoTimestamp> </newContent> </content> <operation>add</operation> - <authorizations type="ATAuthorizations"> <newAuthorizations class="com.activebase.configuration.Authorizations" type="Configurable" /> </authorizations> <status>success</status> - <path type="ATPath"> <newPath>Site/1</newPath> </path> <date>01/08/2013 19:26:57,429</date> <clientIP>127.0.0.1</clientIP> </XML>

0 COMMENTS

We’d like to hear from you!