Table of Contents

Search

  1. About the Data Vault Administrator Guide
  2. Introduction to the Data Vault
  3. Data Vault Service Startup and Shutdown
  4. Data Vault Configuration
  5. Data Vault SSL Setup
  6. Data Vault ODBC Setup
  7. Data Vault Administration
  8. Data Repartitioning
  9. Partial Data Vault Copy
  10. Archived Data Migration
  11. Data Validation
  12. Bulk File Uploader
  13. Data Vault Administration Tool
  14. Data Vault Logs
  15. User Account Privileges
  16. ssasql Command Line Program
  17. Data Vault Audit Log
  18. Appendix A: Sample Configuration Files

Data Vault Administrator Guide

Data Vault Administrator Guide

Audit Log Configuration Process

Audit Log Configuration Process

To create an audit log, first configure the Data Vault
ssa.ini
file. Then, in the Dynamic Data Masking Management Console, configure the Data Vault to connect to Dynamic Data Masking. Last, create connection rules and security rules in the Management Console.
To configure the audit log, perform the following tasks:
  1. Configure the Data Vault
    ssa.ini
    file. The audit log parameters turn the audit log on and off, and control how the audit log files grow. To limit the size of the audit log files, configure either the AUDITLOGLIMIT_FILESIZE or AUDITLOGLIMIT_TIME property. To set the maximum number of audit log files that Data Vault retains, configure the AUDITLOGLIMIT_MAXFILES property.
  2. Configure the Data Vault connection in the Management Console. First, add the Dynamic Data Masking service for Data Vault. Then enter the Data Vault connection details to create a connection to the Data Vault.
  3. To process incoming connection requests from the application or client that issues SQL requests to the Data Vault, create connection rules. The first connection rule that you create identifies incoming connections and routes them to the Data Vault. The second connection rule that you create sends requests to the security rule set.
  4. After you create the connection rules, create a security rule set and security rules. The first security rule that you create logs whenever a connection rule sends an incoming SQL request to the security rule set. The second security rule that you create identifies the columns that you want to trigger the audit. If an incoming SQL request queries any of the columns that you configured to trigger the audit, the rule rewrites the SQL request statement to append an audit tag.

0 COMMENTS

We’d like to hear from you!