5.1.1 Security Considerations Specific to the DHCP Server Management Protocol

DHCP server data and DHCP server operations specified by this implementation can be protected by access checks based on the identity of the RPC client.

Servers implementing this specification do not need to allow anonymous RPC connections. They need to protect DHCP access to all data and operations with access-control checks based on client identity.

RPC over named pipes do not need to be used by clients or servers implementing this specification because it is vulnerable to man in the middle (MITM) attacks. RPC over TCP/IP need to be used instead. RPC over a local procedure call is also not vulnerable to man-in-the-middle attacks and can be used if supported by the DHCP server.

Servers implementing this protocol need to require that clients request RPC_C_AUTHN_LEVEL_PKT_PRIVACY, and the servers need to enforce this in order to protect the privacy of the communication between the client and the server.