Plan the boundaries of an industrial data integration

A practical discussion of network responsibilities, access, data quality and change control in an IIoT project.

Share
  • Assign ownership to each data path.
  • Separate monitoring from control permissions.
  • Validate the selected design and its failure behavior.
In this resource

Map the data path and its owners

Identify the source equipment, acquisition devices, supervisory applications and any external destinations. Record which teams own each part of the path.

Review the network and operational constraints with the site’s responsible IT and controls teams. A protocol name or a generic cloud diagram is not a security design.

Separate acquisition from command authority

Define read-only reporting needs separately from write access or supervisory commands. Document the permitted action and the equipment consequences for any control scope.

Authentication, authorization and connection settings need to fit the selected equipment and deployment. Do not assume a gateway is a one-way data diode unless that behavior is part of a verified design.

Plan data availability and change control

Specify how connection loss, stale timestamps and bad-quality values appear to the application. Define what should happen during recovery.

Agree on configuration ownership, backups and the review process for tag, driver or application updates.

Use project-specific validation

Test the approved data path and relevant failure conditions against documented acceptance criteria. Keep operational responsibilities and handover information with the system documentation.

This paper is a planning framework, not a certification, security assessment or substitute for a site-specific architecture review.

Further reading

External references provide background. Their inclusion does not imply affiliation or equipment compatibility.

Have a site-specific question about these ideas?

Discuss your application