Skip to content

Commit 01ce822

Browse files
authored
adding endpoint details
------- cc: @batamig
1 parent cdb505a commit 01ce822

File tree

1 file changed

+3
-6
lines changed

1 file changed

+3
-6
lines changed

articles/defender-for-iot/organizations/architecture-connections.md

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -7,15 +7,12 @@ ms.date: 09/11/2022
77

88
# OT sensor cloud connection methods
99

10-
This article describes the architectures and methods supported for connecting your Microsoft Defender for IoT OT sensors to the cloud. An integral part of the Microsoft Defender for IoT service is the managed cloud service in Azure that acts as the central security monitoring portal for aggregating security information collected from network monitoring sensors and security agents. In order to ensure the security of IoT/OT at a global scale, the service supports millions of concurrent telemetry sources securely and reliably.
11-
12-
10+
This article describes the architectures and methods supported for connecting your Microsoft Defender for IoT OT sensors to the Azure portal in the cloud.
11+
OT network sensors connect to Azure to provide data about detected devices, alerts, and sensor health, to access threat intelligence packages, and more. For example, connected Azure services include IoT Hub, Blob Storage, Event Hubs, Aria, the Microsoft Download Center.
1312

1413
The cloud connection methods described in this article are supported only for OT sensor version 22.x and later. All methods provide:
1514

16-
- **Simple deployment**, requiring no extra installations in your private Azure environment, such as for an IoT Hub
17-
18-
- **Improved security**, without needing to configure or lock down any resource security settings in the Azure VNET
15+
- **Improved security**, without additional security configurations. Connect to Azure using specific and [secure firewall rules](how-to-set-up-your-network#sensor-access-to-azure-portal.md), without the need for any wildcards.
1916

2017
- **Encryption**, Transport Layer Security (TLS1.2/AES-256) provides encrypted communication between the sensor and Azure resources.
2118

0 commit comments

Comments
 (0)