Abstract
The IoT is described as a smart interactive environment where devices communicate together ubiquitously sometimes in the background, performing functions on behalf of the users and offering many advanced services to them. Examples range from simple smart home applications such as ambient intelligence and remote controlling functionalities to more advanced smart cities setups. A smart IoT city for instance will encompass a network of many interconnected networks where various sensors and actuators distributed across many areas of the city share information, create knowledge and trigger actuation events. In such a dynamic and rich environment, it is vital for security to trace the source of data and verify its origin. This where data provenance in the IoT come to play. This work attempts to explore requirements and applications of data provenance in the IoT and the challenges pertaining to its realisation.
Highlights
Earlier forms of provenance appeared as a method to validate the authenticity of an artefact by examining an object’s origin, ownership or any modifications made to the item [2]
Constricted application Protocol (CoAP) for device to device communication is employed to enables Internet of Things (IoT) devices to use the Representational state transfer (REST) mechanism which is similar to HTTP
Dynamic, and heterogenous interconnected system such as that encountered in the IoT, it is vital to determine the source and origin of data
Summary
Earlier forms of provenance appeared as a method to validate the authenticity of an artefact by examining an object’s origin, ownership or any modifications made to the item [2]. In a world entangled in a mesh of connected networks i.e. the Internet of Things (IoT), provenance becomes even more vital to keep track of events, the source of information, decisions, and origin of data and the metadata. Data provenance is no longer just concerned with finding the origin of the data, but it extends to include the capacity of tracking any events or modification made to the data. Several financial institutions are required by laws to record the source and origin of each digital transaction. Information and lineage data used as provenance must possess some inherent technical features in order for it to be reliable. Some of these features are as follows:. Systems involving data provenance data need to deal with diverging aspects of ensuring that no outside entity or system is able to access the data and at the same time data within the system is readily available and shared among authorised entities for transparency[5]
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
