ICS/SCADA › Module 8 › Lesson 2
Hardening Named
Hardening literacy names disable unused ports, account lockdown, application whitelisting, and backup integrity on OT hosts on YOUR $OT_LAB — defensive OT literacy only; no real-plant attacks, unauthorized OT scans, or exploit cookbooks.
Visual · t38_hardening_named
Hardening Named literacy. $OT_LAB only. Original Cyberlium.
Opening
OT hosts need hardening without breaking vendors — literacy lists baseline rows aligned with CISA ICS guidance.
OT hardening includes removing default accounts, disabling unused USB/network services, application allowlisting on engineering stations, and verified backups. Cyberlium lists hardening checklist rows on fictional assets — not exploit steps to 'test' weak HMIs on live plants. 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: Vendor Hygiene.
1. What Hardening Named covers (named)
Hardening literacy: CIS/NIST OT-aligned baselines, separate engineering vs operator profiles, local admin restriction, AV policy exceptions documented. Coordinate with vendor support before hardening breaks licensing. On $OT_LAB, document literacy rows on fictional LAB-OT-001 — never live plant IPs, credentials, or exploit steps.
Write hardening checklist row — control, asset type, verification stub. LAB-OT-001 engineering workstation fictional 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 Hardening Named covers (named)
═══ TOOLS & WEBSITES ═══ Browse / read these (authorized learning only — stay in YOUR lab / program scope)
CISA hardening — https://www.cisa.gov/resources-tools/resources/ics-recommended-practices 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 curl
macOS: Built-in
Windows: Built-in (PowerShell: Invoke-WebRequest)
═══ LINUX / macOS ═══
Command — copy this
export OT_LAB=${OT_LAB:-$HOME/cyberlium-lab/t38-ot}
cat > "$OT_HARDEN/hardening-checklist.md" <<'EOF'
# OT Hardening Checklist — LAB-OT-001
- [ ] Disable default accounts on HMI/ENG
- [ ] Application allowlist on engineering WS
- [ ] USB policy enforced
- [ ] Verified backup/restores documented
NEVER: bypass security on live HMIs — lab checklist only
EOFCommand — copy this
grep -E '\[ \]|NEVER|allowlist' "$OT_HARDEN/hardening-checklist.md" curl -sS https://www.cisa.gov/resources-tools/resources/ics-recommended-practices | head -3
Primary tools to practice this lesson: grep, curl. Reference sites: CISA hardening (https://www.cisa.gov/resources-tools/resources/ics-recommended-practices); 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 Hardening Named matters for defenders
Hardening reduces ransomware footholds on jump hosts. Backups must be restorable — test on fictional drill rows. On $OT_LAB, document literacy rows on fictional LAB-OT-001 — never live plant IPs, credentials, or exploit steps.
Students draft hardening rows on lab notes. Production follows OT baseline standards. On $OT_LAB, document literacy rows on fictional LAB-OT-001 — never live plant IPs, credentials, or exploit steps.
3. $OT_LAB boundary
Forbidden: hardening bypass tutorials to access live HMIs. Allowed: hardening checklist literacy on OT lab. On $OT_LAB, document literacy rows on fictional LAB-OT-001 — never live plant IPs, credentials, or exploit steps.
Ship: hardening checklist row. Next: Vendor Hygiene.
4. What you ship: hardening named card for $OT_LAB
Hardening literacy names disable unused ports, account lockdown, application whitelisting, and backup integrity on OT hosts. $OT_LAB named. NEVER real-plant attack steps. chmod 600.
5. What you record before the next lesson
Date (UTC). Hardening Named card. $OT_LAB named. File t38-m08-l02-hardening-named.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
Disable security controls on live HMI to ' improve performance.'
Right
Write hardening named card for YOUR $OT_LAB. Next: Vendor Hygiene.
Mission: document Hardening Named 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.
Knowledge Check
APPLY: Hardening Named on Cyberlium means:
Multiple choice
Knowledge Check
APPLY: True or False: Topic 38 includes ICS attack cookbooks against real plants.
True or False
Knowledge Check
APPLY: Hardening Named literacy on Cyberlium uses:
Multiple choice