Trust management system design for the Internet of Things A…

,Click to edit Master title style,Click to edit Master text styles,Second level,Third level,Fourth level,Fifth level,*,Click to edit Master title style,Click to edit Master text styles,Second level,Third level,Fourth level,Fifth level,*,Click to edit Master title style,Click to edit Master text styles,Second level,Third level,Fourth level,Fifth level,*,Click to edit Master title style,Click to edit Master text styles,Second level,Third level,Fourth level,Fifth level,*,Click to edit Master title style,Click to edit Master text styles,Second level,Third level,Fourth level,Fifth level,*,Click to edit Master title style,Click to edit Master text styles,Second level,Third level,Fourth level,Fifth level,*,Click to edit Master title style,Click to edit Master text styles,Second level,Third level,Fourth level,Fifth level,*,Click to edit Master title style,Click to edit Master text styles,Second level,Third level,Fourth level,Fifth level,*,Click to edit Master title style,Click to edit Master text styles,Second level,Third level,Fourth level,Fifth level,*,TRUST MANAGEMENT SYSTEM DESIGN FOR THE INTERNET OF THINGS:A CONTEXT-AWARE AND MULTI-SERVICE APPROACH,Yosra Ben Saied,Alexis Olivereau,Djamal,Zeghlache,Maryline,Laurent,Presented by Ali Asgar Sohanghpurwala,Machine to Machine(M2M)and Internet of Things(IoT)architectures becoming,prevalent,Wireless Sensor Networks(WSNs)introduced,unattended,wireless topologies with resource constrained nodes,IoT expands on WSN requirements,Wider architectures,More heterogeneous,Inconstant resource capabilities,Increased autonomy,INTRODUCTION,Nodes expected to securely communicate with external Internet nodes,but likely dont have resources to do it alone,Constraints such as computing power,battery life,limited bandwidth,Need to collaborate to meet this goal,Cooperative techniques for routing and security have been proposed in literature,Collaboration needs to be controlled,to protect against attacks,Cryptographic methods dont account for insider attacks,Cryptographically trusted nodes can lie,alter data,or selfishly refuse to collaborate,Existing WSN and MANET insufficient for IoT,WHY DOES IOT NEED A TMS?,IoT nodes providing different services assessed by same TMS,Non-malicious nodes may temporarily have low capabilities,IoT nodes are highly heterogeneous,Node owned by multiple self-interest communities,Complex malicious patterns arise with coexistence of heterogeneous and self-concerned nodes,HOW IS TMS DIFFERENT FOR IOT?,ASSESSMENT OF PRIOR TMS WRT IOT,Use past behavior to determine task-specific trust levels for each node,Eventually only the best partners for a specific service are proposed to,requesting,node,Fine-tune trust levels,even in presence of malicious and erroneous,nodes,Geographically,centralized TM servers,Multi-phase approach,OVERVIEW,Initially all nodes are assumed trustworthy,Bootstrapping period is required to gather information before results are trustworthy,Trust manager speeds up process by targeting nodes and inducing artificial interactions,Requesting node classifies behavior of assisting node as positive or negative,Evaluations are stored in trust manager,Context under which evaluations are received is important,Aging,resource capacity,etc.of evaluated node,Execution time,INITIALIZATION AND INFORMATION GATHERING,Each report R,ij,refers to jth report regarding QoS for assisting node P,i,Each report contains the following information:,REPORT INFORMATION,When a node asks for assistance,the trust manager returns a list of trustworthy assisting nodes,Five steps:,Restrict set of proxies p,i,Restrict the set of reports R,ij,for each proxy P,i,Compute weights(w,Rij,)for each report R,ij,Compute trust value T,i,for each proxy p,i,Provide requestor with list of best suited proxies,ENTITY SELECTION,Select candidates based on service requirements,Examples:,Lightweight communication may require nodes in same multi-cast group,Signature delegation schemes may require nodes dispersed in specific locations,May require neighbors in radio range,ENTITY 1:RESTRICT SET OF PROXIES P,I,Find most meaningful reports for prospective nodes,Ideal reports:,Assisting node provided the same service,Assisting node status was the same as it is now,It is likely that there wont be enough ideal reports to judge the node p,i,in specific context,We can calculate context similarity by quantifying node capabilities and service similarity,ENTITY 2:RESTRICT SET OF REPORTS,Quantifying node capability is easy:,Percentage of Battery,CPU power,Memory available,Service similarity isnt as straightforward,Estimate service similarity based on resource requirements,Of measurable resources,energy consumption is recommended by authors,ENTITY 2:QUANTIFY PARAMETERS,Report R,ij,sent by all nodes j,regarding interactions with node P,i,contains:,S,j,service provided by,C,j,capability,N,j,Note,Try to match with target values:,S,target,Current service in request,C,target,Current P,i,capability,ENTITY 2:CONTEXT SIMILARIT