Vendor Hygiene
Vendor hygiene literacy names contracts, SBOM requests, support account reviews, and incident notification clauses on YOUR $OT_LAB — defensive OT literacy only; no real-plant attacks, unauthorized OT scans, or exploit cookbooks.
Visual · t38_vendor_hygiene
Vendor Hygiene literacy. $OT_LAB only. Original Cyberlium.
OT vendors touch your process daily — literacy documents vendor risk rows without sharing live support portals in lab notes.
Vendor hygiene covers least-privilege support accounts, contractual security clauses, SBOM/vulnerability notification expectations, and periodic access recertification. Draft vendor hygiene rows for fictional LAB-VENDOR-001 — not storing live vendor portal passwords. 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: Hardening Lab.
1. What Vendor Hygiene covers (named)
Vendor literacy: contract security exhibit, CVE notification SLA, remote access scope, software bill of materials request. Recertify vendor accounts quarterly — disable stale IDs. On $OT_LAB, document literacy rows on fictional LAB-OT-001 — never live plant IPs, credentials, or exploit steps.
Write vendor hygiene row — vendor stub, access scope, review date, contract clause stub. Fictional vendor 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 Vendor Hygiene covers (named)
═══ TOOLS & WEBSITES ═══ Browse / read these (authorized learning only — stay in YOUR lab / program scope)
CISA vendor access — 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 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_HARDEN/vendor-hygiene.csv" <<'EOF'
vendor_id,access_scope,review_date,contract_clause_stub
LAB-VENDOR-001,read-only support + jump,2026-09-01,SEC-OT-2026
EOFCommand — copy this
grep -E 'LAB-VENDOR|review_date' "$OT_HARDEN/vendor-hygiene.csv"
Primary tools to practice this lesson: grep, python3. Reference sites: CISA vendor access (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 Vendor Hygiene matters for defenders
Vendor compromise is recurring OT breach theme. Links to M6 remote access hygiene rows. On $OT_LAB, document literacy rows on fictional LAB-OT-001 — never live plant IPs, credentials, or exploit steps.
Students draft vendor rows on lab templates. Production follows vendor risk management programs. On $OT_LAB, document literacy rows on fictional LAB-OT-001 — never live plant IPs, credentials, or exploit steps.
3. $OT_LAB boundary
Forbidden: live vendor portal creds in lab CSV. Allowed: vendor hygiene literacy row on OT lab. On $OT_LAB, document literacy rows on fictional LAB-OT-001 — never live plant IPs, credentials, or exploit steps.
Ship: vendor hygiene row. Next: Hardening Lab.
4. What you ship: vendor hygiene card for $OT_LAB
Vendor hygiene literacy names contracts, SBOM requests, support account reviews, and incident notification clauses. $OT_LAB named. NEVER real-plant attack steps. chmod 600.
5. What you record before the next lesson
Date (UTC). Vendor Hygiene card. $OT_LAB named. File t38-m08-l03-vendor-hygiene.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: Archive employer vendor VPN PDF with passwords in lab folder.
- Right: Write vendor hygiene card for YOUR $OT_LAB. Next: Hardening Lab.
Mission: document Vendor Hygiene 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: Vendor Hygiene on Cyberlium means:
APPLY: True or False: Topic 38 includes ICS attack cookbooks against real plants.
APPLY: Vendor Hygiene literacy on Cyberlium uses: