Page History

...

1. In the Explore Activity tree, select the SQL Server instance that hosts the new database.
2. Select Audited Database from the New drop-down.
3. Select the user databases you want to audit, and then click Next.
4. Select which audit collection level you want to use, and then click Next.
5. If you chose to use the Custom audit collection level, select the appropriate audit settings for these databases, and then click Next. SQL CM SQL Compliance Manager audits only the activities and results you select. For information, see Database-level audit settings.
6. If you chose to use the Custom audit collection level and you are auditing DML and SELECT events, select the objects SQL CM SQL Compliance Manager should audit for these events, and then click Next.
7. If you chose to use the Custom audit collection level, select any trusted users you do not want to audit, and then click Next.
   • Trusted users are database users, SQL Server logins, or members of SQL Server roles that you trust to read, update, or manage a particular audited database. SQL CM Compliance Manager does not audit trusted users. Trusted users are designated on the Add Trusted Users window of the New Audited Database wizard.
   • If you are auditing privileged user activity and the trusted user is also a privileged user, SQL CM Compliance Manager continues to audit this user because of its elevated privileges. For example, a service account that is a member of the sysadmin fixed SQL Server role will continue to be audited even though the account is designated as trusted.
8. Click Finish. 

...

• This process requires manually deploying the SQLcompliance SQL Compliance Manager Agent to the instance that hosts this database.
• The auditdatabase command does not support enabling auditing of a database that belongs to a virtual SQL Server instance hosted on a Windows cluster.
• The auditdatabase command supports case-sensitive named instances. Ensure you are using the appropriate case when you cite the instance and database names.
• The CLI does not support configuring Before-After data auditing.
• You can apply either a built-in regulation guideline or an XML template file.

...

To enable database auditing and apply the Typical (default) audit settings:

1. Use the SQL CM Compliance Manager setup program to to manually deploy the SQLcompliance SQL Compliance Manager Agent to  to the instance that hosts the target database.
2. In Windows Command Prompt, use the following syntax: SQLcmCmd [-host CollectionServer] [-port number] auditdatabase instance database.

To enable database auditing and apply a HIPAA or PCI regulation guideline:

1. Use the SQL CM Compliance Manager setup program to to manually deploy the SQLcompliance SQL Compliance Manager Agent to  to the instance that hosts the target database.
2. In Windows Command Prompt, use the following syntax: SQLcmCmd [-host CollectionServer] [-port number] auditdatabase instance database -Regulation {PCI | HIPAA | PCI, HIPAA}.

...

1. Use the SQL Compliance Manager setup program to to manually deploy the SQLcompliance SQL Compliance Manager Agent to  to the instance that hosts the target database.
2. In Windows Command Prompt, use the following syntax: SQLcmCmd [-host CollectionServer] [-port number] auditdatabase instance database -config "FERPA regulation guideline file path".

...

1. Use the SQL CM Compliance Manager setup program to to manually deploy the SQLcompliance SQL Compliance Manager Agent to  to the instance that hosts the target database.
2. In Windows Command Prompt, use the following syntax: SQLcmCmd [-host CollectionServer] [-port number] auditdatabase instance database -config "SOX regulation guideline file path".

...

1. Determine which currently audited database has the audit settings you want to apply to the new database.
2. Export your audit settings from the source database.
3. Use the SQL CM Compliance Manager setup program to to manually deploy the SQLcompliance SQL Compliance Manager Agent to  to the instance that hosts the target database.
4. In Windows Command Prompt, use the following syntax: SQLcmCmd [-host CollectionServer] [-port number] auditdatabase instance database -config "exported audit settings file path".

...

...

...