|
1 | 1 | Defender for Databases generates security alerts in Microsoft Defender for Cloud, but those alerts don't automatically reach the people who need to respond to them. At Contoso Financial Services, the security team enabled Defender for Azure SQL Databases and Defender for open-source relational databases across production subscriptions. Now you configure where alerts go, create suppression rules for expected behavior patterns, and validate that the detection pipeline works end-to-end. |
2 | 2 |
|
3 | | -:::image type="content" source="../media/alert-routing-pipeline.png" alt-text="Diagram showing how Defender for Databases detections flow through alert generation, suppression rules, and routing to email notifications and Microsoft Sentinel." lightbox="../media/alert-routing-pipeline.png"::: |
| 3 | +:::image type="content" source="../media/alert-routing-pipeline.png" alt-text="Diagram of Defender for Databases detections flowing through alert generation, suppression rules, and routing to email and Microsoft Sentinel." lightbox="../media/alert-routing-pipeline.png"::: |
4 | 4 |
|
5 | 5 | | Destination | Configuration method | Purpose | |
6 | 6 | |-------------|---------------------|---------| |
@@ -63,11 +63,11 @@ This validation confirms that when a real incident occurs, the right people rece |
63 | 63 |
|
64 | 64 | Before handing off the implementation: |
65 | 65 |
|
66 | | -- [ ] Defender for Azure SQL Databases is enabled on all production subscriptions |
67 | | -- [ ] Defender for open-source relational databases is enabled on all subscriptions with PostgreSQL or MySQL |
68 | | -- [ ] Email notifications route to the SOC team distribution list |
69 | | -- [ ] Microsoft Sentinel data connector is active and Defender for Databases incidents appear in Microsoft Sentinel |
70 | | -- [ ] Suppression rules are scoped correctly and have expiration dates set |
71 | | -- [ ] Sample alerts are generated and validated end-to-end |
| 66 | +- Defender for Azure SQL Databases is enabled on all production subscriptions |
| 67 | +- Defender for open-source relational databases is enabled on all subscriptions with PostgreSQL or MySQL |
| 68 | +- Email notifications route to the SOC team distribution list |
| 69 | +- Microsoft Sentinel data connector is active and Defender for Databases incidents appear in Microsoft Sentinel |
| 70 | +- Suppression rules are scoped correctly and have expiration dates set |
| 71 | +- Sample alerts are generated and validated end-to-end |
72 | 72 |
|
73 | 73 | With alert routing configured and validated, the security operations team receives Defender for Databases detections in the systems they use for incident management. Your implementation connects detection to response. This foundation enables database security operations at Contoso. |
0 commit comments