Date: Fri, 29 Mar 2024 12:05:56 +0000 (UTC) Message-ID: <1896425296.69979.1711713956878@ip-10-0-1-26.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_69978_1347018450.1711713956878" ------=_Part_69978_1347018450.1711713956878 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Enabling auditing on the database allows you to capture SQL even= ts at the database level. You can enable database-level auditing when you r= egister the SQL Server instance. For more information, see Register your SQL Servers.
When you enable auditing on a database, you can control the Audit collection levels p= er each database, choosing whether to apply the built-in default audit sett= ings, enforce= a regulatory guideline, or define custom audit settings.
After you enable auditing on your databases, set up the audited database= properties to enable more advanced auditing, such as Sen= sitive Columns and Before-After Data in tables.= p>
If you disable auditing for any reason , you = can easily re-enable database-level auditing. On the Explore Activi= ty tree, expand the SQL Server instance on which the database= resides. Right-click the name of the database on which you want to enable = auditing, and then select Enable Auditing. This action ena= bles auditing at the server and database levels.
You can use the SQL Compliance Manager Configuration wizard to add a dat= abase and apply one of the following audit settings:
You can use the Import your audit settings feature to apply an audit template you&= nbsp;previously exp= orted from an audited database. To successfully apply the template, fir= st add the database to SQL Compliance Manager.
You can use the command line interface to enable auditing on a new datab=
ase and apply audit settings. The audit settings can be configured using a&=
nbsp;specific=
regulation or an audit template (audit settings you exported to an XML=
file).
Keep in mind the following requirements and limitations:
SQL Compliance Manager includes sample database audit settings templates=
(Sample_Database_AuditSettings.xml
) for your convenience=
. Use this sample template to familiarize yourself with how specific audit =
settings are defined. By default, the sample template is located under
SQLcmCmd [-h=
ost CollectionServer] [-port number] auditdatabase instance database
=
.SQLcmCmd [-h=
ost CollectionServer] [-port number] auditdatabase instance database -Regul=
ation {PCI | HIPAA | PCI, HIPAA}
.The FERPA regulation guideline is provided as an XML templates (FE=
RPA_Database_Regulation_Guideline.xml
) stored in the SQL Compli=
ance Manager installation directory (C:\Program Files\Idera\SQLcompli=
ance
). Ensure the path you cite for the FERPA template reflects the =
directory you chose during installation.
SQLcmCmd [-h=
ost CollectionServer] [-port number] auditdatabase instance database -confi=
g "FERPA regulation guideline file path"
.The SOX regulation guidelines is provided as an XML template (SOX_=
Database_Regulation_Guideline.xml
) stored in the SQL Compliance=
Manager installation directory (C:\Program Files\Idera\SQLcompliance=
). Ensure the path you cite for the SOX template reflects the direct=
ory you chose during installation.
SQLcmCmd [-h=
ost CollectionServer] [-port number] auditdatabase instance database -confi=
g "SOX regulation guideline file path"
.SQLcmCmd [-h=
ost CollectionServer] [-port number] auditdatabase instance database -confi=
g "exported audit settings file path"
.SQL Compliance Ma=
nager audits all acti=
vity on your server. Learn more >=
; >
IDERA Website | Product= s | Buy | Support&= nbsp;| Community | About Us&n= bsp;| Resources | Legal