Navigation

  • index
  • next |
  • previous |
  • iocafe 0.4 documentation »

Previous topic

Test your new application on the target hardware

Next topic

Process (device) and user identification

This Page

  • Show Source

Quick search

Security¶

I believe that good security is as simple as possible, so that requirements which are necessary to maintain it are understandable. The IOCOM security doesn’t answer device security as whole, only to communication security.

../_images/121619-how-security-works-simplified.jpeg

A simple way to see the security.

Contents:

  • Process (device) and user identification
  • Certificates and chain of trust
    • Organization - root certificate and private key
    • Certifying a server - server certificate and private key
    • If cloud server is maintained by different organization?
    • Certificate expiration
    • Client certificates
    • Restorable server backup copy vs. security
    • Future plans
  • Authentication
  • Automatic pairing IO device and server
  • About security vulnerabilities
  • IOCOM secure network topology - take 1
  • IOCOM secure network topology - take 2
  • Platform security functionality
    • Cryptographic hashes
    • AES encryption wrapper API
    • CPUID Unique CPU or computer identifier

updated 15.3.2021/pekka

Navigation

  • index
  • next |
  • previous |
  • iocafe 0.4 documentation »
© Copyright 2020, Pekka Lehtikoski, Markku Nissinen. Created using Sphinx 1.8.5.