IOT Tasks
IOT Tasks
Introduction
In recent years, the Internet of Things (IoT) has gained much
attention from researchers and application developers. IoT
provides a global infrastructure for the information society,
enabling advanced services by interconnecting (physical and
virtual) things based on existing and evolving interoperable
information and communication technologies. Also, IoT will lead
to automation in nearly all fields, while also enabling advanced
applications like Smart Grid and Smart Cities. The International
Data Corporation (IDC) envisions that the worldwide IoT market
will grow to $1.7 trillion in 2020. This growth will also bring
more interest from third parties that are interested in accessing
the data that flows through these IoT devices. It's predicted
that by 2017, over 20% of businesses will struggle to adapt
their security infrastructure to address these issues. But efforts
to secure IoT have been active only in various research
initiatives, individual organizations' efforts, open source
communities, and traditional standards activities. Currently,
there is no clear architecture or framework that guides secure
IoT development for both organizations and developers. This
research takes a step to understand the security challenges in
IoT, along with the efforts that have been made from various
communities to address these issues. The effects from these
works are analyzed to understand whether they provide a
solution to the current issues and to identify the still unsolved
issues. This understanding will help to give a clearer picture of
the current state and the future direction of IoT security
research and development. This work is useful for both
developers and organizations to understand the current state of
IoT security and to guide their development or research efforts
in IoT in the right direction.
1.1 Overview of IoT Security
In the emerging era of Internet of Things (IoT), security in the
enabled devices still remains at a laggard. The concern of
security is an ongoing war faced by developers and security
professionals. At present, keeping the developments in IoT
technology in mind, most companies are just launching a
product or an app, with IoT integration happening almost
seamlessly. Very little effort is being put into the security of the
app, let alone the device. In most cases, companies are raising
the bar of security requirements after products have been
made public. This back-end approach to security is a faulty one.
The devices need to be built with security in mind from the
ground up, starting from the device development phase. This
can only happen with more education and awareness about
current vulnerabilities and threats that IoT devices face today.
Building security from the ground up means involving
everyone, from the device/hardware developers,
firmware/software developers, all the way to the network
engineers and security professionals. Today, there are
vulnerabilities at every level in an IoT environment. But without
awareness and the tools to fix these issues, the vulnerabilities
will still remain, and the cost in terms of potential risk, will be
far greater in the future. Current methods of device security are
simply not enough. With traditional devices, there exist a
number of methods and tools to keep it secure. These can vary
from firewalls, antivirus software, tools to monitor network
traffic, and so on. These methods can be quite effective in
mitigating a lot of threats to the devices. But IoT devices are a
whole new story. Devices could be anything from a sensor, to
an implantable medical device, to a washer or dryer. Current
methods of security are not versatile enough to provide ample
security for devices such as these.
It is well known that at each layer of the OSI model there will be
many different protocols, it is essential that the management
and interoperability of these protocols is agreed upon by
standard. If security reaches the desired level, it will be
necessary to secure operations both between same and
differing protocol stacks on the various objects to maintain a
global state of the object. For situations such as a multifunction
sensor/controller object, there may be the invocation of a
controller for an actuation dependent upon a sensed event, as
the network needs to be able to dynamically differentiate this
from client/server sessions of the same devices.
Conclusion