Module 9: Smart Home and IoT

Table of Contents
← Return to the Personal Security Course
A smart device combines computing, network access, and product-specific inputs or controls. Cameras and speakers include obvious sensors. Locks, lights, plugs, and appliances expose different event, state, account, and telemetry data. Review each product from its real hardware and service design.
This module covers the purchase decision, network segmentation for devices you did not build, voice assistant specifics, and wearables.
Budget about 30 minutes. Start with inventory, support status, data flows, and network policy.
What You Will Learn
- Evaluate a smart device against its data practices rather than its feature list
- Segment IoT devices onto a separate network from your computers
- Explain what voice assistants retain and what changes when you disable recording
- Assess which wearable sensors sample data, how often they run, and where records go
- Decide which home functions should never connect to the internet
- Produce a smart home record listing devices, network segment, and firmware status
| Term | Meaning |
|---|---|
| IoT | Internet of Things, meaning network-connected devices beyond computers and phones |
| Segmentation | Applying network boundaries and policy to restrict traffic between device groups |
| Default credential | A factory or shared credential which needs review and replacement where supported |
| Voice assistant | A device or service which handles voice input under product-specific local and remote processing rules |
| Telemetry | Usage data a device reports back to its vendor |
The Trade, Stated Plainly
Smart-home benefits and data costs vary by product. Compare required data, optional telemetry, local processing, cloud processing, retention, sharing, and service dependence against the household benefit.
| Category | Typical Collection | Honest Assessment |
|---|---|---|
| Smart speaker | Wake events, queries, audio, account activity, or device state under the selected settings | Review activation, indicators, retention, and linked accounts |
| Indoor camera | Video, motion events, audio, thumbnails, or account events under the selected settings | Review recording triggers, storage, sharing, and breach impact |
| Smart lock | Entry events, codes, users, battery state, or remote commands | Review access logs, recovery, overrides, and account security |
| Thermostat | Temperature, schedules, device state, or occupancy signals | Review remote access, sharing, and local operation |
| Smart lighting | Device state, schedules, scenes, and account events | Review whether cloud access adds enough household value |
| Fitness wearable | Sensor samples chosen by the model and enabled features | Review sampling, sync, export, retention, and deletion |
Give cameras and microphones close scrutiny. Their placement, account access, storage, retention, indicators, mute design, and sharing settings directly affect household privacy.
Ask the inverse question when considering a purchase: what is the worst outcome if this vendor is breached, and would I accept the outcome for what the device does?
What Earns a Place on Your Network
Run this before buying, not after.
- Does the device require an internet connection to function? Local operation reduces service dependence, while firmware, companion apps, supply chain, and optional cloud features might preserve vendor risk
- Does the vendor publish a privacy policy with specifics, or only generalities
- Does it support local control through a standard protocol rather than a vendor cloud
- Is there a firmware update history, and how recent is the last one
- Does it require a cloud account, and does your identity need to be real
Prefer a documented local control path when the design fits household needs. Local operation reduces cloud dependency. Vendor updates, account recovery, remote access, and controller security still need review.
Test Network Segmentation
Put suitable IoT devices on a restricted network segment. The firewall policy decides what a compromised device reaches.
| Setup | Effect |
|---|---|
| Guest network for IoT | Present on many routers. Isolation behavior needs a direct test |
| Dedicated VLAN | A separate broadcast domain. Firewall policy and router behavior determine isolation |
| Per-device blocking | Firewall rules denying outbound access for devices which do not need it |
Three rules for the IoT segment:
- Deny IoT access to computers and storage unless a documented function needs a narrow path. Test guest isolation and firewall behavior directly
- Deny internet access where the device does not need it, which applies to many bulbs and sensors
- Rename every device to something generic, so a device list does not describe your hardware to anyone who sees it
Our Network Security Checklist covers the segment design in more depth, and Module 6 covers the router configuration.
Voice Assistants
A voice assistant is a microphone with a network connection and a retention policy.
| Setting | What It Changes |
|---|---|
| Delete voice recordings | Removes stored audio, and review whether it also removes transcripts |
| Disable voice purchases | Removes the product’s supported voice-purchase path when the setting works as documented |
| Turn off personalization | Changes the uses described by the product. Verify retained history and other account data separately |
| Use the documented mute control | Reduces capture according to the product design. Verify whether the control is electrical or software based |
| Review linked accounts and skills | Third-party access follows current scopes, tokens, account links, and revocation behavior |
The mute design matters. A labeled physical control might still send a software command. Check the manual, teardown, or vendor design statement before treating the control as an electrical disconnect.
Consider whether the assistant needs to exist in bedrooms or rooms where you discuss sensitive matters. A microphone in a bedroom is a different risk from one in a kitchen.
Wearables
A wearable often samples data throughout the day, according to enabled sensors, settings, and use.
| Data | What It Reveals |
|---|---|
| Heart rate | Supports estimates or inferences offered by the device, subject to sensor and model limits |
| Movement and steps | Supports activity and routine estimates when sampling and retention are enabled |
| Sleep patterns | Supports estimated sleep windows and disturbances under the product method |
| Location | Records or infers journeys and stops when location features are enabled |
| Audio | Collection depends on sensors, settings, trigger design, and product behavior |
Review which parties receive wearable data through the vendor, connected apps, research programs, insurance benefits, employer programs, advertising systems, or legal process. Availability and restrictions vary by product, agreement, and jurisdiction.
Our dedicated analysis of the trade-offs: Privacy-First Smartwatch Options for Data-Savvy Users .
Safety-Critical Devices
Safety and accessibility devices need a separate decision.
- Life-safety systems. Require local alarms or operation, power-loss behavior, emergency contacts, and a tested offline path
- Access control. Document fail-secure or fail-safe behavior, mechanical override, battery replacement, and household accessibility needs
- Water and heating controls. Keep local operation and freeze or leak protection after internet or vendor-service loss
Connected products sometimes add monitored safety or accessibility. Decide from fail-safe behavior, local control, power, support lifetime, household needs, and recovery evidence. Include devices in outbuildings or other places with unreliable connectivity in the offline test.
The test is the failure mode. Ask what happens when the internet is down, when the vendor shuts down, or when the account is locked. If the answer is unacceptable, the device belongs on a local-only path or nowhere.
Cloud service closure or account loss might remove remote features or core operation. Record the product’s documented offline behavior, support policy, export path, and mechanical or local fallback.

The Smart Home Record
SMART HOME RECORD
Devices:
- ______________________ segment: ______ internet: yes / no / blocked
- ______________________ segment: ______ internet: yes / no / blocked
- ______________________ segment: ______ internet: yes / no / blocked
- ______________________ segment: ______ internet: yes / no / blocked
Network:
IoT segment: guest network / VLAN / none
Devices blocked from internet: ______________________
Device names anonymized: yes / no
Firmware:
Auto-update enabled: ______________________
Last manual check: ______________________
Voice assistants:
Physical mute: yes / no
Voice recordings deleted: yes / no
Personalization off: yes / no
Skills/accounts reviewed: yes / no
Local-only (no cloud dependency):
- ______________________
Practice and Verify
Inventory first. Change one low-impact device before moving a lock, alarm, medical device, heating control, or water control.
- Record each device, model, owner account, network, data types, controller, firmware, and support date.
- Draw arrows from the device to the phone, hub, vendor cloud, voice assistant, and third parties.
- Move one bulb or plug to the IoT segment.
- Test peer access, trusted-LAN access, internet access, IPv6, DNS, local control, remote control, and casting.
- Turn off internet access briefly where safe. Record which functions remain.
- Review account recovery and remove an old household member or linked service.
Expected Result: the selected device reaches only required services, household control still works, firmware state is known, and loss of vendor service has a documented outcome.
If discovery fails, restore the original network and inspect the protocol before adding a narrow firewall exception. If the device has no supported update path or recovery owner, increase isolation, replace the device, or document a removal date. Restore safety controls immediately after any bounded test.
REDACTED EXAMPLE
Device: smart plug, model hidden
Data flow: plug to local hub to vendor cloud
Firmware/support: current, support date published
IoT-to-LAN: blocked
Internet off test: local switch worked, schedules failed
Recovery owner: household admin
Removal trigger: end of security updates
Pass checklist
- Every device has an owner, support status, data flow, and removal trigger
- Network tests cover peer, LAN, internet, IPv6, DNS, and required discovery
- Local, power-loss, and vendor-end-of-service behavior are recorded
- Safety and accessibility needs appear in the decision
- Account recovery and household access were reviewed
Primary reference, checked 2026-10-10: NIST IR 8425 consumer IoT profile , including device identification, configuration, data protection, access control, updates, and state awareness.
Next Steps
- Continue to Module 10 and protect your accounts and cards: Personal Finance Security
- Move one low-impact IoT device to a tested restricted segment before changing safety-critical devices
- Delete stored voice recordings and disable voice purchasing
- Rename each device so the list does not describe your hardware
- Review the smart home checklist for the organizational version: Physical Security Checklist
- Read the smartwatch comparison before buying a wearable: Privacy-First Smartwatch Options


