ICS/SCADA › Module 9 › Lesson 4
Lab — Reporting
Merge OT IR, reporting checklist, and lessons learned sections on YOUR $OT_LAB — defensive OT literacy only; no real-plant attacks, unauthorized OT scans, or exploit cookbooks.
Visual · t38_reporting_lab
Reporting Lab literacy. $OT_LAB only. Original Cyberlium.
Opening
Incident pack merges IR phases, reporting checklist, and lessons learned — paperwork before capstone module.
Lessons 9-1–9-3 named OT IR, reporting, and lessons learned. Merge into one OT lab incident artifact for fictional INC-LAB-001 tabletop with educational disclaimer. 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: Quiz — Incident and Reporting.
1. What Reporting Lab covers (named)
Create t38-m09-l04-reporting-lab.txt merging M9 sections. Include educational disclaimer — not legal advice for real reporting obligations. On $OT_LAB, document literacy rows on fictional LAB-OT-001 — never live plant IPs, credentials, or exploit steps.
Tabletop scenario: fictional ransomware on jump host — containment with operations coordination. No live incident simulation on real plants. 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 Reporting Lab 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 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_LAB/notes/reporting-lab-summary.md" <<'EOF'
# Incident/Reporting Lab Summary
- ot-ir-phases.md + reporting-checklist.md + lessons-learned.csv
## Refusals
- Fictional INC-LAB-001 tabletop only; no hoax regulatory filings
EOFCommand — copy this
grep -E 'Incident|Refusals|INC-LAB' "$OT_LAB/notes/reporting-lab-summary.md" curl -sS https://www.cisa.gov/topics/industrial-control-systems | head -3
Primary tools to practice this lesson: grep, curl. 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 Reporting Lab matters for defenders
Grep for live incident ticket numbers, real regulator forms with PII — redact. Fictional INC-LAB-001 only. On $OT_LAB, document literacy rows on fictional LAB-OT-001 — never live plant IPs, credentials, or exploit steps.
Cross-reference M5 defense lessons and M6 segmentation gaps. Thread continuity. On $OT_LAB, document literacy rows on fictional LAB-OT-001 — never live plant IPs, credentials, or exploit steps.
3. $OT_LAB boundary
chmod 600 — quiz next, then Checklist. Incident literacy feeds capstone in M10. On $OT_LAB, document literacy rows on fictional LAB-OT-001 — never live plant IPs, credentials, or exploit steps.
Ship: incident/reporting pack. Next: Quiz — Incident and Reporting.
4. What you ship: reporting lab card for $OT_LAB
Merge OT IR, reporting checklist, and lessons learned sections. $OT_LAB named. NEVER real-plant attack steps. chmod 600.
5. What you record before the next lesson
Date (UTC). Reporting Lab card. $OT_LAB named. File t38-m09-l04-reporting-lab.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
Import employer real OT incident report without authorization.
Right
Write reporting lab card for YOUR $OT_LAB. Next: Quiz — Incident and Reporting.
Mission: document Reporting Lab 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: Reporting Lab 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: Reporting Lab literacy on Cyberlium uses:
Multiple choice