10.1 Quality Standards and Compliance Baseline

Quality assurance for OT/IT network segmentation deployments must address both the physical installation quality and the logical security configuration quality. Physical quality encompasses cable management, labeling, grounding, and environmental compliance. Logical quality encompasses firewall rule correctness, zone isolation verification, access control enforcement, and audit trail completeness. The comparison image below illustrates the stark difference between a non-compliant and a compliant installation, highlighting the key quality indicators that acceptance testing must verify.

Non-Compliant vs Compliant OT/IT Network Cabinet Installation

Figure 10.1: Quality Comparison — Non-Compliant (left) vs. Compliant (right) industrial DMZ cabinet installation. Key differences: cable color coding and management, port labeling, zone identification, documentation, equipment selection, and physical security. The compliant installation demonstrates proper IT zone (blue cables), OT zone (orange cables), and management network (yellow cables) separation with clear zone labels and a laminated network diagram on the cabinet door.

Quality Dimension Non-Compliant Indicators Compliant Requirements Verification Method
Cable ManagementTangled cables, mixed colors, no routing planColor-coded by zone, routed in separate trays, labeled at both endsVisual inspection, cable test
Port LabelingUnlabeled or inconsistently labeled portsAll ports labeled with zone ID, device name, and VLANVisual inspection, documentation review
Zone SeparationIT and OT cables mixed in same trayPhysically separate cable paths for IT, OT, and managementPhysical inspection
Credential ManagementShared credentials, passwords on sticky notesIndividual accounts, MFA, PAM-managed credentialsUser account audit, PAM review
Equipment SelectionConsumer-grade or unmanaged switchesIndustrial-grade, managed, certified equipmentEquipment inventory review
DocumentationNo on-site documentationLaminated network diagram in cabinet, equipment log bookVisual inspection
Physical SecurityCabinet unlocked, no access controlCabinet locked, access log, camera coveragePhysical security audit

10.2 Acceptance Testing Procedure

The acceptance testing procedure for an OT/IT segmentation deployment is structured as a series of test phases, each building on the previous. Testing must be conducted in a defined sequence to ensure that foundational requirements (physical installation, connectivity) are verified before higher-level requirements (security policy enforcement, monitoring). All test results must be documented in the acceptance test report and signed off by the project owner, OT security team, and plant operations representative.

Test Phase Test Cases Pass Criteria Tools Required Responsible Party
Phase 1: PhysicalCable continuity, cable labeling, grounding, environmental (temp/humidity), power redundancy100% cable continuity, all cables labeled, grounding resistance <1Ω, temp 10–40°C, humidity 20–80%Cable tester, multimeter, thermometer, hygrometerInstallation Team
Phase 2: ConnectivityLayer 2 connectivity per zone, VLAN isolation, routing table verification, firewall interface statusAll intended paths UP, all unintended paths DOWN, correct VLAN assignmentsNetwork analyzer, ping, tracerouteNetwork Engineer
Phase 3: Security PolicyFirewall rule enforcement (permit/deny), DMZ service reachability, zone-to-zone isolation test, DPI functionalityAll permit rules pass, all deny rules block, DMZ services reachable from correct zones onlyNmap, Wireshark, firewall policy testerOT Security Team
Phase 4: AuthenticationMFA enforcement, PAM access control, session recording, certificate validation, emergency accessMFA required for all remote access, sessions recorded, certificates valid, emergency access documentedPAM audit tool, certificate checkerOT Security Team
Phase 5: MonitoringIDS alert generation, syslog forwarding, SIEM correlation, NTP synchronization, backup verificationIDS generates alerts for test events, logs forwarded within 60s, SIEM receives events, time sync <1sIDS test tool, log analyzerSOC / OT Security
Phase 6: PerformanceFirewall throughput under load, failover time (HA), latency impact on OT protocolsThroughput ≥ design spec, HA failover <30s, OT protocol latency increase <10msTraffic generator, protocol analyzerNetwork Engineer

10.3 Acceptance Checklist

The following acceptance checklist consolidates all mandatory verification items into a single reference document. Each item must be marked as Pass, Fail, or N/A with supporting evidence. Items marked Fail must have a documented remediation plan with a target completion date before the system is accepted for production use.

# Checklist Item Category Mandatory Evidence Required
1All cables color-coded by zone (Blue=IT, Orange=OT, Yellow=Mgmt)PhysicalYesPhotograph
2All cable ends labeled with source/destination and zonePhysicalYesPhotograph
3Cabinet grounding verified (<1Ω to building ground)PhysicalYesMultimeter reading
4No direct IT-to-OT traffic path (verified by firewall rule audit + penetration test)SecurityYesPen test report
5DMZ services accessible only from authorized zonesSecurityYesFirewall test results
6All remote access requires MFASecurityYesAccess test log
7All privileged sessions recorded by PAMSecurityYesPAM session log sample
8OT IDS generating alerts for test attack scenariosMonitoringYesIDS alert log
9All security events forwarded to SIEM within 60 secondsMonitoringYesSIEM event timestamp comparison
10HA failover tested and completed within 30 secondsPerformanceYesFailover test log with timestamps
11Network diagram posted inside cabinet door (laminated)DocumentationYesPhotograph
12Equipment log book present and initial entries completedDocumentationYesPhotograph of log book
13All default passwords changed; no shared credentialsSecurityYesAccount audit report
14Patch management workflow tested (IT → DMZ → OT staging)OperationsYesPatch transfer test log
15Incident response runbooks reviewed and signed by plant managerOperationsYesSigned runbook cover page