Industrial Internet Security Framework v 1.0 | Page 84

Security Framework

9: Protecting Communications and Connectivity

transport level with TLS or DTLS) may not provide sufficient security for application-level traffic
that requires fine-grained security controls.
9.1.2 BUILDING BLOCKS FOR PROTECTING EXCHANGED CONTENT
Where possible, information exchange security among communicating endpoints for sensitive
networks and equipment should employ:
•
•
•
•

explicit endpoint communication policies,
cryptographically strong mutual authentication between endpoints,
authorization mechanisms that enforce access control rules derived from the policy and
cryptographically backed mechanisms to ensure confidentiality, integrity and freshness
of exchanged information

A first step in establishing secured communication is mutual authentication using
cryptographically backed authentication protocols (i.e., by exchanging identity certificates, if a
public-key infrastructure is set up). The parties must then exchange data according to the access
control rules defined in the policy. For example, an endpoint collecting medical metrics that has
been deemed authentic may not be permitted to share some patient data.
Confidentiality and integrity of exchanged messages should be achieved using standard
techniques for encryption (i.e., symmetric algorithms such as AES and asymmetric algorithms
such as RSA) and message authentication (i.e., digital signature schemes such as DSA and
message authentication codes such as HMAC). These techniques often use cryptographic keys
established during the mutual authentication process; encryption without message
authentication should be avoided.
Communication protocols that do not provide integrity and confidentiality of exchanged
messages could be routed through encrypted and authenticated tunnels or otherwise be
contained by information flow control techniques. This improves security of legacy protocols.
9.1.3 CONNECTIVITY STANDARDS AND SECURITY
A core connectivity technology, as defined in ‘Industrial Internet of Things, Volume G5:
Connectivity Framework’ 1, should:
•
•
•
•

1

be an open standard with strong independent, international governance, such as IEEE,
IETF, OASIS, OMG, or W3C,
be horizontal and neutral in its applicability across industries,
be applicable, stable and proven across multiple industries and
have standard-defined gateways to all other connectivity standards.

See [IIC-IICF2017]

IIC:PUB:G4:V1.0:PB:20160926

- 84 -