Tag: Open Trust Protocol

Open Trust Protocol (OTrP) gets revised

~ hucktech ~ Leave a comment

As Marc Canel of EETimes points out the 1st revision of the Open Trust Protocol is out. Open Trust Procotol is an IETF submission by multiple vendors, the companies Symantec, Intercede, Solacia, and ARM Ltd are the employers of the editors of the I-D.

Abstract: This document specifies the Open Trust Protocol (OTrP), a protocol to install, update, and delete applications and to manage security configuration in a Trusted Execution Environment (TEE). TEEs are used in environments where security services should be isolated from a regular operating system (often called rich OS). This form of compartmentlization grants a smaller codebase access to security sensitive services and restricts communication from the rich OS to those security services via mediated access.

http://www.eetimes.com/author.asp?section_id=36&doc_id=1330455&
https://www.ietf.org/id/draft-pei-opentrustprotocol-01.txt
https://tools.ietf.org/html/draft-pei-opentrustprotocol-01
https://datatracker.ietf.org/doc/draft-pei-opentrustprotocol/
https://www.ietf.org/mail-archive/web/saag/current/msg07206.html

 

Open Trust Protocol (OTrP) created

~ hucktech ~ Leave a comment

There’s a new IoT security-centric informational IETF Internet Draft out, called OTrP, Open Trust Protocol. Their spec is released as an informational IETF Internet Draft, the companies of the 5 authors are from: Symantec, Interce, Solacia, and ARM. One of the news sites mentions the full list of companies backing this protocol are: Intercede, Solacia, Symantec, Beanpod, Sequitur Labs, Sprint, Thundersoft, Trustkernel, Verimatrix and ARM. I can’t find any web site for this group.

“This document specifies the Open Trust Protocol (OTrP), a protocol to install, update, and delete applications and to manage security configuration in a Trusted Execution Environment (TEE).TEEs are used in environments where security services should be isolated from a regular operating system (often called rich OS). This form of compartmentlization grants a smaller codebase access to security sensitive services and restricts communication from the rich OS to those security services via mediated access. […]”

https://www.ietf.org/id/draft-pei-opentrustprotocol-01.txt
https://tools.ietf.org/html/draft-pei-opentrustprotocol-01
https://www.arm.com/about/newsroom/connected-devices-need-e-commerce-standard-security-say-cyber-security-experts.php

PS: A bit off-topic, but IETF- and IoT- related, found when looking for above URLs:
https://www.internetsociety.org/publications/ietf-journal-april-2016/internet-things-standards-and-guidance-ietf