Import Azure logs into Security Center

更新时间:
复制 MD 格式

Import logs from Azure channels — Microsoft Entra ID, Azure Key Vault, Azure Firewall, and Azure Activity Log — into the Agentic SOC of Alibaba Cloud Security Center for unified parsing and threat detection. Azure Event Hubs relays the logs, and Security Center pulls them over the Kafka protocol.

How it works

Azure Event Hubs is compatible with the Apache Kafka protocol, so an event hub can act as a Kafka endpoint. Security Center acts as a Kafka client: it connects to the event hub with an endpoint, a topic, and authentication credentials, pulls the log data, and then applies unified parsing and threat detection.

The following diagram shows the end-to-end configuration flow.

image

Prepare an event hub in Azure

Create the Event Hubs namespace and event hub that receive your Azure logs, and then record the connection details that Security Center needs.

Note

For detailed instructions, see the Azure documentation. Create an event hub using the Azure portal

Step 1: Create a resource group

  1. Log on to the Azure portal. Open the Azure portal.

  2. In the left navigation pane, choose Resource groups, then click Create.

  3. On the Create a resource group page, configure the following settings, then click Review + create.

    • Subscription: Select the Azure subscription in which to create the resource group.

    • Resource group name: Enter a unique name for the resource group.

    • Region: Select the Region for the resource group.

  4. Confirm the settings, then click Create.

Step 2: Create an Event Hubs namespace

  1. In the left navigation pane, choose All services. Under Analytics, click Event Hubs.

    Event Hubs service

  2. On the Event Hubs page, click Create and configure the following settings.

    • Subscription: Select the subscription from Step 1.

    • Resource group: Select the resource group created in Step 1.

    • Namespace name: Enter a name for the namespace. The service address of the Kafka endpoint appears at the lower-right of the input box. For example, if you enter test01namespace, the address suffix is .servicebus.windows.net.

    • Region: Select the Region of the resource group created in Step 1.

    • Pricing tier: Select a tier based on your requirements. The default is Basic. To restrict access to the namespace so that only Agentic SOC can reach it, Standard configuration or above is recommended. For instructions, see Configure an event hub allowlist (optional).

      Note

      For the differences between tiers, see the Azure documentation on quotas and limits, Event Hubs Premium, and Event Hubs Dedicated. Quotas and limitsEvent Hubs PremiumandEvent Hubs Dedicated

    • Throughput Units / Processing Units (Premium): Keep the default value.

      Note

      For details about throughput units and processing units, see the Azure documentation on scaling. Scaling with Event Hubs.

    • Auto-inflate: Turn this feature on or off based on your requirements.

  3. On the Networking tab, set Public access as the connectivity method, then click Review + create at the bottom of the page.

    Important

    To grant Agentic SOC exclusive access to the Event Hubs namespace, configure an IP allowlist in Azure. For instructions, see Configure an event hub allowlist (optional).

  4. Verify the settings, then click Create and wait for the deployment to finish.

  5. On the Deployment complete page, click Go to resource to open the namespace details page.

    Note

    You can also open the namespace details page by clicking the namespace name in the list on the Event Hubs home page.

Step 3: Create an event hub

  1. On the namespace details page created in Step 2, click + Event Hub.

  2. On the creation page, configure the following settings, then click Review + create.

    • Name: Enter a name for the event hub.

      Important

      The event hub name is the Kafka topic that you configure later. Use a representative name that is easy to find and understand.

    • Other settings: Keep the defaults.

  3. On the confirmation page, click Create and wait for the task to finish.

  4. Return to the namespace home page. The new event hub appears in the Event Hubs section.

Step 4: Record key information

Record the following information. You need it when you configure Azure diagnostic settings and when you import the Event Hubs logs into Agentic SOC.

Information

Description

Namespace name

The name of the Event Hubs namespace.

Event hub name

The name of the event hub instance created under the namespace.

Consumer group

The default value is $Default. You can also use a custom value.

Shared access policy connection string

To get the connection string:
1. On the namespace page, click Shared access policies under Settings in the left navigation pane.
2. Click the primary policy RootManageSharedAccessKey, then copy the Primary Connection String from the policy details panel.

Configure channel log delivery to the event hub

Configure diagnostic settings on each Azure resource to deliver its logs to the event hub created in Step 3. The steps differ slightly by channel.

Microsoft Entra ID

  1. On the Azure portal home page, search for Microsoft Entra ID and open the service page.

  2. In the left navigation pane, choose Monitoring > Diagnostic settings.

    Diagnostic settings

  3. Click Add diagnostic setting, or select an existing setting to edit.

  4. Select the log categories to collect, such as sign-in logs and audit logs.

  5. Under the destination, select Stream to an event hub, then select the namespace and event hub instance created in Step 3.

    Stream to an event hub

  6. Click Save.

Azure Key Vault

The steps are similar to those for Microsoft Entra ID.

  1. Open the Azure Key Vault resource page.

  2. In the left navigation pane, choose Monitoring > Diagnostic settings.

  3. Click Add diagnostic setting, or select an existing setting to edit.

  4. Select the log categories to collect. Under the destination, select Stream to an event hub, then select the namespace and event hub instance created in Step 3.

  5. Click Save.

Azure Firewall

The steps are similar to those for Microsoft Entra ID.

  1. Open the Azure Firewall resource page.

  2. In the left navigation pane, choose Monitoring > Diagnostic settings.

  3. Click Add diagnostic setting, or select an existing setting to edit.

  4. Select the log categories to collect. Under the destination, select Stream to an event hub, then select the namespace and event hub instance created in Step 3.

  5. Click Save.

Azure Activity Log

The entry point for Activity Log differs from resource-level diagnostic settings.

  1. On the Azure portal home page, search for and open the Azure Monitor service.

  2. In the left navigation pane, choose Activity log.

    Activity log

  3. At the top of the page, click Diagnostic settings.

  4. Click Add diagnostic setting, or select an existing setting to edit.

  5. Select the activity log categories to collect. Under the destination, select Stream to an event hub, then select the event hub created in Step 3.

    Add diagnostic setting for Activity Log

  6. Click Save.

Configure data import in Security Center

After the logs are delivered to the event hub, configure Security Center to pull them.

Step 1: Authorize Security Center to access the event hub

  1. On the Multi-cloud Configuration Management tab, select the multi-cloud asset, then click Add Authorization and select IDC from the drop-down list.

  2. In the panel that appears, configure the following settings:

    • Vendor: Select Apache.

    • Product: Select Kafka.

    • Endpoint: Enter <YOUR-NAMESPACE>.servicebus.windows.net:9093. Replace <YOUR-NAMESPACE> with the Event Hubs namespace name.

    • Username:$ConnectionString. This value is fixed and cannot be changed.

    • Password: The primary connection string of the event hub.

    • Protocol:sasl_ssl.

    • SASL mechanism:plain.

  3. For Configure Sync Policy and AK Service Status Check: Not applicable. Skip this step.

Step 2: Create a data import task

  1. Create a data source for the Azure log data. If you have already created one, skip this step.

  2. On the Data Import tab, click Add Data Import.

  3. In the panel that appears, configure the following settings:

    • Data source type:Kafka.

    • Endpoint:<YOUR-NAMESPACE>.servicebus.windows.net:9093, where <YOUR-NAMESPACE> is the Event Hubs namespace name.

    • Topics: The event hub name that you set when you created the event hub.

    • Value type:json.

  4. Configure the target data source:

    • Data source name: Select the data source created in this step.

    • Target Logstore: Select the Logstore configured for the data source.

  5. Click OK to save the configuration.

After the import is configured, Security Center automatically pulls logs from the Azure event hub.

Configure an event hub allowlist (optional)

Restrict access to the Event Hubs namespace so that only Agentic SOC IP addresses can reach it.

Note

The Basic tier does not support IP allowlist configuration.

Note: For detailed instructions, see the Azure documentation on configuring an IP firewall for an existing namespace.

  1. In the left menu of the Event Hubs namespace, click Networking under Settings.

  2. On the Public access tab of the Networking page, click Manage in the Public network access section.

  3. On the public network access configuration page, in the Default action section, select Enable from selected networks.

  4. In the IP Addresses section, enter the IP addresses to add to the allowlist, then click Save.

Add IP addresses for both of the following.

IP addresses of the region where your SLS project is located

All regions share the same VPC IP address allowlist: 100.104.0.0/16.

Region

Public IP address

China (Hangzhou)

114.55.8.190, 47.99.57.53, 114.55.85.98, 47.99.212.49, 120.26.169.131, 118.178.236.24, 47.98.173.126

China (Shanghai)

101.133.151.144, 47.102.141.56, 106.15.248.175, 47.102.99.12

China (Qingdao)

47.104.146.34, 120.27.20.55

China (Beijing)

59.110.6.146, 39.105.19.110, 47.93.61.189, 182.92.187.76

China (Zhangjiakou)

8.142.80.93, 47.92.90.166, 8.142.152.234, 39.100.37.56

China (Hohhot)

39.104.61.213

China (Ulanqab)

8.130.10.99, 39.101.66.131

China (Shenzhen)

120.76.47.88, 119.23.150.175

China (Heyuan)

47.113.195.162, 47.113.192.163

China (Guangzhou)

8.134.56.134

China (Chengdu)

47.108.26.166

China (Hong Kong)

8.210.69.249, 47.52.240.106

Singapore

47.241.44.82, 47.88.153.120

South Korea (Seoul)

8.213.130.255

Japan (Tokyo)

47.74.56.187

Malaysia (Kuala Lumpur)

47.254.195.145

Indonesia (Jakarta)

149.129.233.70

Philippines (Manila)

8.212.131.139

Thailand (Bangkok)

8.213.194.187

Germany (Frankfurt)

47.91.76.65, 47.91.89.173

UK (London)

8.208.86.103, 8.208.3.16

US (Virginia)

47.253.208.218, 47.90.252.237

US (Silicon Valley)

47.88.8.7, 47.88.7.168

Agentic SOC region IPs

Region

Public IP address

China mainland

106.14.241.32

Outside China mainland

8.222.217.173

Analyze the imported data

After the data is imported, configure parsing and detection rules so that Security Center can analyze the logs. For example, when you filter by the Azure vendor, two predefined normalization rules appear: the Microsoft Entra ID audit log normalization rule and the Microsoft Entra ID sign-in audit log normalization rule. Both use real-time consumption as the normalization method.

Billing

This integration incurs charges for the following services. Review the billing documentation for each service and estimate your costs before you begin.

The following table shows how charges are split by data source type.

Data source type

Agentic SOC charges

SLS charges

Notes

Agentic SOC dedicated collection channel

Log ingestion; log storage and write. Both consume log ingestion traffic.

Charges other than log storage and write, such as internet traffic.

Agentic SOC creates and manages the SLS resources, so Logstore storage and write charges are billed by Agentic SOC.

User Log Service

Log ingestion, which consumes log ingestion traffic.

All log-related charges, including log storage and write, and internet traffic.

The log resources are fully managed by SLS, so all log-related charges are billed by SLS.