Ravindra BagaleCourses & study guides मराठी Track your progress

43. IoT and OT Security – Cameras, Smart Devices, Plant Networks

43.7 Firmware, Updates and Supply-Chain Hygiene

By Last updated:

Cameras and PLCs often:

  • Ship with old OpenSSL / BusyBox
  • Need vendor signed firmware – random "crack firmware" Telegram file = backdoor
  • Sit for years without patch because "line cannot stop"
  • Trust a USB stick from a "helpful" vendor tech

Blue hygiene (concepts):

  1. Inventory model + firmware version
  2. Subscribe to vendor PSIRT / CERT-In advisories that apply
  3. Test update on a spare / window; verify hash/signature when vendor publishes one
  4. Disable unused services after upgrade (Telnet likes to return)
  5. Supply chain: buy from known channel; change support passwords after vendor visit

Stuxnet (2010) remains the classic OT awareness story in exam modules: malware that propagated in industrial environments and impacted uranium enrichment centrifuges in Iran, as widely reported – proof that software can have physical effects. We study it as history and defence motivation, not as a rebuild kit.

Red team (attacker) does Blue team (defender) detects / stops
Tricks staff into unsigned firmware USB Signed updates only; write-protect where possible; train
Abuses old CVE on abandoned camera OS Replace or isolate EOL devices; VLAN + egress deny
Compromises vendor update channel (SUNBURST-class lesson) Outbound allow-list; monitor admin suites; staged rollouts

Ravindra Bagale's Tip

Students flash the "latest cracked ROM". Unsigned firmware = you invited Red in. Interview: "Patch in a change window; verify vendor signature; isolate EOL IoT." Keep this in mind.

Lab

For one fictional camera model in notes: invent (clearly labelled fictional) current version 1.0.2 and advisory "upgrade to 1.0.5". Write rollback plan if video dies. 6 lines. No real plant flash.

Real incident: TRITON / TRISIS against safety controllers (2017)

In 2017, Mandiant (FireEye) publicly described TRITON (also called TRISIS / HatMan in other reporting): malware aimed at Schneider Electric Triconex safety instrumented system (SIS) controllers – the last-resort safety layer that can shut a process down safely. Public write-ups describe attackers reaching an SIS engineering workstation and deploying a framework to interact with the controllers; some controllers entered a failed-safe state and shut the process, which triggered investigation. CISA later published malware analysis (HatMan). Weakness: path to safety systems, insufficient isolation of SIS networks, trust in engineering workstations. Defence: hard segregation of SIS, monitored engineering access, application whitelisting on engineering hosts, anomaly detection on TriStation-class protocols – and never "practise" against real SIS. Source: Mandiant TRITON blog (Dec 2017); CISA MAR HatMan; Schneider Electric advisories (verify).

Extended teaching notes

Why this lesson matters

Cameras, sensors and plant controllers often ship with weak defaults. Segment them from IT, change passwords, block inbound internet, and watch outbound traffic.

Real examples

Global: Mirai showed what default passwords on routers/cameras can do at scale. Indian SME (sample): a factory puts PLCs on a separate VLAN reachable only via a jump host.

Mini case study

Suppose we are on a purple-team exercise for an Indian mid-size company (sample data). Red notes a technique from this lesson against a lab clone. Blue must show the control that stops it, the log that would have fired, and the ticket that hardens production. That is the standard this course trains you for.

Defender's worksheet (do this today)

  1. Write the lesson title, date and the exact lab target you are allowed to use.
  2. List three owned systems (VMs, apps, or cloud accounts) where this lesson applies.
  3. Run one safe check from the lesson on a lab system only. Paste the command and output.
  4. Write a two-sentence fix you would give a teammate.
  5. Name one related public advisory (CERT-In, CISA, NVD, or a vendor bulletin) with its date.

Indian workplace (sample data)

Suppose we are a junior analyst at Infosys, TCS, Wipro or a fintech SOC in Bengaluru/Pune. Turn this lesson into one checklist item with an owner, a due date and a place to store evidence (ticket + screenshot).

Global practice

Compare your notes with OWASP, CIS Benchmarks, NIST CSF/IR guidance or a cloud Well-Architected security question. Write five lines on what overlaps.

Everyday analogy

Explain the risk and the fix to a family member without jargon. If they can repeat the warning, you understand it well enough to teach juniors.

Key terms

  • Control: a safeguard (patch, config, process, detection).
  • Finding: a weakness backed by evidence.
  • Remediation: the fix plus how you verified it.
  • Scope: systems you have written permission to touch.
  • Least privilege: only the access the task needs.
  • Defence in depth: several layers so one failure does not end the story.

Common mistakes

  • Skipping written permission "just for a quick scan".
  • Practising on hostel, office or public targets without authorisation.
  • Collecting tool output without writing the fix.
  • Copying attack steps onto production to "verify". Defenders verify with versions, configs and patches.
  • Publishing screenshots that contain secrets, cookies or internal hostnames.

Recap

  • Evidence, fix, owner, date.
  • Own lab only.
  • Fix > spectacle.