Merge pull request #103550 from chrissie926/master

Update about-iot-dps.md for encryption for data at rest

Author: PRMerger16

articles/iot-dps/about-iot-dps.md

@@ -75,8 +75,10 @@ DPS has many features, making it ideal for provisioning devices.
 * **Enrollment list** containing the complete record of devices/groups of devices that may at some point register. The enrollment list contains information about the desired configuration of the device once it registers, and it can be updated at any time.
 * **Multiple allocation policies** to control how DPS assigns devices to IoT hubs in support of your scenarios: Lowest latency, evenly weighted distribution (default), and static configuration via the enrollment list. Latency is determined using the same method as [Traffic Manager](https://docs.microsoft.com/azure/traffic-manager/traffic-manager-routing-methods#performance).
 * **Monitoring and diagnostics logging** to make sure everything is working properly.
-* **Multi-hub support** allows DPS to late-bind devices to an IoT hub at runtime. DPS can talk to hubs across multiple Azure subscriptions.
-* **Cross-region support** allows DPS to assign devices to IoT hubs in other regions.
+* **Multi-hub support** allows the Device Provisioning Service to assign devices to more than one IoT hub. The Device Provisioning Service can talk to hubs across multiple Azure subscriptions.
+* **Cross-region support** allows the Device Provisioning Service to assign devices to IoT hubs in other regions.
+* **Encryption for data at rest** allows data in Device Provisioning Service to be encrypted and decrypted transparently using 256-bit AES encryption, one of the strongest block ciphers available, and is FIPS 140-2 compliant.
+
 
 You can learn more about the concepts and features involved in device provisioning in [device concepts](concepts-device.md), [service concepts](concepts-service.md), and [security concepts](concepts-security.md).