# Does NetSenX raise a separate anomaly alert for each industrial protocol?

No. NetSenX reads five industrial protocols, Modbus/TCP, DNP3, BACnet/IP, EtherNet/IP and S7comm, but there is no separate anomaly alert per protocol, such as one for unusual Modbus polling or odd BACnet traffic. Its OT alerts are four kinds that work across what it reads: a write to a controller from a host that is not allowed to write, traffic that crosses levels of the plant network, OT activity outside working hours, and S7comm commands such as a stop or a program download. The general detections watch the same hosts as well: beaconing, scanning, lateral movement and unusual outbound volume. If your risk assessment needs deep, protocol-specific anomaly detection, for example for a utility's telecontrol traffic, ask us what is covered before you rely on it, or run a specialist OT tool beside NetSenX. The OT features are available from the Pro plan.

FAQ: [OT and IoT](https://netsenx.com/en/faq/ot) · https://netsenx.com/en/faq/does-netsenx-raise-a-separate-alert-for-each-industrial-protocol

## Read next

- https://netsenx.com/en/ot-network-monitoring
- https://netsenx.com/en/compare

## Related questions

- [Can NetSenX block a dangerous command to a PLC?](https://netsenx.com/en/faq/can-netsenx-block-a-dangerous-command-to-a-plc)
- [Does NetSenX read PROFINET, OPC UA or IEC 60870-5-104?](https://netsenx.com/en/faq/does-netsenx-read-profinet-or-opc-ua)
- [Can a network sensor see serial fieldbus links such as Modbus RTU?](https://netsenx.com/en/faq/can-a-network-sensor-see-serial-fieldbus-links)
- [What does "never actively probed" mean for our controllers?](https://netsenx.com/en/faq/what-does-never-actively-probed-mean-for-our-controllers)
- [Do we need to change anything on our PLCs to monitor them?](https://netsenx.com/en/faq/do-we-need-to-change-anything-on-our-plcs-to-monitor-them)