Azure AD Connect Health Feed

Use the Microsoft Azure AD Connect Health Feed integration to get indicators from the feed.

Data Enrichment & Threat Intelligence · Microsoft Azure AD Connect Health Feed · Feed

Details

IDAzure AD Connect Health Feed
ProviderMicrosoft
CategoryData Enrichment & Threat Intelligence
From Version5.5.0
Docker Imagedemisto/btfl-soup:1.0.1.10120494
Supported ModulesAgentix XSIAM

README

Use the Microsoft Azure AD Connect Health Feed integration to get indicators from the feed.
This integration was integrated and tested with version 1 of Azure AD Connect Health Feed

Configure Azure AD Connect Health Feed in Cortex

Parameter Description Required        
feed Fetch indicators False        
feedReputation Indicator Reputation False        
feedReliability Source Reliability True        
tlp_color The Traffic Light Protocol (TLP) designation to apply to indicators fetched from the feed. More information about the protocol can be found at https://us-cert.cisa.gov/tlp False   feedExpirationPolicy   False
feedExpirationInterval   False        
feedFetchInterval Feed Fetch Interval False        
url The Microsoft Azure endpoint URL True        
feedTags Tags False        
feedBypassExclusionList Bypass exclusion list False        
insecure Trust any certificate (not secure) False        
proxy Use system proxy settings False        

Commands

You can execute these commands from the CLI, as part of an automation, or in a playbook.
After you successfully execute a command, a DBot message appears in the War Room with the command details.

azure-ad-health-get-indicators

Gets indicators from the feed.

Base Command

azure-ad-health-get-indicators

Input

Argument Name Description Required
limit The maximum number of results to return. The default value is 10. Optional

Context Output

There is no context output for this command.

Command Example


#### Context Example

{}
```

Human Readable Output

Indicators from Microsoft Azure Feed

value type
https://login.microsoftonline.com URL
https://secure.aadcdn.microsoftonline-p.com URL
https://login.windows.net URL

Configuration parameters

  • feed — Fetch indicators
  • feedReputation — Indicator Reputation
  • feedReliability — Source Reliability (required)
  • tlp_color — Traffic Light Protocol Color
  • feedExpirationPolicy —
  • feedExpirationInterval —
  • feedFetchInterval — Feed Fetch Interval
  • url — The Microsoft Azure endpoint URL (required)
  • feedTags — Tags
  • feedBypassExclusionList — Bypass exclusion list
  • insecure — Trust any certificate (not secure)
  • proxy — Use system proxy settings

Commands (1)

  • azure-ad-health-get-indicators

    Gets indicators from the feed.

Source

AzureADConnectHealthFeed.py AzureADConnectHealthFeed_test.py AzureADConnectHealthFeed.yml AzureADConnectHealthFeed_description.md command_examples.txt
Download History Raw 
## Microsoft Azure AD Connect Health web scraper:
https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-health-agent-install#outbound-connectivity-to-the-azure-service-endpoints

NOTE: As we scrape this page, we can not ensure the integrity of the fetched indicators upon a change in the source webpage.

Most IT services are moving from on-premise solutions to cloud-based solutions. The public IP addresses, domains, and URLs that function as the endpoints for these solutions are very often not fixed, and the providers of the service publish their details on their websites in a less than ideal format (i.e.: HTML) rather than through a proper REST API (i.e.: JSON).

This fact makes it very difficult for IT and Security teams to provide these services with an appropriate level of security and automation. Any changes in the HTML schema of the provider website, will break the automation and has the potential to cause serious disruption to the users and the business. The alternative is to compromise on the security posture of the organization.

One example of these providers is Microsoft, and an example of their services is Microsoft Azure AD Connect Health.

The goal of this pack is to address this issue by automating the collection of endpoint data in the form of an indicator feed. This will facilitate validation of the indicators before using them in enforcement points, for example firewalls, proxies, and more.