IoT Security Solutions: How to Inventory and Segment Devices
Connected cameras and building controllers need an inventory, network separation, unique credentials and a named responder. This is the order to work in and who owns each step.
Buying a connected device does not make it secure. IoT security solutions start with knowing it is there, separating it from business systems, replacing default credentials and assigning someone to respond to alerts. For a camera or building controller, those controls matter more than another product on the purchase order.
Why does a new controller end up on the office network?
Usually because nobody planned its connection. A contractor installs an access controller, finds a live switch port and gets it working. The controller now shares a network with accounting systems, but nobody adds it to the device inventory. The exposure stays invisible until someone looks.
A building controller is a computer, often without endpoint protection or a reliable update path. Treat it as an unmanaged device from the moment it powers on. If its default password is still active, change it promptly through a controlled process rather than waiting for the next scheduled review.
Who owns the device inventory, and what does it reconcile?
Inventory comes before segmentation. You cannot separate devices you have not identified. Assign one owner for the connected-device list, with IT checking network records and facilities confirming contractor installations.
Reconcile four sources before you design the segments:
- The building system's device list or controller dashboard
- The DHCP lease table from your network
- The switch MAC address tables, which help locate connected devices
- The vendor's installation records
Devices appearing in only one list deserve attention first. A device visible on a switch but missing from installation records needs an owner and a purpose before you can approve its access. Record its location and firmware version first, then name the vendor responsible for it.
How should devices be segmented from business systems?
Separate connected building equipment from your business network. Block its access to sensitive systems such as payroll. Allow only the connections each device needs, then deny the rest by default.
A camera that sends video to a recorder has no reason to reach payroll. Enforce that boundary with network controls rather than relying on a diagram that labels the two systems as separate. Ask the vendor which ports the camera needs to reach the recorder, then allow those and nothing more.
Segmentation can break device functions. Older equipment may depend on discovery traffic that does not cross network boundaries, and vendors accustomed to unrestricted remote access will push back. Test required functions before the change and again afterward. Do not restore unrestricted access just to close the installation ticket.
Where each device class goes
Group devices by function and required access, not just by vendor. This is a starting design, not a universal configuration. Confirm each permitted connection against the system's actual requirements.
| Device class | Segment | Allowed outbound |
|---|---|---|
| Cameras and recorders | Video segment | Recorder and required services, including vendor cloud if used |
| Door and access controllers | Access segment | Access server and required services |
| HVAC and building controllers | Building systems segment | Building management server and approved vendor support path |
| Environmental sensors | Sensor segment | Collection point and required services |
Writing down the exceptions
Every exception needs a written reason and an end date. Review the register every quarter alongside the inventory. An expired support requirement should not leave a permanent route into your network.
What authentication should every device enforce?
Default-password findings are a procurement failure before they are a security failure. Before buying, ask the vendor to document the credentials supplied at delivery, the security update method and support period, and the remote support route. “We follow best practices” answers none of those questions.
Change default credentials before connecting the device to the production network. Make this a documented installation step, not a favor someone remembers to perform. Store credentials in a password manager with a named owner.
- Give every device its own credential. Do not share logins between devices or among vendor staff.
- Disable unused management protocols, external web administration and unnecessary auto-discovery features.
- Require multi-factor authentication on every external vendor access path.
- Use certificate-based authentication wherever the device supports it.
- Verify the update process in a planned test window before relying on it.
If a device cannot be authenticated or updated, it should not sit on the business network, whatever it cost. Identify that limitation before purchase, when replacing the proposed device is cheaper than replacing an installed system.
Who responds when a device does something new?
Log device connections at the firewall. Alert on new devices and on unfamiliar outbound destinations. Assign a responder for business hours and another for after-hours coverage, including holiday weekends, with current contact details in the runbook.
An alert without an assigned responder is a log entry, not an operating control. The responder needs authority to investigate and a documented escalation path when a device supports a critical building function.
Bring in qualified help if a controller contacts unexplained external addresses, former staff still know its credentials, or an incident reaches the access control system. Avoid rebooting as a first response because it can destroy evidence. Record what you observed and when; coordinate any isolation with the person responsible for building safety and continuity.
What should the first week look like?
Use the first week to establish ownership and address exposed credentials. Work through the sequence below, scheduling network changes around testing and building operations rather than forcing every change into a one-week deadline.
- Reconcile the four source lists into one inventory. Name an owner for each device.
- Identify default credentials and replace them through documented changes.
- Plan separate segments by device function. Prioritize equipment with access to sensitive business systems and test before moving it.
- Record required exceptions with a reason, vendor contact and end date.
- Enable firewall logging and alerts. Name the business-hours and after-hours responders.
- Add building controls to the continuity review. In Texas, summer heat makes HVAC operationally critical. Decide who can authorize isolation and how the building will operate afterward.
This work crosses IT and facilities. It needs one accountable program owner, not separate tickets with no one responsible for the result. We run Enterprise Security Risk Management programs across 13 risk domains for mid-market organizations, with reporting directly to the board. Our business continuity work addresses the operational side of security decisions.
If responsibility for connected devices is split between your IT team and building vendors, book a 30-minute risk discussion or call 817-677-0515 to discuss program ownership.
Frequently asked questions
What is IoT security?
IoT security protects connected devices, such as networked cameras, and controls their access to other systems. It starts with an accurate inventory and includes network separation, device authentication, updates and monitoring. Someone must own those controls after installation.
Is CCTV an IoT device?
A network-connected CCTV camera is an IoT device; an analog camera without a network connection is not. A networked camera needs unique credentials and restricted access to other systems. Check the recorder too, because it can provide a network connection even when the cameras themselves are analog.
Does a firewall alone secure connected devices?
No. A firewall restricts network traffic, but it does not replace default passwords or install device updates. Use it to enforce separation while managing credentials and firmware on the devices themselves.
What do we do when a vendor says it needs flat network access for remote support?
Ask the vendor to identify the exact systems and ports its support process requires. Provide a restricted support path with multi-factor authentication rather than granting unrestricted access. Document any approved exception with a reason and an end date, then review it quarterly.
Does this replace endpoint protection for our laptops and servers?
No. Laptops and servers still need endpoint protection and their own security controls. Connected building devices often cannot run those tools, so they require separate controls for network access, credentials and updates.
Total 360 Security provides virtual Chief Security Officer, vCISO, and Enterprise Security Risk Management programs for mid-market organizations. They design, run, and report security programs covering all 13 risk domains rather than just offering advisory decks or point solutions. The firm is Texas DPS-licensed with CPP, CISSP, and CISM credentials.
Serving Texas, California, Nevada, New Mexico.
More from the blog
10 min read
Identity Access Management Software: What to Govern First
A practical order for identity access management software: define privileged access, name an owner, inventory raw exports and review each quarter before buying a tool.
Read article7 min read
SOC 2 Audit: What Type II Requires and Who Owns Each Control
A SOC 2 audit is an independent CPA examination of your controls against the AICPA criteria. Here is what a Type II report requires, who owns each control and what evidence to keep.
Read article7 min read
Compliance Monitoring: What to Check Monthly and Quarterly
Compliance monitoring is the ongoing check that your operations follow the rules that apply to you. This guide sets a monthly evidence set, a quarterly sampling routine and clear ownership for every exception.
Read article