Arrowhead Security

Each and every Arrowhead Framework system runs in either secure or insecure mode. If in the secure mode, the system in question is always associated with a cryptographic identity. That identity is used for three things, which are
  1. to establish secure transports,
  2. to determine system identities and relationships, as well as
  3. to make access control decisions.
Systems running in insecure mode do not have any cryptographic identities, which means that none of the activities listed above can be supported. The insecure mode is primarily intended for development or evaluation scenarios, but could also be useful in context where security is not a requirement.

Whether or not systems are to run securely or not is typically decided on a per-cloud basis, meaning that either all systems part of the same local cloud run in secure mode, or none of them do. There is nothing, however, preventing a single device from running a secure system that is part of a local cloud from also running an insecure version of the same system.

See Also:
Arrowhead Access Control, Arrowhead Identity Management