Use a layered approach to architecture diagramming
- Last UpdatedNov 06, 2025
- 2 minute read
With a more complex ICS, diagramming requires more layers to separately assemble diagram elements and build them into a comprehensive visualization.
Use a layered approach to architecture diagramming
-
Define security objectives.
High availability, operational uptime, and process and data quality should be prioritized with information and IP confidentiality as a close second priority.
-
Define security zones and communication channels.
Security zones following industry standards such as the Purdue Model and IEC 62443 can form a starting point for laying out a system architecture. The following illustration is a simple example of security zones for a general manufacturing application.

-
Define defense-in-depth strategy.
Defense-in-depth can be defined as layered security that ensures the system has no single point of failure.
-
Define network security.
Refer to Recommended actions to secure the network for key actions that can be built into the system architecture.
-
Define endpoint security.
Whitelisting, boot and firmware validation, and patch management are all tools to define endpoint security. These tools might not appear as items on an architectural diagram, but are part of network segmentation as depicted in the preceding illustration.
-
Configure user identity and access management.
Build role-based access control, time constrained and task-specific privileges, and centralized authentication into the system architecture.
-
Assess risks and conduct threat modeling.
Incorporate into the architecture threat modeling mitigation elements. Identify attack surfaces and components with priority protection.
-
Integrate HADR measures.
Backups and redundant elements of HADR measures can be prominently included in architecture diagrams.
-
Reflect monitoring and planned responses.
Reflect security information and event monitoring (SIEM) components such as SIEM utilities and logs in a detailed architecture.