Manage proprietary protocols with Horizon plugins
You can use the Microsoft Defender for IoT Horizon SDK to develop your plugins to support proprietary protocols used for your IoT and ICS devices.
- Unlimited, full support for common, proprietary, custom protocols or protocols that deviate from any standard.
- A new level of flexibility and scope for DPI development.
- A tool that exponentially expands OT visibility and control, without the need to upgrade to new versions.
- The security of allowing proprietary development without divulging sensitive information.
Use the Horizon SDK to design dissector plugins that decode network traffic so it can be processed by automated Defender for IoT network analysis programs.
Protocol dissectors are developed as external plugins and are integrated with an extensive range of Defender for IoT services, for example services that provide monitoring, alerting, and reporting capabilities.
Contact firstname.lastname@example.org for details about working with the Open Development Environment (ODE) SDK and creating protocol plugins.
Add a plugin to your sensor
- Access to the plugin developed for your proprietary protocol and the signing certificate you created for it
- Credentials for the Administrator, Cyberx, or Support users
After you've developed and tested a dissector plugin for proprietary protocols, add it to any sensors where it's needed.
To upload your plugin to a sensor:
Sign in to your sensor machine via CLI as the Administrator, Cyberx, or Support user.
/var/cyberx/properties/horizon.propertiesfile and verify that the
ui.enabledproperty is set to
Sign in to the sensor console as the Administrator, Cyberx, or Support.
Select System settings > Network monitoring > Protocols DPI (Horizon Plugins).
The Protocols DPI (Horizon Plugins) page lists all of the infrastructure plugins provided out-of-the-box by Defender for IoT and any other plugin you've created and uploaded to the sensor.
Select Upload signing certificate, and then browse to and select the certificate you created for your plugin.
Select Upload protocol plugin, and then browse to and select your plugin file.
Toggle a plugin on or off
After you've uploaded a plugin, you can toggle it on or off as needed. Sensors do not handle protocol traffic defined for a plugin that's currently toggled off (disabled).
Infrastructure plugins cannot be toggled off.
Monitor plugin performance
Use the data shown on the Protocols DPI (Horizon Plugins) page in the sensor console to understand details about your plugin usage. To help locate a specific plugin, use the Search box to enter part of all of a plugin name.
The Protocols DPI (Horizon Plugins) lists the following data per plugin:
|Plugin||Defines the plugin name|
|Type||The plugin type, including APPLICATION or INFRASTRUCTURE.|
|Time||The time that data was last analyzed using the plugin. The time stamp is updated every five seconds.|
|PPS||The number of packets analyzed per second by the plugin.|
|Bandwidth||The average bandwidth detected by the plugin within the last five seconds.|
|Malforms||The number of malform errors detected in the last five seconds. Malformed validations are used after the protocol has been positively validated. If there is a failure to process the packets based on the protocol, a failure response is returned.|
|Warnings||The number of warnings detected, such as when packets match the structure and specifications, but unexpected behavior is detected, based on the plugin warning configuration.|
|Errors||The number of errors detected in the last five seconds for packets that failed basic protocol validations for the packets that match protocol definitions.|
Horizon log data is available for export in the Dissection statistics and Dissection Logs, log files. For more information, see Export troubleshooting logs.
Create custom alert rules for Horizon-based traffic
After adding a proprietary plugin to your sensor, you might want to configure custom alert rules for your proprietary protocol. Custom, conditioned-based alert triggers and messages helps to pinpoint specific network activity and effectively update your security, IT, and operational teams.
Use custom alerts to detect traffic based on protocols and underlying protocols in a proprietary Horizon plugin, or a combination of protocol fields from all protocol layers. Custom alerts also let you write your own alert titles and messages, and handle protocol fields and values in the alert message text.
For example, in an environment running MODBUS, you may want to generate an alert when the sensor detects a write command to a memory register on a specific IP address and ethernet destination, or an alert when any access is performed to a specific IP address.
When an alert is triggered by a Horizon-based custom alert rule:
The alert is listed on the sensor and on-premises management consoles Alerts pages, and in integrated partner systems when you've configured forwarding rules.
The alert always has a severity of Critical.
The alert includes static text under the Take action section, indicating that the alert was generated by your organization’s security team.
For more information, see Create custom alert rules on an OT sensor.
For more information, see Microsoft Defender for IoT - supported IoT, OT, ICS, and SCADA protocols.
Submit and view feedback for