Date: Fri, 29 Mar 2024 09:34:20 +0000 (UTC) Message-ID: <882493220.69861.1711704860599@ip-10-0-1-26.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_69860_844979423.1711704860596" ------=_Part_69860_844979423.1711704860596 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
When you add a database to audit, you can select the Default, Cu= stom, or Regulation audit collection level. Use the audit collection level = to control which SQL Server events you audit at the database level.
Default collection level
Allows you to collect the SQL Server events most commonly requested by a= uditors. This collection level audits the following activities and SQL even= ts:
Custom collection level
Allows you to select the specific activities and SQL events you want to = audit on these databases. The Custom collection level is recommended for ad= vanced users, or for cases in which only one type of data is required for c= ompliance. Before using the Custom collection level, review the event data = gathered by the Default collection level.
Regulation
Configures your audit settings to collect the event data required by spe= cific regulator= y guidelines, such as PCI DSS or HIPAA. You can review a list= of the collected events on the Regulation Guidelines window of the SQL Com= pliance Manager Configuration wizard. On the Summary window at the end of t= he wizard, click View the Regulation Guideline Details to = review a summary of all the regulation guidelines applied to the selected d= atabase.