Difference between revisions of "SCOTT:BB26.D"
From its-wiki.no
Josef.Noll (Talk | contribs) (Created page with "{{Building Block |Title=Infrastructure design and security threat analysis |Page Title=BB3.4.D Infrastructure design and security threat analysis |Technology Line=Reference Ar...") |
Josef.Noll (Talk | contribs) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{Building Block | {{Building Block | ||
|Title=Infrastructure design and security threat analysis | |Title=Infrastructure design and security threat analysis | ||
| − | |Page Title= | + | |Page Title=BB26.D Infrastructure design and security threat analysis |
|Technology Line=Reference Architecture/Implementation | |Technology Line=Reference Architecture/Implementation | ||
|Lead partner=ISEP | |Lead partner=ISEP | ||
Latest revision as of 17:51, 13 July 2017
| Title | Infrastructure design and security threat analysis |
|---|---|
| Page Title | BB26.D Infrastructure design and security threat analysis |
| Technology Line | Reference Architecture/Implementation |
| Lead partner | ISEP |
| Leader | Ramiro Robles |
| Contributors | ISEP |
| Related to Use Cases | SCOTT:WP12, SCOTT:WP16 |
| Description | Design a reference architecture that will allow for a convenient infrastructure design and the analysis of security threats in different levels of such architecture |
| Main output | The main output is a full modelling and analysis of security threats for different levels, interfaces and entities of the infrastructure. This will allow us to design security enforcing mechanism in a robust manner, not only at the application level, but across all layers, entities and interfaces of the infrastructure and architecture. |
| BB category | Methodology (for SW/HW development), SW component, Service, Profile, Interface, Standard, Process |
| Baseline | Security in IoT applications has not been addressed in full extent. Current solutions are vendor specific and mainly target encryption at the application level. This gap will be filled by this building block, providing a complete assessment of potential vulnerabilities that will lead to convenient security enforcing mechanisms. |
| Current TRL | TRL 3 |
| Target TRL | TRL 6 |