Skip to content
Tutorials Center
My learning

Topics

Lesson 31 of 53 ยท Network, Wireless and Cloud Security

IoT and CCTV Security

Learn why IoT devices and IP cameras are risky, the common weaknesses (default credentials, old firmware, cleartext traffic, exposed APIs), how authorized testing works and how to harden devices.

The Internet of Things (IoT) is every networked device that is not a traditional computer: IP cameras and CCTV recorders, smart plugs and bulbs, thermostats, routers, printers, door locks, medical devices, industrial sensors. They are cheap, numerous and often forgotten. Many run an old Linux build, ship with the same password on every unit and never receive an update. When something that cannot be patched sits on your network, it becomes the easiest place for an attacker to start from, and a camera that anyone can view is a direct privacy harm.

Test only devices you own or are authorized to assess, on an isolated network. Accessing someone else's camera or smart device, even through a default password, is illegal in most places and invades real people's privacy. Never search the internet for exposed devices to try logging in. The examples here use invented data and a simulated device.

Why IoT is different

IoT devices combine several risk factors.

  • Low cost, low security investment. Margins are thin, and security rarely sells.
  • Hard to update. Updates may require manual steps, or no longer exist once a product reaches its end of life.
  • Long life. A camera installed in 2015 may still be running in 2030.
  • Default and shared credentials. The same admin account and password across all units of a model.
  • Little visibility. No antivirus, minimal logging and no one watching.
  • Always on and connected, often with direct internet reachability through router port forwarding or cloud services.

Large botnets have been built from exactly this: hundreds of thousands of cameras and routers with default passwords, recruited automatically and used for denial-of-service attacks. The device owners often never noticed.

The OWASP IoT view

OWASP maintains an IoT Top 10 list that is a good checklist for what goes wrong. In plain language the main themes are:

  1. Weak, guessable or hard-coded passwords.
  2. Insecure network services exposed unnecessarily.
  3. Insecure ecosystem interfaces: the web, cloud and mobile apps around the device.
  4. Lack of a secure update mechanism.
  5. Use of insecure or outdated components.
  6. Insufficient privacy protection: data collected, stored or sent without need or consent.
  7. Insecure data transfer and storage (no encryption).
  8. Lack of device management: no inventory, no monitoring.
  9. Insecure default settings.
  10. Lack of physical hardening: exposed debug ports, removable storage.

Cameras and CCTV

IP cameras and recorders (DVRs and NVRs) show nearly every weakness in one device.

  • Default credentials such as admin with a blank or common password, never changed.
  • Exposed management interfaces. The camera's web page and streaming port are reachable from the internet because of port forwarding or Universal Plug and Play.
  • Cleartext streams. The video and the login travel unencrypted, visible to anyone on the path (see packet analysis).
  • Old firmware with known vulnerabilities and no vendor patches.
  • Vendor cloud accounts with weak passwords or no multi-factor authentication.
  • Physical access. A serial console or a removable memory card on the device itself.

How an authorized assessment looks

  1. Inventory. Find out what devices exist on the network: addresses, models, firmware versions. Many organizations fail at this step. Use scanning and service discovery on your lab network.
  2. Identify services. Which ports does each device expose? Web, Telnet, SSH, RTSP streaming, UPnP?
  3. Credentials. Do default credentials still work in your lab unit? Is there a lockout?
  4. Traffic. Is login or video cleartext? Which servers does it contact?
  5. Firmware. What version runs? Is it listed in vulnerability databases? Can the update be verified? Firmware can sometimes be downloaded from the vendor and examined offline, which is analysis of a file you are permitted to analyze, with the tools in Reverse Engineering Basics.
  6. Ecosystem. Test the mobile app and the cloud API that control the device (API security, mobile testing).
  7. Report each finding with impact and a fix.

A device audit stand-in

The inventory below is invented. The code runs the checks that a defender's first review would: default credentials, unnecessary exposed services, firmware age and lack of encryption.

Node.js Audit an invented device inventory

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with node:readline or process.stdin), it gets the next line from this box.

In real life the inventory comes from scans and asset records, and the "firmware age" check would query a vulnerability database. The structure of the review stays the same.

A simulated login throttle

One cheap fix with a big effect is making password guessing slow. The second stand-in models a device login that locks out a source after repeated failures and compares it to an unprotected one. Nothing connects to a real device.

Node.js Why lockout and rate limits matter on devices

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with node:readline or process.stdin), it gets the next line from this box.

The device without lockout falls to a list of guesses in a few seconds. With lockout, the same list never reaches the right password. Real attackers distribute guesses across many addresses, so strong, unique passwords still matter most.

Hardening checklist

  • Change default credentials on every device the day it is installed; use unique, long passwords kept in a password manager.
  • Put IoT and cameras on a separate network segment (VLAN) with firewall rules that allow only what they need and block them from reaching your main computers.
  • Disable UPnP and do not forward ports to devices. Reach cameras through a VPN or a managed service with multi-factor authentication.
  • Turn off services you do not use (Telnet, remote shell, unused cloud features).
  • Update firmware, subscribe to vendor advisories and replace devices that are no longer supported.
  • Prefer devices with encrypted communication, signed updates and a published security contact.
  • Keep an inventory and monitor outbound connections. A smart plug that suddenly talks to unknown servers is worth a look (logging and SIEM).
  • Mind privacy: do not point cameras where people expect privacy, and limit retention.

More IoT risks and real examples

IoT problems repeat: default passwords, unpatched firmware, open management ports and insecure mobile and cloud interfaces, where the companion app or vendor cloud lacks authorization checks or sends data unencrypted. Real cases show the range: connected baby monitors with weak accounts, internet-exposed industrial chillers and refrigeration monitors that let outsiders change temperatures, and smart agricultural vehicles whose control interfaces raise safety questions. In each case the device was designed for convenience first.

CCTV system components and audit tooling

A camera system has more parts than the cameras: the DVR or NVR (digital or network video recorder) that stores footage, the management web and mobile apps, the network and the cloud account. Each can be attacked, so each needs hardening: change default credentials, update firmware, put cameras on their own VLAN with no internet access, disable UPnP and unused protocols, and enable encryption on the streaming protocol (RTSP). Open-source tools, including Nmap scripts such as rtsp-url-brute, let you audit your own cameras cost-effectively, but only against devices you own.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Why are default credentials such a common IoT problem?

    Shared defaults let attackers (and botnets) access huge numbers of devices automatically.
  2. 2. Which network design best limits damage from a compromised camera?

    Segmentation keeps a compromised device from reaching important systems.
  3. 3. What is a safe way to view cameras remotely?

    A VPN or protected service avoids exposing the device directly.
  4. 4. Which situation makes updating hardest, and therefore needs replacement?

    Unsupported devices accumulate unpatched vulnerabilities. Replace them or isolate them tightly.

Summary

  • IoT and CCTV devices are cheap, long-lived and often unpatched, with default credentials and cleartext traffic.
  • OWASP's IoT list covers weak passwords, insecure services, ecosystem interfaces, missing updates, old components, privacy and physical hardening.
  • An authorized assessment inventories devices, checks services, credentials, traffic, firmware and the cloud and mobile ecosystem.
  • Fixes: unique passwords, segmentation, no port forwarding, disabling unused services, updates or replacement, and monitoring.
  • Never access devices you do not own or have permission to test.

Next: Email Security and Email Attacks