Skip to content

Commit 7d7eff6

Browse files
Merge pull request #222360 from miashapan/release-notes
Release notes
2 parents 948771e + 802dc40 commit 7d7eff6

File tree

3 files changed

+78
-2
lines changed

3 files changed

+78
-2
lines changed

articles/defender-for-iot/device-builders/concept-micro-agent-configuration.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,7 @@ For example:
3535

3636
`"CollectorsCore_PriorityIntervals"` : `"30,120,1440"`
3737

38+
3839
## Collector types and properties
3940

4041
Configure the micro agent using the following collector-specific properties and settings:
@@ -96,7 +97,7 @@ Configure the micro agent using the following collector-specific properties and
9697
| **NetworkActivity_MessageFrequency** | `Low`/`Medium`/`High` | Defines the frequency in which to send Network Activity events. | `Medium` |
9798
| **NetworkActivity_Devices** | A list of the network devices separated by a comma. <br><br>For example `eth0,eth1` | Defines the list of network devices (interfaces) that the agent will use to monitor the traffic. <br><br>If a network device isn't listed, the network raw events won't be recorded for the missing device.| `eth0` |
9899
| **NetworkActivity_CacheSize** | Positive integer | The number of Network Activity events (after aggregation) to keep in the cache between send intervals. Beyond that number, older events will be dropped (lost).| `256` |
99-
| **NetworkActivity_PacketBufferSize** | Positive integer | Tonfigure the buffer size (in bytes) that will be used to capture packets for a single device per direction (incoming or outcoming traffic). | `2097152 (=2MB)` |
100+
| **NetworkActivity_PacketBufferSize** | Positive integer | Configure the buffer size (in bytes) that will be used to capture packets for a single device per direction (incoming or outcoming traffic). | `2097152 (=2MB)` |
100101

101102
### Process collector-specific settings
102103

articles/defender-for-iot/device-builders/release-notes.md

Lines changed: 32 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,37 @@ This article lists new features and feature enhancements in Microsoft Defender f
1414
Noted features are in PREVIEW. The [Azure Preview Supplemental Terms](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) include other legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
1515

1616
For more information, see [Upgrade the Microsoft Defender for IoT micro agent](upgrade-micro-agent.md).
17+
18+
## December 2022
19+
20+
**Version 4.6.2**:
21+
22+
When upgrading the micro agent from version 4.2.* to 4.6.2, you would first need to remove the package and then reinstall it. For more information, see [Upgrade the Microsoft Defender for IoT micro agent](upgrade-micro-agent.md).
23+
24+
- **Peripheral collector**: Addition of a new collector that detects physical plugins of devices. For more information, see [Micro agent event collection - Peripheral events](concept-event-aggregation.md).
25+
26+
- **File system collector**: Addition of a new collector that monitors specified file systems. For more information, see [Micro agent event collection - File system events](concept-event-aggregation.md).
27+
28+
- **Statistics collector**: Addition of a new collector that reports for each collection cycle, data regarding the different collectors in the agent. For more information, see [Micro agent event collection - Statistics events](concept-event-aggregation.md).
29+
30+
- **System information collector**: System information collector now collects the agent type (Edge/Standalone) and version. For more information, see [Micro agent event collection - System information events](concept-event-aggregation.md).
31+
32+
- **New alerts**: Now supporting new peripheral and file system alerts. For more information, see [Micro agent security alerts](concept-agent-based-security-alerts.md).
33+
34+
- **DMI decode alternative**: Now supporting new alternative to report device information in case device does not support DMI decoder. For more information, see [How to configure DMI decoder](how-to-configure-dmi-decoder.md).
35+
36+
- **Firmware information**: Now supporting device firmware vendor and version collected using DMI decoder or its alternative. For more information, see [How to configure DMI decoder](how-to-configure-dmi-decoder.md).
37+
38+
- **Device Provisioning Service support**: Now you can use DPS to provision your micro agent and devices at scale. For more information, see [How to provision the micro agent using DPS](how-to-provision-micro-agent.md).
39+
40+
- **AMQP protocol over web socket protocol support**: Now supporting AMQP over web socket protocol that can be added after installing your micro agent. For more information, see [Add AMQP over websocket protocol support](tutorial-standalone-agent-binary-installation.md#add-amqp-protocol-support).
41+
42+
- **SBoM collector bug fix**: Now supporting collection of all packages instead of first ingested 500. For more information, see [Micro agent event collection - SBoM events](concept-event-aggregation.md).
43+
44+
- **Debian 10 ARM 64 buster support**: Now supporting Debian 10 ARM 64 devices. For more information, see [Agent portfolio overview and OS support](concept-agent-portfolio-overview-os-support.md).
45+
46+
- **22.04 Ubuntu support**: Now supporting Ubuntu 22.04 devices. For more information, see [Agent portfolio overview and OS support](concept-agent-portfolio-overview-os-support.md).
47+
1748
## September 2022
1849

1950
**Micro agent GA announcement**
@@ -22,7 +53,7 @@ Azure Defender for IoT micro agent is now generally available.
2253

2354
## July 2022
2455

25-
**Version 4.2.4**
56+
**Version 4.2.4**:
2657

2758
- **Proxy connection updates**: Now you can connect your micro-agent to an IoT Hub via a proxy. For more information, see [Connect via a proxy](tutorial-standalone-agent-binary-installation.md#connect-via-a-proxy).
2859

articles/defender-for-iot/device-builders/upgrade-micro-agent.md

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,50 @@ This article describes how to upgrade a Microsoft Defender for IoT micro agent w
1111

1212
For more information, see our [release notes for device builders](release-notes.md).
1313

14+
## Upgrade a micro agent from version 4.2.* to 4.6.2
15+
16+
When upgrading the micro agent from version 4.2.* to 4.6.2, you would first need to remove the package and then reinstall it.
17+
18+
**Standalone micro agent:**
19+
20+
1. Remove the current package. Run:
21+
22+
```bash
23+
sudo apt-get remove defender-iot-micro-agent
24+
```
25+
26+
1. Ensure that you've upgraded the apt. Run:
27+
28+
```bash
29+
sudo apt-get update
30+
```
31+
32+
1. Install the Defender for IoT micro agent on Debian or Ubuntu-based Linux distributions. Run:
33+
34+
```bash
35+
sudo apt-get install defender-iot-micro-agent
36+
```
37+
38+
**Micro agent for Edge:**
39+
40+
1. Remove the current package. Run:
41+
42+
```bash
43+
sudo apt-get remove defender-iot-micro-agent-edge
44+
```
45+
46+
1. Ensure that you've upgraded the apt. Run:
47+
48+
```bash
49+
sudo apt-get update
50+
```
51+
52+
1. Install the Defender for IoT micro agent on Debian or Ubuntu-based Linux distributions. Run:
53+
54+
```bash
55+
sudo apt-get install defender-iot-micro-agent-edge
56+
```
57+
1458
## Upgrade a standalone micro agent
1559

1660
1. Ensure that you've upgraded the apt. Run:

0 commit comments

Comments
 (0)