What's Happening Right Now
The modern office is no longer just computers and phones. HVAC controllers, IP cameras, smart locks, industrial sensors, and networked printers form a sprawling internet of things (IoT) and operational technology (OT) ecosystem. By mid-2025, threat intelligence tracking showed that attackers were systematically targeting these connected devices as low-effort entry points into corporate networks. Unlike workstations, which are hardened with endpoint detection and regular patching, IoT and OT devices are often deployed with factory-default credentials, run legacy operating systems, and are never updated.
The FBI’s Internet Crime Complaint Center (IC3) and CISA have repeatedly highlighted this shift. Attackers no longer need to crack a CFO’s email to get inside. They scan for open ports on smart cameras, exploit unpatched printer firmware, or hijack unsecured HVAC gateways. Once inside, they use these devices as pivots to reach critical systems. NIST’s 2025–2026 IoT cybersecurity guidelines explicitly warn that flat network architectures are the primary enabler of this threat. When a compromised thermostat can talk to the same switch as your financial database, the entire business is exposed.
How This Attack Works
Understanding the attack chain helps you visualize why a $200 office printer matters as much as your server room. Here is how it typically unfolds in a non-technical environment:
- 1Reconnaissance: Attackers scan the internet or internal network for devices with open management ports (often TCP 80, 443, or 8080). Many IoT devices broadcast their presence on networks due to UPnP or mDNS protocols.
- 2Initial Access: The attacker logs in using default credentials (e.g., admin/admin) or exploits a known unpatched vulnerability. MITRE ATT&CK labels this under T1190 (Exploit Public-Facing Application) and T1078 (Valid Accounts).
- 3Lateral Movement: The compromised device is not the end goal. It is a foothold. From an IP camera or smart lock hub, attackers scan adjacent subnets, looking for credentials, unencrypted file shares, or admin consoles. The Verkada breach playbook demonstrates how cloud-managed IoT devices can leak session tokens, allowing direct network access without touching employee endpoints.
- 4Impact: Once inside, attackers deploy ransomware, exfiltrate sensitive data, or manipulate OT controls. Mirai-style infections turn IoT bots into distributed networks that can flood systems or hold them hostage. In manufacturing and logistics, OT pivoting can halt production lines or trigger safety shutdowns.
Real-World Examples
The Verkada incident remains a textbook case of how cloud-connected IoT bypasses traditional perimeters. In 2021, attackers harvested admin credentials from Verkada’s cloud portal, gaining access to live feeds and, critically, internal network access. The playbook is still active in 2025–2026, with threat actors now automating credential harvesting via phishing kits targeting IoT management dashboards.
In a documented 2024–2025 CISA case study, a mid-sized distribution center with roughly 150 employees experienced a ransomware event that originated from an unsecured network printer. The device ran outdated firmware, used a static IP, and shared a flat VLAN with the company’s ERP system. Attackers pivoted through the printer’s embedded web server, compromised a service account, and encrypted the order management database. Recovery cost exceeded $400,000 in downtime and remediation.
Another pattern emerging this year involves HVAC and building management systems. A regional healthcare clinic discovered that a compromised smart thermostat controller allowed attackers to bypass their perimeter firewall, ultimately leading to the exfiltration of patient scheduling data. These incidents are not hypothetical. They are happening because SMEs treat IoT as plug-and-play rather than network infrastructure.
Who Is Most at Risk
Businesses with 10 to 500 employees are disproportionately exposed. SMEs typically lack dedicated security teams, rely on generalist IT staff, and operate on flat networks to simplify connectivity. Industries like manufacturing, logistics, professional services, and healthcare are prime targets because they rely heavily on OT and IoT for daily operations.
CISA’s 2025 IoT/OT hardening guidance notes that organizations with fewer than 500 employees account for nearly half of all IoT-brokered breaches. The risk compounds when vendors manage devices remotely without encrypted tunnels, when contracts expire leaving devices unsupported, or when procurement prioritizes cost over security certifications. If your business uses connected cameras, access control systems, industrial sensors, or networked printers, you are already in the attack path.
Warning Signs to Watch For
You don’t need a SIEM to spot IoT compromise. Watch for these specific red flags:
- Unknown MAC addresses or device names appearing on your network scan
- Smart displays, cameras, or printers reacting to unsolicited commands or displaying gibberish
- Unusual outbound traffic from non-computer devices (e.g., a printer suddenly sending large data packets at 2 AM)
- Repeated failed login attempts on device management interfaces logged by your firewall
- Network slowdowns that coincide with new device deployments or firmware updates
- Alerts from your phone or email about unusual activity from cloud-managed IoT dashboards
- Devices stuck on old firmware versions with no vendor patch history
NIST SP 800-183 recommends treating these signals as indicators of compromise. IoT devices should behave predictably; deviations often mean they have been repurposed by malware.
How to Protect Your Business
Securing IoT and OT requires a defense-in-depth approach, not a single silver bullet. Start by inventorying every connected device, then apply controls that limit blast radius:
Network Segmentation: Place all IoT/OT devices on a dedicated VLAN with strict firewall rules. They should only communicate with what they absolutely need to. Block all outbound internet access unless explicitly required for firmware updates. Use CIS Controls v8 (Control 13: Network Monitoring and Defense) to enforce this.
Credential and Access Hygiene: Disable factory defaults immediately. Enable phishing-resistant MFA for all device admin interfaces (hardware security keys or passkeys, never SMS). Disable UPnP, mDNS, and Telnet/FTP services. Use the principle of least privilege for any cloud management portals.
Firmware and Lifecycle Management: Create a mandatory firmware update schedule. Test updates in a lab environment before deployment. Retire devices that reach end-of-life (EOL) or lack vendor security patches. NIST IR 8259-2 explicitly mandates lifecycle tracking for all connected assets.
Monitoring and Detection: Deploy network access control (NAC) or lightweight IoT monitoring tools that flag anomalous behavior. Map your devices to MITRE ATT&CK techniques (e.g., T1548.001 for abuse of configuration) and set up alerts for lateral movement patterns.
Vendor Accountability: Require security documentation during procurement. Ask for SBOMs (Software Bill of Materials), encryption standards, and patch response SLAs. Never approve a device that cannot be isolated from your primary business network.
Quick Action Checklist
Prioritize these steps by impact. Start here this week:
- [ ] Run an automated network scan to catalog all IoT, OT, and smart office devices
- [ ] Immediately change all default passwords and disable cloud management portals that lack encryption or MFA
- [ ] Move all IoT/OT devices to a segregated VLAN with outbound internet blocked by default
- [ ] Disable unused services: UPnP, mDNS, Telnet, FTP, and any remote access features
- [ ] Schedule and test firmware updates for all critical devices; document support end dates
- [ ] Deploy NAC or network monitoring to alert on anomalous IoT traffic and unauthorized device connections
- [ ] Review vendor contracts and EOL policies; replace or air-gap unsupported devices
Start Here This Week. Pick one network segment, isolate it, scan it, and secure it. IoT security is not about buying more tools—it is about treating every connected device as a potential network gateway and applying the same rigor to a smart thermostat as you do to your firewall. Your IT team can start with the checklist above. If you need help mapping your IoT inventory or designing a segmented network architecture, IJE Software’s security consultants are ready to guide you through the first 30 days of hardening.