Activate and set up your sensor
This article describes how to activate a sensor and perform initial setup.
Administrator users carry out activation when signing in for the first time and when activation management is required. Setup ensures that the sensor is configured to optimally detect and alert.
Security analysts and read-only users can't activate a sensor or generate a new password.
Sign-in and activation for administrator users
Administrators who sign in for the first time should verify that they have access to activation and password recovery files that were downloaded during sensor onboarding. If not, they need Azure security administrator, subscription contributor, or subscription owner permissions to generate these files on the Azure Defender for IoT portal.
First-time sign-in and activation checklist
Before signing in to the sensor console, administrator users should have access to:
The sensor IP address that was defined during the installation.
User sign-in credentials for the sensor. If you downloaded an ISO for the sensor, use the default credentials that you received during the installation. We recommend that you create a new Administrator user after activation.
An initial password. If you purchased a preconfigured sensor from Arrow, you need to generate a password when signing in for the first time.
The activation file associated with this sensor. The file was generated and downloaded during sensor onboarding on the Defender for IoT portal.
An SSL/TLS CA-signed certificate that your company requires.
About activation files
Your sensor was onboarded to Azure Defender for IoT in a specific management mode:
|Cloud connected mode||Information that the sensor detects is displayed in the sensor console. Alert information is also delivered through the IoT hub and can be shared with other Azure services, such as Azure Sentinel. You can also enable automatic threat intelligence updates.|
|Locally connected mode||Information that the sensor detects is displayed in the sensor console. Detection information is also shared with the on-premises management console, if the sensor is connected to it.|
A locally connected, or cloud-connected activation file was generated and downloaded for this sensor during onboarding. The activation file contains instructions for the management mode of the sensor. A unique activation file should be uploaded to each sensor you deploy. The first time you sign in, you need to upload the relevant activation file for this sensor.
Following sensor installation, a local self-signed certificate is generated and used to access the sensor console. After an administrator signs in to the console for the first time, that user is prompted to onboard an SSL/TLS certificate.
Two levels of security are available:
- Meet specific certificate and encryption requirements requested by your organization, by uploading the CA-signed certificate.
- Allow validation between the management console and connected sensors. Validation is evaluated against a certificate revocation list and the certificate expiration date. If validation fails, communication between the management console and the sensor is halted and a validation error appears in the console. This option is enabled by default after installation.
The console supports the following certificate types:
Private and Enterprise Key Infrastructure (private PKI)
Public Key Infrastructure (public PKI)
Locally generated on the appliance (locally self-signed)
We recommend that you don't use the default self-signed certificate. The certificate is not secure and should be used for test environments only. The owner of the certificate can't be validated, and the security of your system can't be maintained. Never use this option for production networks.
See Manage certificates for more information about working with certificates.
Sign in and activate the sensor
To sign in and activate:
Go to the sensor console from your browser by using the IP defined during the installation. The sign-in dialog box opens.
Enter the credentials defined during the sensor installation, or select the Password recovery option. If you purchased a preconfigured sensor from Arrow, generate a password first. For more information on password recovery, see Investigate password failure at initial sign-in.
After you sign in, the Activation dialog box opens. Select Upload and go to the activation file that you downloaded during the sensor onboarding.
Select the Sensor Network Configuration link if you want to change the sensor network configuration before activation. See Update sensor network configuration before activation.
Accept the terms and conditions.
Select Activate. The SSL/TLS certificate dialog box opens.
Define a certificate name.
Upload the CRT and key files.
Enter a passphrase and upload a PEM file if required.
Select Next. The validation screen opens. By default, validation between the management console and connected sensors is enabled.
Turn off the Enable system-wide validation toggle to disable validation. We recommend that you enable validation.
You might need to refresh your screen after uploading the CA-signed certificate.
For information about uploading a new certificate, supported certificate parameters, and working with CLI certificate commands, see Manage individual sensors.
Update sensor network configuration before activation
The sensor network configuration parameters were defined during the software installation, or when you purchased a preconfigured sensor. The following parameters were defined:
- IP address
- Default gateway
- Subnet mask
- Host name
You might want to update this information before activating the sensor. For example, you might need to change the preconfigured parameters defined by Arrow. You can also define proxy settings before activating your sensor.
To update sensor network configuration parameters:
Select the Sensor Network Configuration link form the Activation dialog box.
The parameters defined during installation are displayed. The option to define the proxy is also available. Update any settings as required and select Save.
Activate an expired license (versions under 10.0)
For users with versions prior to 10.0, your license may expire, and the following alert will be displayed.
To activate your license:
Open a case with support.
Supply support with your Activation ID number.
Support will supply you with new license information in the form of a string of letters.
Read the terms and conditions, and check the checkbox to approve.
Paste the string into space provided.
After first-time activation, the Azure Defender for IoT sensor console opens after sign-in without requiring an activation file. You need only your sign-in credentials.
After your sign in, the Azure Defender for IoT console opens.
Initial setup and learning (for administrators)
After your first sign-in, the Azure Defender for IoT sensor starts to monitor your network automatically. Network devices will appear in the device map and device inventory sections. Azure Defender for IoT will begin to detect and alert you on all security and operational incidents that occur in your network. You can then create reports and queries based on the detected information.
Initially this activity is carried out in the Learning Mode, which instructs your sensor to learn your network's usual activity. For example, the sensor learns devices discovered in your network, protocols detected in the network, and file transfers that occur between specific devices. This activity becomes your network's baseline activity.
Review and update basic system settings
Review the sensor's system settings to make sure the sensor is configured to optimally detect and alert.
Define the sensor's system settings. For example:
Define ICS (or IoT) and segregated subnets.
Define port aliases for site-specific protocols.
Define VLANs and names that are in use.
If DHCP is in use, define legitimate DHCP ranges.
Define integration with Active Directory and mail server as appropriate.
Disable learning mode
After adjusting the system settings, you can let the Azure Defender for IoT sensor run in learning mode until you feel that system detections accurately reflect your network activity.
The learning mode should run for about 2 to 6 weeks, depending on your network size and complexity. After you disable learning mode, any activity that differs from your baseline activity will trigger an alert.
To disable learning mode:
- Select System Settings and turn off the Learning option.
First-time sign-in for security analysts and read-only users
Before you sign in, verify that you have:
- The sensor IP address.
- Sign-in credentials that your administrator provided.
Console tools: Overview
You access console tools from the side menu.
|Dashboard||View an intuitive snapshot of the state of the network's security.|
|Device map||View the network devices, device connections, and device properties in a map. Various zooms, highlight, and filter options are available to display your network.|
|Device inventory||The device inventory displays a list of device attributes that this sensor detects. Options are available to:
- Sort, or filter the information according to the table fields, and see the filtered information displayed.
- Export information to a CSV file.
- Import Windows registry details.
|Alerts||Display alerts when policy violations occur, deviations from the baseline behavior occur, or any type of suspicious activity in the network is detected.|
|Reports||View reports that are based on data-mining queries.|
|Event timeline||View a timeline with information about alerts, network events (informational), and user operations, such as user sign-ins and user deletions.|
|Data mining||Generate comprehensive and granular information about your network's devices at various layers.|
|Investigation||View trends and statistics in an extensive range of widgets.|
|Risk Assessment||Display the Vulnerabilities window.|
|Users||Define users and roles with various access levels.|
|Forwarding||Forward alert information to partners, and internal sources (for example, Azure Sentinel) integrating with Defender for IoT, to email addresses, to webhook servers, and more.
See Forward alert information for details.
|System settings||Configure the system settings. For example, define DHCP settings, provide mail server details, or create port aliases.|
|Import settings||Display the Import Settings window. You can perform manual changes in a device's information.
See Import device information for details.
|Support||Contact Microsoft Support for help.|