Microsoft Threat Intelligence Matching Analytics

Published Jul 28 2021 10:01 AM 7,695 Views
Microsoft

Introduction

Azure Sentinel is a cloud native SIEM solution that allows various ways to bring your own threat intelligence data (BYOTI) like STIX/TAXII and from various Threat Intelligence Platforms.

Apart from bringing in your own threat intelligence data, you can also reference threat intelligence data produced by Microsoft for detection and analysis.

Today we are announcing launch of a new analytic rule called Microsoft Threat Intelligence Matching analytics that matches Microsoft generated threat intelligence data with your logs and generates high fidelity alerts/incidents with appropriate severity based on the context of the log. Once a match is generated, the indicator is published to your threat intelligence repository in Azure Sentinel.

 

In this blog, we will cover:

  1. Details and working of the Microsoft Threat Intelligence Matching analytics
  2. How to enable Microsoft Threat Intelligence Matching analytics
  3. Log sources and threat intelligence types used for matching by this rule
  4. Alert grouping for incident generation and searching IOC’s published by this rule

 

Details and working of the Microsoft Threat Intelligence Matching analytics

Microsoft Threat Intelligence matching analytics is an out of the box analytic rule offered to all Azure Sentinel customers. This rule matches your log data with Microsoft generated threat intelligence. Microsoft has a vast repository of threat intelligence data, and this analytic rule uses a subset of this threat intelligence data to generate high fidelity alerts and incidents for SOC teams to triage.

Currently, this rule matches domain indicators against the following log sources:

  1. Common Security Logs (CEF)
  2. DNS logs
  3. Syslog

How to enable Microsoft Threat Intelligence Matching analytics

Microsoft Threat Intelligence matching analytics can be discovered in the Analytic menu of Azure Sentinel.

Follow the below steps to enable this rule:

  1. Open the Azure portal and navigate to the Azure Sentinel service.
  2. Choose the workspace in which you would like to enable this rule.
  3. Select Analytics from the menu and search for “Microsoft Threat Intelligence Analytics” in the Rule Templates tab.
  4. Click the Create Rule button and make the status of the rule as Enabled.
  5. Click the Next button and review all the details. Click Save.
  6. Now the rule is enabled and will show up in the Active Rules tab.

Image 1.png

 

Log sources and threat intelligence types used for matching by this rule

The Threat Intelligence Matcing analytic rule matches Microsoft threat intelligence with your log data. Currently, the following types of logs are available for matching:

1. Common Security Logs (CEF):

  • Matching is done for all CEF logs that are ingested in the CommonSecurityLog table of log analytics except for one that have DeviceVendor as “Cisco”.
  • To match Microsoft generated threat intelligence with CEF logs, please have the domain mapped in the “RequestURL” field of the CEF log. 

2. DNS logs

  • Matching is done for all DNS logs which are lookup DNS queries from clients to DNS services (SubType == "LookupQuery"). Threat Intelligence matching analytics only processes DNS queries for IPv4 (QueryType=”A”) and IPv6 queries(QueryType=” AAAA”).
  • To match Microsoft generated threat intelligence with DNS logs, no manual mapping of columns is needed. All columns are standard from Windows DNS Server. The domains will be in “Name” column by standard.

3. Syslog

  • Matching is done for Syslog events with Facility as “cron”. This will be extended to additional log types in the future.
  • To match Microsoft generated threat intelligence with Syslog, no manual mapping of columns is needed as the details come in the “SyslogMessage” field of the Syslog by default. The rule will parse the domain from the SyslogMessage.

Alert grouping for incident generation and searching IOC’s published by this rule

The Microsoft Threat Intelligence matching analytic generates alert every time a match is received. The rule performs alert grouping while generating incidents. The alerts are grouped on a per observable basis over a 24-hour timeframe. For example, all alerts generated in a 24-hour duration for a match with domain “abc.com” will be grouped in a single incident.

To triage through incidents generated by this analytic rule, you can follow the below steps:

  1. Open the Azure portal and navigate to the Azure Sentinel service.
  2. Choose the workspace in which you have enabled this rule.
  3. Select Incidents from the menu and search for “Microsoft threat Intelligence Analytics”.
  4. If you have any incidents they will show up in the grid of incidents.
  5. Click on the View full details button to view entities and other details about the incident like alerts.

Image 2.png

Once a match is received, the indicator is also published to the ThreatIntelligenceIndicators table of log analytics and shows up in the Threat Intelligence menu. The indicators are stamped with the Source as “Microsoft Threat Intelligence Analytics”.

 

Image 3.png

 

Image 4.png

 

Conclusion

Hopefully, this article has helped you understand how to leverage Microsoft generated threat intelligence matching analytics for generating high fidelity alerts and incidents and triage through them using the information provided with the indicator of compromise (IOC) published to the workspace.

3 Comments
Occasional Contributor

Just curious why CEF matching excludes Cisco?

Contributor

Ref. exclusion of Cisco,  my guess is that is due to the fact  that Cisco  ASA logs are being converted to CEF after the threat intel match. Cisco ASAs don't support CEF and Sentinel is parsing those logs and converts them to CEF in the background (they are the only type of devices that get this special treatment). 

New Contributor

I don't find the Microsoft Threat Intelligence Analytics rule in the Rule Templates tab? Do I just wait for it to be flighted in my client's tenant?

 

%3CLINGO-SUB%20id%3D%22lingo-sub-2525605%22%20slang%3D%22en-US%22%3EMicrosoft%20Threat%20Intelligence%20Matching%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2525605%22%20slang%3D%22en-US%22%3E%3CP%3E%3CFONT%20size%3D%225%22%3E%3CSTRONG%3EIntroduction%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%224%22%3EAzure%20Sentinel%20is%20a%20cloud%20native%20SIEM%20solution%20that%20allows%20various%20ways%20to%20bring%20your%20own%20threat%20intelligence%20data%20(BYOTI)%20like%20STIX%2FTAXII%20and%20from%20various%20Threat%20Intelligence%20Platforms.%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%224%22%3EApart%20from%20bringing%20in%20your%20own%20threat%20intelligence%20data%2C%20you%20can%20also%20reference%20threat%20intelligence%20data%20produced%20by%20Microsoft%20for%20detection%20and%20analysis.%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%224%22%3EToday%20we%20are%20announcing%20launch%20of%20a%20new%20analytic%20rule%20called%20Microsoft%20Threat%20Intelligence%20Matching%20analytics%20that%20matches%20Microsoft%20generated%20threat%20intelligence%20data%20with%20your%20logs%20and%20generates%20high%20fidelity%20alerts%2Fincidents%20with%20appropriate%20severity%20based%20on%20the%20context%20of%20the%20log.%20Once%20a%20match%20is%20generated%2C%20the%20indicator%20is%20published%20to%20your%20threat%20intelligence%20repository%20in%20Azure%20Sentinel.%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%224%22%3EIn%20this%20blog%2C%20we%20will%20cover%3A%3C%2FFONT%3E%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3EDetails%20and%20working%20of%20the%20Microsoft%20Threat%20Intelligence%20Matching%20analytics%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3EHow%20to%20enable%20Microsoft%20Threat%20Intelligence%20Matching%20analytics%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3ELog%20sources%20and%20threat%20intelligence%20types%20used%20for%20matching%20by%20this%20rule%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3EAlert%20grouping%20for%20incident%20generation%20and%20searching%20IOC%E2%80%99s%20published%20by%20this%20rule%3C%2FFONT%3E%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%225%22%3E%3CSTRONG%3EDetails%20and%20working%20of%20the%20Microsoft%20Threat%20Intelligence%20Matching%20analytics%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%224%22%3EMicrosoft%20Threat%20Intelligence%20matching%20analytics%20is%20an%20out%20of%20the%20box%20analytic%20rule%20offered%20to%20all%20Azure%20Sentinel%20customers.%20This%20rule%20matches%20your%20log%20data%20with%20%3CSTRONG%3EMicrosoft%20generated%20%3C%2FSTRONG%3Ethreat%20intelligence.%20Microsoft%20has%20a%20vast%20repository%20of%20threat%20intelligence%20data%2C%20and%20this%20analytic%20rule%20uses%20a%20subset%20of%20this%20threat%20intelligence%20data%20to%20generate%20high%20fidelity%20alerts%20and%20incidents%20for%20SOC%20teams%20to%20triage.%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%224%22%3ECurrently%2C%20this%20rule%20matches%20%3CSTRONG%3Edomain%3C%2FSTRONG%3E%20indicators%20against%20the%20following%20log%20sources%3A%3C%2FFONT%3E%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3ECommon%20Security%20Logs%20(CEF)%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3EDNS%20logs%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3ESyslog%3C%2FFONT%3E%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%3CFONT%20size%3D%225%22%3E%3CSTRONG%3EHow%20to%20enable%20Microsoft%20Threat%20Intelligence%20Matching%20analytics%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%224%22%3EMicrosoft%20Threat%20Intelligence%20matching%20analytics%20can%20be%20discovered%20in%20the%20Analytic%20menu%20of%20Azure%20Sentinel.%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%224%22%3EFollow%20the%20below%20steps%20to%20enable%20this%20rule%3A%3C%2FFONT%3E%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3EOpen%20the%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fportal.azure.com%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3EAzure%20portal%3C%2FA%3E%26nbsp%3Band%20navigate%20to%20the%26nbsp%3B%3CSTRONG%3EAzure%20Sentinel%3C%2FSTRONG%3E%26nbsp%3Bservice.%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3EChoose%20the%26nbsp%3B%3CSTRONG%3Eworkspace%3C%2FSTRONG%3E%26nbsp%3Bin%20which%20you%20would%20like%20to%20enable%20this%20rule.%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3ESelect%26nbsp%3B%3CSTRONG%3EAnalytics%3C%2FSTRONG%3E%26nbsp%3Bfrom%20the%20menu%20and%20search%20for%20%E2%80%9CMicrosoft%20Threat%20Intelligence%20Analytics%E2%80%9D%20in%20the%20%3CSTRONG%3ERule%20Templates%3C%2FSTRONG%3E%20tab.%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3EClick%20the%20%3CSTRONG%3ECreate%20Rule%20%3C%2FSTRONG%3Ebutton%20and%20make%20the%20status%20of%20the%20rule%20as%20%3CSTRONG%3EEnabled.%20%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3EClick%20the%20Next%20button%20and%20review%20all%20the%20details.%20Click%20Save.%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3ENow%20the%20rule%20is%20enabled%20and%20will%20show%20up%20in%20the%20%3CSTRONG%3EActive%20Rules%3C%2FSTRONG%3E%20tab.%3C%2FFONT%3E%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%3CFONT%20size%3D%224%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Image%201.png%22%20style%3D%22width%3A%20624px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F294164i39D42DAB8A563B28%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Image%201.png%22%20alt%3D%22Image%201.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%225%22%3E%3CSTRONG%3ELog%20sources%20and%20threat%20intelligence%20types%20used%20for%20matching%20by%20this%20rule%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%224%22%3EThe%20Threat%20Intelligence%20Matcing%20analytic%20rule%20matches%20Microsoft%20threat%20intelligence%20with%20your%20log%20data.%20Currently%2C%20the%20following%20types%20of%20logs%20are%20available%20for%20matching%3A%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%224%22%3E%3CSTRONG%3E1.%20Common%20Security%20Logs%20(CEF)%3A%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3EMatching%20is%20done%20for%20all%20CEF%20logs%20that%20are%20ingested%20in%20the%20%3CEM%3ECommonSecurityLog%20%3C%2FEM%3Etable%20of%20log%20analytics%20except%20for%20one%20that%20have%20DeviceVendor%20as%20%E2%80%9CCisco%E2%80%9D.%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3ETo%20match%20Microsoft%20generated%20threat%20intelligence%20with%20CEF%20logs%2C%20please%20have%20the%20domain%20mapped%20in%20the%20%E2%80%9CRequestURL%E2%80%9D%20field%20of%20the%20CEF%20log.%26nbsp%3B%3C%2FFONT%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CFONT%20size%3D%224%22%3E%3CSTRONG%3E2.%26nbsp%3B%3C%2FSTRONG%3E%3CSTRONG%3EDNS%20logs%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3EMatching%20is%20done%20for%20all%20DNS%20logs%20which%20are%20lookup%20DNS%20queries%20from%20clients%20to%20DNS%20services%20(SubType%20%3D%3D%20%22LookupQuery%22).%20Threat%20Intelligence%20matching%20analytics%20only%20processes%20DNS%20queries%20for%20IPv4%20(QueryType%3D%E2%80%9DA%E2%80%9D)%20and%20IPv6%20queries(QueryType%3D%E2%80%9D%20AAAA%E2%80%9D).%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3ETo%20match%20Microsoft%20generated%20threat%20intelligence%20with%20DNS%20logs%2C%20no%20manual%20mapping%20of%20columns%20is%20needed.%20All%20columns%20are%20standard%20from%20Windows%20DNS%20Server.%20The%20domains%20will%20be%20in%20%E2%80%9CName%E2%80%9D%20column%20by%20standard.%3C%2FFONT%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CFONT%20size%3D%224%22%3E%3CSTRONG%3E3.%20Syslog%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3EMatching%20is%20done%20for%20Syslog%20events%20with%20Facility%20as%20%E2%80%9Ccron%E2%80%9D.%20This%20will%20be%20extended%20to%20additional%20log%20types%20in%20the%20future.%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3ETo%20match%20Microsoft%20generated%20threat%20intelligence%20with%20Syslog%2C%20no%20manual%20mapping%20of%20columns%20is%20needed%20as%20the%20details%20come%20in%20the%20%E2%80%9CSyslogMessage%E2%80%9D%20field%20of%20the%20Syslog%20by%20default.%20The%20rule%20will%20parse%20the%20domain%20from%20the%20SyslogMessage.%3C%2FFONT%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CFONT%20size%3D%225%22%3E%3CSTRONG%3EAlert%20grouping%20for%20incident%20generation%20and%20searching%20IOC%E2%80%99s%20published%20by%20this%20rule%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%224%22%3EThe%20Microsoft%20Threat%20Intelligence%20matching%20analytic%20generates%20alert%20every%20time%20a%20match%20is%20received.%20The%20rule%20performs%20alert%20grouping%20while%20generating%20incidents.%20The%20alerts%20are%20grouped%20on%20a%20per%20observable%20basis%20over%20a%2024-hour%20timeframe.%20For%20example%2C%20all%20alerts%20generated%20in%20a%2024-hour%20duration%20for%20a%20match%20with%20domain%20%E2%80%9Cabc.com%E2%80%9D%20will%20be%20grouped%20in%20a%20single%20incident.%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%224%22%3ETo%20triage%20through%20incidents%20generated%20by%20this%20analytic%20rule%2C%20you%20can%20follow%20the%20below%20steps%3A%3C%2FFONT%3E%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3EOpen%20the%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fportal.azure.com%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3EAzure%20portal%3C%2FA%3E%26nbsp%3Band%20navigate%20to%20the%26nbsp%3B%3CSTRONG%3EAzure%20Sentinel%3C%2FSTRONG%3E%26nbsp%3Bservice.%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3EChoose%20the%26nbsp%3B%3CSTRONG%3Eworkspace%3C%2FSTRONG%3E%26nbsp%3Bin%20which%20you%20have%20enabled%20this%20rule.%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3ESelect%26nbsp%3B%3CSTRONG%3EIncidents%3C%2FSTRONG%3E%26nbsp%3Bfrom%20the%20menu%20and%20search%20for%20%E2%80%9CMicrosoft%20threat%20Intelligence%20Analytics%E2%80%9D.%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3EIf%20you%20have%20any%20incidents%20they%20will%20show%20up%20in%20the%20grid%20of%20incidents.%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3EClick%20on%20the%20%3CSTRONG%3EView%20full%20details%20%3C%2FSTRONG%3Ebutton%20to%20view%20entities%20and%20other%20details%20about%20the%20incident%20like%20alerts.%3C%2FFONT%3E%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%3CFONT%20size%3D%224%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Image%202.png%22%20style%3D%22width%3A%20624px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F294165i206CADAC84F73CD6%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Image%202.png%22%20alt%3D%22Image%202.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%224%22%3EOnce%20a%20match%20is%20received%2C%20the%20indicator%20is%20also%20published%20to%20the%20%3CEM%3EThreatIntelligenceIndicators%3C%2FEM%3E%20table%20of%20log%20analytics%20and%20shows%20up%20in%20the%20Threat%20Intelligence%20menu.%20The%20indicators%20are%20stamped%20with%20the%20Source%20as%20%E2%80%9CMicrosoft%20Threat%20Intelligence%20Analytics%E2%80%9D.%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%224%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Image%203.png%22%20style%3D%22width%3A%20527px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F294166i3FA04D6E11FBE345%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Image%203.png%22%20alt%3D%22Image%203.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%224%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Image%204.png%22%20style%3D%22width%3A%20528px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F294167i29B10D79F80AFD2C%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Image%204.png%22%20alt%3D%22Image%204.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%225%22%3E%3CSTRONG%3EConclusion%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%224%22%3EHopefully%2C%20this%20article%20has%20helped%20you%20understand%20how%20to%20leverage%20Microsoft%20generated%20threat%20intelligence%20matching%20analytics%20for%20generating%20high%20fidelity%20alerts%20and%20incidents%20and%20triage%20through%20them%20using%20the%20information%20provided%20with%20the%20indicator%20of%20compromise%20(IOC)%20published%20to%20the%20workspace.%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-2525605%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRONG%3E%26nbsp%3BMicrosoft%20Threat%20Intelligence%20Matching%20Analytics%20now%20available%20in%20Public%20cloud%20!!%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2595826%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Threat%20Intelligence%20Matching%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2595826%22%20slang%3D%22en-US%22%3E%3CP%3EI%20don't%20find%20the%26nbsp%3BMicrosoft%20Threat%20Intelligence%20Analytics%20rule%20in%20the%20Rule%20Templates%20tab%3F%20Do%20I%20just%20wait%20for%20it%20to%20be%20flighted%20in%20my%20client's%20tenant%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2595269%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Threat%20Intelligence%20Matching%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2595269%22%20slang%3D%22en-US%22%3E%3CP%3ERef.%20exclusion%20of%20Cisco%2C%26nbsp%3B%20my%20guess%20is%20that%20is%20due%20to%20the%20fact%26nbsp%3B%20that%20Cisco%26nbsp%3B%20ASA%20logs%20are%20being%20converted%20to%20CEF%20after%20the%20threat%20intel%20match.%20Cisco%20ASAs%20don't%20support%20CEF%20and%20Sentinel%20is%20parsing%20those%20logs%20and%20converts%20them%20to%20CEF%20in%20the%20background%20(they%20are%20the%20only%20type%20of%20devices%20that%20get%20this%20special%20treatment).%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2594291%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Threat%20Intelligence%20Matching%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2594291%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20curious%20why%20CEF%20matching%20excludes%20Cisco%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Co-Authors
Version history
Last update:
‎Jul 28 2021 10:01 AM
Updated by:
www.000webhost.com