3 in 10 IP Cameras Exposed Other Users' Video — A CCTV Security Checklist Built from the KISA Inspection

On November 12, 2026, the Korea Consumer Agency and the Korea Internet & Security Agency (KISA) published the results of a security inspection of 10 IP camera products sold in Korea. In 3 of them, user authentication was weak enough that an attacker could download other users' camera video and images or control the camera remotely. If you run IP cameras in a shop, an office, or an apartment management office, the first question is probably "Are our cameras safe?"

Look closely at the results, though, and many items cannot be answered by checking a single camera. Transport encryption, firmware security settings, and the security update support period are things the buyer cannot change. This post summarizes the inspection results and offers a CCTV security checklist in three layers: camera, network, and recording system. For the recording system layer, we also explain which NOX NVR/VMS features back up each item.

What did the inspection find?

The 10 products were chosen based on online store sales rankings and a consumer survey, and they were checked against 37 items covering the device (hardware, network, firmware), the mobile app, and policy and management. As reported by Boannews (2026-11-12), the results were:

FindingProducts
Weak user authentication — other users' video and images could be taken, and the camera controlled remotely3
No secure communication protocol8
Weak password policy5
Security update support period not stated6
Test port left enabled4
Firmware security settings need improvementAll 10

The 3 products with weak user authentication were the RoboView GI-ROBOA7, the VSTARCAM-800X, and the Fineview K11. According to the report, RoboView and Fineview replied with improvement plans and completed the fixes, and VSTARCAM's fix was still in progress. KISA recommended fixes to the manufacturers and said it would keep checking that they are carried out. The report does not mention any actual exploitation.

Note that while the authentication flaw affected a few products, transport encryption (8), update support periods (6), and firmware settings (all 10) were problems across most of them. Avoiding a particular brand is not enough.

Why isn't replacing the camera enough?

Camera security problems fall into two groups. Some the user can fix (default passwords, unneeded remote features, open router ports). Others only the manufacturer can fix (the authentication design, transport encryption, firmware settings, update support). Most of the frequent findings in this inspection belong to the second group. The camera you use today could be reported with a new flaw tomorrow, and if the manufacturer does not ship a patch, there is little the user can do.

Two other reports from the same week point the same way.

  • Older cameras with no support. A Boannews column (2026-11-14) advised against keeping cameras whose last firmware update is more than a year old or that are announced as end of life (EOL), and stressed deleting port forwarding and UPnP rules on the router by hand. Unplugging the camera does not remove the router's open-port rules.
  • Everything tied to one central server. Boannews (2026-11-09) reported that on October 30 an outside connection attempt through an overseas VPN was detected on the central server of an apartment home-network operator. The first-line defense system blocked it, and the operator pre-emptively closed its external integration ports. What was reported was an intrusion attempt; no leak was confirmed. Still, the security industry pointed out that if such a server were taken over, it could lead to covert recording through in-home cameras — and in 2021, wall-pad camera footage from about 400,000 households in 638 apartment complexes was leaked.

The conclusion is simple. You need a structure that stays safe even if you cannot trust the cameras: cut the cameras off from the internet, bring every way in to view video down to one entrance, and guard that entrance properly. The checklist below follows that order.

Checklist layer 1: what should you check on the cameras?

The camera layer is what users can do right away. Installers should record these items on new installations and during routine inspections.

  1. Check the model and its support status. Use the model name and manufacturing date on the camera label to find the manufacturer's support page, and check the date of the last firmware and whether the model has reached end of life.
  2. Change the default password, and use a different one per camera. If every camera shares a password, one compromised camera opens them all.
  3. Turn off remote features you do not use. The manufacturer's P2P cloud connection, remote-access app pairing, and UPnP are often unnecessary at sites where video is viewed through a recording system.
  4. Update the firmware. If the model is no longer supported, plan its replacement (see "Do older cameras need to be replaced right away?" below).

Checklist layer 2: what should you check on the network?

The most frequent finding in the inspection was "no secure communication protocol" (8 products). You cannot change how a camera communicates, but you can decide on the network how far that traffic goes.

  1. Delete port forwarding and UPnP rules on the router. Remove every outside path that leads straight to a camera.
  2. Block the cameras' outbound internet access. Use the router's access control (outbound IP blocking) feature so cameras cannot reach the outside. Step-by-step instructions for ipTime routers are in How to Isolate Chinese IP Cameras from the Internet and Use Them Safely with NOX.
  3. Bring the way in for viewing video down to the recording system alone. If video must be viewed remotely, connect to the NVR/VMS, not the cameras. Where possible, coming in over a VPN leaves a smaller attack surface than opening ports.
  4. Where possible, put cameras and office PCs on separate networks. If an infected device sits on the same network, blocking outside traffic alone will not stop it.

With these changes, traffic between the cameras and the recording system stays inside the site's internal network, and the only thing visible from outside is the recording system. That makes the next layer — the recording system's own security — decisive for the whole site.

Checklist layer 3: what should you check on the recording system (NVR/VMS)?

Once there is a single entrance, it only helps if that entrance is stronger than the cameras. Here are the items to check when choosing or inspecting a recording system, and how NOX handles each one.

Item to checkHow NOX handles it
Can the default account be left in use?Changing the password and account name is mandatory at first login. Until the initial setup is done, everything is blocked — not only the screens but also the API, live video, notifications, and outside ONVIF and RTSP connections
Are weak passwords rejected?Passwords need at least 9 characters with at least one digit, uppercase letter, lowercase letter, and special character; values matching the user ID, repeated characters, and keyboard sequences are rejected
Are password-guessing attacks stopped?Accounts lock automatically after repeated failed logins (5 failures locks for 5 minutes by default, adjustable in security settings)
Do unattended screens stay logged in?Sessions end automatically after inactivity (1 to 10 minutes, 10 by default)
Is the connection encrypted?Web access uses HTTPS (TLS 1.2 or later)
Are camera passwords kept in plain text?Camera passwords are stored encrypted, and credentials embedded in camera addresses are stripped out and stored encrypted as well
Can you separate who sees which cameras?Role-based access control, resource groups, and per-camera permissions. General access and administrative access are also separated
Is there a record of who did what?The audit log is chained with SHA-256 hashes to detect tampering, and it can be sent to an outside log server over remote syslog (TLS)
Is exported video safe if it leaks?Backups are encrypted with AES-256-GCM and integrity-checked. Faces, people, and license plates can also be masked when exporting

These items follow the same axes as the 10 security requirement areas that NOX is aligned with under Korea's NIS (National Intelligence Service) security requirements for video surveillance products — identification and authentication, access control, session management, audit records, data protection, and more. Even outside the public sector, checking a recording system along these axes leaves few gaps. For details, see NVR/VMS Guide to NIS Security Requirements V3.0 Certification.

On devices running in NIS security mode, administrative access can also be limited to an allowlist of IP addresses. If the allowlist is empty, administrative access is possible only from the device's local screen.

Do older cameras need to be replaced right away?

Realistically, replacing every camera at once is hard. The Boannews column suggests that an unsupported camera that still works well can be disconnected from the network entirely and used only for SD card recording. For a home camera, that is a good option.

Sites that manage many cameras through a recording system have a middle step: block the cameras from the internet and let NOX, on the same internal network, receive and record their video over ONVIF and RTSP. Only NOX is visible from outside, so the cameras' flaws are not directly exposed. This reduces the risk but does not remove it. If another infected device gets onto the internal network, the cameras can still be attacked, so schedule the replacement of unsupported cameras as well.

The hassle in replacing a camera is deleting it and registering it again, which breaks its settings and history. NOX's device replacement feature swaps in the new device while keeping the camera ID. It checks the new device's connection before applying the change and lists the retained settings, such as masking, that you should re-check against the new field of view. That makes it easy to plan replacing older cameras one at a time.

For cameras you retire, follow the column's advice: do a factory reset, and when disposing of them for good, physically destroy the internal memory so Wi-Fi details and remaining video cannot be recovered.

How should you explain this to management offices and customers?

When news like this breaks, installers get asked, "Are our cameras at risk too?" Answering with structure rather than brands is more accurate, and the answer holds up longer.

"The cameras are cut off from the internet, and video can be viewed only through one recording server. That server cannot be used with a default password, locks accounts after repeated failed logins, and keeps a record of who connected, when, and what they did."

Add the checklist above as a routine inspection item and it becomes part of the case for a maintenance contract. Reporting security checks together with operational checks such as recording gaps, offline cameras, and disk health makes the value clear to the customer.

Wrapping up

What the inspection showed is not just a problem with particular products. Parts the user cannot change — transport encryption, firmware settings, update support — affect most cameras. That is why the structure you place cameras in matters as much as which cameras you choose. Cut the cameras off from the outside, bring the way in down to one recording system, and guard that entrance with authentication, lockout, session limits, and audit records.

NOX is NVR/VMS software installed on general-purpose x86 servers, so you can build this structure while keeping your existing cameras. We can recommend the edition and configuration that fit your site in a consultation.

If you would like a review of the security setup at an existing CCTV site, please request a NOX consultation.

The inspection results in this post are summarized from Boannews reports (2026-11-09, 11-12, 11-14), and each product's fix status is as of the report. Check with the manufacturers and the original articles for the latest status.


Related Posts