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

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

43.2 Attack Surface – Defaults, Telnet, HTTP, UPnP, Dashboards

By Last updated:

IoT reality check (SME godown):

  • Factory admin/admin or printed sticker password still on camera
  • Telnet or plain HTTP management UI on the LAN (sometimes on the internet via bad NAT/UPnP)
  • UPnP opens ports without Raja knowing
  • Cloud "dashboard" with shared vendor support accounts
  • Old BusyBox / abandoned firmware; no auto-update

Blue hardening (lab + production idea – same spirit):

  1. Change every default password before the device leaves the box
  2. Disable Telnet; prefer SSH/HTTPS if the device supports it – else VLAN-only + jump host
  3. Turn UPnP off on the router that faces the ISP
  4. Management plane only from admin VLAN / VPN
  5. Inventory: MAC, firmware version, who owns the asset
Red team (attacker) does Blue team (defender) detects / stops
Tries vendor default list on port 23/80/554 Disable Telnet; unique passwords; fail2ban-class / lockout on UI
Finds UPnP-mapped camera on WAN UPnP off; WAN port check from own phone on mobile data
Uses shared "support" cloud login SSO, MFA, least privilege, revoke vendor standing access

Ravindra Bagale's Tip

Students say "password changed = done" and leave UPnP on. Password + no WAN exposure + VLAN. Interview: "Default credentials and UPnP are still the SME camera story." Keep this in mind.

Lab

On paper: list 5 default-cred mistakes for a fake DVR (admin/12345, Telnet on, UPnP on, HTTP only, no inventory). For each, one Blue fix. Pair with Zoya – she plays "new camera unboxing checklist".

Real incident: Verkada camera platform access (2021)

In March 2021, attackers accessed Verkada's support / admin tooling and, as reported by the company and covered widely (Bloomberg and others), viewed video for a subset of customers; Verkada's own incident report later described 97 customers with camera access among roughly 6,000 customers (verify their published figures). Public reporting described how exposed super-admin style credentials on an internet-reachable internal system (Jenkins / support tooling) let attackers bypass normal authorization, including MFA on the customer path. Lesson for this section: camera risk is not only "default password on the lens" – cloud and support planes are attack surface too. Defence: no secrets on public CI, MFA that cannot be skipped via support backdoors, customer-side network isolation, vendor risk review. Source: Verkada Security Update / incident report (2021); Cloudflare blog on the same event (verify; say "reported" for camera counts).

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.