Controller-to-device trust is the relationship that allows a managed device to accept commands, configuration, and status requests from an authorized controller. In network management systems, this trust is usually established during onboarding with credentials, certificates, shared secrets, or other enrollment data.
This trust boundary matters because it concentrates control. If an attacker can impersonate the controller, steal enrollment material, or weaken the provisioning process, they may be able to push malicious settings, add rogue devices, or take over management of the fleet. Defenders protect this relationship with strong authentication, device identity verification, protected provisioning channels, least-privilege access, and tight monitoring of new registrations and management-plane traffic. In practice, many attacks target the onboarding step, because breaking the controller-to-device trust link can scale into a fleet-wide compromise instead of a single-device flaw.