Security language on baby monitor packaging has become dense: encrypted, bank-grade, military-grade, hack-proof, ISO-certified. Some of those words refer to something real. Very few of them tell you how the device in your nursery is actually protected — and one of them describes something no security engineer would ever promise.
Most security claims on baby monitors fall into one of four categories, and only one describes the specific product. Algorithm claims — “AES encryption,” “bank-grade,” “military-grade” — name a cipher, which is rarely where products fail; the weak points are usually key management, which parts of the journey are encrypted, and who can decrypt. Company claims — ISO 27001 and similar — certify an organisation’s management system, not a device. Absolute claims — “hack-proof,” “unhackable” — are unfalsifiable and aren’t made by security professionals about any connected product. Product and regulatory claims — conformity with a named product security standard or law — are the ones that actually attach to a device, and they can be checked against documentation. The questions that reveal real security are concrete: which legs of the journey are encrypted and who holds the keys, whether there are default or hardcoded credentials, how long security updates are promised, how vulnerabilities are reported, and what the attack surface is to begin with. A monitor with no internet connection answers several of these differently — not because it’s “unhackable,” but because it has far less exposed to begin with.
§01Why security words drift from security reality
Security is hard to show on a box. A buyer can see a camera’s resolution and a screen’s size; nobody can see a key-management scheme. So marketing reaches for words that convey reassurance, and the words that convey the most reassurance are rarely the ones that carry the most information.
The result is a pattern familiar from the health-claim language article: statements that are individually true, arranged to imply something broader than any of them establishes.
§02The four kinds of security claim
These name a cipher — usually AES — which is a genuinely strong, widely used standard. The problem is that the cipher is almost never the part that fails. Products that have been compromised typically used perfectly good algorithms and fell down elsewhere: keys hardcoded into firmware, some legs of the journey left unencrypted, servers that decrypt everything, or credentials that couldn’t be rotated.
“Bank-grade” and “military-grade” add nothing technical — they describe the algorithm’s pedigree, not the product’s implementation.
ASK INSTEAD: encrypted between which points, and who holds the keys that can decrypt it?ISO 27001 is a real and demanding standard — for an organisation’s information security management system. It certifies that a company runs defined processes for managing security risk within a stated scope. It is not a certification of any product, and a certificate’s scope may cover only part of a company’s operations.
That doesn’t make it meaningless: a company that has built a certified management system is more likely to handle security seriously. But it answers a question about the company’s processes, not about the device.
ASK INSTEAD: what does the certificate’s scope statement cover — and is there anything that certifies the product itself?These are the claims that genuinely attach to a device. Examples include conformity with EU radio equipment cybersecurity requirements (covered in the EN 18031 article), the UK’s product security regime for connectable consumer products — which among other things prohibits universal default passwords and requires published vulnerability reporting and a stated minimum security update period — and consumer IoT baseline standards.
These are checkable. A conformity claim should correspond to a declaration or statement naming the product and the requirement, which a seller should be able to produce.
ASK INSTEAD: which requirement, for which model, and can I see the declaration?No security engineer describes a connected product this way, because it isn’t a statement that can be true. Security is a matter of how much effort an attack requires and how quickly weaknesses are found and fixed — never of whether weaknesses can exist at all. An absolute claim tells you more about the marketing process than about the product.
It’s worth treating as a mild signal rather than a disqualification. A good product can be sold with a bad adjective. But it’s the one category that carries no information whatsoever.
ASK INSTEAD: how do I report a vulnerability, and how long will you ship security updates?FIG.01 — Ordered by informativeness, not by how reassuring they sound. The most prominent claims on packaging tend to sit on the left; the checkable ones are usually in small print or documentation, if they appear at all.
§03“Encrypted” — the questions it leaves open
Encryption is real protection, and a monitor with none would be a serious concern. But the single word hides three questions that determine what it’s actually worth:
| Question | Why it matters |
|---|---|
| WHICH LEGS? | Camera to server, server to app, and storage are separate stages. A claim can be true of one and silent about the others. |
| WHO CAN DECRYPT? | If video is decrypted at the manufacturer’s server before being re-encrypted to your phone, the server sees it in plain form. End-to-end encryption — where only your own devices hold the keys — is a different, stronger arrangement. |
| WHERE ARE THE KEYS? | Keys or credentials baked identically into every unit’s firmware are a common real-world failure. If one device is taken apart, the secret may unlock them all — and it can’t be changed without new firmware. |
TABLE.01 — Three questions that turn “encrypted” from a word into a design. None of them is answered by naming the cipher.
The third row isn’t hypothetical. The widely reported white-label platform vulnerability discussed in the FCC ID article was reported to involve static credentials and keys that couldn’t easily be rotated without reflashing deployed hardware — a key-management failure, not a cipher failure.
§04The questions that actually reveal security
§05What changes when there’s no internet connection
A monitor with no network path answers several of these questions differently — not by being “unhackable,” which no product is, but by having far less to attack in the first place. There’s no server holding footage, no account to take over, no app backend shared across brands, and no remote route for someone elsewhere in the world to reach the device.
The questions that remain are closer and narrower. A radio link carries video through the air between two units, so how that link and the pairing process are safeguarded still matters, and someone would need to be physically nearby to attempt anything. Frequency hopping makes casual interception much harder than a fixed-channel transmission, but it’s a transmission technique rather than encryption — a distinction worth keeping clear, as covered in the hub article.
§06How we describe our own products
We don’t describe our monitors as “hack-proof” or “unhackable,” and we’d encourage you to be sceptical of anyone — including no-WiFi competitors — who does. The accurate claim is narrower and, we think, more useful: our monitors use a dedicated FHSS link with no WiFi, no app, no account and no internet path, so the remote attack surface that connected monitors must defend doesn’t exist.
We also don’t lean on “military-grade” language. Frequency hopping is not encryption, and we won’t blur the two. What safeguards a specific model’s radio link and pairing use are set out in that model’s technical documentation, which we’ll provide on request — along with its conformity documentation for the markets you’re considering.
Specifications are on the product pages.
§07A short checklist
- Is it an algorithm, a company, an absolute, or a product claim? Only the last attaches to the device.
- Encrypted between which points, and can the manufacturer decrypt it?
- Are credentials unique per device, or is there a shared default?
- What’s the stated minimum period for security updates?
- Is there a published vulnerability reporting route?
- For company certificates: what does the scope statement cover?
- What is reachable from outside the home at all?
§08Frequently asked questions
What does “bank-grade encryption” mean on a baby monitor?
Usually that the product uses a strong standard cipher such as AES, the same family used in banking. It says nothing about how the encryption is implemented — which legs of the data’s journey are encrypted, who holds the keys, or whether credentials are stored safely. Compromised products have typically used perfectly good algorithms and failed elsewhere, so the useful follow-up is: encrypted between which points, and who can decrypt it?
Can a baby monitor be hack-proof?
No product can honestly be described that way. Security is a question of how much effort an attack takes and how quickly weaknesses are found and fixed, not of whether weaknesses can exist. Security professionals don’t make absolute claims about connected products, so “hack-proof” or “unhackable” carries no technical information. Better questions are how vulnerabilities are reported and how long security updates will be provided.
Does ISO 27001 mean a baby monitor is secure?
ISO 27001 certifies an organisation’s information security management system within a stated scope — the company’s processes, not a product. It suggests the company takes security seriously, which has value, but it doesn’t certify the device. Check what the certificate’s scope covers, and look separately for any claim that attaches to the product itself, such as conformity with a named product security requirement.
Is a no-WiFi baby monitor more secure?
It has a much smaller attack surface: no servers holding footage, no account to take over, no shared app backend, and no remote route in from outside the home. That’s a structural advantage, not a guarantee. The radio link between camera and parent unit still carries video, so how that link and pairing are safeguarded still matters, and frequency hopping — while it makes casual interception much harder — is a transmission technique rather than encryption.
What security questions should I ask before buying a baby monitor?
Which parts of the data’s journey are encrypted and whether the manufacturer can decrypt it; whether credentials are unique per device or shared defaults; the stated minimum period for security updates; whether there’s a published way to report vulnerabilities; whether the app supports two-factor authentication; and what is reachable from outside the home at all. Answers to these reveal far more than any adjective on the packaging.
Ask what’s exposed, not how strong the lock is
Our monitors have no internet path to defend — and we’ll still give you the documented safeguards for the radio link rather than an adjective. That’s the standard we’d apply to anyone’s claims.
Request technical documentation → info@truebondtech.com · WhatsApp +86 189 2846 4489 · View productsThis series