Network segmentation (IT/OT separation) in SCADA systems - Time & Space Complexity
When we separate IT and OT networks, we want to see how the work needed grows as the network size grows.
We ask: How does the time to check or manage network segments change when more devices are added?
Analyze the time complexity of the following code snippet.
// Pseudo scada_systems code for network segmentation check
function checkNetworkSegments(devices) {
for (device of devices) {
if (device.type == 'OT') {
for (connectedDevice of device.connections) {
if (connectedDevice.type == 'IT') {
alert('IT/OT connection found');
}
}
}
}
}
This code checks all OT devices and their connections to find any IT devices connected, ensuring proper separation.
- Primary operation: Looping over all devices, then for OT devices looping over their connections.
- How many times: Outer loop runs once per device; inner loop runs once per connection of OT devices.
As the number of devices grows, the checks increase based on how many connections OT devices have.
| Input Size (n) | Approx. Operations |
|---|---|
| 10 | About 10 outer checks plus connections of OT devices |
| 100 | About 100 outer checks plus more connections to check |
| 1000 | About 1000 outer checks plus many connections checked |
Pattern observation: The total work grows roughly with the number of devices times their average connections.
Time Complexity: O(n * k)
This means the time grows with the number of devices (n) and the average connections per OT device (k).
[X] Wrong: "The time to check network segments grows only with the number of devices."
[OK] Correct: Because each OT device's connections also add work, so connections matter too.
Understanding how network checks scale helps you design systems that stay efficient as they grow.
"What if we only checked OT devices without looking at their connections? How would the time complexity change?"
Practice
Solution
Step 1: Understand the role of network segmentation
Network segmentation divides a network into parts to isolate sensitive systems from less secure ones.Step 2: Apply this to IT and OT systems
Separating IT (office systems) from OT (industrial control) protects critical SCADA systems from cyber threats.Final Answer:
To improve security by separating critical industrial systems from general IT networks -> Option AQuick Check:
Network segmentation = Security improvement [OK]
- Thinking segmentation speeds up network
- Believing segmentation reduces devices
- Assuming segmentation allows free communication
Solution
Step 1: Identify VLAN usage for separation
Using separate VLANs for IT and OT devices isolates their traffic logically.Step 2: Check for access control lists (ACLs)
ACLs control and restrict traffic between VLANs, enhancing security.Final Answer:
VLAN 10 for IT devices, VLAN 20 for OT devices, with ACLs controlling traffic between them -> Option CQuick Check:
Separate VLANs + ACLs = Proper segmentation [OK]
- Using same VLAN for IT and OT
- Not applying ACLs between VLANs
- Ignoring VLANs and traffic control
permit ip 192.168.1.0 0.0.0.255 10.0.0.0 0.0.0.255What does this rule allow?
Solution
Step 1: Understand ACL syntax
The rule permits IP traffic from source 192.168.1.0/24 to destination 10.0.0.0/24.Step 2: Interpret the wildcard masks
Wildcard 0.0.0.255 means any IP in the last octet, so 192.168.1.x to 10.0.0.x is allowed.Final Answer:
Allow all IP traffic from 192.168.1.x to 10.0.0.x -> Option AQuick Check:
permit ip source to destination = Allow traffic [OK]
- Confusing source and destination
- Misreading wildcard masks
- Assuming rule blocks traffic
Solution
Step 1: Check VLAN separation
If VLAN IDs are different, devices are separated logically, so VLAN ID conflict is unlikely.Step 2: Review ACL rules
ACLs often block traffic between VLANs; missing or wrong ACLs can prevent OT devices from reaching SCADA server.Final Answer:
Missing or incorrect ACL rules blocking OT to SCADA traffic -> Option DQuick Check:
ACL misconfiguration = communication failure [OK]
- Assuming VLAN IDs are same without checking
- Ignoring ACL impact on traffic
- Jumping to hardware power issues first
Solution
Step 1: Understand segmentation with selective access
Segmentation requires separate VLANs; selective access needs controlled rules.Step 2: Apply VLAN and ACLs for fine control
Creating a dedicated VLAN for allowed IT workstations and ACLs restricting access by IP ensures security and selective access.Final Answer:
Create a dedicated VLAN for those IT workstations and configure ACLs to allow only their IPs to OT VLAN -> Option BQuick Check:
Dedicated VLAN + ACLs = selective secure access [OK]
- Mixing IT and OT in one VLAN
- Disabling ACLs completely
- Using broad firewall rules without IP filtering
Ready to prove it?
Pass the test and this pattern moves unknown
