IEEE 1686
Data integrity and data confidentiality (5.3, 5.4) – IEEE 1686

IEEE 1686 5.3: Data integrity

What does 5.3 require?

The IED protects the integrity of its firmware, configuration and communications. The 2013 material Table 1 moves here and into 5.4: the specific cryptographic features, where the IED offers them, of (a) web server functionality, (b) file transfer, (c) text-oriented terminal connections, (d) SNMP network management, (e) network time synchronization and (f) secure tunnels; the cryptographic techniques used; and the configuration software's authentication and digital signature. The corrigendum's clarified definition of value forcing separates valid control operations from forced values that violate integrity.

Maintained by Gerard BlokdykControl text last updated

Other controls in Data integrity and data confidentiality (5.3, 5.4) – IEEE 1686

Query this from an agent

The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.