Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

IoT/Embedded Security

9/25/2018
09:35 AM
Pablo Valerio
Pablo Valerio
News Analysis-Security Now
Connect Directly
Twitter
RSS
E-Mail vvv
50%
50%

Zero Trust & Network Segmentation: Keys to Securing IoT

As IoT devices become more popular both in the home and within businesses, enterprises need new approaches to security. Here's how zero trust and network segmentation can be combined to create a more robust defense.

The proliferation of Internet of Things (IoT) devices is increasing the chances of unauthorized access to network resources and critical data. Enabling policies such as "zero trust" and network segmentation can minimize the risks of data breaches.

Many organizations are still operating on the assumption that everything inside their network can be trusted. Increased insider threats and attack sophistication require businesses to abandon that belief. (See Zero Trust Means Never Trust & Always Verify.)

Not only do users need to have the right credentials to access the network, as well as specific data related to their task, their devices -- smartphones, tablets, PCs -- need to be paired with them to ensure no one else can use the credentials to log in.

(Source: iStock)
(Source: iStock)

New security measures also need to be implemented to stop potential damage from the inside. Threats inside the network are often left uninspected as they are invisible, letting them move wherever they choose to extract sensitive, valuable business data or cause substantial damage.

Never trust, always verify
The central principle of a zero-trust approach is: "Never trust, always verify." To have an effective zero-trust policy it is necessary to implement several criteria:

  • Use user location and device ID to grant access: It is not only necessary to securely identify users: To enable access to all data and resources IT needs to verify the device used and the location of that device.
  • Inspect and log all traffic: Inspecting all traffic is part of the "always verify" approach. A detailed log of all devices connecting to the network should be kept, and further analyzed by looking for changes such as time of access, location, IP addresses, type of data requested, etc. This way if a user or device shows unusual behavior accessing data or resources, it can be singled out for further inspection.
  • Have a least-privileged access strategy: As mentioned above, many organizations are trusting all users to access everything in the network. Businesses need to strictly enforce access control only to the resources every individual user needs. Additionally, limiting access to critical resources reduces the risk of spreading malware. Although sometimes this policy can create more work -- when needed to add additional resources to a user, for example -- the benefits are more significant in the long term.
  • Add additional authentication systems: User two-factor authentication should be a must right now. Additional security should be authenticating the hardware used, and the other devices connected to it.

 

Zero trust and IoT
The proliferation of IoT devices, both in the home and the office, adds a significant layer of potential threats to every organization's IT resources.

For example, a valid user accessing the corporate network with a smartphone, which in turn is connected through Bluetooth to a smartwatch, could enable an app running on the watch access to the company's network.

The same goes for code running on IoT devices running within the organization, such as thermostats, sensors and IoT gateways. That's why it is as important to limit access to IoT devices only to the resources of the network they need to connect to conduct their service.

 

Related posts:

Pablo Valerio is a technology writer whose articles have appeared in numerous publications. Follow him on Twitter: @PABL0VALERIO.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-30477
PUBLISHED: 2021-04-15
An issue was discovered in Zulip Server before 3.4. A bug in the implementation of replies to messages sent by outgoing webhooks to private streams meant that an outgoing webhook bot could be used to send messages to private streams that the user was not intended to be able to send messages to.
CVE-2021-30478
PUBLISHED: 2021-04-15
An issue was discovered in Zulip Server before 3.4. A bug in the implementation of the can_forge_sender permission (previously is_api_super_user) resulted in users with this permission being able to send messages appearing as if sent by a system bot, including to other organizations hosted by the sa...
CVE-2021-30479
PUBLISHED: 2021-04-15
An issue was discovered in Zulip Server before 3.4. A bug in the implementation of the all_public_streams API feature resulted in guest users being able to receive message traffic to public streams that should have been only accessible to members of the organization.
CVE-2021-30487
PUBLISHED: 2021-04-15
In the topic moving API in Zulip Server 3.x before 3.4, organization administrators were able to move messages to streams in other organizations hosted by the same Zulip installation.
CVE-2020-36288
PUBLISHED: 2021-04-15
The issue navigation and search view in Jira Server and Data Center before version 8.5.12, from version 8.6.0 before version 8.13.4, and from version 8.14.0 before version 8.15.1 allows remote attackers to inject arbitrary HTML or JavaScript via a DOM Cross-Site Scripting (XSS) vulnerability caused ...