Date: Fri, 29 Mar 2024 01:50:41 +0000 (UTC) Message-ID: <1477226613.69585.1711677041163@ip-10-0-1-26.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_69584_673733582.1711677041159" ------=_Part_69584_673733582.1711677041159 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
You can use Event Alerts to identify any type of SQL Server even= t data you are currently auditing. Event Alerts allow you to track suspicio= us events collected in your audit data stream. You can use these alerts to = warn about potentially malicious activity or record routine activity on an = audited instance or database.
For example, when a suspicious event is discovered, you can be notified = by email so you can immediately diagnose and resolve the issue. You can als= o configure IDERA SQL Compliance Manager to write a custom message to the a= pplication event log so you have an ongoing record.
Use the following examples to help you identify the alert criteria you n= eed to define in the corresponding Event Alert rule to monitor a specific a= ction.
Data you want to alert on =E2=80=A6 | Type of Event Alert rule criteria to set =E2=80= =A6 |
---|---|
When a login fails to access a database containi= ng customer information |
|
When any login performs a password change |
|
When a non-privileged user attempts to add a log= in to role |
|
When a login other than HR01 changes the Salary = table |
|
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