Date: Fri, 29 Mar 2024 07:50:23 +0000 (UTC)
Message-ID: <1929630401.69723.1711698623893@ip-10-0-1-26.ec2.internal>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_69722_1779526319.1711698623890"
------=_Part_69722_1779526319.1711698623890
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
As you configure or modify audit settings for your SQL Server in=
stances, you may want to apply the same settings across multiple SQL Server=
instances in your environment. You can import audit settings through previ=
ously exported XML files, allowing you to:
- Use previously configured audit settings as a baseline, or template, yo=
u deploy to multiple instances and databases so that the same events are au=
dited across your environment
- Ensure all SQL Server databases used by regulated applications, such as=
SAP, are consistently audited and held to the same level of compliance
- Streamline and automate your configuration workflow
If a user is assigned privileged status as part of the aler=
t rule you are importing, and that user does not yet exist in the environme=
nt you are importing to, the privileged user status will appl=
y if the user is ever added to your environment.
Auditing the same events across multiple instances and dat=
abases
You can import previously configured audit settings to use as a baseline=
, or template. By deploying this baseline to multiple instances and databas=
es, you can ensure the same events are audited across your environment.
To audit the same events across multiple instances or datab=
ases:
- Navigate to Registered SQL Servers in the Admi=
nistration tree.
- On the Registered SQL Servers tab, click Impor=
t.
- On the Select File to Import window, click Browse and =
locate the audit settings file, and then click Open.
- Click Next.=20
- If you want to audit events at the server level as well as=
events initiated by privileged users, select these import op=
tions.
- If you want to audit events at the database level, click Database Audit Settings, and then select the =
database you want to use as your baseline or template.
- On the Target Servers window, select the registered SQL Server instance=
s to which you want to apply the selected audit settings, and then click
Next.
- On the Import Audit Settings window, select the audit settings you want=
to import, and then click Next.
- On the Target Databases window, select the audited databases to which y=
ou want to apply the selected audit settings, and then click Next=
strong>.
- On the Summary window, choose whether you want your imported audit sett=
ings to overwrite the settings on the target SQL Server instances and datab=
ases or be added to the settings already present. Click Finish to import your audit settings.
Auditing regulated applications across your environment
You can import previously-configured audit settings to ensure all SQL Se=
rver databases used by regulated applications, such as SAP, are consistentl=
y audited and are held to the same level of compliance.
To audit regulatory applications across your environment:
- Navigate to Registered SQL Servers in the Admi=
nistration tree.
- On the Registered SQL Servers tab, click Import.
- On the Select File to Import window, click Browse and =
locate the audit settings file, and then click Open.
- Click Next.
- On the Import Audit Settings window, specify which databases are config=
ured with the audit settings you want to import. Complete the following ste=
ps:=20
- Click Database Audit Settings, and then select the Only import for matching database names option.
- Select the databases whose audit settings you want to apply.
- If you also want to audit events at the server level as we=
ll as events initiated by privileged users, select these opti=
ons, and then click Next.
- On the Target Servers window, select the audited SQL Server instances y=
ou want to apply the audit settings to from the list, and then click Next.
- On the Target Databases window, ensure the target database list matches=
the database names you specified to match. Select the audited databases to=
which you want to apply the imported audit settings, and then click Next.
- On the Summary window, select whether you want your imported audit sett=
ings to overwrite the settings on the target SQL Server instances and datab=
ases or added to the settings already present. Click Finish to import your audit settings.
SQL Compliance Manager monitor, audit and alert on SQL user activity and data changes=
.
------=_Part_69722_1779526319.1711698623890--