Outgoing feed - Microsoft Azure Sentinel Outgoing Feed

This article describes how to configure outgoing feeds for a particular feed source. To see how to configure outgoing feeds in general, see Configure outgoing feeds general options.


Specifications

Transport type

Microsoft Azure Sentinel Outgoing Feed

Content type

Microsoft Azure Sentinel JSON model

Published data

See Map EclecticIQ Platform entities to Microsoft Azure Sentinel Indicators.

Requirements

  • Your Microsoft Azure tenant ID.

  • A Microsoft Azure user to set up the service application. This use should have one of these roles:

    • Global Administrator

    • Application Administrator

    • Cloud Application Administrator

  • A service application.

    This provides you with a client_id and client_secret for setting up the outgoing feed. See Set up service application on Azure.

Set up service application on Azure

Before setting up an outgoing feed with the Microsoft Azure Sentinel Outgoing Feed transport type, you must:

  1. Register a service application in Azure.

    The outgoing feed connects to your Azure Sentinel workspace using this service application.

  2. Obtain client_id and client_secret from your new service application.

    You need the client_id and client_secret to Configure the outgoing feed.

  3. Assign ThreatIndicators.ReadWrite.OwnedBy permisisons to your service application.

  4. Grant the service application tenant-wide admin consent.

  5. (Optional) Assign user or group to service application.

These steps are documented in the official Microsoft Azure Sentinel documentation.

Once done, Configure the outgoing feed.

Configure the outgoing feed

  1. Create or edit an outgoing feed.

  2. Under Transport and content, fill out these fields:

    Required fields are marked with an asterisk (*).

    Field

    Description

    Transport type*

    Select Microsoft Azure Sentinel Outgoing Feed from the drop-down menu.

    Content type*

    Select Microsoft Azure Sentinel JSON model from the drop-down menu.

    Datasets*

    Select one or more existing datasets from the drop-down menu. The menu only displays datasets that contain observables supported by the Transport type you’ve selected.

    See Supported observable types for more information.

    Update strategy*

    Select an update strategy.

    See Update strategies for Microsoft Azure Sentinel for more information.

    Supported update strategies:

    • DIFF

    • APPEND

    • REPLACE

    API URL*

    https://graph.microsoft.com/beta/

    Client ID*

    Enter the client_id for your service application.

    See Set up service application on Azure for more information.

    Client Secret*

    Enter the client_secret for your service application.

    See Set up service application on Azure for more information.

    Tenant ID*

    Enter the tenant ID of the tenant that your Azure Sentinel workspace is located on.

  3. Store your changes by selecting Save.

Map EclecticIQ Platform entities to Microsoft Azure Sentinel Indicators

When the outgoing feed runs, it looks through the selected dataset(s) and collects entities that have one or more of the selected observable types attached to them. These entities are then translated into tiIndicator objects that we send to the target Azure Sentinel instance.

Each tiIndicators object only allows an indicator to represent one observable. This means that entities which have more than one attached observable creates one indicator per observable found in the dataset(s).

The following table describes how data from EclecticIQ Platform is translated into a format that the Azure Sentinel instance can ingest:

Field name

JSON field

From EclecticIQ JSON

Description

Example

Action

action

N/A

Default for tiIndicator object.

alert

Target Product

targetProduct

N/A

Default for tiIndicator object.

Azure Sentinel

External ID

externalId

data.id

ID of EclecticIQ entity.

{http://example.com/}Indicator-611935aa-4db5-4b63-88ac-ac651634f09b

Description

description

Entity from EclecticIQ Platform. <data.title>

Indicator description containing title of packaged EclecticIQ entity.

Entity from EclecticIQ Platform. example.com

TLP Level

tlpLevel

See TLP mapping table.

amber

Confidence

confidence

See Confidence mapping table.

100

Severity

severity

See Maliciousness mapping table.

5

Threat Type

threatType

See Indicator type mapping table.

Proxy

Expiration

expirationDateTime

meta.estimated_threat_start_time + meta.half_life

Date and time when entity or observable half-life expires.

2020-04-29T07:41:21.9273279Z

Last Reported

lastReportedDateTime

meta.estimated_observed_time

Date and time indicator was observed.

2020-04-29T07:41:21.9273279Z

Tags

tags

meta.tags[n]

See Tag mapping table.

['tag name 1','tag name 2','tag name 3']

Kill Chain

killChain

if meta.taxonomy_paths[n][n] contains 'Kill chain -'

Derive kill chain phase name from tags; See also Tag mapping table.

Reconnaissance

File Hash Type

fileHashType

See File hash type table.

If indicator has a file hash, get type of file hash here.

md5

Network Source ASN

networkSourceAsn

extracts[n].value if extracts[n].kind=='asn'

If indicator has an ASN, set ASN value here.

3265

Domain Name

domainName

extracts[n].value if extracts[n].kind=='domain'

If indicator has a domain, set domain name here.

example.com

Email Sender Address

emailSenderAddress

extracts[n].value if extracts[n].kind=='email'

If indicator has an email address, set email address name here.

[email protected]

Email Source Domain

emailSourceDomain

Extract domain from emailSenderAddress

If indicator has an email address, derive domain from email address.

mail.example.com

Email Subject

emailSubject

extracts[n].value if extracts[n].kind=='email-subject'

If indicator has an email subject, set email subject.

RE: FWD: Example email subject

File Name

fileName

extracts[n].value if extracts[n].kind=='file'

If indicator has a file, set file name here.

example.docx.exe

File Hash Value

fileHashValue

extracts[n].value if extracts[n].kind has a file hash type

If indicator has a file hash type, set value of file hash here.

0c089b611e8a72f025164c29ddef09e2905cf3c8

Network IPv4

networkIPv4

extracts[n].value if extracts[n].kind=='ipv4'

If indicator has an IPv4 address, set value of IPv4 address here.

127.0.0.1

Network IPv6

networkIPv6

extracts[n].value if extracts[n].kind=='ipv6'

If indicator has an IPv6 address, set value of IPv6 address here.

::1

File Mutex Name

fileMutexName

extracts[n].value if extracts[n].kind=='mutex'

If indicator has a named mutex, set name of mutex here.

FwtSqmSession123456789_S-1-5-20

Network Port

networkPort

extracts[n].value if extracts[n].kind=='port'

If indicator has a port, set value of port here.

8080

URL

url

extracts[n].value if extracts[n].kind=='uri'

If indicator has a URL or URI, set value of URL/URI here.

https://example.com/resource/path/here.html?=query

Is Active

isActive

N/A

Default for tiIndicator object.

true

Example outgoing feed JSON submission

Where:

  • EIQ_ENTITY_ID is an EclecticIQ Platform entity identifier in the format: <EclecticIQ_Platform_URL><entity_type>-<uuid>

    For example: {https://tip.example.com}indicator-14975dea-86cd-4211-a5f8-9c2e4daab69a

  • EIQ_OBSERVABLE_ID is an EclecticIQ Platform observable identifier in the format <observable_type>:<observable_value>

    For example: email:[email protected]

$EIQ_ENTITY_ID: {
$EIQ_OBSERVABLE_ID: {
'action': 'value',
'targetProduct': 'value',
'externalId': 'value',
'description': 'value',
'tlpLevel': 'value',
'confidence': 0,
'severity': 0,
'threatType': 'value',
'expirationDateTime': 'value',
'lastReportedDateTime': 'value',
'tags': ['tag name', 'tag name 2'],
'killChain': ['tag name', 'tag name 2'],
'fileHashType': 'value',
'networkSourceAsn': 'value',
'domainName': 'value',
'emailSenderAddress': 'value',
'emailSourceDomain': 'value',
'emailSubject': 'value',
'fileName': 'value',
'fileHashValue': 'value',
'networkIPv4': 'value',
'networkIPv6': 'value',
'fileMutexName': 'value',
'networkPort': 'value',
'url': 'value',
'isActive': true
}
}

Mapping tables

Some field values in EclecticIQ Platform must be translated to match the values that Azure Sentinel expects when we submit an indicator using the outgoing feed.

For example, a confidence value of High in an EclecticIQ Platform entity is translated to 100 when the entity is submitted as a Microsoft Azure Sentinel indicator.

Map EclecticIQ entity TLP values to Azure Sentinel indicator TLP values


EclecticIQ Platform field

Azure Sentinel field

Field name

“TLP Color”

“TLP Level”

JSON field

meta.tlp_color

value[n].tlpLevel

Description

EclecticIQ TLP

Azure Sentinel indicator TLP

TLP White

White

white

TLP Green

Green

green

TLP Amber

Amber

amber

TLP Red

Red

red

Map EclecticIQ entity confidence values to Azure Sentinel indicator confidence values


EclecticIQ Platform field

Azure Sentinel field

Field name

“Confidence”

“Confidence”

JSON field

data.confidence.value

value[n].confidence

Description

EclecticIQ confidence

Azure Sentinel indicator confidence

No set confidence level (default)

None

0

Low confidence

Low

33

Medium confidence

Medium

66

High confidence

High

100

Map EclecticIQ observable maliciousness values to Azure Sentinel indicator maliciousness values


EclecticIQ Platform field

Azure Sentinel field

Field name

“Maliciousness”

“Severity”

JSON field

extracts[n]meta.classification and extracts[n].meta.confidence

value[n].severity

Description

EclecticIQ maliciousness

Azure Sentinel indicator maliciousness

Safe (default)

Safe

0

Low maliciousness

Low

1

Medium maliciousness

Medium

3

High maliciousness

High

5

Map EclecticIQ indicator type values to Azure Sentinel indicator type values


EclecticIQ Platform field

Azure Sentinel field

Field name

“Types”

“Threat Type”

JSON field

data.types[n].value

value[n].threatType

Description

EclecticIQ indicator types

Azure Sentinel indicator types

Malicious E-mail

Malicious E-mail

Phishing

IP Watchlist

IP Watchlist

WatchList

File Hash Watchlist

File Hash Watchlist

WatchList

Domain Watchlist

Domain Watchlist

WatchList

URL Watchlist

URL Watchlist

WatchList

Malware Artifacts

Malware Artifacts

Malware

C2

C2

C2

Anonymization

Anonymization

Proxy

Exfiltration

Exfiltration

WatchList

Host Characteristics

Host Characteristics

WatchList

Compromised PKI Certificate

Compromised PKI Certificate

WatchList

Login Name

Login Name

WatchList

IMEI Watchlist

IMEI Watchlist

WatchList

IMSI Watchlist

IMSI Watchlist

WatchList

Map EclecticIQ observable type (hash) to Azure Sentinel indicator hash type


EclecticIQ Platform field

Azure Sentinel field

Field name

“Type”

“File Hash Type”

JSON field

extracts[n].kind

value[n].fileHashType

Description

EclecticIQ hash type

Azure Sentinel indicator hash type

MD5 hash

hash-md5

md5

SHA1 hash

hash-sha1

sha1

SHA256 hash

hash-sha256

sha256

Map EclecticIQ tag name to Azure Sentinel indicator tag name


EclecticIQ Platform field

Azure Sentinel field

Field name

“Tags”

“Tags”

JSON field

extracts[n].tags[n]

value[n].tags[n]

Description

EclecticIQ indicator tag name

Azure Sentinel indicator tag name

Actions on Objectives

Actions on Objectives

Actions

Command and Control

Command and Control

C2

Delivery

Delivery

Delivery

Exploitation

Exploitation

Exploitation

Installation

Installation

Installation

Reconnaissance Artifacts

Reconnaissance Artifacts

Reconnaissance

Weaponization

Weaponization

Weaponization

Supported observable types

This outgoing feed supports the following observable types:

  • email

  • email-subject

  • sha1

  • sha256

  • md5

  • mutex

  • file

  • domain

  • ipv4

  • ipv6

  • uri

  • port

  • asn

Update strategies for Microsoft Azure Sentinel

The update strategy you set for the outgoing feed determines how the extension updates indicators that originate from that going feed on your Azure Sentinel instance.

Each observable type in the dataset creates one indicator for Azure Sentinel.

If an observable is updated on EclecticIQ Platform, it is treated as a new indicator.

REPLACE:

The REPLACE update strategy removes all indicators that have been previously sent by the outgoing feed. Then, it uploads all indicators, old and new, to the Azure Sentinel instance.

The feed does the following:

  1. Gets all indicator IDs of entities with supported observables in the selected dataset(s).

  2. Determines the indicator IDs that have been previously sent to the Azure Sentinel instance up to the last time the feed was run.

  3. Deletes those indicators on the Azure Sentinel instance.

  4. Updates the Azure Sentinel instance with all indicators from the dataset(s).

APPEND:

The APPEND update strategy only updates the Azure Sentinel instance with indicators that have been added to the dataset(s) since the last time the feed was run.

It does not remove indicators from Azure Sentinel when entities or observables are removed from the selected dataset(s).

The feed does the following:

  1. Determines the indicator IDs for entities and observables that have been added to the dataset(s) since the last time the feed was run.

  2. Updates the Azure Sentinel instance with the new indicators.

DIFF:

The DIFF update strategy determines the indicators that have been added and removed to the dataset(s) since the last time the feed was run. Then, on the Azure Sentinel instance, the feed adds the new indicators and deletes indicators that have been removed from the dataset(s).

The feed does the following:

    1. Determines the indicator IDs for entities and observables that have been removed from the dataset(s) or have expired since the last time the feed was run.

    2. Determines the indicator IDs of entities and observables that have been added to the dataset(s) since the last run.

  1. Updates the Azure Sentinel instance with the new indicators.

  2. Deletes indicators that have been removed from the dataset(s), or have expired.