Announcement: Introducing the Azure IoT Hub IP Filter

%3CLINGO-SUB%20id%3D%22lingo-sub-31137%22%20slang%3D%22en-US%22%3EAnnouncement%3A%20Introducing%20the%20Azure%20IoT%20Hub%20IP%20Filter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-31137%22%20slang%3D%22en-US%22%3E%3CP%3EAs%20more%20businesses%20turn%20to%20the%20Internet%20of%20Things%20(IoT)%2C%20security%20and%20privacy%20are%20often%20top%20of%20mind.%20Our%20goal%20at%20Microsoft%20is%20to%20keep%20our%20customers'%20IoT%20solutions%20secure.%20As%20part%20of%20our%20ongoing%20security%20efforts%2C%20Microsoft%20recently%20launched%20the%20%3CA%20title%3D%22%22%20href%3D%22https%3A%2F%2Fblogs.microsoft.com%2Fmicrosoftsecure%2F2016%2F10%2F26%2Fsecuring-the-internet-of-things-introducing-the-security-program-for-azure-iot%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3ESecurity%20Program%20for%20Azure%20IoT%3C%2FA%3E%2C%20which%20provides%20customers%20with%20a%20choice%20of%20security%20auditors%20who%20can%20assess%20their%20IoT%20solutions%20from%20device%20to%20cloud.%20Microsoft%20also%20offers%20%3CA%20title%3D%22%22%20href%3D%22https%3A%2F%2Fblogs.microsoft.com%2Fmicrosoftsecure%2F2016%2F10%2F26%2Fsecuring-the-internet-of-things-introducing-the-security-program-for-azure-iot%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ecomprehensive%20guidance%3C%2FA%3E%20on%20IoT%20security%20and%20state%20of%20the%20art%20security%20built%20into%20Azure%20IoT%20Suite%20and%20Azure%20IoT%20Hub.%20%3CSTRONG%3EToday%2C%20Microsoft%20is%20excited%20to%20announce%20another%20important%20security%20feature%3A%20IP%20filtering.%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIP%20filtering%20enables%20customers%20to%20instruct%20IoT%20Hub%20to%20only%20accept%20connections%20from%20certain%20IP%20addresses%2C%20to%20reject%20certain%20IP%20addresses%20or%20a%20combination%20of%20both.%20We%E2%80%99ve%20made%20it%20easy%20for%20administrators%20to%20configure%20these%20IP%20filtering%20rules%20for%20their%20IoT%20Hub.%20These%20rules%20apply%20any%20time%20a%20device%20or%20a%20back-end%20application%20is%20connecting%20on%20any%20supported%20protocols%20(currently%20AMQP%2C%20MQTT%2C%20AMQP%2FWS%2C%20MQTT%2FWS%2C%20HTTP%2F1).%20Any%20application%20from%20an%20IPv4%20address%20that%20matches%20a%20rejecting%20IP%20rule%20receives%20an%20unauthorized%20401%20status%20code%20without%20specific%20mention%20of%20the%20IP%20rule%20in%20the%20message.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20IP%20filter%20allows%20maximum%2010%20rules%20each%20rejecting%20or%20accepting%20an%20individual%20IPv4%20address%20or%20a%20subnet%20using%20the%20CIDR-notation%20format.%20The%20following%20two%20examples%20demonstrate%20how%20to%20blacklist%20an%20IP%20address%20and%20whitelist%20a%20certain%20subnet.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ERead%20more%20on%20%3CA%20href%3D%22https%3A%2F%2Fazure.microsoft.com%2Fen-us%2Fblog%2Fintroducing-the-azure-iot-hub-ip-filter%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EAzure%20Blogs%3C%2FA%3E%20for%20tutorials%20on%20how%20to%20Blacklist%20an%20IP%20address%20and%20Whitelist%20a%20Subnet.%26nbsp%3B%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22Introducing%20the%20Azure%20IoT%20Hub%20IP%20Filter%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F8644i753F3D335FD48892%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%227ed0e830-b115-44f3-9de1-5795770d21f7%22%20alt%3D%22Introducing%20the%20Azure%20IoT%20Hub%20IP%20Filter%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EIntroducing%20the%20Azure%20IoT%20Hub%20IP%20Filter%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId-1156044888%22%20id%3D%22toc-hId-1156044888%22%3E%26nbsp%3B%3C%2FH3%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-31137%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EInternet%20of%20Things%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EPredictive%20Maintenance%20with%20IoT%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ERemote%20Monitoring%20with%20IoT%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Former Employee

As more businesses turn to the Internet of Things (IoT), security and privacy are often top of mind. Our goal at Microsoft is to keep our customers' IoT solutions secure. As part of our ongoing security efforts, Microsoft recently launched the Security Program for Azure IoT, which provides customers with a choice of security auditors who can assess their IoT solutions from device to cloud. Microsoft also offers comprehensive guidance on IoT security and state of the art security built into Azure IoT Suite and Azure IoT Hub. Today, Microsoft is excited to announce another important security feature: IP filtering.

 

IP filtering enables customers to instruct IoT Hub to only accept connections from certain IP addresses, to reject certain IP addresses or a combination of both. We’ve made it easy for administrators to configure these IP filtering rules for their IoT Hub. These rules apply any time a device or a back-end application is connecting on any supported protocols (currently AMQP, MQTT, AMQP/WS, MQTT/WS, HTTP/1). Any application from an IPv4 address that matches a rejecting IP rule receives an unauthorized 401 status code without specific mention of the IP rule in the message.

 

The IP filter allows maximum 10 rules each rejecting or accepting an individual IPv4 address or a subnet using the CIDR-notation format. The following two examples demonstrate how to blacklist an IP address and whitelist a certain subnet.

 

Read more on Azure Blogs for tutorials on how to Blacklist an IP address and Whitelist a Subnet. 

 

Introducing the Azure IoT Hub IP FilterIntroducing the Azure IoT Hub IP Filter

 

 

 

 

0 Replies