Download presentation
Presentation is loading. Please wait.
Published byDarrell Harrison Modified over 9 years ago
1
CHARLES UNIVERSITY IN PRAGUE http://d3s.mff.cuni.cz faculty of mathematics and physics CHARLES UNIVERSITY IN PRAGUE http://d3s.mff.cuni.cz faculty of mathematics and physics CHARLES UNIVERSITY IN PRAGUE http://d3s.mff.cuni.cz faculty of mathematics and physics Security and Trust in Data Sharing Smart Cyber-Physical Systems Ondřej Štumpf, Tomáš Bureš, Vladimír Matěna matena@d3s.mff.cuni.cz SANCS‘15
2
What we are dealing with sCPS (Smart Cyber Physical Systems) Next generation ICT Embedded Real time Interconnected Collaborating
3
Motivation for security and trust in sCPS Owner: David Hill Speed: 48 Km/h GPS:14.450,40.325 Owner: John Doe Speed: 45 Km/h GPS:14.451,40.321 Collision avoidance Owner record inspection Owner: Police dep. Speed: 42Km/h GPS:14.448,40.323 POLICE
4
Motivation for security and trust in sCPS Owner, Speed, GPS Owner: David Hill Speed: 48 Km/h GPS:14.450,40.325 Owner: John Doe Speed: 45 Km/h GPS:14.451,40.321 Owner: Police dep. Speed: 42Km/h GPS:14.448,40.323 POLICE Speed, GPS
5
Motivation for security and trust in sCPS Owner: David Hill Speed: 48 Km/h GPS:14.450,40.325 City: Prague In Pursuit: no Owner: Police dep. Speed: 42Km/h GPS:14.448,40.323 POLICE City: Berlin In Pursuit: no Owner: Police dep. Speed: 42Km/h GPS:14.428,41.326 POLICE City: Berlin In Pursuit: yes Owner: Police dep. Speed: 42Km/h GPS:14.438,41.342 POLICE
6
Problem definition Complex access control and trust management Open-ended and dynamic systems Partitioned networks Lack of systematic approach in engineering Separation of security and trust
7
Related approaches ACL (Access control lists) and RBACm
8
Related approaches ACL (Access control lists) and RBACm Do not capture complex security
9
Related approaches ACL (Access control lists) and RBACm Do not capture complex security RBAC (Role Based Access Control)
10
Related approaches ACL (Access control lists) and RBACm Do not capture complex security RBAC (Role Based Access Control) Do not capture dynamic systems
11
Related approaches ACL (Access control lists) and RBACm Do not capture complex security RBAC (Role Based Access Control) Do not capture dynamic systems dRBAC (Distributed Role Based Access Control)
12
Related approaches ACL (Access control lists) and RBACm Do not capture complex security RBAC (Role Based Access Control) Do not capture dynamic systems dRBAC (Distributed Role Based Access Control) Need to verify trust chains Split security and trust Does not work well on partitioned networks
13
Proposed solution Based on RBAC and dRBAC Security and trust on the level of architecture Roles assigned to components Roles can base on other roles i.e. role StatePolice implies MunicipalPolice(*) Access control and trust for component data i.e. Vehicle knowledge Owner read by StatePolice only Roles parametrized by knowledge i.e. PoliceVehicle[CityOfJurisdiction] cdRBAC (Context Dependent Role Based Access Control)
14
cdRBAC: Realization Public key Private key Owner Role: idEntity[42] Role: idEntity[43] Role: Police[Prague] POLICE Speed GPS
15
cdRBAC: Realization Public key Private key Owner Role: IdEntity[42] IdEntity 42 Role: IdEntity[43] IdEntity 43 Role: Police[Prague] POLICE Police Prague Speed GPS Public/private key pairs are assigned to each role and each role parameter
16
cdRBAC: Realization Public key Private key Owner Role: IdEntity[42] IdEntity 42 Role: IdEntity[43] IdEntity 43 Role: Police[Prague] POLICE Police Prague Speed GPS Offline authority bootstraps the system by assigning key pairs to roles and static parameters.
17
cdRBAC: Realization Public key Private key Owner Role: IdEntity[42] IdEntity 42 Role: IdEntity[43] IdEntity 43 Role: Police[Prague] POLICE Police Prague Speed GPS
18
cdRBAC: Realization Public key Private key Owner Police Role: IdEntity[42] IdEntity 42 Role: IdEntity[43] IdEntity 43 Role: Police[Prague] POLICE Police Prague Speed GPS
19
cdRBAC: Realization Public key Private key Owner Police Prague Role: IdEntity[42] IdEntity 42 Role: IdEntity[43] IdEntity 43 Role: Police[Prague] POLICE Police Prague Speed GPS
20
cdRBAC: Realization Public key Private key Owner Police Prague Role: IdEntity[42] IdEntity 42 Role: IdEntity[43] IdEntity 43 Role: Police[Prague] POLICE Police Prague Speed GPS If the knowledge needs to be read by multiple roles it is send multiple times.
21
cdRBAC: Realization Public key Private key Role: Police[Prague] POLICE Police Role: PraguePolice PraguePolice Prague PraguePolice signed by Note: PraguePolice can be also realized by role Police with parameter Prague. PraguePolice was used for the sake of simplicity.
22
cdRBAC: Realization Public key Private key Role: Police[Prague] POLICE Police Prague PraguePolice signed by Role: IdEntity[42] IdEntity 42 Role: IdEntity[43] IdEntity 43
23
Component: PoliceVehicle DEECo as a reference sCPS Owner: John Doe Speed: 45 Km/h GPS:14.451,40.321 Owner: Police dep. Speed: 42Km/h GPS:14.448,40.323 POLICE Local Knowledge Others: [{},{},…] Owner: David Hill Speed: 48 Km/h GPS:14.450,40.325 Component: Vehicle
24
Component: PoliceVehicle DEECo as a reference sCPS Owner: John Doe Speed: 45 Km/h GPS:14.451,40.321 Owner: Police dep. Speed: 42Km/h GPS:14.448,40.323 POLICE Collision avoidance process @10ms Local Knowledge Others: [{},{},…] Owner: David Hill Speed: 48 Km/h GPS:14.450,40.325 Component: Vehicle
25
Component: PoliceVehicle Ensemble: Driver info Ensemble: Crash avoidance DEECo as a reference sCPS Owner: John Doe Speed: 45 Km/h GPS:14.451,40.321 Owner: Police dep. Speed: 42Km/h GPS:14.448,40.323 POLICE Collision avoidance process @10ms Local Knowledge Others: [{},{},…] Owner: David Hill Speed: 48 Km/h GPS:14.450,40.325 Component: Vehicle
26
Component: PoliceVehicle Ensemble: Driver info Ensemble: Crash avoidance Condition: distance < 50m Mapping: Speed, GPS -> Others DEECo as a reference sCPS Owner: John Doe Speed: 45 Km/h GPS:14.451,40.321 Owner: Police dep. Speed: 42Km/h GPS:14.448,40.323 POLICE Collision avoidance process @10ms Local Knowledge Others: [{},{},…] Owner: David Hill Speed: 48 Km/h GPS:14.450,40.325 Component: Vehicle
27
Component: PoliceVehicle Ensemble: Driver info Ensemble: Crash avoidance Condition: distance < 50m Mapping: Speed, GPS -> Others DEECo as a reference sCPS Owner: John Doe Speed: 45 Km/h GPS:14.451,40.321 Owner: Police dep. Speed: 42Km/h GPS:14.448,40.323 POLICE Local Knowledge Owner: John Doe Speed: 45 Km/h GPS:14.451,40.321 Replica @15ms Others: [{},{},…] Owner: David Hill Speed: 48 Km/h GPS:14.450,40.325 Collision avoidance process @10ms Component: Vehicle Owner: John Doe Speed: 45 Km/h GPS:14.451,40.321 Owner: Police dep. Speed: 42Km/h GPS:14.448,40.323 POLICE
28
DEECo as a reference sCPS Components are objects in the system Knowledge is internal data of the component Process is a task on the local knowledge Ensemble is an knowledge exchange mechanism Knowledge mapping based on condition DEECo (Dependable Emergent Ensembles of Components).
29
cdRBAC: DEECo extension Standard DEECo DSL component Vehicle knowledge: id, owner, GPS,... process updateGPS(out GPS) {... } component PoliceVehicle extends Vehicle knowledge: nearby,... process checkOffenders(in nearby) ensemble UpdateVehiclesNearby: coordinator: PoliceVehicle member: Vehicle membership: isCloseBy(coord.GPS, mbr.GPS) exchange: coord.nearby += mbr.owner Extended DEECo DSL role IdEntity(id [const]) role StatePolice component Vehicle hasRole IdEntity(id) knowledge [public]: position knowledge [public read, const write]: id knowledge [StatePolice read]: owner component StatePoliceVehicle extends PoliceVehicle hasRole StatePolice
30
Open issues How to design and engineer security and trust for sCPS in general How to capture these on the architecture level How to apply this to other fields
31
Questions Owner: John Doe Speed: 45 Km/h GPS:14.451,40.321 Owner: John Doe Speed: 45 Km/h GPS:14.451,40.321 Owner: John Doe Speed: 45 Km/h GPS:14.451,40.321 POLICE Replica Knowledge
32
cdRBAC: Performance impact A performance of the implementation was measured on the 10 minute simulation of the example application with 10 vehicles. Average number of messages sent with access control in place was 20% higher. The average extra time was 51%.
Similar presentations
© 2024 SlidePlayer.com. Inc.
All rights reserved.