Difference between revisions of "SCOTT:BB23.C"
From its-wiki.no
Josef.Noll (Talk | contribs) (Created page with "{{Building Block |Title=HW supported security mechanisms |Page Title=BB3.1.C HW supported security mechanisms |Technology Line=Security & Safety |Lead partner=VIF |Leader=Marc...") |
Josef.Noll (Talk | contribs) |
||
| Line 5: | Line 5: | ||
|Lead partner=VIF | |Lead partner=VIF | ||
|Leader=Marco Steger | |Leader=Marco Steger | ||
| − | |Partner= | + | |Partner=Nokia, VIF, VTT, AVL, JKU, TUG, UiO, F-SECURE, TU Delft, IMEC, AIT, FEV, |
|Related to Use Cases=SCOTT:WP7, SCOTT:WP11, SCOTT:WP12, SCOTT:WP13, SCOTT:WP14, | |Related to Use Cases=SCOTT:WP7, SCOTT:WP11, SCOTT:WP12, SCOTT:WP13, SCOTT:WP14, | ||
|Description=Supporting basic security mechanisms such as trust assurance, encryption, signing, authentication, key storage on both virtualized and dedicated HW. This will help the make security features more efficient (power, time, trust) and increase the security level within a WSSN. | |Description=Supporting basic security mechanisms such as trust assurance, encryption, signing, authentication, key storage on both virtualized and dedicated HW. This will help the make security features more efficient (power, time, trust) and increase the security level within a WSSN. | ||
Revision as of 23:45, 4 July 2017
| Title | HW supported security mechanisms |
|---|---|
| Page Title | BB3.1.C HW supported security mechanisms |
| Technology Line | Security & Safety |
| Lead partner | VIF |
| Leader | Marco Steger |
| Contributors | Nokia, VIF, VTT, AVL, JKU, TUG, UiO, F-SECURE, TU Delft, IMEC, AIT, FEV |
| Related to Use Cases | SCOTT:WP7, SCOTT:WP11, SCOTT:WP12, SCOTT:WP13, SCOTT:WP14 |
| Description | Supporting basic security mechanisms such as trust assurance, encryption, signing, authentication, key storage on both virtualized and dedicated HW. This will help the make security features more efficient (power, time, trust) and increase the security level within a WSSN. |
| Main output | Common SCOTT hardware chip(s) plus guidelines on how to use and integrate the security chip in existing hardware and software stacks, as well as an API to simply integrate the hardware module in an existing software implementation. |
| BB category | Methodology (for SW/HW development), HW component |
| Baseline | Chip manufactorers already provide security modules for different purposes (HSM, TPM). Within SCOTT we want to define guidelines on how to choose and use the right module depending on the application and its requirements w.r.t. power consumption, time, speed etc. |
| Current TRL | TRL 3-4, HW modules exist (mainly for IT security) but cannot directly be used in WSNs and smart sensors |
| Target TRL | TRL 5-6, the HW module will be integrated in SCOTT‘s demonstrators and resulting prototypes |