Protocol Risks
Protocol risk literacy names plaintext, flat networks, vendor defaults, and compensating controls on YOUR $OT_LAB — defensive OT literacy only; no real-plant attacks, unauthorized OT scans, or exploit cookbooks.
Visual · t38_protocol_risks
Protocol Risks literacy. $OT_LAB only. Original Cyberlium.
OT protocols were built for reliability not zero trust — literacy names risks defenders mitigate with zones and monitoring.
Common OT protocol risks include lack of authentication, no encryption on legacy serial/TCP, flat VLANs, default credentials on HMIs, and unmonitored engineering laptops. Document risk rows and compensating controls on fictional plant — not exploit chains on live infrastructure. Cyberlium Topic 38 practices on $OT_LAB — YOUR fictional OT templates, zone diagrams, and labeled checklists under $HOME/cyberlium-lab/t38-ot/ no real-plant attacks, unauthorized OT scans, or exploit cookbooks. Next: Protocols Lab.
1. What Protocol Risks covers (named)
Risk literacy: plaintext Modbus/DNP3, exposed engineering ports, USB maintenance paths, vendor remote support. Compensating: segmentation, allowlists, passive monitoring, jump hosts with MFA. On $OT_LAB, document literacy rows on fictional LAB-OT-001 — never live plant IPs, credentials, or exploit steps.
Write protocol risk row — risk, affected layer, compensating control. On LAB-OT-001 only. On $OT_LAB, document literacy rows on fictional LAB-OT-001 — never live plant IPs, credentials, or exploit steps.
Command guide
Try these commands — What Protocol Risks covers (named)
═══ TOOLS & WEBSITES ═══ Browse / read these (authorized learning only — stay in YOUR lab / program scope)
CISA ICS — https://www.cisa.gov/topics/industrial-control-systems NIST SP 800-82 — https://csrc.nist.gov/publications/detail/sp/800-82/rev-3/final
═══ INSTALL ═══
Linux (Debian/Ubuntu):
Command — copy this
sudo apt install python3
macOS:
Command — copy this
brew install python3
Windows: Download https://python.org/downloads/
═══ LINUX / macOS ═══
Command — copy this
export OT_LAB=${OT_LAB:-$HOME/cyberlium-lab/t38-ot}
cat > "$OT_PROTOCOLS/protocol-risks.csv" <<'EOF'
risk_id,protocol,layer,risk,compensating_control
R-001,Modbus,L1-L2,no authentication,segmentation + passive monitor
R-002,DNP3,L2,legacy plaintext paths,integrity options + conduit
R-003,OPC UA,L3,certificate expiry,monitoring + PKI hygiene
EOFCommand — copy this
grep -E 'R-00[1-3]|compensating' "$OT_PROTOCOLS/protocol-risks.csv"
Primary tools to practice this lesson: grep, python3. Reference sites: CISA ICS (https://www.cisa.gov/topics/industrial-control-systems); NIST SP 800-82 (https://csrc.nist.gov/publications/detail/sp/800-82/rev-3/final). Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.
2. Why Protocol Risks matters for defenders
Risk rows feed zone maps and monitoring use cases. Honest gaps beat checkbox compliance. On $OT_LAB, document literacy rows on fictional LAB-OT-001 — never live plant IPs, credentials, or exploit steps.
Students draft risk/comp control pairs on lab templates. Production follows CISA ICS recommended practices. On $OT_LAB, document literacy rows on fictional LAB-OT-001 — never live plant IPs, credentials, or exploit steps.
3. $OT_LAB boundary
Forbidden: chaining protocol exploits against real plants in lab notes. Allowed: protocol risk + compensating control literacy card. On $OT_LAB, document literacy rows on fictional LAB-OT-001 — never live plant IPs, credentials, or exploit steps.
Ship: protocol risk card. Next: Protocols Lab.
4. What you ship: protocol risks card for $OT_LAB
Protocol risk literacy names plaintext, flat networks, vendor defaults, and compensating controls. $OT_LAB named. NEVER real-plant attack steps. chmod 600.
5. What you record before the next lesson
Date (UTC). Protocol Risks card. $OT_LAB named. File t38-m04-l03-protocol-risks.txt chmod 600.
6. Wrong vs right: plant attacks vs YOUR OT lab sims
Worked failure — same MSF word, opposite target. Right never needs a café Wi-Fi or classmate laptop.
- Wrong: Document live exploit chain against employer Modbus devices.
- Right: Write protocol risks card for YOUR $OT_LAB. Next: Protocols Lab.
Mission: document Protocol Risks on YOUR OT lab
1) Name literacy rows on $OT_LAB. 2) Write NEVER list (no real-plant attacks, unauthorized OT scans, or exploit cookbooks). 3) chmod 600. Never scan or exploit real industrial networks.
Stuck? Ask Cyberlium AI Mentor
Ask Mentor: literacy on $OT_LAB — not attack recipes against live plants.
APPLY: Protocol Risks on Cyberlium means:
APPLY: True or False: Topic 38 includes ICS attack cookbooks against real plants.
APPLY: Protocol Risks literacy on Cyberlium uses: