Security agent authentication methods

Artikel
03/28/2022

This article explains the different authentication methods you can use with the AzureIoTSecurity agent to authenticate with the IoT Hub.

For each device onboarded to Defender for IoT in the IoT Hub, a Defender-IoT-micro-agent is required. To authenticate the device, Defender for IoT can use one of two methods. Choose the method that works best for your existing IoT solution.

SecurityModule option
Device option

Authentication methods

The two methods for the Defender for IoT AzureIoTSecurity agent to perform authentication:

Defender-IoT-micro-agent authentication mode
The agent is authenticated using the Defender-IoT-micro-agent identity independently of the device identity. Use this authentication type if you would like the security agent to use a dedicated authentication method through Defender-IoT-micro-agent (symmetric key only).
Device authentication mode
In this method, the security agent first authenticates with the device identity. After the initial authentication, the Defender for IoT agent performs a REST call to the IoT Hub using the REST API with the authentication data of the device. The Defender for IoT agent then requests the Defender-IoT-micro-agent authentication method and data from the IoT Hub. In the final step, the Defender for IoT agent performs an authentication against the Defender for IoT module.

Use this authentication type if you would like the security agent to reuse an existing device authentication method (self-signed certificate or symmetric key).

See Security agent installation parameters to learn how to configure.

Authentication methods known limitations

SecurityModule authentication mode only supports symmetric key authentication.
CA-Signed certificate is not supported by Device authentication mode.

Security agent installation parameters

When deploying a security agent, authentication details must be provided as arguments. These arguments are documented in the following table.

Linux Parameter Name	Windows Parameter Name	Shorthand Parameter	Description	Options
authentication-identity	AuthenticationIdentity	aui	Authentication identity	SecurityModule or Device
authentication-method	AuthenticationMethod	aum	Authentication method	SymmetricKey or SelfSignedCertificate
file-path	FilePath	f	Absolute full path for the file containing the certificate or the symmetric key
host-name	HostName	hn	FQDN of the IoT Hub	Example: ContosoIotHub.azure-devices.net
device-id	DeviceId	di	Device ID	Example: MyDevice1
certificate-location-kind	CertificateLocationKind	cl	Certificate storage location	LocalFile or Store

When using the install security agent script, the following configuration is performed automatically. To edit the security agent authentication manually, edit the config file.

Change authentication method after deployment

When deploying a security agent with an installation script, a configuration file is automatically created.

To change authentication methods after deployment, manual editing of the configuration file is required.

C#-based security agent

Edit Authentication.config with the following parameters:

<Authentication>
  <add key="deviceId" value=""/>
  <add key="gatewayHostname" value=""/>
  <add key="filePath" value=""/>
  <add key="type" value=""/>
  <add key="identity" value=""/>
  <add key="certificateLocationKind" value="" />
</Authentication>

C-based security agent

Edit LocalConfiguration.json with the following parameters:

"Authentication" : {
    "Identity" : "",
    "AuthenticationMethod" : "",
    "FilePath" : "",
    "DeviceId" : "",
    "HostName" : ""
}

Del via