DNP3 (Distributed Network Protocol 3)
What is DNP3 (Distributed Network Protocol 3)?
DNP3 (Distributed Network Protocol 3), standardized as IEEE 1815, carries readings and control commands between a master station and field devices on electric, water and gas utility SCADA networks. AdminKit's Modbus/TCP check targets DNP3's sibling OT protocol, which shares the same often-disabled-authentication exposure on internet-facing industrial networks.
By AdminKit team, Netbase JSC · Updated
DNP3 (Distributed Network Protocol 3) is a communication protocol used across electric, water, gas and other utility SCADA systems to carry readings and control commands between a master station and field devices like remote terminal units (RTUs). It was standardized as IEEE 1815 by the DNP3 Users Group, which added an optional Secure Authentication mode on top of the original, unauthenticated protocol, but that mode is frequently left disabled in the field because it requires extra configuration and key management the original design never assumed. IANA’s service name and port number registry lists port 20000 for DNP and a separate port, 19999, for the secured dnp-sec service. An exposed DNP3 endpoint without Secure Authentication enabled will accept control commands from whoever can reach it over TCP port 20000, the same no-built-in-trust problem NIST’s operational technology security guide flags across SCADA protocols in general, and the same exposure that makes Modbus/TCP a recurring finding on industrial networks. AdminKit’s Modbus/TCP check targets that sibling protocol directly; DNP3 endpoints sit in the same OT exposure category and deserve the same internet-facing scrutiny.
Why an exposed DNP3 endpoint is risky:
- Secure Authentication is optional in IEEE 1815, and is frequently left disabled in the field.
- Without it, an endpoint accepts control commands from anyone who can reach TCP port 20000.
- The same unauthenticated-by-default pattern that makes Modbus/TCP a recurring OT finding.
AdminKit groups dNP3 (Distributed Network Protocol 3) under its machine protocols cluster — browse the AdminKit glossary index for other related terms.
Frequently asked questions
What does DNP3 carry between a master station and field devices?
Readings and control commands on electric, water, gas and other utility SCADA systems, between a master station and remote terminal units (RTUs).
Does DNP3 authenticate commands by default?
No -- the DNP3 Users Group added an optional Secure Authentication mode on top of the original, unauthenticated protocol, but it's frequently left disabled because it requires extra configuration and key management the original design never assumed.
What happens if an internet-facing DNP3 endpoint doesn't have Secure Authentication enabled?
It accepts control commands from whoever can reach it over TCP port 20000, with no built-in trust check on who sent them.
What standard formalizes DNP3?
IEEE 1815, developed with input from the DNP3 Users Group.