Accenture MDR Quick Start Guide for Microsoft Azure SQL
- KM (Unlicensed)
This quick start guide will help Accenture MxDR customers configure Microsoft Azure SQL Event to allow log collection from the Log Collection Platform (LCP).
The document includes the following topics:
Â
Supported Versions
A list of supported versions is available in the Accenture MDR Supported Products List document (Accenture_MDR_Supported_Products_List.xlsx) which can be found in
Accenture MDR Portal - https://mss.accenture.com/PortalNextGen/Reports/Documents
 Port Requirements    Â
Table 1-1: Port requirements for LCP communication.
Source | Destination | Port | Description |
LCP | Event Hub | TCP / 443 | Default port and protocol |
Configuring Microsoft Azure SQL
Prerequisites
An Azure subscription that you can sign in to.
Azure Event Hub to stream the logs.Â
Reference URLs
How to configure Event Hub?
Azure Quickstart - Create an event hub using the Azure portal - Azure Event Hubs
Configuration Steps
Log In to Azure Portal i.e https://portal.azure.com/
Navigate to Auditing under the Security heading in your SQL database or SQL server panel.
3. If you prefer to set up a server auditing policy, you can select the View server settings link on the database auditing page. You can then view or modify the server auditing settings. Server auditing policies apply to all existing and newly created databases on this server.
4. If you prefer to enable auditing on the database level, switch Auditing to ON. If server auditing is enabled, the database-configured audit will exist side-by-side with the server audit.
5. You have multiple options for configuring where audit logs will be written. You can write logs to an Azure storage account, to a Log Analytics workspace for consumption by Azure Monitor logs, or to event hub for consumption using event hub.
Note: For Azure SQL, MxDR supports consumption using event hub only.
6. To configure writing audit logs to an event hub, select Event Hub. Select the event hub where logs will be written and then click Save. Be sure that the event hub is in the same region as your database and server.
7. Use below link to get credentials for Azure Event HUB.
Accenture MDR Quick Start Guide to Get Credentials for Azure Storage and Azure Event HUB
LCP Configuration parameters
Table 1-2: The Microsoft Azure SQL Event (API - ) collec5041tor properties to be configured by MxDR are shown in table.
Property | Value If Using EventHub |
|---|---|
Logging Source | Select EventHub |
eventHubConnectionString | Event hub connection string |
consumerGroupName | Optional and used if consumer Group is other than default |
Account Key | Access Key to access storage account |
Blob Container | Storage blob Container name |
Storage Account Name | Azure storage account name |
Subscription | Set Eventhub name |
initialReadPolicy | N/A (keep default selection) |
Note: In case of EventHub logging source, storage Account Key/SAS Token, Blob Container, and Storage Account Name are required because the marker for the event hub gets stored in the storage account.
Legal Notice
Copyright © 2021 Accenture. All rights reserved.
Accenture, the Accenture Logo, and DeepSight Intelligence are trademarks or registered trademarks of Accenture in the U.S. and other countries. Other names may be trademarks of their respective owners.
The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Accenture and its licensors, if any.
THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. ACCENTURE SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.
The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19 "Commercial Computer Software - Restricted Rights" and DFARS 227.7202, et seq. "Commercial Computer Software and Commercial Computer Software Documentation," as applicable, and any successor regulations, whether delivered by Accenture as on premises or hosted services. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.