Date: Thu, 28 Mar 2024 08:08:51 +0000 (UTC) Message-ID: <1296198175.67717.1711613331446@ip-10-0-1-26.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_67716_1562817822.1711613331444" ------=_Part_67716_1562817822.1711613331444 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 regulat= ory guidelines, such as PCI DSS or HIPAA. You can review a li= st of the collected events on the Regulation Guidelines window of the SQL C= ompliance Manager Configuration wizard. On the Summary window at the end of= the wizard, click View the Regulation Guideline Details t= o review a summary of all the regulation guidelines applied to the selected= database.