Integrations / Microsoft Sentinel
A free TAXII feed for Microsoft Sentinel
Sentinel has a TAXII data connector, and HoneyLabs runs a TAXII 2.1 server that a free account can read. You give the connector our API root, a collection ID and your API key as the password, and indicators arrive in ThreatIntelIndicators on the schedule you pick. If the free TAXII feed from the tutorial you followed has closed, this one goes into the same form.
The result
Indicators that carry their own evidence, and expire on their own
Confidence grades what is behind each indicator: 90 means a hundred or more observed attacks, 60 means a single sighting. That is what lets you alert on the top band and watchlist the rest, instead of muting a feed that fires on everything. Known research scanners are excluded, and every indicator carries a valid_until, so an address that goes quiet ages out of your workspace without a cleanup job.

An indicator is sent once, and again only when it changed
Sentinel writes a record for every indicator a feed hands it, and a feed that dates its indicators by last sighting hands over every address that is still attacking on every poll. Ours sends an indicator again only when its confidence band rose, it gained a label, or its expiry has to move. An hourly poll therefore returns what is new since the last one, and the ingestion you pay for follows the number of indicators and not the number of polls.
Labels you can filter on inside KQL
Each indicator carries its source network as asn:ASxxxx, its origin as country:XX, and the indicator kind. On paid plans the attacker collection also carries CVE probers, each labelled with the CVE ids that source went after, so 'who is probing this CVE and did any of them reach us' is a single query.
A link back to the full evidence on every hit
When a rule fires, the indicator's description names the ASN, the country and the observation window, and links to its report at honeylabs.net/lookup: first seen, the exact requests, captured payloads and client fingerprints. An analyst confirming a match does not have to take the score on trust.
Setup
- 01
Install the Threat Intelligence solution
In Sentinel, open Content hub, find the Threat Intelligence solution by Microsoft, and install it. That adds the TAXII data connector plus the rule templates that match indicators against your logs. Skip this if the connector is already present.
- 02
Get an API key
Any HoneyLabs API key works as the TAXII password, including a free one. Create the key on the dashboard; the account it belongs to is what shows up in your usage view later.
honeylabs.net/dashboard?src=sentinel, then API keys, then New key
- 03
Add the TAXII connector
Under Data connectors, open Threat Intelligence - TAXII and fill in the form. The username can be any string; only the password, your key, is checked. Hourly polling matches how often the collection changes. Indicators appear in the Threat intelligence blade within a few minutes of the first poll, with SourceSystem starting HoneyLabs.
Field Value Friendly name HoneyLabs attackers API root URL https://honeylabs.net/taxii2/api/ Collection ID 019bc26f-7216-562c-b110-16ccd9c553f6 Username taxii Password <your API key> Polling Once an hour - 04
Add the malware infrastructure collection
Optional, and a second connector entry with the same API root and credentials. This one carries the loader and command-and-control URLs pulled out of captured payloads. It is a smaller and different signal from the attacker addresses, useful on egress inspection, and it is kept separate so it does not dilute them.
Field Value Friendly name HoneyLabs malware infrastructure Collection ID e144c129-a19a-55c8-b926-dd2dfbbd8138 - 05
Turn on the matching rules
Under Analytics, enable the TI mapping rule templates for the log sources you collect: CommonSecurityLog for firewalls, ASIM network sessions, SigninLogs. Indicators arrive tagged with the friendly name you chose, so an incident says where the intel came from, and each links back to its HoneyLabs report for the full evidence.
- 06
Check what landed
One KQL query confirms the pipe end to end and shows the spread of confidence scores, which is what a threshold is set on. If this returns nothing an hour after the first poll, the connector page reports the last poll and its result.
KQLThreatIntelIndicators | where TimeGenerated >= ago(14d) | where IsActive == true and ValidUntil > now() | summarize arg_max(TimeGenerated, *) by Id | where SourceSystem startswith 'HoneyLabs' | where ObservableKey == 'ipv4-addr:value' | summarize Indicators = dcount(ObservableValue) by Confidence | order by Confidence desc
Worth knowing
- Collection IDs also accept aliases: attackers, exploiters, malware-infrastructure. The attacker collection (019bc26f-7216-562c-b110-16ccd9c553f6) is the one to point at. It grows with your plan, adding CVE probers on a paid one through the same ID with no reconfiguration.
- Indicators carry valid_until, so anything that goes quiet expires out of your workspace on its own: an attacker address 7 to 10.5 days after its last sighting, a malware URL 14 to 21 days after.
- TAXII polling does not count against your API credit quota; only REST and MCP calls are metered.
- A workbook, four analytic rules, four hunting queries and an incident-enrichment playbook are in Microsoft's Sentinel repository under Solutions/HoneyLabs (Azure/Azure-Sentinel PR 14697, merged August 2026) and are not listed in the Content hub yet. The screenshot above is that workbook. The connector plus Microsoft's own TI mapping templates are the supported path, and everything on this page works without the solution.
To check the collection outside the portal, request two objects with your key:
curl -u 'taxii:<key>' \
'https://honeylabs.net/taxii2/api/collections/attackers/objects/?limit=2'The same collections work in anything that polls TAXII 2.1 (OpenCTI, ThreatQ, EclecticIQ). For a feed of your own query, create it on the feeds page, or see the other integrations.