Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

Cybersecurity deployment guide

Architecture diagram recommendations

  • Last UpdatedAug 20, 2025
  • 2 minute read

The diagram itself can be as simple or as complex as required. The diagram need not use a large library of icons and thumbnails, although some tools provide built in libraries that make visualizations more readable. Simple block diagrams also can achieve the result especially for less complex systems. .

Architecture diagram and visualization recommendations

Many tools exist to create high quality, detailed diagrams. Use the tools that best meet the system needs and provide ease of use. When building architecture diagrams, especially in complex ICS contexts, we recommend the following best practices:

  • Include data flows between system components. Communication, whether through a LAN or through system or service-level channels, should be included as key architectural elements. Historian data flows, cloud data flows, remote access, and data exchanges should all be identified.

  • Include trust boundaries and specific security control elements in each zone.

  • Use a layered diagram, especially for more complex ICS contexts, to show enterprise IT and OT separation, DMZs, and communication channels.

The preceding diagram shows zones only. You can build on this or use it to cross check a more complete system architecture. The following diagram is a simplified example of an AVEVA System Platform architecture with basic security elements included. Additional layers could include a DMZ, gateways, or internal communication services and channels.

System Platform security architecture