Connect Threat Indicators to Azure Sentinel

By Ashwin Venugopal -

 



Plan for threat intelligence connectors

Azure Sentinel readily allows you to import the threat indicators your organization uses, which can enhance your security analysts ability to detect and prioritize known threats. Several features from Azure Sentinel then become available or are enhanced are as follows:

  • Analytics includes a set of scheduled rule templates you can enable to generate alerts and incidents based on matches of log events from your threat indicators.

  • Workbooks provide summarized information about the threat indicators imported into Azure Sentinel and any alerts generated from analytics rule that match your threat indicators.

  • Hunting queries allow security investigators to use threat indicators within the context of common hunting scenarios.

  • Notebooks can use threat indicators when you investigate anomalies and hunt for malicious behaviors.   

There are two types of Threat Intelligence Connectors- the TAXII Connector and the Threat Intelligence Platforms Connector. Both of which writes to the ThreatIntelligenceIndicator table and have different configuration procedures.

Connect the threat intelligence TAXII connector

Azure Sentinel is adjoined with TAXII 2.0 and 2.1 data sources to enable monitoring, alerting, and hunting using your threat intelligence and can be used to send threat indicators from TAXII servers to Azure Sentinel. Threat indicators can include IP addresses, domains, URLs, and file hashes. To view the connector page:

  1. Select Data connector page.
  2. Select Threat intelligence- TAXII. 
  3. Select the Open connector page on the preview pane.
  4. Specify the required and optional information in the text boxes. 

  • Friendly name (for server)
  • API root URL
  • Collection ID
  • Username
  • Password          

     5. Select Add to enable the connection.

The list of configure TAXII servers shows the currently connector TAXII servers and the last indicator received time. 

Connect the threat intelligence platforms connector

Azure Sentinel integrates with the Microsoft Graph Security API data sources to enable monitoring, alerting, and hunting using your threat intelligence. Use this connector to send threat indicators to Azure Sentinel from your Threat Intelligence Platform (TIP), such as Threat Connect, Palo Alto Networks MindMeld, MISP, or other integrated applications. Threat indicators can include IP addresses, domains, URLs, and file hashes.

Connect Azure Sentinel to your threat intelligence platform

  • Register an application in Azure Active Directory to get an application ID, application secret, Azure Active Directory tenant ID. 

  • Configure API permissions for the registered application- Add the Microsoft Graph Application permission ThreatIndicators.ReadWrite.OwnedBy to your registered application.

  • Ask your Azure AD tenant administrator to grant admin consent to the registered application for your organization. From the Azure portal- Azure Active Directory- App registrations- app name- View API permissions- Grant admin consent for tenant name.

  • Configure your TIP product or app that uses direct integration with Microsoft Graph Security tiIndicators API to send indicators to Azure Sentinel by specifying the following:
  • The values for the registered application's ID, secret, and tenant ID.
  • For the target product, specify Azure Sentinel.
  • For the action, specify alert.

  • In the Azure portal, navigate to Azure Sentinel then Data connectors and then select the Threat Intelligence Platforms (Preview) connector.

  • Select Open connector page, and then connect.

  • To view the threat indicators imported into Azure Sentinel, navigate to Azure Sentinel Logs then SecurityInsights, and lastly expand ThreatIntelligenceIndicator.          

View your Threat Indicators

The indicators are located in the ThreatIntelligenceIndicator table which is the basis for queries performed by other Azure Sentinel features such as Analytics and Workbooks. To view your threat indicators with KQL, select Logs from the General section of the Azure Sentinel menu and then run a query on the ThreatIntelligenceIndicator.














Comments

Post a Comment

Popular posts from this blog

Query, Visualize, & Monitor Data in Azure Sentinel

By Ashwin Venugopal -
Image
  Azure Sentinel Workbooks Several ready for use templates are provided by the Azure Sentinel that can be used to create your own workbook and then modify them as needed for Contoso. Most of the data connectors it uses to ingest data come with their own workbooks, but better insight can be obtained by simply looking into the data that is being ingested by using tables and visualizations, including bar and pie charts. You can also make your own workbook easily by using this data from the beginning instead of using the predefined templates. Workbook Page You can easily access the workbook page from the Azure Sentinel from the navigation pane which consists of the: Workbook header- You can add a new workbook and review the saved workbooks as well as templates that are available on the workbook page. Templates section- You can access existing workbook templates on the Templates tab. You can save some of the workbooks for quick access and they will appear on the My Workbooks tab.  From the
Read more

Planning for Implementing SAP Solutions on Azure (Part 2 of 5)

By Ashwin Venugopal -
Image
  To read part 1 please click  here To read part 3 please click  here To read part 4 please click  here To read part 5 please click  here Load Balancing The load balancer uses probe ports to determine as well as route the traffic to an active DBMS node, but of there's any failover then the most common SAP application architecture can automatically reconnect against the private virtual IP address without the need for the SAP application to reconfigure it, while the load balancer redirect the traffic against the private virtual IP address without any need for the SAP application to reconfigure. The loaf balancer also offers an option of DirectServerReturn which if configured, can help in directing the traffic from the DBMS VM to the SAP application layer directly to the application layer without routing through the load balancer. But, if it isn't configured, then the return traffic to the SAP application layer is routed through the load balancer. You can also use Azure Load Balan
Read more

Work with String Data Using KQL Statements

By Ashwin Venugopal -
Image
  Extract Data from Unstructured String Fields Unstructured string fields often contains the Security log data and requires parsing to extract data. There are multiple ways of pulling information from string fields in KQL and the two primary operators used are extract and parse.  Extract It gets a match for a regular expression from a text string. You can convert the extracted substring to the indicated type.  Arguments regex- A regular expression. captureGroup- A positive int constant indicating the capture group to extract. 0 stands for the entire match, 1 for the value matched by the first '('parenthesis')' in the regular expression, 2 or more for subsequent parenthesis.  text- A string to search. typeLiteral- An optional type literal. If provided, the extracted substring is converted to this type.  Returns If regex finds a match in text- the substring matched against the indicated capture group captureGroup, optionally converted to typeLiteral. If there's no mat
Read more