How to Distribute Keytos Shield Network Profiles to Your Devices in NinjaOne MDM

Overview - How to Distribute Network Profiles to Your NinjaOne-Managed Devices

NinjaOne offers a Mobile Device Management (MDM) platform that allows you to configure and manage your organization’s devices.

Once you get Keytos Shield up and running in your network, you need to configure your devices so they’ll use EAP-TLS certificate-based authentication to connect to your network. If you’re using the NinjaOne MDM to manage your devices, you can follow one of the guides to set up RADIUS authentication in NinjaOne MDM.

How Does Distributing Network Profiles via NinjaOne Work?

Pushing a network profile to a managed device in NinjaOne requires a few different pieces to properly configure trust, encryption, and authentication. This typically involves:

1. Trusted Certificate: For a device to trust your Shield identities, server endpoints, and network infrastructure, it must have your Shield’s Root CA certificate pushed to its trusted certificate store. Without this certificate, the device will not be able to establish a secure connection to Shield for network access or authentication.
2. SCEP Certificate: Every NinjaOne managed device needs its own identity and certificate, which is delivered via the Simple Certificate Enrollment Protocol (SCEP) protocol. Shield communicates with your device and with NinjaOne via the SCEP device attestation protocol to ensure that each device has a unique and trusted identity for network authentication.
3. Wi-Fi Profile: A Wi-Fi profile contains the necessary network settings, such as the SSID, security type, and authentication method, required for the device to connect to your network. This profile ensures that the device can automatically connect to the network using the appropriate credentials and certificates provisioned through NinjaOne.