Integrations · Microsoft Sentinel
Pull HoneyLabs intel into Microsoft Sentinel
Sentinel ships a TAXII data connector, and HoneyLabs runs a TAXII 2.1 server at honeylabs.net/taxii2/. Give the connector our API root, a collection ID, and your API key as the password, and evidence-backed indicators land in your workspace on the schedule you pick. Nothing gets deployed on the Azure side.
- 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.
https://honeylabs.net/dashboard?src=sentinel -> API keys -> 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 collections change.
Friendly name : HoneyLabs exploiters API root URL : https://honeylabs.net/taxii2/api/ Collection ID : exploiters Username : taxii Password : <your API key> Polling : Once an hour - 04
Add the second collection
Repeat the previous step with the malware-infrastructure collection to also ingest loader and C2 URLs extracted from captured payloads.
Friendly name : HoneyLabs malware infrastructure Collection ID : malware-infrastructure - 05
Turn on the matching rules
Under Analytics, enable the TI mapping rule templates for the log sources you actually collect (CommonSecurityLog for firewalls, SigninLogs, DNS). Indicators arrive tagged with the friendly name you chose, so incidents say where the intel came from. Each indicator links back to its HoneyLabs report for the full evidence.
Worth knowing
- Collection IDs accept the aliases above or their spec UUIDs: exploiters is 253ff00b-4863-571f-8949-9d05616de5b7, malware-infrastructure is e144c129-a19a-55c8-b926-dd2dfbbd8138.
- Indicators carry valid_until (7 days for exploiter IPs, 14 for malware URLs), so anything that goes quiet expires out of your workspace on its own.
- TAXII polling does not count against your API credit quota; only REST and MCP calls are metered.
- To sanity-check outside the portal: curl -u taxii:<key> 'https://honeylabs.net/taxii2/api/collections/exploiters/objects/?limit=2'
The same collections work in anything that polls TAXII 2.1 (OpenCTI, ThreatQ, EclecticIQ). For per-query feeds instead, mint one on the feeds page, or browse the other integrations.