Query Details

Multiple IP Entity Email Events

Query

// This query assumes a feed of threat indicators is ingested/synchronized periodically, and each synchronization ingests new indicators and only old indicators that have been modified.
// Active threat indicators in Sentinel are renovated as ThreatIntelligenceIndicator events every ~12 days.
let query_frequency = 1h;
let query_period = 14d;
let query_wait = 0h;
let table_query_lookback = 14d;
let _TIBenignProperty =
    _GetWatchlist('ID-TIBenignProperty')
    | where Notes has_any ("[SourceIPAddress]")
    | project IndicatorId, BenignProperty
;
let _TIExcludedSources = toscalar(
    _GetWatchlist('Activity-ExpectedSignificantActivity')
    | where Activity == "ThreatIndicatorSource"
    | summarize make_list(Auxiliar)
    );
let _TITableMatch = (table_start: datetime, table_end: datetime, only_new_ti: boolean, ti_start: datetime = datetime(null)) {
    // Scheduled Analytics rules have a query period limit of 14d
    let _Indicators =// materialize(
        ThreatIntelligenceIndicator
        | where TimeGenerated > ago(query_period)
        // Take the earliest TimeGenerated and the latest column info
        | summarize hint.strategy=shuffle
            minTimeGenerated = min(TimeGenerated),
            arg_max(TimeGenerated, Active, Description, ActivityGroupNames, IndicatorId, ThreatType, DomainName, Url, ExpirationDateTime, ConfidenceScore, AdditionalInformation, ExternalIndicatorId, NetworkIP, NetworkSourceIP, NetworkDestinationIP, EmailSourceIpAddress)
            by IndicatorId
        // Remove inactive or expired indicators
        | where not(not(Active) or ExpirationDateTime < now())
        // Pick indicators that contain the desired entity type
        | mv-expand IPAddress = pack_array(NetworkIP, NetworkSourceIP, NetworkDestinationIP, EmailSourceIpAddress) to typeof(string)
        | where isnotempty(IPAddress)
        | extend TI_IPAddress = IPAddress
        // Remove indicators from specific sources
        | where not(AdditionalInformation has_any (_TIExcludedSources) or Description has_any (_TIExcludedSources))
        // Remove excluded indicators with benign properties
        | join kind=leftanti _TIBenignProperty on IndicatorId, $left.IPAddress == $right.BenignProperty
        // Deduplicate indicators by IPAddress column, equivalent to using join kind=innerunique afterwards
        | summarize hint.strategy=shuffle
            minTimeGenerated = min(minTimeGenerated),
            take_any(*)
            by IPAddress
        // If we want only new indicators, remove indicators received previously
        | where not(only_new_ti and minTimeGenerated < ti_start)
    //)
    ;
    //let _IndicatorsLength = toscalar(_Indicators | summarize count());
    //let _IndicatorsPrefilter = toscalar(
    //    _Indicators
    //    | extend AuxiliarField = tostring(extract(@"([0-9A-Za-f]+)[\.\:]", 1, IPAddress))
    //    | summarize make_set_if(AuxiliarField, isnotempty(AuxiliarField), 10000)
    //);
    //let _IndicatorsPrefilterLength = array_length(_IndicatorsPrefilter);
    let _TableEvents =
        EmailEvents
        | where ingestion_time() between (table_start .. table_end)
        // Filter events that may contain indicators
        | where not(EmailDirection in ("Intra-org"))
        | mv-expand IPAddress = pack_array(SenderIPv4, SenderIPv6) to typeof(string)
        | where isnotempty(IPAddress)
        //| where not(_IndicatorsPrefilterLength < 10000 and not(IPAddress has_any (_IndicatorsPrefilter))) // "has_any" limit 10000
        //| where not(_IndicatorsLength < 1000000 and not(IPAddress in (toscalar(_Indicators | summarize make_list(TI_IPAddress))))) // "in" limit 1.000.000
        | project-rename EmailEvents_TimeGenerated = TimeGenerated
    ;
    _Indicators
    | join kind=inner hint.strategy=shuffle _TableEvents on IPAddress
    // Take only a single event by key columns
    //| summarize hint.strategy=shuffle take_any(*) by IPAddress, NetworkMessageId
    | project
        EmailEvents_TimeGenerated,
        Description, ActivityGroupNames, IndicatorId, ThreatType, DomainName, Url, ExpirationDateTime, ConfidenceScore, AdditionalInformation, TI_IPAddress, NetworkIP, NetworkSourceIP, NetworkDestinationIP, EmailSourceIpAddress,
        SenderFromAddress, SenderFromDomain, SenderMailFromAddress, SenderMailFromDomain, SenderDisplayName, SenderIPv4, SenderIPv6, AuthenticationDetails, RecipientEmailAddress, EmailDirection, Subject, EmailLanguage, UrlCount, AttachmentCount, AdditionalFields, OrgLevelPolicy, OrgLevelAction, UserLevelPolicy, UserLevelAction, EmailActionPolicy, EmailAction, DeliveryAction, DeliveryLocation, ThreatTypes, ConfidenceLevel, DetectionMethods, Connectors, NetworkMessageId, ReportId
};
union// isfuzzy=true
    // Match      current table events                                all indicators available
    _TITableMatch(ago(query_frequency + query_wait), ago(query_wait), false),
    // Match      past table events                                                          new indicators since last query execution
    _TITableMatch(ago(table_query_lookback + query_wait), ago(query_frequency + query_wait), true, ago(query_frequency))
| summarize arg_max(EmailEvents_TimeGenerated, *) by IndicatorId, NetworkMessageId
| extend
    timestamp = EmailEvents_TimeGenerated,
    IPCustomEntity = TI_IPAddress

Explanation

This KQL query is designed to identify and correlate email events with threat indicators in Microsoft Sentinel. Here's a simplified breakdown of what the query does:

  1. Setup Parameters:

    • The query defines several parameters for its operation, such as how often it runs (query_frequency), the period it covers (query_period), and how far back it looks for data (table_query_lookback).
  2. Watchlists:

    • It retrieves two watchlists: one for benign properties (_TIBenignProperty) and another for excluded sources (_TIExcludedSources). These are used to filter out non-threatening or irrelevant indicators.
  3. Threat Indicators:

    • The query fetches active threat indicators from the ThreatIntelligenceIndicator table. It filters out inactive or expired indicators and those from excluded sources. It also removes indicators with benign properties.
  4. Email Events:

    • It retrieves email events from the EmailEvents table, excluding intra-organization emails. It focuses on emails that might contain threat indicators based on IP addresses.
  5. Correlation:

    • The query joins the threat indicators with email events on matching IP addresses. This helps identify emails that are potentially associated with known threats.
  6. Union and Summarization:

    • It combines results from current and past events to ensure it captures both ongoing and newly identified threats. The results are summarized to take the most recent event for each indicator and email combination.
  7. Output:

    • The final output includes details about the threat indicators and the associated email events, such as timestamps, threat descriptions, and email metadata.

In essence, this query is used to detect and analyze email events that may be linked to known threat indicators, helping security teams identify and respond to potential threats more effectively.

Details

Jose Sebastián Canós profile picture

Jose Sebastián Canós

Released: December 13, 2023

Tables

ThreatIntelligenceIndicatorEmailEvents

Keywords

ThreatIntelligenceIndicatorEmailEvents

Operators

lethas_anyprojecttoscalarwheresummarizemake_listdatetimematerializeagoarg_maxnowmv-expandpack_arrayisnotemptyjoinkindleftantiextendbetweenproject-renameinunionby

Actions

GitHub