⚠️ HoneyForge Threat Detection

⚠️ Unpublished: This item is from a solution that is not yet published on Azure Marketplace or not installed in Content Hub.

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

↑ Back to Connectors Index


Attribute Value
Connector ID HoneyForge
Publisher BUI
Used in Solutions HoneyForge
Collection Method AMA
Connector Definition Files HoneyForge.json

The HoneyForge connector ingests deception sensor events from the HoneyForge Threat Detection Platform into Microsoft Sentinel. HoneyForge deploys hardware honeypot sensors across your network that passively listen for connection attempts. Any interaction with a sensor is, by definition, suspicious — because legitimate systems should never communicate with a decoy device.

Events are forwarded to Microsoft Sentinel in Common Event Format (CEF) via syslog. The connector provides immediate detection coverage through the bundled analytic rule, hunting queries, and operational workbook.

Tables Ingested

This connector ingests data into the following tables:

Table Selection Criteria Transformations Ingestion API Lake-Only
CommonSecurityLog DeviceProduct == "HoneyForge"
DeviceVendor == "BUI"
✓ ✓ ✓

💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.

Permissions

Resource Provider Permissions:

Custom Permissions:

Setup Instructions

⚠️ Note: These instructions were automatically generated from the connector's user interface definition file using AI and may not be fully accurate. Please verify all configuration steps in the Microsoft Sentinel portal.

NOTE: This connector uses the Common Event Format (CEF) to forward HoneyForge sensor events to Microsoft Sentinel via syslog. An ASIM parser (HoneyForgeEvent) is deployed with this solution to normalise the events to the ASIM NetworkSession schema.

1. Step 1 — Deploy the CEF syslog forwarder

Deploy a Linux machine to act as the syslog forwarder between your HoneyForge deployment and Microsoft Sentinel. This machine can be on-premises, in Azure, or in another cloud. It must have network line-of-sight to receive syslog from HoneyForge and outbound HTTPS to the Log Analytics workspace.

Requirements:

Configure HoneyForge to forward CEF-formatted sensor events to the Linux forwarder.

  1. Log in to the HoneyForge dashboard at platform.honeyforge.tech.
  2. Navigate to Settings → SIEM / Syslog.
  3. Enter the IP address of your Linux forwarder and port 514.
  4. Select CEF as the format and save.
  5. Click Send test event to verify connectivity.

For assistance configuring syslog forwarding, contact BUI at support@bui.co.za.

3. Step 3 — Validate connectivity

Allow up to 20 minutes for the first events to appear in the CommonSecurityLog table. Validate that events are arriving with the following query:

CommonSecurityLog
| where DeviceVendor =~ "BUI"
| where DeviceProduct =~ "HoneyForge"
| take 10

If no events appear after 20 minutes, run the connectivity troubleshooter:


Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

↑ Back to Connectors Index